Wednesday, 2019-01-23

openstackgerritMerged openstack/kuryr-kubernetes master: Removing lbaasv2 related code  https://review.openstack.org/63126100:13
*** spsurya has quit IRC00:26
*** hongbin has joined #openstack-kuryr02:25
*** rh-jelabarre has quit IRC03:52
*** hongbin has quit IRC04:18
*** phuoc__ has quit IRC05:25
*** spsurya has joined #openstack-kuryr06:08
*** phuoc has joined #openstack-kuryr06:09
*** ccamposr has joined #openstack-kuryr06:53
*** yboaron_ has joined #openstack-kuryr06:55
*** ccamposr__ has joined #openstack-kuryr06:55
*** ccamposr has quit IRC06:58
*** aojea has joined #openstack-kuryr07:03
*** gcheresh has joined #openstack-kuryr07:08
*** aojea has quit IRC07:28
*** aojea has joined #openstack-kuryr07:29
*** aojea has quit IRC07:31
*** maysams has joined #openstack-kuryr07:42
*** gkadam has joined #openstack-kuryr08:22
*** celebdor has joined #openstack-kuryr08:27
openstackgerritMichał Dulko proposed openstack/kuryr-kubernetes master: Remove way of running without kuryr-daemon  https://review.openstack.org/63127809:29
dulekltomasbo, celebdor: Rebased. ^09:29
ltomasbodone09:36
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Ensure host to pod connectivity for NP  https://review.openstack.org/63250309:45
openstackgerritMichał Dulko proposed openstack/kuryr-kubernetes master: Fixup gate names after LBaaS v2 removal  https://review.openstack.org/63267409:51
openstackgerritYossi Boaron proposed openstack/kuryr-tempest-plugin master: Rerun test in a single thread if multi-thread failed  https://review.openstack.org/63268410:14
celebdorthanks dulek10:25
celebdorltomasbo: could I get some more info on https://review.openstack.org/#/c/631781/10:37
*** pcaruana has joined #openstack-kuryr10:37
celebdorthe commit message is very poor on details10:37
celebdorabout what the problem was10:37
celebdorand the commit message lines are not wrapped!10:37
ltomasbocelebdor, problem is 2 fold10:38
ltomasbocelebdor, the initial patch set was not fixing was it was intended to10:38
celebdorso did it fix something?10:38
ltomasbocelebdor, nop, it was actually removing extra rules that needed to be there10:38
ltomasbocelebdor, this is the redo of that patch: https://review.openstack.org/#/c/63158710:39
celebdorand what's the second fold?10:40
ltomasbocelebdor, second part was that it deletes rules that needed to be there10:41
ltomasbocelebdor, thus breaking the NP support for svc10:41
celebdorI thought that was the first part10:41
celebdorltomasbo: did you sync with maysams to sort out the misunderstanding? Cause it feels like at some point we were out of sync about how NP svcs work10:42
ltomasbocelebdor, yep, maysams and I were working on the same set of patch sets to fix the svc support10:43
*** livelace has joined #openstack-kuryr10:43
celebdordulek: I managed to get you a review for https://review.openstack.org/#/c/626885/10:43
celebdorbut not with the expected result :P10:43
ltomasbocelebdor, problem was that we need each other reviews to be more sure that we cover all the cases...10:44
maysamsltomasbo, celebdor: Indeed. Is always better to have each other reviews10:44
ltomasbocelebdor, and test it, otherwise it is easy to miss corner cases (that was missing the case for multiple NPs)10:44
ltomasbocelebdor, maysams: so, to the best of my knowledge, the next steps are:10:45
ltomasbo1) merging the revert10:45
ltomasbo2) merging this: https://review.openstack.org/#/c/63123010:46
ltomasbo3) rebasing and merge https://review.openstack.org/#/c/63158710:46
ltomasbo4) rebasing, and maysams reviews on https://review.openstack.org/#/c/62985610:46
ltomasboahh, and independently of such, reviewing ( celebdor and maysams) this: https://review.openstack.org/#/c/632503/10:47
ltomasbowith this, we only have the bug that maysams filed about the target ports to handle10:47
maysamsltomasbo: we also have this one https://bugs.launchpad.net/kuryr-kubernetes/+bug/181039410:49
openstackLaunchpad bug 1810394 in kuryr-kubernetes "CRD podSelector is not properly updated on NP update" [High,Triaged] - Assigned to Maysa de Macedo Souza (maysa)10:49
maysamsbut is not related to services10:49
mrosteckihey folks! did anyone see the following error recently? http://paste.openstack.org/show/743162/10:50
mrosteckiI'm using master devsstack and master kuryr-kubernetes10:50
celebdorltomasbo: did you look into running kubernetes or openshift's NP tests?10:51
ltomasbocelebdor, I didn't yet10:51
celebdormrostecki: Hi10:52
* celebdor looking10:52
celebdoroh, a devstack issue10:52
celebdormrostecki: can you show us your local.conf?10:52
celebdorit is as if it missed octavia10:52
celebdorltomasbo: btw, I had already reviewed https://review.openstack.org/#/c/632503/10:53
mrosteckicelebdor: I disabled octavia on purpose10:54
mrosteckicelebdor: http://paste.opensuse.org/view/raw/4231712610:54
mrosteckicelebdor: so, the changes I made were 1) disabling octavia 2) disabling k8s services10:55
mrosteckiand disabling etcd10:55
mrosteckiI want to reuse my currently existing cluster10:55
mrosteckiand I want to write my CNI config for kubelet later by hand ;)10:55
celebdormrostecki: right10:56
celebdorright now devstack assumes there is either lbaasv2 (or was it removed yesterday) or octavia10:56
celebdormrostecki: I would welcome a patch that checked if services are enabled in the handler and if they are not, that it would skip setting the LB stuff10:57
celebdorare you up for it?10:57
mrosteckicelebdor: yes, I can try to do that10:57
celebdorcool10:58
celebdorthanks mrostecki!10:58
celebdorTrying it together with cillium?10:58
mrosteckiyes. and months ago when I did that, disabling octavia didn't cause anny issues10:59
mrosteckibut I guess that lbaasv2 was used instead10:59
mrosteckinow I'm trying things again from scratch, because the PR for enabling cilium as a chained plugin was merged recenty11:00
celebdorexactly :-)11:00
celebdorbut that path was removed yesterday11:00
celebdorafter a long deprecation11:00
celebdorbut didn't consider the no service approach11:01
celebdorsorry about that11:01
mrosteckidamn, I should've start trying out kuryr on Monday, hahahah ;)11:01
mrosteckino problem11:02
mrosteckiif I will hit any bigger issues with fixing devstack plugin, then I will maybe just enable octavia11:02
ltomasboping maysams: about your comment here: https://review.openstack.org/#/c/629856/8/kuryr_kubernetes/controller/drivers/lbaasv2.py11:11
celebdormrostecki: ok. Please do let me know11:12
celebdorand I'll try to help11:12
mrosteckicelebdor: so many things in the plugin depend on lb values. I think I will rather try to enable octavia11:28
mrosteckicelebdor: and create a bug on launchpad to follow up later11:28
mrosteckiwith allowing to disable octavia without errors11:29
celebdormrostecki: cool11:29
celebdoryeah, deploying with octavia and then just disabling the handler is probably the easiest way to go ahead with your stuff11:30
celebdor:-)11:30
mrosteckicelebdor: diskimage-builder is still broken? should I use prefetched images?11:34
celebdorI don't remember11:35
celebdorltomasbo: ^^11:35
ltomasbocelebdor, I actually don't know, I always use the prefetched one11:37
celebdormrostecki: safe to do the same then11:37
maysamsltomasbo: pong12:10
ltomasbomaysams, ping :)12:11
ltomasbomaysams, it was about your comment on https://review.openstack.org/#/c/629856/8/kuryr_kubernetes/controller/drivers/lbaasv2.py12:11
ltomasbomaysams, for the comment on lines 231-268, you mean if the pod (aka NP sg) has the default rule, just add a continue on after line 230, right?12:12
maysamsyes12:13
maysamsltomasbo ^^12:13
ltomasbomaysams, yep, that make sense and make me realize about other possible problem12:14
maysamstell me12:14
ltomasbomaysams, as for the comment on l27612:14
ltomasbomaysams, we do need to have and 'and', right?12:14
maysamsyes12:14
maysamswait.. I read it wrong12:15
ltomasbowe only remove those rules if we added some, and the rule is the default one12:15
ltomasboif we didn't add any rule, and there was a default rule, we should not remove it12:15
ltomasbomaysams, ^^12:15
ltomasbomaysams, and now what I realized, at line 284, we should do something different12:16
ltomasbomaysams, because just because one NP does not apply, we should not set the default listener rules (if there is any other NP that applies)12:17
ltomasboright?12:17
maysamsltomasbo: I agree. Please, ignore that comment12:18
ltomasbomaysams, ok, and regarding the add_default rules if... what do you think?12:20
ltomasbomaysams, if there are different NPs applied to the pods/svc12:20
ltomasboif one does not match the container, but the second one does, we should not add the default rules, right?12:21
maysamsltomasbo, I don't think we need to worry about this. Aren't we getting the sg applied to that specific service in here:12:24
maysamshttps://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/drivers/network_policy_security_groups.py#L24012:24
ltomasbomaysams, true12:26
maysamsAll the matching that needed to be done regarding NPs was done previously, and we only look to the sgs.12:26
ltomasbomaysams, so many peaces...12:26
ltomasbomaysams, but... one sec12:26
ltomasbothat will return the list of sgs, right?12:27
maysamsltomasbo, yes12:27
ltomasbosg1 for NP1, sg2 for NP212:27
maysamsok12:27
ltomasboahh, ok, so the default SG will not be there...12:27
ltomasbogot it12:27
ltomasbomaysams, then, given that... shoud we instead of having a continue at line 230, simply have a break?12:28
maysamsltomasbo, just one sec12:32
maysamsltomasbo: I think we still need to create the rules in the LBaaS when we have the default sgs..12:36
maysamsltomasbo: Its possible to have the default sgs returned in that method we were talking about12:37
maysamsltomasbo: due to this https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/drivers/network_policy_security_groups.py#L14212:37
maysamsltomasbo: ahh, but we are adding out of the iteration, so it's ok to break :)12:39
maysamssry12:39
*** rh-jelabarre has joined #openstack-kuryr12:45
dulekUh, seems like we have some requirements issue with os-resource-classes. I'm investigating that now.13:05
dulekOkay, looks like new version isn't showing up in infra's pypi mirror. Not much we can do.13:21
livelacecelebdor, https://bugs.launchpad.net/kuryr-kubernetes/+bug/181301513:22
openstackLaunchpad bug 1813015 in kuryr-kubernetes "Controller doesn't delete LB if wrong floating subnet was set in a Service" [Undecided,New]13:22
celebdorthakns livelace13:23
celebdoryboaron_: could you take a look at ^^13:24
*** livelace has quit IRC13:45
*** livelace has joined #openstack-kuryr13:49
yboaron_celebdor, Yep, I'll take care of that14:00
celebdorthanks yboaron_!!!14:01
yboaron_livelace, Hi14:12
yboaron_livelace, regarding https://bugs.launchpad.net/kuryr-kubernetes/+bug/1813015 , Could you please attach the K8S service manifest to the bug?14:13
openstackLaunchpad bug 1813015 in kuryr-kubernetes "Controller doesn't delete LB if wrong floating subnet was set in a Service" [Undecided,New] - Assigned to Yossi Boaron (yossi-boaron-1234)14:13
*** yboaron_ has quit IRC14:37
*** livelace has quit IRC14:58
*** aojea_ has joined #openstack-kuryr15:12
*** aojea_ has quit IRC15:31
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Fix CRD update when NP has namespaceSelectors  https://review.openstack.org/63123016:07
dulekltomasbo: Oh my, +400 lines in a bugfix? :D ^16:10
ltomasbodulek, /o\16:10
ltomasbodulek, yep, but it was because the functionality code ended up in the wrong driver16:11
ltomasbodulek, so it is pretty much moving it from one to the other16:11
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Revert "Ensure reaction to svc target-port update"  https://review.openstack.org/63178116:11
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Ensure lb sg rules are not deleted when adding members  https://review.openstack.org/63158716:11
dulekltomasbo: Well, hard stuff is difficult to get right immediately. ;)16:11
ltomasbodulek, now that you are here, I rebased this one and lost +W: https://review.openstack.org/#/c/631781/16:12
ltomasbodulek, can you add it back16:12
dulekltomasbo: Done.16:13
ltomasbothanks!16:13
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Ensure lb sg rules are not deleted when adding members  https://review.openstack.org/63158716:15
openstackgerritYossi Boaron proposed openstack/kuryr-kubernetes master: Handle exception raised in FIP allocation  https://review.openstack.org/63277216:15
*** gcheresh has quit IRC16:21
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Ensure NP changes are applied to services  https://review.openstack.org/62985616:31
*** livelace has joined #openstack-kuryr16:37
*** ccamposr__ has quit IRC16:41
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Ensure host to pod connectivity for NP  https://review.openstack.org/63250316:44
dulekltomasbo: I'm looking at https://review.openstack.org/#/c/632503.16:59
dulekltomasbo: Is the current approach that SG's are provided by SG driver and all the rules are casually added by NP driver?17:00
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Ensure NP changes are applied to services  https://review.openstack.org/62985617:03
ltomasbodulek, yep, SG driver is returning the SG associated to pods/services17:03
ltomasbodulek, and the NP driver is in charge of adding the needed rules17:04
ltomasbodulek, or the lbaas one for the loadbalancers17:04
dulekltomasbo: "sg = self.neutron.create_security_group(body=security_group_body)" - seems like it also creates the SG…17:04
dulekltomasbo: I'm a bit puzzled about what are the responsibilities of each piece.17:05
dulekltomasbo: In perfect world SG operations would happen only in SG driver, right?17:05
ltomasboSG driver is not creating the SGs actually, it is returning the information about the ones assigned to each resource17:05
ltomasbowell, to make that happen, we will need to make drivers aware of each other17:06
ltomasboand/or move a lot of the functionality from drivers to handlers17:07
dulekltomasbo: Can you provide an example why? Just so I understand the complexity here.17:07
ltomasboin my view, separation is, handlers to the kubernetes event, and then use the drivers to create the openstack resources17:08
dulekltomasbo: Hm, yeah, I get this. I'd rather have less code in drivers and more in handlers, but I don't think I have any arguments besides gut feeling, so I might be totally wrong with that.17:08
dulekltomasbo: Yeah, that's my understanding as well.17:08
dulekltomasbo: That's why I'm puzzled on network_policy driver as there is no such OpenStack resource. :P17:09
ltomasboperhaps it is time to reorganize the code too... since it is getting a bit to match linked with that many options17:09
ltomasboproblem is that, network policy driver is using the network policy sg drvier to get the security groups associated to the pods and services17:09
ltomasbothen it is doing some actions, but at the same time, the lbaasV2 driver is the one in charge of handling the security groups for the services17:10
ltomasboand then, at the same time, NPs needs namespace functionality (not the isolation though) to create the different subnets per namespace17:10
ltomasboI guess the main thing is that SG/SG_rules creation/deletion may happen at different events (namespace creation, service creation, pod creation, network_policy creation, and the respective updates/deletion)17:13
ltomasbodulek, ^^17:13
dulekltomasbo: Uh, yeah… We'd need to pass all those resources state into SG driver for it to calculate what to do.17:13
dulekltomasbo: BTW - why do we do subnet per namespace for NP?17:14
ltomasbowhen you create a network policy, its scope is the namespace in which it is created17:14
ltomasboand we are using the subnet CIDR to reduce the crazyness of security group rules17:14
dulekltomasbo: Ooooh, good.17:14
*** gkadam has quit IRC17:29
*** maysams has quit IRC17:43
openstackgerritMichał Dulko proposed openstack/kuryr-kubernetes master: Enable debug logs on Kubernetes services  https://review.openstack.org/62660918:09
openstackgerritMichał Dulko proposed openstack/kuryr-kubernetes master: DNM: Save etcd metrics  https://review.openstack.org/63150618:10
*** aojea has joined #openstack-kuryr18:27
*** aojea has quit IRC18:29
*** celebdor has quit IRC18:30
*** aojea has joined #openstack-kuryr18:30
*** spsurya has quit IRC19:55
*** aojea has quit IRC20:03
*** aojea has joined #openstack-kuryr20:04
*** celebdor has joined #openstack-kuryr20:36
openstackgerritYossi Boaron proposed openstack/kuryr-kubernetes master: Handle exception raised in FIP allocation  https://review.openstack.org/63277220:48
*** aojea_ has joined #openstack-kuryr21:27
*** aojea has quit IRC21:28
*** livelace has quit IRC21:32
*** mrostecki has quit IRC22:19
*** mrostecki has joined #openstack-kuryr22:23
openstackgerritMerged openstack/kuryr-kubernetes master: Fix CRD update when NP has namespaceSelectors  https://review.openstack.org/63123022:36
*** mrostecki has quit IRC22:37
*** mrostecki has joined #openstack-kuryr22:43
*** mrostecki has quit IRC22:51
*** mrostecki has joined #openstack-kuryr22:56
*** aojea_ has quit IRC23:13

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!