Tuesday, 2019-03-19

*** markvoelker has joined #openstack-meeting00:03
*** a-pugachev has joined #openstack-meeting00:05
*** lseki has quit IRC00:07
*** markvoelker has quit IRC00:07
*** tetsuro has joined #openstack-meeting00:14
*** gyee has quit IRC00:15
*** a-pugachev has quit IRC00:15
*** jamesmcarthur has joined #openstack-meeting00:20
*** armax has quit IRC00:25
*** markvoelker has joined #openstack-meeting00:35
*** armax has joined #openstack-meeting00:38
*** markvoelker has quit IRC00:49
*** slaweq has quit IRC00:58
*** mattw4 has quit IRC01:06
*** slaweq has joined #openstack-meeting01:10
*** jamesmcarthur has quit IRC01:11
*** hongbin has joined #openstack-meeting01:12
*** armax has quit IRC01:21
*** iyamahat has quit IRC01:22
*** yamahata has quit IRC01:22
*** slaweq has quit IRC01:24
*** whoami-rajat has joined #openstack-meeting01:25
*** absubram has quit IRC01:33
*** cheng1 has joined #openstack-meeting01:36
*** eharney_ has quit IRC01:40
*** rodrigods has joined #openstack-meeting01:42
*** lbragstad has quit IRC01:56
*** lbragstad has joined #openstack-meeting02:09
*** jamesmcarthur has joined #openstack-meeting02:20
*** jamesmcarthur has quit IRC02:25
*** jamesmcarthur has joined #openstack-meeting02:38
*** jamesmcarthur has quit IRC02:43
*** jamesmcarthur has joined #openstack-meeting03:14
*** apetrich has quit IRC03:14
*** armax has joined #openstack-meeting03:30
*** jamesmcarthur has quit IRC03:31
*** jamesmcarthur has joined #openstack-meeting03:31
*** igordc has quit IRC03:32
*** shilpasd has joined #openstack-meeting03:33
*** janki has joined #openstack-meeting03:44
*** tpatil has joined #openstack-meeting03:52
samPHi all for masakari03:59
*** imsurit_ofc has joined #openstack-meeting04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Mar 19 04:00:24 2019 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
samPtpatil: Hi04:00
*** sagara has joined #openstack-meeting04:00
samP#topic Critical Bugs and Patches04:00
*** openstack changes topic to "Critical Bugs and Patches (Meeting topic: masakari)"04:00
tpatil#link : https://bugs.launchpad.net/masakari/+bug/181957804:01
openstackLaunchpad bug 1819578 in masakari "HOST failure recovery fails with reserved host " [Critical,New] - Assigned to Shilpa Devharakar (shilpasd)04:01
tpatilWork is in progress04:01
tpatilWill upload patch by e.o.d Wednesday04:01
samPtpatil: Thanks04:02
*** tashiromt has joined #openstack-meeting04:02
sagaratpatil: Do you know which releases are affected with this bug?04:04
tpatilCurrent one i.e Stein04:04
sagaratpatil: Thanks04:05
samPPlease bring up any issues related to this any time in this meeting.04:06
samP#topic Stein Work Items04:06
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)"04:06
samPPlease share any updates on Stein work items04:07
tpatil1) Add devstack support for masakari-monitors04:07
tpatilThe gate job is passing now04:07
tpatilNeha will fix some minor review comments and then I will vote +2 on this patch04:07
tpatil#link :https://review.openstack.org/#/c/638577/04:08
tpatilin the instance monitor log, I have noticed some warning. But this issue in present in the functional tests04:08
tpatil#l link : http://logs.openstack.org/77/638577/21/check/masakari-functional-devstack-multinode/2d55c52/compute1/logs/screen-masakari-instancemonitor.txt.gz04:09
tpatil2) Functional tests04:10
tpatil#link : https://review.openstack.org/#/c/642223/04:10
tpatilPlease review this patch04:10
tpatilonce this patch is merged, it then we have covered segment, host and notification (VM, PROCESS) functional tests04:11
tpatilfor compute host, we have one dependency on openstacksdk04:11
tpatilin openstacksdk, it support to force_down a service but they don't have API to set it back to False04:11
tpatilWe are planning to add this API in openstacksdk but I think it's too late for this Stein cycle04:12
samPtpatil: sure, I will review this04:12
*** hongbin has quit IRC04:12
tpatilsamP: Thanks04:13
samPtpatil: This issue is not critical for masakari, but for functional tests.04:13
*** cheng1 has quit IRC04:13
samPLet's try it on next release04:13
tpatilsamP: Sure04:13
tpatil Improve logging error messages04:14
tpatil#link : https://review.openstack.org/#/c/64161104:14
tpatilNeed one more +2 and/or workflow +104:14
samPsagara: please review ^^ if you have time.04:14
*** diablo_rojo has quit IRC04:15
samPOtherwise, I will WF+1 for this, since changes are clear and simple04:16
sagarasamP: OK, I will review it.04:16
samPsagara: thank you!04:16
tpatilThat's all about Stein work items from my end04:18
samPtpatil: thanks04:18
samPno update from my end04:18
samP#topic Stein release04:19
*** openstack changes topic to "Stein release (Meeting topic: masakari)"04:19
samPI am planning to cut the stable/stain branch on 3/2104:19
samPsame point will be the RC1 for Stein04:20
tpatilsamP: OK, before that we will fix and merge the critical issue04:20
samPtpatil: sure, thanks04:20
samPif patches not going to make can still merge into master and backport to stable/stein04:21
tpatilsamP: Yes, Sure04:22
samPI will release new version for masakari-dashboard, once we create RC1 for masakari04:23
samPthat's all from my side04:23
tpatilsamP: OK04:23
samPif no other topics, we can end today's meeting here04:23
tpatilsamP: No other topics to be discussed from my end04:24
samPPlease use #openstack-masakari IRC@freenode or openstack-discuss@lists.openstack.org for further discussion04:24
shilpasdsamP: hi, need review for dashboard patch https://review.openstack.org/#/c/642981/04:25
*** sridharg has joined #openstack-meeting04:25
shilpasdits for real time data for notification recovery workflow details.04:26
samPshilpasd: sure, I will04:26
shilpasdsamP: Thank you04:26
samPthanks for adding this04:26
samPThank you all!04:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:27
openstackMeeting ended Tue Mar 19 04:27:11 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-03-19-04.00.html04:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-03-19-04.00.txt04:27
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-03-19-04.00.log.html04:27
*** sagara has quit IRC04:29
*** tetsuro has quit IRC04:33
*** jamesmcarthur has quit IRC04:40
*** tpatil has quit IRC04:40
*** dklyle has quit IRC04:44
*** dklyle has joined #openstack-meeting04:45
*** cheng1 has joined #openstack-meeting04:52
*** vishalmanchanda has joined #openstack-meeting04:59
*** cheng1 has quit IRC05:11
*** cheng1 has joined #openstack-meeting05:26
*** liuyulong has quit IRC06:01
*** markvoelker has joined #openstack-meeting06:20
*** markvoelker has quit IRC06:25
*** njohnston_ has quit IRC06:28
*** lbragstad has quit IRC06:38
*** markvoelker has joined #openstack-meeting06:51
*** Luzi has joined #openstack-meeting06:59
*** SergeyLukjanov has quit IRC06:59
*** SergeyLukjanov has joined #openstack-meeting07:01
*** pcaruana has joined #openstack-meeting07:14
*** apetrich has joined #openstack-meeting07:26
*** dkushwaha has joined #openstack-meeting07:31
*** iyamahat has joined #openstack-meeting07:32
*** pcaruana has quit IRC07:33
*** pcaruana has joined #openstack-meeting07:34
*** kopecmartin|off is now known as kopecmartin07:36
*** slaweq has joined #openstack-meeting07:38
*** tetsuro has joined #openstack-meeting07:58
*** hadai has joined #openstack-meeting08:01
dkushwaha#startmeeting tacker08:03
openstackMeeting started Tue Mar 19 08:03:13 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:03
*** openstack changes topic to " (Meeting topic: tacker)"08:03
openstackThe meeting name has been set to 'tacker'08:03
dkushwaha#topic Roll Call08:03
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:03
dkushwahawho is here for Tacker weekly meeting?08:03
hyunsikyangI am here08:04
dkushwahahello hyunsik08:04
dkushwahaseems no other members.08:07
hyunsikyangHumm.. I think so.08:07
*** ttsiouts has joined #openstack-meeting08:08
*** hjwon has joined #openstack-meeting08:09
dkushwahai have some updates, so will keep it quick08:09
dkushwahalets start..08:09
*** hokeeeeun has joined #openstack-meeting08:09
dkushwaha#topic Announcement08:09
*** openstack changes topic to "Announcement (Meeting topic: tacker)"08:09
*** jaewook_oh has joined #openstack-meeting08:09
dkushwahaTackerclient 0.15.0 is released08:10
dkushwaha#link https://releases.openstack.org/stein/#python-tackerclient08:10
hyunsikyangMy lab members has joined here.08:10
dkushwahaDear new member, please introduce yourself08:11
jaewook_ohHello, this is Jaewook from IISTRC with Hyunsik08:12
dkushwahajaewook_oh,  Welcome in Tacker team08:12
jaewook_ohThank you for greeting me :)08:13
dkushwahajaewook_oh, you are also doing research with hyunsik?08:13
jaewook_ohyes exactly,08:13
dkushwahajaewook_oh, what is your area of scope ?08:14
jaewook_ohCurrently, I'm working with the containerized vim, especially kubernetes one08:14
hokeeeeunHello, this is Hokeun from IISTRC with Hyunsik08:16
hyunsikyangSo I suggested he deal with  monitoring part of Containerized VIM.08:16
dkushwahajaewook_oh,  we have lots of stuffs to do in container area, your support will be great help. :)08:16
dkushwahahokeeeeun, Welcome to Tacker team :)08:17
jaewook_ohThanks again, and I hope I can contribute to tacker :D08:17
*** cheng1_ has joined #openstack-meeting08:17
dkushwahaFeels great to see new members from IISTRC :)08:18
dkushwahamoving next..08:18
hjwonHello, this is HoJoon from IISTRC with Hyunsik  :)08:19
*** tssurya has joined #openstack-meeting08:19
dkushwahawelcome hjwon in Tacker team :)08:19
dkushwaha#topic Stein-items08:20
*** dmacpher has quit IRC08:20
*** openstack changes topic to "Stein-items (Meeting topic: tacker)"08:20
*** cheng1 has quit IRC08:20
dkushwahaI have some pending items for stein08:20
dkushwahaand still working on that08:20
dkushwahai.e. VNF-force-delete08:21
hyunsikyangCould you mention the list for Stein?08:21
dkushwahaand hope to land it soon08:21
dkushwahahyunsikyang, https://blueprints.launchpad.net/tacker/stein08:22
dkushwahaTeam, I have already fixed https://blueprints.launchpad.net/tacker/+spec/improve-return-message08:23
dkushwahabut it will be great if somebody can work on that for more improvements08:23
dkushwahai.e. to handle more cases.08:24
*** brault has joined #openstack-meeting08:24
dkushwaha#topic force-delete08:24
*** openstack changes topic to "force-delete (Meeting topic: tacker)"08:24
dkushwaha#link https://review.openstack.org/#/c/620385/08:25
hyunsikyangOK we will check it together.08:25
*** ttsiouts has quit IRC08:25
dkushwahaI will update this patch soon. Request you folks to please review it08:25
dkushwahahyunsikyang, thanks08:25
*** e0ne has joined #openstack-meeting08:25
dkushwahamoving next..08:26
dkushwaha#topic Train Grooming08:27
*** openstack changes topic to "Train Grooming (Meeting topic: tacker)"08:27
dkushwaha#link https://etherpad.openstack.org/p/tacker-train-grooming08:27
dkushwahaI have created etherpad for train-cycle working items08:27
dkushwahaSo please Put your stuffs here08:28
jaewook_ohOk :)08:28
hyunsikyangYou added my blueprint. Thanks.08:28
dkushwahawe will use this etherpad for reference and further discussions08:29
dkushwahanothing else from my side for today08:29
dkushwaha#topic OpenDiscussion08:29
*** openstack changes topic to "OpenDiscussion (Meeting topic: tacker)"08:29
hyunsikyangI have a question for Summit presentation.08:29
dkushwahahyunsikyang, yes please08:30
hyunsikyangI just asking about contents for presentation.08:31
hyunsikyangwe only have 10 min right?08:31
dkushwahahyunsikyang, yes08:32
hyunsikyangWhen you prepare it, please let me know. we can discuss it and make material together.08:33
dkushwahaour topic is big enough, but as it got selected in for 10 minuts tolks, So we have to cover multiple points, but needs to keep all brief08:33
hyunsikyangyes. I think so.08:33
dkushwahahyunsikyang, yes, I will suggest to use google docs, where we both can view and update.08:34
hyunsikyangOk. I will tell you in a personal channel later.08:35
dkushwahahyunsikyang, nice08:35
hyunsikyangI am done.08:36
dkushwahaThanks all08:37
*** priteau has joined #openstack-meeting08:38
dkushwahaLooking for yours great support in Tacker, to make it more and more stable, popular and usable08:39
dkushwahaThanks Folks08:39
dkushwahaclosinf it for now08:39
dkushwahaIn India there will be a long holiday due to Holi Festival, So I will less active on IRC during this week08:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:41
openstackMeeting ended Tue Mar 19 08:41:24 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-03-19-08.03.html08:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-03-19-08.03.txt08:41
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-03-19-08.03.log.html08:41
*** hokeeeeun has quit IRC08:42
*** rossella_s has quit IRC08:46
*** ttsiouts has joined #openstack-meeting08:49
*** hadai has quit IRC08:54
*** Luzi has quit IRC08:59
*** dklyle has quit IRC09:08
*** dklyle has joined #openstack-meeting09:09
*** kukacz has quit IRC09:11
*** jbadiapa has joined #openstack-meeting09:13
*** kukacz has joined #openstack-meeting09:28
*** cheng1_ has quit IRC09:28
*** kukacz has quit IRC09:29
*** kukacz has joined #openstack-meeting09:30
*** ttsiouts has quit IRC09:31
*** ttsiouts has joined #openstack-meeting09:32
*** Lucas_Gray has joined #openstack-meeting09:33
*** rossella_s has joined #openstack-meeting09:33
*** Wryhder has joined #openstack-meeting09:37
*** kukacz has quit IRC09:39
*** Lucas_Gray has quit IRC09:39
*** Wryhder is now known as Lucas_Gray09:39
*** kukacz has joined #openstack-meeting09:39
*** electrofelix has joined #openstack-meeting09:47
*** dkushwaha has left #openstack-meeting09:52
*** cheng1_ has joined #openstack-meeting09:56
*** e0ne has quit IRC09:56
*** jbadiapa has quit IRC09:59
*** Lucas_Gray has quit IRC10:04
*** Lucas_Gray has joined #openstack-meeting10:09
*** jbadiapa has joined #openstack-meeting10:12
*** jbadiapa has quit IRC10:29
*** hjwon has quit IRC10:40
*** jbadiapa has joined #openstack-meeting10:43
*** bbowen has quit IRC10:44
*** janki has quit IRC10:45
*** yamamoto has quit IRC10:50
*** e0ne has joined #openstack-meeting10:50
*** yamamoto has joined #openstack-meeting10:56
*** carlos_silva has joined #openstack-meeting10:58
*** yamamoto has quit IRC11:00
*** jrbalderrama has joined #openstack-meeting11:04
*** yamamoto has joined #openstack-meeting11:05
*** yamamoto has quit IRC11:05
*** njohnston has joined #openstack-meeting11:06
*** yamamoto has joined #openstack-meeting11:06
*** psachin has joined #openstack-meeting11:06
*** priteau has quit IRC11:08
*** ttsiouts has quit IRC11:09
*** tetsuro has quit IRC11:21
*** rcernin has quit IRC11:24
*** Wryhder has joined #openstack-meeting11:34
*** Lucas_Gray has quit IRC11:34
*** Wryhder is now known as Lucas_Gray11:35
*** hyunsikyang__ has joined #openstack-meeting11:37
*** adrianc has quit IRC11:41
*** hyunsikyang has quit IRC11:41
*** hyunsikyang__ has quit IRC11:42
*** hyunsikyang has joined #openstack-meeting11:43
*** janki has joined #openstack-meeting11:49
*** klindgren_ has quit IRC11:51
*** imsurit_ofc has quit IRC11:52
*** psachin has quit IRC11:54
*** klindgren has joined #openstack-meeting12:03
*** bbowen has joined #openstack-meeting12:04
*** finucannot is now known as stephenfin12:05
*** bbowen_ has joined #openstack-meeting12:06
*** raildo has joined #openstack-meeting12:08
*** bbowen has quit IRC12:08
*** adrianc has joined #openstack-meeting12:10
*** ttsiouts has joined #openstack-meeting12:10
*** jbadiapa has quit IRC12:11
*** adrianc has quit IRC12:24
*** markvoelker has quit IRC12:24
*** rbudden has joined #openstack-meeting12:32
*** adrianc has joined #openstack-meeting12:36
*** rfolco has joined #openstack-meeting12:37
*** enriquetaso has joined #openstack-meeting12:49
*** adrianc has quit IRC12:51
*** mriedem has joined #openstack-meeting12:54
*** adrianc has joined #openstack-meeting12:59
*** jaewook_oh has quit IRC13:00
*** liuyulong has joined #openstack-meeting13:00
*** eharney has joined #openstack-meeting13:03
*** yamamoto has quit IRC13:09
*** hyunsikyang__ has joined #openstack-meeting13:15
*** hyunsikyang has quit IRC13:17
*** jbadiapa has joined #openstack-meeting13:18
*** tssurya has quit IRC13:18
*** cheng1_ has quit IRC13:26
*** yamamoto has joined #openstack-meeting13:28
*** tashiromt has quit IRC13:33
*** lbragstad has joined #openstack-meeting13:34
*** Luzi has joined #openstack-meeting13:54
*** whoami-rajat has quit IRC13:55
*** mjturek has joined #openstack-meeting14:07
*** needscoffee is now known as kmalloc14:09
*** bbowen_ is now known as brbowen14:18
*** hongbin has joined #openstack-meeting14:29
*** adrianc has quit IRC14:36
*** jamesmcarthur has joined #openstack-meeting14:39
*** adrianc has joined #openstack-meeting14:39
*** factor has quit IRC14:48
*** igordc has joined #openstack-meeting14:49
*** yamamoto has quit IRC14:49
*** mattw4 has joined #openstack-meeting14:50
*** yamamoto has joined #openstack-meeting14:55
*** yamamoto has quit IRC14:55
*** yamamoto has joined #openstack-meeting14:56
*** yamamoto has quit IRC14:58
*** yamamoto has joined #openstack-meeting14:58
*** yamamoto has quit IRC14:58
*** cheng1 has joined #openstack-meeting14:58
*** yamamoto has joined #openstack-meeting14:59
*** diablo_rojo has joined #openstack-meeting15:02
*** adrianc has quit IRC15:02
*** evgenyl has joined #openstack-meeting15:02
*** yamamoto has quit IRC15:03
*** vishalmanchanda has quit IRC15:05
*** artom has joined #openstack-meeting15:06
*** adrianc has joined #openstack-meeting15:08
*** cheng1 has quit IRC15:09
*** cheng1 has joined #openstack-meeting15:10
*** Luzi has quit IRC15:12
*** eharney has quit IRC15:14
*** whoami-rajat has joined #openstack-meeting15:22
*** adrianc has quit IRC15:24
*** adrianc has joined #openstack-meeting15:27
*** dmsimard has joined #openstack-meeting15:30
*** jrbalderrama has quit IRC15:34
*** ttsiouts has quit IRC15:38
*** yamamoto has joined #openstack-meeting15:39
*** ttsiouts has joined #openstack-meeting15:40
*** yamamoto has quit IRC15:45
*** anteaya has joined #openstack-meeting15:50
*** raildo has quit IRC15:51
*** raildo has joined #openstack-meeting15:51
*** ttsiouts has quit IRC15:54
*** mlavalle has joined #openstack-meeting15:57
*** igordc has quit IRC15:58
*** cheng1 has quit IRC15:59
*** njohnston is now known as njohnston_16:00
*** njohnston_ is now known as 07EAA60LH16:00
slaweq#startmeeting neutron_ci16:00
*** njohnston_ has joined #openstack-meeting16:00
openstackMeeting started Tue Mar 19 16:00:24 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
*** njohnston_ is now known as njohnston16:00
slaweqok, lets start16:01
slaweqfirst of all Grafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:01
slaweqPlease open now :)16:01
slaweq#topic Actions from previous meetings16:02
*** ttsiouts has joined #openstack-meeting16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqfirst action:16:02
slaweqralonsoh to take a look at fullstack dhcp rescheduling issue https://bugs.launchpad.net/neutron/+bug/179955516:02
openstackLaunchpad bug 1799555 in neutron "Fullstack test neutron.tests.fullstack.test_dhcp_agent.TestDhcpAgentHA.test_reschedule_network_on_new_agent timeout" [High,Confirmed] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)16:02
slaweqI know that ralonsoh was looking into this one16:03
slaweqbut there was no data why network wasn't rescheduled to new dhcp agent after one agent was down16:03
slaweqso he send some dnm patch https://review.openstack.org/#/c/643079/ to get some more logs16:03
* mlavalle has to leave 45 minutes after the hour16:03
slaweqso he will probably continue this work as he is assigned to the bug16:04
slaweqnext one was:16:04
slaweqslaweq to talk with tmorin about networking-bagpipe16:04
*** armax has quit IRC16:04
*** jamesmcarthur has quit IRC16:04
mlavalleyou sent an email, didn't you?16:04
slaweqI sent email to Thomas today because I couldn't catch him on irc16:04
*** jamesmcarthur has joined #openstack-meeting16:05
slaweqif he will not respond, I will probably start this work for bagpipe project - it shouldn't be a lot of work to do16:05
slaweqok, and the last one from last week was:16:06
slaweqralonsoh to take a look at update_revises unit test failures16:06
slaweqIIRC this patch should address this issue https://review.openstack.org/#/c/642869/16:06
slaweqso thx ralonsoh we should be good with this :)16:06
mlavalleyeap, it looks like it16:07
slaweqand that was all actions from previous week16:07
slaweqany questions/comments?16:07
mlavallenot rom me16:08
*** cheng1 has joined #openstack-meeting16:08
slaweqok, lets go then to the next topic16:08
slaweq#topic Python 316:08
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:08
slaweqStadium projects etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:08
slaweqnjohnston: any updates?16:08
njohnstonno updates on this for this week.16:08
njohnstonI hope to spend more time with it later this week16:09
slaweqsure, that is not urgent for now16:09
mlavalleso I volunteered last time16:09
slaweqwe have more important things currently IMO :)16:09
mlavallefor one of them16:09
mlavallebut the etherpad seems changed16:09
njohnstonmlavalle: wasn’t that the tempest plugin work?16:10
slaweqmlavalle: I think You voluntereed for something else, trust me ;)16:10
mlavalleyeah, you are right16:10
slaweqmlavalle: You should tell that to my wife :P16:10
slaweqok, lets move on to the next topic16:11
slaweq#topic Ubuntu Bionic in CI jobs16:11
*** openstack changes topic to "Ubuntu Bionic in CI jobs (Meeting topic: neutron_ci)"16:11
slaweqlast week I think patch which switched all legacy jobs to be run on Bionic was merged16:11
slaweqyep, it's here: https://review.openstack.org/#/c/641886/16:12
slaweqin Neutron we are good with it16:12
slaweqas for stadium projects, we need https://review.openstack.org/#/c/642456/ for fullstack job in networking-bagpipe16:13
bcafarelslaweq: I still see ubuntu-xenial-2-node in .zuul.yaml ?16:13
slaweqbut this job is there non-voting, and even with this patch it's failing because of some other reason16:13
slaweqbcafarel: where?16:13
slaweqahh, right bcafarel16:14
slaweqso we need to switch our grenade jobs to be run on bionic too16:14
slaweqit's like that because we have specified nodeset in our .zuul.yaml file for them16:14
slaweqany volunteer to switch that to bionic?16:15
slaweqif no, I can do that16:15
bcafarelsince I raised it I can try to fix it :)16:15
slaweqthx bcafarel16:15
*** cheng1 has quit IRC16:15
slaweq#action bcafarel to switch neutron-grenade multinode jobs to bionic nodes16:16
slaweqfrom other stadium projects there is also issue with networking-midonet16:16
mlavalleshould we ask yamamoto?16:17
slaweqbut they are aware of it: https://midonet.atlassian.net/browse/MNA-1344 so I don't think we should bother a lot with that16:17
slaweqmlavalle: yamamoto know about this issues, I already mailed him some time ago16:17
njohnstonyes there was an ML thread16:17
*** jbadiapa has quit IRC16:17
slaweqand that's basically all about switch to bionic16:18
mlavallenot from me16:18
*** eharney has joined #openstack-meeting16:18
slaweqok, next topic then16:18
slaweq#topic tempest-plugins migration16:18
*** openstack changes topic to "tempest-plugins migration (Meeting topic: neutron_ci)"16:18
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo16:18
slaweqmlavalle: here You volunteered :)16:19
slaweqany updates about that?16:19
mlavalleI intend to work on this towards the end of the week16:19
njohnstonI pushed a couple of changes for fwaas16:19
bcafarelI think njohnston is the most ahead there16:19
njohnstonI need to work on the zuul job definitions16:20
slaweqyep, I saw today Your "super-WIP" patch :)16:20
slaweqit's pretty red16:20
njohnstonI’ll fiddle with it later in the week16:21
slaweqbut great that You started this work already :)16:21
slaweqthx njohnston16:21
slaweqok, so lets move on to the next topic then16:22
slaweq#topic Grafana16:22
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:22
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:22
slaweqYou have it already :)16:22
*** Lucas_Gray has quit IRC16:22
slaweqworst thing is IMO fullstack job in check queue16:23
slaweqwhich is on quite high numbers again16:24
slaweqbut today there is also some spike on neutron-tempest-dvr-ha-multinode-full job16:24
mlavalleyeah, fullstack is where the action / problem is16:25
slaweqmlavalle: yes16:25
slaweqaccording to this neutron-tempest-dvr-ha-multinode-full I would say - lets wait and see how it will be16:25
*** ttsiouts has quit IRC16:25
slaweqthere wasn't many jobs run today so this spike may be just because of some bad coincidence16:27
slaweqfrom good things: functinal jobs looks good currently finally :)16:27
slaweqany other comments on that?16:28
mlavalleis it not from me16:28
slaweqor can we move on to talk about fullstack?16:28
mlavalleI menat not from me16:28
slaweqok, lets move on then16:28
mlavallelet's move on16:28
slaweq#topic fullstack/functional16:28
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:28
slaweqI was looking into some fullstack failures today16:28
slaweqand I identified basically 2 new (for me at least) issues16:29
openstackLaunchpad bug 1820865 in neutron "Fullstack tests are failing because of "OSError: [Errno 22] failed to open netns"" [Critical,Confirmed]16:29
slaweqthis one is problem with open netns16:29
slaweqand second is https://bugs.launchpad.net/neutron/+bug/182087016:29
openstackLaunchpad bug 1820870 in neutron "Fullstack tests are failing with error connection to rabbitmq" [High,Confirmed]16:29
slaweqthat one is related to some issues with connectivity from agents to rabbitmq16:30
slaweqboth are quite often now so I set them as Critical and High priority for now16:30
slaweqbut I think we need some volunteers for them as I will not have cycles for both during this week16:30
mlavalledo we need manpower for them?16:31
slaweqmlavalle: yes, definitely16:31
mlavalleassigne me one16:31
mlavallethe one you think is more important16:31
slaweqI marked bug/1820865 as Critical because I think it happens more often16:32
mlavalleok, I take it16:32
slaweqgreat, thx mlavalle16:32
*** e0ne has quit IRC16:32
* mlavalle assigned it to himself16:32
slaweqif I will have some time, I will try to take a look at second one but I can't promise that16:32
slaweqso I will not assign it to myself yet16:33
mlavalleif I have time I will also try to get to the second one16:33
mlavalleI'll ping you if I get there16:33
*** lseki has joined #openstack-meeting16:33
slaweq#action mlavalle to check https://bugs.launchpad.net/neutron/+bug/182087016:33
openstackLaunchpad bug 1820870 in neutron "Fullstack tests are failing with error connection to rabbitmq" [High,Confirmed]16:33
openstackRemoving item from minutes: #action mlavalle to check https://bugs.launchpad.net/neutron/+bug/182087016:33
mlavalleyeap, it's the other one16:34
slaweq#action mlavalle to check https://bugs.launchpad.net/neutron/+bug/182086516:34
openstackLaunchpad bug 1820865 in neutron "Fullstack tests are failing because of "OSError: [Errno 22] failed to open netns"" [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)16:34
slaweq#action slaweq/mlavalle to check https://bugs.launchpad.net/neutron/+bug/182087016:34
slaweqnow it's good :)16:34
slaweqthx mlavalle for help16:34
slaweqI hope that when those 2 will be fixed, we will be in better shape with fullstack too16:35
slaweqany questions/comments?16:35
slaweqok, lets move to the next topic then16:35
slaweq#topic Tempest/Scenario16:36
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:36
slaweqmlavalle: as https://review.openstack.org/#/c/636710/ is merged, did You send patch to unmark tests from https://bugs.launchpad.net/neutron/+bug/1789434 as unstable?16:36
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,In progress] - Assigned to Miguel Lavalle (minsel)16:36
mlavalleslaweq: I'll do it today16:36
*** ttsiouts has joined #openstack-meeting16:36
slaweqmlavalle: thx16:37
slaweqother thing related to this is that still neutron-tempest-plugin-dvr-multinode-scenario is failing almost always.16:37
slaweqI was checking couple of results of such failed jobs today16:38
slaweqand there is no one single reason. We probably need someone who will go through some failed tests and report bugs for them.16:38
slaweqany volunteers?16:38
mlavalleI want to do that16:38
slaweqthx mlavalle :)16:38
mlavalleas long as I'm allowed to do it slowly16:38
slaweqmaybe You will be able to identify some groups of failures and report them as bugs that we can track them later16:39
mlavallemy goal is a little broader16:39
mlavalleI want to make that job stable generally16:39
*** jbadiapa has joined #openstack-meeting16:39
slaweqthat would be great definitelly16:39
slaweq#action mlavalle to debug reasons of neutron-tempest-plugin-dvr-multinode-scenario failures16:40
slaweqok, and that's all from me regarding scenario jobs16:41
bcafarelnone here16:41
*** kopecmartin has quit IRC16:42
slaweqso one last thing we I wanted mention is16:42
slaweqthx njohnston we have fixed our first os-ken bug: https://storyboard.openstack.org/#!/story/2005142 - thx a lot njohnston :)16:42
slaweqand with this optimistic accent I think we can finish our meeting a bit earlier today :)16:43
mlavalleThanks everybody16:43
slaweqand let mlavalle to go where he need to go16:43
slaweqthanks for attending16:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:43
openstackMeeting ended Tue Mar 19 16:43:26 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-03-19-16.00.html16:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-03-19-16.00.txt16:43
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-03-19-16.00.log.html16:43
*** mattw4 has quit IRC16:45
*** mlavalle has left #openstack-meeting16:46
*** njohnston is now known as n8johnston16:47
*** 07EAA60LH is now known as njohnston16:47
*** cheng1 has joined #openstack-meeting16:49
*** n8johnston has quit IRC16:57
*** cheng1 has quit IRC17:04
*** mattw4 has joined #openstack-meeting17:06
*** rsimai is now known as rsimai_away17:08
*** iyamahat has quit IRC17:11
*** jaypipes has joined #openstack-meeting17:16
*** igordc has joined #openstack-meeting17:16
*** zhubx has quit IRC17:19
*** zhubx has joined #openstack-meeting17:19
*** gyee has joined #openstack-meeting17:24
*** priteau has joined #openstack-meeting17:25
*** iyamahat has joined #openstack-meeting17:26
*** enriquetaso has quit IRC17:26
*** janki has quit IRC17:29
*** iyamahat_ has joined #openstack-meeting17:29
*** iyamahat has quit IRC17:32
*** jamesmcarthur has quit IRC17:39
*** ttsiouts has quit IRC17:40
*** yamahata has joined #openstack-meeting17:43
*** jamesmcarthur has joined #openstack-meeting17:54
*** ivy has joined #openstack-meeting18:05
*** priteau has quit IRC18:07
*** jamesmcarthur has quit IRC18:12
*** jamesmcarthur has joined #openstack-meeting18:14
*** jamesmcarthur has quit IRC18:14
*** jamesmcarthur has joined #openstack-meeting18:14
*** enriquetaso has joined #openstack-meeting18:19
*** cloudrancher has quit IRC18:23
*** cloudrancher has joined #openstack-meeting18:23
*** cloudrancher has quit IRC18:24
*** tobiash has joined #openstack-meeting18:25
*** cloudrancher has joined #openstack-meeting18:25
*** senrique_ has joined #openstack-meeting18:32
*** kopecmartin has joined #openstack-meeting18:34
*** enriquetaso has quit IRC18:34
*** rbudden has quit IRC18:37
*** ivy has quit IRC18:44
*** ivy has joined #openstack-meeting18:45
*** sridharg has quit IRC18:46
*** ivy has quit IRC18:49
*** ivy has joined #openstack-meeting18:49
*** jbadiapa has quit IRC18:50
*** Shrews has joined #openstack-meeting18:59
clarkbAnyone here for the infra meeting?18:59
clarkb#startmeeting infra19:01
openstackMeeting started Tue Mar 19 19:01:02 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-March/006296.html19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbI'll be AFK next week from the 25-28th19:01
clarkbAlso doesn't look like anyone wanted to run against me for PTL so I get to do that again19:02
corvusclarkb: congratulations!19:02
clarkbIf you want to volunteer to chair the meeting next week let me know as I won't be able to do it19:02
clarkb#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-03-12-19.01.txt minutes from last meeting19:03
clarkbianw: I htink you rotated those backups?19:03
clarkbanything interesting to say about that?19:03
ianwyes, please review19:03
ianw#link https://review.openstack.org/64445719:03
*** diablo_rojo has quit IRC19:03
ianwthat's all :)19:04
clarkbthe other item was project renames19:04
* jroll lurks19:04
clarkbdo we want to talk about that now or during the opendev topic?19:04
* dtroyer sneaks in19:05
diablo_rojo_phonDedicated PTL https://usercontent.irccloud-cdn.com/file/87xmHZDF/IMG_20190319_120415.jpg19:05
clarkbwe can pick it up during the opendev topic19:05
clarkb#topic Specs Approval19:05
*** openstack changes topic to "Specs Approval (Meeting topic: infra)"19:05
clarkbThere are no specs to review19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkbWe've updated more servers to puppet 4 in the last week. So far the only real gotcha has been that the pip provider doesn't like the warnings that pip prints on stderr19:06
clarkbso if pip is emitting warnings we have to fix those (last time was via upgrade of cyptography and pyopenssl19:07
clarkbcorvus: anything new on the image building front? I guess that its actually in production now?19:07
clarkbwith documentation and everything?19:07
corvusyep, nothing substantial new there; just cleaning up a few bugs19:08
clarkb#topic Opendev19:09
*** openstack changes topic to "Opendev (Meeting topic: infra)"19:09
clarkbI managed to fixup the bug tracker situation in gitea19:09
clarkbthat should be all done now19:09
corvusyay!  thanks!19:10
clarkbWant to talk about project renames now?19:10
fungii've had the initial redirects change up for review for a while, looking for feedback19:10
fungi#link https://review.openstack.org/642173 Set up legacy git redirect sites19:10
jrolleverybody wants to, judging by the ML19:10
corvus#link mailing list thread about openstack namespaces: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003943.html19:12
corvusjroll: that thread?19:12
jrollsorry, yes, that one19:12
jrollit seems we have some traction, assuming it's died down I'll do a governance change to get the general ack19:13
clarkbya so far I have only heard positive things19:13
jrollwhen are we looking to try and get renames done?19:13
fungii haven't really seen any overt objections on that thread, agreed. mostly just questions19:13
clarkbjroll: April 19 is the day we pencilled in last week19:14
fungisame time as the switch in domain names, ideally19:14
clarkband we havne't run into any major issues since so that seems to still be on track19:14
jrollcool, that seems doable19:14
corvusjroll: what's your tl;dr read on that thread?19:14
jroll(assuming nobody comes and splatters random colors on the shed)19:14
corvuswas it leaning toward one of your 3 options?19:15
fungii think it was some of option 3 and some of ttx's option 419:15
jrollcorvus: I have to re-read to get a count, sounds like either (2) or ttx's option is the winner19:15
* jroll finds that link19:15
jroll#link http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003971.html19:15
corvusgot it, thanks!19:15
corvusi'll be sure to read the whole thread after the meeting; i somehow missed that. sorry.19:16
*** mattw4 has quit IRC19:16
jrollnow that I think about it, both of those have some nebulous naming activities to do, but I think we can meet april 1719:16
jrollno worries :)19:16
* jroll s/17/19/19:16
fungithere's still some question as to whether team-oriented namespaces make more sense, and also what to do about projects with no representation on the openstack map diagram thingie19:16
corvuscool, those both sound great, and i agree, that sounds plausible19:17
clarkbdtroyer: things look good your side?19:17
*** senrique_ has quit IRC19:18
dtroyerclarkb: really quiet so far, at this point it looks like we'll just be moving to a starlingx namespace and retiring 3 or so repos19:18
fungiand dropping the stx-prefixes, or have you decided?19:18
dtroyeryes, dropping stx- too19:18
clarkbI expect zuul will be ready19:19
clarkbready to talk about the git:// to https:// transition again?19:20
clarkbI wanted to make sure that we don't get stuck in limbo on that topic19:20
corvusyeah, i think ianw wanted a decision on that at this meeting, and i agree we should do that :)19:20
*** ttsiouts has joined #openstack-meeting19:20
ianwi did post about it as mentioned in the last meeting, but didn't generate as much discussion19:20
ianw#link http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html19:20
clarkbah it went to that list not the infra list which is probably why i missed it (I'm not great at keeping up there)19:21
ianwsorry i figured everyone would want to have an opinion since it might touch their repos, but it was maybe a little obscure19:21
fungiyeah, and it has a bit of a devstack-focus anyway19:22
clarkbfwiw your proposal seems reasonable to me19:22
corvusi think i'm with ianw and on board option 119:22
fungisame, option 1 for me19:22
*** enriquetaso has joined #openstack-meeting19:22
clarkbin that case it sounds like we can go ahead with 1) as proposed19:23
corvuswhen should we actually upload the changes?  do we want to try to do that at the start of a weekend or something?19:23
ianwgiven that it looks like from the prior discussion we might be doing some fairly complex namespace swizzles, i think that avoids us having to synchronize19:24
fungiprojects are sure to be putting through a ton of other changes after the transition to update domain names and project names and namespaces and stuff in their readmes and contributor docs anyway19:24
clarkbcorvus: maybe ianw can do it during his monday morning which is sunday for most of us19:24
ianwsure, i can make it drizzle in over 24 hours19:25
corvusianw: i think if you do it then, you can do it all at once19:25
*** jgriffith has quit IRC19:26
corvuszuul is pretty idle over the "weekend"19:26
corvusand hopefully that will reduce the window for copycat patches19:26
clarkbsounds like a plan19:26
corvus(i still can't believe that's a thing we have to consider)19:27
ianwok, i will set it all up in a screen on bridge.o.o and we can check it over19:27
corvus(i mean, i believe it, i'm just... you know, wow.)19:27
*** electrofelix has quit IRC19:27
clarkbanything else opendev related?19:28
*** e0ne has joined #openstack-meeting19:28
clarkbsounds like now. Onward!19:28
clarkb#topic Storyboard19:29
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:29
clarkbshould I undo?19:29
corvusyeah, sorry one more quick thing19:29
ianwoh, yeah, one more thing19:29
openstackRemoving item from minutes: #topic Storyboard19:29
corvusshould i send out an email announcing the date now?19:29
clarkbcorvus: ++ I don't think we have anything coming up that will prevent it at this point19:29
ianw(for me) we agree to force merge outstanding git://->https:// changes too?  what date should we do that?19:30
fungiyes, should reduce some further confusion over the anticipated timeframe for things19:30
fungithe announcement i mean19:30
corvusianw: i'm ambivalent about that -- since i don't expect *functional* breakage, i'm less inclined to force-merge, but i don't object if folks think it's worthwhile.19:31
corvusso, consider me a weak -1 on force-merge but happy to support it if there are other +1s19:31
clarkbI think a deadline helps get eyeballs on it19:31
*** jgriffith has joined #openstack-meeting19:31
clarkbthe 12th gives people a couple weeks if we want it done ahead of time19:32
fungiyeah, i'm honestly more concerned about the .gitreview and {.,}zuul{.d/*,}.yaml edits not lingering19:32
*** gouthamr_ has joined #openstack-meeting19:34
ianwok, ummm i like the idea of a deadline being a call to action -- i'll draft something in the review commit log as part of the change; i'll request comments on in a gerrit review of the scripts19:35
clarkbianw: sounds good19:35
clarkb#topic Storyboard19:35
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:35
clarkbok anything storyboard to talk about?19:35
clarkbdiablo_rojo_phon says no19:35
clarkbthere are changes to review19:35
clarkbmordred isn't around today but any idea how his patches for swift things are going?19:35
fungiyeah, lots and lots of sb changes to review19:36
clarkbsounds like they are still outstanding due to changes needed in the sdk19:37
clarkbLets move on since diablo_rojo_phon is eating lunch19:38
fungiSotK just pushed up a couple of testing-related improvements as well19:38
*** gouthamr_ has quit IRC19:38
diablo_rojo_phonYes please lol19:38
*** pabelanger has joined #openstack-meeting19:38
* fungi lets diablo_rojo_phon get back to her lunch. clarkb doesn't actually get to eat though19:38
clarkb#topic General Topics19:38
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:38
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:39
clarkbServer upgrades continue19:39
clarkbAFS is completely done now which is nice to get behind us19:39
clarkbfungi: how are wiki things?19:39
fungi#link https://review.openstack.org/643476 Switch from PHP5 to default PHP (PHP7 on Xenial)19:39
fungithat's needed to progress further on the wiki-dev02.openstack.org deployment19:40
fungiif any infra-puppet-core is available to review, it's a one-character removal19:40
clarkbI can take a look today19:40
clarkbThe last item on my list is PTG planning19:41
clarkb#link https://etherpad.openstack.org/2019-denver-ptg-infra-planning19:41
*** jamesmcarthur has quit IRC19:41
clarkb#link https://www.openstack.org/ptg#tab_schedule Draft schedule. We have Friday and Saturday in a shared room with the QA team.19:41
dmsimardI added an item after PTG planning, needs refresh :D19:41
clarkbThe draft schedule has us in a room friday and saturday with the qa team19:41
corvusclarkb: is there any chance we could shift that to thurs-friday?19:41
*** jamesmcarthur has joined #openstack-meeting19:42
clarkbcorvus: we can ask, I don't actually know19:42
clarkbI think the saturday is a conflict for fungi too19:42
clarkbI'll investigate that19:42
fungiyeah, the tc also wants a full day on saturday19:43
corvusin addition to that, i would be largely idle on thursday19:43
corvusso if we can do something on thursday and possibly friday, it's a better use of time and we dodge fungi's conflict19:43
clarkb#action clarkb ask about infra ptg days being thursday friday19:43
corvusif it doesn't work out, maybe we can just find a nice spot on thursday and hack on server container stuff anyway?19:44
clarkbOk next up is dmsimard's ara github replication item19:44
clarkbI think this is serving as a template for replication to git remotes via zuul?19:45
dmsimardindeed, I've written a role with a job to test it: https://review.openstack.org/#/q/topic:upload-git-mirror19:45
*** jamesmcarthur has quit IRC19:45
*** jamesmcarthur_ has joined #openstack-meeting19:45
dmsimardIt should hopefully be flexible enough to push from anywhere to anywhere over SSH19:46
corvusdmsimard: great, thanks!  are those ready for review now?19:46
dmsimardcorvus: they are19:46
corvusi will (re-)review them asap19:46
dmsimardSo once we set that up, should we remove ara from the gerrit github replication ?19:47
corvusright now our replication is openstack*19:47
corvusso it might be tricky to pull one out...19:47
dmsimardYeah I looked at the replication config: configuration19:48
corvusdmsimard: but....19:48
corvusdmsimard: you could *additionally* replicate to another repo pretty easily19:48
corvusdmsimard: like, you could replicate openstack/ara to dmsimard/just-testing-git-pushes19:49
corvusi think that would be a sufficient "production test" before we tell everyone to start using that19:49
fungisounds great to me19:49
dmsimardThe thing is I'd like the ability to *move* that github repo and then once it's moved, keep replicating to the new repo19:49
dmsimardThe reason for the move would be to carry stuff like watchers/stars/forks/pull requests/etc around19:50
fungibasically asking that the namespace moves in gitea also be reflected with org transfers in github?19:50
fungithe tricky bit (perhaps less so for you though) is that last i looked you need a common admin account in both the source and target orgs to make that work19:51
dmsimardfungi: I don't mind where ara ends up being replicated in gitea19:51
*** e0ne has quit IRC19:51
clarkbfungi: ya we might have to bootstrap that19:51
clarkbfungi: but once its done we should be able to remove ourselves from all the orgs19:51
dmsimardI'm admin in the destination org, I'm not sure I have admin in the openstack org19:51
corvusdo we have an automated way to do that transfer?19:52
dmsimardnot to my knowledge, it's a manual transfer in the github ui19:52
fungithat's the other problem... last i looked, org transfers weren't exposed in the gh api19:52
corvusso if we did this, we may need to perform 1500+ transfers manually through the gh web ui?19:52
corvusi don't think that's something i can commit to.19:53
*** iyamahat__ has joined #openstack-meeting19:53
clarkbwe should double check that19:53
clarkbbecause ya that will be painful19:53
dmsimardcorvus: where would those 1500+ projects be moved to ?19:54
corvuswell, it would if we did it.  but i don't think we have said that we would.19:54
corvusit hasn't been in any of the project planning so far19:54
fungiwe've made a big point of saying we'll make sure the git urls we've been hosting continue to work and get redirected to the new domain/orgs/repos but nobody's actually asked if the same will be true of repos we're replicating to github. i know a lot of people have remotes and bookmarks to github against our recommendation, and may not realize this is going to impact them as well19:55
clarkbits definitely something we should do if feasible19:55
corvusdmsimard: i don't know where they will be moved to; presumably wherever their owners wish?19:55
corvusfungi: we've said that if you aren't in the openstack* namespace, automatic replication will cease.19:55
dmsimardcorvus: fair, I went with the assumption that there was not going to be many projects in a situation similar to ara19:56
fungicorvus: right. most projects are *currently* in the openstack namespace though19:56
corvusdmsimard: you may have missed the opendev topic earlier19:56
fungi~most of the plans supported so far in the openstack-discuss ml thread will involve evicting a majority of the repositories currently in that namespace19:56
*** rbudden has joined #openstack-meeting19:56
*** iyamahat_ has quit IRC19:56
fungiincluding official openstack projects19:56
corvusyeah that ^19:57
clarkbtime check we have ~3 minutes left19:57
fungiwhat would be left in the openstack namespace would either be just the ~60 service repos, or possibly nothing whatsoever19:57
corvusdmsimard: can you look into whether there's a way to automate that?19:57
dmsimardfungi: what does eviction imply in practice ? no more replication ? deletion of the project ? moving it elsewhere ?19:57
fungidmsimard: that hasn't been covered yet exactly19:58
corvusdmsimard: it means a rename in gerrit, and whatever the project wants to do on github.19:58
dmsimardfungi: ok so github.com/openstack will remain but only with the official official things19:58
fungilikely a very small subset of the official official things19:58
corvusdmsimard: that hasn't been decided yet, but that's the gist of the most likely options.19:58
fungiand perhaps not even those19:58
dmsimardI'll explore if there is an easy way to automate the transfer19:59
corvusdmsimard: thanks!19:59
clarkbAnd we are basically at time19:59
clarkbthank you everyone19:59
clarkband yes I somehow managed to eat lunch too :)19:59
fungithanks clarkb!19:59
funginow, dessert19:59
clarkbFind us on IRC (#openstack-infra) or on the openstack-infra@lists.openstack.org mailing list if there are things to followup on20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Mar 19 20:00:15 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-03-19-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-03-19-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-03-19-19.01.log.html20:00
*** ttsiouts has quit IRC20:01
*** jamesmcarthur_ has quit IRC20:02
*** jamesmcarthur has joined #openstack-meeting20:03
*** Shrews has left #openstack-meeting20:04
*** mattw4 has joined #openstack-meeting20:06
*** jamesmcarthur has quit IRC20:08
*** jamesmcarthur has joined #openstack-meeting20:08
*** brbowen has quit IRC20:10
*** Lucas_Gray has joined #openstack-meeting20:15
*** yamamoto has joined #openstack-meeting20:18
*** artom has quit IRC20:20
*** yamamoto has quit IRC20:22
*** diablo_rojo has joined #openstack-meeting20:25
*** iyamahat_ has joined #openstack-meeting20:26
*** iyamahat__ has quit IRC20:29
*** senrique_ has joined #openstack-meeting20:33
*** enriquetaso has quit IRC20:35
*** e0ne has joined #openstack-meeting20:41
*** senrique_ has quit IRC20:43
*** mjturek has quit IRC20:45
*** e0ne has quit IRC20:46
*** b1airo has joined #openstack-meeting20:53
*** ttsiouts has joined #openstack-meeting20:54
*** oneswig has joined #openstack-meeting20:56
*** martial has joined #openstack-meeting20:59
martialGood day20:59
*** jtopjian has joined #openstack-meeting21:00
*** jmlowe has joined #openstack-meeting21:00
oneswigGreetings guys21:00
b1airo#startmeeting scientific-sig21:00
openstackMeeting started Tue Mar 19 21:00:45 2019 UTC and is due to finish in 60 minutes.  The chair is b1airo. 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
jmloweI expect rbudden to make an appearance today21:00
b1airo#chair oneswig21:01
openstackCurrent chairs: b1airo oneswig21:01
oneswigjmlowe: so quickly proven correct21:01
b1airo#chair martial21:01
openstackCurrent chairs: b1airo martial oneswig21:01
oneswiggreetings all21:01
b1airohopefully joe manages to get on soon21:01
jmloweI may have cheated and compared calendars with him within the past 45 min21:01
rbuddenbeen far too long21:02
*** janders has joined #openstack-meeting21:02
b1airomorning janders21:03
martialI invited Maxime and Alex to join this session to see how we run those sessions, they are proposing to discuss their work with us next week :)21:03
oneswigAlthough I am going to Texas next week to see our friends at Dell21:04
martialI will help start the meeting21:05
oneswigI expect I'll be jet-lagged so still in about the right time zone!21:05
martialwas just about to email you about it21:05
janderstexan bbq! :)21:05
jtopjianI'm here! sorry21:06
oneswigjanders: damn right21:06
oneswighi jtopjian, welcome21:06
*** priteau has joined #openstack-meeting21:07
jandershave you guys heard the news about NVIDIA's Mellanox acquisition?21:07
rbuddenshould be interesting21:07
*** eharney has quit IRC21:07
oneswigMixes things up a little!21:07
jandersI sense this should push the HPC side of things more21:08
janders(unlike with some other potential buyers who were on the table)21:08
martial yep, outbid Intel by a lot too21:08
oneswigThere's a good deal of talk about the high performance data centre21:08
oneswigwhich sounds good to me21:08
jandersany thoughts on how this would affect Mellanox'es OpenStack work?21:09
oneswigneutral-to-positive, I'd guess21:10
b1airoi doubt it will have any immediate impact janders21:10
janderssame feelings here21:10
jmloweI'm kind of banking on Mellanox continuing to do good things for both ceph and openstack21:10
*** simon-AS559 has joined #openstack-meeting21:10
jandersI came across this yesterday: https://www.nextplatform.com/2019/03/18/intel-to-take-on-openpower-for-exascale-dominance-with-aurora/21:10
oneswigb1airo: increased interest in virtualised gpu direct, perhaps?21:10
b1airothough a general HPC-datacentre trend might make NVIDIA more interested in e.g. Cyborg21:10
b1airopossibly oneswig21:11
b1airoor some new version thereof (more likely)21:11
jmloweWhich I find astounding, "We've delivered nothing, but double our money an we'll deliver something even better, we priomise"21:11
jandersyeah.. and the interconnect bit is "interesting"21:11
jandersas much as I am a fan of competitive landscape, no one except Mellanox seems to have the right answers to the right questions about advanced fabric features21:12
oneswigThat's more than a ripple in the pond, janders, if it's true it's a huge splash21:12
b1airothey are also guilty of claiming to have the answers 2 years before they have a product containing any of them, but i guess everyone knows that now21:13
jmloweWho exactly signed off on 1/2 billion to a company that just completely botched your 1/4 billion dollar acquisition?21:13
b1airoNVIDIA's acquisition history is not great mind you, would have been interesting to have a front row seat to Mellanox boardroom talks when that topic came up21:14
jmloweI'm still waiting on my sriov live migration from Mellanox21:14
b1airolols, good luck21:14
b1airothere is some upstream kvm work that looks promising - vfio migrations21:14
*** tobiash has left #openstack-meeting21:15
b1airook, we should move along and pass the baton to jtopjian21:15
jmloweI might get live migration with vgpus from nvidia though21:15
jandersjmlowe: are you thinking eth or ib for live migration?21:15
jtopjiansure. I shouldn't take long, but happy to answer questions, too.21:16
jandersI think SRIOV is tricky, but the RDMA/QP part is even trickier21:16
b1airo#topic Nomad for GPU container workload management21:16
*** openstack changes topic to "Nomad for GPU container workload management (Meeting topic: scientific-sig)"21:16
jmlowejanders: We wound up pitching mellanox eth21:16
b1airostow it for the wrap-up lads :-)21:16
martialjtopjian: and link for slides or external material?21:16
jtopjiannone :)21:16
b1airogive us the pitch jtopjian21:16
jtopjianThere's a group we're working with who have a stack of nine servers, each with four GPUs. Currently, users log into each server directly and perform whatever GPU processing there.21:17
b1airowas i correct that they are doing exploratory data-science and ML stuff jtopjian ?21:17
jtopjianThat's correct21:17
jtopjianThe group has a wide range of knowledge and skill as well as a wide range of what they're working on.21:18
jtopjianThey asked us if we could do anything to help automate job submission. We figured we'd try a bit of an experiment and do something totally different.21:18
oneswigI guess these are all single node workloads, right?21:18
jtopjianPossibly. I don't think there was ever enough parallel work for a node to be running more than one job :)21:19
jtopjianUnfortunately we were not able to get direct access to the hardware, due to a myriad of non-technical reasons, so we set up a PoC cluster in our OpenStack cloud: 5 instances, one control node and 4 worker nodes with 1 GPU each21:20
martialfor a second I though it was 4 GPUs per node21:20
jtopjianThe existing cluster is. We could not get physical access to it.21:21
jtopjianSo we build a virtual PoC instead.21:21
jtopjianWe had a nomad master on the control node and a worker on each one. The only Nomad driver we used was "raw_exec" which basically just runs a shell command on the root filesystem. The reason we went with this route was because the group had a second request about Singularity support.21:21
jtopjianNomad 0.9-dev (master branch) has support for GPU polling. It'll poll the amount of memory the GPU cards are using and schedule jobs that way. So I had to compile Nomad from source, but that's not terribly hard at all.21:22
*** maxhub_ has joined #openstack-meeting21:22
jtopjianWith all of that in place, I set up some sample jobs and shared it out21:23
jtopjianAnd then waited for feedback21:23
jtopjianout of six people who used the cluster, I received feedback from 2.21:23
b1airo#link https://www.hashicorp.com/products/nomad21:23
jtopjianRight, some quick background: Nomad is a very basic scheduler. It supports various execution styles (batch, service) and drivers (docker, exec, qemu).21:24
jtopjianJobs are declared using an HCL-type syntax. If you've worked with Terraform, Packer, etc - it's the same.21:24
b1airo#link https://github.com/hashicorp/hcl21:25
jtopjianOne person "got it" and one person did not.21:25
jtopjianI'm quite new to working with data analysis, ML etc and learned that there are a number of different ways users work on data. I assumed we'd just give them a bunch of GPUs with a scheduler and they'd have a field day21:26
b1airoheh, users are the hardest part of this world21:26
jtopjianThe person with positive feedback was at this phase of their work: they had some code they wanted to run repeatedly with different arguments and Nomad did this quite well (you can crate "parameterized jobs" which repeat jobs with new input)21:27
jtopjianThe person with negative feedback had no code written and wanted to be as close to the GPU as possible.21:27
*** woeifwoegihwoghw has joined #openstack-meeting21:27
jtopjianSo they wondered why they couldn't get shell access to the GPU and thought it was a bother to have to commit or copy their code somewhere each time they ran a job21:28
jtopjianSo it was a learning experience.21:28
oneswigjtopjian: what is the execution environment nomad creates for a job that might get in the way for this user?21:28
*** woeifwoegihwoghw is now known as alexandre_b21:28
martialany into into nvidia-docker (v2) to try to give people access to the bare metal resources through an abstraction layer (seems to be very "core" OpenStack so far or am I missing something?)21:29
jtopjianWe used "raw_exec" which just ran a command on the root filesystem. So whatever you have installed on the OS is what you have access to.21:29
jtopjianBut Nomad also allows for chroot execution, docker execution, etc21:29
jtopjianI would have used Docker, but a few users wanted to use Singularity instead.21:29
jtopjianSo "raw_exec" basically just exec'd the singularity command with an image the user made available21:30
martial(the HPC ... we need root squash issue ... re: Docker)21:31
*** igordc has quit IRC21:31
b1airodunno about jtopjian , but i can't parse that question (was it a question?) martial ...21:31
jtopjianSo that's the summary of the PoC. As for next steps, I've learned that having job submission access is just a small part of what these users want, so I'm going to be looking at something like Kubeflow to see if that can provide better features for them.21:31
oneswigDoes it assume a network filesystem - or how is data and code copied if not?21:32
jtopjianNomad can download "artifacts". Unfortunately it only supports a few methods such as http and git at the moment.21:32
jtopjianIn your job spec, you declare different artifacts you want the worker to download and it'll pull them. The artifacts can also be interpolated so you can have an input variable of a version to download a certain version of something21:33
b1airojtopjian: do they need to turn these things into services with jobs that will be spun up in the cluster?21:33
oneswigAnd I guess outputs need something too?21:33
jtopjian@b1airo we used the "batch" scheduler which ran jobs once21:33
jtopjian@oneswig Nomad will save the stdout for review. For saving data somewhere else, that's something I didn't explore.21:34
oneswigI guess there's many ways that can be approached.21:34
b1airoit sort of sounds like the primary use-case is interactive exploration/design-iteration style work21:34
jtopjianHowever, one thing I was not a fan of was that Nomad does not keep logs around long. It expects you to send logs to a more robust logging system. While I understand the intention of the design, it felt lame21:35
b1airoif that's true i wonder whether container orchestration is really buying them anything?21:35
jtopjian@b1airo actually, no. This was more for a something along the lines of "I have a large dataset that I want to run a known good piece of code on for a few hours"21:36
jtopjianAnd so one piece of learning on my part was that most users are actually in the exploratory phase which made this cluster harder to work with.21:36
jtopjianThey really just need easy access to, say, Jupyter with GPU21:36
oneswigThe world needs that :-)21:37
b1airohow had some of them come to Singularity already jtopjian ?21:38
jtopjianThat's a good question. There were 3-4 users who were very keen on it, but others in the group who had not heard of it.21:40
jtopjianI'm not sure how the one group came across it21:40
b1airohad those 3-4 already been exposed to HPC in some way?21:40
jtopjianYes and I believe they wanted Singularity for this PoC because they were unable to use it in their institution's existing clusters21:40
martial(b1airo not a question)21:41
oneswigWhat was Singularity gaining for them, specifically?21:42
b1airowhich leads me to the next question, why not Slurm/PBS (plus Singularity or whatever) etc instead of these higher level programming interfaces ?21:42
jtopjian@oneswig: Again, good question and I'm not sure. Personally, I didn't mind using Singularity for this (I had to learn it to implement it) but I wasn't able to figure out what the big difference between it and Docker was.21:43
oneswigWere they wanting to use images from Singularity hub?21:43
b1airoi suspect you'd have to sit down with the users for a few hours to see how they were actually using it. i guess they maybe just learned how to create Singularity images and didn't know Docker images are very similar and compatible ?21:44
jtopjian@b1airo Slurm was mentioned in the first meeting and we chose not to implement it for two reasons: 1) it's been done and we wanted to take a chance and 2) part of our interaction with users is to... how do I want to say... work with them outside of an academic context. Being a little facetious: I don't see too many Medium articles on Slurm :)21:44
jtopjian@oneswig They had their own images to use21:45
b1airoSingularity Hub... what are people's thoughts? i went looking for an Intel optimised tensorflow container the other day and it felt like a mess21:45
oneswigNot tried using it b1airo21:45
*** senrique_ has joined #openstack-meeting21:46
jtopjianAnd "sit down" - yes, this is something we plan to do. We feel there's a big gap between students/researchers/users and infrastructure teams like my group. We want to bridge that21:46
oneswigSometimes people call that bridge you're making "ResOps" - is that familiar?21:48
*** goldenfri has joined #openstack-meeting21:48
jtopjianIt's not! That's new to me :)21:49
martialwhat were the advantages of Nomad for this setup?21:49
oneswigkind of derivative but fits the bill21:49
*** senrique__ has joined #openstack-meeting21:50
b1airojtopjian: sure, it's great you're getting to do some exploration. though i'd challenge you on the "academic" context - HPC is a much bigger industry than just universities. anyway, i think yours is the first real-world example i've seen of attempting to push the status quo of workload management in this space. convergence of container orchestration and hpc workload management was raised in a couple different forums21:50
b1airoat SC last year, so you're on trend :-)21:50
jtopjianExactly: from the specs which were discussed, it checked off all the boxes. Nomad, being a single binary, made deployment really quick and simple (ignoring I had to compile it, but I'm familiar with Go so that was fine). In practice, it helped us uncover a lot of missing knowledge we had about data processing.21:51
jtopjianTo be clear: I was (and am not) not trying to challenge status quo or indoctrinate people. Part of my job is to do experiments like this.21:52
*** whoami-rajat has quit IRC21:52
*** senrique_ has quit IRC21:52
jtopjianIf it was requested, I'd have no problems deploying something like Slurm for this group. But if I have the opportunity to explore different approaches, I'll take it.21:53
*** senrique_ has joined #openstack-meeting21:53
martialstill it sounds pretty fun, and a good setup21:53
martialThanks for sharing21:53
b1airosome other interesting examples floating around like what CERN is doing on top of Magnum, but that seems to be more about using a dynamic k8s cluster on a per-workload basis21:53
oneswigIn a similar vein, I'd be very interested to hear about anyone's experiences with Univa NavOps - https://kubernetes.io/blog/2017/08/kubernetes-meets-high-performance/21:54
jtopjianIndeed. It was a great learning experience. Nomad itself works great as a very foundational scheduler. But it's truly foundational. You'll need to add things on top of it to make it more user-friendly.21:54
jtopjianIn another similar vein, (I can't remember if I mentioned Kubeflow earlier in this meeting), Kubeflow is on my list to look at.21:54
*** senrique__ has quit IRC21:55
*** senrique__ has joined #openstack-meeting21:56
b1airoyeah that sounds interesting too, suspect it might have a broader potential audience21:56
oneswigThanks jtopjian - very interesting to hear about your work21:56
b1airoyou got Magnum in any of your clouds jtopjian ?21:56
jtopjian@oneswig very welcome!21:57
*** diablo_rojo has quit IRC21:57
jtopjian@b1airo Yes, we support both Swarm and Kubernetes21:57
b1airoyes +1, thanks jtopjian , interesting stuff21:57
rbuddenindeed, thanks for sharing21:57
b1airowould make a good lightning talk if you're in Denver :-)21:57
janders+1 thank you21:57
jandersgreat idea!21:58
jtopjianUnfortunately I won't make it to Denver :/21:58
oneswiggoing back to the NextPlatform article janders shared - see the reference to "Intel OneAPI" at the top of this - http://3s81si1s5ygj3mzby34dq6qf-wpengine.netdna-ssl.com/wp-content/uploads/2019/03/argonne-aurora-tech.jpg - I wondered if that was an IaaS API but it seems not...21:58
*** senrique_ has quit IRC21:58
jandersregarding jmlowe's live migration concenrs, I found this:21:59
janderscopying hardware state for bm migration sounds like a nightmare. But.. if an identical image were to be spun up on identical hardware, maybe copying the delta it wouldnt actually be that bad..22:00
jandersinteresting idea :)22:00
oneswigLive migration of bare metal?  "1) power off server, 2) move server to new rack, 3) power on server again?"22:00
jmloweI used to use openvz and was able to live migrate with that22:00
jmloweeffectively live migration of containers22:01
jandersa friend used to leverage dual PSUs and LACP to move servers between racks without powering off..we used to make jokes that's the bm livemigration22:01
*** iyamahat__ has joined #openstack-meeting22:01
janderstrue.. container could be that shim layer they are referring to22:01
b1airothe vfio migration work that is being discussed upstream at the moment sounds like it is allowing for vendor-specific state capture and transfer22:01
b1airoooh, we're overtime!22:02
jandersthanks guys! great chat22:02
b1airothanks all, good turnout!22:02
oneswigThanks all22:02
janderssee you next week22:02
rbuddencatch ya later22:02
b1airosounds good!22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:02
openstackMeeting ended Tue Mar 19 22:02:39 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
*** jtopjian has quit IRC22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-03-19-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-03-19-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-03-19-21.00.log.html22:02
*** oneswig has quit IRC22:03
*** iyamahat_ has quit IRC22:04
*** iyamahat__ has quit IRC22:04
*** iyamahat__ has joined #openstack-meeting22:04
*** pcaruana has quit IRC22:08
*** jamesmcarthur has quit IRC22:08
*** Lucas_Gray has quit IRC22:12
*** senrique__ has quit IRC22:13
*** yamahata__ has joined #openstack-meeting22:13
*** isq_ has quit IRC22:14
*** rcernin has joined #openstack-meeting22:16
*** ivy has quit IRC22:21
*** rbudden has quit IRC22:27
*** diablo_rojo has joined #openstack-meeting22:30
*** jamesmcarthur has joined #openstack-meeting22:30
*** slaweq has quit IRC22:32
*** raildo has quit IRC22:35
*** igordc has joined #openstack-meeting22:42
*** jamesmcarthur has quit IRC22:45
*** jamesmcarthur has joined #openstack-meeting22:46
*** ttsiouts has quit IRC22:51
*** jamesmcarthur has quit IRC22:52
*** priteau has quit IRC22:54
*** brbowen has joined #openstack-meeting22:59
*** simon-AS559 has quit IRC23:00
*** janders has quit IRC23:00
*** iyamahat__ has quit IRC23:04
*** iyamahat__ has joined #openstack-meeting23:04
*** mriedem is now known as mriedem_away23:07
*** iyamahat__ has quit IRC23:10
*** iyamahat has joined #openstack-meeting23:11
*** iyamahat_ has joined #openstack-meeting23:14
*** jamesmcarthur has joined #openstack-meeting23:14
*** yaawang has quit IRC23:17
*** iyamahat has quit IRC23:17
*** yaawang has joined #openstack-meeting23:18
*** carlos_silva has quit IRC23:24
*** hongbin has quit IRC23:25
*** jamesmcarthur has quit IRC23:30
*** mattw4 has quit IRC23:38
*** diablo_rojo has quit IRC23:46
*** jamesmcarthur has joined #openstack-meeting23:51
*** diablo_rojo has joined #openstack-meeting23:56

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