Merge "Add a 'Client (CLI) impact' section to the spec"

This commit is contained in:
Jenkins 2015-05-13 19:01:39 +00:00 committed by Gerrit Code Review
commit d5b6a20209
5 changed files with 25 additions and 5 deletions

View File

@ -81,6 +81,10 @@ REST API impact
---------------
None
Client (CLI) impact
-------------------
None
Driver API impact
-----------------
None

View File

@ -86,6 +86,10 @@ REST API impact
---------------
None
Client (CLI) impact
-------------------
None
RPC API impact
--------------
None

View File

@ -78,6 +78,10 @@ REST API impact
None
Client (CLI) impact
-------------------
None
RPC API impact
--------------

View File

@ -74,6 +74,10 @@ REST API impact
---------------
None
Client (CLI) impact
-------------------
None
RPC API impact
--------------
None

View File

@ -191,6 +191,13 @@ content of the JSON dict and an ability to validate it.
Reuse of existing predefined parameter types is highly encouraged.
Client (CLI) impact
-------------------
Typically, but not always, if there are any REST API changes, there are
corresponding changes to python-ironicclient. If so, what does the user
interface look like. If not, describe why there are REST API changes but
no changes to the client.
RPC API impact
--------------
@ -287,11 +294,8 @@ to the OpenStack Security Group at openstack-security@lists.openstack.org.
Other end user impact
---------------------
Aside from the API, are there other ways a user will interact with this
feature?
* Does this change have an impact on python-ironicclient? What does the user
interface there look like?
Aside from the API and client, are there other ways a user will interact with
this feature?
* Will this require changes in the Horizon panel, or any other OpenStack
project?