openstack
/
deb-senlin
Code Issues Proposed changes

Refresh openstack cli outputs info 

All openstack cli return info changed 'Property' to 'Field', we
need refesh doc.
senlin <sub-command> no need to refresh.

Change-Id: I29fe87d49b0266f9171c66cd843f89bd8ab78a27
This commit is contained in:
liyi 2017-07-10 17:19:25 +08:00
parent de3bfc6050
commit 90a75ac9e6
10 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/install.rst
View File

@ -180,15 +180,15 @@ following.
::
$ openstack cluster build info
+----------+---------------------+
| Property | Value |
+----------+---------------------+
| api | { |
| | "revision": "1.0" |
| | } |
| engine | { |
| | "revision": "1.0" |
| | } |
+----------+---------------------+
+--------+---------------------+
| Field | Value |
+--------+---------------------+
| api | { |
| | "revision": "1.0" |
| | } |
| engine | { |
| | "revision": "1.0" |
| | } |
+--------+---------------------+
You are ready to begin your journey (aka. adventure) with Senlin, now.

4
doc/source/scenarios/autoscaling_ceilometer.rst
View File

@ -56,7 +56,7 @@ Then you can create a cluster using the profile named "``pserver``":
$ senlin cluster-create -p pserver -c 2 mycluster
+------------------+--------------------------------------+
| Property | Value |
| Field | Value |
+------------------+--------------------------------------+
| created_at | 2016-06-07T02:26:33Z |
| data | {} |
@ -128,7 +128,7 @@ by two nodes every time it is triggered:
$ openstack cluster receiver create --action CLUSTER_SCALE_OUT --params count=2 --cluster mycluster r_01
+------------+----------------------------------------------------------------------------+
| Property | Value |
| Field | Value |
+------------+----------------------------------------------------------------------------+
| action | CLUSTER_SCALE_OUT |
| actor | { |

2
doc/source/tutorial/autoscaling.rst
View File

@ -28,7 +28,7 @@ you can create a receiver for this task:
$ openstack cluster receiver create --type webhook --cluster mycluster \
--action CLUSTER_SCALE_OUT so_receiver_1
+------------+---------------------------------------------------+
| Property | Value |
| Field | Value |
+------------+---------------------------------------------------+
| action | CLUSTER_SCALE_OUT |
| actor | { |

2
doc/source/user/actions.rst
View File

@ -150,7 +150,7 @@ An example is shown below::
$ openstack cluster action show 8fac487f
+---------------+--------------------------------------+
| Property | Value |
| Field | Value |
+---------------+--------------------------------------+
| action | CLUSTER_DELETE |
| cause | RPC Request |

2
doc/source/user/bindings.rst
View File

@ -122,7 +122,7 @@ example::
$ openstack cluster policy binding show --policy dp01 c3
+--------------+--------------------------------------+
| Property | Value |
| Field | Value |
+--------------+--------------------------------------+
| cluster_name | c3 |
| data | None |

2
doc/source/user/clusters.rst
View File

@ -229,7 +229,7 @@ An example is shown below::
$ openstack cluster show c3
+------------------+--------------------------------------+
| Property | Value |
| Field | Value |
+------------------+--------------------------------------+
| created_at | 2015-07-07T03:30:53Z |
| data | {} |

2
doc/source/user/events.rst
View File

@ -166,7 +166,7 @@ An example is shown below::
$ openstack cluster event show 19ba155a
+---------------+--------------------------------------+
| Property | Value |
| Field | Value |
+---------------+--------------------------------------+
| action | delete |
| cluster_id | ce85d842-aa2a-4d83-965c-2cab5133aedc |

2
doc/source/user/nodes.rst
View File

@ -203,7 +203,7 @@ An example is shown below::
$ openstack cluster node show test_node
+---------------+--------------------------------------+
| Property | Value |
| Field | Value |
+---------------+--------------------------------------+
| cluster_id | None |
| created_at | 2015-07-09T11:41:20 |

4
doc/source/user/policies.rst
View File

@ -133,7 +133,7 @@ following command::
$ cd /opt/stack/senlin/examples/policies
$ openstack cluster policy create --spec deletion_policy.yaml dp01
+------------+-----------------------------------------------------------+
| Property | Value |
| Field | Value |
+------------+-----------------------------------------------------------+
| created_at | None |
| id | c2e3cd74-bb69-4286-bf06-05d802c8ec12 |
@ -164,7 +164,7 @@ the ID, the name or the "short ID" of a policy object. For example::
$ openstack cluster policy show dp01
+------------+------------------------------------------------------------+
| Property | Value |
| Field | Value |
+------------+------------------------------------------------------------+
| created_at | 2015-07-11T04:24:34 |
| id | c2e3cd74-bb69-4286-bf06-05d802c8ec12 |

4
doc/source/user/profiles.rst
View File

@ -140,7 +140,7 @@ Now you can create a profile using the following command::
--spec heat_stack_random_string.yaml \
my_stack
+--------------+-----------------------------------------------------------+
| Property | Value |
| Field | Value |
+--------------+-----------------------------------------------------------+
| created_at | 2015-07-01T03:13:23 |
| id | c0389712-9c1a-4c58-8ba7-caa61b34b8b0 |
@ -225,7 +225,7 @@ command to show the properties of a profile::
$ openstack cluster profile show myserver
+------------+---------------------------------------------------------+
| Property | Value |
| Field | Value |
+------------+---------------------------------------------------------+
| created_at | 2015-07-01T03:18:58 |
| id | 70a36cc7-9fc7-460e-98f6-d44e3302e604 |