Open Stack

The goal isn't for ec2 api to be a "second class citizen", but to keep it
from being a limiting factor since we don't have control over it. How does
the compatibility layer make it second class?

On Thu, Jul 7, 2011 at 10:53 AM, Soren Hansen <soren at linux2go.dk> wrote:

> 2011/7/7 Vishvananda Ishaya <vishvananda at gmail.com>:
> > I think we should move toward ec2 being a compatibility layer that is
> translated into the os api.  This compatibility layer would sit at the top
> level zone and could maintain its own database for conversion of ids,
> management of secret and access keys, etc.
>
> With all due respect, I think this is a terrible idea. From a
> technical perspective, a backend that is flexible enough to support
> both the EC2 and the OpenStack (and OCCI and vCloud and whatever else)
> APIs without translation layers is a good thing and helps keep the
> separation clean.
>
> From an adoption perspective, like it or not, EC2 is popular. Lots of
> people use it and are comfortable and familiar with its API. I don't
> see what we'll win by so thoroughly reducing the EC2 API to a second
> class citizen in Nova.
>
> --
> Soren Hansen        | http://linux2go.dk/
> Ubuntu Developer    | http://www.ubuntu.com/
> OpenStack Developer | http://www.openstack.org/
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110707/f033f7b7/attachment.html>