[Engine-devel] Task Manager Design Review

[Itamar Heim]

On 01/01/2012 02:39 AM, Moti Asayag wrote:
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel

looks pretty comprehensive - a few questions:
1. can one see all audit log events related to a task?

2. "A command with VDSM tasks" - what about other types of tasks? what 
if after the vdsm tasks there is another part of logic, then another 
vdsm task (iirc, there was a legacy limitation of "one single async task 
in the end of the command", but this shouldn't be relevant any more).

3. "A command which invokes internal commands - By default, the internal 
command will not be presented as a step of the parent command."

examples of the non default behavior?

4. "A customized command - an asynchronous job which its termination is 
decided by an event other than tasks. There are few types of scenarios 
for it"
the examples are all described as internal implementation details - what 
are some actual relevant use cases/flows and what will the user see for 
them?

you also mention AddVdsCommand here - will it's internal steps be 
visible to the user as part of the monitored task?

5. requirements: what about internal tasks originated by the system (SPM 
election, live migration due to load balancing, fencing taking place, 
refresh of users from a directory, etc.)?


6. STEP table, start_time is "not null" - shouldn't it be nullable?

7. UX - no main tasks view?

8. can i define a step based on a previous step failure rather than 
success (i.e., step 2 will be run only if step 1 succeeds, step 3 will 
only run if step 1 failed, step 4 could be either dependent on any of 
them, or run after step 2 and 3 finished, whatever their result was.

9. REST API modeling?