openstack team mailing list archive

[Justin Santa Barbara <justin@xxxxxxxxxxxx>]

In my experience, the API is the most visible yet smallest problem of
working with different clouds.

For example, EC2 and Rackspace Cloud have completely different
approaches to volumes, such that the way you backup your VMs has to be
completely different (disk snapshot vs application level).  Rackspace
Cloud had limited images compared to EC2, so you often couldn't rely
on image-based deployment or the right OS/kernel modules being
available.  Those are the problems that really bite you when trying to
support multiple clouds.

I believe what OpenStack is building is the true cross-cloud API: a
common API with common concepts and functionality.  If you choose the
OpenStack API, I believe there are a half dozen public clouds today
you can use; there are at least as many companies that will help you
build a private cloud.  All with the same API, all with the same basic
behaviour.  By year-end, I suspect the weight of numbers will be
overwhelming.

If you want to add OpenStack support to deltacloud, by all means do
so, but these cross-cloud abstractions are a long-term dead-end, in my
opinion.

Justin


On Tue, Feb 21, 2012 at 8:04 AM, Frans Thamura <frans@xxxxxxxxxxxx> wrote:
>
> anyone know deltacloud
>
> i think this is intersting
>
> esp after OpenStack want to make their own standard vs Amazon API :)
>
> i think the foundation need to be hurry and work closely with Apache ;0
>
> http://www.sdtimes.com/APACHE_ADOPTS_NEW_TOP_LEVEL_CLOUD_PROJECT/By_Alex_Handy/About_APACHE_and_CLOUD_and_DELTACLOUD/36373
>
> F
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp