[openstack-dev] [Neutron] API Extensions - Namespace URLs
Kevin Benton
blak111 at gmail.com
Tue Jun 9 21:21:18 UTC 2015
I wasn't planning on wiping them out for now since I'm leveraging a lot of
the extension loading that exists so someone can remove the namespaces if
they want.
On Tue, Jun 9, 2015 at 1:12 PM, Salvatore Orlando <sorlando at nicira.com>
wrote:
> Jay is pretty much right.
>
> In Neutron's case it is even more trivial. Somebody copied the extension
> manager from Nova, and a sort of extension interface with this namespace.
> And every neutron developer, including me felt compelled to filling that
> up with something that resembled an XML namespace URI (which often resolve
> to nowhere anyway).
>
> I think a patch for blanking out those namespace is a great low hanging
> fruit for new contributors.
> But on the other hand I'm pretty sure Kevin is wiping them out as a part
> of the Pecan refactor.
>
> Salvatore
>
> On 9 June 2015 at 20:33, Kevin Benton <blak111 at gmail.com> wrote:
>
>> I heard rumors that Oracle was going to introduce XML-as-a-service to
>> OpenStack to make it enterprise-grade. If that's the case, we'll be ahead
>> of everyone with our namespaces.
>> On Jun 9, 2015 12:04 PM, "Brandon Logan" <brandon.logan at rackspace.com>
>> wrote:
>>
>>> I believe XML support got removed from the API last cycle.
>>> ________________________________________
>>> From: Jay Pipes <jaypipes at gmail.com>
>>> Sent: Tuesday, June 9, 2015 1:08 PM
>>> To: openstack-dev at lists.openstack.org
>>> Subject: Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
>>>
>>> On 06/08/2015 05:10 PM, Sean M. Collins wrote:
>>> > Hi,
>>> >
>>> > Within each API extension in the neutron tree, there is a method:
>>> >
>>> > def get_namespace(cls):
>>> >
>>> > Which returns a string, containing a URL.
>>>
>>> <snip>
>>>
>>> > I believe that they all 404.
>>> >
>>> > A dumb question to start, then progressively smarter questions:
>>> >
>>> > * What is the purpose of the URLs?
>>>
>>> They are the sad detritus left from XML support.
>>>
>>> > * Should the URL point to documentation?
>>>
>>> Perhaps.
>>>
>>> > * What shall we do about the actual URLs 404'ing?
>>>
>>> Honestly, I'd prefer the namespaces just be removed, but I'm not sure
>>> what Neutron's position is about XML and the REST API...
>>>
>>> Best,
>>> -jay
>>>
>>>
>>> __________________________________________________________________________
>>> 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
>>>
>>>
>>> __________________________________________________________________________
>>> 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
>>>
>>
>> __________________________________________________________________________
>> 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
>>
>>
>
> __________________________________________________________________________
> 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
>
>
--
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150609/52f5e4af/attachment.html>
More information about the OpenStack-dev
mailing list