Hiya All,

I figure we should get the ball rolling on what we would all like to
see in 0.6 for Libcloud (maybe it could be called 1.0 too, but its
probably best to have that discussion separately)

My thoughts so far:

- DNS API:  Amazon, Linode, Zerigo, Slicehost, etc all have DNS
management APIs.  Combining the management of Load Balancer with DNS
seems like the next logical step.

- Monitoring API: Amazon Cloudwatch and Cloudkick both provide APIs
for monitoring instances;  I'm not sure we can actually get a good
abstraction here yet, maybe it is too early. (And full disclaimer, I
work at Cloudkick)

- Revamp of Locations & Regions:  I believe for the compute API its
obvious the mix of having a Driver for different region, or sometimes
the list_locations API is less than ideal.  I think a related issue is
the pain it is to point a driver at a custom endpoint URL, which will
become more common as things like OpenStack Nova instances get stood
up by more companies.

- Improve non-python access to Libcloud:  Maybe this means we could
adopt the provide a REST api that DeltaCloud supports, or maybe just
bundling something like lctools <http://novel.github.com/lc-tools/> ?

Thoughts? Other features?

Thanks,

Paul

Reply via email to