summaryrefslogtreecommitdiffstats
path: root/docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst
diff options
context:
space:
mode:
authorBozawglanian, Hagop (hb755d) <hb755d@att.com>2018-09-12 22:48:10 +0000
committerBozawglanian, Hagop (hb755d) <hb755d@att.com>2018-09-12 23:21:33 +0000
commitefb8f384941889d8d7fa469fecebe9b0e8169065 (patch)
tree106a74d8c789497b85019ebec7674fb3b2ba620b /docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst
parent50f5d2aaf582d3abd1db447646456cce2d1274b5 (diff)
VNFRQTS - update HEAT Batch 2
Including changes for sections 5.6 - 5.9 Issue-ID: VNFRQTS-438 Change-Id: I9bfcaf52cd41a523ff6f6b4dd1cd32bc731d47d2 Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
Diffstat (limited to 'docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst')
-rw-r--r--docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst20
1 files changed, 14 insertions, 6 deletions
diff --git a/docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst b/docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst
index 70ba197..7e1ebe3 100644
--- a/docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst
+++ b/docs/Chapter5/Heat/ONAP Heat VNF Modularity.rst
@@ -15,12 +15,12 @@ referred to as *VNF Modules*. During orchestration, these modules
are deployed incrementally to create the complete VNF.
As stated in :need:`R-33132`, a VNF's Heat Orchestration Template **MAY** be
- 1.) Base Module Heat Orchestration Template (also referred to as a
- Base Module),
- 2.) Incremental Module Heat Orchestration Template (referred to as
- an Incremental Module), or
- 3.) a Cinder Volume Module Heat Orchestration Template (referred to as
- Cinder Volume Module).
+ 1. Base Module Heat Orchestration Template (also referred to as a
+ Base Module),
+ 2. Incremental Module Heat Orchestration Template (referred to as
+ an Incremental Module), or
+ 3. a Cinder Volume Module Heat Orchestration Template (referred to as
+ Cinder Volume Module).
As stated in :need:`R-20974`, at orchestration time, the VNF's Base Module **MUST**
be deployed first, prior to any incremental modules.
@@ -39,6 +39,9 @@ As stated in :need:`R-37028` and :need:`R-13196`, a VNF **MUST** be composed
of one Base Module and *MAY** be composed of zero to many Incremental
Modules.
+As stated in :need:`R-20974`, at orchestration time, the VNF's Base Module
+**MUST** be deployed first, prior to any incremental modules.
+
ONAP also supports the concept of an optional, independently deployed
Cinder volume via a separate Heat Orchestration Templates, referred to
as a Cinder Volume Module. This allows the volume to persist after a VM
@@ -58,6 +61,8 @@ Incremental Module.
:id: R-61001
:target: VNF
:keyword: MUST
+ :validation_mode: static
+ :updated: casablanca
A shared Heat Orchestration Template resource must be defined
in the base module. A shared resource is a resource that that will
@@ -71,6 +76,9 @@ When the shared resource needs to be referenced by a resource in an
incremental module, the UUID of the shared resource must be exposed by
declaring an ONAP Base Module Output Parameter.
+Note that a Cinder volume is not a shared resource. A volume template
+must correspond 1:1 with a base module or incremental module.
+
An example of a shared resource is the resource
OS::Neutron::SecurityGroup. Security groups are sets of IP filter rules
that are applied to a VNF’s networking. The resource OS::Neutron::Port