openstack team mailing list archive
Mailing list archive
Re: OpenStack Compute API 1.1
An API is for life, not just for Cactus.
I agree that stability is important. I don't see how we can claim to
deliver 'stability' when the plan is then immediately to destablize
everything with a very disruptive change soon after, including customer
facing API changes and massive internal re-architecting.
On Thu, Feb 17, 2011 at 4:18 PM, Jay Pipes <jaypipes@xxxxxxxxx> wrote:
> On Thu, Feb 17, 2011 at 6:57 PM, Justin Santa Barbara
> <justin@xxxxxxxxxxxx> wrote:
> > Pulling volumes & images out into separate services (and moving from AMQP
> > REST) sounds like a huge breaking change, so if that is indeed the plan,
> > let's do that asap (i.e. Cactus).
> Sorry, I have to disagree with you here, Justin :) The Cactus release
> is supposed to be about stability and the only features going into
> Cactus should be to achieve API parity of the OpenStack Compute API
> with the Rackspace Cloud Servers API. Doing such a huge change like
> moving communication from AMQP to HTTP for volume and network would be
> a change that would likely undermine the stability of the Cactus
> release severely.