[openstack-dev] [tripleO][Neutron] Appropriate location for networking-* pythonclient extensions

Fawad Khaliq fawad at plumgrid.com
Sun Feb 14 19:26:13 UTC 2016


Hi Triple-O folks,

I am trying to understand how the notion of overcloud and undercloud would
play with the Neutron subprojects. Neutron has sub-projects like
networking-l2gw [1], networking-bgpvpn [2] etc, which have their own
python-neutronclient CLI extensions [3][4] in their respective repositories
and packages.

I assume it is recommended and it is a common usage that undercloud
python-neutronclient is also used to access the overcloud resources via
overload RC files/credentials. Now, since these CLI extensions are not part
of Neutron packages and in some cases only supposed to be part of the
overcloud, how would you recommend installation of the python-neutronclient
CLI extensions for these sub-projects?

I was thinking that a particular overcloud installation and it's respective
neutronclient extensions (from subprojects) be installed on the
"recommended" location, which in this case is the undercloud client node(s).

Please advise how can we proceed with this. The goal is to understand the
location for these overcloud CLI extensions so it is intuitive for the
users of the system and not have silent failures by introducing separate
clients for undercloud (base Neutron install) and overcloud(base Neutron
install + subprojects).

Tagged Neutron, as someone from the Neutron or sub-projects teams might
already have a solution to this.

[1] https://github.com/openstack/networking-l2gw
[2] https://github.com/openstack/networking-bgpvpn
[3]
https://github.com/openstack/networking-l2gw/tree/master/networking_l2gw/l2gatewayclient
[4]
https://github.com/openstack/networking-bgpvpn/tree/master/networking_bgpvpn/neutronclient

Thanks a lot,
Fawad Khaliq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160215/34b35e0c/attachment.html>


More information about the OpenStack-dev mailing list