You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

[work in progress]

BBS use case aims at using ONAP for the design, creation and activation of the High Speed Internet Access CFS.



The following TOSCA model is Work In Progress.

It is just a starting point for further discussing TOSCA modeling for BBS and it is apparently incomplete.

In case there is any TOSCA validators that we may use, please let us know with a comment.

tosca.nodes.ONT
tosca.nodes.OLT_Connectivity
TOSCA model for HSIA 
tosca_definitions_version: tosca_simple_yaml_1_1

description: Template for the BBS use case's HSIA service

capability_types:
   org.onap.bbs.capabilities.ONT:
      derived_from: onap.capabilities.PNFDevice
      description:  Declaration of being an ONT PNF Device

node_types:

  # Access Connectivity RFS node type
  org.onap.bbs.nodes.AccessConnectivityRFS:
    derived_from: onap.nodes.VNF
    description: Access Connectivity RFS Resource
    properties:
      service_type:
        type: string
        description: Type of service that will be served upon this access connection
        default: HSIA
      olt_name:
        type: string
        description: Name of OLT offering the access connection
      olt_uni_slot:
        type: integer
        constraints:
          - in_range: [ 1, 10 ]
        description: Name of OLT card slot participating in the access connection
      olt_uni_port:
        type: integer
        constraints:
          - in_range: [ 1, 100 ]
        description: Name of OLT port participating in the access connection
      olt_nni_port:
        type: integer
        constraints:
          - in_range: [ 1, 10 ]
        description: Name of uplink OLT port participating in the access connection
      upstream_bandwidth:
        type: integer
        description: Upstream BW of the connection
      downstream_bandwidth:
        type: integer
        description: Downstream BW of the connection        
      fiber_name:
        type: string
        description: Fiber on which the access device will be ranged
      forwarding_mode:
        type: string
        constraints:
          - valid_values: [valid_value1, valid_value2]
        description: Mode of Layer-2 forwarding 
        required: false
      cvlan:
        type: integer
        constraints:
          - in_range: [ 1, 4096 ]
        description: C-VLAN ID of the acess subscriber
        required: false
      svlan:
        type: integer
        constraints:
          - in_range: [ 1, 4096 ]
        description: S-VLAN ID of the acess subscriber
      expected_ont_serial_number:
        type: string
        description: In case of pre-provisioned ONT to specific PON port of OLT 
        required: false
    capabilities:
      pon_termination:
        type: onap.capabilities.Bindable
        description: Capable of terminating an access point connection
        occurrences: [1, 1]

  # Allotted Resource node type
  org.onap.bbs.nodes.TrasportAllottedResource: 
    derived_from:  onap.nodes.Resource
    properties:
      property_to_be_defined:
        type: integer
        description: To be defined
    requirements:
     - transport_network_requirement
         node: org.onap.bbs.nodes.TransportRFS
         capability: onap.capabilities.AllottedResourceProvider
         relationship:  onap.relationships.AllottedBy

  # Allotted Resource Provider node type
  org.onap.bbs.nodes.TransportRFS: 
    derived_from:  onap.nodes.Service
    properties:
      to_be_defined:
        type: integer
        description: To be defined
    capabilities:
      transport_network:
        type: onap.capabilities.AllottedResourceProvider
        valid_source_types: [org.onap.bbs.nodes.TrasportAllottedResource]     

  # PNF device node type
  org.onap.bbs.nodes.ONTPNF:
    derived_from: onap.nodes.PNFDevice
    description:  A PNF Device representing actual ONT
    capabilities:
      pnf_device:
        type: org.onap.bbs.capabilities.ONT

  # ONT RFS node type
  org.onap.bbs.nodes.ONTRFS:
    derived_from: onap.nodes.PNF
    description: ONT RFS Resource
    properties:
      ont_id:
        type: string
        # constraints: 
        #  - pattern: <regular_expression>
        description: ONT ID in the form of vvvONT-ID where vvv are 3 digits representing the vendor
      ont_type:
        type: string
        description: Type of ONT
      ont_port:
        type: integer
        constraints:
          - in_range: [ 1, 10 ]
        description: Name of ONT NNI port connected to the OLT PON port via the ODN network
      ont_name:
        type: string
        required: false
        description: Name of ONT (optional)
      ont_sw_version:
        type: string
        required: false
        description: SW version of ONT
    requirements:
      - access_network_requirement:
          capability: pon_termination
          occurrences: [1, 1]
          relationship: ConnectsTo
      - ont_pnf_device:
          capability: org.onap.bbs.capabilities.ONT
          relationship: onap.relationships.PNFHostedOn

topology_template:

  node_templates:

    # Access Connectivity RFS
    access_newtork:
      type: org.onap.bbs.nodes.AccessConnectivityRFS    
    
    # Access Connectivity's need for transport
    # TODO: how to connect this resource with Access Connectivity RFS
    access_network_needs_transport:
      type: org.onap.bbs.nodes.TrasportAllottedResource       

    # Acutal ONT PNF device
    ont_pnf_device:
      type: org.onap.bbs.nodes.ONTPNF

    # ONT RFS
    ont:
      type: org.onap.bbs.nodes.ONTRFS
      requirements:
        - access_network_requirement:
            node: access_newtork
            capability: pon_termination
  • No labels