VNFRQTS - Openstack lifecycle operations

Moving the VNF Operation resilient information from Ch 7 to Ch 4.

Issue-ID: VNFRQTS-459

Change-Id: Icd9b1626d412f35b6b448250a709ec196ccf0bb7
Signed-off-by: Bozawglanian, Hagop (hb755d) <hagop.bozawglanian@att.com>

3 files changed, 158 insertions, 66 deletions

diff --git a/docs/Chapter4/Resiliency.rst b/docs/Chapter4/Resiliency.rst
index 09e42a4..ea93f33 100644
--- a/docs/Chapter4/Resiliency.rst
+++ b/docs/Chapter4/Resiliency.rst
@@ -624,3 +624,98 @@ Monitoring & Dashboard Requirements
     rating for the VNF to be incorporated into the software design and
     development of the VNF.
 
+Virtual Function - Container Recovery Requirements
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+As part of life cycle management, for Cloud environment, VNFs need to
+support a set of basic recovery capabilities to maintain the health
+and extend the life of the VNF, eliminating and reducing the frequency
+that an entire VNF needs to be rebuilt or re-instantiated to recover one
+or more of its containers. For instance, a VNF in an Openstack environment
+is composed of one or more containers called VMs (Virtual Machines). During
+the life of a VNF it is expected that Cloud infrastructure hardware will
+fail or they would need to be taken down for maintenance or hardware and
+software upgrades (e.g. firmware upgrades, HostOS (Hypervisor), power
+maintenance, power outages, etc.) To deal with such life cycle events
+without having to rebuild entire VNFs or even entire sites these basic
+recovery capabilities of individual containers, Virtual Machines or other,
+must be supported.
+
+**Evacuate(VM)**: The Controller client is requesting moving a specified
+VM from its current AIC host to another (when the host is down). Moving
+from a specified Host will be supported at in a later release (Openstack).
+
+**Migrate (VM)**: The Controller client is requesting migrating a running
+target VM from its current AIC host to another. Migrating a running target
+VM from a specified Host will be supported at in a later release (Openstack).
+
+**Reboot(VM)**: The Controller client is requesting to reboot the VM.
+Options are soft (graceful) or hard (Openstack).
+
+**Rebuild (VM)**: The Controller client is recreating a target VM instance
+to a known (good) state (Openstack).
+
+**Restart (VM)**: The Controller client is requesting to restart the VM
+(Openstack).
+
+**Snapshot (VM)**: The Controller client is requesting to create a snapshot
+of a VNF or VM and store it (Openstack).
+
+**Start (VM)**: The Controller client is requesting to start the VM
+(Openstack).
+
+**Stop (VM)**: The Controller client is requesting to stop the VM
+(Openstack).
+
+.. req::
+    :id: R-11790
+    :target: VNF
+    :keyword: MUST
+
+    The VNF **MUST** support ONAP Controller's
+    **Restart (stop/start or reboot)** command.
+
+.. req::
+    :id: R-56218
+    :target: VNF
+    :keyword: MUST
+
+    The VNF **MUST** support ONAP Controller's Migrate command that
+    moves container (VM) from a live Physical Server / Compute Node to
+    another live Physical Server / Compute Node.
+
+        Note: Container migrations MUST be transparent to the VNF and no more intrusive than a stop,
+        followed by some down time for the migration to be performed from one Compute Node / Physical
+        Server to another, followed by a start of the same VM with same configuration on the new
+        Compute Node / Physical Server.
+
+.. req::
+    :id: R-38001
+    :target: VNF
+    :keyword: MUST
+
+    The VNF **MUST** support ONAP Controller's **Rebuild** command.
+
+.. req::
+    :id: R-76901
+    :target: VNF
+    :keyword: MUST
+
+    The VNF **MUST** support a container rebuild mechanism based on existing
+    image (e.g. Glance image in Openstack environment) or a snapshot.
+
+.. req::
+    :id: R-46851
+    :target: VNF
+    :keyword: MUST
+    :introduced: casablanca
+
+    The VNF **MUST** support ONAP Controller’s Evacuate command.
+
+.. req::
+    :id: R-48761
+    :target: VNF
+    :keyword: MUST
+    :introduced: casablanca
+
+    The VNF **MUST** support ONAP Controller’s Snapshot command.
\ No newline at end of file
diff --git a/docs/Chapter7/Configuration-Management.rst b/docs/Chapter7/Configuration-Management.rst
index 1259bc7..c737a62 100755
--- a/docs/Chapter7/Configuration-Management.rst
+++ b/docs/Chapter7/Configuration-Management.rst
@@ -241,61 +241,6 @@ failed).
 
     The xNF **MUST** support ONAP Controller's **UpgradeBackOut** command.
 
