One thing we do at Overstock.com<http://Overstock.com> to try and help with this concern in our dev and test environments is to require that an expiration date is associated with each Openstack resource. As users spin up an environment, they have an expiration date such that if they don’t renew their ‘lease’, their instances are suspended and then destroyed shortly thereafter. This expiration information is stored outside Openstack in the system that they interact with for requesting resources.
Doesn’t solve all your problems - since users can (and often do) just renew their environments all the time, but it does ensure that if people do not tell us that they are still actively using their resources, that they are removed. On Jul 23, 2017, at 5:51 PM, Manuel Sopena Ballesteros <manuel...@garvan.org.au<mailto:manuel...@garvan.org.au>> wrote: Dear Openstack community, We are a medical research institute and we have been running HPC for many years, we started playing with Openstack a few months ago and we like it’s flexibility to deploy multiple environments. However we are quite concern about the resource utilization, what I mean is that, in HPC the resources are released for the rest of the community once job has finished, however a VM keeps the resources for the owner of the vm until the instance is killed. I would like to ask, how do you organize your resources used by Openstack to maximize utilization across the organization? Thank you very much Manuel Sopena Ballesteros | Big data Engineer Garvan Institute of Medical Research The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010 T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: manuel...@garvan.org.au<mailto:manuel...@garvan.org.au> NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed. _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ________________________________ CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
