Example: TOSCA service template

•This example illustrates a 5G NS contains two VNFs: CU-UP, CU-CP, connected through NsVirtualLink_F1U/E1/F1C/SnU./XnC/NgC/X2C.
•There are may be 1-N of the VnfExtCp of CU-UP and Cu-CP are exposed as the Sap of this NS.
•The flavour_id is "simple".
•DU_1_to_N : a dependency requirement to CU-UP, CU-CP, which indicates that all the instances of CU-UP, CU-CP have to be deployed first before deploy the instances of DU_1_to_N.


Example: 5G NSD example
tosca_definitions_version: tosca_simple_yaml_1_2

# omitted here for brevity

description: 5G RAN simple example

imports:
  - etsi_nfv_sol001_nsd_2_6_1_types.yaml

node_types:
  tosca.5gexample_NS:
    derived_from: tosca.nodes.nfv.NS
    properties:
      descriptor_id:
      version:
      invariant_id:
      flavour_id: 
    
topology_template:
  substitution_mappings:
    node_type: tosca.5gexample_NS
    requirements:
       - virtual_link: [ CU-UP, virtual_link_XYZ ] # the External connection point of CU-UP
       - virtual_link: [ CU-CP, virtual_link_XYZ ] # the External connection point of CU-CP

  node_templates:
    my_5gservice:
      type: tosca.5gexample_NS
      properties:
      interfaces:
    requirements:
       - virtual_link: [ CU-UP, virtual_link_XYZ ] # the External connection point of CU-UP
       - virtual_link: [ CU-CP, virtual_link_XYZ ] # the External connection point of CU-CP


    CU-UP:
      type: tosca.nodes.nfv.5Gexample_VNF1 # the description of this type is described
                                        # in another service template
      properties:
        flavour_id: simple
        vnf_profile:
      requirements:
        - virtual_link_F1U: NsVirtualLink_F1U
        - virtual_link_E1: NsVirtualLink_E1
        - virtual_link_S1U: NsVirtualLink_S1U
        - virtual_link_XnU: NsVirtualLink_XnU
        - virtual_link_NgU: NsVirtualLink_NgU
        - virtual_link_X2U: NsVirtualLink_X2U
        - virtual_link_MnS: NsVirtualLink_MnS

    CU-CP:
      type: tosca.nodes.nfv.5Gexample_VNF1 # the description of this type is described
                                        # in another service template
      properties:
        flavour_id: simple
        vnf_profile:
      requirements:
        - virtual_link_E1: NsVirtualLink_E1
        - virtual_link_F1c: NsVirtualLink_F1c
        - virtual_link_XnC: NsVirtualLink_XnC
        - virtual_link_NgC: NsVirtualLink_NgC
        - virtual_link_X2C: NsVirtualLink_X2C
        - virtual_link_MnS: NsVirtualLink_MnS


    DU_1_to_N:
      type: tosca.nodes.pnf.5gexample_DU # the description of this type is described
                                        # in another service template
      properties:
      requirements:
        - virtual_link_F1C: NsVirtualLink_F1C
        - virtual_link_F1U: NsVirtualLink_F1U
        - virtual_link_MnS: NsVirtualLink_MnS
        - dependency: CU-UP, CP-CP

    NsVirtualLink_F1U:  # 
      type: tosca.nodes.nfv.NsVirtualLink
      properties:
        connectivity_type:
        vl_profile:

    NsVirtualLink_E1:  # 
      type: tosca.nodes.nfv.NsVirtualLink
      properties:
        connectivity_type:
        vl_profile:

    NsVirtualLink_F1C:  # 
      type: tosca.nodes.nfv.NsVirtualLink
      properties:
        connectivity_type:
        vl_profile:

# omitted here for brevity


  • No labels

1 Comment

  1. Michela Bevilacqua

    Mns is modelled as a CP. Is there the intent to model in ONAP the xNF management plane connectivity as a service ?  It could be good to clarify