openstack team mailing list archive

[Joshua Harlow <harlowja@xxxxxxxxxxxxx>]

Ya, we should figure out how to organize to make this happen.

It seems to provide many benefits (not just for openstack).

Maybe setup a little working group around this...

On 4/23/12 12:01 PM, "Doug Hellmann" <doug.hellmann@xxxxxxxxxxxxx> wrote:

Martin Packman mentioned that there are some other groups interested in creating a separate AWS validation test suite, and that AWSOME would probably be using that. I think Joshua Harlow from Yahoo! was working in that area, too.

On Mon, Apr 23, 2012 at 1:38 PM, Joshua Harlow <harlowja@xxxxxxxxxxxxx> wrote:
We just have to be careful here to make sure that lots and lots of tests are done to ensure that the EC2 response is valid as well as to ensure the performance is not de-graded by having this proxy layer. If it does get de-graded then there needs to be some work done to ensure that this does not happen (ie new features in the openstack-api). Hopefully this proxy layer can also remain stateless, for as long as possible (for everyone's sanity).


On 4/23/12 7:57 AM, "Nick Barcet" <nick.barcet@xxxxxxxxxxxxx <http://nick.barcet@xxxxxxxxxxxxx> > wrote:

On 04/23/2012 02:39 PM, Thierry Carrez wrote:
> Philipp Wollermann wrote:
>> What's the advantage of replacing the native EC2 compatibility layer with AWSOME from a user / operator point of view?
>
> One thing that was mentioned is that the proxy could be run on top of a
> public cloud that chose to only deploy OpenStack API support.

Another reason why we started this project is that we believe this
architecture would be easier to use and maintain than what currently
exists in Nova. This is why we are proposing this work as a longer term
solution for EC2 compatibility.

Nick



_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp