*** salv-orlando has joined #openstack-neutron-ovn | 00:49 | |
*** openstackgerrit has quit IRC | 00:51 | |
*** openstackgerrit has joined #openstack-neutron-ovn | 00:52 | |
*** salv-orlando has quit IRC | 00:54 | |
*** salv-orlando has joined #openstack-neutron-ovn | 02:03 | |
*** salv-orlando has quit IRC | 02:08 | |
*** salv-orlando has joined #openstack-neutron-ovn | 02:08 | |
*** salv-orlando has quit IRC | 02:10 | |
*** armax has joined #openstack-neutron-ovn | 02:52 | |
*** armax has quit IRC | 03:21 | |
*** salv-orlando has joined #openstack-neutron-ovn | 04:02 | |
*** salv-orlando has quit IRC | 04:10 | |
*** salv-orlando has joined #openstack-neutron-ovn | 04:13 | |
*** salv-orlando has quit IRC | 04:18 | |
*** salv-orlando has joined #openstack-neutron-ovn | 05:16 | |
*** salv-orlando has quit IRC | 05:24 | |
*** salv-orlando has joined #openstack-neutron-ovn | 05:25 | |
*** salv-orlando has quit IRC | 05:29 | |
*** salv-orlando has joined #openstack-neutron-ovn | 06:43 | |
*** salv-orlando has quit IRC | 06:46 | |
*** salv-orlando has joined #openstack-neutron-ovn | 06:51 | |
*** salv-orlando has quit IRC | 06:56 | |
*** salv-orlando has joined #openstack-neutron-ovn | 07:48 | |
*** fzdarsky has joined #openstack-neutron-ovn | 08:58 | |
*** yalie1 has left #openstack-neutron-ovn | 09:52 | |
*** armax has joined #openstack-neutron-ovn | 14:00 | |
*** shettyg has joined #openstack-neutron-ovn | 14:36 | |
*** fzdarsky has quit IRC | 15:15 | |
*** fzdarsky has joined #openstack-neutron-ovn | 15:21 | |
*** russellb has quit IRC | 15:36 | |
*** aluria has quit IRC | 15:36 | |
*** russellb has joined #openstack-neutron-ovn | 15:37 | |
*** aluria has joined #openstack-neutron-ovn | 15:37 | |
*** armax has quit IRC | 15:48 | |
*** cascardo has joined #openstack-neutron-ovn | 15:54 | |
*** armax has joined #openstack-neutron-ovn | 16:01 | |
*** armax has quit IRC | 16:08 | |
*** armax has joined #openstack-neutron-ovn | 16:09 | |
*** fzdarsky has quit IRC | 16:10 | |
*** armax has quit IRC | 16:13 | |
*** fzdarsky has joined #openstack-neutron-ovn | 16:14 | |
*** armax has joined #openstack-neutron-ovn | 16:21 | |
*** fzdarsky has quit IRC | 16:22 | |
*** fzdarsky has joined #openstack-neutron-ovn | 16:24 | |
*** fzdarsky has quit IRC | 16:37 | |
*** fzdarsky has joined #openstack-neutron-ovn | 16:39 | |
*** armax has quit IRC | 18:07 | |
*** armax has joined #openstack-neutron-ovn | 18:13 | |
*** s3wong has joined #openstack-neutron-ovn | 18:19 | |
openstackgerrit | Aaron Rosen proposed openstack/networking-ovn: DON"T REVIEW TEST.. https://review.openstack.org/201286 | 18:32 |
---|---|---|
russellb | pfft, /me reviewed it anyway | 18:35 |
*** armax has quit IRC | 18:46 | |
*** gsagie_ has joined #openstack-neutron-ovn | 18:50 | |
*** armax has joined #openstack-neutron-ovn | 18:58 | |
*** nlahouti has joined #openstack-neutron-ovn | 19:05 | |
*** nlahouti has left #openstack-neutron-ovn | 19:06 | |
*** arosen has joined #openstack-neutron-ovn | 19:11 | |
arosen | hiya russellb | 19:11 |
russellb | arosen: o/ | 19:11 |
gsagie_ | Hi Aaron | 19:11 |
arosen | hi | 19:11 |
russellb | arosen: just wanted to check in on your ml2 conversion ... seems to be passing tests just as well as the ml2 version | 19:12 |
russellb | want to just merge what you have? | 19:12 |
russellb | or anything known not working yet? | 19:12 |
arosen | russellb: Sorry I was working on some other internal stuff. Let me hack on what i have up for a few hours and we can merge it tomorrow. | 19:12 |
russellb | arosen: no problem at all! just didn't want you to feel like you had to make it pass all tempest or anything | 19:13 |
arosen | is anyone hitting this btw? | 19:13 |
russellb | because it doesn't now | 19:13 |
arosen | Obtaining file:///opt/stack/networking-ovn | 19:13 |
arosen | Complete output from command python setup.py egg_info: | 19:13 |
arosen | error in setup command: Invalid environment marker: (python_version=='2.7' # Apache-2.0) | 19:13 |
arosen | 19:13 | |
russellb | arosen: that came up on openstack-dev ... try updating pip | 19:13 |
russellb | and pbr | 19:13 |
russellb | and whatever else, heh | 19:13 |
russellb | it was something like that | 19:13 |
gsagie_ | טקשי פנר | 19:13 |
gsagie_ | yeah pbr | 19:14 |
gsagie_ | its also failing on neutron windows dependencies | 19:14 |
arosen | russellb: Sounds good. I wanted to make sure that everything that passed with ML2 passes with the new plugin. | 19:14 |
russellb | arosen: yeah, that makes sense :) | 19:14 |
arosen | That said a lot of the stuff that is passing with ML2 doesn't really work. Just the API passes. | 19:14 |
russellb | :-| | 19:14 |
arosen | so i've been trying to sort through that a little. | 19:14 |
arosen | yea :( | 19:15 |
russellb | well that's no good | 19:15 |
russellb | sounds like the tests aren't any good then IMO | 19:15 |
arosen | the tests just test that the API is working. | 19:15 |
russellb | gotcha | 19:16 |
russellb | oh well | 19:16 |
russellb | and here i was thinking we had so much working ... | 19:16 |
arosen | There are also several tests in tempest on the nova side that assume neutron implement security groups. | 19:16 |
russellb | magically | 19:16 |
arosen | And the nova-compute <-> neutron integration only works if we have security groups :( | 19:16 |
arosen | So for now we just have to lie it looks like. | 19:17 |
arosen | anyways, I'm getting closer. | 19:17 |
arosen | hopefully by the end of today I should match parity with ml2. | 19:17 |
russellb | nice | 19:17 |
arosen | The other thing I'm planning on working next is the docker integration stuff in the OVN plugin. | 19:18 |
russellb | arosen: the binding:profile thing? | 19:18 |
arosen | i've been talking to Guru and a few other internal guys and we realized we can have the vlan allocation stuff allocated in the plugin directly rather than making the caller specifiy the vlan. | 19:19 |
russellb | i never actually tested that with containers ... just verified that it configured OVN like i expected it to | 19:19 |
arosen | yup | 19:19 |
russellb | well ... | 19:19 |
arosen | So one neutron change we need to make is have neutron allocate the vlans on the port that are unused. | 19:19 |
russellb | yeah i guess that's fine, not a huge win because the caller still has to know about all the VLANs in use | 19:19 |
russellb | so that it can configure ovs in the VM properly | 19:19 |
arosen | So the neutron api only needs to reciece the parent_port_id and we'll allocate you a free vlan | 19:19 |
arosen | russellb: We can make it so they can also specify the vlan and if it isn't used they can use their own. | 19:20 |
russellb | ok, i guess if it gets auto allocated, it should (could) be in the API call response | 19:21 |
russellb | so you'd know what VLAN to use without having to do another API call | 19:21 |
arosen | russellb: right but this also makes it easier for them because now they don't need to keep track of all the vlans in use on their end. | 19:21 |
russellb | yeah | 19:21 |
arosen | yup, i think we should put the vlan in the response. | 19:21 |
russellb | agree :) | 19:21 |
russellb | wfm | 19:21 |
russellb | would also love to get this integrated with kubernetes | 19:22 |
russellb | that really shows the value | 19:22 |
russellb | i know some others have looked at neutron integration with k8s in general | 19:22 |
russellb | maybe docker networking support will get us there? | 19:23 |
* russellb hasn't really looked at this stuff enough | 19:23 | |
russellb | provider networks are still making me shed a few tears | 19:23 |
arosen | Yea I think getting this integrated in other places should be pretty cool | 19:24 |
arosen | shettyg: has been working on the docker network stuff | 19:24 |
russellb | yeah, i've seen his stuff, but haven't tried it yet :( | 19:25 |
* russellb should start building a real team here for ovn | 19:25 | |
arosen | russellb: hrm do you have that email handy about updating pip? I just search for the error in my email and google but i'm not seeing it :( | 19:27 |
gsagie_ | aarosen : how is the vlan thing going to, because its the containers management system that needs to bind the containers to the correct VLAN port on OVS (in the VM hosting the containers) | 19:28 |
gsagie_ | and OVN/neutron has no access there, right? | 19:28 |
russellb | arosen: the thing i had in mind was "[openstack-dev] [all][requirements] Whats with the "python_version=='2.7'" stuff thats showing up from today?" | 19:28 |
russellb | arosen: but that doesn't seem to have the answer | 19:29 |
arosen | gsagie the vlan id can be passed in there along with what/ever is getting the response to start the container. | 19:29 |
russellb | arosen: oh btw, check out the vlan-aware-vms spec | 19:29 |
russellb | can't remember if it got approved yet or not | 19:29 |
russellb | but i was thinking that covers our use case | 19:29 |
russellb | and it definitely didn't include auto vlan id allocation | 19:29 |
arosen | russellb: Yea i think it's somewhat similar | 19:31 |
gsagie_ | arosen : so you are just managing VLAN allocation across local switches (or networks) in that VM right? | 19:32 |
gsagie_ | but you need to do it per VM | 19:32 |
arosen | gsagie per port. | 19:32 |
russellb | arosen: i think it's our best hope of a generic API for what we want anyway | 19:32 |
arosen | that is what my thought was. | 19:32 |
gsagie_ | yes per port | 19:32 |
gsagie_ | per VM port | 19:32 |
arosen | yup | 19:32 |
arosen | brb | 19:32 |
arosen | russellb: it looks like this change is what is breaking me | 19:37 |
arosen | -ovs>=2.4.0.dev0 # Apache-2.0 | 19:37 |
arosen | +ovs>=2.4.0.dev0;python_version=='2.7' # Apache-2.0 | 19:37 |
russellb | yep | 19:38 |
arosen | commit abb9c14ffc4da5906cbfe02cf984c184da202a3f | 19:38 |
arosen | Author: OpenStack Proposal Bot <openstack-infra@lists.openstack.org> | 19:38 |
russellb | maybe ask in -infra | 19:38 |
russellb | i don't remember .. | 19:38 |
gsagie_ | nice idea regarding the VLAN allocations | 19:40 |
gsagie_ | \guess lib network support returning data for the container creation | 19:40 |
*** thumpba has joined #openstack-neutron-ovn | 19:42 | |
*** armax has quit IRC | 19:48 | |
*** gsagie_ has quit IRC | 19:51 | |
openstackgerrit | Aaron Rosen proposed openstack/networking-ovn: Convert plugin away from ML2 https://review.openstack.org/195326 | 20:01 |
shettyg | I have been looking at Kubernetes integration of OVN for a month now. Without OVN providing a LB, there are are no clean integration points with Kubernetes v1.0 | 20:09 |
russellb | shettyg: ah ok ... if it's neutron integration with OVN on the backend, we might be able to make neutron LBaaS work ... but I'm not sure how mature that is | 20:11 |
russellb | never tried it | 20:11 |
shettyg | I had a meeting with Tim Hockin from Google-Kubernetes and he was looking at changing the way they do LB in Kubernetes (without changing the source IP of the packet) post v1.0. If that happens, we can provide the first round of integration | 20:12 |
shettyg | wherein Kubernetes still does LB, OVN only provides L2 + L3 | 20:12 |
shettyg | russellb: I also do not know how Neutron LB works or how good that is. Kubernetes needs a LB for both north-south as well as east-west traffic. | 20:26 |
russellb | reference implementation of the lbaas API is called octavia ... I think it's a bit young | 20:28 |
russellb | it spawns up VMs that run haproxy, basically | 20:28 |
shettyg | russellb; looking at providing LB as part of OVN. Have the basic idea. But need to brainstorn on how it fits the pipeline | 20:31 |
russellb | well we don't have L3 at all in OVN yet | 20:31 |
shettyg | russellb: yes, along with L3. | 20:31 |
shettyg | The idea is to use conntrack to track stateful connections and then to IP address translation to LB VIP | 20:31 |
russellb | great | 20:32 |
*** fzdarsky has quit IRC | 21:15 | |
*** armax has joined #openstack-neutron-ovn | 21:27 | |
*** thumpba has quit IRC | 21:38 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!