summaryrefslogtreecommitdiffstats
path: root/docs/Chapter4/Devops.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/Chapter4/Devops.rst')
-rw-r--r--docs/Chapter4/Devops.rst168
1 files changed, 124 insertions, 44 deletions
diff --git a/docs/Chapter4/Devops.rst b/docs/Chapter4/Devops.rst
index 702db95..c333523 100644
--- a/docs/Chapter4/Devops.rst
+++ b/docs/Chapter4/Devops.rst
@@ -20,50 +20,129 @@ the DevOps guidelines for VNFs.
DevOps Requirements
-* R-46960 NCSPs **MAY** operate a limited set of Guest OS and CPU
- architectures and families, virtual machines, etc.
-* R-23475 VNFCs **SHOULD** be agnostic to the details of the Network Cloud
- (such as hardware, host OS, Hypervisor or container technology) and must run
- on the Network Cloud with acknowledgement to the paradigm that the Network
- Cloud will continue to rapidly evolve and the underlying components of
- the platform will change regularly.
-* R-33846 The VNF **MUST** install the NCSP required software on Guest OS
- images when not using the NCSP provided Guest OS images. [1]_
-* R-09467 The VNF **MUST** utilize only NCSP standard compute flavors. [1]_
-* R-02997 The VNF **MUST** preserve their persistent data. Running VMs
- will not be backed up in the Network Cloud infrastructure.
-* R-29760 The VNFC **MUST** be installed on non-root file systems,
- unless software is specifically included with the operating system
- distribution of the guest image.
-* R-20860 The VNF **MUST** be agnostic to the underlying infrastructure
- (such as hardware, host OS, Hypervisor), any requirements should be
- provided as specification to be fulfilled by any hardware.
-* R-89800 The VNF **MUST NOT** require Hypervisor-level customization
- from the cloud provider.
-* R-86758 The VNF **SHOULD** provide an automated test suite to validate
- every new version of the software on the target environment(s). The tests
- should be of sufficient granularity to independently test various
- representative VNF use cases throughout its lifecycle. Operations might
- choose to invoke these tests either on a scheduled basis or on demand to
- support various operations functions including test, turn-up and
- troubleshooting.
-* R-39650 The VNF **SHOULD** provide the ability to test incremental
- growth of the VNF.
-* R-14853 The VNF **MUST** respond to a "move traffic" [2]_ command
- against a specific VNFC, moving all existing session elsewhere with
- minimal disruption if a VNF provides a load balancing function across
- multiple instances of its VNFCs. Note: Individual VNF performance
- aspects (e.g., move duration or disruption scope) may require further
- constraints.
-* R-06327 The VNF **MUST** respond to a "drain VNFC" [2]_ command against
- a specific VNFC, preventing new session from reaching the targeted VNFC,
- with no disruption to active sessions on the impacted VNFC, if a VNF
- provides a load balancing function across multiple instances of its VNFCs.
- This is used to support scenarios such as proactive maintenance with no
- user impact.
-* R-64713 The VNF **SHOULD** support a software promotion methodology
- from dev/test -> pre-prod -> production in software, development &
- testing and operations.
+
+.. req::
+ :id: R-46960
+ :target: VNF
+ :keyword: MAY
+
+ NCSPs **MAY** operate a limited set of Guest OS and CPU
+ architectures and families, virtual machines, etc.
+
+.. req::
+ :id: R-23475
+ :target: VNF
+ :keyword: SHOULD
+
+ VNFCs **SHOULD** be agnostic to the details of the Network Cloud
+ (such as hardware, host OS, Hypervisor or container technology) and must run
+ on the Network Cloud with acknowledgement to the paradigm that the Network
+ Cloud will continue to rapidly evolve and the underlying components of
+ the platform will change regularly.
+
+.. req::
+ :id: R-33846
+ :target: VNF
+ :keyword: MUST
+
+ The VNF **MUST** install the NCSP required software on Guest OS
+ images when not using the NCSP provided Guest OS images. [1]_
+
+.. req::
+ :id: R-09467
+ :target: VNF
+ :keyword: MUST
+
+ The VNF **MUST** utilize only NCSP standard compute flavors. [1]_
+
+.. req::
+ :id: R-02997
+ :target: VNF
+ :keyword: MUST
+
+ The VNF **MUST** preserve their persistent data. Running VMs
+ will not be backed up in the Network Cloud infrastructure.
+
+.. req::
+ :id: R-29760
+ :target: VNF
+ :keyword: MUST
+
+ The VNFC **MUST** be installed on non-root file systems,
+ unless software is specifically included with the operating system
+ distribution of the guest image.
+
+.. req::
+ :id: R-20860
+ :target: VNF
+ :keyword: MUST
+
+ The VNF **MUST** be agnostic to the underlying infrastructure
+ (such as hardware, host OS, Hypervisor), any requirements should be
+ provided as specification to be fulfilled by any hardware.
+
+.. req::
+ :id: R-89800
+ :target: VNF
+ :keyword: MUST NOT
+
+ The VNF **MUST NOT** require Hypervisor-level customization
+ from the cloud provider.
+
+.. req::
+ :id: R-86758
+ :target: VNF
+ :keyword: SHOULD
+
+ The VNF **SHOULD** provide an automated test suite to validate
+ every new version of the software on the target environment(s). The tests
+ should be of sufficient granularity to independently test various
+ representative VNF use cases throughout its lifecycle. Operations might
+ choose to invoke these tests either on a scheduled basis or on demand to
+ support various operations functions including test, turn-up and
+ troubleshooting.
+
+.. req::
+ :id: R-39650
+ :target: VNF
+ :keyword: SHOULD
+
+ The VNF **SHOULD** provide the ability to test incremental
+ growth of the VNF.
+
+.. req::
+ :id: R-14853
+ :target: VNF
+ :keyword: MUST
+
+ The VNF **MUST** respond to a "move traffic" [2]_ command
+ against a specific VNFC, moving all existing session elsewhere with
+ minimal disruption if a VNF provides a load balancing function across
+ multiple instances of its VNFCs.
+
+ Note: Individual VNF performance aspects (e.g., move duration or
+ disruption scope) may require further constraints.
+
+.. req::
+ :id: R-06327
+ :target: VNF
+ :keyword: MUST
+
+ The VNF **MUST** respond to a "drain VNFC" [2]_ command against
+ a specific VNFC, preventing new session from reaching the targeted VNFC,
+ with no disruption to active sessions on the impacted VNFC, if a VNF
+ provides a load balancing function across multiple instances of its VNFCs.
+ This is used to support scenarios such as proactive maintenance with no
+ user impact.
+
+.. req::
+ :id: R-64713
+ :target: VNF
+ :keyword: SHOULD
+
+ The VNF **SHOULD** support a software promotion methodology
+ from dev/test -> pre-prod -> production in software, development &
+ testing and operations.
.. [1]
@@ -72,3 +151,4 @@ DevOps Requirements
.. [2]
Not currently supported in ONAP release 1
+