Merge "Add a 'Client (CLI) impact' section to the spec"
This commit is contained in:
commit
d5b6a20209
@ -81,6 +81,10 @@ REST API impact
|
|||||||
---------------
|
---------------
|
||||||
None
|
None
|
||||||
|
|
||||||
|
Client (CLI) impact
|
||||||
|
-------------------
|
||||||
|
None
|
||||||
|
|
||||||
Driver API impact
|
Driver API impact
|
||||||
-----------------
|
-----------------
|
||||||
None
|
None
|
||||||
|
@ -86,6 +86,10 @@ REST API impact
|
|||||||
---------------
|
---------------
|
||||||
None
|
None
|
||||||
|
|
||||||
|
Client (CLI) impact
|
||||||
|
-------------------
|
||||||
|
None
|
||||||
|
|
||||||
RPC API impact
|
RPC API impact
|
||||||
--------------
|
--------------
|
||||||
None
|
None
|
||||||
|
@ -78,6 +78,10 @@ REST API impact
|
|||||||
|
|
||||||
None
|
None
|
||||||
|
|
||||||
|
Client (CLI) impact
|
||||||
|
-------------------
|
||||||
|
None
|
||||||
|
|
||||||
RPC API impact
|
RPC API impact
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
@ -74,6 +74,10 @@ REST API impact
|
|||||||
---------------
|
---------------
|
||||||
None
|
None
|
||||||
|
|
||||||
|
Client (CLI) impact
|
||||||
|
-------------------
|
||||||
|
None
|
||||||
|
|
||||||
RPC API impact
|
RPC API impact
|
||||||
--------------
|
--------------
|
||||||
None
|
None
|
||||||
|
@ -191,6 +191,13 @@ content of the JSON dict and an ability to validate it.
|
|||||||
|
|
||||||
Reuse of existing predefined parameter types is highly encouraged.
|
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
|
RPC API impact
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
@ -287,11 +294,8 @@ to the OpenStack Security Group at openstack-security@lists.openstack.org.
|
|||||||
Other end user impact
|
Other end user impact
|
||||||
---------------------
|
---------------------
|
||||||
|
|
||||||
Aside from the API, are there other ways a user will interact with this
|
Aside from the API and client, are there other ways a user will interact with
|
||||||
feature?
|
this feature?
|
||||||
|
|
||||||
* Does this change have an impact on python-ironicclient? What does the user
|
|
||||||
interface there look like?
|
|
||||||
|
|
||||||
* Will this require changes in the Horizon panel, or any other OpenStack
|
* Will this require changes in the Horizon panel, or any other OpenStack
|
||||||
project?
|
project?
|
||||||
|
Loading…
Reference in New Issue
Block a user