Open Stack

so some questions

- how can we decide ( identify ) if the VM to delete  can indeed be deleted
- Can we better enforce quota per app / cluster level
- This delete from older VM can only  work if these are individual VM
operating only to support work loads ( and not as standalone apps ) ?


On Tue, Jun 17, 2014 at 2:18 PM, Tim Bell <Tim.Bell at cern.ch> wrote:

>
>
> We have some projects which are dynamically creating VMs up to their
> quota. Under some circumstances, as cloud administrators, we would like
> these projects to shrink and make room for other higher priority work.
>
>
>
> We had investigated setting the project quota below the current
> utilisation (i.e. effectively delete only, no create). This will eventually
> match the desired level of VMs as the dynamic workload leads to old VMs
> being deleted and new ones cannot be created.
>
>
>
> However, OpenStack does not allow a quota to be set to below the current
> usage.
>
>
>
> This seems a little restrictive … any thoughts from others ?
>
>
>
> Tim
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140617/51d79211/attachment.html>