Tuesday, 2018-12-18

*** macza has quit IRC00:13
*** macza has joined #openstack-meeting00:15
*** macza has quit IRC00:20
*** Liang__ has joined #openstack-meeting00:37
*** absubram has quit IRC00:38
*** Liang__ is now known as LiangFang00:40
*** erlon_ has joined #openstack-meeting00:48
*** iyamahat has joined #openstack-meeting00:48
*** iyamahat has quit IRC00:50
*** dmellado has joined #openstack-meeting00:53
*** iyamahat has joined #openstack-meeting00:56
*** stevebaker has joined #openstack-meeting01:03
*** bobh has joined #openstack-meeting01:08
*** jamesmcarthur has joined #openstack-meeting01:14
*** gyee has quit IRC01:18
*** jamesmcarthur has quit IRC01:19
*** bobh has quit IRC01:20
*** yikun has joined #openstack-meeting01:27
*** iyamahat_ has joined #openstack-meeting01:39
*** iyamahat has quit IRC01:42
*** hongbin has joined #openstack-meeting01:42
*** mhen has quit IRC02:22
*** mhen has joined #openstack-meeting02:25
*** hongbin_ has joined #openstack-meeting02:28
*** hongbin has quit IRC02:29
*** bobh has joined #openstack-meeting02:38
*** psachin has joined #openstack-meeting02:41
*** iyamahat_ has quit IRC02:52
*** yamahata has quit IRC02:52
*** erlon_ has quit IRC02:57
*** apetrich has quit IRC03:15
*** hongbin has joined #openstack-meeting03:20
*** hongbin_ has quit IRC03:21
*** rcernin has quit IRC03:25
*** rcernin has joined #openstack-meeting03:27
*** rcernin has quit IRC03:28
*** rcernin has joined #openstack-meeting03:28
*** bobh has quit IRC03:34
*** hongbin has quit IRC03:43
*** mriedem has joined #openstack-meeting03:49
*** bobh has joined #openstack-meeting03:51
*** dtrainor_ has joined #openstack-meeting03:57
*** dtrainor_ has quit IRC03:57
*** tpatil has joined #openstack-meeting03:58
samPhi all for masakari04:00
tpatilHi04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Dec 18 04:00:19 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPHi all04:00
samP#topic critical bugs and patches04:00
*** openstack changes topic to "critical bugs and patches (Meeting topic: masakari)"04:01
samPAny bugs or patches need to discuss?04:01
samP#link https://review.openstack.org/#/c/596614/304:01
samPPlease review ^^ for masakari-dashboard04:01
tpatilSure04:01
tpatilI have reviewed three patches submitted by takahara.kengo as discussed in the last week04:03
samPtpatil: Thanks04:03
tpatilAlso, Shilpa has proposed patches for sending notifications for API changes04:04
tpatil#link : https://review.openstack.org/#/q/status:open+project:openstack/masakari+branch:master+topic:bp/notifications-in-masakari04:04
*** sagara has joined #openstack-meeting04:04
tpatilCI jobs are failing, she will look into this issue04:05
samPtpatil: Got it. Thanks04:05
samPI will review those04:05
samPAny other patches or bugs?04:06
*** tashiromt has joined #openstack-meeting04:06
sagarasamP: Hi, from my side, nothing.04:07
samPMoving to next topic, please bring up any issues in any time in this meeting.04:07
samPsagara: thanks04:07
samP#topic Stein Work Items04:07
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)"04:07
samPPlease share any updates on Stein Work Items04:07
tpatilNotification related patches are up for review04:07
tpatilRecovery workflow events: In progress04:08
samPtpatil: thanks04:10
samPnothing to share from my side.04:11
tpatilhttps://bugs.launchpad.net/masakari/+bug/180851304:11
openstackLaunchpad bug 1808513 in masakari "Incorrect payload in notification results in running status forever" [Undecided,New]04:11
tpatilWorking on fixing this issue04:12
*** bobh has quit IRC04:12
samPtpatil: Thanks04:13
samPif no other topics to share, we may finish the meeting early today.04:15
sagarasamP: I have no topic. Bye.04:17
tpatilsamP: nothing from my end as well04:17
samPPlease use openstack-discussion ML or #openstack-masakari @freenode IRC for further discussion04:18
samPsagara: tpatil thanks04:18
samPlet's end today's meeting04:18
samPThank you all!04:18
samP#endmeeting04:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:18
openstackMeeting ended Tue Dec 18 04:18:37 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-12-18-04.00.html04:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-12-18-04.00.txt04:18
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-12-18-04.00.log.html04:18
*** Bhujay has joined #openstack-meeting04:20
*** sagara has quit IRC04:20
*** Bhujay has quit IRC04:21
*** Bhujay has joined #openstack-meeting04:21
*** Bhujay has quit IRC04:22
*** Bhujay has joined #openstack-meeting04:23
*** tpatil has quit IRC04:24
*** rf0lc0 has joined #openstack-meeting04:28
*** rfolco has quit IRC04:29
*** mriedem has quit IRC04:31
*** hle2 has joined #openstack-meeting04:35
*** hle2 has quit IRC04:36
*** janki has joined #openstack-meeting04:50
*** armax has quit IRC05:07
*** mahatic has joined #openstack-meeting05:08
*** sridharg has joined #openstack-meeting05:08
*** kmalloc has quit IRC05:14
*** iyamahat has joined #openstack-meeting05:24
*** diablo_rojo has quit IRC05:25
*** mgagne_ has quit IRC06:35
*** mgagne has joined #openstack-meeting06:39
*** gouthamr has quit IRC06:55
*** cheng1_ has joined #openstack-meeting06:55
*** iyamahat has quit IRC07:01
*** cheng1_ has quit IRC07:02
*** Luzi has joined #openstack-meeting07:03
*** iyamahat has joined #openstack-meeting07:09
*** e0ne has joined #openstack-meeting07:11
*** apetrich has joined #openstack-meeting07:18
*** imacdonn has quit IRC07:29
*** imacdonn has joined #openstack-meeting07:29
*** dkushwaha_ has joined #openstack-meeting07:45
*** yamahata has joined #openstack-meeting07:53
*** slaweq has joined #openstack-meeting07:53
*** bhagyashris has joined #openstack-meeting07:55
*** kopecmartin|off is now known as kopecmartin07:59
*** longkb has joined #openstack-meeting08:01
dkushwaha_#startmeeting tacker08:01
openstackMeeting started Tue Dec 18 08:01:20 2018 UTC and is due to finish in 60 minutes.  The chair is dkushwaha_. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: tacker)"08:01
openstackThe meeting name has been set to 'tacker'08:01
dkushwaha_#topic Roll Call08:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:01
dkushwaha_who is here for Tacker weekly meeting?08:01
bhagyashrisO/08:04
dkushwaha_hi bhagyashris08:04
bhagyashrisHi08:04
dkushwaha_seems no more members available today08:05
*** apetrich has quit IRC08:06
dkushwaha_#topic Open Discussion08:06
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:06
dkushwaha_bhagyashris, do you have something to discuss ?08:06
bhagyashrisYeah,  just give me one min08:07
dkushwaha_sure08:07
bhagyashrisRegarding : Add VNF to monitor after restarting tacker service08:07
*** noonedeadpunk[h] has joined #openstack-meeting08:07
bhagyashrisSo I have fix the review comments and uploaded patch for community review https://review.openstack.org/#/c/614964/08:08
bhagyashrisAnf this change is made on current master08:08
*** noonedeadpunk has quit IRC08:09
bhagyashrisand yesterday phouc has cherry pick on stable/rocky and uploaded for CG: https://review.openstack.org/#/c/625461/08:09
bhagyashrisSo just wanted to know which one will merge08:10
bhagyashrisOr will be consider08:12
dkushwaha_bhagyashris, i am ok to merge  https://review.openstack.org/#/c/614964 on master, and as  https://review.openstack.org/#/c/625461 is from same on stable/Rocky, so this one will be merged in stable/Rocky.08:13
dkushwaha_although as Phouch suggested, let me try first https://review.openstack.org/#/c/486924 for master08:14
*** phuochoang has joined #openstack-meeting08:14
dkushwaha_bhagyashris, i will test  https://review.openstack.org/#/c/625461 on stable and will merge it first.08:15
bhagyashrisdkushwaha_: yeah me to have same understanding about cherry pick first the change should go on master and then on stable/branch08:15
bhagyashrisdkushwaha_: ok. Thank you :)08:16
bhagyashrisdkushwaha_: Want to discuss regarding : [WIP] Implement VNF monitoring using Mistral https://review.openstack.org/#/c/486924/4808:17
dkushwaha_the suitable wy is  https://review.openstack.org/#/c/486924, so I request to do some deep review of this patch(as it is big enough)08:17
dkushwaha_sure08:18
bhagyashrisdkushwaha_: yeah :). Actually I have tested this patch on my environment and facing one issue at mistral side08:18
*** ralonsoh has joined #openstack-meeting08:19
bhagyashris# link: http://paste.openstack.org/show/737527/08:19
*** hadai has joined #openstack-meeting08:21
bhagyashrisdkushwaha_: yeah this https://review.openstack.org/#/c/486924 will solve the issue but on stable branches the issue will remain as is, so this https://review.openstack.org/#/c/614964 minimal change will help to resolve this08:22
dkushwaha_bhagyashris, thanks for testing patch. I am not sure about the issue, but will check it again08:22
*** liuyulong has quit IRC08:23
bhagyashrisdkushwaha_: Welcome I will check deep in free time :)08:23
*** phuochoang has quit IRC08:23
dkushwaha_i suspect , I made some mistake while resolving merge conflicts, will update the patch after resolving issue and other hardcoded values08:24
bhagyashrisdkushwaha_: Thank you for reviewing vdu_autoheal patch now fixing review comments and upload ASAP :)08:25
dkushwaha_bhagyashris, cool08:25
bhagyashrisdkushwaha_:  ok I will check the new patch set and also test in my environment and will let you know08:26
bhagyashrisThe result08:26
dkushwaha_great08:26
dkushwaha_bhagyashris, anything else to discuss?08:26
bhagyashrisdkushwaha_:  No thats all from my side08:27
bhagyashris:)08:27
dkushwaha_Ok, Thanks for joining meeting. :)08:27
bhagyashris:)08:27
dkushwaha_Closing this meeting for now08:27
dkushwaha_#endmeeting08:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:27
openstackMeeting ended Tue Dec 18 08:27:41 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-12-18-08.01.html08:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-12-18-08.01.txt08:27
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-12-18-08.01.log.html08:27
*** hadai has quit IRC08:35
*** lhinds has quit IRC08:36
*** lhinds has joined #openstack-meeting08:37
*** apetrich has joined #openstack-meeting08:38
*** dkushwaha_ has quit IRC08:42
*** tetsuro has joined #openstack-meeting08:42
*** priteau has joined #openstack-meeting08:47
*** tetsuro has quit IRC08:47
*** tetsuro has joined #openstack-meeting08:48
jiaopengju#startmeeting karbor09:05
openstackMeeting started Tue Dec 18 09:05:21 2018 UTC and is due to finish in 60 minutes.  The chair is jiaopengju. Information about MeetBot at http://wiki.debian.org/MeetBot.09:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:05
*** openstack changes topic to " (Meeting topic: karbor)"09:05
openstackThe meeting name has been set to 'karbor'09:05
jiaopengjuhi, anyone here for karbor weekly meeting?09:05
jiaopengjuSeems no karbor guys here09:07
jiaopengjuNow I am doing dev of the feature ‘cross site backup and resotre’, if anyone else has interest on it, please contact me in karbor irc channel09:09
jiaopengjuI will end the meeting soon09:09
jiaopengju#endmeeting09:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:09
openstackMeeting ended Tue Dec 18 09:09:43 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-12-18-09.05.html09:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-12-18-09.05.txt09:09
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-12-18-09.05.log.html09:09
*** jesusaur has quit IRC09:15
*** rcernin has quit IRC09:18
*** iyamahat has quit IRC09:21
*** jesusaur has joined #openstack-meeting09:22
*** Bhujay has quit IRC09:24
*** a-pugachev has joined #openstack-meeting09:27
*** a-pugachev has left #openstack-meeting09:27
*** arne_wiebalck has quit IRC09:36
*** arne_wiebalck has joined #openstack-meeting09:38
*** a-pugachev has joined #openstack-meeting09:40
*** LiangFang has quit IRC09:45
*** vishalmanchanda has joined #openstack-meeting09:46
*** erlon_ has joined #openstack-meeting09:51
*** Bhujay has joined #openstack-meeting10:02
*** Bhujay has quit IRC10:03
*** Bhujay has joined #openstack-meeting10:04
*** bhagyashris has quit IRC10:04
*** Bhujay has quit IRC10:05
*** Bhujay has joined #openstack-meeting10:05
*** Bhujay has quit IRC10:06
*** Bhujay has joined #openstack-meeting10:07
*** erlon_ has quit IRC10:08
*** ttsiouts has joined #openstack-meeting10:10
*** electrofelix has joined #openstack-meeting10:12
*** yamamoto has quit IRC11:01
*** longkb has quit IRC11:13
*** ttsiouts has quit IRC11:17
*** ttsiouts has joined #openstack-meeting11:18
*** tashiromt has quit IRC11:19
*** ttsiouts has quit IRC11:22
*** longkb has joined #openstack-meeting11:23
*** longkb has quit IRC11:23
*** a-pugachev has left #openstack-meeting11:28
*** erlon_ has joined #openstack-meeting11:32
*** yamamoto has joined #openstack-meeting11:38
*** EmilienM|off is now known as EmilienM11:41
*** Bhujay has quit IRC11:46
*** ttsiouts has joined #openstack-meeting11:47
*** baojg has joined #openstack-meeting11:52
*** Bhujay has joined #openstack-meeting11:52
*** Bhujay has quit IRC11:53
*** Bhujay has joined #openstack-meeting11:53
*** yamamoto has quit IRC11:54
*** yamamoto has joined #openstack-meeting11:54
*** Bhujay has quit IRC11:54
*** Bhujay has joined #openstack-meeting11:55
*** Bhujay has quit IRC11:56
*** Bhujay has joined #openstack-meeting11:56
*** Bhujay has quit IRC11:57
*** Bhujay has joined #openstack-meeting11:58
*** Bhujay has quit IRC11:59
*** Bhujay has joined #openstack-meeting11:59
*** Bhujay has quit IRC12:00
*** Bhujay has joined #openstack-meeting12:01
*** raildo has joined #openstack-meeting12:01
*** tpsilva has joined #openstack-meeting12:06
*** thgcorrea has joined #openstack-meeting12:12
*** janki has quit IRC12:17
*** eharney has joined #openstack-meeting12:33
*** liuyulong has joined #openstack-meeting12:40
*** e0ne has quit IRC12:53
*** yamamoto has quit IRC13:37
*** yamamoto has joined #openstack-meeting13:38
*** yamamoto has quit IRC13:43
*** rf0lc0 is now known as rfolco13:48
*** rubasov has joined #openstack-meeting13:53
*** lajoskatona has joined #openstack-meeting13:56
*** e0ne has joined #openstack-meeting13:57
*** liuyulong_ has joined #openstack-meeting13:59
*** hle2 has joined #openstack-meeting13:59
*** mlavalle has joined #openstack-meeting14:00
*** boden has joined #openstack-meeting14:00
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Dec 18 14:00:12 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
lajoskatonao/14:00
amotokihi14:00
haleybhi14:01
rubasovo/14:01
bcafarelhello14:01
slaweqhi14:01
liuyulong_hi14:01
bodenhowdy14:01
mlavallehello everybody!14:01
mlavallewelcome to our last meeting of the year!14:01
mlavalle#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
mlavalleFirst a reminder that our Stein 2 milestone will be on January 7 - 1114:02
mlavalleSecond there is a proposal by amotoki to release Neutron "Beta"14:03
mlavalleplease remember that in the new model, we don't release necessarily code in the milestone weeks14:03
mlavalleand ecently we have landed some important stuff:14:04
mlavalleryu -> os-ken switch14:04
mlavallepolicy-in-code support framework14:04
mlavalleupgrade-checker framework (which landed or is about to)14:04
mlavalleamotoki: do you want to add something14:05
mlavalle?14:05
*** awaugama has joined #openstack-meeting14:05
*** tidwellr has joined #openstack-meeting14:05
amotokiI hope I covered all imporant things14:05
amotokinothing I need to add14:05
mlavalleany objections from anybody?14:06
bcafarelnone, that's a great "progress" list to end the year!14:06
amotokiah, one thing. note that this is about 'neutron' itself.14:06
*** pgodek has joined #openstack-meeting14:06
mlavalleamotoki: good ctach!14:07
amotokiif you need a beta release for stadium projects, it can be released separately.14:07
*** e0ne has quit IRC14:07
mlavalleok, so lets wait for https://review.openstack.org/#/c/615196/ to land and then we can go ahead with the release, agree?14:08
slaweq+114:08
amotoki+114:08
mlavallecool14:09
mlavalleThe other thing we wanted to discuss today (outside our normal topics) is Ocata branch to be put under EM (Extended Maintenance)14:09
mlavallebcafarel: do you want to add to this?14:10
bcafareljust some quick context14:10
bcafarel#link https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance14:10
bcafarelfor those scared, extended maintenance is not end-of-life yet :)14:10
bcafarelwe will still accept patches and get them in as time permits (I see it as "best effort" support)14:11
mlavallecorrect, we can still merge fixes when they are deemed necessary14:11
mlavalleand bandwidth allows14:11
amotokiit means the upsream developer team does not take care of such branches much and no new release is coming, while we accept backports14:11
amotokisomeone interested in maintaining some branch can raise their hand14:12
*** psachin has quit IRC14:12
mlavallethat's an excellent point amotoki14:12
mlavalleany objections from the team to take this step?14:13
slaweqit's fine for me14:13
mlavalleok, we will move ahead with this.14:14
mlavallebcafarel: do you have anything you need for this?14:15
mlavalleeverything^^^14:15
bcafarel:)14:15
amotokiit might be better to ask maintainers of driver projects like netwokring-ovn14:15
mlavalleamotoki: message to the ML?14:16
bcafarelone question remaining, as said we plan to do a final ocata release (before tagging), should we do it for neutron only or include stadium? (stadium projects have mostly test fixes, from amotoki's findings)14:16
amotokimlavalle: yes, I think so. as they usually cut their release separately14:16
bcafarelack, a heads-up warning message sounds like a good idea14:17
mlavallebcafarel: so let's send a message to the ML and lets ask this question there. makes sense?14:17
bcafarelmlavalle: good for me :)14:17
mlavalleok, I think we can move on then....14:18
amotokisounds good14:18
mlavalle#topic Blueprints14:18
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:18
mlavalleDoes anybody have updates on blueprints?14:19
tidwellrmlavalle: I do14:20
bcafarelfeedback on http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000796.html I guess?14:20
tidwellrbcafarel: yes, I'm not sure if any of that made sense :)14:21
*** yamamoto has joined #openstack-meeting14:22
mlavalletidwellr: I need to go over that slowly and carefully. I'll provide feedback today or tomorrow. Does that help?14:22
tidwellrmlavalle: that would be great, I've got subnet onboard in a pretty good spot now, the last outstanding bit is what to do with what I think is a mistake in the API definition14:23
tidwellrI'm unclear with how to handle this since we merged the API definition so long ago14:23
mlavalleok, let's do that. I encourage other to take a look and lend a helping hand14:23
slaweqtidwellr: sorry, I was reading Your email and I forgot to answer to it14:24
* bcafarel notes to finish his reply email to that too14:24
slaweqtidwellr: I will do it tomorrow morning or today evening14:24
tidwellrI've been meaning to just push a review up to neutron-lib that removes the troublesome bits from the definition just to jump-start a discussion14:24
tidwellrthanks everyone, that's all I had14:25
mlavalletidwellr: if you have the patch ready, go ahead and push it. it will provide more context to the email14:25
tidwellrI'll push that up today14:25
mlavallegreat14:26
*** mriedem has joined #openstack-meeting14:27
mlavalleyamamoto: you around?14:27
mlavallemaybe not14:28
mlavallelet's move on14:28
mlavalle#topic neutron-lib14:28
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:28
mlavalleLet's talk about neutron-lib out of our normal order, so boden can take care of his paternal duties14:28
boden:) thanks14:29
bodenjust wanted to mention that I've recently updated the neutron meeting wiki for neutron-lib https://wiki.openstack.org/wiki/Network/Meetings#Neutron-lib.2C_planned_refactoring_and_other_impacts14:29
bodenthere's a section titled "PATCHES THAT NEED REVIEWS"... if folks get bored and want to help with reviews, that's probably the best place to start14:30
mlavalleahh, very good14:30
bodenany questions/comments on that?14:30
mlavalleno, I think this will be helpful14:30
bodenok well 1 last thing that has nothing to do with neutron-lib14:30
mlavalleI will go over that section between today and tomorrow14:30
bodenI threw out a patch to test the lower-constraints with python 3.6 https://review.openstack.org/#/c/625922/14:31
bodenjust to make sure things won't break... details in the commit message14:31
bodenand that's it from me unless there are comments/questions14:31
mlavalleboden: thanks for that patch!14:32
bodenmlavalle np... it did break some other projects for the record :)14:32
mlavallelet's keep an eye on it14:32
mlavalleok, let's move on14:32
mlavalle#topic Community goals14:33
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:33
mlavalleFirst of all, I want to congratulate and THANK amotoki, slaweq and njohnston for their hard work on this goals14:33
mlavalleas mentioned before, https://review.openstack.org/#/c/615196 seems that will merge soon14:34
mlavalleand with that we can claim victory with upgrade checks14:35
slaweqyes :)14:35
mlavalleand with policy in code, we are set, right amotoki?14:35
amotokire: policy-in-code, thanks for your review on the first basic work in neutron.14:35
amotokiin the neutron repo side, I plan to send several clean up patches (including docs)14:35
amotokiI also sent a mail on the progress to the list http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001019.html14:36
amotokiI hope individual project teams review and test pending policy-in-code patches14:36
mlavalleperfect14:37
amotokithat's all from me14:37
mlavalleThanks for your hard work14:38
mlavallelet's move on14:38
mlavalle#topic Bugs14:38
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:38
mlavalleThe bugs deputy last week was bcafarel14:38
mlavalleand his report is here: http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001022.html14:39
bcafarelindeed, relatively quiet week, just wanted to highlight a few ones here14:39
mlavallego ahead please14:39
bcafarelhttps://bugs.launchpad.net/neutron/+bug/1808731 - Needs the method to14:40
openstackLaunchpad bug 1808731 in neutron "[RFE] Needs the method to stop metadata proxy" [Undecided,New] - Assigned to cheng li (chengli3)14:40
bcafarelstop metadata proxy I left as undecided, there is some discussion already there (slaweq, haleyb, etc)14:40
slaweqI marked this one as RFE to discuss it on drivers meeting14:41
bcafarelack, good idea14:41
bcafarelhttps://bugs.launchpad.net/neutron/+bug/1808541 is about some race condition with ovs flows, it would benefit from some expert eyes14:41
openstackLaunchpad bug 1808541 in neutron "Openflow entries are not totally removed for stopped VM" [High,New]14:41
mlavalleI see it alreade has the rfe tag. we will capture it in the drivers agenda14:41
bcafarelother high bugs have patches in review14:42
bcafareland one gate failure in nova https://bugs.launchpad.net/neutron/+bug/180817114:43
openstackLaunchpad bug 1808171 in neutron "TaggedBootDevicesTest.test_tagged_boot_devices intermittently fails waiting for network-vif-plugged event which neutron does not send" [Medium,Confirmed]14:43
mlavalleI don't see comments to the one on OVS flows. I'll look at it14:43
*** e0ne has joined #openstack-meeting14:43
bcafarelmlavalle: thanks14:44
bcafarelother bugs are in good shape or progressing (or tagged as rfe)14:44
-amotoki- took the policy bug. it turns out a bit complicated and he forgot to comment it.14:44
mlavallethanks for the good report bcafarel :-)14:45
*** ttsiouts has quit IRC14:45
liuyulongThat network-vif-plugged event bug is related to this, IMO, https://bugs.launchpad.net/neutron/+bug/176004714:45
openstackLaunchpad bug 1760047 in neutron "some ports does not become ACTIVE during provisioning" [High,Triaged]14:45
mlavalleso this week our deputy will be pasuder14:45
*** ttsiouts has joined #openstack-meeting14:46
mlavallethe following week will be hongbin14:46
liuyulongAnd this: https://bugs.launchpad.net/neutron/+bug/1778616, we recently still meet such issue during a VM starting storm.14:47
openstackLaunchpad bug 1760047 in neutron "duplicate for #1778616 some ports does not become ACTIVE during provisioning" [High,Triaged]14:47
mlavalleand the one after that will be slaweq14:47
mlavalleliuyulong: thanks for pointing this out14:47
slaweqyep, I will be first one in 2019 :)14:47
bcafarelhappy new year of bugs to slaweq :)14:48
mlavalleliuyulong: should we mark some of those dulicated?14:48
liuyulong1778616 has been set duplicated.14:48
mlavalleperfect, thanks14:48
mlavalleok, moving on14:49
mlavalle#topic os-ken14:49
*** openstack changes topic to "os-ken (Meeting topic: networking)"14:49
mlavallehongbin couldn't make it to the meeting today14:49
mlavallebut he gave me his update yesterday14:49
*** ttsiouts has quit IRC14:50
*** Luzi has quit IRC14:50
mlavalleFirst, we merged the swicth to os-ken in neutron last week: https://review.openstack.org/#/c/607008/14:50
mlavalleGreat job, hongbin14:50
mlavalleand second there is a corresponding patch in neutron-dynamic-routing: https://review.openstack.org/#/c/608357/14:52
mlavalletidwellr: would you take a look?14:52
tidwellrthat's my patch :)14:52
mlavalleah ok?14:53
mlavalleI will review it then14:53
*** boden has quit IRC14:53
mlavallethat's it for os-ken14:53
mlavalle#topic On demand agenda14:53
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:53
*** Bhujay has quit IRC14:53
mlavallebcafarel: we covered all that you added to this section, right?14:54
amotokiI added it but forgot to add my name :(14:54
amotokiwe already covered it14:54
bcafarel:)14:54
mlavalleperfect14:54
bcafarelyes everything coverted14:54
mlavalleanything else we should discuss today?14:54
mlavalleok, please keep in mind that we will skip the next two meetings14:55
amotokiwill the next meeting at Jan 1?14:55
mlavallewe will resume on January 7th14:56
amotokiah...14:56
amotokiI see my calendar wth JST :)14:56
mlavalleI wish everybody great Holidays14:56
mlavalleand a very succesful 201914:57
slaweqthx, You too mlavalle :)14:57
mlavalleand I also thank everybody for your contributions during 201814:57
mlavallelet's go have some fun \o/14:57
mlavalle#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:57
openstackMeeting ended Tue Dec 18 14:57:49 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-12-18-14.00.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-12-18-14.00.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-12-18-14.00.log.html14:57
slaweqsee You all in 2019 :)14:57
*** tidwellr has left #openstack-meeting14:58
bcafarelnice conclusion :) o/14:58
*** hle2 has quit IRC14:58
*** ttsiouts has joined #openstack-meeting14:58
amotokihappy holidays o/14:58
lajoskatonayeah, happy holidays14:58
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Dec 18 15:00:40 2018 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
ralonsohhello15:00
rubasovhi15:01
lajoskatonao/15:01
slaweqhi15:01
mlavalleo/15:01
* slaweq will need to go out in about 30 minutes15:01
ralonsohhello everyone, I cleanup the backlog and I think today is going to be a short meeting15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsohwe have two active RFE15:02
ralonsohfirst one15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:02
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:02
ralonsohlinks:15:02
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:minimum-bandwidth-allocation-placement-api15:02
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/bandwidth-resource-provider15:02
ralonsoh#link https://review.openstack.org/#/c/622316/15:02
ralonsohrubasov, lajoskatona any update? blocker?15:03
lajoskatonayeah, some movements with the patches15:03
rubasovwe don't have a blocker at the moment15:03
*** Chenjie_ has joined #openstack-meeting15:03
mlavalleso, just go over the reviews?15:03
lajoskatonaI think the newest thing is that a scenario test is uploaded (https://review.openstack.org/625253)15:03
lajoskatonamlavalle: yeah, I think there is no blocker15:04
rubasovwe also went over our todo list since milestone 2 is near15:04
*** xyang has joined #openstack-meeting15:04
ralonsohis https://review.openstack.org/#/c/625253/ tested with the neutron patch?15:04
ralonsohslaweq, tested it manually. Is it working?15:04
*** Chenjie_ has quit IRC15:04
mlavallerubasov: how are we feeling about Stein-115:04
mlavalleStein-2^^^?15:04
*** munimeha1 has joined #openstack-meeting15:05
rubasovand we think that the bp won't be completed fully for ms-2, but we're on good track to complete it in this release15:05
slaweqralonsoh: tested what?15:05
lajoskatonaralonsoh: and the nova patches (https://review.openstack.org/569459)15:05
mlavallerubasov: that's what I was asking about. Thanks15:05
slaweqif You are asking about testing of https://review.openstack.org/#/c/625253/ then I didn't test that one15:05
ralonsohslaweq, the neutron patch related to the tempest test https://review.openstack.org/#/c/590363/15:05
slaweqralonsoh: so this one hhttps://review.openstack.org/#/c/598423/15 right?15:06
lajoskatonaslaweq, ralonsoh: I can add as comment to the patch the dependencies15:06
slaweqif so, yes I tested it and it works fine15:06
ralonsohslaweq, yes, this one15:06
lajoskatonato make it exacutable by others15:06
slaweqthat one is working fine IMO15:07
ralonsohlajoskatona, yes, we should do this15:07
lajoskatonaralonsoh: ok, thanks15:07
ralonsohone question: how fast is the nova development going?15:07
ralonsohbecause I have the feeling the Neutron part is almost finish, but not the Nova part15:07
mlavallegood question15:07
lajoskatonaralonsoh: gibi said that he got reviews for one of his basic oatches15:08
lajoskatonapatches15:08
ralonsoh(well, not the feeling, I can see the patches)15:08
rubasovmy understanding is there's good progress on the nova side15:08
ralonsohok, maybe this is out of context, but we can spend some time on those ones15:08
* gibi just discussion the first of the current nova series on #openstack-nova with mriedem :)15:08
ralonsoh(I mlavalle is OK hehehe)15:08
rubasovbut there are parts expected to go over into the next release15:08
rubasovbut gibi will better summarize it if he's here :-)15:09
ralonsohyes, that's the point, so you don't expect to have this in Stein15:09
lajoskatonaralonsoh: the plan from nova side to make working the basic scenario, like boot VM15:09
rubasovralonsoh: server create/delete is expected to work in this release15:10
gibiso what is currently proposed for nova as code handles, boot, delete, detach interface and re-schedule. The server move operations (resize, migrate, evacuate) likely slip to the next cyle15:10
gibicycle15:10
lajoskatonabut not the server moves if I undenrstand well15:10
rubasovralonsoh: other server lifecycle operations can easily spill over to the next release15:10
ralonsohgibi, rubasov yes, for sure. At least basic operations15:10
mlavalleso let's push on the Neutron side to finish the feature15:10
rubasovmlavalle: ack15:10
ralonsohperfect, so for the other developers: please, take a look at the neutron patches15:11
ralonsoh#link https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)15:11
ralonsohanything else?15:11
mlavallerubasov, lajoskatona, gibi: thanks for your hard work!15:11
rubasovthanks for the reviews and the help15:12
ralonsohfor sure, big feature and great work15:12
lajoskatonamlavalle: let's have happy coding15:12
ralonsohthanks, let's move to next one15:12
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:12
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:12
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/156096315:13
ralonsohThere are two parts: the physical bridges implementation (first patch)15:13
ralonsohand the tunnel interfaces implementation15:13
ralonsohfor the second part, I'm implementing a series of patches using pyroute2 to handle the TC qdiscs, classes and filters15:14
*** hongbin has joined #openstack-meeting15:14
ralonsohof course, I still need to implement, using those ones, the tunnel shaping15:14
ralonsohno blockers, I need reviews!15:14
mlavalleeverything is under that topic, right?15:14
ralonsohyes, everything15:15
mlavalleGreat!15:15
mlavallewill take a look15:15
mlavalleand learn15:15
slaweqme too15:15
rubasov+115:15
ralonsohping me in case of doubt15:15
mlavallethat's the good thing about working with ralonsoh, lajoskatona, rubasov and El Comandante15:15
mlavalleI get to learn from their patches15:15
slaweqLOL15:16
slaweqshould I change my IRC nick? :)15:16
mlavallemaybe15:16
rubasovnova folks change it on Fridays :-)15:16
ralonsohthere are other three RFEs with no progress, I won't spend time on this. If you want, please, take a look at https://etherpad.openstack.org/p/neutron_qos_meeting_chair15:16
mriedemquestion about testing for bw scheduling,15:17
mlavalleralonsoh: I think one of those is mine. I'll get to finsh it this week15:17
mriedemit looks like the integration testing for that is going into a tempest plugin?15:17
mriedemwill those tests get run in the tempest-full job?15:17
ralonsohmlavalle, do you want to discuss it today?15:17
mlavalleralonsoh: no need. Just wanted you to be aware that it is in my todos before enbd of year15:18
mriedemi want to make sure nova has integration test coverage of the feature15:18
lajoskatonamriedem: yes it is now in neutron-tempest-plugin15:18
slaweqneutron-tempest-plugin isn't run in tempest-full job IIRC15:18
slaweqit's run only in neutron jobs15:18
mriedemhmm, so what is being tested in the tempest plugin? just neutron stuff? or both neutron and nova?15:18
mriedemif the latter, that should live in tempest proper imo15:19
lajoskatonamriedem: we can move the test there, if that is good for tempest folks.15:19
mriedemare the tests using nova at all? i.e. creating a server with a port that has a qos policy on it?15:20
slaweqin neutron-tempest-plugin we have some scenario test: https://review.openstack.org/#/c/625253/115:20
lajoskatonamriedem: yes15:20
slaweqand it is using nova as it spawns vms15:20
mriedemok i think that needs to be in tempest then so it's run in the integrated gate15:20
mriedemor,15:20
mriedemnova needs to add some new CI job or wrinkle to an existing job to get those tests15:20
mriedemanyway, sorry to derail, but that's an important one for me from a nova pov15:21
*** aojea has joined #openstack-meeting15:21
slaweqyes, so maybe it would be better to move this scenario test to tempest repo directly15:21
mriedemb/c this is a ton of complicated code15:21
ralonsohmriedem, you are welcome15:21
*** eharney has quit IRC15:22
ralonsohlajoskatona, rubasov : do you have your own roadmap in a etherpad15:22
ralonsohmaybe you can add this request to it15:22
rubasovhere: https://etherpad.openstack.org/p/QoS_minimum_bandwidth_allocation_in_Placement_API15:22
ralonsohperfect, thanks!15:23
rubasovadded it to L5215:24
ralonsohthanks15:24
ralonsohok, is there any other RFE am I missing?15:24
ralonsoh#topic Bugs15:24
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:24
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178400615:24
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:24
ralonsohany update?15:25
mlavallenope15:25
ralonsohno problem15:25
ralonsohnext one15:25
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178518915:25
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:25
ralonsohstill no progress...15:25
ralonsohand that's all!15:26
ralonsoh#topic Open Discussion15:26
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:26
ralonsohjust a heads up15:26
mlavalleralonsoh: I am going to discuss that patch with haleyb now in the Neutron channel15:26
ralonsohi two weeks I'll be OOO15:26
ralonsohactually, next meeting is 1 January15:27
ralonsohSo I think we'll skip this one15:27
ralonsohmlavalle, Am I ok?15:27
mlavallein two weeks we should cancel, since it is New Year15:27
slaweq+115:27
ralonsohperfect15:27
mlavalleso we resume on January 15th15:27
ralonsohmlavalle, thanks to catch Brian15:28
ralonsohany other topic? problem? discussion?15:28
mlavalleralonsoh: just please sned a message to the ML that the meeting on the 1st is cancelled15:28
ralonsohmlavalle, I'll do it now15:28
mlavallethat's it from me15:29
ralonsohthank you everyone!15:29
ralonsoh#endmeeting15:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:29
openstackMeeting ended Tue Dec 18 15:29:31 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-12-18-15.00.html15:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-12-18-15.00.txt15:29
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-12-18-15.00.log.html15:29
ralonsohslaweq, just in time!15:29
lajoskatonabye15:29
ralonsoh30 mins15:29
rubasovbye15:29
mlavallethanks ralonsoh for the 30 minutes15:31
*** vishalmanchanda has quit IRC15:35
*** lajoskatona has left #openstack-meeting15:35
*** liuyulong has quit IRC15:38
*** liuyulong_ has quit IRC15:38
*** armax has joined #openstack-meeting15:44
*** jamesmcarthur has joined #openstack-meeting15:59
*** jamesmcarthur has quit IRC15:59
*** jamesmcarthur has joined #openstack-meeting15:59
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Dec 18 16:00:19 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
slaweqhi16: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
mlavalleo/16:00
*** diablo_rojo has joined #openstack-meeting16:01
hongbino/16:01
slaweqok, lets start16:01
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqmlavalle will continue debugging trunk tests failures in multinode dvr env16:02
mlavalleI did work on this, in fact I was having a chat with haleyb about it16:02
mlavalleI am finding that the instance that lands in the controller node cannot access the metadata service16:02
slaweqmlavalle: I'm now looking at dvr multinode job results and I see a lot of errors like: http://logs.openstack.org/59/625359/4/check/neutron-tempest-plugin-dvr-multinode-scenario/0fcd454/controller/logs/screen-q-l3.txt.gz?level=ERROR16:03
slaweqdo You think that those may be related somehow?16:03
* mlavalle looking16:04
haleybslaweq: i had meant to file a bug for that and another traceback i saw, need to find the tab16:04
mlavalleI saw those and they definitely need to be fixed16:04
*** iyamahat has joined #openstack-meeting16:05
mlavallebut I don't necessarily see the connection with the other bug16:05
slaweqyes, but I wonder if that may be a reason why trunk tests are still failing, even with Your patch16:05
mlavalleI don't rule it out, but I don't see the connection now16:05
slaweqok16:05
slaweqhaleyb: will You fill bug for this one or should I do it?16:05
mlavalleI am also finding that the L3 agent in the controller doesn't seem to be processing the router16:06
mlavalleonly the agent in the compute node is processing the router16:06
haleybi can file a bug, wonder about the JSON issues as well, could mean a bad message?16:06
slaweqwhat JSON issue exactly?16:07
haleybi think i've seen these with a malformed rpc, but can't remember16:07
bcafarellate hi o/16:07
haleybhttp://logs.openstack.org/59/625359/4/check/neutron-tempest-plugin-dvr-multinode-scenario/0fcd454/controller/logs/screen-q-l3.txt.gz?level=ERROR#_Dec_17_23_29_17_34053716:07
mlavalleif that is actually the case, then there is no metadata proxy to process the request from the instance in the controller16:07
haleybslaweq: things like that^^16:07
mlavalleso here's what I plan to do:16:08
mlavalle1) Dig further in the logs16:08
slaweqhmm, I didn't saw this one before16:08
mlavalle2) I will test locally the creation of the router16:09
mlavalle3) add some log debug statements and test16:09
mlavalleagree?16:09
slaweqmlavalle: You are talking about debugging trunk issue, right?16:09
mlavalleright16:09
*** guilhermesp has left #openstack-meeting16:09
slaweqok, that is fine for me16:09
mlavallebut at this poiint, it is not a trunk issue16:10
slaweq#action mlavalle will continue debugging trunk tests failures in multinode dvr env16:10
mlavalleit is a router /L3 agent issue16:10
mlavalleslaweq: ^^^^^16:10
mlavalleand that spills to:16:10
mlavalle1) potentially the messages you are seeing in the logs16:10
mlavalle2) the other ssh timouts that you gave me as hoemwork last week16:11
mlavallemakes sense?16:11
slaweqyep16:12
mlavalleok16:12
slaweqmlavalle: so do You think that we should report separate bugs for those issues from logs?16:12
slaweqI think so but what's Your opinion? :)16:12
mlavalleyes16:12
slaweqk16:12
slaweqhaleyb: will You report them?16:12
mlavalleand I'll point to them in the bug that I am working on16:13
haleybsure, will report them16:13
mlavalleso if I find a relationship, I keep the connection16:13
slaweq#action haleyb to report bugs about recent errors in L3 agent logs16:13
slaweqthx mlavalle and haleyb16:13
slaweqok, lets move on16:14
slaweqnext one: slaweq to continue debugging bug 179847516:14
openstackbug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,In progress] https://launchpad.net/bugs/1798475 - Assigned to LIU Yulong (dragon889)16:14
slaweqI asked for help L3 experts and liuyulong jumped in. Patch proposed: https://review.openstack.org/#/c/625054/16:14
mlavalleok16:15
mlavallegreat!16:15
mlavalleit is still WIP16:16
slaweqso as liuyulong is working on it, I think we are in good hands with this one :)16:16
mlavalleyeap16:16
slaweqok, lets move on then16:17
slaweqslaweq to continue fixing funtional-py3 tests16:17
slaweqI limited output from functional job by disabling warnings and some logging to stdout16:17
slaweqpatches for that are proposed:16:18
slaweqhttps://review.openstack.org/#/c/625555/16:18
slaweq https://review.openstack.org/#/c/625569/16:18
slaweq https://review.openstack.org/#/c/625704/16:18
slaweq https://review.openstack.org/#/c/625571/16:18
slaweqwith those patches this functional job running on python3 should be (almost) good16:18
slaweqalmost because I noticed that also 3 tests related to SIGHUP signal are failing: http://logs.openstack.org/83/577383/19/check/neutron-functional/6470d68/logs/testr_results.html.gz16:18
slaweqbcafarel: can You take a look at them and check if that is related to this issue with handling SIGHUP which we already have reported somewhere?16:19
slaweqor maybe it's some different issue16:19
slaweqok, I think that bcafarel is not here now16:21
slaweqI will ping him tomorrow about that issue16:21
slaweq#action slaweq to talk with bcafarel about SIGHUP issue in functional py3 tests16:21
slaweqnext one:16:21
slaweqhongbin to report and check failing neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed test16:21
bcafarelslaweq: o/ sorry was AFK I can take a look tomorrow (hopefully)16:21
slaweqbcafarel: no problem, thx a lot16:22
hongbino/16:22
hongbinthere is a proposed patch for that16:22
hongbin#link https://review.openstack.org/#/c/625359/16:22
hongbinIMO, we can merge the patch and see if it is able to resolve the error16:23
slaweqthx hongbin, I will take a look at it tomorrow16:23
hongbinslaweq: thanks16:24
slaweqok, lets move to the next one then16:24
slaweqslaweq to switch neutron-tempest-iptables_hybrid job as non-voting if it will be failing a lot because of bug 180794916:24
openstackbug 1807949 in os-vif "os_vif error: [Errno 24] Too many open files" [High,Fix released] https://launchpad.net/bugs/1807949 - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)16:24
slaweqI did: Patch https://review.openstack.org/#/c/624489/ is merged already16:24
slaweqand also revert is already proposed: https://review.openstack.org/#/c/625519/ - proper fix is already in os_vif16:25
slaweqso please review this revert :)16:25
slaweqand thx ralonsoh for proper fix in os_vif :)16:25
slaweqnext one:16:26
slaweqslaweq to mark db migration tests as unstable for now16:26
slaweqPatch https://review.openstack.org/#/c/624685/  - merged16:26
slaweqand I recently found out that there was mistake in this patch, so there is another one: https://review.openstack.org/#/c/625556/ and this is also merged16:27
slaweqI hope we should be better in functional tests ratio now16:27
slaweqand that was all on my list from last week16:28
slaweqanything else You want to ask/talk from previous week?16:28
*** bobh has joined #openstack-meeting16:28
slaweqok, lets move to the next topic then16:29
slaweq#topic Python 316:29
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:29
slaweqI have 2 things related to python 316:29
slaweq1. Rally job switch to python3: https://review.openstack.org/#/c/624358/ - please review it16:29
slaweqit required fix on rally side and it's merged already16:29
slaweqso we should be good to switch this job to python316:30
slaweq2. Some info: As per gmann’s comment in https://review.openstack.org/#/c/624360/3 - we will not get rid of tempest-full python 2.7 job for now.16:30
slaweqthat's all from my side about python3 CI jobs16:32
slaweqanything else You want to add?16:32
mlavallenope, thanks for the update16:32
slaweqok16:32
*** a-pugachev has joined #openstack-meeting16:32
slaweq#topic Grafana16:33
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:33
*** a-pugachev has left #openstack-meeting16:33
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:33
slaweqdo You see anything worth to discuss now?16:34
slaweqI think that all is more or less under controll now - we have still some issues which we are aware of but nothing new and nothing which would cause very high failure rates16:35
slaweqneutron-tempest-iptables_hybrid jobs is clearly back in good shape after ralonsoh's fix for os_vif16:35
*** noonedeadpunk[h] is now known as noonedeadpunk16:35
mlavalleit looks overall good16:35
slaweqand neutron-tempest-plugin-dvr-multinode-scenario is back to 100% of failures16:36
mlavalleright I was about to mention that16:36
slaweqbut this was already discussed before and we know why it happens like that16:36
mlavallebut keep in mind that the work I amdoing with the trunk tests adresses that16:36
mlavalleat least partially16:36
slaweqfullstack tests are mostly failing because of those issues which hongbin and liuyulong are working on16:37
mlavalleThat's what I figured16:37
slaweqonly quite high failure rate for functional tests worrying me a bit16:38
slaweqI'm looking for some recent examples16:38
slaweqI found something like that for example: http://logs.openstack.org/00/612400/16/check/neutron-functional/3e8729c/logs/testr_results.html.gz16:40
slaweqand I see such error for first time16:41
slaweqother examples which I found looks that are related to patches on which it was running16:43
slaweqso maybe there is no any new issue with those tests16:43
slaweqlets just monitor it for next days :)16:43
slaweqwhat do You think?16:43
*** ralonsoh has quit IRC16:44
mlavalleyes16:44
mlavallelet's monitor it16:44
slaweq:)16:45
slaweqok, lets move on16:45
slaweq#topic Periodic16:45
*** openstack changes topic to "Periodic (Meeting topic: neutron_ci)"16:45
slaweqI just wanted to mention that thx mriedem our neutron-tempest-postgres-full is good again :)16:45
slaweqthx mriedem16:45
slaweqand except that all other periodic jobs looks good now16:45
slaweqok, so last topic for today16:46
slaweq#topic Open discussion16:46
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:46
mriedem\o/16:46
slaweqfirst of all I want to mention that next 2 meetings will be cancelled as it would be during Christmas and New Year16:46
slaweqI will send email about that today too16:47
mlavalleno meetings on the 25th and the 1st, right?16:47
slaweqmlavalle: right16:47
mlavalleI don't have anything else16:47
slaweqand second thing which I want to raise here is patch16:47
slaweq#link https://review.openstack.org/57393316:47
slaweqit is waiting for very long time for review16:47
slaweqI was already mentioning it here few times16:48
slaweqplease take a look at it16:48
mlavalleI'll comment today16:48
slaweqthx mlavalle16:48
mlavalleas I've said before, I'm not fan of it16:48
slaweqpersonally I don't think we should merge it but I don't want to block it if others things that it's good16:48
slaweqok, thats all from me for today16:49
slaweqdo You have anything else You want to talk?16:49
mlavallenope16:49
slaweqif not, then I will give You back 10 minutes16:49
mlavallethanks16:49
slaweqhave a great holidays and Happy New Year!16:50
mlavalleyou too!16:50
*** e0ne has quit IRC16:50
bcafarelthe same :)16:50
slaweqHappy CI New Year even :)16:50
mlavallealthough I still expect to see you in the Neutron channel16:50
slaweqand see You all in January on meetings16:50
slaweqmlavalle: yes, I will be available until this Friday for sure16:50
slaweqnext week maybe if I will need to rest from family a bit :P16:51
mlavalle:-)16:51
slaweq#endmeeting16:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:51
slaweqo/16:51
openstackMeeting ended Tue Dec 18 16:51:18 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-12-18-16.00.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-12-18-16.00.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-12-18-16.00.log.html16:51
bcafarelo/16:51
*** macza has joined #openstack-meeting16:56
*** kopecmartin is now known as kopecmartin|off17:05
*** e0ne has joined #openstack-meeting17:13
*** ttsiouts has quit IRC17:14
*** ttsiouts has joined #openstack-meeting17:15
*** jamesmcarthur has quit IRC17:16
*** e0ne has quit IRC17:19
*** armax_ has joined #openstack-meeting17:19
*** armax has quit IRC17:19
*** armax_ is now known as armax17:19
*** ttsiouts has quit IRC17:19
*** eharney has joined #openstack-meeting17:22
*** mlavalle has left #openstack-meeting17:29
*** bobh has quit IRC17:39
*** bobh has joined #openstack-meeting17:40
*** jamesmcarthur has joined #openstack-meeting17:52
*** _alastor_ has joined #openstack-meeting17:53
*** gouthamr_ has joined #openstack-meeting17:54
*** cloudrancher has quit IRC17:55
*** _alastor_ has quit IRC17:55
*** _alastor_ has joined #openstack-meeting17:56
*** iyamahat has quit IRC17:57
*** cloudrancher has joined #openstack-meeting17:57
*** yamahata has quit IRC17:57
*** _alastor_ has quit IRC18:05
*** iyamahat has joined #openstack-meeting18:11
*** Shrews has joined #openstack-meeting18:17
*** armax has quit IRC18:17
*** _alastor_ has joined #openstack-meeting18:25
*** yamahata has joined #openstack-meeting18:31
*** e0ne has joined #openstack-meeting18:34
*** e0ne has quit IRC18:40
*** gyee has joined #openstack-meeting18:48
*** pabelanger has joined #openstack-meeting18:56
*** priteau has quit IRC18:58
clarkbanyone here for the infra meeting?19:00
fungii suppose19:00
ianwhello!  merry christmas to all :)19:00
fungi#define here19:00
Shrewsi'm here for the eggnog19:00
pabelangerhello!19:00
clarkbianw: is it "merry" or "happy" in your part of the world?19:00
fungior "have a furrowing yule"19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Dec 18 19:01:15 2018 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
diablo_rojoo/19:01
gary_perkinso/ Ho ho ho! :)19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
ianwmerry :)  happy holidays to my US friends :)19:01
fungiit's still hallowe'en here19:01
clarkbI wonder if I should start linking to my email thread archive instead of the wiki19:01
fungiclarkb: yes, please!19:02
clarkbin any case we have an agenda and I sent it out about 24 hours ago19:02
fungimakes it seem a little more formalized19:02
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-December/006255.html19:02
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
clarkbAs ianw has pointed out we are entering the happy/merry time of year for many of us19:03
clarkbThe next two regularly scheduled meetings happen on holidays I expect we'll be celebrating so I've cancelled them. Our next meeting will be January 819:03
*** armax has joined #openstack-meeting19:04
clarkbIf you are taking time off I hope you enjoy it. I'll be traveling myself starting thursday early morning which means I may start winding down work things tomorrow19:04
*** sridharg has quit IRC19:05
clarkb#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
*** e0ne has joined #openstack-meeting19:05
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-11-19.01.txt minutes from last meeting19:05
clarkbI've noticed that the actiosn from last meeting section was one I didn't update properly in the email agenda19:05
clarkbThe two actions we do have from last week are ianw testing github shared account and fungi volunteering for storyboard db moves19:06
clarkbI know ianw made progress on github and we've got tiem for that later19:06
clarkbfungi: any update on the storyboard db moves?19:06
fungiahh, no, lemme see where that got to19:06
fungi#link https://review.openstack.org/623290 Run a local MySQL service on StoryBoard servers19:07
fungiseems it's got enough votes but wasn't approved19:08
fungii'll go ahead and do that now as all it will do is install and start a mysqld19:08
clarkb++, thanks19:08
clarkb#topic Specs approval19:08
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:08
*** eharney has quit IRC19:08
clarkbWe've got two specs that I think we can put up for official approval voting19:08
clarkb#link https://review.openstack.org/623033 OpenDev Repo Hosting Rework Spec19:08
clarkb#link https://review.openstack.org/607377 Storyboard Attachements19:08
fungii agree those should be ready for council roll call19:09
clarkbI'd like to do so now then plan for a longish approval period as I'm unsure of how many days we'll be working over the next couple weeks19:09
corvusnormal approval period would be until thursday, right?19:09
corvusis that insufficient?19:09
clarkbcorvus: it would be. I'm not sure about others but I need to work on packing the family and stuff for a 6am thursday flight :/19:10
clarkbI suppose I could pop my head in once I have internets again after flying and approve changes if others think they will be able to review19:10
corvusperhaps we could ask people to -1 if they need more time?19:11
corvusotherwise proceed as normal?19:11
clarkbcorvus: thatworks for me19:11
*** eharney has joined #openstack-meeting19:11
clarkb#info Please -1 the above specs if you are not able to review them properly for approval prior to Thursdayish. Clarkb will plan to approve the specs once he has internet again late this week (earliest thursday)19:12
corvusrelated, i've been working with mordred to get a gitea POC up and running; you can see it here: http://38.108.68.96/19:12
corvusthat's very temporary, but it's something we can play with.  i'm happy to talk about the implementation later if folks want.19:13
clarkbcorvus: thanks19:13
corvuspretend the 'register' button isn't there :)19:13
clarkbI'll also call out tristanC and dirks log analysis spec19:13
clarkb#link https://review.openstack.org/581214 Anomaly Detection in CI Logs19:13
clarkbI don't think this one is ready for approval, but feedback would be good19:13
fungiLinkid also has a wip spec up about hosting a video hosting/streaming service19:14
Linkidhi19:14
Linkidyes :)19:14
fungiwhich has some interesting tie-ins to the containerization of services work19:14
Linkidhttps://review.openstack.org/#/c/62545019:14
clarkb#link https://review.openstack.org/#/c/625450/ video hosting/streaming spec19:15
Linkid^ the spec about video hosting service19:15
fungia good one for those who have opinions on what direction we're going in the service container space19:15
corvuscool, i'll review that soon -- i have learned a lot about that lately :)19:15
clarkb#topic Priority Efforts19:16
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:16
clarkb#topic Update Config Management19:16
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:16
clarkbthere has been a bunch of progress and firefighting around ansible and docker and puppet in the last week19:16
clarkbGood news is the bootstrapping for docker work is now merged (as of a couple hours ago), we have a script to generate our static inventory too19:17
corvusoh great! which change was that?19:18
clarkbKeep in mind the static inventory generation will emit an inventory with our magnum nodes in it, we don't want to use an inventory with those nodes in it, though ansible should fail to ssh into them19:18
clarkb#link https://review.openstack.org/#/c/622964/ Inventory generation script19:18
corvusif we apply deltas to config management, we should be able to review that19:18
corvusso we can -1 changes which add magnum nodes :)19:18
clarkbya, mostly a heads up that you'll want to edit the inventory that is generated19:18
clarkbbut that should be easier than trying to scan all the clouds by hand19:19
corvusok https://review.openstack.org/605585 is the docker change19:19
clarkbI've also started moving the puppet-4 work wioth futureparser enablement forward. Since chances are we'll be running puppet on various services for a while. Next up on the list are the leasticsearch nodes19:19
clarkbthank you cmurphy for that stack of chagnes. I'm trying to get through them :)19:20
clarkbThat did expose that our groups.yaml file is a list of globs not regexes19:20
clarkbwe should all be careful of that when making changes to the groups.yaml file. + matches a literal + for example and * doesn't apply to the previous character19:20
fungiseems we need to be periodically reminded of that19:20
fungieasy to miss when reviewing19:21
clarkbWe also discovered a really fun ansible bug19:21
clarkb#link https://github.com/ansible/ansible/issues/49969 Ansible bug that crashes current play and returns success19:21
clarkbI've worked around ^ in our roles so it no longer affects us, but another warning that nested sequences of include_tasks results in sad ansible that reports happyness19:22
*** mriedem is now known as mriedem_afk19:22
clarkband upstream is working to fix it which is good19:22
clarkbAnything else on this effort?19:22
cmurphythanks clarkb19:22
clarkb#topic Storyboard19:24
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:24
clarkbAs noted above there is the storyboard attachments spec up for approval this week19:24
clarkbfungi has the votes necessary to move foward on db migratiosn for storyboard19:24
fungiaside from the spec up for review and me making poor progress on the mysql move, no news i'm aware of19:24
diablo_rojoNo news besides the spec and the migration of the db really19:25
diablo_rojoits been pretty slow going19:25
clarkbok19:25
clarkbit is that time of year where everything seems to turn into molasses19:25
diablo_rojoIndeed.19:25
clarkb#topic OpenDev19:25
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:25
clarkb#link https://review.openstack.org/#/c/625671/ Publish early opendev web content19:25
clarkbLooks like this was just merged? still no website though so we will want to double check on that after hte meeting19:26
clarkbIn addition to that we now have the ability to host mailing lists at lists.opendev.org19:26
clarkbSounds like corvus has been busy POCing the repo hosting side of things19:27
clarkbLooking like early next year might be a sprint to actually hosting things?19:27
clarkbvery exciting19:27
corvusthe poc i linked is running on a 3-node k8s cluster with a shared cephfs19:27
fungia group of people collaborating around special-purpose virtual machine monitors in rust are our first takers on lists.opendev.org19:28
fungifor anyone wondering how obscure this was going to get right off the bat ;)19:28
corvusmordred and i should be able to push up ansible changes to drive a gitea that way soon19:28
clarkbcorvus: is that so you can have gerrit replicate as the writer then have gitea mount the filesytem read only in a distributed manner?19:29
corvusclarkb: yes -- but moreover, we would push to gitea in the normal way, so all of its hooks are triggered (so it records and publishes events, etc).  but the main thing is that should let us use other features in the future if we want (eg wiki).19:30
clarkbcan gitea safely do that with multiple instances writing to the same fs?19:30
corvusbasically, it would be a real HA gitea system19:30
clarkb(things to sort out later I guess)19:30
corvusclarkb: yes19:30
clarkbneat19:30
corvusi think it would be our first stateful ha system19:31
corvusthe cephfs-in-k8s thing (rook) is pretty neat too.  basically we can have all the components HA running inside k8s.  it's what k8s was actually designed to do :)19:31
fungifrom what i understand of the wiki implementation so far i'm not sure it's actually a fit for some of our current wiki.o.o use cases due to needing explicit editor rights granted from repository owners, but it's possible i'm overlooking what makes it possible to let anyone who authenticates create and edit pages. that said, the ability to drop codesearch.o.o is compelling on its own19:32
clarkbya the one gotcha with ceph run in that manner is that osds are tied to disk so you can't just replace hosts (have to do it in a rolling fashion with intermediate recovery points)19:32
corvusclarkb: yep.  but we can handle k8s node failures.19:33
clarkbwhereas stateless k8s workload you can just move around all you want19:33
corvusfungi: yeah, i'm waving hands on the wiki thing right now.  i haven't looked into it at all19:33
corvusfungi: mostly i'm using it as a use case for "let's not back ourselves into a corner so we can't do it later if we want"19:33
corvusoh shoot, i forgot to turn on code searching in the poc19:34
corvusi'll do that after the meeting19:34
clarkbalright anything else on OpenDev before we move to the general topics list?19:34
clarkb#topic General Topics19:35
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:35
clarkbianw volunteered to set up a shared github account that we can use to administer our github things. This has been done and I've confirmed that I can log in to the account19:36
*** aojea has quit IRC19:36
clarkb#link https://review.openstack.org/#/c/624531/ ianw's docs update19:36
clarkbI think ianw is looking for consensus on ^ before changing the setup in github itself19:36
ianwwe've got 2 votes ... i'll give it to say EOD and then i'd like to give the user permissions (and remove my own personal ones)19:37
clarkbThis simplifies new root onboarding and gets us away from using our personal accounts for this 9which we didn't want to be doing anyway)19:37
corvussounds good to me; i'll try it out and +2 if no issues19:38
fungithanks ianw!19:39
clarkbNext on the list started as my list of changes I'd like to see merged before I am not around a computer. But they've since merged yesterday19:39
corvusi do wonder if the username is accurate :)19:39
clarkbsince they have merged I'll go ahead and open it to anyone else to point out changes that would be good to have eyeballs on them before rooters are afk19:40
clarkbmaybe ansible lint pinning if we end up needing that19:41
clarkbthough I'm not yet aware of needing that19:41
clarkbin any case if you spot important bug fixes please call them out so we can try to get fixes in prior to holidays19:42
clarkbAnd now on to the docker mirroring issues19:42
clarkbI'll admit I'm not completely sure I understand what the problem is here. I thought this was a known issue and is why we mirror docker on ports 8081 and 808219:42
clarkbBasically infra has addressed it by having mirrors that handle both cases and jobs need to know which to use based on their version of docker19:43
fungiare there still issues? everyone i saw follow up said switching to the port 8082 mirror solved it for them19:43
clarkbfrickler: mordred corvus ^ do you know?19:43
fricklerit seems the patch has resolved things for us19:44
corvusi don't know anything about dockerhub :(19:44
clarkbfrickler: have a link to the patch so we can record here if others run into the same issue it may serve as a good template bug fix19:44
fricklerand mgoddard also confirm things working for them19:44
fungis/mirror/proxy/19:44
frickler#link  https://review.openstack.org/625596 Switch to using the pathless :8082 variant of our mirror unconditionally19:45
fricklerthere is a bit of follow-up because our openstack specific mirror setup shouldn't be known to zuul-jobs19:46
clarkbbasically newer docker wants things hosted at / and so you can't tell it to talk to host.foo.com:8081/other/root/path19:46
corvusi think that means we can drop 808119:46
fricklerI think there were some projects that might still use 808119:46
clarkbso we have a host.foo.com:8082/ proxy and have kept a host.foo.com:8081/other/path for backward compat19:46
clarkbI want to say pabelanger tested older docker against the 8082 one and it didn't work there19:46
corvusfrickler: without using that role?19:46
fungiand part of what brought this up is that ubuntu switched to new enough docker to need the new protocol?19:47
clarkbcorvus: ya tripleo does their own mirror/proxy setup19:47
corvusclarkb: i thought tripleo used the new url too?19:47
fricklercorvus: like this http://git.openstack.org/cgit/openstack/kayobe/tree/playbooks/kayobe-overcloud-base/overrides.yml.j219:48
corvusit's not important i guess; we can check the logs later19:48
clarkbcorvus: they use the new v2 api on top of the 8081 proxy because they don't actually use docker aiui19:48
clarkbcorvus: but they don't use that role19:48
clarkbits weird19:48
clarkbin any case it sounds like we've confirmed that 8082 does fix things and that we should start pushing people towards that address so that we can turn off 808119:48
clarkbprobably worth a -discuss email thread for that19:49
fricklerfungi: yes, ubuntu backported a new docker into xenial-updates19:49
clarkband we can use apache logs to confirm that people have moved19:49
fungiright, seems like in that case anyone using the port 8081 proxy even from xenial is broken now19:50
fungiso odds are it'll no longer be needed but we can check apache access logs19:50
clarkbfungi: ya, the weird one is tripleo beacuse they use 8081 wiht the new v2 url api aiui. And I think they get away with it because their client isn't the docker client19:50
fricklerexcept they install docker from somewhere else than ubuntu repos19:50
clarkbso fi we switch tripleo then likely everyone else will be on 808219:50
fungik19:50
clarkb#topic Open Discussion19:51
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:51
clarkbAnything else before we get ready to call it a year?19:51
fungii hope everyone enjoys whatever end-of-year festivities they prefer19:53
corvusi'm celebrating the 8 days of k8s19:53
fungihah19:53
fungiubernete19:53
clarkbas mentioned earlier starting tomorrow I expect to not be around much. I've got to pack for early thursday flight (and this time with kids which makes logistics a million times more complicated)19:54
corvusi should be around this week.  not so much next.19:55
*** manjeets has quit IRC19:55
fungii'm around all this week and intermittently the next19:55
fungiand then around most of the following weel again19:56
fungiweek too19:56
ianwfyi i'm pto from EOD today till 07 jan19:56
fungibold!19:56
fungii like your style19:56
clarkbeveryone should enjoy the time they are taking off. I expect that most of openstack and related acitivities will as well19:56
clarkbwe should remind the release team to not make any releases next week :P19:57
fungiheh19:57
clarkbfungi: I still rememebr the year it was pbr or something made a release on the 24th and broke everything for a few days19:57
clarkbalso the year setuptools and pip released weekend before christmas or was it weekend of new years19:57
fungioh, yeah, fun times!19:58
clarkbAlright sounds like that is it. We'll see you all here on the 8th of January. Until then happy/merry $holiday19:58
clarkb#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:58
openstackMeeting ended Tue Dec 18 19:58:44 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-18-19.01.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-18-19.01.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-18-19.01.log.html19:58
*** Shrews has left #openstack-meeting19:59
fungithanks clarkb!19:59
*** erlon_ has quit IRC20:04
*** _alastor_ has quit IRC20:29
*** _alastor_ has joined #openstack-meeting20:30
*** erlon has joined #openstack-meeting20:32
*** bobh has quit IRC20:32
*** bobh has joined #openstack-meeting20:33
*** mriedem_afk is now known as mriedem20:50
*** njohnston has joined #openstack-meeting20:57
*** jamesmcarthur has quit IRC20:58
*** mriedem has quit IRC21:02
*** mriedem has joined #openstack-meeting21:04
*** hongbin has quit IRC21:09
*** hongbin has joined #openstack-meeting21:09
*** rcernin has joined #openstack-meeting21:22
*** jamesmcarthur has joined #openstack-meeting21:26
*** jamesmcarthur has quit IRC21:27
*** jamesmcarthur has joined #openstack-meeting21:27
*** jamesmcarthur has quit IRC21:30
*** tpsilva has quit IRC21:31
*** raildo has quit IRC21:36
*** rcernin has quit IRC21:37
*** eharney has quit IRC21:40
*** manjeets has joined #openstack-meeting21:48
*** e0ne has quit IRC21:51
*** thgcorrea has quit IRC21:58
*** rcernin has joined #openstack-meeting22:04
*** munimeha1 has quit IRC22:05
*** jamesmcarthur has joined #openstack-meeting22:11
*** jamesmcarthur has quit IRC22:16
*** manjeets has quit IRC22:30
*** awaugama has quit IRC22:31
*** rcernin has quit IRC22:37
*** rcernin has joined #openstack-meeting22:41
*** rcernin has quit IRC22:43
*** rcernin has joined #openstack-meeting22:45
*** manjeets has joined #openstack-meeting22:45
*** bobh has quit IRC22:48
*** bobh has joined #openstack-meeting23:07
*** bobh has quit IRC23:17
*** bobh has joined #openstack-meeting23:18
*** bobh has quit IRC23:22
*** armax has quit IRC23:29
*** efried has joined #openstack-meeting23:29
*** efried has quit IRC23:34
*** _alastor_ has quit IRC23:37

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