3 ms·

Thanks for the screenshot. Interesting. I am not getting the point of it. I mean, its kind of a "api translation" right? Instead of using boto, you will be usi

by amitu 13y ago

Thanks for the screenshot. Interesting. I am not getting the point of it. I mean, its kind of a "api translation" right? Instead of using boto, you will be using django's db-api to create/manage things. This in itself is quite compelling, who wants to learn boto? I am wondering if this was the reason you built it, or you had some other use case? Also, this is a little bit less "accurate" than boto right? If for example I have to query the number of instance running using my account, a direct query using boto will give me accurate result, but a query on django can be out of sync due to any number of reasons. Is there anything to summarily say if my data is in sync with EC2? Good work btw, I think you should def open source it. :-)

micah_chatt 13y ago
Your points are valid, its not a total replacement to the console, and is a wrapper around Boto. There are several reasons that we use this: * 'Template' out our infrastructure. If us-east-1 is ever down, we can easily re-create and spin up in us-west or wherever we'd like. * If us-east-1 ever goes offline (a-la hurricane sandy), we have a record of what size/how many resources we had in production. Especially helpful since our infrastructure is dynamic. We add autoscale groups as we gain customers. * We can easily foriegn key models in other apps in our project to an Autoscale group/ELB's etc. Ex: a customer is assigned to a particular autoscale group or load balancer. * The loss in accuracy is acceptable, as we don't use every feature of AWS, so we only (at this point) have built out the necessary features.