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. ;-)
-- Ed Leafe
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
