org.openecomp.resource.vl.overlaytunnel:
    derived_from: tosca.nodes.Root
    description: This entity represents abstract overlay tunnel end point.
    properties:
      id:
        type: string
        description: Identifier of the Tunnel Endpoint node.
        required: false
      template_name:
        type: string
        required: false
      version:
        type: string
        required: false
      name:
        type: string
        description: Overlay tunnel name used by for reference by the administrator.
        required: false
      description:
        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

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']
        required: false    
      ac1_protocol_bgp_as:
        type: string
        description: autonomous-system number of ac1, , only required for ebgp protocol
        required: false                    
      ac2_id:
        type: string
        description: id of attachment circuit2, it can be port name or uuid  
        required: false    
      ac2_svlan:
        type: integer
        description: ac2 svlan
        required: false    
      ac2_ip:
        type: string
        description: ip of ac2, only for layer3 vpn, it should contain mask
        required: false    
      ac2_peer_ip:
        type: string
        description: ip of ac2 peer CE tp, only for layer3 vpn, it should contain mask
        required: false    
      ac2_route:
        type: string
        description: route configure of ac2, only for layer3 vpn
        required: false    
      ac2_protocol:
        type: string
        description: routing protocol type of ac2, only for layer3 vpn   
        constraints:
          - valid_values: ['STATIC','OSPF','ISIS','BGP','other']        
        default: 'STATIC'    
        required: false    
      ac2_protocol_bgp_as:
        type: string
        description: autonomous-system number of ac2, , only required for ebgp protocol        
        required: false    
      af_type:
        type: string
        description: address family type
        default: 'ipv4'
        required: false
    requirements:
    - virtualLink:
        capability: tosca.capabilities.network.Linkable
        relationship: tosca.relationships.network.LinksTo
    capabilities:
      virtual_linkable:
        type: tosca.capabilities.network.Linkable

onap.node.wan.Resource:
        derived_from: tosca.nodes.Root
        properties:
            uuid:
                type: string
            name:
                type: string
            version:
                type: string
            label:
                type: list
                entry_schema:
                    type: string   
            type:
                type: string
                description: component type
            paras:
                type: org.openecomp.datatypes.Root
        capabilities:
            - component:
                type: tosca.capabilities.network.Bindable          
        requirements:
            - specifications: 
                node: onap.node.wan.Resourece 
                capabilities: tosca.capabilities.network.Bindable
                relationship: relationships.network.BindsTo    

onap.node.wan.Resource.Connection:
        derived_from: onap.node.wan.Resource
        properties:
        capabilities:     
			- connection:
				type: tosca.capabilities.network.Linkable
        requirements:
            - fcs: 
                node: onap.node.wan.Resource.Fc 
                capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn  
			- links:
				node: onap.node.wan.Resource.Link
				capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn
			- fds:
				node: onap.node.wan.Resource.Fd
				capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn 

onap.node.wan.Resource.Fd:
        derived_from: onap.node.wan.Resource
        description: 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:
            address:
                type: string
                description: ip, or mac, or geo address
        capabilities:
            - domain: 
                type: tosca.capabilities.Attachment
			- node:
				type: tosca.capabilities.Node
        requirements:
            - higherLevelFd:
				node: onap.node.wan.Resource.Fd
                capabilities: tosca.capabilities.Attachment
                relationship: tosca.relationships.AttachesTo    
			- ltps:
				node: onap.node.wan.Resource.Ltp
                capabilities:  tosca.capabilities.Attachment
                relationship: tosca.relationships.AttachesTo    

onap.node.wan.Resource.Fc:
        description: The ForwardingConstruct (FC) class models enabled constrained potential for forwarding between two or more interfaces at a particular specific layerProtocol. 
        derived_from: onap.node.wan.Resource
        properties: 
        capabilities:
			- node:
				type: tosca.capabilities.Node
        requirements: 
            - endPoint:
                node: onap.node.wan.Resource.FcPort    
				capabilities: tosca.capabilities.network.Bindable
                relationship: relationships.network.BindsTo 
            - fcRoute:
                node: onap.node.wan.Resource.FcRoute
				capabilities: tosca.capabilities.network.Bindable
                relationship: relationships.network.BindsTo 
			- lowerLevelFc:
				node: onap.node.wan.Resource.Fc 
                capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn  

onap.node.wan.Resource.FcPort:
        description: Fowarding Construct Point. The association of the FC to interfaces is made via FcPorts. The FcPort class models the access to the FC function.  
        derived_from: onap.node.wan.Resource
        properties:
            address:
                type: string
                description: ip, or mac    
            FcPortDirection:
                type: string
			role:
				type: string
				constraints:
                    - valid_values: ['working','protection','protected','symmetric','hub', 'spoke', 'leaf', 'root']   
        capabilities:
        requirements:
            - fd:
				node: onap.node.wan.Resource.Ltp
                capabilities:  tosca.capabilities.Attachment
                relationship: tosca.relationships.AttachesTo
            - ltp:
				node: onap.node.wan.Resource.Ltp
                capabilities: tosca.capabilities.Endpoint
                relationship: tosca.relationships.ConnectsTo

onap.node.wan.Resource.LinkPort:
        description: The association of the Link to LTPs is made via LinkPort. The LinkPort class models the access to the Link function.  
        derived_from: onap.node.wan.Resource
        properties:
            role:
                type: 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. 
                constraints:
                    - valid_values: ['symmetric','hub', 'spoke', 'leaf', 'root']   
        capabilities:
        requirements:
            - ltp:
                node: onap.node.wan.Resource.Ltp
                capabilities: tosca.capabilities.Endpoint
                relationship: tosca.relationships.ConnectsTo

onap.node.wan.Resource.Ltp:
        description: The Logical Termination Point (LTP) class encapsulates the termination and adaptation functions of one or more transport layers represented by instances of LayerProtocol.
        derived_from: onap.node.wan.Resource
        properties:
            physicalPortReference:
                type: string
            ltpDirection:
                type: string
        capabilities:
            - endPoint:
                type: tosca.capabilities.Endpoint  
        requirements:
            - fd:
				node: onap.node.wan.Resource.Fd
                capabilities:  tosca.capabilities.Attachment
                relationship: tosca.relationships.AttachesTo  
            - serverLtp:
                node: onap.node.wan.Resource.Ltp
				capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn  
            - lp:
                node: onap.node.wan.Resource.LayerProtocol
                capabilities: tosca.capabilities.network.Bindable
                relationship: relationships.network.BindsTo 

onap.node.wan.Resource.LayerProtocol:
        description: The 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:
                type: string
            address:
                type: string

onap.node.wan.Resource.Link:
        description: The Link class models effective adjacency between two or more ForwardingDomains (FD). 
        derived_from: onap.node.wan.Resource
        properties:
		capabilities:
			- node:
				type: tosca.capabilities.Node
        requirements: 
            - fc:
                node: onap.node.wan.Resource.Fc
				capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn  
            - endPoint:
                node: onap.node.wan.Resource.LinkPort    
                capabilities: tosca.capabilities.Endpoint
                relationship: tosca.relationships.ConnectsTo

onap.node.wan.Resource.FcRoute:
        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:   
        requirements:
            - link:
                node: onap.node.wan.Resource.Link
				capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn
            - subFc:
                node: onap.node.wan.Resource.Fc
				capabilities: tosca.capabilities.Node
                relationship: tosca.relationships.DependsOn