Open Stack

See inline.

Sent from my iPad

> On Aug 3, 2016, at 8:49 PM, 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?
> 
> Sam
> 

Technically nothing.  Most users don't know about metadata and they don't look at their vm's very hard.  For us it help clean up the cruft.  But if someone is willing to update the metadata on their vm every 15 days, imho they can keep it running in their user- project.  We are mainly trying to auto cleanup cruft that users did for testing and then forgot about.


> 
>> 
>> I believe I remember seeing something presented in the paris(?) time frame by overstock(?) that would treat vm’s more as a lease.  IE You get an env for 90 days, it goes away at the end of that.
>> 
>> 
>> ___________________________________________________________________
>> Kris Lindgren
>> Senior Linux Systems Engineer
>> GoDaddy
>> 
>> On 8/3/16, 10:47 AM, "Jonathan D. Proulx" <jon at csail.mit.edu> wrote:
>> 
>>   Hi All,
>> 
>>   As a private cloud operatior who doesn't charge internal users, I'd
>>   really like a way to force users to set an exiration time on their
>>   instances so if they forget about them they go away.
>> 
>>   I'd though Blazar was the thing to look at and Chameleoncloud.org
>>   seems to be using it (any of you around here?) but it also doesn't
>>   look like it's seen substantive work in a long time.
>> 
>>   Anyone have operational exprience with blazar to share or other
>>   solutions?
>> 
>>   -Jon
>> 
>>   _______________________________________________
>>   OpenStack-operators mailing list
>>   OpenStack-operators at lists.openstack.org
>>   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> 
>> 
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>