NSD Requirements:
1, VFC project requirement
- VFC project implement ETSI NFVO, which needs to consume the NSD.
- VFC needs to expose NFVO northbound SOL005 interfaces to SO or OSS/BSS/3GPP Management System
JIRA : VFC-635/VFC-648
2, NSD vs ServiceD differences:
Service Descriptor in SDC R3: Service composites many resources in the SDC, including SDC AID resources(vf, extVL, AllottedResource) and R2+ resources.
NSD in VFC: NSD composites VNFD, PNFD, and NSVirtualLink, nested NSD, etc, ETSI NFV resources.
NSD requires to do some limitation in NFV resources composition, not all the SDC resources and substitution_mappings to NS TOSCA node
NSD related work pages:
R3 NetworkServiceModel
ONAP R2+ Design-Time Service DM Input.
PNF resource IM proposal
Network Service Descriptor Model - Based on R2
tosca.nodes.nfv.NS:
derived_from: tosca.nodes.Root
properties:
ns_id:
type: string
required: true
designer:
type: string
required: true
version:
type: string
required: true
name:
type: string
required: true
invariant_id:
type: string
required: true
capabilities:
#monitoring_parameter:
# modelled as ad hoc capabilities in VNF node template
requirements:
- virtual_link:
capability:
tosca.capabilities.nfv.VirtualLinkable
relationship:
tosca.relationships.nfv.VirtualLinksTo
node: tosca.nodes.nfv.NsVirtualLink # tosca.nodes.nfv.VL
occurrences: [ 0, UNBOUNDED ]
refer to https://wiki.onap.org/display/DW/Node+Type #tosca.nodes.nfv.VNF:
tosca.nodes.nfv.PNF:
derived_from: tosca.nodes.Root
properties:
descriptor_id: # instead of pnfd_id
type: string
required: true
provider:
type: string
required: true
version:
type: string
required: true
descriptor_invariant_id:
type: string # GUID
required: true
name:
type: string
required: true
function_description:
type: string
required: true
#geographical_location_info:
# type: TBD
# required: true
requirements:
- virtual_link:
capability: tosca.capabilities.nfv.VirtualLinkable
relationship: tosca.relationships.nfv.VirtualLinksTo
tosca.nodes.nfv.NsVirtualLink:
derived_from:
tosca.nodes.Root
description: node definition of Virtual Links
properties:
provider:
type: string
required: false
version:
type: string
required: true
vl_profile
type: tosca.datatypes.nfv.VlProfile # only covers nin/max bitrate requirements
required: true
connectivity_type:
type: tosca.datatypes.nfv.ConnectivityType
required: true
qos:
type: tosca.datatypes.nfv.Qos
required: false
service_availability:
type: tosca.datatypes.nfv.ServiceAvailability
required: false
capabilities:
VirtualLinkable:
type: tosca.capabilities.nfv.VirtualLinkable
4 Comments
Michela Bevilacqua
VNF node type is already defined in Node Type, remove the node type definition here and refer to.
maopeng zhang
I update it, and add the reference URL.
Thinh Nguyenphu
Would you please add to this page with a reference to original proposal and concept which was presented back in early spring, ONAP R2+ Design-Time Service DM Input.
maopeng zhang
I add it as related pages. Hope it good for you.