Comment 3 for bug 1259910

Looks reasonable. I'd like to clarify the following:

1. "only one "state change task" is allowed to run at the same time per node" Isn't it something that "shared=False" currently does? And what do you think about other tasks, f.e. do_node_deploy discussed recently. Do we need to similar singletone task for this one?

2. You said that the method that creates the new task resource is synchronous, is it something that already exist, or you're going to implement this in RPC interface?

3. If it's synchronous then I assume it won't do actual job, just register a task, get lock and that's all, am I right? If so, then how we're going to start the job? Will it be some conductor periodic task that picks all tasks registered in db and start them, or will it be another RPC call (async) to start the task?