Re: [ovs-discuss] Fwd: Help for replacing linux bridging with OpenVswitch

2016-10-13 Thread Gaurav Goyal 
Thanks Ben!

Initially i had done some wrong configuration using vxlan.

Now i am using gre for tunneling. But i could still see vxlan ports in
ovs-vsctl show output.

Is there any option can can read current configuration files and remove the
non required configuration from ovs-vsctl .

I mean i am looking for reset option.


[root@OSKVM1 nova]# ovs-vsctl show
602ca311-4ebe-4773-8d58-00d1a0161294
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 "qr-2fdc65ca-3a"
tag: 2
Interface "qr-2fdc65ca-3a"
type: internal
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Port "tap4763d73b-95"
tag: 1
Interface "tap4763d73b-95"
type: internal
Port "qg-a690c808-49"
tag: 1
Interface "qg-a690c808-49"
type: internal
Port "tape364c044-4f"
tag: 2
Interface "tape364c044-4f"
type: internal
Bridge br-ex
Port "p5p2"
Interface "p5p2"
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
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 "gre-0a180005"
Interface "gre-0a180005"
type: gre
options: {df_default="true", in_key=flow,
local_ip="10.24.0.4", out_key=flow, remote_ip="10.24.0.5"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
ovs_version: "2.5.0"
[root@OSKVM1 nova]#
[root@OSKVM1 ~]# nova list


On Thu, Oct 13, 2016 at 2:05 PM, Ben Pfaff  wrote:

> From an OVS perspective, yes.
>
> From an OpenStack perspective, you'd be better off asking on an
> OpenStack mailing list.
>
> On Thu, Oct 13, 2016 at 09:54:04AM -0400, Gaurav Goyal wrote:
> > 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 
> > 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@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@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@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@OSKVM1 ~]# history|grep ovs-vsctl add
> > >31. grep: add: No such file or directory
> > >32. [root@OSKVM1 ~]# history|grep ovs-vsctl
> > >33.   846  ovs-vsctl show
> > >34.   922

Re: [ovs-discuss] Fwd: Help for replacing linux bridging with OpenVswitch

2016-10-13 Thread Ben Pfaff 
From an OVS perspective, yes.

From an OpenStack perspective, you'd be better off asking on an
OpenStack mailing list.

On Thu, Oct 13, 2016 at 09:54:04AM -0400, Gaurav Goyal wrote:
> 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 
> 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@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@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@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@OSKVM1 ~]# history|grep ovs-vsctl add
> >31. grep: add: No such file or directory
> >32. [root@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@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@OSKVM1 neutron]# ovs-vsctl list-ports br-ex
> >
> > p5p2
> >
> > [root@OSKVM1 neutron]# ovs-vsctl list-ports br-int
> >
> > patch-tun
> >
> > tap33501010-4d
> >
> > [root@OSKVM1 neutron]# ifconfig -a
> >
> > br-ex: flags=4098  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  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

[ovs-discuss] Fwd: Help for replacing linux bridging with OpenVswitch

2016-10-13 Thread Gaurav Goyal 
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 
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@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@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@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@OSKVM1 ~]# history|grep ovs-vsctl add
>31. grep: add: No such file or directory
>32. [root@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@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@OSKVM1 neutron]# ovs-vsctl list-ports br-ex
>
> p5p2
>
> [root@OSKVM1 neutron]# ovs-vsctl list-ports br-int
>
> patch-tun
>
> tap33501010-4d
>
> [root@OSKVM1 neutron]# ifconfig -a
>
> br-ex: flags=4098  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  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  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  mtu 1450
>
> inet6 fe80::7e:27ff:fea9:796f  prefixlen 64  scopeid 0x20
>
> ether 1e:bc:5d:27:7e:75  txqueuelen 0  (Ethernet)
>
>