Ask Your Question
0

Beryllium integration with OpenStack liberty [closed]

asked 2016-03-15 20:47:29 -0700

harsha gravatar image

updated 2016-03-17 19:57:20 -0700

Hi there! I am integrating ODL Be with OpenStack Liberty. ODL was able to create networks but while launching instance i'm getting an error port binding failed. Please help me with the issue and here are further details

ovs-vsctl show on network node

1991b947-85a7-43fe-9610-753e86c0db39
    Manager "tcp:172.16.0.1:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:172.16.0.1:6653"
        Controller "tcp:172.16.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "qg-fba10451-e1"
            Interface "qg-fba10451-e1"
                type: internal
        Port "tapeb022c89-38"
            Interface "tapeb022c89-38"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "tap9511234f-3e"
            Interface "tap9511234f-3e"
                type: internal
        Port "qr-81678afc-6d"
            Interface "qr-81678afc-6d"
                type: internal
        Port "vxlan-192.168.57.4"
            Interface "vxlan-192.168.57.4"
                type: vxlan
                options: {key=flow, local_ip="192.168.57.6", remote_ip="192.168.57.4"}
    Bridge br-ex
        Controller "tcp:172.16.0.1:6633"
            is_connected: true
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth0"
            Interface "eth0"
    ovs_version: "2.4.0"

on compute node

e7a43ca6-3925-4e9a-bed0-f64d6eb73551
    Manager "tcp:172.16.0.1:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:172.16.0.1:6633"
            is_connected: true
        Controller "tcp:172.16.0.1:6653"
            is_connected: true
        fail_mode: secure
        Port "vxlan-192.168.57.6"
            Interface "vxlan-192.168.57.6"
                type: vxlan
                options: {key=flow, local_ip="192.168.57.4", remote_ip="192.168.57.6"}
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "2.4.0"

networks on ODL

{
   "networks" : [ {
      "id" : "1f6b8960-b52a-4349-b528-9f733caa2d21",
      "tenant_id" : "20a06d61fb1b43b7aa067c7867cbe59a",
      "name" : "private",
      "admin_state_up" : true,
      "shared" : false,
      "router:external" : false,
      "provider:network_type" : "vxlan",
      "provider:segmentation_id" : "25",
      "status" : "ACTIVE",
      "segments" : [ ]
   }, {
      "id" : "b5ef05ed-66be-4287-a8f2-8944a9e5af33",
      "tenant_id" : "7d0ba03260174e94b9357437bf2e2962",
      "name" : "public",
      "admin_state_up" : true,
      "shared" : true,
      "router:external" : true,
      "provider:network_type" : "flat",
      "provider:physical_network" : "external",
      "segments" : [ ]
   }

Here is the tail of neutron server log

2016-03-16 08:29:19.584 869 ERROR neutron.plugins.ml2.managers [req-40c54eb8-c405-4831-949a-9dafcdeb344f - - - - -] Mechanism driver opendaylight failed in bind_port
2016-03-16 08:29:19.584 869 ERROR neutron.plugins.ml2.managers Traceback (most recent call last):
2016-03-16 08:29:19.584 869 ERROR neutron.plugins.ml2.managers   File "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py", line 720, in _bind_port_level
2016-03-16 08:29:19.584 869 ERROR neutron.plugins.ml2.managers     driver.obj.bind_port(context)
2016-03-16 08:29:19.584 869 ERROR neutron.plugins.ml2.managers   File "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/opendaylight/driver.py", line 92, in bind_port
2016-03-16 08:29:19.584 869 ERROR neutron.plugins.ml2.managers     self.odl_drv.bind_port(context)

Here is Tail of ODL Log

2016-03-16 09:14:35,402 | WARN  | entLoopGroup-7-6 | ListDeserializer                 | 262 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.7.0.Beryllium | Problem during reading table feature property. Skipping unknown feature property: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null.If more information is needed, set org.opendaylight.openflowjava do DEBUG log level.

[ Updated ]

Karaf logs

karaf.log https://gist.github.com/harsha-hari/a...

karf.log.1 https://gist.github.com/harsha-hari/8...

karaf.log.2 https://gist.github.com/harsha-hari/5...

Neutron Server log

Neutron-server.log https ...

(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by harsha
close date 2016-03-18 09:12:18

Comments

Features installed are odl-ovsdb-openstack.

harsha ( 2016-03-15 20:51:33 -0700 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2016-03-18 03:35:05 -0700

harsha gravatar image

updated 2016-03-18 04:21:42 -0700

@maciekkt Remove any existing networking-odl drivers after stopping neutron-server and install git. Clone the networking-odl repo with git clone https://github.com/openstack/networking-odl -b stable/liberty and install drivers using python setup.py install. Clean ovs database on both compute and network node and then connect it to controller and start neutron-server.

edit flag offensive delete publish link more
0

answered 2016-03-17 17:41:06 -0700

jamoluhrsen gravatar image

thanks for all the details in this question. Unfortunately, your ODL log is from another unrelated bug dealing with table features in ovs 2.4 (I am assuming you have ovs 2.4). You will probably see a flood of those log messages when you first connect your ovs instances to opendaylight. If you let those settle out and then create your openstack compute instance you might get a more relevant log for us to learn from. The other outputs you give (besides trouble in neutron log) seem reasonably correct to me.

edit flag offensive delete publish link more

Comments

@jamoluhrsen Thanks for your time. I have attached complete logs in the updated section of the question. Please help me with the issue. Thank you!

harsha ( 2016-03-17 20:01:08 -0700 )edit

So looking closer I dont see any obvious thing in ODL logs. The neutron logs are clear that the odl driver doesn't have the bind_port attr. I've recently played with Beryllium+Liberty and didn't see this. what releases are you using?

jamoluhrsen ( 2016-03-17 21:23:19 -0700 )edit

@jamoluhrsen i'm also using Liberty and Beryllium(Stable) and OVS version is 2.4.0. networking-odl driver is installed using pip install networking_odl command. Can you please share me the steps and confguration files (Localrc and ODL-OpenStack integration) that you have used?

harsha ( 2016-03-17 22:41:51 -0700 )edit

I have the same issue, my installation is also beryllium (stable) with Liberty (rdo, from packstack on separated control, network and compute nodes), ODL is on separated machine, OVS is also 2.4.0.

maciekkt ( 2016-03-18 02:32:16 -0700 )edit

@jamoluhrsen@maciekkt Finally i was able to integrate Be and Liberty by installing code available in the GitHub. Thank You!

harsha ( 2016-03-18 03:15:52 -0700 )edit

Question Tools

Follow
1 follower

Stats

Asked: 2016-03-15 20:47:29 -0700

Seen: 637 times

Last updated: Mar 18 '16