I'd also recommend documenting the version of the EC2 API supported by the project. That can then become a reference for a true standard, instead of the moving non-standard from AWS.
-George On Nov 8, 2011, at 3:38 PM, Chuck Short wrote: > Hi, > > At the last Openstack Design Summit we had a session about how we can > take care of the EC2 API more affectively. One of the outcomes of this > session was to create an EC2 API team, that will help take care of the > EC2 API in Nova. > > Today I would like to announce the formation of the Nova EC2 API team > on launchpad. The goal of this team is to take of the EC2 API, which > includes bugs on launchpad, making sure the EC2 API is compatible, and > testing the current EC2 API on Nova. > > I would also like to announce the first meeting, next Tuesday at 15:00 > UTC on #openstack-meeting. > > If you have any questions please let me know. > > Regards > chuck > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.com t: @GeorgeReese p: +1.207.956.0217 f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http://www.enstratus.com To schedule a meeting with me: http://tungle.me/GeorgeReese
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
