<tt><font size=2>Akihiro Motoki <amotoki@gmail.com> wrote on 05/06/2016
08:20:45 PM:<br>
<br>
> From: Akihiro Motoki <amotoki@gmail.com></font></tt>
<br><tt><font size=2>> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org></font></tt>
<br><tt><font size=2>> Date: 05/06/2016 08:23 PM</font></tt>
<br><tt><font size=2>> Subject: [openstack-dev] [neutron][osc] Austin
Design summit summary<br>
> on the future of Neutron client</font></tt>
<br><tt><font size=2>> <br>
> n Austin we had a session on the future of neutron client and<br>
> discussed the CLI transition to OpenStack Client (OSC).<br>
> The session etherpad is found at [1].<br>
> <br>
> * We checked the progress of OSC transition and it is good.<br>
> Support of 11 resources which are targets of the initial effort.<br>
> In Newton cycle, we will focus on achieving the feature parity
to<br>
> the existing 'neutron' CLI.<br>
> <br>
> * We agreed that OSC support for neutron advanced services will be<br>
> done via OSC plugin.<br>
> BGP stuff (neutron-dynamic-routing) will be supported via OSC
<br>
> plugin as well.<br>
> neutron-dynamic-routing needs to be added to the list at [2].</font></tt>
<br>
<br><tt><font size=2>Thanks for the summary Akihiro. Here's the patch set
to add BGP:</font></tt>
<br><a href=https://review.openstack.org/#/c/313865/><tt><font size=2>https://review.openstack.org/#/c/313865/</font></tt></a>
<br>
<br><tt><font size=2>> Future official sub projects (possibly
like sfc, l2gw) will be<br>
> handled in the same way.<br>
> <br>
> * CLI support for new features should be implemented in OpenStack<br>
> Client (and openstacksdk).<br>
> All should go to OSC. neutronclient CLI support is optional.<br>
> Around the feature freeze, neutron and openstackclient team
will<br>
> communicate more closely to coordinate a new release.<br>
> <br>
> * python bindings in neutronclient:<br>
> All features provided by the main neutron repo will be supported
by<br>
> openstackclient and openstacksdk.<br>
> python bindings in the python-neutronclient need to be added
only if<br>
> an openstack service needs to use the bindings.<br>
> (for example, get-me-a-network python binding is required by
nova.)<br>
> <br>
> * A discussion about where is an appropriate place for admin commands,<br>
> OSC repo vs OSC plugin in the python-neutronclient repo.<br>
> If admin commands are provided by OSC plugin, it will reduce
the<br>
> number of commands that regular users will see.<br>
> On the other hand, API permissions can be configured by the
policy.<br>
> One option is to install the OSC plugin<br>
> which provides admin commands if users want to use them.<br>
> In my understanding, there is no actual consensus in the session.<br>
> (Note that the similar discussion happend for nova OSC support
in<br>
> the dev list after the summit. [3])<br>
> <br>
> Thanks,<br>
> Akihiro<br>
> <br>
> [1] </font></tt><a href="https://etherpad.openstack.org/p/newton-neutron-future-neutron-client"><tt><font size=2>https://etherpad.openstack.org/p/newton-neutron-future-neutron-client</font></tt></a><tt><font size=2><br>
> [2] </font></tt><a href="https://github.com/openstack/python-neutronclient/blob/master/"><tt><font size=2>https://github.com/openstack/python-neutronclient/blob/master/</font></tt></a><tt><font size=2><br>
> doc/source/devref/transition_to_osc.rst#developer-guide<br>
> [3] </font></tt><a href="http://lists.openstack.org/pipermail/openstack-dev/2016-May/093955.html"><tt><font size=2>http://lists.openstack.org/pipermail/openstack-dev/2016-May/093955.html</font></tt></a><tt><font size=2><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>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
> <br>
</font></tt>