openstack/fuel-docs
Code Issues Proposed changes

Fix Typo in create plugin

Browse Source 
Change-Id: Id8afeec53fa9861e664a416b319234899fde326e
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
This commit is contained in:
Guo Ruijing
2016-07-07 16:36:11 +08:00
parent dba0d16eac
commit e572a834f2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
plugindocs/fuel-plugin-sdk-guide/create-plugin/create-auto-plugin.rst
View File

@@ -60,8 +60,8 @@ The automatically generated plugin does the following:
|``tasks.yaml`` |Deprecated, use ``deployment_tasks.yaml`` instead |
+----------------------------------------------+--------------------------------------------------+
|``volumes.yaml`` |Mapping between node roles and volume allocation. |
| |You can also define new volumesand map them to the|
| |new or existing nodes. |
| |You can also define new volumes and map them to |
| |the new or existing nodes. |
+----------------------------------------------+--------------------------------------------------+
#. Build the automatically generated plugin:
@@ -113,4 +113,4 @@ You can also verify the plugin installation using Fuel CLI:
Enabling a plugin after deployment makes sense only in one case:
when this adds a new node role and a node with this role can be
added after the environment is deployed. In this case use the keyword
``is_hotppluggable`` in ``metadata.yaml``
``is_hotppluggable`` in ``metadata.yaml``