Versions Compared

Old Version 142

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version 143

changes.mady.by.user Byung-Woo Jun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Epic

User Story

Description

Guilin Plan?

JIRA

Onboard and Design ETSI SOL004 compliant VNF packages


Executive Summary - Enable a vendor provided ETSI SOL004 compliant VNF package including an ETSI SOL001 VNF Descriptor to  be onboarded into ONAP for composition into an ONAP Service

Business Impact - Enables operators and service providers to use same ETSI compliant VNF packages with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators that are currently using ETSI packages to deploy VNFs

Funding/Financial Impacts - Reduction in operations expense from using industry standard VNF packaging.  Reduction in capital expense from vendors using a single packaging methodology.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2610


Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)

Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)

  • Support SDC AID DM VF descriptor (see the 

    SOL001 VNFD mapping to/from SDC AID DM VFD section)

Yes

SDC-2611 - SDC supports onboarding of the SOL004 VNF Package includes SOL001 VNFD OPEN


Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model

Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model

VNF Mapping:

  • Define a new data type based on the org.openecomp.resource.abstract.nodes.VF with ETSI SOL001 VNF data type attributes.

    • Make the org.openecomp.resource.abstract.nodes.ETSI.VNF a superset of both tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.node.VF
    • During VNF onboarding, SDC copies SOL001 VNF attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VNF
      • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VNF attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
    • SOL001 VNF attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
      • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
      • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
      • For the Honolulu release, it is under consideration
        • to sync up between those modified SOL001 VNF attributes and the vendor ETSI Package attributes 
        • to reflect those modified SOL001 VNF attributes in the orchestration
    • ONAP specific attributes that are inherited from the org.openecomp.resource.abstract.nodes.VF will be filled up by SDC (design time)
      • Those attribute contents will not be mapped back into the SOL001 VNF (reverse mapping). For that case, only the SOL001 VNF corresponding attributes will be copied

VDU Mapping:

  • Make the org.openecomp.resource.abstract.nodes.ETSI.VFC a superset of both tosca.nodes.nfv.Vdu and org.openecomp.resource.abstract.nodes.VFC
  • Note: the org.openecomp.resource.abstract.nodes.VFC represents design-time VFC, not VFC instances
  • During VNF onboarding, SDC copies SOL001 VDU attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VFC
    • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VDU attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
  • SOL001 VDU attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
    • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
    • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
    • For the Honolulu release, it is under consideration
      • to sync up between those modified SOL001 VDU attributes and the vendor ETSI Package attributes 
      • to reflect those modified SOL001 VDU / VFC attributes in the orchestration

VF-Module Mapping:

  • SDC deduces the VF-Module from the SOL001 VNFD Policies>scaling_aspects>properties>aspects
  • Additional VF-Module attributes are deduced as the following table
  • SOL003 Adapter may need to transform the VF-Module back to the SOL001 VNFD policies for the scaling and healing requests from VNFM(s) – not part of Guilin
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2617


Support for editing ETSI v2.7.1 SOL001 VNF Descriptor
  • Support for editing ETSI v2.7.1 SOL001 VNF Descriptor
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2881


Support for using an ETSI v2.7.1 VNF in an ONAP Service

  • Support for using an ETSI v2.7.1 VNF in an ONAP Service

TBD

Support the substitution_mappings in the VNFD.

Currently, the substitution_mappings is not supported by SDC. Lack of this support blocks SOL004 VNF package management and ETSI Catalog Manager:

  • Prior to Frankfurt, as a workaround, the operator creates a dummy VNF without the substitution_mappings or node_types in the MainServiceTemplate.yaml and added a real VNF package with the substitution_mappings and user-define nodes in its Artifacts>DEPLOYMENT>OTHER directory.
  • It is to trick the current SDC onboarding issues because SDC does not check the OTHER directory.
  • In the Frankfurt/Dublin release, SDC was enhanced to support the vendor VNF package in the ETSI_PACKAGE directory.
  • In the Guilin release, the ONBOARDED_PACKAGE directory is changed to the ETSI_PACKAGE.
  • Since SDC Frankfurt/Dublin, we don't have to use the secondary VNF package unnecessary, but we still needs to follow an old way because of lack of substitution_mappings and user-defined node_types.
  • When SDC supports the subscription_mappings user-defined node types, the vendor VNF package does not have to add another VNF package in the Artifacts>DEPLOYMENT>OTHER directory, and the ETSI Catalog Manager will support the VNF package in the ETSI_PACKAGE directory.
    • ETSI Catalog Manager will depend on this SDC support.

