<font size=2 face="sans-serif">Hi Richard,</font><br><br><font size=2 face="sans-serif">I read the contents in the link, I think
the discussion in Austin summit have not updated to the webpage.</font><br><font size=2 face="sans-serif">But from here </font><a href="https://etherpad.openstack.org/p/newton-neutron-future-neutron-client"><font size=2 color=blue face="sans-serif">https://etherpad.openstack.org/p/newton-neutron-future-neutron-client</font></a><font size=2 face="sans-serif">,
it mentions python-neutronclient provides OSC plugin for neutron-*aas,</font><br><font size=2 face="sans-serif">does it mean all neutron-*aas CLIs still
live in python-neutronclient repo? If yes, should every neutron-*aas owner
updates the CLIs from neutron to openstack?</font><br><font size=2 face="sans-serif"><br>I found Dean Troyer set the </font><font size=2 face="sans-serif"><b>[Blueprint
neutron-client] implement neutron commands</b></font><font size=2 face="sans-serif">state to obsolete, does the OSC transition continue move along?<br><br><br>Regards,<br>Juno Zhu<br>IBM China Development Labs (CDL) Cloud IaaS Lab<br>Email: nazhu@cn.ibm.com<br>5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District,
Shanghai, China (201203)</font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Richard Theis <rtheis@us.ibm.com></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Na Zhu <openstack-dev@lists.openstack.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">openstack-dev@lists.openstack.org</font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">2016/05/04 03:05</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
[neutron] OSC transition</font><br><hr noshade><br><br><br><font size=2 face="sans-serif">I've asked about the conclusion here
[1].</font><font size=3> <br></font><font size=2 face="sans-serif"><br>[1] </font><a href="http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html"><font size=2 color=blue face="sans-serif"><u>http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html</u></font></a><font size=3><br></font><tt><font size=2><br>Na Zhu/China/IBM wrote on 05/01/2016 09:11:43 PM:<br><br>> From: Na Zhu/China/IBM@IBMCN</font></tt><font size=3> </font><tt><font size=2><br>> To: rtheis@us.ibm.com</font></tt><font size=3> </font><tt><font size=2><br>> Cc: openstack-dev@lists.openstack.org</font></tt><font size=3> </font><tt><font size=2><br>> Date: 05/01/2016 09:11 PM</font></tt><font size=3> </font><tt><font size=2><br>> Subject: Re: [openstack-dev] [neutron] OSC transition</font></tt><font size=3></font><tt><font size=2><br>> <br>> Hi Richard, <br>> <br>> So what is the conclusion of where to put *aas CLI? <br>> <br>> <br>> <br>> Regards,<br>> Juno Zhu<br>> IBM China Development Labs (CDL) Cloud IaaS Lab<br>> Email: nazhu@cn.ibm.com<br>> 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong
<br>> New District, Shanghai, China (201203) <br>> <br>> <br>> <br>> From: Richard Theis <rtheis@us.ibm.com>
<br>> To: "OpenStack Development Mailing
List \(not for usage <br>> questions\)" <openstack-dev@lists.openstack.org> <br>> Date: 2016/04/26 22:32 <br>> Subject: Re: [openstack-dev] [neutron]
OSC transition <br>> <br>> <br>> <br>> Hi, <br>> <br>> The latest devref [1] would place it in python-neutronclient as <br>> Henry noted. But stay tuned for results from the summit session. <br>> <br>> [1] </font></tt><a href="https://github.com/openstack/python-neutronclient/blob/master/"><tt><font size=2 color=blue><u>https://github.com/openstack/python-neutronclient/blob/master/</u></font></tt></a><tt><font size=2><br>> doc/source/devref/transition_to_osc.rst <br>> <br>> - Richard<br>> <br>> <br>> "Na Zhu" <nazhu@cn.ibm.com> wrote on 04/26/2016 08:29:21
AM:<br>> <br>> > From: "Na Zhu" <nazhu@cn.ibm.com> <br>> > To: HenryG@gessau.net <br>> > Cc: "OpenStack Development Mailing List \(not for usage
questions\)"<br>> > <openstack-dev@lists.openstack.org> <br>> > Date: 04/26/2016 08:34 AM <br>> > Subject: Re: [openstack-dev] [neutron] OSC transition <br>> > <br>> > Hi Henry,<br>> > <br>> > Thanks your information, why you think neutron-dynamic-routing
CLI <br>> > should live in python-neutronclient?<br>> > From this link </font></tt><a href="http://docs.openstack.org/developer/python-"><tt><font size=2 color=blue><u>http://docs.openstack.org/developer/python-</u></font></tt></a><tt><font size=2><br>> > neutronclient/devref/transition_to_osc.htmlsection "Where
does my <br>> 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: nazhu@cn.ibm.com<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 <HenryG@gessau.net><br>> > To: "OpenStack Development Mailing
List (not for usage <br>> > questions)" <openstack-dev@lists.openstack.org><br>> > Date: 2016/04/26 21:09<br>> > Subject: Re: [openstack-dev] [neutron]
OSC transition<br>> > <br>> > <br>> > <br>> > 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
ashe is the<br>> > one leading the transition to OSC. He is rtheis on IRC.<br>> > <br>> > See:<br>> > </font></tt><a href="http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html"><tt><font size=2 color=blue><u>http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html</u></font></tt></a><tt><font size=2><br>> > </font></tt><a href=https://review.openstack.org/309587><tt><font size=2 color=blue><u>https://review.openstack.org/309587</u></font></tt></a><tt><font size=2><br>> > <br>> > <br>> > Na Zhu <nazhu@cn.ibm.com> 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 _http://docs.openstack.org/developer/python-openstackclient/<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 <br>> 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: nazhu@cn.ibm.com<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: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> > > </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font size=2><br>> > > <br>> > <br>> > <br>> > __________________________________________________________________________<br>> > OpenStack Development Mailing List (not for usage questions)<br>> > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> > </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font size=2><br>> > <br>> > <br>> > __________________________________________________________________________<br>> > OpenStack Development Mailing List (not for usage questions)<br>> > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> > </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font size=2><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font size=2>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br></font></tt><br><BR>