+1 from me on this work

+ sync-dev
+ mark


----- Original Message -----
From: "Benson Wong" <[email protected]>
To: "Lloyd Hilaiel" <[email protected]>
Cc: [email protected], "Gene Wood" <[email protected]>
Sent: Wednesday, September 25, 2013 10:29:14 AM
Subject: Re: Managing our AWS instances

Hi, 

That would solve the "who does this box belong to?" problem we currently have. 
I keep wanting to be able to stop/start a box on demand for the dev boxes, 
similar to what Heroku does. 

I've been rethinking the reaping strategy. So a plan/action items: 

- in the PROD account, identify the AWSBoxes that are running services that 
should keep running. Ie: 123done.org, etc. 
- make sure all Awsbox users have accounts in our DEV account
- terminate *all* non-prod AWSBoxes. 
- remove all identity accounts on PROD IAM
- figure out a good Reaper algorithm
- hack together the new reaper 
- rejoice at the savings (ref: http://bit.ly/12r10li)

Reaper Algorithm, (off the top of my head): 

- has received less than X bytes/day, stop it. Runs once / day
- has been stopped for 15 days, terminate it. 

It would be nice if AWSBox has a facility to start up the awsbox again. 

----- Original Message -----
From: "Lloyd Hilaiel" <[email protected]>
To: [email protected]
Cc: [email protected]
Sent: Wednesday, September 25, 2013 2:06:05 AM
Subject: Managing our AWS instances

In an effort to better manage our aws instances, I propose we add an "email" 
tag to all instances we create.  Here's changes we could make to awsbox to 
support this:

1. default behavior of create is to look for AWS_EMAIL in env and fail if it's 
not there
2. upon creation, instance will be tagged with 'email' - 'your email'
3. add a 'claim' command so you can attach your email to existing instances
4. add an 'unclaimed' command so you can see all instances that are unclaimed

Based on this little feature I hope we can implement simple automated ways of 
reaping unused instances (like, via email nagging).  Also, an unclaimed 
instance running for a long time without termination protection, is a good 
candidate for something that should be reaped.

Here's the awsbox pull request that would implement it: 
https://github.com/mozilla/awsbox/pull/109

How do folks feel about this convention?  Mark / mostly - you guys think this 
is a good first step to getting our AWS usage under control?

lloyd

_______________________________________________
identity-staff mailing list
[email protected]
https://mail.mozilla.org/listinfo/identity-staff
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev

Reply via email to