Ask Your Question
0

VM does not boot with IP, Openstack+Opendaylight Integration

asked 2015-09-07 20:42:54 -0700

anonymous user

Anonymous

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> other</uuid_returned>config:local_ip=<ip-of-your-data-interface> "</ip-of-your-data-interface>

Expecting more insight on this integration, Please Help !

edit retag flag offensive close merge delete

Comments

Hi , I am also doing the same thing but struck as my VM donot boot with IP . DHCP allocation fails. https://ask.opendaylight.org/question/5235/devstack-multinode-setup-integration-with-opendaylight/ can you help me out here? A;lso what is the use of the last command which you mentioned above?

90.suman ( 2015-09-08 08:18:17 -0700 )edit

Hi, Remove conf.db ~con.db from /etc.openvswitch, Restart openvswitch, ovs-vsctl set OpenvSwitch <uuid_returned> other</uuid_returned>config:local_ip=<ip-data-interface> "</ip-data-interface>, set-manager tcp:cont_ip:6640 on all node, br-int should be created by ODL automatically as well as vxlan port

Samta ( 2015-09-09 05:24:01 -0700 )edit

Thanks for the time. Well I did the same but those bridges - br-int and vxlan port was not created. OVS was clean with manager set. What do you think could have gone wrong? Any help is appreciated.

90.suman ( 2015-09-09 22:39:48 -0700 )edit

Not sure what would have gone wrong, ODL guys might help. But until unless br-int and vxlan ports are not created automatically, there is no point in moving ahead. Though you can try creating by urself and see if ODL recognise that.

Samta ( 2015-09-18 00:09:32 -0700 )edit

I upgraded my ovs to 2.3.1 and then set manager automatically created br-int on both controller and compute node. After creation of a network vxlan port on br-int on both nodes was also created. Though br-ex was not created,is that a problem?

90.suman ( 2015-09-18 00:29:09 -0700 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-09-08 04:19:42 -0700

Samta gravatar image

updated 2015-09-08 04:20:56 -0700

Oops, even I said that I configured "ovs-vsctl set OpenvSwitch <uuid_returned> other</uuid_returned>config:local_ip=<ip-data-interface> "</ip-data-interface> on controller and compute, I did only on compute and assumed that I did in controller.

After performing on both node it worked. Means VM booted with IP.

edit flag offensive delete publish link more

Comments

Like this ovs-vsctl set OpenvSwitch <uuid_returned> 8495f533-5eef-41a6-bc5a-f8e920dfd4c3</uuid_returned>config:local_ip=<ip-data-interface>192.168.0.18</ip-data-interface>

Guruprasad ( 2015-11-03 01:34:45 -0700 )edit

ovs-vsctl set OpenvSwitch 8495f533-5eef-41a6-bc5a-f8e920dfd4c3 config:local_ip=192.168.0.16, when I tried this command it gives error that ovs-vsctl: unknown table "OpenvSwitch"

Guruprasad ( 2015-11-03 01:39:45 -0700 )edit
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2015-09-07 20:42:54 -0700

Seen: 509 times

Last updated: Sep 08 '15