-Virtual Function - Container Recovery Requirements
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-As part of life cycle management, for Cloud environment, VNFs need to
-support a set of basic recovery capabilities to maintain the health
-and extend the life of the VNF, eliminating and reducing the frequency
-that an entire VNF needs to be rebuilt or re-instantiated to recover one
-or more of its containers. For instance, a VNF in an Openstack environment
-is composed of one or more containers called VMs (Virtual Machines). During
-the life of a VNF it is expected that Cloud infrastructure hardware will
-fail or they would need to be taken down for maintenance or hardware and
-software upgrades (e.g. firmware upgrades, HostOS (Hypervisor), power
-maintenance, power outages, etc.) To deal with such life cycle events
-without having to rebuild entire VNFs or even entire sites these basic
-recovery capabilities of individual containers, Virtual Machines or other,
-must be supported.
-
-
-.. req::
-    :id: R-11790
-    :target: VNF
-    :keyword: MUST
-
-    The VNF **MUST** support ONAP Controller's
-    **Restart (stop/start or reboot)** command.
-
-.. req::
-    :id: R-56218
-    :target: VNF
-    :keyword: MUST
-
-    The VNF **MUST** support ONAP Controller's Migrate command that
-    moves container (VM) from a live Physical Server / Compute Node to
-    another live Physical Server / Compute Node.
-
-        Note: Container migrations MUST be transparent to the VNF and no more intrusive than a stop,
-        followed by some down time for the migration to be performed from one Compute Node / Physical
-        Server to another, followed by a start of the same VM with same configuration on the new
-        Compute Node / Physical Server.
-
-.. req::
-    :id: R-38001
-    :target: VNF
-    :keyword: MUST
-
-    The VNF **MUST** support ONAP Controller's **Rebuild** command.
-
-.. req::
-    :id: R-76901
-    :target: VNF
-    :keyword: MUST
-
-    The VNF **MUST** support a container rebuild mechanism based on existing
-    image (e.g. Glance image in Openstack environment) or a snapshot.
-
 HealthCheck and Failure Related Commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/docs/data/needs.json b/docs/data/needs.json