Support of the substitution_mappings and user-defined node_types will remove the issues and support ETSI package management and others.

Support of the user-defined node types is handled by another task. This task needs to handle the substitution_mappings only.


For the testing,  use the vgw6.csar


For the Frankfurt release workaround, we added the following to the MainServiceTemplate.yaml, so the ETSI Catalog Manager can retrieve the descriptor_id from the metadata, instead of from the node_type. Once the substitution_mapping is supported by SDC, we don't have to use the descriptor_id in the metadata section.

  • descriptor_id: b1bb0ce7-2222-4fa7-95ed-4840d70a1177
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2957

Onboard ETSI SOL007 compliant Network Service Descriptor packages


Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) to  be onboarded into ONAP for composition into an ONAP Service or deployment using an ETSI compliant NFVO.

  • Support for Cataloging and Preserving the original SOL007 package

  • Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

  • Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO

  • Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

stretch goal

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2801


Support onboarding for Cataloging and Preserving the original SOL007 package

Support onboarding for Cataloging and Preserving the original SOL007 package (Link to ETSI SOL001 v2.7.1)

stretch goal

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2806


Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

  • use SOL001 NSD as SDC AID DM
stretch goal

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2618

Support for deploying a service that contains an ETSI SOL001

Design ETSI SOL007 compliant Network Service Descriptor & packages


Executive Summary - Design, catalog and distribute  an ETSI SOL007 v2.7.1 compliant

Network Service using VF-C as the NFVOSupport for deploying a service that contains an ETSI SOL001 v2

(Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1

compliant

SOL001 Network Service

using VF-C as the NFVO		No

Close this, expect the current SDC distribution is sufficient

Descriptor (NSD) for deployment using an ETSI compliant NFVO.

  • Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using

an external

  • VF-C as the NFVO

  • Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

No

Close this, expect the current SDC distribution is sufficient

Design ETSI SOL007 compliant Network Service Descriptor & packages

Executive Summary - Design, catalog and distribute  an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) for deployment using an ETSI compliant NFVO.

  • Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO

  • Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

