IPs not assigned to eth0, eth1 of VNFs

[Rashmi]

Hi,

I am trying to spawn a VNF using tacker using tosca yaml and openwrt image. Though the dashboard shows IP address assigned to the VNF, if i login to the console, i am not able to see the IP address assigned to eth0 or eth1. There is no communication happening between the dhcp and tacker. Tcp dump shows no DNS queries received at the dhcp end.

Even if i use Cirros as the image, result is the same. IP is not being assigned to eth0.

---

Tacker log shows the following :

2017-01-02 23:49:37.696 10033 DEBUG tacker.agent.linux.utils [-] Running command: ['ping', '-c', '3', '-W', '1', '-i', '10', '10.10.10.48'] create_process /usr/lib/python2.7/site-packages/tacker/agent/linux/utils.py:46
2017-01-02 23:50:29.725 10033 ERROR tacker.agent.linux.utils [-] Running Command: ['ping', '-c', '3', '-W', '1', '-i', '10', '10.10.10.48'] Exit code: 1
Stdout: 'PING 10.10.10.48 (10.10.10.48) 56(84) bytes of data.\n\n--- 10.10.10.48 ping statistics ---\n3 packets transmitted, 0 received, 100% packet loss, time 19999ms\n\n'
Stderr: ''
2017-01-02 23:50:29.726 10033 WARNING tacker.vm.monitor_drivers.ping.ping [-] Cannot ping ip address: 10.10.10.48
2017-01-02 23:50:29.727 10033 DEBUG tacker.vm.monitor [-] driver_return failure run_monitor /usr/lib/python2.7/site-packages/tacker/vm/monitor.py:150

--

However, If i spawn a VM manually using the same openwrt image, IPs are assigned to the eth0, eth1 interfaces. When manually spawned, requests are being received by DHCP. These IPs are also reachable from the particular name spaces.

Please help to fix the issue that is occurring with tacker.

[Sridhar Ramaswamy (srics-r)]

what neutron network (VL) are you using for VM spawned with Tacker? Is it the same network that you use when you spawn VM directly (without Tacker) ?

[Rashmi (mgrashmi)]

Hi,

The neutron network (VL) and the image i used for direct VM spawning and tacker are the same.

I am using a multinode setup with separate controller, network and compute nodes. When spawned through tacker, linux bridges are being created in compute node, but dhcp queries are not received in the tap interfaces of network node.

[Bob Haddleton (bob-haddleton)]

What happens if you deploy the equivalent Heat stack without using Tacker?

There is really no reason that Tacker should have anything to do with the problem since it delegates all of the gory details like networking and DHCP to Heat/Nova/Neutron.

[Rashmi (mgrashmi)]

Hi Bob,

Thanks for the input.

I deployed a VM using an equivalent heat stack. It takes the IP address and is working fine. Only when deployed using tacker, the VNFs are not taking IPs.

[Ukesh (ukeshkumar)]

@Rashmi, could you share the tosca yaml template and heat template (can find under stacks page) which generated by tacker ?

[Rashmi (mgrashmi)]

Hi Ukesh,

Please find the templates.

Tosca template:
--------------

template_name: sample-vnfd
description: demo-example

service_properties:
  Id: sample-vnfd
  vendor: tacker
  version: 1

vdus:
  vdu1:
    id: vdu1
    vm_image: Cirros
    instance_type: m1.tiny

    network_interfaces:
      management:
        network: Private1
        management: true

    placement_policy:
      availability_zone: nova

    auto-scaling: noop

----------------------------------------------------------------------------------------------------------

Corresponding heat-stack template:
---------------------------------

description: demo-example
heat_template_version: '2013-05-23'
outputs:
  mgmt_ip-vdu1:
    description: management ip address
    value:
      get_attr: [vdu1-Private1-port, fixed_ips, 0, ip_address]
resources:
  vdu1:
    properties:
      availability_zone: nova
      flavor: m1.tiny
      image: Cirros
      networks:
      - port: {get_resource: vdu1-Private1-port}
    type: OS::Nova::Server
  vdu1-Private1-port:
    properties:
      fixed_ips: []
      network: Private1
      port_security_enabled: false
    type: OS::Neutron::Port

[yong sheng gong (gongysh)]

This is not a tosca template. :)

and you can boot a VM on "Private1" on openstack horizon to check if it works.

[Launchpad Janitor (janitor)]

[Expired for tacker because there has been no activity for 60 days.]