1 / 5

Network Connectivity Use cases at Carrier / service providers

Network Connectivity Use cases at Carrier / service providers. A vi.vachnis@alcatel-lucent.com CloudBand June 2014. Use cases. As an application architect I’d like to model my application and network topology as follows:. TOSCA Simple profile YAML - Network node type. # continue…

major
Download Presentation

Network Connectivity Use cases at Carrier / service providers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Network Connectivity Use cases at Carrier / service providers Avi.vachnis@alcatel-lucent.com CloudBand June 2014

  2. Use cases As an application architect I’d like to model my application and network topology as follows:

  3. TOSCA Simple profile YAML - Network node type # continue… end_ip: type: string required: false gateway: type: string required: false default: true attributes: segmentation_id: type: string description: VLAN ID to be set in runtime node_types: tosca.nodes.Network: derived_from: tosca.nodes.Root properties: ip_version: type: integer required: true cidr: type: string required: false start_ip: type: string required: false # continue at the right

  4. TOSCA Simple profile YAML - port node type order: • type: integer • required: true • description: The order of the network interface • default: 1  zero based is prefered • constraints: • - greater_than: 0 • attributes: • ip_address: • type: string • relationship_types: • tosca.relationships.LinkedTo: • short_name: link • derived_from: tosca.relationships.DependsOn • valid_targets: [ tosca.capabilities.Linkable] • capability_types: • tosca.capabilities.Linkable: • derived_from: tosca.capabilities.Feature node_types: tosca.nodes.Port: derived_from: tosca.nodes.Root properties: network_id: type: string required: false description: network ID (required if network_name is not provided) network_name: type: string required: false description: network name (required if network_id is not provided)

  5. TOSCA Simple profile YAML - service template example fe_oam_net_port: type: tosca.nodes.Port properties: network_name: oam_network requirements: - link: frontend fe_admin_net_port: type: tosca.nodes.Port properties: network_name: admin_network requirements: - link: frontend be_admin_net_port: type: tosca.nodes.Port properties: network_name: admin_network order: 1 requirements: - link: backend be_data_net_port: type: tosca.nodes.Port properties: network_name: data_network order: 2 requirements: - link: backend db_data_net_port: type: tosca.nodes.Port properties: network_name: data_network requirements: - link: database node_templates: frontend: type: tosca.nodes.Compute properties: # omitted for brevity backend: type: tosca.nodes.Compute properties: # omitted for brevity database: type: tosca.nodes.Compute properties: # omitted for brevity oam_network: type: tosca.nodes.Network properties: ip_version: { get_input: oam_network_ip_version } # 4 cidr: { get_input: oam_network_cidr } start_ip: { get_input: oam_network_start_ip } end_ip: { get_input: oam_network_end_ip } admin_network: type: tosca.nodes.Network properties: ip_version: { get_input: admin_network_ip_version } #  4 dhcp_enabled: { get_input: admin_network_dhcp_enabled } #  false data_network: type: tosca.nodes.Network properties: ip_version: { get_input: data_network_ip_version } #  6 cidr: { get_input: data_network_cidr } #  2001:db8:92a4:0:0:6b3a:180:abcd/64

More Related