updating folders structure and README files

examples/demos/README.md

@@ -0,0 +1,4 @@
+# Demos
+
+This directory contains some scenarios presented on demonstrations.
+

examples/demos/boot_from_SAN_and_server_profile_and_volume_migration/README.md

@@ -0,0 +1,17 @@
+# Demo
+## Server profile with boot from SAN and server profile & volume migration
+
+This demo is composed by 5 steps, each one associated with a playbook, that should be executed in the specified order: 
+
+- `step_1_create_server_profile_boot_from_SAN_and_assign_to_bay1.yml`: This playbook exemplifies how to create a server profile with boot from SAN (3PAR) and without using a template. On task #1, the server profile is created (if not already present) and assigned to server hardware in bay 1. You can check all parameters, including those related to the server hardware and those related to the storage as SAN connections and volume attachment. The volume must be ready to use. On task #2, the server hardware is powered on.
+
+- `step_2_based_on_server_profile_boot_from_SAN_add_another_volume.yml`: This playbook exemplifies how to add an extra volume attachment to an existing server profile. Task #1 was copied from step 1 and a new volume attachment was added identified by id 2. When this task is executed, the additional volume becomes available to the operating system.
+
+- `step_3_create_server_profile_based_on_server_profile_template_and_assign_to_bay12.yml`: This playbook exemplifies how to create a server profile using a server profile template. On task #1, the server profile is created (if not already present) and assigned to server hardware in bay 12. In this case, all settings were configured in the template, including network connections and OS deployment plan to use Image Streamer. On task #2, the server hardware is powered on.
+
+- `step_4_migrate_data_volume_from_bay1_to_bay12.yml`: This playbook exemplifies how to migrate a data volume from one server profile to another. 
+Task #1 was copied from step 2 when the extra volume was attached. To remove it, just remove volume attachment identified by id 2 and insert into task #2.
+Task #2 was copied from step 3 and a new volume attachment was added identified by id 2. The connectionId used by the storage paths must match with the SAN connections. In this case, the SAN connection ids in the server profile template were 4 and 5. 
+
+- `step_5_migrate_server_profile_from_bay1_to_bay11.yml`: This playbook exemplifies how to migrate a server profile from one server hardware to another. Task #1 was copied from step 1. To migrate from one server hardware you just need to specify the new server hardware name. 
+