From 6c82731fe733a6f85430cae0ddc541faa7f54dc5 Mon Sep 17 00:00:00 2001 From: Richard Theis Date: Tue, 29 Mar 2016 13:10:47 -0500 Subject: [PATCH] Devref Update: Transition to OpenStack Client Update the "Transition to OpenStack Client" devref with the following: - Status update per start of Newton release - Change developer references to use github for latest information Change-Id: I17111b833a83395f379ed8e93091cd1956b80dbd Related-Bug: #1521291 --- doc/source/devref/transition_to_osc.rst | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/source/devref/transition_to_osc.rst b/doc/source/devref/transition_to_osc.rst index 0ac2c90..511c41a 100644 --- a/doc/source/devref/transition_to_osc.rst +++ b/doc/source/devref/transition_to_osc.rst @@ -82,13 +82,13 @@ Transition Steps is enabled, then the nova client's Python library will continue to be used. See the following OSC bugs: - * `Floating IP CRUD `_ + * **In Progress** `Floating IP CRUD `_ - * `Port CRUD `_ + * **In Progress** `Port CRUD `_ - * `Security Group CRUD `_ + * **Done** `Security Group CRUD `_ - * `Security Group Rule CRUD `_ + * **In Progress** `Security Group Rule CRUD `_ 6. **In Progress:** OSC continues enhancing its networking support. At this point and when applicable, enhancements to the ``neutron`` @@ -122,8 +122,8 @@ Transition Steps Developer Guide --------------- The ``neutron`` CLI version 4.x, without extensions, supports over 200 -commands while the ``openstack`` CLI version 2.1.0 supports about 30 -networking commands. Of the 30 commands, many do not have all of the options +commands while the ``openstack`` CLI version 2.2.0 supports about 35 +networking commands. Of the 35 commands, many do not have all of the options or arguments of their ``neutron`` CLI equivalent. With this large functional gap, a couple critical questions for developers during this transition are "Which CLI do I change?" and "Where does my CLI belong?" The answer depends on the @@ -205,8 +205,8 @@ you can optionally propose an which documents the new command interface before proceeding with the implementation. Users of the neutron client's command extensions must adopt the -`OSC plugin system `_ -for this transition. Such users will maintain their OSC plugin within their +`OSC plugin `_ +system for this transition. Such users will maintain their OSC plugin within their own project and should follow the guidance in the table above to determine which command to change. @@ -215,17 +215,17 @@ Developer References * See `OSC neutron support etherpad `_ to determine if an ``openstack`` command is in progress. -* See `OSC command list `_ +* See `OSC command list `_ to determine if an ``openstack`` command exists. * See `OSC command spec list `_ to determine if an ``openstack`` command spec exists. * See `OSC plugin command list `_ to determine if an ``openstack`` plugin command exists. -* See `OSC command structure `_ +* See `OSC command structure `_ to determine the current ``openstack`` command objects, plugin objects and actions. -* See `OSC human interface guide `_ +* See `OSC human interface guide `_ for guidance on creating new OSC command interfaces. -* See `OSC plugin `_ +* See `OSC plugin `_ for information on the OSC plugin system to be used for ``neutron`` CLI extensions. * Create an OSC blueprint: https://blueprints.launchpad.net/python-openstackclient/ * Report an OSC bug: https://bugs.launchpad.net/python-openstackclient/+filebug