Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
On Tue, Jun 09, 2015 at 05:21:18PM EDT, Kevin Benton wrote: 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. OK - I'll take it on if there's no objections -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
Thanks for asking about this Sean! ;) Sean M. Collins wrote: On Tue, Jun 09, 2015 at 05:21:18PM EDT, Kevin Benton wrote: 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. OK - I'll take it on if there's no objections __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
I believe XML support got removed from the API last cycle. From: Jay Pipes jaypi...@gmail.com Sent: Tuesday, June 9, 2015 1:08 PM To: openstack-dev@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
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 sorla...@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 blak...@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.lo...@rackspace.com wrote: I believe XML support got removed from the API last cycle. From: Jay Pipes jaypi...@gmail.com Sent: Tuesday, June 9, 2015 1:08 PM To: openstack-dev@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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
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 blak...@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.lo...@rackspace.com wrote: I believe XML support got removed from the API last cycle. From: Jay Pipes jaypi...@gmail.com Sent: Tuesday, June 9, 2015 1:08 PM To: openstack-dev@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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs
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.lo...@rackspace.com wrote: I believe XML support got removed from the API last cycle. From: Jay Pipes jaypi...@gmail.com Sent: Tuesday, June 9, 2015 1:08 PM To: openstack-dev@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] API Extensions - Namespace URLs
Hi,
Within each API extension in the neutron tree, there is a method:
def get_namespace(cls):
Which returns a string, containing a URL.
A quick survey:
agent.py:def get_namespace(cls):
agent.py-return http://docs.openstack.org/ext/agent/api/v2.0;
--
allowedaddresspairs.py:def get_namespace(cls):
allowedaddresspairs.py-return
http://docs.openstack.org/ext/allowedaddresspairs/api/v2.0;
--
dhcpagentscheduler.py:def get_namespace(cls):
dhcpagentscheduler.py-return
http://docs.openstack.org/ext/dhcp_agent_scheduler/api/v1.0;
--
dvr.py:def get_namespace(cls):
dvr.py-return (http://docs.openstack.org/ext/;
--
external_net.py:def get_namespace(cls):
external_net.py-return
http://docs.openstack.org/ext/neutron/external_net/api/v1.0;
--
external_net.py:return {l3.L3.get_alias(): l3.L3.get_namespace()}
--
extra_dhcp_opt.py:def get_namespace(cls):
extra_dhcp_opt.py-return
http://docs.openstack.org/ext/neutron/extra_dhcp_opt/api/v1.0;
--
extraroute.py:def get_namespace(cls):
extraroute.py-return
http://docs.openstack.org/ext/neutron/extraroutes/api/v1.0;
--
flavor.py:def get_namespace(cls):
flavor.py-return http://docs.openstack.org/ext/flavor/api/v1.0;
--
l3.py:def get_namespace(cls):
l3.py-return http://docs.openstack.org/ext/neutron/router/api/v1.0;
--
l3_ext_gw_mode.py:def get_namespace(cls):
l3_ext_gw_mode.py-return
http://docs.openstack.org/ext/neutron/ext-gw-mode/api/v1.0;
--
l3_ext_ha_mode.py:def get_namespace(cls):
l3_ext_ha_mode.py-return
--
l3agentscheduler.py:def get_namespace(cls):
l3agentscheduler.py-return
http://docs.openstack.org/ext/l3_agent_scheduler/api/v1.0;
--
metering.py:def get_namespace(cls):
metering.py-return
http://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth#API;
--
multiprovidernet.py:def get_namespace(cls):
multiprovidernet.py-return
http://docs.openstack.org/ext/multi-provider/api/v1.0;
--
netmtu.py:def get_namespace(cls):
netmtu.py-return http://docs.openstack.org/ext/net_mtu/api/v1.0;
--
portbindings.py:def get_namespace(cls):
portbindings.py-return http://docs.openstack.org/ext/binding/api/v1.0;
--
portsecurity.py:def get_namespace(cls):
portsecurity.py-return
http://docs.openstack.org/ext/portsecurity/api/v1.0;
--
providernet.py:def get_namespace(cls):
providernet.py-return http://docs.openstack.org/ext/provider/api/v1.0;
--
quotasv2.py:def get_namespace(cls):
quotasv2.py-return
http://docs.openstack.org/network/ext/quotas-sets/api/v2.0;
--
routerservicetype.py:def get_namespace(cls):
routerservicetype.py-return
--
securitygroup.py:def get_namespace(cls):
securitygroup.py-# todo
--
servicetype.py:def get_namespace(cls):
servicetype.py-return
http://docs.openstack.org/ext/neutron/service-type/api/v1.0;
--
subnetallocation.py:def get_namespace(cls):
subnetallocation.py-return (http://docs.openstack.org/ext/;
--
vlantransparent.py:def get_namespace(cls):
vlantransparent.py-return
http://docs.openstack.org/ext/vlantransparent/api/v1.0;
I believe that they all 404.
A dumb question to start, then progressively smarter questions:
* What is the purpose of the URLs?
* Should the URL point to documentation?
* What shall we do about the actual URLs 404'ing?
Thanks!
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
