Hi,
We plan to introduce support for gluster tasks in oVirt, using the
current Jobs/steps framework. Which means, any gluster async task
started on a cluster will be shown as a Job in the "Tasks" tab. While
this helps in listing and monitoring the status of all gluster tasks, we
have a requirement to support a set of actions on such tasks. One should
be able to select a task, and then, if supported for that task, perform
one or more of the following actions on it:
- pause
- resume
- abort
- commit
I think this can probably be achieved by introducing a generic mechanism
for performing actions on task, allowing each type of task to define
what actions are allowed on it in it's current state.
Requesting opinions/suggestions on possible ways to achieve this
requirement.
Thanks,
Shireesh
_______________________________________________
Engine-devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-devel
