Open Stack

Sean, David,

Thanks for your reply and useful links.
Neutron LBaaS API had experimental status, so i think the guidelines might
be relaxed for this case, but now I just tend to workaround this and
preserve API compatibility.

Thanks,
Eugene.




On Wed, Nov 20, 2013 at 9:57 PM, David Kranz <dkranz at redhat.com> wrote:

> On 11/19/2013 09:40 PM, Sean Dague wrote:
>
>> On 11/17/2013 09:55 PM, Eugene Nikanorov wrote:
>>
>>> Hi folks,
>>>
>>> I'm working on major change to Neutron LBaaS API, obviously it will
>>> break existing tempest API tests for LBaaS.
>>> What would be the right process to deal with this? I guess I can't just
>>> push fixed tests to tempest because they will not pass against existing
>>> neutron code, and vice versa.
>>>
>>
>> The answer is, you don't. If it's a published API than it has to be
>> versioned. Changing an existing API in a non compatible way is not allowed.
>>
> Indeed. See these for more details:
>
> https://wiki.openstack.org/wiki/Governance/Approved/APIStability
> https://wiki.openstack.org/wiki/APIChangeGuidelines
>
>  -David
>
>
>
>
>> So please explain the deprecation and versioning plan for LBaaS, then we
>> can probably figure out the right path forward.
>>
>>     -Sean
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131121/4ab23f41/attachment.html>