<p dir="ltr">From my point of view, I would suggest discussing it once during the NeutronClient session/OSC sessions on Thursday or once in the design meetup on Friday. I feel we can see at it once more.<br>
Currently I feel that the definition which is mentioned in the github is not completely clear.</p>
<p dir="ltr">For the projects which already use clientcommand extension, the implementation needs to be done in the project repo.<br>
For "CORE" Resources, the implementation needs to be done in python-osc.<br>
However, for the new resources/projects, the implementation needs to be clear because IMHO there is currently no clear definition as to which resources should implement clientcommandextension( which means implement the client code in the own repo) vs which resources can be added as simple extensions to NeutronClient(I.e. which can reside in the NeutronClient repo). However this is IMO, and if you have any guidelines which tells a developer if a project needs to be a clientcommand extension for NeutronClient ( or not) , please share the same.<br>
</p>
<div class="gmail_quote">On Apr 26, 2016 21:10, "Vikram Choudhary" <<a href="mailto:vikschw@gmail.com">vikschw@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 for keeping neutron-dynamic-routing CLI's in neutronclient repo like other *aaS services.<div><br></div><div>Thanks</div><font color="#888888"><div>Vikram</div></font></div><div class="elided-text"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 26, 2016 at 7:47 PM, Richard Theis <span dir="ltr"><<a href="mailto:rtheis@us.ibm.com" target="_blank">rtheis@us.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">Hi,</font>
<br>
<br><font size="2" face="sans-serif">The latest devref [1] would place it
in python-neutronclient as Henry noted. But stay tuned for results from
the summit session.</font>
<br>
<br><font size="2" face="sans-serif">[1] </font><a href="https://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst" target="_blank"><font size="2" color="blue" face="sans-serif">https://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst</font></a>
<br>
<br><font size="2" face="sans-serif">- Richard<br>
</font>
<br>
<br><tt><font size="2">"Na Zhu" <<a href="mailto:nazhu@cn.ibm.com" target="_blank">nazhu@cn.ibm.com</a>> wrote
on 04/26/2016 08:29:21 AM:<br>
<br>
> From: "Na Zhu" <<a href="mailto:nazhu@cn.ibm.com" target="_blank">nazhu@cn.ibm.com</a>></font></tt>
<br><tt><font size="2">> To: <a href="mailto:HenryG@gessau.net" target="_blank">HenryG@gessau.net</a></font></tt>
<br><tt><font size="2">> Cc: "OpenStack Development Mailing List
\(not for usage questions\)"<br>
> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font></tt>
<br><tt><font size="2">> Date: 04/26/2016 08:34 AM</font></tt>
<br><span><tt><font size="2">> Subject: Re: [openstack-dev] [neutron] OSC transition</font></tt>
<br></span><tt><font size="2">> <br><span>
> Hi Henry,<br>
> <br>
> Thanks your information, why you think neutron-dynamic-routing CLI
<br>
> should live in python-neutronclient?<br>
> From this link </span></font></tt><a href="http://docs.openstack.org/developer/python-" target="_blank"><tt><font size="2">http://docs.openstack.org/developer/python-</font></tt></a><tt><font size="2"><span><br>
> neutronclient/devref/transition_to_osc.htmlsection "Where does
my CLI belong?<br>
> ", *aas CLI belongs to their own project, not project python-<br>
> neutronclient. BGP is also service like *aas, so I think BGP CLIs
<br>
> should live in neutron-dynamic-routing, or a separate repo named <br>
> python-*client. Pls correct me if I am wrong, thanks.<br>
> <br>
> <br>
> <br>
> Regards,<br>
> Juno Zhu<br>
> IBM China Development Labs (CDL) Cloud IaaS Lab<br>
> Email: <a href="mailto:nazhu@cn.ibm.com" target="_blank">nazhu@cn.ibm.com</a><br>
> 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong
<br>
> New District, Shanghai, China (201203)<br>
> <br>
> <br>
> <br>
> From: Henry Gessau <<a href="mailto:HenryG@gessau.net" target="_blank">HenryG@gessau.net</a>><br>
> To: "OpenStack Development Mailing
List (not for usage <br>
> questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
> Date: 2016/04/26 21:09<br>
> Subject: Re: [openstack-dev] [neutron]
OSC transition<br>
> <br>
> <br>
> <br></span><div><div>
> Adding the [neutron] tag.<br>
> <br>
> I believe that the OSC extension for neutron-dynamic-routing should
live in<br>
> the python-neutronclient repo. Keep in touch with Richard Theis as
he is the<br>
> one leading the transition to OSC. He is rtheis on IRC.<br>
> <br>
> See:<br>
> </div></div></font></tt><a href="http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html" target="_blank"><tt><font size="2">http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html</font></tt></a><div><div><tt><font size="2"><br>
> </font></tt><a href="https://review.openstack.org/309587" target="_blank"><tt><font size="2">https://review.openstack.org/309587</font></tt></a><tt><font size="2"><br>
> <br>
> <br>
> Na Zhu <<a href="mailto:nazhu@cn.ibm.com" target="_blank">nazhu@cn.ibm.com</a>> wrote:<br>
> > Dear All,<br>
> > <br>
> > <br>
> > I have a question about OSC transition, recently, the community
approves<br>
> > moving bgp out of neutron, as a service like other *aas. The
BGP <br>
> CLIs need be<br>
> > removed from neutronclient. Because of OSC transition, I can
not <br>
> just move the<br>
> > BGP CLIs code from python-neutronclient repo to neutron-dynamic-<br>
> routing repo.<br>
> > I have to refactor the code and do transition to OSC plugin system.<br>
> > <br>
> > From the<br>
> > link _<a href="http://docs.openstack.org/developer/python-openstackclient/" target="_blank">http://docs.openstack.org/developer/python-openstackclient/</a><br>
> plugins.html_, the<br>
> > client has a separate repo, take designate as example, the CLI
repo is<br>
> > python-designateclient, the project repo is designate. So for
BGP, should I<br>
> > create a repo for CLI, or leverage project repo neutron-dynamic-routing?<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > Regards,<br>
> > Juno Zhu<br>
> > IBM China Development Labs (CDL) Cloud IaaS Lab<br>
> > Email: <a href="mailto:nazhu@cn.ibm.com" target="_blank">nazhu@cn.ibm.com</a><br>
> > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong
New<br>
> > District, Shanghai, China (201203)<br>
> > <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>
> > </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size="2"><br>
> > <br>
> <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>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size="2"><br>
> <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>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size="2"><br>
</font></tt></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><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>