+1 I think the work really lives with formalizing the contracts at the nova.[service].api level and pushing the discrepancies into the respective public API's.
-S ________________________________________ From: openstack-bounces+sandy.walsh=rackspace....@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace....@lists.launchpad.net] on behalf of Tim Bell [tim.b...@cern.ch] Sent: Monday, July 11, 2011 2:38 PM To: Soren Hansen; Eric Day Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort? At the risk of making things more complicated, we should anticipate an eventual Cloud API standard which could be any solution from EC2/OpenStack/OCCI/... and a set of legacy interfaces for backwards compatibility. This, as far as I see, pushes us strongly towards the multiple APIs as a presentation layer and a backend which is relatively flexible (as we also can adapt the presentation layers to convert if required without impacting the clients). Some interfaces, such as the OpenStack one could be relatively light and the additional business logic of mapping/transforming added to the other interfaces as required. Tim Bell CERN _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp This email may include confidential information. If you received it in error, please delete it. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