Design ETSI SOL001 NSD and generate ETSI SOL007 v2.7.1 compliant Network Service package

  • Create NS and compose NS with its sub components, such as VNFs, VLs, VNF-FG and dependencies between VNFs, etc. - final support scope will be defined
  • Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
    • use SOL001 NSD as SDC AID DM
    • Generate SOL007 NS package

    Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2802

    Note: there is a PoC for this. Soon, the PoC design could be shared as initial input for discussions

    		Design ETSI SOL001 NSD and generate an ETSI SOL001 v2.7.1 compliant Network Service Descriptor & package

    service provider. 

    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2808

    		Support for  deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVOSupport for deploying a service that contains

    2802

    Note: there is a PoC for this. Soon, the PoC design could be shared as initial input for discussions


    		Design ETSI SOL001 NSD and generate an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
    • Wrap the NS package in the Service for VF-C
    		Yes

    Close this, expect the current SDC distribution is sufficient

    		Support for deploying a service that contains an ETSI SOL001 Descriptor & package

    Design ETSI SOL001 NSD and generate ETSI SOL007 v2.7.1 compliant Network Service

    using an external NFVO

    Support for deploying a service that contains an ETSI SOL001 package

    • Create NS and compose NS with its sub components, such as VNFs, VLs, VNF-FG and dependencies between VNFs, etc. - final support scope will be defined
    • Support for mapping of ETSI v2.7.1
    compliant Network Service using an external NFVO
    • Wrap the NS package in the Service for an external NFVO
    		YesClose this, expect the current SDC distribution is sufficient
    • SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
      • use SOL001 NSD as SDC AID DM
    • Generate SOL007 NS package
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2808


    		Support design of Service templates, leveraging NSDsSupport design of Service templates, leveraging NSDsYes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2882


    		Change the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directoryChange the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directoryYes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-3244

    Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor

    Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1)  Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for composition into an ONAP Service or deployment using an ETSI compliant NFVO.

    Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

    Business Markets - All operators and service providers that are developing ETSI compatible Network Services especially for 5G Slicing where each Slice Subnet is associated with a Network Service 

    Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

    Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

    		No

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2803


    		Support for onboarding of the SOL007 v2.7.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP ServiceSupport for onboarding of the SOL007 v2.7.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP ServiceNo

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2811

    Onboard ETSI SOL004 compliant PNF packages

    Executive Summary - Enable a vendor provided ETSI SOL004 compliant PNF package including an ETSI SOL001 PNF Descriptor to  be onboarded into ONAP for composition into an ONAP Service

    Business Impact - Enables operators and service providers to use same ETSI compliant PNF packages with ONAP and existing NFVO. Industry compatibility.

    Business Markets - All operators that are currently using ETSI packages to deploy PNFs

    Funding/Financial Impacts - Reduction in operations expense from using industry standard PNF packaging.  Reduction in capital expense from vendors using a single packaging methodology.

    Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2805


    SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD

    • PNFD onboarding is done and its regression testing will be done
    • SOL004 PNF package onboarding is done in Dublin but support v2.7.1
    • Update onboarding procedure for v2.7.1
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2837



    Support for mapping of ETSI v2.7.1 SOL001 PNF Descriptor into SDC AID Data Model


    		SOL001 PNFD 2.7.1 Mapping to SDC AID DMYes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2836

    Support additional package artifact Indicators for ETSI packages and Non-ETSI packages

    SDC supports additional package artifact types to split ETSI packages from other non-ETSI TOSCA packages

    • SDC (notification) generates additional artifact types
    • SDC client filters on the additional artifact types
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2813


    		SDC Notification supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages

    SDC (Notification) supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages

    • for SOL004 and SOL007 packages, artifact type = ONBOARDED_ETSI_PACKAGE
    • for non-ETSI TOSCA package, artifact type = ONBOARDED_ONAP_PACKAGE
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2814


    		SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages

    SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages

    • for SOL004 and SOL007 packages, filtering for artifact type = ONBOARDED_ETSI_PACKAGE
    • for non-ETSI TOSCA package, filtering for artifact type = ONBOARDED_ONAP_PACKAGE
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2815

    Support ETSI Package Security and validation

    • ONAP supports vendor ETSI Package Security and validation

      • If the vendor package includes signature and certificate, ONAP supports the package security
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2613


    • SOL004 VNF/PNF Package security will be supported by SDC, based on the package signature and certificate
    • ONAP SDC supports the package security
    		Done

    • SOL007 NS Package security will be supported by SDC, based on the package signature and certificate
    • ONAP SDC supports the package security
    		Yes

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2614

    Support of ETSI Package Validation
    		VNF SDK will support ETSI package validation for VNF and NSTBD

    		VNF SDK will support ETSI VNF package pre-onboarding for validationVNF SDK will support ETSI VNF package pre-onboarding for validationTBD

    		VNF SDK will support ETSI NS package pre-onboarding for validationVNF SDK will support ETSI NS package pre-onboarding for validationTBD

    ...

    SOL001 VNFD
    		SDC AID DM VFD
    NameGrammar
    		NameGrammar
    tosca_definitions_version

    string

    (tosca_simple_yaml_1_2)


    		tosca_definitions_version

    string

    (tosca_simple_yaml_1_2)

    descriptionstring
    		descriptionstring
    metadatamap of <string>
    		metadatamap of <string>
    imports

    Single-line grammar

    • <URI_1>
    • <URI_2>

    Multi-line grammar

    • file: <file_URI>
    • repository: <repository name>
    • namespace_uri: <definition_namespace_uri> # deprecated
    • namespace_prefix: <definition_namespace_prefix>

    		importsIdentifies the lower level models (VFC, CP, VL, heat)
    data_types

    <data_type_name>:

    derived_from: <existing_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <datatype_description>

    constraints:

    - <type_constraints>

    properties:

    <property_definitions>


    		data_types

    <data_type_name>:

    derived_from: <existing_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <datatype_description>

    constraints:

    - <type_constraints>

    properties:

    <property_definitions>

    node_types

    <node_type_name>:

    derived_from: <parent_node_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <node_type_description>

    attributes:

    <attribute_definitions>

    properties:

    <property_definitions>

    requirements:

    - <requirement_definitions>

    capabilities:

    <capability_definitions>

    interfaces:

    <interface_definitions>

    artifacts:

    <artifact_definitions>


    		node_types

    <node_type_name>:

    derived_from: <parent_node_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <node_type_description>

    attributes:

    <attribute_definitions>

    properties:

    <property_definitions>

    requirements:

    - <requirement_definitions>

    capabilities:

    <capability_definitions>

    interfaces:

    <interface_definitions>

    artifacts:

    <artifact_definitions>

    topology_template

    topology_template:

    description: <template_description>

    inputs: <input_parameter_list>

    outputs: <output_parameter_list>

    node_templates: <node_template_list>

    relationship_templates: <relationship_template_list>

    groups: <group_definition_list>

    policies:

    - <policy_definition_list>

    workflows: <workflow_list>

    # Optional declaration that exports the Topology Template

    # as an implementation of a Node Type.

    substitution_mappings:

    <substitution_mappings>


    		topology_template

    similar, but the following are different

    • node_templates contents
    • groups
    • workflows
    • description
    		string
    • description
    		string
    • inputs


    • inputs

    <parameter name>:

    type: <parameter_type>

    description: <parameter_description>

    required: <parameter_required>

    default: <parameter_default_value>

    constraints:

    - <parameter_constraints>

    • node_templates

    vnf: tosca.nodes.nfv.Vnf

    vdu: tosca.nodes.nfv.Vdu

    vl: tosca.nodes.nfv.VnfVirtualLink

    vduCp: tosca.nodes.nfv.VduCp

    vduCompute: tosca.nodes.nfv.Vdu.Compute


    • node_templates

    vfc:

        type: org.openecomp.resources.vfc.<>

    vl:

        type: org.openecomp.resources.vl.<>

    cp: 

        type: org.openecomp.resources.cp.<>

    allotted_resource:

        type: org.openecomp.resource.allottedResource.<>





    • workflows
    		<workflow name>

    policies

    • scaling aspect

    tosca.datatypes.nfv.ScalingAspect

    • description
    • properties
      • name:
      • description
      • max_scale_level:
      • step_deltas:

    • groups

    list of VF Modules

    VFModule_Base:

        type: org.openecomp.groups.VfModule

    VFModule_Expansion:

        type: org.openecomp.groups.VfModule




    • policies
    		optional list of policies
    substitution_mappings

    		substitution_mappings
    • node_type


    • node_type

    • capabilities

    <capability_type_name>:

    derived_from: <parent_capability_type_name>

    version: <version_number>

    description: <capability_description>

    properties:

    <property_definitions>

    attributes:

    <attribute_definitions>

    valid_source_types: [ <node type_names> ]


    		capabilities

    <capability_type_name>:

    derived_from: <parent_capability_type_name>

    version: <version_number>

    description: <capability_description>

    properties:

    <property_definitions>

    attributes:

    <attribute_definitions>

    valid_source_types: [ <node type_names> ]

    • requirements


    • requirements

    groupnot defined
    		group

    <group_type_name>:

    derived_from: <parent_group_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <group_description>

    properties:

    <property_definitions>

    members: [ <list_of_valid_member_types> ]

    requirements:

    - <requirement_definitions>

    capabilities:

    policy

    only the Abstract.SecurityGroupRule policy type is defined

    • not sure if we can map this into SDC AID DM

    		policy

    <policy_type_name>:

    derived_from: <parent_policy_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <policy_description>

    properties:

    <property_definitions>

    targets: [ <list_of_valid_target_types> ]

    triggers:

    <list_of_trigger_definitions>

    relationship

    tosca.relationships.nfv.VirtualBindsTo

    tosca.relationships.nfv.AttachesTo


    		relationship

    <relationship_type_name>:

    derived_from: <parent_relationship_type_name>

    version: <version_number>

    metadata:

    <map of string>

    description: <relationship_description>

    properties:

    <property_definitions>

    attributes:

    <attribute_definitions>

    interfaces:

    <interface_definitions>

    valid_target_types: [ <capability_type_names> ]




    		annotation_type

    <annotation_type_name>:

    version: <version_number>

    description: <annotation_type_description>

    properties:

    <property_definitions>




    		annotation

    <annotation_name>:

    type: <annotation_type>

    properties:

    <property_assignments>






    ...