Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

VM does not boot with IP, Openstack+Opendaylight Integration

Hello there,

I am trying out the juno+helium release for integrating ODL and Openstack integration, Basically following devstack setup for controller and compute from this https://github.com/vthapar/odl-openstack/tree/master/juno.

For single node setup (controller+compute on same node), VM boots up with IP. But with multinode (controller and compute are in different node), VM never picks up the IP (though it boots fine).

Both controller and compute node have single interface eth0, Controller IP: 10.162.103.192 Compute IP: 10.162.103.222 ODL Host IP: 10.162.103.79

ovs-vsctl show at Controller :-

8e7c757a-7a1a-4262-a2ca-08c2656faddf

Manager "tcp:10.162.103.79:6640"
    is_connected: true
Bridge br-int
    Controller "tcp:10.162.103.79:6633"
        is_connected: true
    fail_mode: secure
    Port "tap20e3e5be-68"
        Interface "tap20e3e5be-68"
            type: internal
    Port "qr-b2619e19-bd"
        Interface "qr-b2619e19-bd"
            type: internal
    Port "tap142ddd3a-5f"
        Interface "tap142ddd3a-5f"
    Port "vxlan-10.162.103.222"
        Interface "vxlan-10.162.103.222"
            type: vxlan
            options: {key=flow, local_ip="10.162.103.193", remote_ip="10.162.103.222"}
    Port br-int
        Interface br-int
Bridge br-ex
    Controller "tcp:10.162.103.79:6633"
        is_connected: true
    Port br-ex
        Interface br-ex
            type: internal
    Port "qg-c636fa77-de"
        Interface "qg-c636fa77-de"
            type: internal
ovs_version: "2.0.2"

ovs-vsctl show at Compute :-

1b1177ea-4942-42a0-a17e-4029fc8d8d03

Manager "tcp:10.162.103.79:6640"
    is_connected: true
Bridge br-int
    Controller "tcp:10.162.103.79:6633"
        is_connected: true
    fail_mode: secure
    Port br-int
        Interface br-int
    Port "tap52f84182-d3"
        Interface "tap52f84182-d3"
    Port "vxlan-10.162.103.193"
        Interface "vxlan-10.162.103.193"
            type: vxlan
            options: {key=flow, local_ip="10.162.103.222", remote_ip="10.162.103.193"}
ovs_version: "2.0.2"

Few doubts: - Why there is no br-tun (tunnel between controller and compute, which connects them) as it used to be when we chose openvswitch as mechanism driver ? - Or br-int port vxlan is responsible for that ? - If yes, then how does br-int sends packet to outside world, since it is not mapped to eth0 (interface connects to outside world).

And yes I also did this on both node "ovs-vsctl set OpenvSwitch <uuid_returned> otherconfig:local_ip=<ip-of-your-data-interface> "

Expecting more insight on this integration, Please Help !