index 9a905b5..a40c781 100644
--- a/docs/data/needs.json
+++ b/docs/data/needs.json
@@ -1,5 +1,5 @@
 {
-    "created": "2018-10-15T15:13:37.861776",
+    "created": "2018-10-15T22:34:19.210493",
     "current_version": "casablanca",
     "project": "",
     "versions": {
@@ -21858,7 +21858,7 @@
             "needs_amount": 750
         },
         "casablanca": {
-            "created": "2018-10-15T15:13:37.861759",
+            "created": "2018-10-15T22:34:19.210426",
             "needs": {
                 "R-00011": {
                     "description": "A VNF's Heat Orchestration Template's parameter defined\nin a nested YAML file\n**MUST NOT** have a parameter constraint defined.",
@@ -24137,8 +24137,7 @@
                     "section_name": "Virtual Function - Container Recovery Requirements",
                     "sections": [
                         "Virtual Function - Container Recovery Requirements",
-                        "Controller Interactions With VNF",
-                        "Configuration Management"
+                        "VNF Resiliency"
                     ],
                     "status": null,
                     "tags": [],
@@ -30199,8 +30198,7 @@
                     "section_name": "Virtual Function - Container Recovery Requirements",
                     "sections": [
                         "Virtual Function - Container Recovery Requirements",
-                        "Controller Interactions With VNF",
-                        "Configuration Management"
+                        "VNF Resiliency"
                     ],
                     "status": null,
                     "tags": [],
@@ -32098,6 +32096,34 @@
                     "validated_by": "",
                     "validation_mode": "static"
                 },
+                "R-46851": {
+                    "description": "The VNF **MUST** support ONAP Controller\u2019s Evacuate command.",
+                    "full_title": "",
+                    "hide_links": "",
+                    "id": "R-46851",
+                    "impacts": "",
+                    "introduced": "casablanca",
+                    "keyword": "MUST",
+                    "links": [],
+                    "notes": "",
+                    "section_name": "Virtual Function - Container Recovery Requirements",
+                    "sections": [
+                        "Virtual Function - Container Recovery Requirements",
+                        "VNF Resiliency"
+                    ],
+                    "status": null,
+                    "tags": [],
+                    "target": "VNF",
+                    "test": "",
+                    "test_case": "",
+                    "test_file": "",
+                    "title": "",
+                    "title_from_content": "",
+                    "type_name": "Requirement",
+                    "updated": "",
+                    "validated_by": "",
+                    "validation_mode": ""
+                },
                 "R-46908": {
                     "description": "The VNF **MUST**, if not integrated with the Operator's Identity\nand Access Management system, comply with \"password complexity\"\npolicy. When passwords are used, they shall be complex and shall at\nleast meet the following password construction requirements: (1) be a\nminimum configurable number of characters in length, (2) include 3 of\nthe 4 following types of characters: upper-case alphabetic, lower-case\nalphabetic, numeric, and special, (3) not be the same as the UserID\nwith which they are associated or other common strings as specified\nby the environment, (4) not contain repeating or sequential characters\nor numbers, (5) not to use special characters that may have command\nfunctions, and (6) new passwords must not contain sequences of three\nor more characters from the previous password.",
                     "full_title": "",
@@ -32638,6 +32664,34 @@
                     "validated_by": "",
                     "validation_mode": ""
                 },
+                "R-48761": {
+                    "description": "The VNF **MUST** support ONAP Controller\u2019s Snapshot command.",
+                    "full_title": "",
+                    "hide_links": "",
+                    "id": "R-48761",
+                    "impacts": "",
+                    "introduced": "casablanca",
+                    "keyword": "MUST",
+                    "links": [],
+                    "notes": "",
+                    "section_name": "Virtual Function - Container Recovery Requirements",
+                    "sections": [
+                        "Virtual Function - Container Recovery Requirements",
+                        "VNF Resiliency"
+                    ],
+                    "status": null,
+                    "tags": [],
+                    "target": "VNF",
+                    "test": "",
+                    "test_case": "",
+                    "test_file": "",
+                    "title": "",
+                    "title_from_content": "",
+                    "type_name": "Requirement",
+                    "updated": "",
+                    "validated_by": "",
+                    "validation_mode": ""
+                },
                 "R-48880": {
                     "description": "If a VNF's Port is attached to an external network and the port's\nIP addresses are assigned by ONAP's SDN-Controller,\nthe ``OS::Neutron::Port`` Resource's\n\n* property ``fixed_ips`` map property ``ip_address`` **MUST** be used\n* property ``fixed_ips`` map property ``subnet``\n  **MUST NOT** be used",
                     "full_title": "",
@@ -34111,8 +34165,7 @@
                     "section_name": "Virtual Function - Container Recovery Requirements",
                     "sections": [
                         "Virtual Function - Container Recovery Requirements",
-                        "Controller Interactions With VNF",
-                        "Configuration Management"
+                        "VNF Resiliency"
                     ],
                     "status": null,
                     "tags": [],
@@ -38232,8 +38285,7 @@
                     "section_name": "Virtual Function - Container Recovery Requirements",
                     "sections": [
                         "Virtual Function - Container Recovery Requirements",
-                        "Controller Interactions With VNF",
-                        "Configuration Management"
+                        "VNF Resiliency"
                     ],
                     "status": null,
                     "tags": [],
@@ -43416,7 +43468,7 @@
                     "validation_mode": "static"
                 }
             },
-            "needs_amount": 757
+            "needs_amount": 759
         }
     }
 }
\ No newline at end of file