Tuesday, 2019-10-01

*** jamesmcarthur has quit IRC00:08
*** donghao has joined #openstack-meeting00:13
*** jamesmcarthur has joined #openstack-meeting00:17
*** donghao has quit IRC00:17
*** yamamoto has quit IRC00:24
*** markvoelker has quit IRC00:26
*** gyee has quit IRC00:27
*** yamamoto has joined #openstack-meeting00:28
*** jamesmcarthur has quit IRC00:31
*** jamesmcarthur has joined #openstack-meeting00:32
*** yamamoto has quit IRC00:43
*** yamamoto has joined #openstack-meeting00:44
*** ekcs has quit IRC00:48
*** yamamoto has quit IRC00:49
*** yamamoto has joined #openstack-meeting00:55
*** jamesmcarthur has quit IRC01:14
*** jamesmcarthur has joined #openstack-meeting01:17
*** ianychoi has quit IRC01:17
*** ianychoi has joined #openstack-meeting01:18
*** mhen has quit IRC01:20
*** jamesmcarthur has quit IRC01:22
*** igordc has quit IRC01:26
*** jamesmcarthur has joined #openstack-meeting01:40
*** lseki has quit IRC01:47
*** hongbin has joined #openstack-meeting01:55
*** jamesmcarthur has quit IRC02:06
*** jamesmcarthur has joined #openstack-meeting02:07
*** yamamoto has quit IRC02:14
*** donghao has joined #openstack-meeting02:15
*** yamamoto has joined #openstack-meeting02:17
*** macz has joined #openstack-meeting02:19
*** brinzhang has joined #openstack-meeting02:19
*** donghao has quit IRC02:19
*** hyunsikyang has quit IRC02:23
*** macz has quit IRC02:23
*** brinzhang_ has joined #openstack-meeting02:24
*** brinzhang has quit IRC02:27
*** hongbin has quit IRC02:33
*** hongbin has joined #openstack-meeting02:34
*** hyunsikyang has joined #openstack-meeting02:42
*** yamamoto has quit IRC02:59
*** psachin has joined #openstack-meeting03:12
*** gmann_afk is now known as gmann03:33
*** markvoelker has joined #openstack-meeting03:41
*** markvoelker has quit IRC03:42
*** markvoelker has joined #openstack-meeting03:43
*** yamamoto has joined #openstack-meeting03:44
*** yamamoto has quit IRC03:49
*** hongbin has quit IRC03:56
*** igordc has joined #openstack-meeting03:58
*** ianychoi has quit IRC03:59
*** ianychoi has joined #openstack-meeting04:00
*** whoami-rajat has joined #openstack-meeting04:04
*** yamamoto has joined #openstack-meeting04:15
*** ricolin has joined #openstack-meeting04:16
*** donghao has joined #openstack-meeting04:16
*** rfolco has quit IRC04:17
*** macz has joined #openstack-meeting04:20
*** yamamoto has quit IRC04:21
*** donghao has quit IRC04:22
*** macz has quit IRC04:25
*** yamamoto has joined #openstack-meeting04:28
*** macz has joined #openstack-meeting04:28
*** macz has quit IRC04:30
*** macz has joined #openstack-meeting04:30
*** jamesmcarthur has quit IRC04:31
*** jamesmcarthur has joined #openstack-meeting04:33
*** macz has quit IRC04:35
*** yamamoto_ has joined #openstack-meeting04:49
*** yamamoto has quit IRC04:51
*** pcaruana has joined #openstack-meeting05:01
*** Luzi has joined #openstack-meeting05:02
*** ianychoi has quit IRC05:03
*** ianychoi has joined #openstack-meeting05:05
*** dviroel has quit IRC05:07
*** jbadiapa has joined #openstack-meeting05:13
*** links has joined #openstack-meeting05:13
*** yamamoto_ has quit IRC05:16
*** yamamoto has joined #openstack-meeting05:16
*** jamesmcarthur has quit IRC05:17
*** ianychoi has quit IRC05:27
*** ianychoi has joined #openstack-meeting05:29
*** ykatabam has quit IRC05:33
*** markvoelker has quit IRC05:47
*** jamesmcarthur has joined #openstack-meeting05:47
*** igordc has quit IRC05:52
*** yamamoto has quit IRC05:57
*** ianychoi has quit IRC06:00
*** ianychoi has joined #openstack-meeting06:01
*** bbowen_ has joined #openstack-meeting06:14
*** bbowen has quit IRC06:15
*** donghao has joined #openstack-meeting06:19
*** jamesmcarthur has quit IRC06:20
*** jbadiapa has quit IRC06:22
*** donghao has quit IRC06:23
*** jamesmcarthur has joined #openstack-meeting06:28
*** lpetrut has joined #openstack-meeting06:31
*** macz has joined #openstack-meeting06:32
*** yamamoto has joined #openstack-meeting06:35
*** ttsiouts has joined #openstack-meeting06:35
*** macz has quit IRC06:36
*** ianychoi has quit IRC06:40
*** ianychoi has joined #openstack-meeting06:42
*** yamamoto has quit IRC06:47
*** hongbin has joined #openstack-meeting06:56
*** slaweq has joined #openstack-meeting06:57
*** hongbin has quit IRC07:00
*** rpittau|afk is now known as rpittau07:04
*** jamesmcarthur has quit IRC07:04
*** zbr is now known as zbr|ruck07:08
*** keiko-k has joined #openstack-meeting07:14
*** tesseract has joined #openstack-meeting07:16
*** apetrich has joined #openstack-meeting07:17
*** kopecmartin|off is now known as kopecmartin07:24
*** jbadiapa has joined #openstack-meeting07:27
*** joxyuki has joined #openstack-meeting07:42
*** ttsiouts has quit IRC07:43
*** ralonsoh has joined #openstack-meeting07:45
*** markvoelker has joined #openstack-meeting07:47
*** markvoelker has quit IRC07:51
*** ayoung has quit IRC07:54
*** ayoung has joined #openstack-meeting07:57
*** ttsiouts has joined #openstack-meeting07:57
*** takahashi-tsc has joined #openstack-meeting08:01
*** ociuhandu has joined #openstack-meeting08:02
*** dkushwaha_ has joined #openstack-meeting08:02
*** apetrich has quit IRC08:02
*** rcernin has quit IRC08:02
dkushwaha_#startmeeting tacker08:02
openstackMeeting started Tue Oct  1 08:02:27 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha_. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: tacker)"08:02
openstackThe meeting name has been set to 'tacker'08:02
*** dkushwaha_ is now known as dkushwaha08:02
dkushwaha#topic Roll Call08:02
*** jbadiapa has quit IRC08:03
*** rcernin has joined #openstack-meeting08:04
*** jbadiapa has joined #openstack-meeting08:04
*** brinzhang has joined #openstack-meeting08:05
*** apetrich has joined #openstack-meeting08:06
dkushwahahi all08:06
*** brinzhang_ has quit IRC08:08
*** dkushwaha_ has joined #openstack-meeting08:10
dkushwaha_#topic announcement08:11
*** openstack changes topic to "announcement (Meeting topic: tacker)"08:11
dkushwaha_we have released tacker2.0.0.0rc108:11
joxyukithanks dkushwaha08:12
dkushwaha_and as we are in R2, so we can have make other fixes available for train cycle08:12
*** ttsiouts has quit IRC08:12
dkushwaha_thanks all for your hard work08:12
*** dkushwaha has quit IRC08:12
dkushwaha_#topic Open Discussion08:13
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:13
dkushwaha_i am working on functional gate job fix, but wondering some test randomly failing on gate but not on my local env08:14
dkushwaha_loking for volunteer who can help on gate xies08:16
*** nitinuikey has joined #openstack-meeting08:17
*** tpatil has joined #openstack-meeting08:17
dkushwaha_joxyuki, please help on reviewing https://review.opendev.org/#/c/685538/08:18
*** ttsiouts has joined #openstack-meeting08:18
joxyukidkushwaha, yes, I looked it.08:18
joxyukiand having a question that this test fail is due to Glance bug. so should we skip the test until the bug is fixed instead of changing that test?08:19
tpatilIs this bug already reported in glance?08:20
joxyukinot yet but I am prepering it.08:20
tpatiljoxyuki: Ok08:20
joxyukiI will nofity you when I report a bug to Glance.08:21
dkushwaha_joxyuki, make sense, yes we can skip it for now08:21
*** ociuhandu has quit IRC08:21
tpatil+1, skip tests08:21
*** ociuhandu has joined #openstack-meeting08:22
*** nitinuikey has quit IRC08:22
dkushwaha_ok, i will skip it for now08:22
dkushwaha_another issue is with cmd_executor https://review.opendev.org/#/c/678499/08:23
dkushwaha_test working fine on my env, but bot sure why failing on gate. I tried with multiple fixes in this patch set, but seems still failing08:24
joxyukidkushwaha, I also tested the patch on my local and works fine.08:25
*** nitinuikey has joined #openstack-meeting08:25
joxyukinow I have no idea why the test fails in zuul.08:25
*** yamamoto has joined #openstack-meeting08:26
*** dkushwaha has joined #openstack-meeting08:28
*** e0ne has joined #openstack-meeting08:29
*** dkushwaha_ has quit IRC08:29
dkushwahatpatil, could you please help on test_create_delete_vnf_with_placement_policy_affinity test failure08:29
*** nitinuikey has quit IRC08:30
*** nitinuikey has joined #openstack-meeting08:32
dkushwahamoving next..08:33
dkushwahaI have plan to join Shanghai summit & PTG.08:34
dkushwahaHope to see you guys there08:34
*** nnsingh has joined #openstack-meeting08:35
dkushwahaAs of now nothing else from my side.08:35
*** shubham_potale has joined #openstack-meeting08:35
tpatildkushwaha: Yes, I will check the above test failure issue08:36
dkushwahatpatil, thanks.08:36
*** brinzhang_ has joined #openstack-meeting08:37
keiko-kdkushwaha you arrange Tacker PTG in Shanghai?08:37
dkushwahasomebody have anything to discuss?08:37
dkushwahakeiko-k, yes, with help & presence of all you guys :)08:38
*** brinzhang_ has quit IRC08:38
*** brinzhang_ has joined #openstack-meeting08:39
keiko-kdkushwaha Nice. I also will be there.08:40
*** brinzhang has quit IRC08:40
*** dkushwaha_ has joined #openstack-meeting08:41
dkushwaha_can we close this meeting, if no other things to discuss?08:42
dkushwaha_Thanks Folks08:43
dkushwaha_Closing this meeting08:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:44
openstackMeeting ended Tue Oct  1 08:43:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-10-01-08.02.html08:44
*** dkushwaha has quit IRC08:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-10-01-08.02.txt08:44
*** joxyuki has left #openstack-meeting08:44
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-10-01-08.02.log.html08:44
*** takahashi-tsc has quit IRC08:45
*** dkushwaha_ is now known as dkushwaha08:46
*** keiko-k has quit IRC08:50
*** macz has joined #openstack-meeting08:51
*** macz has quit IRC08:55
*** tpatil has quit IRC08:56
*** nitinuikey has quit IRC08:56
*** jamesmcarthur has joined #openstack-meeting09:01
*** ociuhandu has quit IRC09:02
*** dkushwaha has quit IRC09:04
*** jamesmcarthur has quit IRC09:06
*** nnsingh has left #openstack-meeting09:06
*** donghao has joined #openstack-meeting09:21
*** ociuhandu has joined #openstack-meeting09:23
*** donghao has quit IRC09:26
*** ociuhandu has quit IRC09:28
*** rfolco has joined #openstack-meeting09:29
*** jbadiapa has quit IRC09:29
*** jbadiapa has joined #openstack-meeting09:30
*** tssurya has joined #openstack-meeting09:41
*** ricolin has quit IRC09:44
*** markvoelker has joined #openstack-meeting09:48
*** markvoelker has quit IRC09:53
*** yamamoto has quit IRC10:02
*** shubham_potale has quit IRC10:05
*** ttsiouts has quit IRC10:08
*** brinzhang has joined #openstack-meeting10:08
*** ttsiouts has joined #openstack-meeting10:09
*** brinzhang_ has quit IRC10:12
*** tetsuro has joined #openstack-meeting10:12
*** ttsiouts has quit IRC10:13
*** ociuhandu has joined #openstack-meeting10:20
*** tetsuro has quit IRC10:28
*** tetsuro has joined #openstack-meeting10:34
*** macz has joined #openstack-meeting10:52
*** bbowen_ has quit IRC10:52
*** jbadiapa has quit IRC10:53
*** macz has quit IRC10:57
*** artom has joined #openstack-meeting10:59
*** yamamoto has joined #openstack-meeting11:00
*** ttsiouts has joined #openstack-meeting11:16
*** donghao has joined #openstack-meeting11:24
*** hyunsikyang__ has joined #openstack-meeting11:24
*** tetsuro has quit IRC11:28
*** hyunsikyang has quit IRC11:28
*** donghao has quit IRC11:28
*** tssurya has quit IRC11:31
*** tssurya_ has joined #openstack-meeting11:31
*** raildo has joined #openstack-meeting11:42
*** markvoelker has joined #openstack-meeting11:49
*** markvoelker has quit IRC11:54
*** dviroel has joined #openstack-meeting11:54
*** yamamoto has quit IRC11:58
*** bbowen has joined #openstack-meeting12:03
*** lseki has joined #openstack-meeting12:06
*** enriquetaso has joined #openstack-meeting12:06
*** ianychoi has quit IRC12:10
*** ianychoi has joined #openstack-meeting12:13
*** brinzhang_ has joined #openstack-meeting12:21
*** brinzhang has quit IRC12:24
*** lpetrut has quit IRC12:24
*** yamamoto has joined #openstack-meeting12:25
*** ricolin has joined #openstack-meeting12:32
*** trident has quit IRC12:34
*** trident has joined #openstack-meeting12:35
*** brinzhang has joined #openstack-meeting12:35
*** yamamoto has quit IRC12:37
*** brinzhang_ has quit IRC12:39
*** tetsuro has joined #openstack-meeting12:42
*** tetsuro has quit IRC12:47
*** macz has joined #openstack-meeting12:53
*** Luzi has quit IRC12:55
*** macz has quit IRC12:57
*** rcernin has quit IRC12:58
*** jbadiapa has joined #openstack-meeting13:06
*** yamamoto has joined #openstack-meeting13:10
*** jawad_axd has joined #openstack-meeting13:14
*** mriedem has joined #openstack-meeting13:15
*** jbadiapa has quit IRC13:16
*** yamamoto has quit IRC13:17
*** trident has quit IRC13:22
*** trident has joined #openstack-meeting13:23
*** donghao has joined #openstack-meeting13:26
*** donghao has quit IRC13:31
*** ociuhandu has quit IRC13:42
*** ociuhandu has joined #openstack-meeting13:43
*** ociuhandu has quit IRC13:48
*** markvoelker has joined #openstack-meeting13:50
*** jawad_axd has quit IRC13:54
*** markvoelker has quit IRC13:55
*** markvoelker has joined #openstack-meeting13:57
*** markvoelker has quit IRC14:01
haleyb#startmeeting networking-ovn14:02
openstackMeeting started Tue Oct  1 14:02:20 2019 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: networking-ovn)"14:02
openstackThe meeting name has been set to 'networking_ovn'14:02
bcafarelthis time I had it correctly set in my agenda :)14:02
haleybbcafarel: hi14:02
haleyb#chair tidwellr14:03
openstackCurrent chairs: haleyb tidwellr14:03
*** artom has quit IRC14:03
haleybi need to send a reminder to the ML about this meeting...14:03
*** shintaro has joined #openstack-meeting14:04
haleybbcafarel: i guess it's just the two of us, i'll wait a few minutes for quorum of 314:05
haleybtidwellr: hi, you make quorum14:07
tidwellrsorry, had some drama dropping a kid off at school today :(14:07
haleybbeen there before14:07
tidwellrcomes with the territory14:07
haleyb#topic Announcements14:08
*** openstack changes topic to "Announcements (Meeting topic: networking-ovn)"14:08
haleybI'll just restate their is a discussion topic on this at the PTG, https://etherpad.openstack.org/p/neutron-shanghai-forum-brainstorming14:09
haleybCan add any questions there14:10
tidwellrthese sessions aren't recorded, are they?14:10
haleybno, i don't believe so14:10
tidwellrdidn't think so...14:10
*** ociuhandu has joined #openstack-meeting14:10
haleybany other announcements?14:11
bcafarelwe can try to record/broadcast, but the quality will be "guy recording from his laptop in a corner of the noisy room"14:11
haleyb#topic ML2-OVS-DVR/OVN convergence14:13
*** openstack changes topic to "ML2-OVS-DVR/OVN convergence (Meeting topic: networking-ovn)"14:13
haleybThere were some comments in the draft last week regarding moving the networking-ovn code into the neutron tree14:13
* haleyb doesn't see jlibosva on freenode14:14
bcafarelI see him in #openstack-neutron14:15
*** jlibosva has joined #openstack-meeting14:17
haleybfrom what i understand, if we plan on in the future having OVN as the default, having it in-tree is a requirement, unless i mis-understand things14:17
haleybjlibosva: hi, you're multi-meeting-plexing like me :-/14:18
haleybjust wanted to discuss your comments in the spec14:18
jlibosvahaleyb: :) yeah, using ears in videomeeting and fingers here14:18
slaweqhi, sorry for being late14:18
tidwellrand if I understand jlibosva correctly the concern is really a matter timing for moving things in-tree, am I understanding you correctly?14:18
jlibosvahaleyb: I was not aware of such policy - do you have a link handy where it's defined we need to use in-tree code for default backends?14:19
jlibosvamy point was that we might be taking a big task that might not be necessary - but I was not aware there is a policy that requires the code to be in-tree14:20
haleybjlibosva: i don't have a link to any policy, i just assumed14:20
tidwellrhaleyb: I was under the same assumption, but that's just tribal knowledge I've been handed14:21
haleybit makes it look more supported if it's in-tree14:21
jlibosvawho should have such piece of information? TC members?14:22
* haleyb has been here for a while, but doesn't know for sure14:22
slaweqI guess that nobody every raised such question yet in fact :)14:22
*** markvoelker has joined #openstack-meeting14:22
njohnstonPolicy requiring code to be in-tree?  With my TC member hat on, I think that is up to the projects.14:22
jlibosvanjohnston: I planned to reach out to you, you replied before I asked, thanks :)14:23
njohnstonI mean, neutron could be arranged so ML2 was a separate repo, ML2/OVS was a separate repo from that, etc.  But it would raise the barrier for development work considerably because coordinating changes across repos adds complexity and difficulty14:23
*** shintaro has quit IRC14:24
tidwellrmy only concern is the barrier to entry, we already have a number of repo's for code to be scattered across14:24
*** ttsiouts has quit IRC14:25
haleybright, and part of the effort is to lower the bar for working on OVN14:25
*** ttsiouts has joined #openstack-meeting14:25
slaweqit may also makes some things harder, if someone will need to add change which will require patches to 2 repos14:25
slaweqit is ofcourse doable with Depends-On but it's easier if all is in one repo and one patch :)14:26
*** markvoelker has quit IRC14:26
haleyband i know jlibosva already mentioned we have this today with neutron-lib/neutron changes...14:26
bcafarelyes, also if you want to learn how a features works, it's easier if API and reference implementation are in same place :)14:27
njohnstonMy personal opinion is that with a shrinking dev base we want the barrier for entry into neutron to be as low as possible.14:27
*** markvoelker has joined #openstack-meeting14:27
tidwellrnjohnston: +1, and to add to that I feel like more repos = more maintenance overhead14:28
njohnstonMy TC opinion is that neutron knows best how to arrange it's repos, there is not a one-size-fits-all solution.14:28
jlibosvaI agree with all said above, that having it in-tree is simpler. I wanted to make sure it's all worth the effort and that we understand what work needs to be done (merging devstack plugins etc.)14:28
jlibosvaand I understand the burden, when working with tripleo and needed to send a patch to 10 repos, I wanted to shoot myself :)14:29
haleybjlibosva: i will need some help on making the list of work items, and please don't shoot yourself :)14:29
tidwellrjlibosva: I would say if we're only just "exploring" this, then I agree with you about not proceeding. But, if we are indeed serious about the OVN direction then I think for all the reasons that folks have expressed we should move it in-tree14:30
*** ttsiouts has quit IRC14:30
*** munimeha1 has joined #openstack-meeting14:31
jlibosvaif all the folks are aware of amount of work it requires and agree it's worth having the code in-tree then sure, let's move towards it14:31
haleybwe have 30 minutes, so can discuss the work, even if some is obvious, or i can start an etherpad to collect it14:31
tidwellrjlibosva: if we've resolved your concern about in-tree vs. not, is there anything else that stood out in the spec that you think should be addressed?14:33
jlibosvaperhaps - do we want to have another spec for the move or is everybody ok with what is currently in the spec regarding the move?14:34
njohnstonI'm all right with it14:38
tidwellrI mentioned this to haleyb before, I don't think another spec is in order. But I'm just one person.....14:38
haleybjlibosva: do you want me to start an etherpad so we can list the work items?  then maybe after a little brainstorming we'll have a pretty good list14:39
jlibosvahaleyb: sounds good14:39
*** links has quit IRC14:40
haleyband if some "oh shit" item comes up we can work throught it14:40
bcafarel+1 that could be then summarized/reused in the spec if we realize it is complicated14:40
slaweqhaleyb: etherpad with todo list sounds good for me14:40
*** lpetrut has joined #openstack-meeting14:40
haleyb#action haleyb to make an etherpad outlining steps of moving OVN in-tree14:41
haleybi'll do that today and add a link to the spec14:43
haleybis there anything else people want to discuss about the spec?14:45
haleyb#topic Open Discussion14:46
*** openstack changes topic to "Open Discussion (Meeting topic: networking-ovn)"14:46
*** lpetrut has quit IRC14:47
njohnstonWhat is left before the spec can merge, in your mind haleyb?  Do we need to have the work items enumerated?14:47
haleybjlibosva: this is where we talk about deprecating linuxbridge to free-up zuul space :)14:47
njohnstonhaleyb: I added that as a PTG topic14:47
haleybnjohnston: i think just adding a link to the etherpad so it's findable14:48
*** ttsiouts has joined #openstack-meeting14:49
haleybnjohnston: thanks, i'll go look, it's always a good time to talk about # of jobs14:50
haleybany other topics?14:51
haleybok, well thanks for coming everyone and having a good discussion14:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:53
openstackMeeting ended Tue Oct  1 14:53:13 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ovn/2019/networking_ovn.2019-10-01-14.02.html14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ovn/2019/networking_ovn.2019-10-01-14.02.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ovn/2019/networking_ovn.2019-10-01-14.02.log.html14:53
*** jamesmcarthur has joined #openstack-meeting14:55
*** artom has joined #openstack-meeting14:57
*** artom has quit IRC14:57
*** artom has joined #openstack-meeting14:58
*** jbadiapa has joined #openstack-meeting14:58
*** jbadiapa has quit IRC15:05
*** tetsuro has joined #openstack-meeting15:12
*** lpetrut has joined #openstack-meeting15:13
*** tetsuro has quit IRC15:17
*** ociuhandu has quit IRC15:17
*** ociuhandu has joined #openstack-meeting15:18
*** ianychoi has quit IRC15:20
*** ttsiouts has quit IRC15:22
*** ianychoi has joined #openstack-meeting15:23
*** ociuhandu has quit IRC15:24
*** ociuhandu has joined #openstack-meeting15:25
*** donghao has joined #openstack-meeting15:28
*** ociuhandu has quit IRC15:30
*** ociuhandu has joined #openstack-meeting15:31
*** mattw4 has joined #openstack-meeting15:32
*** tesseract has quit IRC15:33
*** donghao has quit IRC15:33
*** gyee has joined #openstack-meeting15:34
*** lpetrut has quit IRC15:35
*** ociuhandu has quit IRC15:36
*** ociuhandu has joined #openstack-meeting15:42
*** rpittau is now known as rpittau|afk15:42
*** ociuhandu has quit IRC15:46
*** ociuhandu has joined #openstack-meeting15:49
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Oct  1 16:00:18 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
slaweqlet's start16:02
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:02
slaweq(for later use)16:02
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqnjohnston update python 3 stagium etherpad for bagpipe16:02
njohnstonI did not get to that; as we talked about yesterday I got stuck debugging the tempest jobs16:03
slaweqnjohnston: no problem16:03
slaweqas I said yesterday, I will check this failing tempest job this week16:03
slaweqand I can than update this etherpad if You want16:04
njohnstonThat would be great, thanks16:04
slaweqsure, np16:04
*** macz has joined #openstack-meeting16:04
slaweq#action slaweq to fix networking-bagpipe python3 scenario job and update etherpad16:05
slaweqok, next one16:05
slaweqslaweq to invesigate issue with  neutron.tests.functional.agent.linux.test_iptables.IptablesManagerTestCase.test_tcp_output16:05
slaweqI looked into this but I didn't found anything clearly wrong in logs16:05
slaweqit also happend only this one time in last 30 days16:06
slaweqso I gave up on this, at least for now16:06
slaweqif this will happend more often, I will report bug and work on it once again16:06
slaweqnext one:16:07
slaweqralonsoh to take a look at failing neutron.tests.functional.agent.linux.test_bridge_lib.FdbInterfaceTestCase.test_add_delete(no_namespace16:07
ralonsohslaweq, yes, the problem is solved here16:07
ralonsoh(i'll find it)16:08
slaweqralonsoh: sure :)16:08
slaweqmost important that it's solved now16:08
ralonsohyes, the problem was in the VXLAN interfaces16:09
bcafarelah the tests reusing the same ID?16:09
ralonsohyou can't have more than one vxlan interface in the same VTEP with the same ID16:09
ralonsohplease, go on, i'll find the patch16:09
slaweqok, thx a lot16:09
slaweqso next one16:09
slaweqslaweq to ask rubasov if he can check neutron.tests.fullstack.test_agent_bandwidth_report.TestPlacementBandwidthReport.test_configurations_are_synced_towards_placement16:09
ralonsohbcafarel, exactly, thanks!16:10
slaweqthx bcafarel for link16:10
slaweqand thx ralonsoh for the fix :)16:10
slaweqaccording to last mentioned action item, lajoskatona looked into this16:10
slaweqbut he also couldn't reproduce this issue and it didn't happend since last week anymore16:11
slaweqso for now we are not working on this anymore16:11
slaweqand the last one from last week:16:11
slaweqslaweq to investigate neutron.tests.fullstack.test_l3_agent.TestLegacyL3Agent.test_mtu_update16:11
*** ociuhandu has quit IRC16:11
slaweqvery similar case, I couldn't find anything clearly indicating issue in logs16:11
slaweqand this didn't happend anymore according to logstash16:12
slaweqso I didn't bother more with this for now16:12
slaweqok, that's all actions from last week which I have today16:12
slaweqany questions/comments?16:12
ralonsohI don't think we should expend more time on this test16:13
ralonsoh(for now)16:13
ralonsohand, btw, we have a patch to force the MTU status16:13
ralonsohso maybe we can wait16:13
ralonsoh(force ==> not null)16:13
slaweqyes, I remember that patch16:13
slaweqI will not spent more time on it, I have other things to do16:14
slaweqlet's hope it will not happend anymore ;)16:14
bcafarel:) yes especially with the not null MTU patch getting close16:15
slaweqok, let's move on16:15
slaweqnext topic16:15
slaweq#topic Stadium projects16:15
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:15
slaweqPython 3 migration16:15
slaweqetherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:15
njohnstonwe got an update from yamamoto yesterday, and we already talked about bagpipe16:16
njohnstonI don't see lajoskatona on this channel16:16
slaweqand I think that lajoskatona is slowly working on odl16:17
slaweqMy biggest concern for now related to this topic is midonet16:17
slaweqas it don't even supports Ubuntu Bionic yet16:17
*** lajoskatona has joined #openstack-meeting16:17
slaweqhi lajoskatona16:18
njohnstonthanks for joining lajoskatona16:18
lajoskatonaNo problem16:18
*** e0ne has quit IRC16:18
njohnstonso we were talking about https://etherpad.openstack.org/p/neutron_stadium_python3_status16:18
njohnstonhow do things fare with networking-odl?16:18
lajoskatonaJust a moment I collect my thughts :-)16:19
njohnstonof course!16:19
lajoskatonaSo: The voting jobs are running on python3 now16:19
lajoskatonaWith the non-voting we have issues integrating ODL with latest openstack16:20
njohnstonWe had defined the non-voting jobs as being out of scope anyway16:20
njohnstonso if all the voting jobs are on python3 then networking-odl is done16:21
slaweqyes, so if we have voting jobs running on py3 than we can mark it as done16:21
lajoskatonanjohnston: yes few days ago we discussed with slaweq, but anyway16:21
slaweqlajoskatona: sorry, I may forgot :/16:21
lajoskatonaslaweq, njohnston: ok, and I continue with local team to make the other jobs working and perhaps later voting again16:22
*** lpetrut has joined #openstack-meeting16:22
lajoskatonaslaweq: it was perhaps last week, so long-long time ago ;)16:22
slaweqlajoskatona: sure, so for now I think we can mark networking-odl as done ion etherpad16:22
slaweqlajoskatona: LOL, yes16:22
lajoskatonaslaweq: thanks16:22
slaweqlajoskatona: thx for working on this and for an update16:22
lajoskatonaslaweq: I am happy to make thing working :-)16:23
njohnstonthanks veyr much lajoskatona!16:23
slaweqok, let's move on16:23
slaweqnext is16:23
slaweqtempest-plugins migration16:24
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo16:24
slaweqneutron-dynamic-routing patch for "phase1" https://review.opendev.org/#/c/652099 was just merged finally16:24
slaweqthx tidwellr for this16:24
slaweqso now we only need to delete those tests from neutron-dynamic-routing repo and use job defined in neutron-tempest-plugin16:25
slaweqexcept that we still need vpnaas which is on mlavalle16:25
*** ociuhandu has joined #openstack-meeting16:25
slaweqand I know that he is willing to help with this16:25
slaweqthat's all from my side16:26
slaweqany other questions/comments regrading stadium projects?16:26
slaweqok, so let's move on16:27
slaweq#topic Grafana16:27
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:27
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:27
slaweqtbh for me grafana looks to good this week ;)16:28
ralonsohbetter than previous weeks16:28
slaweqmuch better16:28
slaweqand maybe because of that we also quite fast released rc1 without big problems16:29
njohnstonthe ironic and openstacksdk cross-gating jobs look totally healthy now, should we mark them as voting?16:29
*** ociuhandu has quit IRC16:29
slaweqnjohnston: I'm not sure16:29
slaweqwe can discuss about it but IIRC in Denver we agreed to add jobs from other projects as non-voting only16:30
njohnstonok thats fine16:30
slaweqbut of course it would be better to have it voting as it is much more effective to prevent breaking changes16:31
slaweqfrom the other hand, we are getting more dependent on other projects with our gating16:31
slaweqIMO let's keep them as non-voting for now16:32
slaweqif other team will ask to promote such job to be voting, we can talk about it16:32
slaweqwhat do You think?16:32
*** ricolin has quit IRC16:33
slaweqok, let's move on than16:33
slaweqI don't have any new issues for functional/fullstack jobs now16:34
slaweqso let's go directly to16:34
slaweq#topic Tempest/Scenario16:34
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:34
slaweqregarding scenario jobs, I have only one info to share16:34
slaweqthere was an issue in networking-ovn which caused random failures in trunk_subport_lifecycle test16:35
slaweqbut it should be fixed when https://review.opendev.org/#/c/685206/ will be merged16:35
slaweqso if You will see such test failed in networking-ovn-tempest-dsvm-ovs-release, that's the reason16:35
*** jlibosva has quit IRC16:36
slaweqand that's all from my side16:36
slaweqit is really much better this week with ci imo16:36
slaweqdo You have anything else to talk about?16:36
njohnstonall good here16:36
slaweq#topic On Demand16:37
*** openstack changes topic to "On Demand (Meeting topic: neutron_ci)"16:37
slaweqI have one more small announcement16:37
slaweqI was reviewing list of Neutron lieutenants recently, and I talked with hongbin about his testing lieutenant role16:37
slaweqhe confirmed me that he don't have enough time for it16:37
slaweqso I asked ralonsoh if he can take care of it16:38
slaweqand ralonsoh accepted to be testing liuetenant16:38
ralonsoha joke!!16:38
njohnstoncongrats ralonsoh!  May your grafanas always be flat and low.16:38
slaweqYou got me :P16:38
ralonsohnjohnston, hahahaha16:39
slaweqso, I will update this docs in next few days as I also want to confirm/make some other changes to it16:39
slaweqbut I wanted to announce it here already16:39
slaweqand Thank You ralonsoh for taking care of it16:39
ralonsohmy pleasure16:39
slaweqand that's all from me for today16:40
slaweqif You don't have anything else, I can give You back 20 minutes16:40
njohnstonI wonder if the infra liaison and the testing liaison might do well to be combined into one role16:40
njohnstonsince the overlap between infra issues and testing issues is very large16:41
slaweqnjohnston: good point16:41
slaweqTBH, in last cycle I wasn't testing liuetenant but I was taking care a lot of ci and about infra too16:41
slaweqralonsoh: do You want to take care both of those roles?16:42
njohnstonyes, I was thinking about all that you did when I had that idea16:42
slaweqralonsoh: thx a lot16:42
slaweqso I will update this one too :)16:43
slaweqand thx njohnston for raising this16:43
slaweqok, anything else for today?16:44
slaweqlast call :)16:44
slaweqok, have a nice day16:44
slaweqand thx for attending16:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:45
openstackMeeting ended Tue Oct  1 16:45:06 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-10-01-16.00.html16:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-10-01-16.00.txt16:45
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-10-01-16.00.log.html16:45
*** lajoskatona has left #openstack-meeting16:51
*** armax has quit IRC17:06
*** yamamoto has joined #openstack-meeting17:15
*** yamamoto has quit IRC17:19
*** enriquetaso has quit IRC17:21
*** tssurya_ has quit IRC17:22
*** raildo has quit IRC17:26
*** raildo has joined #openstack-meeting17:26
*** ralonsoh has quit IRC17:27
*** raildo has quit IRC17:29
*** donghao has joined #openstack-meeting17:29
*** raildo has joined #openstack-meeting17:30
*** ekcs has joined #openstack-meeting17:30
*** lpetrut has quit IRC17:31
*** donghao has quit IRC17:34
*** e0ne has joined #openstack-meeting17:35
*** rubasov has joined #openstack-meeting17:36
*** igordc has joined #openstack-meeting17:37
*** jamesmcarthur has quit IRC17:38
*** armax has joined #openstack-meeting17:47
*** jamesmcarthur has joined #openstack-meeting17:48
*** artom has quit IRC17:55
*** raildo_ has joined #openstack-meeting17:57
*** jamesmcarthur has quit IRC17:59
*** jamesmcarthur has joined #openstack-meeting17:59
*** raildo has quit IRC17:59
*** whoami-rajat has quit IRC18:02
*** jamesmcarthur has quit IRC18:04
*** artom has joined #openstack-meeting18:10
*** psachin has quit IRC18:10
*** psachin has joined #openstack-meeting18:12
*** artom has quit IRC18:15
*** artom has joined #openstack-meeting18:17
*** e0ne has quit IRC18:17
*** psachin has quit IRC18:17
*** Shrews has joined #openstack-meeting18:19
*** jamesmcarthur has joined #openstack-meeting18:19
*** jamesmcarthur has quit IRC18:23
*** ociuhandu has joined #openstack-meeting18:34
*** ociuhandu has quit IRC18:37
*** ociuhandu has joined #openstack-meeting18:39
*** ociuhandu has quit IRC18:46
*** AJaeger has joined #openstack-meeting18:46
*** ociuhandu has joined #openstack-meeting18:46
*** jamesmcarthur has joined #openstack-meeting18:47
*** brinzhang_ has joined #openstack-meeting18:51
*** brinzhang_ has quit IRC18:51
*** brinzhang_ has joined #openstack-meeting18:51
*** brinzhang_ has quit IRC18:52
*** brinzhang_ has joined #openstack-meeting18:52
*** brinzhang has quit IRC18:54
*** andrebeltrami has joined #openstack-meeting18:55
clarkbhello anyone else here for the infra meeting?19:00
AJaegerhi clarkb !19:00
clarkbAJaeger: hello!19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Oct  1 19:01:13 2019 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-September/006488.html Our Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbNothing major to announce. I'll be out thursday but otherwise I'm back to business as usuall after traveling last week19:02
clarkbmnaser launched a zuul service on vexxhost at ansiblefest last week. That might be worth announcing :)19:02
clarkb#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-09-17-19.01.txt minutes from last meeting19:03
clarkbWe don't have any actions there and its been a while since the last meeting and half of us have been traveling and focused on other things for a bit too19:04
clarkbI do see the ianw seems to have written the spec for replacing the static server19:04
clarkbwhcih wasn't called out as a specific action but worth noting and we'll get to that a bit later in the agenda19:04
clarkb#topic Priority Efforts19:05
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:05
clarkb#topic OpenDev19:05
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:05
clarkbI poked around gitea a bit more after some guidance from upstream and found that all git process forks in gitea should be timed out already19:06
clarkbthat coupled with the lack of gitea issues that we've seen recently make me wonder if perhaps the disk problems we were having intermittently may have been an underlying cause of slowness?19:06
*** njohnston has quit IRC19:07
clarkbI need to review logs again but it is possible that things are happy as is and we need to monitor for those disk issues instead19:07
clarkbI also found a bug for the "its slow to browse large repos" issue19:07
*** ociuhandu has quit IRC19:07
clarkbupstream seems well aware of it and there are a couple of avenues being investigated for improving this19:07
clarkbI think this topic will likely make good conversation in shanghai19:08
ianwdevstack has a periodic job that walks repos looking for plugins which occasionally gets a 500 ... it was then reporting spurious changes to documentation (https://review.opendev.org/#/c/684434/).  might be one to monitor19:08
*** e0ne has joined #openstack-meeting19:08
clarkb#link https://github.com/go-gitea/gitea/issues/49119:09
clarkbis the upstream bug for slowness19:09
fungi`time wget -qO/dev/null https://opendev.org/openstack/nova` reports real 0m16.175s for me, as a benchmark19:09
fungiapropos of nothing in particular19:09
clarkbianw: good to know. I think 500s are what we want (at least rather than spending hours trying to respond to a request causing requests to backup and then we OOM)19:10
clarkbthat bug in particular has some good insight into why it is slow19:10
clarkbit basically scans the entire history for everything19:10
fungiwow, opened almost 3 years ago too19:11
clarkbfungi: yup and still active as of a couple weeks ago19:11
clarkbthe last opendev related item I wanted to bring up is I haven't yet drafted that email re governance changes19:12
clarkbthat and ptg stuff are high on my list this week now that things should be going back to normal for me19:12
clarkbany other opendev related topics?19:12
ianw"The previous gitea web ui would take > 3 hours to load" ... that's some dedicated testing :)19:13
fungiwas there any pending followup on https://github.com/go-gitea/gitea/issues/8146 then?19:13
clarkbfungi: I asked them for help further debugging the slowness but considering we've been stable (from what I've seen) its possible that the issue has largely gone away. But I need to double check logs for OOMs as well as really slow requests19:14
fungiahh, yeah, okay19:15
clarkb#topic Update Config Managment19:16
*** openstack changes topic to "Update Config Managment (Meeting topic: infra)"19:16
clarkbmordred: I know you've been traveling like some of us, but are we in a position now to try deploying review-dev with our docker image?19:16
clarkbI expect that we are really close to that given the changes that have been reviewed and merged to the docker image building for gerrit19:17
clarkbI'm guessing mordred is either eating dinner or jetlagged or both :)19:18
clarkbAnyone have topics to point out here? ianw perhaps your logrotate changes?19:18
ianwwell the fedora mirror still takes hours and hours to release every time, haven't debugged that further, at this point19:19
ianwhowever, mirror issues  turned out to be a red herring for the centos-8 changes i was debugging, it was actually a problem with yum/dnf/???19:19
*** markvoelker has quit IRC19:21
corvus(tangentially related -- my current focus on zuul-registry is largely driven by a desire to fix reliability issues we've seen with container image builds)19:21
corvus(ie, the more successful we are with things like building/deploying gerrit with docker, the more we'll need this)19:22
clarkb#topic Storyboard19:23
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:23
fungiso i've got some new stuff here19:24
clarkbgo for it19:24
fungithere's a semi-recent feature which the zuul community has been taking advantage of so far19:24
fungiyou can flag a team in sb as a "security team" and then any projects you associate with that team will automatically add access for it to any stories which get marked as security-related19:25
fungithe openstack vmt is starting to make use of it as well, but this raises a self-service challenge19:25
fungiright now, teams can only be created and members added/removed by an sb admin19:25
fungiand shoving an entire rbac into sb would be a ton of new work, so...19:26
fungi#link https://review.opendev.org/685778 Record vulnerability management teams used in SB19:26
*** artom has quit IRC19:26
fungiafter some deliberation the idea of automating group membership and keeping it in yaml is very attractive for a number of reasons19:27
fungiso that change is my proposed schema, before i dive headlong into trying to implement the validation and automation for it19:27
clarkbthat change lgtm19:28
fungii left it open for the potential to use it to define non-security teams as well19:28
AJaegerfungi: change could use some README ;)19:28
fungiAJaeger: a great idea, thanks19:29
fungilike stuff one in the top of the storyboard tree?19:29
AJaegerthat would be fine19:29
fungiwe could probably stand to stick some readmes in other places in our config repos too19:29
fungii considered putting this in opendev/project-config but for now it's probably better off in the same repo as the gerrit/projects.yaml to avoid people having to make correlated changes in too many repos19:30
AJaegerfungi: and/or update top-level README19:30
fungiahh, yeah i can totally do that19:30
fungii figure this would move to and/or get split out at the same time gerrit configuration does19:31
*** donghao has joined #openstack-meeting19:32
clarkbSounds like that is it for storyboard?19:33
clarkb#topic General Topics19:34
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:34
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:34
clarkbfungi: any progress with wiki openid stuff?19:34
funginext phase on the wiki replacement is i think to refresh the current production database and images directory, then work on matching the configuration. i haven't done those things though, no19:34
clarkbThe other item in this is the static.o.o replacement/update/transition19:35
clarkbianw wrote a spec19:35
clarkb#link https://review.opendev.org/683852 Review spec19:35
*** njohnston has joined #openstack-meeting19:35
clarkbAJaeger: thank you for taking a first pass review19:35
AJaegerafter I made first changes, ianw disagreed and so write something up so that we're all on the same page.19:36
clarkbcorvus: ^ that may interest you as I think you suggested it in a meeting a couple weeks ago19:36
AJaegerspec looks good to me, but has two open quesitons19:36
AJaegerso, my ask: Review spec and let's discuss the open questions19:36
ianwyeah, we had discussed parts of this across a few meetings, so this pulls it into one place19:36
clarkb++ I think it would also be good if we can get agreement on this pre summit/ptg19:36
*** donghao has quit IRC19:36
clarkbthen we can bring it up with teams there as necessary19:36
corvuslooks good -- my interest is mostly in getting this in front of the tc so they know about the needs19:38
clarkbwe should be able to merge the spec reasonably quickly (next week?) then we can point the TC to the published version? or do we think we need their input in review too?19:39
ianwin terms of it being mechanical (moving things to volumes, etc) i don't think so19:39
corvusearlier the better i'd say19:39
AJaegerdo we want to figure out the two open questions ourselves? Or need input on those as well?19:39
fungii expect as long as the end result is sites published in the form they are now, all the backend and automation is mostly implementation detail they won't care about19:40
ianw... but if there's policy things around how much of this is affected by opendev.org in the future, etc, that may be different19:40
fungibut yeah, it's still good to get them to say that one way or the other19:40
clarkbI can bring it up in office hours later today (local time)19:41
corvusto be clear, i want to make sure that the openstack project is aware of the operational cost of this and that it's an opportunity to contribute to the commons.19:41
clarkbcorvus: yup, that was why I figured the published version might be easiest, but early feedback is always nice19:42
corvus(most of these sites were set up so that we could retire the wiki; instead we're now maintaining the wiki and these sites)19:42
clarkbThat takes us to the last agenda item. PTG Planning19:44
corvusthe ssl question is a very interesting one19:44
fungiare there particular tasks in the spec which would be good to call out as in need of additional assistance, or is it more a general point that we'd welcome assistance in maintaining all of it?19:44
corvusi still have no interest in dealing with a manual dns system19:44
clarkbcorvus: I believe that ianw had automated the dns changes required for rax so it isn't manual19:45
clarkbbut does require using their one off api19:45
corvusclarkb: not the point19:45
corvusthat's the point19:45
corvusunless we can come up with some way to manage openstack.org dns collaboratively with the foundation through code review, i want to stay away from it19:45
fungiyeah, we've got a dns management solution built on revision control, ci and all free software. the project wanting to use the same domain as the foundation is the challenge presently19:46
clarkbcorvus: in this case at least most of the changes are to a different domain (or can be)19:46
clarkbyou do need the glue type records in the parent domain that point to the acme hosting domain19:46
clarkb(not a perfect solution for sure)19:46
corvusi just don't think that opendev should be managing openstack.org stuff if we can't do it using the system we've constructed19:47
corvusso maybe what we can offer is some more neutrally branded hosting?19:48
corvusalong the lines of tarballs.opendev.org and docs.opendev.org19:48
clarkbfungi: re tasks which people can pick up I believe the updates to publishing jobs in particular should be doable by anyone that has edited zuul jobs before so could be a good place to start19:48
fungiclarkb: yeah, that makes sense19:48
corvusand maybe this is a bigger question than i originally thought :/19:49
fungii think it's a great question to pose to them19:49
*** bbowen has quit IRC19:49
AJaegerclarkb: I pushed the first three changes for jobs, that will help others to do the rest...19:50
fungibut yes, suggesting all openstack documentation and similar online content be redirected to and served from a different domain is a significant change, so i would expect a lot of concern, at least initially19:50
clarkbAJaeger: thanks!19:50
AJaegerclarkb: https://review.opendev.org/#/q/status:open+project:openstack/project-config+branch:master+topic:static-services19:51
clarkbcorvus: maybe we can write up those concerns as comments on the change and that can be a piece that the TC offers feedback on?19:51
ianwclarkb: (on publishing jobs) yep, although if we do the per-project volumes we do need to create them manually as there's no facility to do that19:52
ianwI guess that is really what i was calling out as "Perhaps there are plans afoot for OpenDev-ing some of these bits?19:52
ianw    Is there some sort of succession planning?"19:52
fungii personally think redirecting governance.openstack.org to docs.opendev.org/openstack/governance would be fine, and even like the idea of maybe finally being able to serve all those disparate openstack static content sites from a single logical tree19:53
clarkbits possible we may also want to do this in stages too19:54
*** brinzhang has joined #openstack-meeting19:54
clarkbconvert to afs hosted thing for what we currently have using the existing certs19:54
ianwahh, files02 ... i'm not sure i considered this host19:54
clarkband decouple opendevifying this from the switch to afs19:54
ianwis that deployed via puppet?19:55
clarkbthere is a files.pp iirc19:55
ianwoh wait, files02.openstack.org == files.opendev.org == files.openstack.org19:56
fungiit's unclear to me what in particular about the static files webserver would benefit from containerization, but configuring it with ansible instead of puppet still might19:56
ianwi mean docs.opendev.org ... there's only one "files" server though, right?19:56
clarkbianw: ya there is only one files server19:57
clarkb02 was a replacement for 01 not running side by side19:57
clarkband no openstack vs opendev yes as far as I know19:57
corvuswe can load-balance it if we want19:57
*** brinzhang_ has quit IRC19:57
clarkbquick timecheck we only have a few minutes left19:57
ianwok, right, got it :)  so yeah, the idea of starting an ansible-only host to migrate these things to separately is still in play19:57
clarkbI wanted to mention that there is a PTG schedule proposed starting at this thread #link http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009733.html Proposed schedule thread19:57
clarkb#link https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-201919:58
clarkbI'm going to start adding content to that this week I hope19:58
clarkbalso as a heads up I don't actually have a visa yet and am told that I won't know more about that until mid october :/19:58
clarkbAnd we are just about at time now.19:59
*** slaweq has quit IRC19:59
clarkbThanks everyone. We can continue the afsification discussion on that review or in #openstack-infra19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
corvusi left some quick thoughts there20:00
openstackMeeting ended Tue Oct  1 20:00:08 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-01-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-01-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-01-19.01.log.html20:00
*** AJaeger has left #openstack-meeting20:00
*** markvoelker has joined #openstack-meeting20:00
*** Shrews has left #openstack-meeting20:01
*** brinzhang_ has joined #openstack-meeting20:02
*** brinzhang has quit IRC20:05
*** jamesmcarthur has quit IRC20:07
*** enriquetaso has joined #openstack-meeting20:09
*** kopecmartin is now known as kopecmartin|off20:11
*** jamesmcarthur has joined #openstack-meeting20:16
*** enriquetaso has quit IRC20:17
*** e0ne has quit IRC20:27
*** pcaruana has quit IRC20:33
*** yamamoto has joined #openstack-meeting20:37
*** enriquetaso has joined #openstack-meeting20:41
*** trandles has joined #openstack-meeting20:47
*** oneswig has joined #openstack-meeting20:57
*** martial has joined #openstack-meeting20:57
*** whoami-rajat has joined #openstack-meeting20:58
oneswig#startmeeting scientific-sig21:00
openstackMeeting started Tue Oct  1 21:00:17 2019 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"21:00
openstackThe meeting name has been set to 'scientific_sig'21:00
oneswigAfternoon all21:00
martialhello everybody :)21:00
oneswig#chair martial21:00
openstackCurrent chairs: martial oneswig21:00
oneswigWhat's new?21:01
oneswigI've been working on some follow-up for this project21:02
oneswig#link federated Ceph for the Euclid space telescope https://indico.cern.ch/event/765214/contributions/3517141/attachments/1908894/3153554/2019-09-17-TelferGarbutt-Ad-hoc-Filesystems.pdf21:02
oneswigTurns out our Ceph deployment is not at all balanced in its data distribution21:03
trandlesI'm kinda here for the meeting but might get interrupted...so my one question is for martial. Is everything sorted for the SC19 BoF? I'll be there on a full technical pass this year.21:03
oneswighad OSD occupancy ranging ~1% - ~94%21:03
*** rbudden has joined #openstack-meeting21:03
oneswigtrandles: thanks for the reminder, had forgotten to buy a ticket, better put that on the list...21:03
martialyou know, I need to do that too :)21:04
oneswigtrandles: do you get your money's worth from the full pass?21:06
trandlesmartial: we don't need to submit a revised proposal or anything?21:07
martialtrandles: I ned to confirm attendance but beyond that I believe we have everything needed21:07
trandlesoneswig: yeah, I'll be able to attend all the talks I like21:07
trandlesUsually I'm on exhibitor and can't do anything but attend meetings and stay in the exhibit hall :(21:07
oneswigtrandles: I only went to SC16 previously and I think that's what I had too.21:08
*** ociuhandu has joined #openstack-meeting21:08
*** yamamoto has quit IRC21:08
martialoneswig: so what about that OSD? :)21:11
*** bbowen has joined #openstack-meeting21:11
*** yamamoto has joined #openstack-meeting21:11
oneswigha.  I'm working hard to get this cluster reweighted to the point where it resembles balance.  Still nowhere near.21:12
*** ociuhandu has quit IRC21:12
oneswigI wonder if there's a way in Ceph to establish how big each PG is, some of these ones do seem quite chunky.21:13
oneswigGot another interesting problem, in that the MDS has halted processing CephFS, possibly due to nearfull OSDs (hopefully - because that's something I can fix)21:13
oneswigThe MDS claims to be "behind on trimming" and ballooning in memory21:14
oneswigstill working on that bit.  I was hoping jomlowe would have some wise words on it...21:15
martialwas hoping to ask Cloud Federation question with jmlowe as well21:16
oneswigmartial: what's up there?21:17
martialmostly about metadata exchange solutions21:18
martialand understand how xseed does it21:19
oneswigMike and Bob Budden gave a talk once on a way of using IIRC Murano to share application images between clouds...21:21
martialmight ask that of them next time I see them21:24
oneswigOK, I think I need to shut down for the night... anything more to raise?21:24
martialall good on my end21:24
trandlesrbudden: PING! You're being talked about21:24
oneswigha, IRC ears are burning21:25
oneswigOK I'm going to head off before he notices and corrects my slanders! :-)21:25
trandlesI have nothing. Been working on Ironic stuff. We should have our new cloud engineer starting very soon. Hope to have some new developments to discuss in Denver.21:25
oneswigtrandles: good to hear you filled the post21:25
oneswigShould be an exciting role, no doubt!21:26
martialcool :)21:26
trandlesFingers crossed it goes to plan21:26
oneswigbtw trandles: am somewhat proud of this recent work on Ironic https://www.stackhpc.com/bespoke-bare-metal.html21:27
trandlesThx for the link, I'll read up21:27
oneswigexcellent.  Until next time y'all21:28
*** oneswig has quit IRC21:28
*** donghao has joined #openstack-meeting21:34
*** donghao has quit IRC21:38
*** munimeha1 has quit IRC21:51
*** mriedem has quit IRC21:56
*** trandles has left #openstack-meeting22:02
*** ekcs has quit IRC22:42
*** jamesmcarthur has quit IRC22:48
*** yamamoto has quit IRC22:57
*** yamamoto has joined #openstack-meeting23:01
*** enriquetaso has quit IRC23:01
*** macz has quit IRC23:05
*** macz has joined #openstack-meeting23:07
*** macz has quit IRC23:10
*** raildo_ has quit IRC23:21
*** jamesmcarthur has joined #openstack-meeting23:32
*** rcernin has joined #openstack-meeting23:33
*** donghao has joined #openstack-meeting23:36
*** martial has quit IRC23:37
*** markvoelker has quit IRC23:38
*** ykatabam has joined #openstack-meeting23:38
*** yamamoto has quit IRC23:39
*** yamamoto has joined #openstack-meeting23:39
*** bbowen_ has joined #openstack-meeting23:39
*** bbowen has quit IRC23:41
*** donghao has quit IRC23:41
*** yamamoto has quit IRC23:43
*** markvoelker has joined #openstack-meeting23:44
*** yamamoto has joined #openstack-meeting23:48
*** yamamoto has quit IRC23:52
*** yamamoto has joined #openstack-meeting23:55

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