WAN R2
Same with R1
Panel |
---|
|
Code Block |
---|
title | onaporg.openecomp.datatyperesource.wanvl.UserDefineoverlaytunnel |
---|
collapse | true |
---|
| onaporg.openecomp.datatyperesource.wanvl.UserDefineoverlaytunnel:
derived_from: tosca.datatypesnodes.Root
propertiesdescription:
This entity represents abstract overlay tunnel end point.
nameproperties:
id:
type: string
description: Identifier of the Tunnel Endpoint node.
description: resful uri supported
required: false
template_name:
required type: truestring
required: false
valueversion:
type: string
typerequired: stringfalse
name:
type: string
required: false |
|
Panel |
---|
|
Code Block |
---|
title | onap.capability.wan.host |
---|
collapse | true |
---|
| onap.capability.wan.host:
description: Overlay tunnel name derived_from: tosca.capabilities.Node | Code Block |
---|
title | onap.capability.wan.component |
---|
collapse | true |
---|
| onap.capability.wan.component:
used by for reference by the administrator.
required: false
derived_from: tosca.capabilities.Root | Code Block |
---|
title | onap.capability.wan.dependable |
---|
collapse | true |
---|
| onap.capability.wan.dependabledescription:
derived_from: tosca.capabilities.Root |
Code Block |
---|
firstline | 1 |
---|
title | tosca.capabilities.wan.VirtualLinkable |
---|
linenumbers | true |
---|
collapse | true |
---|
| tosca.capabilities.wan.VirtualLinkable:
derived_from: tosca.capabilities.Root |
|
Panel |
---|
|
type: string
description: Additional comments/information about overlay tunnel.
required: false
tunnelType:
type: string
constraints:
- valid_values: ['L3-DCI','L2-DCI']
description: type defines if the overlay tunnel is L3-DCI tunnel or L2-DCI tunnel.
required: true
site1_id:
type: string
description: Identifier of first DCI overlay tunnel endpoint. This could be IP address of domain controller.
required: true
site1_description:
type: string
description: Additional comments/information about overlay tunnel. Description can also be used to identify domain controller.
required: false
site1_networkName:
type: string
description: Name of the network that is being associated with overlay tunnel.
required: true
site1_routerId:
type: string
description: Identifier of router connected to L3 tunnel end point, while configuring L3-DCI tunnel.
required: false
site1_importRT1:
type: string
description: List of Route targets imported by the local router.
required: false
site1_exportRT1:
type: string
description: List of Route targets exported by the local router.
required: false
site1_vni:
type: integer
description: VXLAN ID
required: false
site1_fireWallEnable:
type: boolean
required: false
description: Identifies if a firewall exists in the path of overlay tunnel.
default: false
site1_fireWallId:
type: string
description: Identifier of Firewall that is in overlay tunnel path
required: false
site1_localNetworkAll:
type: boolean
description: Identifies whether all the local networks associate with the tunnel or not.
required: false
default: 'false'
site2_id:
type: string
description: Identifier of second DCI overlay tunnel endpoint. This could be IP address of domain controller.
required: true
site2_description:
type: string
description: Additional comments/information about overlay tunnel. Description can also be used to identify domain controller.
required: false
site2_networkName:
type: string
description: Name of the network that is being associated with overlay tunnel.
required: true
site2_routerId:
type: string
description: Identifier of router connected to L3 tunnel end point, while configuring L3-DCI tunnel.
required: false
site2_importRT1:
type: string
description: List of Route targets imported by the local router.
required: false
site2_exportRT1:
type: string
description: List of Route targets exported by the local router.
required: false
site2_vni:
type: integer
description: VXLAN ID
required: false
site2_fireWallEnable:
type: boolean
required: false
description: Identifies if a firewall exists in the path of overlay tunnel.
default: false
site2_fireWallId:
type: string
description: Identifier of Firewall that is in overlay tunnel path
required: false
site2_localNetworkAll:
type: boolean
description: Identifies whether all the local networks associate with the tunnel or not.
required: false
default: 'false'
requirements:
- virtualLink:
capability: tosca.capabilities.network.Linkable
relationship: tosca.relationships.network.LinksTo
capabilities:
virtual_linkable:
type: tosca.capabilities.network.Linkable |
Code Block |
---|
title | org.openecomp.resource.vl.underlayvpn |
---|
collapse | true |
---|
| org.openecomp.resource.vl.underlayvpn:
derived_from: tosca.nodes.Root
description: undelay vpn type definitions
properties:
id:
type: string
required: false
template_name:
type: string
required: false
version:
type: string
required: false
vendor:
type: string
required: false
template_author:
type: string
required: false
name:
type: string
required: false
description:
type: string
required: false
serviceType:
type: string
description: type of VPN service
required: false
default: 'l3vpn_sptn'
topology:
type: string
description: type of VPN topology
constraints:
- valid_values: ['full-mesh','point_to_multipoint','point_to_point','singlePoint','hubspoke','hubspoke_via_hubce','hubspoke_disjoint','ADD_DROP_Z']
required: false
default: 'full-mesh'
technology:
type: string
description: type of VPN technology
constraints:
- valid_values: ['mpls','rosen multivpn','vxlan overlay l3vpn','eth over sdh','vlan']
required: false
default: 'mpls'
site1_name:
type: string
description: name of first site
required: false
site2_name:
type: string
description: name of second site
required: false
sna1_name:
type: string
description: name of site network accesses associated with the site1
required: false
sna2_name:
type: string
description: name of site network accesses associated with the site2
required: false
pe1_id:
type: string
description: id of provider edge1, it can be name or ip or uuid
required: false
pe2_id:
type: string
description: id of provider edge2, it can be name or ip or uuid
required: false
ac1_id:
type: string
description: id of attachment circuit1, it can be port name or uuid
required: false
ac1_svlan:
type: integer
description: ac1 svlan
required: false
ac1_ip:
type: string
description: ip of ac1, only for layer3 vpn, it should contain mask
required: false
ac1_peer_ip:
type: string
description: ip of ac1 peer CE tp, only for layer3 vpn, it should contain mask
required: false
ac1_route:
type: string
description: route configure of ac1, only for layer3 vpn
required: false
ac1_protocol:
type: string
description: routing protocol type of ac1, only for layer3 vpn
constraints:
- valid_values: ['STATIC','OSPF','ISIS','BGP','other'] | Code Block |
---|
title | onap.relationship.wan.HostOn |
---|
collapse | true |
---|
| onap.relationship.wan.HostOn:
description: >-
required: false The relationship specifies what Node the Endpoint is hosted on.
ac1_protocol_bgp_as:
type: string
derived_from: tosca.relationships.Root
valid_target_types: [onap.capability.wan.host] | Code Block |
---|
title | onap.relationship.wan.Contains |
---|
collapse | true |
---|
| onap.relationship.wan.Contains:
description: autonomous-system number of ac1, , only required for ebgp protocol
required: false description: >-
The relationship
specifies what component is contained. ac2_id:
derived_fromtype: tosca.relationships.Rootstring
valid_target_typesdescription: [onap.capability.wan.component] | Code Block |
---|
title | onap.relationship.wan.DependsOn |
---|
collapse | true |
---|
| onap.relationship.wan.DependsOn:
description: >-id of attachment circuit2, it can be port name or uuid
required: false The relationship
specifies what is depended on. ac2_svlan:
derived_fromtype: tosca.relationships.Rootinteger
valid_target_types: [onap.capability.wan.dependable] | Code Block |
---|
firstline | 1 |
---|
title | tosca.relationships.wan.VirtualLinksTo |
---|
linenumbers | true |
---|
collapse | true |
---|
| tosca.relationships.wan.VirtualLinksTo:description: ac2 svlan
required: false
derived_from: tosca.relationships.DependsOn ac2_ip:
type: string
valid_target_types: [ tosca.capabilities.wan.VirtualLinkable ] |
|
Panel |
---|
|
Code Block |
---|
title | onap.node.wan.Component |
---|
collapse | true |
---|
| onap.node.wan.Component:
derived_from: tosca.nodes.Root description: ip of ac2, only for layer3 vpn, it should contain mask
properties:required: false
ac2_peer_ip:
uuidtype: string
description: ip of ac2 peer CE tp, only for type: string
layer3 vpn, it should contain mask
name:
required: false
ac2_route:
type: string
description: route configure of version:
ac2, only for layer3 vpn
required: false type: string
ac2_protocol:
description:
type: string
description: routing protocol type: stringof ac2, only for
layer3 vpn
typeconstraints:
type: string
- valid_values: ['STATIC','OSPF','ISIS','BGP','other']
descriptiondefault: component'STATIC' type
parasrequired:
false
type: list
ac2_protocol_bgp_as:
type: string
entry_schemadescription:
autonomous-system number of ac2, , only required for ebgp protocol type: onap.datatype.wan.UserDefine
capabilities:
required: false component:
af_type:
type: onap.capability.wan.componentstring
description: address family type
requirementsdefault: 'ipv4'
required: false
- configurationrequirements:
- virtualLink:
nodecapability: onaptosca.nodecapabilities.wannetwork.Component Linkable
capabilityrelationship: onaptosca.capabilityrelationships.wannetwork.componentLinksTo
capabilities:
virtual_linkable:
relationshiptype: onaptosca.relationshipcapabilities.wan.Contains network.Linkable |
|
WAN R3+
Panel |
---|
|
Code Block |
---|
title | onap.node.wan.Resource |
---|
collapse | true |
---|
| onap.node.wan.Resource:
derived_from: tosca.nodes.Root
properties:
uuid:
type: string
name:
type: string
version:
type: string
descriptionlabel:
type: stringlist
typeentry_schema:
type: string
type:
description: component type
parastype: string
typedescription: listcomponent type
entry_schemaparas:
type: onaporg.datatypeopenecomp.wan.UserDefine datatypes.Root
capabilities:
- component:
type: onaptosca.capabilitycapabilities.wannetwork.componentBindable
requirements:
- configurationspecifications:
node: onap.node.wan.ComponentResourece
capabilitycapabilities: onaptosca.capabilitycapabilities.wannetwork.componentBindable
relationship: onaprelationships.relationshipnetwork.wan.ContainsBindsTo |
Code Block |
---|
title | onap.node.wan.Resource.NodeConnection |
---|
collapse | true |
---|
| onap.node.wan.Resource.NodeConnection:
derived_from: onap.node.wan.Resource
descriptionproperties:
Node resource, it could be site or necapabilities: or anything else which can be a host for endPoint
- connection:
type: tosca.capabilities.network.Linkable
propertiesrequirements:
address- fcs:
typenode: stringonap.node.wan.Resource.Fc
descriptioncapabilities: ip, or mac, or geo address
tosca.capabilities.Node
vendorrelationship:
tosca.relationships.DependsOn type: string
- links:
node: onap.node.wan.Resource.Link
capabilities: tosca.capabilities.Node
capabilities:
relationship: host:
typetosca.relationships.DependsOn
- fds:
node: onap.capabilitynode.wan.Resource.host
Fd
capabilities: tosca.capabilities.Node
requirements:
relationship: tosca.relationships.DependsOn |
Code Block |
---|
title | onap.node.wan.Resource.Fd |
---|
collapse | true |
---|
| onap.node.wan.Resource.Fd:
parentNode:
derived_from: onap.node.wan.Resource
nodedescription: onap.node.wan.Component.Node
capability: onap.capability.wan.host
relationship: onap.relationship.wan.HostOn | Code Block |
---|
title | onap.node.wan.Component.FC |
---|
collapse | true |
---|
| onap.node.wan.Component.FC The Forwarding Domain (FD) class models the topological component that represents a forwarding capability that provides the opportunity to enable forwarding (of specific transport characteristic information at one or more protocol layers) between points.
properties:
description: The ForwardingConstruct (FC) class models enabled constrained potential for forwarding between two or more interfaces at a particular specific layerProtocol. address:
type: string
derived_from: onap.node.wan.Component
description: ip, properties:
or mac, or geo address
topologycapabilities:
- domain:
type: string
type: constraints:tosca.capabilities.Attachment
- node:
type: tosca.capabilities.Node
requirements:
- valid_values: ['hub-spoke','fullmesh','p2p']higherLevelFd:
node: onap.node.wan.Resource.Fd
tenant:capabilities: tosca.capabilities.Attachment
typerelationship: string
tosca.relationships.AttachesTo creator:
- ltps:
node: onap.node.wan.Resource.Ltp
typecapabilities: stringtosca.capabilities.Attachment
description:relationship: tosca.relationships.AttachesTo |
Code Block |
---|
title | onap.node.wan.Resource.Fc |
---|
collapse | true |
---|
| onap.node.wan.Resource.Fc:creator
capabilitiesdescription:
The ForwardingConstruct (FC) class models enabled constrained potential for forwarding between two dependable:
or more interfaces at a particular specific layerProtocol.
typederived_from: onap.capabilitynode.wan.dependableResource
virtual_linkable:properties:
capabilities:
- node:
type: tosca.capabilities.wan.VirtualLinkableNode
requirements:
- endPoint:
node: onap.node.wan.ComponentResource.FCPointFcPort
capability capabilities: tosca.capabilities.network.EndpointBindable
relationship: toscarelationships.relationshipsnetwork.ConnectsToBindsTo
- subFcfcRoute:
node: onap.node.wan.ComponentResource.FC
capability: onap.capability.wan.dependableFcRoute
capabilities: tosca.capabilities.network.Bindable
relationship: onaprelationships.relationship.wan.DependsOn
- fcRoute:
network.BindsTo
- lowerLevelFc:
node: onap.node.wan.ComponentResource.FCRouteFc
capabilitycapabilities: onaptosca.capabilitycapabilities.wan.dependableNode
relationship: onaptosca.relationship.wanrelationships.DependsOn
|
Code Block |
---|
title | onap.node.wan.Resource.FCPointFcPort |
---|
collapse | true |
---|
| onap.node.wan.Resource.FCPointFcPort:
description: Fowarding Construct Point. The association of the FC to interfaces is made via FCPointsFcPorts. The FCPointFcPort class models the access to the FC function.
derived_from: onap.node.wan.Resource
properties:
address:
propertiestype: string
interface: description: ip, or mac
FcPortDirection:
type: string
address:
type: string
role:
type: string
constraints:
type: string
- valid_values: ['working','protection','protected','symmetric','hub', 'spoke', 'leaf', 'root']
description: ip, or mac capabilities:
hub-spoke-rolerequirements:
type: string- fd:
node: onap.node.wan.Resource.Ltp
descriptioncapabilities: role of the FC Point tosca.capabilities.Attachment
constraints:
relationship: tosca.relationships.AttachesTo
- valid_values: ['hub','spoke']ltp:
node: onap.node.wan.Resource.Ltp
requiredcapabilities: falsetosca.capabilities.Endpoint
capabilities:
endPointrelationship: tosca.relationships.ConnectsTo |
Code Block |
---|
title | onap.node.wan.Resource.LinkPort |
---|
collapse | true |
---|
| onap.node.wan.Resource.LinkPort:
description: The association of the Link to LTPs type: tosca.capabilities.Endpoint
requirements:
node:is made via LinkPort. The LinkPort class models the access to the Link function.
nodederived_from: onap.node.wan.Component.NodeResource
capability: onap.capability.wan.host
properties:
role:
relationship: onap.relationship.wan.HostOn | Code Block |
---|
title | onap.node.wan.Resource.XCPoint |
---|
collapse | true |
---|
| onap.node.wan.Resource.XCPoint:
descriptiontype: Exchange Connection Point. Interfaces involved in exchange in a node
derived_from: onap.node.wan.Resource
properties:
hub-spoke-role:string
description: Each LinkPort of the Link has a role (e.g., symmetric, hub, spoke, leaf, root) in the context of the Link with respect to the Link capability.
typeconstraints:
string
description: role of the FC Point
- valid_values: ['symmetric','hub', 'spoke', 'leaf', 'root']
constraintscapabilities:
requirements:
- valid_values: ['hub','spoke']ltp:
requirednode: falseonap.node.wan.Resource.Ltp
interface:capabilities: tosca.capabilities.Endpoint
type: relationship: tosca.relationships.ConnectsTo |
Code Block |
---|
title | onap.node.wan.Resource.Ltp |
---|
collapse | true |
---|
| onap.node.wan.Resource.Ltp: string
capabilitiesdescription:
The Logical Termination Point (LTP) class encapsulates the termination and endPoint:
adaptation functions of one or more transport layers represented by instances of LayerProtocol.
typederived_from: toscaonap.node.capabilitieswan.EndpointResource
requirementsproperties:
nodephysicalPortReference:
node: onap.node.wan.Component.Nodetype: string
ltpDirection:
capabilitytype: onap.capability.wan.host
string
capabilities:
relationship: onap.relationship.wan.HostOn | Code Block |
---|
title | onap.node.wan.Resource.XC |
---|
collapse | true |
---|
| onap.node.wan.Resource.XC:
- endPoint:
description type: Exchange Connection. The exchange relationship within a node describes how the interfaces within the node are linked.
tosca.capabilities.Endpoint
requirements:
derived_from- fd:
node: onap.node.wan.Resource.Fd
properties:
requirementscapabilities: tosca.capabilities.Attachment
- endPort:
relationship: tosca.relationships.AttachesTo
node: onap.node.wan.Component.XcPoint - serverLtp:
capability node: onap.node.wan.Resource.Ltp
capabilities: tosca.capabilities.EndpointNode
relationship: tosca.relationships.ConnectsToDependsOn
description: all endPorts can access each other
- ne- lp:
node: onap.node.wan.Component.Node Resource.LayerProtocol
capabilitycapabilities: onaptosca.capabilitycapabilities.wannetwork.hostBindable
relationship: onaprelationships.relationship.wan.HostOnnetwork.BindsTo |
Code Block |
---|
title | onap.node.wan.Resource.LinkConnectionLayerProtocol |
---|
collapse | true |
---|
| onap.node.wan.Resource.LinkConnectionLayerProtocol:
description: The exchange relationship between nodes, describing how the interfaces between nodes are linked. The link can depend on the FC of the service layer projection of an LTP into each transport layer is represented by a LayerProtocol (LP) instance. A LayerProtocol instance can be
used for controlling termination and monitoring functionality.
derived_from: onap.node.wan.Resource
properties:
layerProtocolName:
propertiestype: string
topology address:
type: string |
Code Block |
---|
title | onap.node.wan.Resource.Link |
---|
collapse | true |
---|
| onap.node.wan.Resource.Link:
constraints:
description: The Link class models effective adjacency between two or more ForwardingDomains (FD).
- validderived_values: ['hub-spoke','fullmesh','p2p']from: onap.node.wan.Resource
properties:
capabilities:
- node:
type: tosca.capabilities.Node
requirements:
- fc:
node: onap.node.wan.ComponentResource.FC
capability: onap.capability.wan.dependableFc
capabilities: tosca.capabilities.Node
relationship: onaptosca.relationship.wan.DependsOnrelationships.DependsOn
- endPoint:
node: onap.node.wan.ComponentResource.XcPointLinkPort
capabilitycapabilities: tosca.capabilities.Endpoint
relationship: tosca.relationships.ConnectsTo |
Code Block |
---|
title | onap.node.wan.Resource.FCRouteFcRoute |
---|
collapse | true |
---|
| onap.node.wan.Resource.FCRouteFcRoute:
description: The routing relationships within FC are described, including routing between sub FC (interdomain links), and links between network elements and network elements.
derived_from: onap.node.wan.Resource
properties:
capabilities:
dependable:
type: onap.capability.wan.dependable
requirements:
- xclink:
node: onap.node.wan.ComponentResource.XC
capability: onap.capability.wan.componentLink
capabilities: tosca.capabilities.Node
relationship: onaptosca.relationship.wan.Contains relationships.DependsOn
- lcsubFc:
node: onap.node.wan.ComponentResource.LinkConnection
capability: onap.capability.wan.componentFc
capabilities: tosca.capabilities.Node
relationship: onaptosca.relationship.wan.Contains relationships.DependsOn |
|
R3 Class Explain
Wan Connection IM proposal