[Openstack-operators] Blazar? (Reservations and/or scheduled termination)

Blair Bethwaite blair.bethwaite at gmail.com
Thu Aug 4 03:12:41 UTC 2016


On 4 August 2016 at 12:48, Sam Morrison <sorrison at gmail.com> wrote:
>
>> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren <klindgren at godaddy.com> wrote:
>>
>> We do something similar.  We give everyone in the company an account on the internal cloud.  By default they have a user-<username> project.  We have a Jenkins job that adds metadata to all vm’s that are in user- projects.  We then have additional jobs that read that metadata and determine when the VM has been alive for x period of time.  At 45 days we send an email saying that we will remove the vm in 15 days, and they can request a 30 day extension (which really just resets some metadata information on the vm).  On day 60 the vm is shut down and removed.  For non user- projects, people are allowed to have their vm’s created as long as they want.
>
> What stops a user modifying the metadata? Do you have novas policy.json set up so they can’t?

System-metadata?

-- 
Cheers,
~Blairo



More information about the OpenStack-operators mailing list