Ask Your Question

Devstack multinode setup integration with Opendaylight

asked 2015-09-08 08:10:25 -0700

anonymous user


I have a working 2 node openstack setup through devstack. Controller + Compute + Opendaylight -> Compute ->

I have br-int and br-tun on both compute and controller node with their manager set to ODL and each bridge is connected to controller, as evident from ODL GUI.

I am able to create a network.But when I launch a cirros VM, in the logs I see, udhcpc (v1.21.1) started Sending discover... Sending discover... Sending discover...

My DHCP server is running with IP (IP allocated from network created) and corresponding tap device is attached to br-int. when I run ovs-ofctl dump-ports br-int , I do not see any traffic going to dhcp tap though tap device created for VM is sending packets.

After few minutes "lease fail" message is displayed and IP is not allocated to VM.

Can anyone help me out here.

edit retag flag offensive close merge delete


do you see any tunnel created on the controller and compute node ? is this devstack installation is using networking-odl or it's vanilla devstack setup for neutron openvswitch ? Also follow the below thread for more details

Anil Vishnoi ( 2015-09-22 20:14:15 -0700 )edit

Hi Anil, I have a vxlan tunnel created between the 2 nodes and that problem of mine is fixed after I restarted the switch. Now my VMs get the IP address and I am able to ping them, but I am unable to see hosts on ODL GUI. Can you help me what is going wrong? And yes I am using networking-odl.

90.suman ( 2015-09-22 21:58:07 -0700 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-09-23 04:00:07 -0700


In case of OpenStack setup, you won't see host information in the OpenDaylight GUI. OpenDaylight GUI uses hosttracker to learn the host and hosttracker learns it by looking at the packet that it receives from host (e.g Like ARP request broadcast packet). But in case of OpenStack setup, we don't allows any other packet except LLDP to go to the controller because we install very specific rules to control the traffic.And that's why controller don't learn any host, which is expected behavior.

edit flag offensive delete publish link more


Thanks Anil for answer.This somehow explains why I am not able to view the host in dlux GUI. But who decides this "we don't allows any other packet except LLDP to go to the controller"?Is this in terms of flow, if yes then who add this flow(to OVS ?)? Is there any way to see opnstack hosts in dlux?

90.suman ( 2015-09-23 04:30:32 -0700 )edit

It's OVDSB Net-Virt provide that realize the OpenStack services in ODL. It already knows all the details from OpenStack to install all the required flow, so there is no need to send any packet to the controller. And Yes,everything is done through flows. I don't see there is any other way, except you modify the dlux code to fetch these details from OpenStack and show it OR modify net-virt code to send the broadcast packet to controller. Later has performance impact on controller.

Anil Vishnoi ( 2015-09-23 04:49:24 -0700 )edit

DLUX could refer NeutronPort information in data store to get information not just about VMs but computes they're hosted on. Information is all there, just need some code in place to bring it all together.

Vishal Thapar ( 2015-09-24 00:36:34 -0700 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]


Asked: 2015-09-08 08:10:25 -0700

Seen: 544 times

Last updated: Sep 23 '15