Fix yaml metadata example for volumes and roles

Change-Id: I7a8b2d0ed32ef9d704cd47eb6237e7144d6bf3ad
Implements: blueprint role-as-a-plugin
This commit is contained in:
Andriy Popovych 2015-07-10 11:52:58 +03:00
parent 8fcc8c99b9
commit 9dfb24e830

View File

@ -278,7 +278,6 @@ Plugin impact
.. code-block:: yaml .. code-block:: yaml
role_name: role_name:
metadata:
name: "Some plugin role" name: "Some plugin role"
description: "Some description" description: "Some description"
conflicts: conflicts:
@ -288,9 +287,6 @@ Plugin impact
restrictions: restrictions:
- condition: "some logic condition" - condition: "some logic condition"
message: "Some message for restriction warning" message: "Some message for restriction warning"
volumes_mapping:
- {allocate_size: "min", id: "os"}
- {allocate_size: "all", id: "role_volume_name"}
Description of volumes partition in `volumes` yaml file: Description of volumes partition in `volumes` yaml file:
@ -312,6 +308,10 @@ Plugin impact
name: "swap" name: "swap"
size: {generator: "calc_swap_size"} size: {generator: "calc_swap_size"}
file_system: "swap" file_system: "swap"
volumes_roles_mapping:
role_name:
- {allocate_size: "min", id: "os"}
- {allocate_size: "all", id: "role_volume_name"}
Pre/Post deployment tasks are kept in `tasks` yaml as before and Pre/Post deployment tasks are kept in `tasks` yaml as before and
deployment tasks will be described in `deployment_tasks` yaml file. deployment tasks will be described in `deployment_tasks` yaml file.