VNFRQTS - OpenStack recovery commands

Add Openstack foundational recovery commands to start, stop, rebuild, migrate, evacuate, snapshot VM or other containers.

Change-Id: I6ba8c6e8af4fd8f648830c6d7abbbdc6ee9f47c7
Issue-ID: VNFRQTS-213
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>

3 files changed, 81 insertions, 0 deletions

diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst
index 58e02f3..c501e7f 100644
--- a/docs/Chapter4.rst
+++ b/docs/Chapter4.rst
@@ -131,6 +131,10 @@ All Layer Redundancy Requirements
 * R-36843 The VNF **MUST** support the ability of the VNFC to be deployable
   in multi-zoned cloud sites to allow for site support in the event of cloud
   zone failure or upgrades.
+* R-00098 The VNF **MUST NOT** impact the ability of the VNF to provide
+  service/function due to a single container restart.
+* R-79952 The VNF **SHOULD** support container snapshots if not for rebuild
+  and evacuate for rollback or back out mechanism.
 
 Minimize Cross Data-Center Traffic
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -186,6 +190,16 @@ Application Resilient Error Handling Requirements
   service continuity.
 * R-36792 The VNF **MUST** automatically retry/resubmit failed requests
   made by the software to its downstream system to increase the success rate.
+* R-70013 The VNF **MUST NOT** require any manual steps to get it ready for
+  service after a container rebuild.
+* R-65515 The VNF **MUST** provide a mechanism and tool to start VNF
+  containers (VMs) without impacting service or service quality assuming
+  another VNF in same or other geographical location is processing service
+  requests.
+* R-94978 The VNF **MUST** provide a mechanism and tool to perform a graceful
+  shutdown of all the containers (VMs) in the VNF without impacting service
+  or service quality assuming another VNF in same or other geographical
+  location can take over traffic and process service requests.
 
 
 System Resource Optimization
@@ -1369,3 +1383,4 @@ Note:
 
 .. [2]
    Not currently supported in ONAP release 1
+
diff --git a/docs/Chapter7.rst b/docs/Chapter7.rst
index 89e6736..197771d 100644
--- a/docs/Chapter7.rst
+++ b/docs/Chapter7.rst
@@ -464,6 +464,39 @@ failed).
 * R-65641 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.
+
+* R-11790 The VNF **MUST** support ONAP Controller’s
+  **Restart (stop/start or reboot)** command.
+* R-56218 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.
+  
+* R-38001 The VNF MUST support ONAP Controller’s **Rebuild** command.
+* R-76901 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
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -1853,3 +1886,4 @@ Security
 .. |image3| image:: Protocol_Buffers_Driven_Model.png
       :width: 4.74in
       :height: 3.3in
+
diff --git a/docs/Chapter8.rst b/docs/Chapter8.rst
index 3b51bd9..1a4ad68 100644
--- a/docs/Chapter8.rst
+++ b/docs/Chapter8.rst
@@ -988,6 +988,12 @@ R-36843 The VNF **MUST** support the ability of the VNFC to be deployable
 in multi-zoned cloud sites to allow for site support in the event of cloud
 zone failure or upgrades.
 
+R-00098 The VNF **MUST NOT** impact the ability of the VNF to provide
+service/function due to a single container restart.
+
+R-79952 The VNF **SHOULD** support container snapshots if not for rebuild
+and evacuate for rollback or back out mechanism.
+
 R-92935 The VNF **SHOULD** minimize the propagation of state information
 across multiple data centers to avoid cross data center traffic.
 
@@ -1027,6 +1033,19 @@ service continuity.
 R-36792 The VNF **MUST** automatically retry/resubmit failed requests
 made by the software to its downstream system to increase the success rate.
 
+R-70013 The VNF **MUST NOT** require any manual steps to get it ready for
+service after a container rebuild.
+
+R-65515 The VNF **MUST** provide a mechanism and tool to start VNF
+containers (VMs) without impacting service or service quality assuming
+another VNF in same or other geographical location is processing service
+requests.
+
+R-94978 The VNF **MUST** provide a mechanism and tool to perform a graceful
+shutdown of all the containers (VMs) in the VNF without impacting service
+or service quality assuming another VNF in same or other geographical
+location can take over traffic and process service requests.
+
 R-22059 The VNF **MUST NOT** execute long running tasks (e.g., IO,
 database, network operations, service calls) in a critical section
 of code, so as to minimize blocking of other operations and increase
@@ -2522,6 +2541,18 @@ command.
 R-65641 The xNF **MUST** support ONAP Controller’s **UpgradeBackOut**
 command.
 
+R-11790 The VNF **MUST** support ONAP Controller’s
+**Restart (stop/start or reboot)** command.
+
+R-56218 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.
+  
+R-38001 The VNF MUST support ONAP Controller’s **Rebuild** command.
+
+R-76901 VNF MUST support a container rebuild mechanism based on existing
+image (e.g. Glance image in Openstack environment) or a snapshot.
+
 R-41430 The xNF **MUST** support ONAP Controller’s **HealthCheck**
 command.
 
@@ -3807,3 +3838,4 @@ UpgradePostCheck:
 .. [7]
    Multiple ONAP actions may map to one playbook.
 
+