1 .. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
3 .. Licensed under the Creative Commons License, Attribution 4.0 Intl.
4 (the "License"); you may not use this documentation except in compliance
5 with the License. You may obtain a copy of the License at
7 .. https://creativecommons.org/licenses/by/4.0/
9 .. Unless required by applicable law or agreed to in writing, software
10 distributed under the License is distributed on an "AS IS" BASIS,
11 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 See the License for the specific language governing permissions and
13 limitations under the License.
16 ONAP TOSCA VNFD or PNFD Requirements
17 ------------------------------------
23 The following sub-clauses describe the numbered requirements for VNF
24 Descriptor (VNFD) and PNF Descriptor (PNFD) or in other words the VNF/PNF
25 Service Template based on the most updated draft of ETSI NFV-SOL001 standard
26 for VNF/PNF Descriptor. The ETSI standard specifies a NFV specific data
27 model using TOSCA/YAML data model constructs specified in TOSCA Simple
28 Profile in YAML v.1.2.
30 The requirements for TOSCA/CSAR based VNF/PNF package are described as well
31 and they are based on ETSI NFV-SOL004 standard.
36 1. ETSI GS NFV-SOL001 v.2.5.1
37 2. TOSCA SIMPLE Profile in YAML v.1.2
38 3. ETSI GS NFV-SOL004 v.2.6.1 + NFV CR NFVSOL(18)000746r3.
43 This document is intended for developers of VNF TOSCA templates that
44 will be orchestrated by ONAP. The document is also applicable for
45 creating RFP’s with the list of required TOSCA/YAML features
46 supported by VNF provider.
51 ONAP implementations of Network Cloud supports TOSCA Templates, also
52 referred to as TOSCA in this document.
54 ONAP requires the TOSCA Templates to follow a specific format. This
55 document provides the mandatory, recommended, and optional requirements
56 associated with this format.
61 The document includes three charters to help the VNF or PNF providers to
62 use the VNF or PNF model design tools and understand the VNF or PNF package
63 structure and VNF or PNF TOSCA templates.
65 In the ONAP, VNF or PNF Package and VNFD or PNFD template can be designed by
66 manually or via model designer tools. VNF or PNF model designer tools can
67 provide the GUI and CLI tools for the VNF or PNF provider to develop the
68 VNF or PNF Package and VNFD or PNFD template.
70 The VNF or PNF package structure is align to the NFV TOSCA protocol,
73 The VNFD or PNFD and VNF or PNF package are all align to the NFV TOSCA
74 protocol, which supports multiple TOSCA template yaml files, and also
75 supports self-defined node or other extensions.
77 VNF or PNF CSAR Package
78 ^^^^^^^^^^^^^^^^^^^^^^
83 TOSCA YAML CSAR file is an archive file using the ZIP file format whose
84 structure complies with the TOSCA Simple Profile YAML v1.2 Specification.
85 The CSAR file may have one of the two following structures:
87 - CSAR containing a TOSCA-Metadata directory, which includes the TOSCA.meta
88 metadata file providing an entry information for processing a CSAR file.
90 - CSAR containing a single yaml (.yml or .yaml) file at the root of the
91 archive. The yaml file is a TOSCA definition template that contains a
92 metadata section with template_name and template_version metadata. This
93 file is the CSAR Entry-Definitions file.
95 VNF Package Structure and Format
96 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
102 :introduced: casablanca
104 The VNF package **MUST** be arranged as a CSAR archive as specified in
105 TOSCA Simple Profile in YAML 1.2.
112 :introduced: casablanca
114 The VNF package provided by a VNF vendor **MAY** be either with
115 TOSCA-Metadata directory (CSAR Option 1) or without TOSCA-Metadata
116 directory (CSAR Option 2) as specified in ETSI GS NFV-SOL004. On-boarding
117 entity (ONAP SDC) must support both options.
119 **Note:** SDC supports only the CSAR Option 1 in Casablanca. The Option 2
120 will be considered in future ONAP releases,
124 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
130 :introduced: casablanca
132 The VNF package **MUST** contain all standard artifacts as specified in
133 ETSI GS NFV-SOL004 including Manifest file, VNFD (or Main TOSCA/YAML
134 based Service Template) and other optional artifacts. CSAR Manifest
135 file as per SOL004 - for example ROOT\\ **MainServiceTemplate.mf**
141 :introduced: casablanca
144 The VNF or PNF package Manifest file **MUST** contain: VNF or PNF package
145 meta-data, a list of all artifacts (both internal and external) entry's
146 including their respected URI's, an algorithm to calculate a digest and
147 a digest result calculated on the content of each artifacts, as specified
148 in ETSI GS NFV-SOL004.
154 :introduced: casablanca
156 The VNF provider **MUST** provide their testing scripts to support
157 testing as specified in ETSI NFV-SOL004 - Testing directory in CSAR
163 :introduced: casablanca
165 The VNF provider **MUST** provide the binaries and images needed to
166 instantiate the VNF (VNF and VNFC images) either as:
168 - Local artifact in CSAR: ROOT\\Artifacts\\ **VNF_Image.bin**
170 - externally referred (by URI) artifact in Manifest file (also may be
171 referred by VNF Descriptor)
173 Note: Currently, ONAP doesn't have the capability of Image management,
174 we upload the image into VIM/VNFM manually.
180 :introduced: casablanca
182 The VNF provider MUST enumerate all of the open source licenses
183 their VNF(s) incorporate. CSAR License directory as per ETSI SOL004.
185 for example ROOT\\Licenses\\ **License_term.txt**
193 The VNF or PNF package Manifest file **MUST** contain: non-mano artifact
194 set with following ONAP public tag:
204 VNF Package Authenticity
205 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
207 Will be added in future releases.
210 VNF Package ONAP Extensions
211 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
213 1. TOACA data type extension tosca.datatypes.nfv.injectFile is used for vCPE
215 2. ONAP extensions for VNF package that is currently proposed for Dublin
216 release is VES extension described below.
221 TOSCA defines a Meta model for defining IT services. This Meta model
222 defines both the structure of a service as well as how to manage it. A
223 Topology Template (also referred to as the topology model of a service)
224 defines the structure of a service. Plans define the process models that
225 are used to create and terminate a service as well as to manage a
226 service during its whole lifetime.
228 A Topology Template consists of a set of Node Templates and Relationship
229 Templates that together define the topology model of a service as a (not
230 necessarily connected) directed graph. A node in this graph is
231 represented by a *Node Template*. A Node Template specifies the
232 occurrence of a Node Type as a component of a service. A *Node Type*
233 defines the properties of such a component (via *Node Type Properties*)
234 and the operations (via *Interfaces*) available to manipulate the
235 component. Node Types are defined separately for reuse purposes and a
236 Node Template references a Node Type and adds usage constraints, such as
237 how many times the component can occur.
241 Figure 1: Structural Elements of Service Template and their Relations
243 TOSCA Modeling Principles & Data Model
244 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
246 This section describing TOSCA modeling principles and data model for
247 NFV, which shall be based on [TOSCA-1.0] and [TOSCA-Simple-Profile-YAML
248 V1.0], or new type based on ETSI NFV requirements, etc.
251 ^^^^^^^^^^^^^^^^^^^^^^^^^
260 :introduced: casablanca
262 The VNF Descriptor (VNFD) provided by VNF vendor **MUST** comply with
263 TOSCA/YAML based Service template for VNF descriptor specified in
266 **Note**: As the ETSI NFV-SOL001 is work in progress the below tables
267 summarizes the TOSCA definitions agreed to be part of current version
268 of NFV profile and that VNFD MUST comply with in ONAP Release 2+
276 :introduced: casablanca
278 The VNFD **MUST** comply with ETSI GS NFV-SOL001 document endorsing
279 the above mentioned NFV Profile and maintaining the gaps with the
280 requirements specified in ETSI GS NFV-IFA011 standard.
287 :introduced: casablanca
289 The VNFD **MAY** include TOSCA/YAML definitions that are not part of
290 NFV Profile. If provided, these definitions MUST comply with TOSCA
291 Simple Profile in YAML v.1.2.
297 :introduced: casablanca
299 A VNFD is a deployment template which describes a VNF in terms of
300 deployment and operational behavior requirements. It contains
301 virtualized resources (nodes) requirements as well as connectivity
302 and interfaces requirements and **MUST** comply with info elements
303 specified in ETSI GS NFV-IFA 011. The main parts of the VNFD are
306 - VNF topology: it is modeled in a cloud agnostic way using virtualized
307 containers and their connectivity. Virtual Deployment Units (VDU)
308 describe the capabilities of the virtualized containers, such as
309 virtual CPU, RAM, disks; their connectivity is modeled with VDU
310 Connection Point Descriptors (VduCpd), Virtual Link Descriptors
311 (VnfVld) and VNF External Connection Point Descriptors
314 - VNF deployment aspects: they are described in one or more
315 deployment flavours, including configurable parameters, instantiation
316 levels, placement constraints (affinity / antiaffinity), minimum and
317 maximum VDU instance numbers. Horizontal scaling is modeled with
318 scaling aspects and the respective scaling levels in the deployment
321 **Note**: The deployment aspects (deployment flavour etc.) are postponed
322 for future ONAP releases.
324 - VNF lifecycle management (LCM) operations: describes the LCM operations
325 supported per deployment flavour, and their input parameters;
326 Note, thatthe actual LCM implementation resides in a different layer,
327 namely referring to additional template artifacts.
333 :introduced: casablanca
335 The following table defines the major TOSCA Types specified in
336 ETSI NFV-SOL001 standard draft. The VNFD provided by a VNF vendor
337 **MUST** comply with the below definitions:
340 .. csv-table:: **TOSCA Definition**
341 :file: TOSCA_descriptor.csv
353 :introduced: casablanca
355 The below table includes the data types used by NFV node and is based
356 on TOSCA/YAML constructs specified in draft GS NFV-SOL 001. The node
357 data definitions/attributes used in VNFD **MUST** comply with the below
360 .. csv-table:: **NFV Data Types**
361 :file: NFV_data_type.csv
370 :introduced: casablanca
372 The below table describes the data types used for LCM configuration
373 and is based on TOSCA constructs specified in draft GS NFV-SOL 001.
374 The LCM configuration data elements used in VNFD **MUST** comply
375 with the below table.
377 .. csv-table:: **LCM Configuration**
378 :file: LCM_config.csv
384 ~~~~~~~~~~~~~~~~~~~~~~~~
386 No artifact type is currently supported in ONAP.
389 ~~~~~~~~~~~~~~~~~~~~~~~~
395 :introduced: casablanca
397 The VNFD provided by VNF vendor may use the below described TOSCA
398 capabilities. An on-boarding entity (ONAP SDC) **MUST** support them.
400 **tosca.capabilities.nfv.VirtualBindable**
402 A node type that includes the VirtualBindable capability indicates
403 that it can be pointed by **tosca.relationships.nfv.VirtualBindsTo**
406 **tosca.capabilities.nfv.VirtualLinkable**
408 A node type that includes the VirtualLinkable capability indicates
409 that it can be pointed by **tosca.relationships.nfv.VirtualLinksTo**
412 **tosca.capabilities.nfv.ExtVirtualLinkable**
414 A node type that includes the ExtVirtualLinkable capability
415 indicates that it can be pointed by
416 **tosca.relationships.nfv.VirtualLinksTo** relationship.
418 **Note**: This capability type is used in Casablanca how it does
419 not exist in the last SOL001 draft
421 **tosca.capabilities.nfv.VirtualCompute** and
422 **tosca.capabilities.nfv.VirtualStorage** includes flavours of VDU
426 ~~~~~~~~~~~~~~~~~~~~~~~~
432 :introduced: casablanca
434 The VNFD provided by VNF vendor may use the below described TOSCA
435 relationships. An on-boarding entity (ONAP SDC) **MUST** support them.
437 **tosca.relationships.nfv.VirtualBindsTo**
439 This relationship type represents an association relationship between
440 VDU and CP node types.
442 **tosca.relationships.nfv.VirtualLinksTo**
444 This relationship type represents an association relationship between
445 the VduCpd's and VirtualLinkDesc node types.
449 ~~~~~~~~~~~~~~~~~~~~~~~~
455 :introduced: casablanca
457 The VNFD provided by VNF vendor may use the below described TOSCA
458 interface types. An on-boarding entity (ONAP SDC) **MUST** support them.
460 **tosca.interfaces.nfv.vnf.lifecycle.Nfv** supports LCM operations
464 ^^^^^^^^^^^^^^^^^^^^^^^^^
476 ~~~~~~~~~~~~~~~~~~~~~~~~
480 ~~~~~~~~~~~~~~~~~~~~~~~~
484 ~~~~~~~~~~~~~~~~~~~~~~~~
488 ~~~~~~~~~~~~~~~~~~~~~~~~
492 ~~~~~~~~~~~~~~~~~~~~~~~~
508 +--------------------------------------------------------------------+
509 | +--------------------------------------------------------------+ |
510 | | tosca\_definitions\_version: tosca\_simple\_yaml\_1\_0 | |
512 | | description: VNFD TOSCA file demo | |
516 | | - TOSCA\_definition\_nfv\_1\_0.yaml | |
518 | | - TOSCA\_definition\_nfv\_ext\_1\_0.yaml | |
520 | | | **node\_types: | |
521 | | tosca.nodes.nfv.VNF.vOpenNAT: | |
522 | | derived\_from:** tosca.nodes.nfv.VNF | |
523 | | | **requirements: | |
524 | | **- **sriov\_plane: | |
525 | | capability:** tosca.capabilities.nfv.VirtualLinkable | |
526 | | | **node:** tosca.nodes.nfv.VnfVirtualLinkDesc | |
527 | | | **relationship:** tosca.relationships.nfv.VirtualLinksTo | |
528 | +--------------------------------------------------------------+ |
529 +====================================================================+
530 +--------------------------------------------------------------------+
536 1. SR-IOV Passthrought
538 Definitions of SRIOV\_Port are necessary if VDU supports SR-IOV. Here is
551 tosca\_name: SRIOV\_Port
555 virtual\_network\_interface\_requirements:
559 support\_mandatory: false
569 description: sriov port
571 layer\_protocol: ipv4
577 capability: virtual\_binding
583 type: tosca.relationships.nfv.VirtualBindsTo
587 node: tosca.nodes.Root
589 type: tosca.nodes.nfv.VduCpd
591 substitution\_mappings:
601 node\_type: tosca.nodes.nfv.VNF.vOpenNAT
606 Definitions of mem\_page\_size as one property shall be added to
607 Properties and set the value to large if one VDU node supports
608 huagepages. Here is an example.
620 tosca\_name: Huge\_pages\_demo
624 mem\_page\_size:large
629 Likewise, we shall add definitions of numa to
630 requested\_additional\_capabilities if we wand VUD nodes to support
631 NUMA. Here is an example.
651 virtual\_mem\_size: 2 GB
653 requested\_additional\_capabilities:
657 support\_mandatory: true
659 requested\_additional\_capability\_name: numa
661 target\_performance\_parameters:
665 hw:numa\_cpus.0: "0,1"
667 hw:numa\_mem.0: "1024"
669 hw:numa\_cpus.1: "2,3,4,5"
671 hw:numa\_mem.1: "1024"
676 Definitions of Hyper-Theading are necessary as one of
677 requested\_additional\_capabilities of one VUD node if that node
678 supports Hyper-Theading. Here is an example.
698 virtual\_mem\_size: 2 GB
700 requested\_additional\_capabilities:
704 support\_mandatory: true
706 requested\_additional\_capability\_name: hyper\_threading
708 target\_performance\_parameters:
710 hw:cpu\_sockets : "2"
712 hw:cpu\_threads : "2"
716 hw:cpu\_threads\_policy: "isolate"
721 Definitions of ovs\_dpdk are necessary as one of
722 requested\_additional\_capabilities of one VUD node if that node
723 supports dpdk. Here is an example.
743 virtual\_mem\_size: 2 GB
745 requested\_additional\_capabilities:
749 support\_mandatory: true
751 requested\_additional\_capability\_name: ovs\_dpdk
753 target\_performance\_parameters:
759 ^^^^^^^^^^^^^^^^^^^^^^^^^
761 **Note: ONAP proprietary extensions in ETSI SOL004 standards for VES support
762 in CSAR package need to be manually loaded in R3 (Casablanca) for VNF and
763 PNFs. Platform support will be developed for this in upcoming releases.**
766 NFV TOSCA Type Definition
767 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
769 tosca.capabilites.nfv.VirtualCompute
770 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
772 This capability is used with the properties specified in ETSI SOL001 draft.
774 tosca.nodes.nfv.VDU.Compute
775 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
777 The NFV Virtualization Deployment Unit (VDU) compute node type
778 represents a VDU entity which it describes the deployment and
779 operational behavior of a VNF component (VNFC), as defined by **[ETSI
782 +-----------------------+-------------------------------+
783 | Shorthand Name | VDU.Compute |
784 +=======================+===============================+
785 | Type Qualified Name | tosca:VDU.Compute |
786 +-----------------------+-------------------------------+
787 | Type URI | tosca.nodes.nfv.VDU.Compute |
788 +-----------------------+-------------------------------+
789 | derived\_from | tosca.nodes.Compute |
790 +-----------------------+-------------------------------+
803 +------------+--------------------+------------+------------------------------+
804 | Name | Type | Constraints| Description |
805 +============+====================+============+==============================+
806 | virtual\ | tosca.\ | | Describes virtual compute |
807 | _compute | capabilities.nfv.\ | | resources capabilities. |
808 | | VirtualCompute | | |
809 +------------+--------------------+------------+------------------------------+
810 | monitoring\| tosca.\ | None | Monitoring parameter, which |
811 | _parameter | capabilities.nfv.\ | | can be tracked for a VNFC |
812 | | Metric | | based on this VDU |
814 | | | | Examples include: |
815 | | | | memory-consumption, |
816 | | | | CPU-utilisation, |
817 | | | | bandwidth-consumption, VNFC |
818 | | | | downtime, etc. |
819 +------------+--------------------+------------+------------------------------+
820 | Virtual\ | tosca.\ | | Defines ability of |
821 | _binding | capabilities.nfv.\ | | VirtualBindable |
822 | | VirtualBindable | | |
824 | | editor note: need | | |
825 | | to create a | | |
826 | | capability type | | |
827 +------------+--------------------+------------+------------------------------+
836 tosca.nodes.nfv.VDU.Compute:
838 derived\_from: tosca.nodes.Compute
856 type: list # explicit index (boot index) not necessary, contrary to IFA011
874 configurable\_properties:
880 type: tosca.datatypes.nfv.VnfcConfigurableProperties
906 type: tosca.capabilities.nfv.VirtualCompute
910 type: tosca.capabilities.nfv.VirtualBindable
912 #monitoring\_parameter:
914 # modeled as ad hoc (named) capabilities in VDU node template
920 # cpu\_load: tosca.capabilities.nfv.Metric
922 # memory\_usage: tosca.capabilities.nfv.Metric
924 host: #Editor note: FFS. How this capabilities should be used in NFV Profile|
926 type: *tosca.capabilities.Container*
928 valid\_source\_types:
929 [*tosca.nodes.SoftwareComponent*]
931 occurrences: [0,UNBOUNDED]
942 #Editor note: FFS. How this capabilities should be used in NFV Profile
944 type: *tosca.capabilities.Scalable*
948 occurrences: [0,UNBOUND]
954 capability: tosca.capabilities.nfv.VirtualStorage
956 relationship: tosca.relationships.nfv.VDU.AttachedTo
958 node: tosca.nodes.nfv.VDU.VirtualStorage
960 occurences: [ 0, UNBOUNDED ]
962 - local\_storage: #For NFV Profile, this requirement is deprecated.
972 type: tosca.artifacts.nfv.SwImage
978 Note: currently not supported.
980 +--------+---------+----------------+------------+------------------------+
981 | Name | Required| Type | Constraints| Description |
982 +========+=========+================+============+========================+
983 | SwImage| Yes | tosca.\ | | Describes the software |
984 | | | artifacts.nfv.\| | image which is directly|
985 | | | SwImage | | realizing this virtual |
987 +--------+---------+----------------+------------+------------------------+
994 tosca.nodes.nfv.VDU.VirtualStorage
995 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
997 The NFV VirtualStorage node type represents a virtual storage entity
998 which it describes the deployment and operational behavior of a virtual
999 storage resources, as defined by **[ETSI NFV IFA011].**
1001 **[editor note]** open issue: should NFV profile use the current storage
1002 model as described in YAML 1.1. Pending on Shitao proposal (see
1003 NFVIFA(17)000110 discussion paper)
1005 **[editor note]** new relationship type as suggested in Matt
1006 presentation. Slide 8. With specific rules of "valid\_target\_type"
1008 +---------------------------+--------------------------------------+
1009 | **Shorthand Name** | VirtualStorage |
1010 +===========================+======================================+
1011 | **Type Qualified Name** | tosca: VirtualStorage |
1012 +---------------------------+--------------------------------------+
1013 | **Type URI** | tosca.nodes.nfv.VDU.VirtualStorage |
1014 +---------------------------+--------------------------------------+
1015 | **derived\_from** | tosca.nodes.Root |
1016 +---------------------------+--------------------------------------+
1018 tosca.artifacts.nfv.SwImage
1019 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1021 +---------------------------+------------------------------------+
1022 | **Shorthand Name** | SwImage |
1023 +===========================+====================================+
1024 | **Type Qualified Name** | tosca:SwImage |
1025 +---------------------------+------------------------------------+
1026 | **Type URI** | tosca.artifacts.nfv.SwImage |
1027 +---------------------------+------------------------------------+
1028 | **derived\_from** | tosca.artifacts.Deployment.Image |
1029 +---------------------------+------------------------------------+
1034 +-----------------+---------+----------+------------+-------------------------+
1035 | Name | Required| Type | Constraints| Description |
1036 +=================+=========+==========+============+=========================+
1037 | name | yes | string | | Name of this software |
1039 +-----------------+---------+----------+------------+-------------------------+
1040 | version | yes | string | | Version of this software|
1042 +-----------------+---------+----------+------------+-------------------------+
1043 | checksum | yes | string | | Checksum of the software|
1044 | | | | | image file |
1045 +-----------------+---------+----------+------------+-------------------------+
1046 | container\ | yes | string | | The container format |
1047 | _format | | | | describes the container |
1048 | | | | | file format in which |
1049 | | | | | software image is |
1050 | | | | | provided. |
1051 +-----------------+---------+----------+------------+-------------------------+
1052 | disk\_format | yes | string | | The disk format of a |
1053 | | | | | software image is the |
1054 | | | | | format of the underlying|
1055 | | | | | disk image |
1056 +-----------------+---------+----------+------------+-------------------------+
1057 | min\_disk | yes | scalar-\ | | The minimal disk size |
1058 | | | unit.size| | requirement for this |
1059 | | | | | software image. |
1060 +-----------------+---------+----------+------------+-------------------------+
1061 | min\_ram | no | scalar-\ | | The minimal RAM |
1062 | | | unit.size| | requirement for this |
1063 | | | | | software image. |
1064 +-----------------+---------+----------+------------+-------------------------+
1065 | Size | yes | scalar-\ | | The size of this |
1066 | | | unit.size| | software image |
1067 +-----------------+---------+----------+------------+-------------------------+
1068 | sw\_image | yes | string | | A reference to the |
1069 | | | | | actual software image |
1070 | | | | | within VNF Package, or |
1072 +-----------------+---------+----------+------------+-------------------------+
1073 | operating\ | no | string | | Identifies the operating|
1074 | _system | | | | system used in the |
1075 | | | | | software image. |
1076 +-----------------+---------+----------+------------+-------------------------+
1077 | supported\ | no | list | | Identifies the |
1078 | _virtualization\| | | | virtualization |
1079 | _enviroment | | | | environments (e.g. |
1080 | | | | | hypervisor) compatible |
1081 | | | | | with this software image|
1082 +-----------------+---------+----------+------------+-------------------------+
1088 .. code-block:: yaml
1090 tosca.artifacts.nfv.SwImage:
1092 derived\_from: tosca.artifacts.Deployment.Image
1094 properties or metadata:
1132 type: scalar-unit.size # Number
1138 type: scalar-unit.size # Number
1144 type: scalar-unit.size # Number
1160 supported\_virtualisation\_environments:
1171 .. |image1| image:: ../Image1.png
1175 .. |image2| image:: ../Image2.png