Description of problem:
By creating pool with big number of VMs user now can't stop the creation of VMs and after that start it again.
When user creates pool and after that he realize that he created the pool wrongly (e.g from wrong template). He has to wait until all the Vms are created before he can remove the pool and create another one.
Another situation occured when I created pool from template with cinder disk a the cinder server returns error. The creation of VMs stops and after fixing the cinder problem I cannot continue to create the VMs.
That's too bad, but I do not see what to do about it. Pool creation is a non-frequent operation, so you need to be careful what you do
Anyone any other thought?
(In reply to Michal Skrivanek from comment #1)
> That's too bad, but I do not see what to do about it. Pool creation is a
> non-frequent operation, so you need to be careful what you do
> Anyone any other thought?
BTW, you should be much more concerned with deletion - that you can't stop in the middle or undo it.