openstackgerrit | Akihiro Motoki proposed openstack/networking-bgpvpn master: Django 2.0 support https://review.openstack.org/568128 | 02:47 |
---|---|---|
*** matrohon has joined #openstack-net-bgpvpn | 07:37 | |
*** tmorin has joined #openstack-net-bgpvpn | 07:42 | |
*** tmorin has quit IRC | 07:54 | |
*** tmorin has joined #openstack-net-bgpvpn | 08:08 | |
*** bobmel has quit IRC | 08:34 | |
*** tmorin has quit IRC | 08:37 | |
*** tmorin has joined #openstack-net-bgpvpn | 08:37 | |
*** pjrusak has joined #openstack-net-bgpvpn | 11:53 | |
pjrusak | hi @tmorin | 11:54 |
pjrusak | so to understand your mail correctly you recommend to use ovs as dataplane driver for IPVPN and EVPN | 11:55 |
tmorin | hi pjrusak ! | 12:17 |
tmorin | if you want to interop with something doing only MPLS/GRE or MPLS/UDP for IPVPN, then yes, you should use the OVS driver for IPVPN | 12:19 |
tmorin | you'll have things to do to support MPLS/GRE though: use a recent OVS with the openvswitch module provided with OVS, and configure bagpipe-bgp so that MPLS/GRE is used in an interoperable way | 12:20 |
tmorin | for E-VPN, both the linuxbrigde and ovs drivers will allow to do VXLAN in a way that will interop | 12:21 |
tmorin | if you want to do IPVPN MPLS/GRE with linuxbridge and you are ready to test work-in-progress code, I can try to push the work I have locally, to let you test it | 12:22 |
openstackgerrit | Andrzej Denisiewicz proposed openstack/networking-bgpvpn master: Add a test test_bgpvpn_loopback_port_association_create_and_update to test many loopbacks (default 100). https://review.openstack.org/568279 | 12:22 |
pjrusak | for now I think I will go for supported path, but later definitely will give a try to linuxbrigde | 12:24 |
pjrusak | so need to check what version of ovs I have | 12:25 |
pjrusak | I got 2.8.1 so I need to switch to 2.9.0 to make mpls forwarding work | 12:27 |
tmorin | I don't have the exact release in mind, but 2.8.1 should be fine | 12:35 |
tmorin | I think MPLS/GRE was in 2.8.0 | 12:35 |
tmorin | yes, you just need >=2.8.0 | 12:36 |
tmorin | be careful to use the openvswitch module shipping with OVS (usually compiled with DKMS), rather than the module shipping with the kernel | 12:37 |
tmorin | and you will need "gre_tunnel_options = packet_type=legacy_l3" in the [DATAPLANE_DRIVER_IPVPN] section of /etc/bagpipe/bgp.conf | 12:38 |
pjrusak | ok, great than I don't need to upgrade version | 12:38 |
pjrusak | do i have to setup gre_tunnel and mpls_interface as well? | 12:39 |
pjrusak | what about those kernel modules? is it only performance issue or stock one missing anything? | 12:40 |
tmorin | using "mpls_interface=*gre*" is sufficient | 12:42 |
tmorin | in fact it depends also on your kernel release, some older kernels have an openvswitch module that does not have what is needed for packet_type=xxx | 12:43 |
tmorin | if you have a very recent kernel, then using the openvswitch module shipping with the kernel possibly would work, but I'm not sure | 12:44 |
tmorin | I haven't followed in which kernels the datapath OVS->kernel backports have landed | 12:45 |
pjrusak | is it any further step other than defining VPN as l3 and accociate that network to correct VPN under project, is needed to advertise network using BGP by bagpipe-bgp | 12:45 |
pjrusak | s/accociate/associate/ | 12:46 |
tmorin | no, that should be sufficient | 12:46 |
tmorin | if you have the associations in the neutron API, and nothing showing up under "bagpipe-looking-glass vpns instances", then the problem is probably somewhere in the neutron agent or its config | 12:47 |
tmorin | if you have the VPN definitions in "bagpipe-looking-glass vpns instances" and nothing advertise, then the problem is somewhere in the BGP peering, or in bagpipe-bgp, or on the neighbor | 12:47 |
pjrusak | got it. I'm going to adjust my config using this information and will get back if it won't work | 12:48 |
pjrusak | thanks a lot | 12:49 |
tmorin | don't hesitate to send me logs or "bagpipe-looking-glass -r" dumps if you run into issues | 12:52 |
*** bobmel has joined #openstack-net-bgpvpn | 12:52 | |
*** bobmel has quit IRC | 13:09 | |
pjrusak | I don't see anything under "bagpipe-looking-glass vpns instances" or "bgp adv_routes". Will gather logs and sent you via email | 13:13 |
pjrusak | I might be missing something in my devstack "local.conf" | 13:13 |
*** bobmel has joined #openstack-net-bgpvpn | 13:24 | |
tmorin | I've just had a look at your conf and dump | 13:57 |
tmorin | if you don't have any VPN instance defined in bagpipe-bgp, it means that the problem is around neutron agent and (likely) more specifically the bagpipe_bgpvpn agent extension | 13:58 |
tmorin | can you send (or paste.openstack.org) the neutron agent logs ? (journalctl -u devstack@neutron-agent) ? | 13:59 |
tmorin | also, as background information: the OVS driver for IPVPN has been here for a while and has CI tempest tests, so I'm confident you can have it running ok, but the OVS driver for EVPN is much younger (and does not yet have a tempest CI job) | 14:01 |
tmorin | so if you want to try the simpler things first, try with IPVPN | 14:01 |
tmorin | another thing: I've seen "Exception while initializing dataplane state: Exit code 1 when running 'ovs-vsctl add-port br-mpls mpls_gre -- set Interface mpls_gre type=gre options:local_ip=192.168.0.5 options:remote_ip=flow options:options:layer3=true' " in your dump | 14:02 |
tmorin | can you send me your bgp.conf file please ? | 14:04 |
tmorin | pjrusak: replies above ^^ | 14:04 |
pjrusak | Sure, I will collect that additional logs and config files and sent you via email | 14:05 |
tmorin | pjrusak: for the bgp.conf issue, I think I know what happened: bgp.conf previously had a wrong suggested line, which you probably uncommented, instead of using the one I proposed, right ? | 14:15 |
tmorin | (the misleading suggestion has been fixed in master, but not in stable/queens) | 14:16 |
*** pjrusak has quit IRC | 14:19 | |
*** matrohon has quit IRC | 15:56 | |
openstackgerrit | Thomas Morin proposed openstack/networking-bgpvpn master: unit test fix: fix api_extension_path being overriden https://review.openstack.org/568322 | 15:57 |
*** tmorin has quit IRC | 16:09 | |
*** pjrusak has joined #openstack-net-bgpvpn | 17:04 | |
*** rusakp has joined #openstack-net-bgpvpn | 17:06 | |
*** pjrusak has quit IRC | 17:06 | |
rusakp | tmorin, you are correct. Originally the line with "gre_tunnel_options" was commented out. Later I uncommented it and restarted BGP service | 17:20 |
rusakp | oh, I got it now. Just checked configuration file bgp.conf and that's right the suggested "gre_tunnel_options" line is different than the one you told me | 17:24 |
rusakp | after correcting this option and restarting b-bgp service this problem was solved. now the route is listed among "bgp routes" | 17:34 |
*** matrohon has joined #openstack-net-bgpvpn | 19:00 | |
*** matrohon has quit IRC | 20:14 | |
*** rusakp has quit IRC | 21:48 | |
openstackgerrit | Merged openstack/networking-bgpvpn master: unit test fix: fix api_extension_path being overriden https://review.openstack.org/568322 | 22:20 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!