Tuesday, 2018-09-25

*** hongbin has joined #openstack-kuryr01:00
*** pmannidi has joined #openstack-kuryr01:13
*** maysams has quit IRC03:31
*** hongbin has quit IRC04:33
*** pcaruana has joined #openstack-kuryr05:41
*** irenab has joined #openstack-kuryr06:40
openstackgerritMerged openstack/kuryr-kubernetes master: Add HOWTO for SRIOV use case  https://review.openstack.org/59412506:58
*** celebdor has joined #openstack-kuryr07:39
*** garyloug has joined #openstack-kuryr08:08
*** garyloug_ has joined #openstack-kuryr08:09
*** garyloug__ has joined #openstack-kuryr08:11
garyloug__dmellado, all, this is the os-vif patch as mentioned yesterday https://review.openstack.org/#/c/604992/08:12
dulekltomasbo: Whoops, you've merged the SR-IOV docs patch. The document linked there is still private.08:28
dulekI guess I should have gave +1 instead of +2 there.08:28
ltomasbodulek, it is private?08:29
ltomasbodulek, I tried and it opened for me...08:29
dulekltomasbo: Maybe you've got permissions earlier, dunno.08:30
danilltomasbo, dulek: hello. Could you please explain what wrong with https://review.openstack.org/#/c/600022/13 ?? It says that "Failed to read build info file: ValueError("build info file is broken: IndexError('list index out of range',)",)"08:32
danilbut I can't find an issue08:32
ltomasbodulek, maybe... sorry then, I just checked if I could open it, and as I open it, and saw that the first line said [public]08:33
ltomasbodulek, i thought it was already fixed08:33
dulekltomasbo: Sure, I understand that. Let's just make sure aperevalov makes it public. :)08:33
dulekdanil: Looking…08:34
danildulek: thanks08:34
*** pmannidi has quit IRC08:35
dulekdanil: http://logs.openstack.org/22/600022/13/check/openstack-tox-docs/89a600b/job-output.txt.gz#_2018-09-21_07_08_45_60031008:35
dulekdanil: Seems like this is the root reason?08:35
aperevalovdulek: it wasn't my document, I asked original authors, it's Gary's colegues, they promissed to publish it yesterday, but they were busy... and they still busy08:36
dulekaperevalov: Sure, sure. Let's just make sure it'll become public one day. ;)08:36
danildulek: hm, thanks, I'll check it . There is a yaml spec example08:37
dulekdanil: I think you shouldn't use "::" followed by code blocks.08:39
dulekdanil: But after fixing that it still doesn't build locally for me.08:39
danildulek: hmmmm, it's strange08:40
dulekdanil: Maybe it's some kind of bug on openstackdocstheme or even infra.08:45
dulekdanil: Yup, master doesn't build for me as well.08:47
danildulek: looks like that. I've removed the whole part of yaml  description from file but I stil have the same error08:47
dmelladogaryloug__: ack, thanks!08:59
*** janki has joined #openstack-kuryr09:20
*** janki has quit IRC10:07
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: ignore Editor tags  https://review.openstack.org/60503110:19
celebdordmellado: are you around?10:27
dmelladocelebdor: what's up?10:27
celebdordmellado: what did you say that you wanted done in ansible10:27
celebdor?10:27
celebdorand why10:27
dmelladohmmm I did recall wanting to swamp you into something regarding ansible10:28
dmelladobut as of lately my mind is a LIFO pipe10:28
dmelladoso who knows! xD10:28
*** maysams has joined #openstack-kuryr10:28
dmelladoI could've said that I want you to implement a platypus ascii for kuryr related roles10:28
celebdordmellado: wasn't it something to do with redoing most of our devstack stuff in ansible?10:30
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Translate security group rules.  https://review.openstack.org/59234910:30
dmelladocelebdor: oh, yeah10:30
celebdorcan you give me more details?10:31
dmelladonow I'm starting to remember10:31
dmelladoso, basically, as a part of dulek's conversations10:31
celebdorwe should make a blueprint and such10:31
dmelladoon the PTG10:31
dmelladoyeah, deff10:31
dmelladootherwise we'll deff forget as you're even worse than me10:31
celebdorright10:31
celebdorI am10:31
celebdorso10:32
celebdorwhat will it be10:32
dmelladobtw, before I forget too10:32
celebdorone playbook that is called from the plugin.sh?10:32
dmelladoltomasbo: celebdor10:32
dmelladocould you please +2+A that patch?10:32
dmelladoI've just gone over a trivial change10:32
celebdorwhich?10:32
ltomasbodmellado, which one?10:33
dmelladohttps://review.openstack.org/59234910:33
dmelladoI've removed the handler unit test10:33
dmelladoand will put that on a diff patch10:33
dmelladoas we agreed10:33
dmelladootherwise, mainly the same10:33
ltomasbodmellado, great! thanks!10:33
dmelladocelebdor: yeah, basically a rewrite of our devstack plugin10:33
dmelladoin ansible10:33
dmelladofor the multinode thing10:33
dmelladodulek: could you ellaborate that?10:33
* dulek reads…10:34
dulekdmellado: More like for multinode and nested stuff. To correctly implement it we need some kind of synchronization between what's running on different nodes. devstack-gate is unable to provide us with this.10:35
dmelladoyeah, so we wanted that to be done in ansible10:35
dmelladoso we could control that node-like10:35
dmelladonow it gets back10:35
dmelladolol10:35
dulekSo I propose implementing Kubernetes/OpenShift installation as Ansible playbooks to be able to do that.10:35
dulekMoreover it'll be easier to make it run on VMs created on DevStack, instead of DevStack itself.10:36
celebdorhow will ansible help with that?10:36
dulekcelebdor: The "remote" execution or the synchronization?10:37
celebdorboth10:37
dulekcelebdor: Well, in case of sync in Ansible you can generate certificates and .kubeconfig and then copy it onto the nodes. devstack-gate runs are simply independent on both nodes.10:39
dulekOf course in case of "non-nested" deployment we could just deploy from controller's plugin.sh.10:39
dulekI mean nested. :P10:39
celebdordulek: how do you know about the nodes?10:40
celebdorthey are independent, right?10:40
dulekcelebdor: In nested case nodes are VMs you spawn, so it's pretty easy.10:40
celebdordulek: I was thinking of gates10:40
dulekIn non-nested case… Hm, ansible should have them in inventory.10:41
celebdordynamic inventory does htat10:41
celebdorbut how can we get the list of nodes in the current job10:41
celebdorand credentials to access them10:41
celebdordmellado: ^^10:41
dmelladocelebdor: we'd need to check how the default job does that10:42
dmelladoI'll add that to my research topics10:42
dulekcelebdor: http://logs.openstack.org/29/601829/1/check/kuryr-kubernetes-tempest-multinode-octavia/536b5c1/ara-report/10:42
dulekcelebdor: Seems like OpenStack's Ansible has it in the inventory already.10:42
dulekcelebdor: I mean gate's Ansible.10:42
celebdordulek: does that run in the node?10:43
dulekcelebdor: What's "node"?10:44
celebdornevermind10:44
celebdorso we have the controller label for a host10:45
dmelladoyep10:46
celebdorand the other one is labeled 'compute'? Or what?10:46
dmelladocelebdor: check even our own gate definitions10:46
dmelladoyou have subnodes and so10:46
dmelladoyou lazy emerit TPL xD10:46
dmelladoseriously, would you like to have a quick bluejeans10:46
dmelladoso I explain this to you?10:46
celebdordmellado: I'd rather just know which label to use for the worker nodes10:46
celebdorxD10:46
dmelladolol10:47
dmelladocelebdor: i.e. https://review.openstack.org/#/c/599608/1/.zuul.d/base.yaml10:47
dulekcelebdor: "controller" and "compute1"?10:48
celebdorok10:48
celebdorthanks10:48
*** janki has joined #openstack-kuryr10:50
dmelladodulek: btw, as I said before, could you merge https://review.openstack.org/59234910:53
dmelladoI'd like to move on to the next PS after it10:53
celebdordmellado: let's say we do the ansible thing10:55
celebdorhow would we deal with the devstack stages?10:55
dmelladowe'll implement whatever necessary on playbooks10:55
dmelladoand we can call that from our devstack plugin10:55
dmelladoin any case we need to do a blueprint10:55
celebdorso split it into multiple different playbooks?10:55
celebdorwhat a drag10:56
dmelladoexactly10:56
dmelladothat's why I wanted you to do it10:56
dmelladoxD10:56
dulekdmellado: You know that you can develop next commits locally without previous being merged? :D10:56
dmelladodulek: I knwo10:56
dmelladoand I'm already doing that10:56
dmelladobut the less I rebase, the better10:56
dmelladoxD10:56
dmelladoso c'mon! xD10:56
dmelladosee? was it so hard? xD10:56
dulekdmellado: It's not that bad actually if you use `git rebase -i HEAD~10`, and then move commits around with "fixup" action.10:57
celebdordulek: preach!10:57
dmelladoLOL10:57
celebdordulek: it seems the lazy PTL is him10:57
dmelladodulek: do you know that I once had an intern who confused merge with rebase and did squashes?10:57
celebdorxD10:57
dmelladoxD10:57
dmelladocelebdor: we both are10:57
dmelladoxD10:57
dmelladonow that I think about it, that was even worse than the pip thing on superfluidity10:58
* dmellado shivers10:58
celebdorlol10:58
dulekdmellado: We've once worked with a team of folks that shared the SSH key and all the commits were attributed to their team leader. ;)10:58
dmelladoLOL10:58
dmelladoreally? xD10:58
dulekdmellado: Yup, we were quite surprised about how quick the guy is producing the code. :D10:59
dulekdmellado: My point is - we've all seen *things*.10:59
dmelladolol10:59
dmelladolet's call them 'things' yeah10:59
dmelladosuch as the guy who refused to use any kind of control version11:00
dmelladoand sent his changes over email11:00
dmelladoto all the team, daily11:00
dmelladoxD11:00
* dmellado off for lunch11:01
*** janki has quit IRC11:07
*** pcaruana has quit IRC11:15
*** maysams has quit IRC11:47
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: svc namespace isolation support for different octavia drivers  https://review.openstack.org/60471711:49
*** aojea has joined #openstack-kuryr12:00
*** rh-jelabarre has joined #openstack-kuryr12:05
*** aojea has quit IRC12:51
*** maysams has joined #openstack-kuryr13:10
openstackgerritMichał Dulko proposed openstack/kuryr-kubernetes master: Move Python 3.6 jobs to check and gate as voting  https://review.openstack.org/60506813:22
*** aojea has joined #openstack-kuryr13:26
openstackgerritMichał Dulko proposed openstack/kuryr-kubernetes master: Remove kuryr-kubernetes-tempest-lbaasv2 job  https://review.openstack.org/60507013:27
*** aojea has quit IRC13:30
openstackgerritMichał Dulko proposed openstack/kuryr-tempest-plugin master: Sync up with kuryr-kubernetes gates  https://review.openstack.org/60507213:32
dulekcelebdor, dmellado, ltomasbo, irenab: ^ This is my try to reorganize our gates a bit.13:33
ltomasbodulek, thanks! reviewing...13:33
dmelladoyep, reviewing13:34
dmelladoI was about to push the 1)13:34
dmelladoso thanks for  being faster xD13:34
dmelladodulek: in any case, note13:34
dmelladoyou should do the same and sync for the tempest plugin gates13:34
dmelladootherwise we'll differ and chaos will reign13:34
dmelladoxD13:34
dmellado(and ltomasbo's bad jokes, which are better than mine, but that's another topic)13:34
ltomasbodmellado, ???? xD13:35
dmelladoxD13:35
ltomasbodmellado, actually, dulek has already sync the tempest side too13:35
ltomasbodmellado, look at the last patch13:35
dmelladooh, cool13:36
dmelladothen chaos will not reign13:36
dmelladojust bad jokes13:36
dmelladoxD13:36
ltomasboxD13:36
dulek:)13:36
dulekAt the moment tempest plugin seems to be compatible with Python 3, but I've noticed one of gcheresh patches in review isn't.13:37
dmelladodulek: there you go, -113:37
dmelladoxD13:37
dulekSo I want to add py36 gate there, because I don't think we can notice incompatibilities manually.13:37
dmelladonope, don't let me have nightmares about manual testing, please13:38
dmelladoalready been thru that too many times already13:38
dulekIt's a bit of an issue that there are some tests running only with certain configs. E.g. gcheresh patch is one of those, so this py36 gate won't help here anyway.13:38
dulekI'm starting to think about "consolidating" some of the gates.13:39
dmelladowhat we could do is just port all gates to py313:39
dmelladoyep13:39
dulekE.g. I don't really see a point in running separated openshift, openshift with ingress and openshift with namespaces gates. This could be joined into a single one.13:39
dmelladodulek: makes sense, as this started growing bit by bit13:40
dmelladonow we'd be able to just set the defaults and if there's any odd leftover that can't be left out13:41
dmelladothat'll be put out to experimental13:41
dulekdmellado: Yup. I haven't put out patches doing that, because we might want to discuss this on Monday's meeting. I might be missing some dependencies.13:42
dmellado+113:42
dmelladolet's discuss that as I'd also like for gecheresh and the folks to be around13:43
ltomasbodulek, I saw your comment about no-daemon removal on stein14:41
ltomasbodulek, aren't we already on stein?14:42
dulekltomasbo: Yes, we are. I was thinking that it should be delayed to T(rain) to follow deprecation policy (which we don't officially follow, BTW), but looks like it's not.14:45
dulekltomasbo: I guess that's another topic for Monday's meeting?14:45
ltomasboI don't mind having it there until T if that is the standard policy14:45
dulekltomasbo: Nah, turns out it's just next release *and* at least 3 months. So we're past that, I've deprecated it 6 months ago.14:46
ltomasbodulek, ok, for that, should we also remove the non-daemonize code?14:47
dulekltomasbo: I would love to do that. :D14:47
ltomasbo+1 from my side14:47
ltomasboit will make it simple to maintain14:47
*** celebdor has quit IRC15:01
openstackgerritMerged openstack/kuryr-kubernetes master: ignore Editor tags  https://review.openstack.org/60503115:12
*** celebdor has joined #openstack-kuryr15:15
*** celebdor has quit IRC15:19
*** rh-jelabarre has quit IRC15:39
openstackgerritMerged openstack/kuryr-kubernetes master: Translate security group rules.  https://review.openstack.org/59234915:41
*** rh-jelabarre has joined #openstack-kuryr15:42
*** aperevalov has quit IRC15:55
*** pcaruana has joined #openstack-kuryr16:07
*** garyloug_ has quit IRC16:23
*** garyloug has quit IRC16:23
*** garyloug__ has quit IRC16:23
dmelladolet's remove it16:50
dmelladoit'll make things much simpler16:50
dmelladoand I'd like to avoid having a big pipeline there16:50
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: [WIP] Support network policy update  https://review.openstack.org/60515017:01
*** celebdor has joined #openstack-kuryr17:23
*** aojea has joined #openstack-kuryr18:13
*** maysams has quit IRC18:26
*** celebdor has quit IRC18:34
*** dmellado has quit IRC18:53
*** dmellado has joined #openstack-kuryr20:07
*** celebdor has joined #openstack-kuryr20:10
*** janki has joined #openstack-kuryr20:12
*** pcaruana has quit IRC20:43
*** janki has quit IRC21:08
*** aojea has quit IRC21:58
*** aojea has joined #openstack-kuryr23:31
*** aojea has quit IRC23:35
*** aojea has joined #openstack-kuryr23:54
*** aojea has quit IRC23:59

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