[openstack-dev] Ugly Hack to deal with multiple versions

We have to support old clients. Old clients expect that the URL that comes back for the service catalog has the version in it. Old clients don't do version negotiation. Thus, we need an approach to not-break old clients while we politely encourage the rest of the world to move to later APIs.

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On Mon, Feb 3, 2014 at 1:50 PM, Adam Young wrote: > > HACK: In a new client, look at the URL. If it ends with /v2.0, chop it > off and us the substring up to that point. > > Now, at this point you are probably going: That is ugly, is it really > necessary? Can't we do something more correct? >

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On Tue, Feb 4, 2014 at 6:20 AM, Adam Young wrote: > We have to support old clients. > Old clients expect that the URL that comes back for the service catalog > has the version in it. > Old clients don't do version negotiation. > > Thus, we need an approach to not-break old clients while we polite

Re: [openstack-dev] Ugly Hack to deal with multiple versions

Can you be more specific about what goes wrong here? I'm not entirely sure I understand why an old client of arbitrary age needs to be supported with new OpenStack. The contract is the API, not the client, and an old client that doesn't do version discovery is just a buggy client from what I'm conc

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On Tue, Feb 4, 2014 at 9:00 AM, Sean Dague wrote: > Can you be more specific about what goes wrong here? I'm not entirely > sure I understand why an old client of arbitrary age needs to be > supported with new OpenStack. The contract is the API, not the client, > and an old client that doesn't do

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On 02/05/2014 01:09 AM, Dean Troyer wrote: > On Tue, Feb 4, 2014 at 9:00 AM, Sean Dague > wrote: > > Can you be more specific about what goes wrong here? I'm not entirely > sure I understand why an old client of arbitrary age needs to be > supported with new Ope

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On 02/04/2014 11:09 AM, Dean Troyer wrote: On Tue, Feb 4, 2014 at 9:00 AM, Sean Dague > wrote: Can you be more specific about what goes wrong here? I'm not entirely sure I understand why an old client of arbitrary age needs to be supported with new OpenStack. T

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On Feb 4, 2014, at 10:31 AM, Sean Dague wrote: > On 02/05/2014 01:09 AM, Dean Troyer wrote: >> On Tue, Feb 4, 2014 at 9:00 AM, Sean Dague > > wrote: >> >>Can you be more specific about what goes wrong here? I'm not entirely >>sure I understand why an old client of

Re: [openstack-dev] Ugly Hack to deal with multiple versions

- Original Message - > From: "Dean Troyer" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, February 4, 2014 9:31:57 AM > Subject: Re: [openstack-dev] Ugly Hack to deal with multiple versions > > On Mon,

Re: [openstack-dev] Ugly Hack to deal with multiple versions

- Original Message - > From: "Adam Young" > To: openstack-dev@lists.openstack.org > Sent: Wednesday, February 5, 2014 2:29:18 AM > Subject: Re: [openstack-dev] Ugly Hack to deal with multiple versions > On 02/04/2014 11:09 AM, Dean Troyer wrote: > > On Tu

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On 02/05/2014 01:50 AM, Jesse Noller wrote: > > On Feb 4, 2014, at 10:31 AM, Sean Dague wrote: > >> On 02/05/2014 01:09 AM, Dean Troyer wrote: >>> On Tue, Feb 4, 2014 at 9:00 AM, Sean Dague >> > wrote: >>> >>>Can you be more specific about what goes wrong here? I'm not

Re: [openstack-dev] Ugly Hack to deal with multiple versions

On Feb 4, 2014, at 1:28 PM, Sean Dague wrote: > On 02/05/2014 01:50 AM, Jesse Noller wrote: >> >> On Feb 4, 2014, at 10:31 AM, Sean Dague wrote: >> >>> On 02/05/2014 01:09 AM, Dean Troyer wrote: On Tue, Feb 4, 2014 at 9:00 AM, Sean Dague >>> > wrote: C

Re: [openstack-dev] Ugly Hack to deal with multiple versions

It would really be nice to be able to hit an endpoint like https://hostname:35357/ and get a list of available versions back. It would make discovery easier. But, for scripting languages like PHP this would add a lot of extra http requests unless you cache the location between page views/requests.

Re: [openstack-dev] Ugly Hack to deal with multiple versions

Excerpts from Jesse Noller's message of 2014-02-04 11:55:57 -0800: > > On Feb 4, 2014, at 1:28 PM, Sean Dague wrote: > > > On 02/05/2014 01:50 AM, Jesse Noller wrote: > >> > >> On Feb 4, 2014, at 10:31 AM, Sean Dague wrote: > >> > >>> On 02/05/2014 01:09 AM, Dean Troyer wrote: > On Tue,