Open Stack

Moving this to openstack, as it’s not appropriate
for openstack-dev.

On Jan 9, 2014, at 4:56 PM, Kanthi P <pavuluri.kanthi at gmail.com> wrote:

> Hi,
> 
> I am trying to use vxlans in Havana. I have two nodes, one acting as controller+network node and other as compute node.
> 
> VM's launched have not got the dhcp ip.
> 
> I have compiled openvswitch from openvswitch-2.0.0 tar ball and installed both userspace and kmod rpms.
> 
> modinfo openvswitch
> filename:       /lib/modules/3.9.5-301.fc19.x86_64/kernel/extra/openvswitch/openvswitch.ko
> version:        2.0.0
> license:        GPL
> description:    Open vSwitch switching datapath
> srcversion:     4728289FE3C06CF45730614
> depends:        libcrc32c,gre
> vermagic:       3.9.5-301.fc19.x86_64 SMP mod_unload
> 
> My kernel version is 3.9.5-301.fc19.x86_64.
> 

> I am using ml2 plugin and here is the configuration w.r.t vxlans
> 
> ml2_conf.ini
> type_drivers = vxlan
> vni_ranges = 100:1000
> vxlan_group = 239.10.10.1
> enable_tunneling = True
> local_ip = 21.21.21.11--------------> This is the ip of the interface which is used as data network
> tunnel_types = vxlan
> 
> ovs_neutron_plugin.ini
> tunnel_id_ranges = 200:1000
> 
Can you either paste the exact options in your configuration
file, or even better, put them into paste.openstack.org and
paste a link here? That way we can validate your options
are in the appropriate place.

> Similar configuration exists on compute node as well.
> Below is ovs dump on controller.
> 
> [root at cirros SOURCES]# ovs-vsctl show
> 2cf1fe42-1f7d-48ab-a8e6-fbe033513da2
>     Bridge br-tun
>         Port br-tun
>             Interface br-tun
>                 type: internal
>         Port "vxlan-21.21.21.11"
>             Interface "vxlan-21.21.21.11"
>                 type: vxlan
>                 options: {in_key=flow, local_ip="21.21.21.10", out_key=flow, remote_ip="21.21.21.11"}
>         Port patch-int
>             Interface patch-int
>                 type: patch
>                 options: {peer=patch-tun}
>     Bridge br-int
>         Port br-int
>             Interface br-int
>                 type: internal
>         Port "tap06b8d215-3a"
>             tag: 1
>             Interface "tap06b8d215-3a"
>                 type: internal
>         Port patch-tun
>             Interface patch-tun
>                 type: patch
>                 options: {peer=patch-int}
>     ovs_version: "2.0.0"
> 
> 
> on compute:
> 
> accd3b1f-58b7-46cf-80f9-a4e007b0c47c
>     Bridge br-tun
>         Port "vxlan-21.21.21.10"
>             Interface "vxlan-21.21.21.10"
>                 type: vxlan
>                 options: {in_key=flow, local_ip="21.21.21.11", out_key=flow, remote_ip="21.21.21.10"}
>         Port patch-int
>             Interface patch-int
>                 type: patch
>                 options: {peer=patch-tun}
>         Port br-tun
>             Interface br-tun
>                 type: internal
>     Bridge br-int
>         Port br-int
>             Interface br-int
>                 type: internal
>         Port patch-tun
>             Interface patch-tun
>                 type: patch
>                 options: {peer=patch-int}
>         Port "qvo11538984-b7"
>             tag: 4095
>             Interface "qvo11538984-b7"
>     ovs_version: "2.0.0"
> 
> I see some error/warning logs in openvswitch logs
> 2014-01-09T11:21:56.733Z|00009|bridge|INFO|bridge br-tun: added interface br-tun on port 65534
> 2014-01-09T11:21:56.733Z|00010|bridge|INFO|bridge br-tun: using datapath ID 0000ee4470d36449
> 2014-01-09T11:21:56.733Z|00011|connmgr|INFO|br-tun: added service controller "punix:/var/run/openvswitch/br-tun.mgmt"
> 2014-01-09T11:21:56.811Z|00012|bridge|WARN|could not open network device patch-tun (No such device)
> 2014-01-09T11:21:56.897Z|00013|netdev_vport|ERR|patch-tun: patch type requires valid 'peer' argument
> 2014-01-09T11:21:56.897Z|00014|bridge|WARN|could not configure network device patch-tun (Invalid argument)
> 2014-01-09T11:21:56.982Z|00015|bridge|INFO|bridge br-int: added interface patch-tun on port 1
> 2014-01-09T11:21:57.133Z|00016|bridge|WARN|could not open network device patch-int (No such device)
> 2014-01-09T11:21:57.217Z|00017|netdev_vport|ERR|patch-int: patch type requires valid 'peer' argument
> 2014-01-09T11:21:57.217Z|00018|bridge|WARN|could not configure network device patch-int (Invalid argument)
> 2014-01-09T11:21:57.284Z|00019|bridge|INFO|bridge br-tun: added interface patch-int on port 1
> 2014-01-09T11:21:58.179Z|00020|memory|INFO|peak resident set size grew 268% in last 10.0 seconds, from 9336 kB to 34332 kB
> 2014-01-09T11:21:58.179Z|00021|memory|INFO|ports:4 rules:16
> 2014-01-09T11:21:58.340Z|00022|bridge|WARN|could not open network device vxlan-21.21.21.11 (No such device)
> 2014-01-09T11:21:58.404Z|00023|netdev_vport|ERR|vxlan-21.21.21.11: vxlan type requires valid 'remote_ip' argument
> 2014-01-09T11:21:58.404Z|00024|bridge|WARN|could not configure network device vxlan-21.21.21.11 (Invalid argument)
> 2014-01-09T11:21:58.488Z|00025|bridge|INFO|bridge br-tun: added interface vxlan-21.21.21.11 on port 4
> 
> I also don't see patch-tun, patch-int or vxlan-21.21.21.10 in ifconfig.
> 
> Could you please help me resolve the issue
> 
Can you verify what exactly your problem is here? Is DHCP not working
for VM ports? Or you are just concerned you don’t see the ports where you
think they should be?

Thanks!
Kyle

> Regards,
> Kanthi
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev