<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:10pt;color:#000000;background-color:#FFFFFF;font-family:'Courier New',monospace;">
<p>++ I think it'd be great to get that nailed down because, like you've mentioned, its likely we'll see a bit more of this as we widen our scope.<br>
</p>
<p><br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px"><font size="2" face="Consolas, monospace"><span style="font-size:10pt"><br>
</span></font></div>
<div style="font-size:13px"><font size="2" face="Consolas, monospace"><span style="font-size:10pt">--<br>
<br>
Kevin Carter<br>
IRC: cloudnull</span></font></div>
<div style="font-family:Tahoma; font-size:13px"><font face="Courier New" size="2"><span style="font-size:10pt"><br>
</span></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Javeria Khan <javeriak@plumgrid.com><br>
<b>Sent:</b> Friday, February 26, 2016 4:34 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [openstack-ansible] Installing networking-* pythonclient extensions to multiple locations</font>
<div> </div>
</div>
<div>
<div dir="ltr">That makes sense Kevin. I don't have a use case in mind that would require access to the additional clients, so we can address that if/when it ever comes up. For now the utility container getting the extensions installed should suffice. As OSA
is integrating with more types of plugins moving forward, it would help to get some kind of structure in place that references neutron parameters for such use cases.</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">--</div>
<div style="font-size:12.8000001907349px">Javeria</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Thu, Feb 25, 2016 at 4:08 AM, Kevin Carter <span dir="ltr">
<<a href="mailto:kevin.carter@rackspace.com" target="_blank">kevin.carter@rackspace.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" style="font-size:10pt; color:#000000; background-color:#ffffff; font-family:'Courier New',monospace">
<p>Hi Javeria,<br>
</p>
<p><br>
</p>
<p>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[0][1]. 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? <br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>[0] - <a href="https://github.com/openstack/openstack-ansible/blob/master/playbooks/roles/os_neutron/defaults/main.yml#L349" target="_blank">https://github.com/openstack/openstack-ansible/blob/master/playbooks/roles/os_neutron/defaults/main.yml#L349</a><br>
</p>
<p>[1] - <a href="https://github.com/openstack/openstack-ansible/blob/master/playbooks/defaults/repo_packages/openstack_services.yml#L85-L87" target="_blank">https://github.com/openstack/openstack-ansible/blob/master/playbooks/defaults/repo_packages/openstack_services.yml#L85-L87</a><br>
</p>
<p><br>
</p>
<div>
<div name="divtagdefaultwrapper">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px"><font size="2" face="Consolas, monospace"><span style="font-size:10pt">--<br>
<br>
Kevin Carter<br>
IRC: cloudnull</span></font></div>
<div style="font-family:Tahoma; font-size:13px"><font face="Courier New" size="2"><span style="font-size:10pt"><br>
</span></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
<div style="color:rgb(33,33,33)">
<hr style="display:inline-block; width:98%">
<div dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Javeria Khan <<a href="mailto:javeriak@plumgrid.com" target="_blank">javeriak@plumgrid.com</a>><br>
<b>Sent:</b> Sunday, February 21, 2016 5:09 AM<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
<b>Subject:</b> [openstack-dev] [openstack-ansible] Installing networking-* pythonclient extensions to multiple locations</font>
<div> </div>
</div>
<div>
<div class="h5">
<div>
<div dir="ltr">Hey everyone,
<div><br>
</div>
<div><span style="font-size:12.8px">At the moment OSA installs the python-neutronclient in a few locations including the containers neutron-server, utility, heat, tempest.</span></div>
<div><span style="font-size:12.8px"> </span></div>
<div><span style="font-size:12.8px">Now neutron has a bunch of sub-projects like networking-l2gw [1], networking-bgpvpn [2] networking-plumgrid [5] etc, which have their own python-neutronclient CLI extensions [3][4][5] in their respective repositories and
packages. </span><br clear="all">
<div>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div style="font-size:12.8px"><br>
</div>
<div><span style="font-size:12.8px">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</span><span style="font-size:12.8px"> </span><span style="font-size:12.8px">inside the OSA plays?</span><span style="font-size:12.8px"> 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? </span></div>
<div style="font-size:12.8px"><span style="font-size:12.8px"><br>
</span></div>
<div style="font-size:12.8px"><span style="font-size:12.8px">[1] </span><a href="https://github.com/openstack/networking-l2gw" target="_blank" style="font-size:12.8px">https://github.com/openstack/networking-l2gw</a>
<div style="font-size:12.8px">[2] <a href="https://github.com/openstack/networking-bgpvpn" target="_blank">https://github.com/openstack/networking-bgpvpn</a></div>
<div style="font-size:12.8px">[3] <a href="https://github.com/openstack/networking-l2gw/tree/master/networking_l2gw/l2gatewayclient" target="_blank">https://github.com/openstack/networking-l2gw/tree/master/networking_l2gw/l2gatewayclient</a></div>
<div style="font-size:12.8px">[4] <a href="https://github.com/openstack/networking-bgpvpn/tree/master/networking_bgpvpn/neutronclient" target="_blank">https://github.com/openstack/networking-bgpvpn/tree/master/networking_bgpvpn/neutronclient</a></div>
<div style="font-size:12.8px">[5] <a href="https://github.com/openstack/networking-plumgrid" target="_blank">https://github.com/openstack/networking-plumgrid</a> </div>
</div>
<div style="font-size:12.8px"><span style="font-size:12.8px"><br>
</span></div>
<div style="font-size:12.8px"><span style="font-size:12.8px"><br>
</span></div>
<div style="font-size:12.8px">Thanks,</div>
<div style="font-size:12.8px">Javeria</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>