[openstack-dev] [neutron] OSC transition
nazhu at cn.ibm.com
Tue Apr 26 13:29:21 UTC 2016
Thanks your information, why you think neutron-dynamic-routing CLI should
live in python-neutronclient?
>From this link
section "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.
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: nazhu at cn.ibm.com
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
District, Shanghai, China (201203)
From: Henry Gessau <HenryG at gessau.net>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at 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
the python-neutronclient repo. Keep in touch with Richard Theis as he is
one leading the transition to OSC. He is rtheis on IRC.
Na Zhu <nazhu at 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
> removed from neutronclient. Because of OSC transition, I can not just
> BGP CLIs code from python-neutronclient repo to neutron-dynamic-routing
> I have to refactor the code and do transition to OSC plugin system.
> From the
> client has a separate repo, take designate as example, the CLI repo is
> python-designateclient, the project repo is designate. So for BGP,
> create a repo for CLI, or leverage project repo neutron-dynamic-routing?
> Juno Zhu
> IBM China Development Labs (CDL) Cloud IaaS Lab
> Email: nazhu at 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)
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev