Open Stack

On Thu, Dec 3, 2015 at 10:33 AM, Ihar Hrachyshka <ihrachys at redhat.com>
wrote:

> Akihiro Motoki <amotoki at gmail.com> wrote:
>
> Hi,
>>
>> python-neutronclient still has XML support of Neutron API.
>> I would like to discuss when we drop XML support in neutronclient.
>>
>> Neutron API XML suppoort was marked as deprecated in Icehouse and Juno
>> and was dropped in Kilo. Juno is now EOL and we have no gate testing which
>> requires XML support. This is a minimum requirement.
>> From this point, we can drop XML support now.
>>
>> Another point is users who are OpenStack clouds using Juno or older
>> versions
>> may use the latest python-neutronclient.
>> XML support in Neutron was deprecated since Icehouse, and if our
>> deprecation
>> notice works, XML API is used only in cloud deployed before Icehouse.
>> In addition, older versions of neutronclient are available from
>> various distributions and PyPI.
>> Do we need to continue XML support for users of such cloud?
>> Note that we no longer have a way to test XML API support is functional.
>>
>> Thanks,
>> Akihiro
>>
>
> Let’s not pretend anything ungated works in OpenStack world. If we don’t
> have infra to validate it, we should kill the support for it.


I'd take that one step further and argue that if it's not tested in a gate,
then by definition it is not supported :)

And +1 for generally removing unnecessary XML support everywhere.


>
>
> Ihar
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20151203/eb641668/attachment.html>