Open Stack

On 03/26/2015 01:01 PM, Rob Hirschfeld wrote:
> On 03/26/2015 08:17 AM, Chris Hoge wrote:
>> This also overlaps a bit with versioned apis. Right now in Keystone
>> we’re in the transition
>> from v2 to v3, and being able to have a decision on the required
>> version or allowing
>> an ‘or’ on the versions will need to be addressed.
> I'm less enthusiastic about having two versions of the same thing in the
> spec.  From an OpenStack user, I consider that Nova and Nova-Net are
> different components (some may disagree, of course).

I agree with Rob.

>From a user perspective, I vehemently do not care about what version of
a thing the vendor has happened to deploy, and if the vendor's choice
there presents as a difference that I have to know about as a user, it's
a terrible experience.

They keystone v2 to v3 is an excellent example. Neither of the public
clouds actually expose the v3 api yet, so requiring keystone v3
capabilities would be a bit premature. However, it turns out the v2
capabilities are covered in the v3 api - so I'd argue that the subset
that is covered by both is fair game, and once we decide that we want to
require capabilities covered by the v3 api, it needs to be an absolute
"these are now required".

Anything else is soul-shreddingly painful and a disservice to our users.
(if you write a single piece of code that does basic operations against
both HP and Rackspace right now you have a ton of "if v1: elif v2:" in
it and the bodies of those are TOTALLY different.)