> -----Original Message----- > From: openstack-bounces+ewan.mellor=citrix....@lists.launchpad.net > [mailto:openstack-bounces+ewan.mellor=citrix....@lists.launchpad.net] > On Behalf Of Ed Leafe > Sent: 11 July 2011 16:39 > To: openstack@lists.launchpad.net > Subject: Re: [Openstack] Cross-zone instance identifiers in EC2 API - > Is it worth the effort? > > On Jul 11, 2011, at 6:46 PM, Ed Leafe wrote: > > >> If so, then I would say that your proposed limitation above is not > acceptable. We don't want a situation where tenants have to stop using > the EC2 API as soon as their service provider wants to offer a rich set > of offerings. > > > > That was my working premise, too, but the decision was made > within Rackspace to not spend time on EC2 support for zones since we > use the OS API exclusively, so my hands were tied. > > > Wait, that didn't sound right. What I should have said is that > the decision was made within *my team* at Rackspace, not by Rackspace > as a whole. Our team's job is to make sure that everything is > implemented in nova that we will need to switch our code base, and > since the EC2 API isn't one of those things, it was decided not to > spend any time on it. That doesn't mean that we wouldn't love someone > for whom EC2 compatibility matters to add it in; it just means that it > isn't going to be us. ;-)
Well, as long as it's not precluded by design choices that you're making, then someone else can pick up the work and finish the job. No-one expects Rackspace to do _everything_ -- that's what the other (*checks ever increasing counters on openstack.org*) 82 companies and 1150 people are here for! Ewan. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
