From 0ca11a945f993ee571a13f0ae56c8253714e440a Mon Sep 17 00:00:00 2001 From: Hagop Bozawglanian Date: Wed, 24 Apr 2019 17:17:59 +0000 Subject: VNFRQTS - Doc8 fixes Change-Id: Ic39bc7aa3e8eab163a8123164f88f30df7ae616c Issue-ID: VNFRQTS-606 Signed-off-by: Hagop Bozawglanian --- docs/Chapter5/Heat/ONAP Heat Networking.rst | 4 ++-- .../Neutron Parameters.rst | 6 +++--- .../Nova Parameters.rst | 6 +++--- .../Resource IDs.rst | 4 ++-- docs/Chapter5/Tosca.rst | 6 +++--- 5 files changed, 13 insertions(+), 13 deletions(-) (limited to 'docs/Chapter5') diff --git a/docs/Chapter5/Heat/ONAP Heat Networking.rst b/docs/Chapter5/Heat/ONAP Heat Networking.rst index 09a2244..8149a8a 100644 --- a/docs/Chapter5/Heat/ONAP Heat Networking.rst +++ b/docs/Chapter5/Heat/ONAP Heat Networking.rst @@ -173,10 +173,10 @@ or an external gateway or router * If the network name in is used to reference the network, the output parameter name in the base template **MUST** follow the naming convention ``int_{network-role}_net_name`` - + ``{network-role}`` **MUST** be the network-role of the internal network created in the Base Module. - + ``The Base Module Output Parameter MUST be declared in the ``parameters:`` section of the Incremental Module(s) where the ``OS::Neutron::Port`` resource(s) is attaching to the internal network. diff --git a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst index d2a7240..eb02322 100644 --- a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst +++ b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Neutron Parameters.rst @@ -1499,11 +1499,11 @@ VIP Assignment, External Networks, Supported by Automation OS::Nova::Server * ``{network-role}`` is the {network-role} of the external network - + And the parameter **MUST** be declared as ``type: string`` and **MUST** be enumerated in the environment file. - OR + OR the parameter name **MUST** follow the naming convention @@ -1516,7 +1516,7 @@ VIP Assignment, External Networks, Supported by Automation OS::Nova::Server * ``{network-role}`` is the {network-role} of the external network - + And the parameter **MUST** be declared as ``type: comma_delimited_list`` and **MUST** be enumerated in the environment file. diff --git a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Nova Parameters.rst b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Nova Parameters.rst index 0876628..4cbf3f5 100644 --- a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Nova Parameters.rst +++ b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Nova Parameters.rst @@ -376,10 +376,10 @@ Property: availability_zone :updated: casablanca The VNF's Heat Orchestration Template's Resource ``OS::Nova::Server`` - property ``availability_zone`` parameter name + property ``availability_zone`` parameter name **MUST** follow the naming convention - - * ``availability_zone_{index}`` + + * ``availability_zone_{index}`` where ``{index}`` is a numeric value that **MUST** start at zero in a VNF's Heat Orchestration Templates and **MUST** diff --git a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Resource IDs.rst b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Resource IDs.rst index 69fa19d..0d1093b 100644 --- a/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Resource IDs.rst +++ b/docs/Chapter5/Heat/ONAP Heat Resource ID and Parameter Naming Convention/Resource IDs.rst @@ -131,7 +131,7 @@ Heat Orchestration Template resources are described in :ref:`resources`. When a VNF's Heat Orchestration Template's Resource ID contains an ``{index}``, the ``{index}`` is a numeric value that **MUST** start at - zero and **MUST** increment by one. + zero and **MUST** increment by one. As stated in R-16447, *a VNF's MUST be unique across all Heat @@ -139,7 +139,7 @@ Heat Orchestration Template resources are described in :ref:`resources`. Nested YAML files that are used to create the VNF*. While the ``{index}`` will start at zero in the VNF, the ``{index}`` may not start at zero in a given Heat Orchestration Template or HEAT Orchestration Template - Nested YAML file. + Nested YAML file. OpenStack Heat Resources Resource ID Naming Convention ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/docs/Chapter5/Tosca.rst b/docs/Chapter5/Tosca.rst index e3d6102..79c6ad2 100644 --- a/docs/Chapter5/Tosca.rst +++ b/docs/Chapter5/Tosca.rst @@ -75,7 +75,7 @@ protocol, which supports multiple TOSCA template yaml files, and also supports self-defined node or other extensions. VNF or PNF CSAR Package -^^^^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^^^^^^^^^^^^^ CSAR Overview ~~~~~~~~~~~~~~~~ @@ -185,7 +185,7 @@ VNF Package Contents The VNF or PNF CSAR PACKAGE with TOSCA-Metadata **MUST** include following additional keywords pointing to TOSCA files: - + - ETSI-Entry-Manifest - ETSI-Entry-Change-Log @@ -683,7 +683,7 @@ Relationship Types The PNFD provided by a PNF vendor **MUST** comply with the following Relationship Types as specified in ETSI NFV-SOL001 standard: - + - tosca.datatypes.nfv.VirtualLinksTo -- cgit 1.2.3-korg