Please see: http://etherpad.openstack.org/FolsomEC2Compatibility
Euca2ools is a a start, but there is more than meets the eye that is missing/lacking/incorrect in the EC2 layer. And there are many ways of solving it, but I think one of the key take-aways from that session is that we need a validation suite in order to figure out even where to begin (ie how can u fix something if u do not know how broken it is in the first place). On 4/19/12 10:58 AM, "Alisson Soares Limeira Pontes" <apon...@cpqd.com.br> wrote: I have the same doubt as you Philipp. By the way, some days ago I read "Citrix takes cloudstack to apache, abandons openstack" [http://www.pcworld.com/businesscenter/article/253084/citrix_takes_cloudstack_to_apache_abandons_openstack.html] They said that one of the reasons was that they believe supporting Amazon's API is crucial to the success of cloud platforms and "While OpenStack supports some Amazon APIs, it appears more interested in backing its own APIs." I could not understand, since I can use euca2ools without problem with openstack. +1 2012/4/17 Philipp Wollermann <wollermann_phil...@cyberagent.co.jp> Hi, I just saw the announcement of Canonical's AWSOME (https://launchpad.net/awsome), providing a translation proxy from the EC2 API to the OpenStack API. I'm definitely not an expert regarding OpenStack, but... doesn't OpenStack already support an EC2 compatibility API? At least, I can use the euca2ools without problems on OpenStack Nova Diablo. I haven't tried Swift yet. What's the advantage of replacing the native EC2 compatibility layer with AWSOME from a user / operator point of view? Thanks :) Philipp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
