[openstack-dev] [openstack-ansible] Installing networking-* pythonclient extensions to multiple locations
kevin.carter at RACKSPACE.COM
Wed Feb 24 23:08:37 UTC 2016
We could call out our supported sub-projects in the `openstack_services.yml` file and install them as part of the plugin backend similar to what we've done with the "neutron_lbaas" package. However, this would not specifically fix the neutron clients in all places as you've mentioned. While I can make a case for the utility container to get the extra neutron-client-extensions, I'm not sure we need them everywhere. Do we suspect a user or service may need access to the additional client extensions from the Heat or Nova venvs or anywhere else for that matter?
 - https://github.com/openstack/openstack-ansible/blob/master/playbooks/roles/os_neutron/defaults/main.yml#L349
 - https://github.com/openstack/openstack-ansible/blob/master/playbooks/defaults/repo_packages/openstack_services.yml#L85-L87
From: Javeria Khan <javeriak at plumgrid.com>
Sent: Sunday, February 21, 2016 5:09 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [openstack-ansible] Installing networking-* pythonclient extensions to multiple locations
At the moment OSA installs the python-neutronclient in a few locations including the containers neutron-server, utility, heat, tempest.
Now neutron has a bunch of sub-projects like networking-l2gw , networking-bgpvpn  networking-plumgrid  etc, which have their own python-neutronclient CLI extensions  in their respective repositories and packages.
Since these CLI extensions are not part of the neutron packages and must be enabled by installing the additional networking-* packages. We don't install most of these sub-projects in OSA at the moment, however moving forward do you think its reasonable to install said packages in every location that installs the neutron client inside the OSA plays? If so, then how would you recommend we go about it since the installation will be conditional on the enabling of the relevant neutron subproject features?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev