Open Stack

On Tuesday, February 25, 2014 4:02:13 PM, Dan Smith wrote:
>> +1, seems would could explore for another cycle just to find out that
>> backporting everything to V2 isn't going to be what we want, and now
>> we've just wasted more time.
>
>> If we say it's just deprecated and frozen against new features, then
>> it's maintenance is just limited to bug fixes right?
>
> No, any time we make a change to how the api communicates with compute,
> conductor, or the scheduler, both copies of the API code have to be
> changed. If we never get rid of v2 (and I don't think we have a good
> reason to right now) then we're doing that *forever*. I do not want to
> sign up for that.

Yeah, so objects is the big one here.  And it doesn't sound like we're 
talking about getting rid of V2 *right now*, we're talking about 
deprecating it after V3 is released (plan would be Juno for 
nova-network and tasks) and then maintaining it for some amount of time 
before it could be removed, and it doesn't sound like we know what that 
number is until we get some input from deployers/operators.

>
> I'm really curious what deployers like RAX, HP Cloud, etc think about
> freezing V2 to features and having to deploying V3 to get them. Does RAX
> expose V3 right now? Also curious if RAX/HP/etc see the V3 value
> statement when compared to what it will mean for their users.

I'd also be interested to see what happens with the Keystone V2 API 
because as I understand it, it's deprecated already and there is no V3 
support in python-keystoneclient, that's all moved to 
python-openstackclient, which I don't think even Tempest is using yet, 
at least not for API tests.

So what kind of reaction are the Keystone people getting to that?  Do 
they plan on removing their V2 API at some point?  Or just maintain it 
with bug fixes forever?

>
> --Dan
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

--

Thanks,

Matt Riedemann