[Openstack] Help for replacing linux bridging with OpenVswitch
sinh.lam at verizondigitalmedia.com
sinh.lam at verizondigitalmedia.com
Mon Oct 17 09:57:05 UTC 2016
I’m curious as to why you’re switching from linuxbridge to ovs.
From: Jose Manuel Ferrer Mosteiro
Sent: Monday, October 17, 2016 2:55 AM
To: openstack at lists.openstack.org
Subject: Re: [Openstack] Help for replacing linux bridging with OpenVswitch
I also like openvswitch.
My configuration with mitaka ...
in controller node:
https://github.com/paradigmadigital/ansible-openstack-vcenter/blob/develop/etc_ansible/roles/networking-compute-controller/templates/ml2_conf.ini.j2
https://github.com/paradigmadigital/ansible-openstack-vcenter/blob/develop/etc_ansible/roles/networking-compute-controller/templates/l3_agent.ini.j2
https://github.com/paradigmadigital/ansible-openstack-vcenter/blob/develop/etc_ansible/roles/networking-compute-controller/templates/openvswitch_agent.ini.j2
in compute nodes:
https://github.com/paradigmadigital/ansible-openstack-vcenter/blob/develop/etc_ansible/roles/kvm-hypervisor/templates/ml2_conf.ini.j2
https://github.com/paradigmadigital/ansible-openstack-vcenter/blob/develop/etc_ansible/roles/kvm-hypervisor/templates/openvswitch_agent.ini.j2
I don't know if this is the perfect configuration but works for my.
Have a nice day.
El 2016-10-13 15:53, Gaurav Goyal escribió:
Awaiting your response please!
Can i use management interface as tunneling interface?
Regards
Gaurav Goyal
On Thu, Oct 13, 2016 at 6:52 AM, Gaurav Goyal <er.gauravgoyal at gmail.com> wrote:
Dear Team,
I am working on liberty version of openstack environment.
As per generic liberty openstack guide, i was using linux bridging with vxlan, but want to move to ovs.
I need your help to configure my platform as per OVS requirement.
My architecture is
Node 1 - controller + network + compute1
Node 2 --> compute2
As a classic installation guide , using 2 interfaces on each node
p5p1 -- management
p5p2 -- unnumbered (external)
Please help me to configure ml1_conf.ini and openvswitch_agent.ini file.
I do not find standard doc on openstack page.
Here is my configuration setup following kilo guide
1. [root at OSKVM1 ~]# grep -v "^#" /etc/neutron/plugins/ml2/ml2_conf.ini|grep -v ^$
2. [ml2]
3. type_drivers = flat,vlan,vxlan
4. tenant_network_types = vxlan
5. mechanism_drivers = openvswitch,l2population
6. extension_drivers = port_security
7. [ml2_type_flat]
8. flat_networks = public
9. [ml2_type_vlan]
10. [ml2_type_gre]
11. [ml2_type_vxlan]
12. vni_ranges = 1:1000
13. [ml2_type_geneve]
14. [securitygroup]
15. [root at OSKVM1 ~]# grep -v "^#" /etc/neutron/plugins/ml2/openvswitch_agent.ini|grep -v ^$
16. [ovs]
17. integration_bridge = br-int
18. tunnel_bridge = br-tun
19. local_ip = 10.24.0.4
20. [agent]
21. tunnel_types = vxlan
22. [securitygroup]
23. [root at OSKVM1 ~]# grep -v "^#" /etc/neutron/dhcp_agent.ini|grep -v ^$
24. [DEFAULT]
25. interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
26. dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq
27. enable_isolated_metadata = True
28. dnsmasq_config_file = /etc/neutron/dnsmasq-neutron.conf
29. [AGENT]
30. [root at OSKVM1 ~]# history|grep ovs-vsctl add
31. grep: add: No such file or directory
32. [root at OSKVM1 ~]# history|grep ovs-vsctl
33. 846 ovs-vsctl show
34. 922 ovs-vsctl show
35. 924 ovs-vsctl-show
36. 925 ovs-vsctl show
37. 931 ovs-vsctl show
38. 933 ovs-vsctl add-br br-ex
39. 934 ovs-vsctl add-port br-ex p5p2
40. 935 ovs-vsctl show
[root at OSKVM1 neutron]# ovs-vsctl show
602ca311-4ebe-4773-8d58-00d1a0161294
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "p5p2"
Interface "p5p2"
Bridge br-int
fail_mode: secure
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
Port "tap33501010-4d"
Interface "tap33501010-4d"
type: internal
Bridge br-tun
fail_mode: secure
Port "vxlan-0a180005"
Interface "vxlan-0a180005"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="10.24.0.4", out_key=flow, remote_ip="10.24.0.5"}
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
ovs_version: "2.5.0"
[root at OSKVM1 neutron]# ovs-vsctl list-ports br-ex
p5p2
[root at OSKVM1 neutron]# ovs-vsctl list-ports br-int
patch-tun
tap33501010-4d
[root at OSKVM1 neutron]# ifconfig -a
br-ex: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether a0:36:9f:87:f7:d5 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 12573 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-int: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether f2:fd:fb:5c:96:43 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 8 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-tun: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 6e:06:ab:85:70:46 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
brq7ec081e4-5d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet6 fe80::7e:27ff:fea9:796f prefixlen 64 scopeid 0x20<link>
ether 1e:bc:5d:27:7e:75 txqueuelen 0 (Ethernet)
RX packets 8 bytes 508 (508.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 10.35.0.4 netmask 255.255.255.0 broadcast 10.35.0.255
inet6 fe80::eef4:bbff:fed9:1568 prefixlen 64 scopeid 0x20<link>
ether ec:f4:bb:d9:15:68 txqueuelen 1000 (Ethernet)
RX packets 10757 bytes 724798 (707.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 272 bytes 11652 (11.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ec:f4:bb:d9:15:6a txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em3: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ec:f4:bb:d9:15:6c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x91a80000-91afffff
em4: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ec:f4:bb:d9:15:6d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x91a00000-91a7ffff
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 246932194 bytes 319184736555 (297.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 246932194 bytes 319184736555 (297.2 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ovs-system: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ea:a6:8d:26:10:7e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p5p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.24.0.4 netmask 255.255.255.224 broadcast 10.24.0.31
inet6 fe80::a236:9fff:fe87:f7d4 prefixlen 64 scopeid 0x20<link>
ether a0:36:9f:87:f7:d4 txqueuelen 1000 (Ethernet)
RX packets 69961147 bytes 28103399130 (26.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 66026779 bytes 16612105684 (15.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x91f00000-91ffffff
p5p2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a236:9fff:fe87:f7d5 prefixlen 64 scopeid 0x20<link>
ether a0:36:9f:87:f7:d5 txqueuelen 1000 (Ethernet)
RX packets 10630260 bytes 6850866320 (6.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6506871 bytes 1069537087 (1019.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x91e00000-91efffff
p5p3: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether a0:36:9f:87:f7:d6 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x91d00000-91dfffff
p5p4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether a0:36:9f:87:f7:d7 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x91c00000-91cfffff
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:9a:cc:bf txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:9a:cc:bf txqueuelen 500 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vxlan-2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
ether 1e:bc:5d:27:7e:75 txqueuelen 0 (Ethernet)
RX packets 6 bytes 396 (396.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0
Regards
Gaurav Goyal
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack at lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20161017/8383ed34/attachment.html>
More information about the Openstack
mailing list