tacker

tacker is creating two networks with the same name

Hello all,

I'm currently try to deploy a NSD with two VNFD, where the VirtualLink are passed from the NSD over substitution_mappings, like the following example:

https://github.com/openstack/tacker/blob/master/samples/tosca-templates/nsd/sample-tosca-nsd.yaml

The problem happens because, we are forcing the network creation with the following parameters:

    VL1:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: {get_input: net1_name}
        vendor: tacker
        ip_version: 4
        cidr: '10.10.0.0/24'
        start_ip: '10.10.0.50'
        end_ip: '10.10.0.200'
        gateway_ip: '10.10.0.1'

following this example: https://specs.openstack.org/openstack/tacker-specs/specs/mitaka/automatic-resource-creation.html

At the end (after the nsd deploy), we have the net1_name network duplicated with the same ip range.

Do you have any workaround to solve this possible issue?

Question information

Language:
English Edit question
Status:
Answered
For:
tacker Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Cong Phuoc Hoang (hoangphuoc) said : 		#1

Can you send me Tacker version and your network descriptor template?

Currently, we recommend you to use master version of Tacker. Thanks

Revision history for this message
Pedro Miguel Correia de Sousa Ambrósio (neoplanet) said : 		#2

Hello all,

Tacker 0.8.1 with Kolla installation.

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: ACS tacker demo

imports:
  - vCPE1
  - vCPE2

topology_template:
  inputs:
    net1_name:
      type: string
      description: Interface name for net1
      default: net1
    net2_name:
      type: string
      description: Interface name for net2
      default: net2
    net3_name:
      type: string
      description: Interface name for net3
      default: net3
    net4_name:
      type: string
      description: Interface name for net4
      default: net4

  node_templates:
    VNF1:
      type: tosca.nodes.nfv.VNF1
      requirements:
        - virtualLink1: VL1
        - virtualLink2: VL2
        - virtualLink3: VL3
        - virtualLink4: VL4

    VNF2:
      type: tosca.nodes.nfv.VNF2
      requirements:
        - virtualLink1: VL1
        - virtualLink2: VL2
        - virtualLink3: VL3
        - virtualLink4: VL4

    VL1:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: {get_input: net1_name}
        vendor: tacker
        ip_version: 4
        cidr: '10.10.0.0/24'
        start_ip: '10.10.0.50'
        end_ip: '10.10.0.200'
        gateway_ip: '10.10.0.1'

    VL2:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: {get_input: net2_name}
        vendor: tacker
        ip_version: 4
        cidr: '10.20.0.0/24'
        start_ip: '10.20.0.50'
        end_ip: '10.20.0.200'
        gateway_ip: '10.20.0.1'

    VL3:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: {get_input: net3_name}
        vendor: tacker
        ip_version: 4
        cidr: '10.30.0.0/24'
        start_ip: '10.30.0.50'
        end_ip: '10.30.0.200'
        gateway_ip: '10.30.0.1'

    VL4:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: {get_input: net4_name}
        vendor: tacker
        ip_version: 4
        cidr: '10.40.0.0/24'
        start_ip: '10.40.0.50'
        end_ip: '10.40.0.200'
        gateway_ip: '10.40.0.1'

Revision history for this message
Cong Phuoc Hoang (hoangphuoc) said : 		#3

I got that issue. I will push the patch for that in few days.

Revision history for this message
Pedro Miguel Correia de Sousa Ambrósio (neoplanet) said : 		#4

Hello Cong,

Thank you, for your help. Let me know when the fix is available

Can you help with this problem?

Provide an answer of your own, or ask Pedro Miguel Correia de Sousa Ambrósio for more information if necessary.

To post a message you must log in.