<div dir="ltr">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.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 9, 2015 at 1:12 PM, Salvatore Orlando <span dir="ltr"><<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Jay is pretty much right.<div><br></div><div>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.</div><div>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).</div><div><br></div><div>I think a patch for blanking out those namespace is a great low hanging fruit for new contributors.</div><div>But on the other hand I'm pretty sure Kevin is wiping them out as a part of the Pecan refactor.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Salvatore</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 9 June 2015 at 20:33, Kevin Benton <span dir="ltr"><<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">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. </p><div><div>
<div class="gmail_quote">On Jun 9, 2015 12:04 PM, "Brandon Logan" <<a href="mailto:brandon.logan@rackspace.com" target="_blank">brandon.logan@rackspace.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I believe XML support got removed from the API last cycle.<br>
________________________________________<br>
From: Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>><br>
Sent: Tuesday, June 9, 2015 1:08 PM<br>
To: <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
Subject: Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs<br>
<br>
On 06/08/2015 05:10 PM, Sean M. Collins wrote:<br>
> Hi,<br>
><br>
> Within each API extension in the neutron tree, there is a method:<br>
><br>
>      def get_namespace(cls):<br>
><br>
> Which returns a string, containing a URL.<br>
<br>
<snip><br>
<br>
> I believe that they all 404.<br>
><br>
> A dumb question to start, then progressively smarter questions:<br>
><br>
> * What is the purpose of the URLs?<br>
<br>
They are the sad detritus left from XML support.<br>
<br>
> * Should the URL point to documentation?<br>
<br>
Perhaps.<br>
<br>
> * What shall we do about the actual URLs 404'ing?<br>
<br>
Honestly, I'd prefer the namespaces just be removed, but I'm not sure<br>
what Neutron's position is about XML and the REST API...<br>
<br>
Best,<br>
-jay<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div>Kevin Benton</div></div>
</div>