I've asked about the conclusion here [1]. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html
Na Zhu/China/IBM wrote on 05/01/2016 09:11:43 PM: > From: Na Zhu/China/IBM@IBMCN > To: rth...@us.ibm.com > Cc: openstack-dev@lists.openstack.org > Date: 05/01/2016 09:11 PM > Subject: Re: [openstack-dev] [neutron] OSC transition > > Hi Richard, > > So what is the conclusion of where to put *aas CLI? > > > > Regards, > Juno Zhu > IBM China Development Labs (CDL) Cloud IaaS Lab > Email: na...@cn.ibm.com > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong > New District, Shanghai, China (201203) > > > > From: Richard Theis <rth...@us.ibm.com> > To: "OpenStack Development Mailing List \(not for usage > questions\)" <openstack-dev@lists.openstack.org> > Date: 2016/04/26 22:32 > Subject: Re: [openstack-dev] [neutron] OSC transition > > > > Hi, > > The latest devref [1] would place it in python-neutronclient as > Henry noted. But stay tuned for results from the summit session. > > [1] https://github.com/openstack/python-neutronclient/blob/master/ > doc/source/devref/transition_to_osc.rst > > - Richard > > > "Na Zhu" <na...@cn.ibm.com> wrote on 04/26/2016 08:29:21 AM: > > > From: "Na Zhu" <na...@cn.ibm.com> > > To: hen...@gessau.net > > Cc: "OpenStack Development Mailing List \(not for usage questions\)" > > <openstack-dev@lists.openstack.org> > > Date: 04/26/2016 08:34 AM > > Subject: Re: [openstack-dev] [neutron] OSC transition > > > > Hi Henry, > > > > Thanks your information, why you think neutron-dynamic-routing CLI > > should live in python-neutronclient? > > From this link http://docs.openstack.org/developer/python- > > neutronclient/devref/transition_to_osc.htmlsection "Where does my > CLI belong? > > ", *aas CLI belongs to their own project, not project python- > > neutronclient. BGP is also service like *aas, so I think BGP CLIs > > should live in neutron-dynamic-routing, or a separate repo named > > python-*client. Pls correct me if I am wrong, thanks. > > > > > > > > Regards, > > Juno Zhu > > IBM China Development Labs (CDL) Cloud IaaS Lab > > Email: na...@cn.ibm.com > > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong > > New District, Shanghai, China (201203) > > > > > > > > From: Henry Gessau <hen...@gessau.net> > > To: "OpenStack Development Mailing List (not for usage > > questions)" <openstack-dev@lists.openstack.org> > > Date: 2016/04/26 21:09 > > Subject: Re: [openstack-dev] [neutron] OSC transition > > > > > > > > Adding the [neutron] tag. > > > > I believe that the OSC extension for neutron-dynamic-routing should live in > > the python-neutronclient repo. Keep in touch with Richard Theis ashe is the > > one leading the transition to OSC. He is rtheis on IRC. > > > > See: > > http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html > > https://review.openstack.org/309587 > > > > > > Na Zhu <na...@cn.ibm.com> wrote: > > > Dear All, > > > > > > > > > I have a question about OSC transition, recently, the community approves > > > moving bgp out of neutron, as a service like other *aas. The BGP > > CLIs need be > > > removed from neutronclient. Because of OSC transition, I can not > > just move the > > > BGP CLIs code from python-neutronclient repo to neutron-dynamic- > > routing repo. > > > I have to refactor the code and do transition to OSC plugin system. > > > > > > From the > > > link _http://docs.openstack.org/developer/python-openstackclient/ > > plugins.html_, the > > > client has a separate repo, take designate as example, the CLI repo is > > > python-designateclient, the project repo is designate. So for > BGP, should I > > > create a repo for CLI, or leverage project repo neutron-dynamic-routing? > > > > > > > > > > > > > > > Regards, > > > Juno Zhu > > > IBM China Development Labs (CDL) Cloud IaaS Lab > > > Email: na...@cn.ibm.com > > > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New > > > District, Shanghai, China (201203) > > > > > > > > > __________________________________________________________________________ > > > OpenStack Development Mailing List (not for usage questions) > > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
