Monday, 2017-06-05

*** netapp has quit IRC00:01
*** netapp_ has joined #openstack-meeting-alt00:02
*** netapp_ is now known as netapp00:03
*** dimtruck is now known as zz_dimtruck00:14
*** zz_dimtruck is now known as dimtruck00:14
*** gouthamr has quit IRC00:21
*** yamamoto has joined #openstack-meeting-alt00:23
*** yamamoto has quit IRC00:30
*** markvoelker has quit IRC00:31
*** tovin07_ has joined #openstack-meeting-alt00:35
*** trungnv has quit IRC00:39
*** yamamoto has joined #openstack-meeting-alt00:43
*** julim has joined #openstack-meeting-alt00:46
*** trungnv has joined #openstack-meeting-alt00:46
*** mickeys has joined #openstack-meeting-alt00:52
*** kumarmn has quit IRC00:53
*** mickeys has quit IRC00:57
*** gcb has joined #openstack-meeting-alt01:19
*** fzdarsky_ has joined #openstack-meeting-alt01:33
*** mickeys has joined #openstack-meeting-alt01:33
*** zhurong has joined #openstack-meeting-alt01:33
*** fzdarsky__ has quit IRC01:35
*** kumarmn has joined #openstack-meeting-alt01:36
*** zhurong has quit IRC01:44
*** baoli has joined #openstack-meeting-alt01:46
*** hiro-kobayashi has joined #openstack-meeting-alt01:48
*** funzo has joined #openstack-meeting-alt01:48
*** dmitryme has quit IRC01:50
*** dmitryme has joined #openstack-meeting-alt01:51
*** gongysh has joined #openstack-meeting-alt01:52
*** funzo has quit IRC01:53
*** tovin07_ has quit IRC01:57
*** cinerama` has quit IRC02:02
*** neil__ has quit IRC02:03
*** adrian_otto has joined #openstack-meeting-alt02:04
*** tovin07_ has joined #openstack-meeting-alt02:05
*** cinerama has joined #openstack-meeting-alt02:06
*** cloudrancher has quit IRC02:10
*** cloudrancher has joined #openstack-meeting-alt02:11
*** baoli has quit IRC02:20
*** adrian_otto has quit IRC02:22
*** markvoelker has joined #openstack-meeting-alt02:28
*** baoli has joined #openstack-meeting-alt02:28
*** zhurong has joined #openstack-meeting-alt02:32
*** mickeys has quit IRC02:33
*** kumarmn has quit IRC02:33
*** kumarmn has joined #openstack-meeting-alt02:34
*** baoli has quit IRC02:40
*** kumarmn has quit IRC02:58
*** markvoelker has quit IRC03:02
*** julim has quit IRC03:09
*** kumarmn has joined #openstack-meeting-alt03:17
*** gouthamr has joined #openstack-meeting-alt03:19
*** Yangyapeng has joined #openstack-meeting-alt03:24
*** dimtruck is now known as zz_dimtruck03:31
*** kumarmn has quit IRC03:37
*** julim has joined #openstack-meeting-alt03:39
*** julim has quit IRC03:39
*** reedip_ has joined #openstack-meeting-alt03:54
*** markvoelker has joined #openstack-meeting-alt03:58
*** reedip_ has quit IRC04:07
*** sshnaidm is now known as sshnaidm|off04:09
*** jamesbenson has joined #openstack-meeting-alt04:09
*** gouthamr has quit IRC04:12
*** markvoelker has quit IRC04:32
*** julim has joined #openstack-meeting-alt04:32
*** mickeys has joined #openstack-meeting-alt04:35
*** julim has quit IRC04:36
*** sridharg has joined #openstack-meeting-alt04:39
*** tuanluong has joined #openstack-meeting-alt04:39
*** mickeys has quit IRC04:39
*** trinaths has joined #openstack-meeting-alt04:49
*** janki has joined #openstack-meeting-alt04:49
*** mickeys has joined #openstack-meeting-alt04:57
*** noslzzp has joined #openstack-meeting-alt05:06
*** salv-orlando has joined #openstack-meeting-alt05:08
*** beekneemech has quit IRC05:11
*** MarkBaker has joined #openstack-meeting-alt05:16
*** noslzzp has quit IRC05:17
*** dsariel has joined #openstack-meeting-alt05:27
*** yamamoto has quit IRC05:28
*** jamesbenson has quit IRC05:39
*** anilvenkata has joined #openstack-meeting-alt05:40
*** rwsu has joined #openstack-meeting-alt05:45
*** tobberydberg has joined #openstack-meeting-alt05:47
*** jamesbenson has joined #openstack-meeting-alt05:49
*** pgadiya has joined #openstack-meeting-alt05:49
*** pgadiya has quit IRC05:49
*** funzo has joined #openstack-meeting-alt05:50
*** funzo has quit IRC05:54
*** jamesbenson has quit IRC05:54
*** pbourke has quit IRC05:55
*** pbourke has joined #openstack-meeting-alt05:55
*** brault has joined #openstack-meeting-alt06:04
*** salv-orlando has quit IRC06:05
*** mickeys has quit IRC06:05
*** chhavi has joined #openstack-meeting-alt06:08
*** brault has quit IRC06:08
*** yamamoto has joined #openstack-meeting-alt06:13
*** jamesbenson has joined #openstack-meeting-alt06:15
*** mjura has joined #openstack-meeting-alt06:18
*** oidgar has joined #openstack-meeting-alt06:19
*** jamesbenson has quit IRC06:20
*** MarkBaker has quit IRC06:25
*** markvoelker has joined #openstack-meeting-alt06:28
*** rcernin has joined #openstack-meeting-alt06:29
*** jprovazn has joined #openstack-meeting-alt06:35
*** kobis has joined #openstack-meeting-alt06:35
*** ltomasbo|away is now known as ltomasbo06:36
*** brault has joined #openstack-meeting-alt06:37
*** chhavi has quit IRC06:38
*** hiro-kobayashi has quit IRC06:44
*** jchhatbar has joined #openstack-meeting-alt06:50
*** anilvenkata has quit IRC06:50
*** dsariel has quit IRC06:50
*** janki has quit IRC06:50
*** tuanluong has quit IRC06:50
*** cloudrancher has quit IRC06:50
*** cinerama has quit IRC06:50
*** trungnv has quit IRC06:50
*** SpamapS has quit IRC06:50
*** fdegir has quit IRC06:50
*** zaro has quit IRC06:50
*** jaranovich_ has quit IRC06:50
*** carl_baldwin has quit IRC06:50
*** Lokesh_Jain_ has quit IRC06:50
*** panda|travel has quit IRC06:50
*** amit213 has quit IRC06:50
*** alex_didenko has quit IRC06:50
*** raddaoui has quit IRC06:50
*** raddaoui_____ has quit IRC06:50
*** kong has quit IRC06:50
*** hogepodge has quit IRC06:50
*** sballe_ has quit IRC06:50
*** uli-k has quit IRC06:50
*** pasquier-s has quit IRC06:50
*** ameade has quit IRC06:50
*** johnsom has quit IRC06:50
*** ChrisPriceAB has quit IRC06:50
*** CaptTofu__ has quit IRC06:50
*** xgerman has quit IRC06:50
*** dsariel_ has joined #openstack-meeting-alt06:50
*** cinerama` has joined #openstack-meeting-alt06:50
*** raddaoui______ has joined #openstack-meeting-alt06:50
*** ChrisPriceAB_ has joined #openstack-meeting-alt06:50
*** xgerman_ has joined #openstack-meeting-alt06:50
*** anilvenkata has joined #openstack-meeting-alt06:50
*** trungnv has joined #openstack-meeting-alt06:50
*** CaptTofu___ has joined #openstack-meeting-alt06:50
*** panda|travel has joined #openstack-meeting-alt06:50
*** carl_baldwin has joined #openstack-meeting-alt06:50
*** tuanluong has joined #openstack-meeting-alt06:50
*** pasquier-s_ has joined #openstack-meeting-alt06:50
*** jaranovich_ has joined #openstack-meeting-alt06:50
*** kong has joined #openstack-meeting-alt06:51
*** zaro_ has joined #openstack-meeting-alt06:51
*** Lokesh_Jain_ has joined #openstack-meeting-alt06:51
*** raddaoui has joined #openstack-meeting-alt06:51
*** sballe_ has joined #openstack-meeting-alt06:51
*** alex_didenko has joined #openstack-meeting-alt06:51
*** MapspaM has joined #openstack-meeting-alt06:51
*** hogepodge has joined #openstack-meeting-alt06:51
*** ameade has joined #openstack-meeting-alt06:51
*** johnsom has joined #openstack-meeting-alt06:51
*** amit213 has joined #openstack-meeting-alt06:51
*** fdegir has joined #openstack-meeting-alt06:51
*** uli-k has joined #openstack-meeting-alt06:51
*** cloudrancher has joined #openstack-meeting-alt06:51
*** loquacities has quit IRC06:52
*** loquacities has joined #openstack-meeting-alt06:55
*** skramaja has joined #openstack-meeting-alt07:01
*** markvoelker has quit IRC07:02
*** salv-orlando has joined #openstack-meeting-alt07:04
*** mickeys has joined #openstack-meeting-alt07:06
*** mickeys has quit IRC07:11
*** brault has quit IRC07:11
*** dizquierdo has joined #openstack-meeting-alt07:12
*** fzdarsky_ is now known as fzdarsky|afk07:17
*** ccamacho has joined #openstack-meeting-alt07:18
*** mickeys has joined #openstack-meeting-alt07:19
*** mickeys has quit IRC07:21
*** shuyingya has joined #openstack-meeting-alt07:26
*** salv-orl_ has joined #openstack-meeting-alt07:28
*** brault has joined #openstack-meeting-alt07:30
*** brault has quit IRC07:31
*** salv-orlando has quit IRC07:31
*** brault has joined #openstack-meeting-alt07:31
*** zhurong has quit IRC07:31
*** bogdando has joined #openstack-meeting-alt07:32
*** kzaitsev_ws has joined #openstack-meeting-alt07:32
*** brault_ has joined #openstack-meeting-alt07:33
*** brault has quit IRC07:33
*** jpena|off is now known as jpena07:36
*** dizquierdo has quit IRC07:39
*** zhurong has joined #openstack-meeting-alt07:40
*** markvoelker has joined #openstack-meeting-alt07:59
*** rossella_s has joined #openstack-meeting-alt08:06
*** salv-orl_ has quit IRC08:07
*** neil__ has joined #openstack-meeting-alt08:09
*** salv-orlando has joined #openstack-meeting-alt08:10
*** rossella_s has quit IRC08:14
*** shuyingy_ has joined #openstack-meeting-alt08:17
*** zhurong has quit IRC08:20
*** shuyingya has quit IRC08:21
*** chhavi has joined #openstack-meeting-alt08:22
*** mickeys has joined #openstack-meeting-alt08:22
*** mickeys has quit IRC08:28
*** panda|travel is now known as panda08:30
*** rossella_s has joined #openstack-meeting-alt08:30
*** panda is now known as Guest9854608:30
*** karthiks has joined #openstack-meeting-alt08:31
*** markvoelker has quit IRC08:32
*** chhavi_ has joined #openstack-meeting-alt08:32
*** chhavi has quit IRC08:33
*** Yangyapeng has quit IRC08:47
*** zhurong has joined #openstack-meeting-alt08:50
*** salv-orlando has quit IRC08:50
*** salv-orlando has joined #openstack-meeting-alt08:51
*** itamaro has quit IRC09:08
*** anilvenkata has quit IRC09:09
*** sambetts|afk is now known as sambetts09:13
*** salv-orlando has quit IRC09:13
*** salv-orlando has joined #openstack-meeting-alt09:14
*** dizquierdo has joined #openstack-meeting-alt09:23
*** mickeys has joined #openstack-meeting-alt09:24
*** oidgar has quit IRC09:24
*** mickeys has quit IRC09:29
*** Guest98546 is now known as panda09:29
*** markvoelker has joined #openstack-meeting-alt09:29
*** rossella_s has quit IRC09:30
*** jamesbenson has joined #openstack-meeting-alt09:31
*** jamesbenson has quit IRC09:35
*** dalgaaf has quit IRC09:35
*** dalgaaf has joined #openstack-meeting-alt09:37
*** rossella_s has joined #openstack-meeting-alt09:46
*** rossella_s has quit IRC09:54
*** zhurong has quit IRC09:59
*** anilvenkata has joined #openstack-meeting-alt10:00
*** tovin07_ has quit IRC10:00
*** iyamahat has joined #openstack-meeting-alt10:01
*** markvoelker has quit IRC10:02
*** iyamahat has quit IRC10:07
*** zhurong has joined #openstack-meeting-alt10:13
*** jchhatbar is now known as janki10:13
*** yamamoto has quit IRC10:17
*** jtomasek is now known as jtomasek|brb10:23
*** mickeys has joined #openstack-meeting-alt10:25
*** mickeys has quit IRC10:29
*** sulo_ is now known as sulo10:38
*** dizquierdo has quit IRC10:42
*** anilvenkata has quit IRC10:43
*** dsariel_ has quit IRC10:55
*** gongysh has quit IRC10:58
*** jkilpatr has joined #openstack-meeting-alt10:58
*** markvoelker has joined #openstack-meeting-alt11:00
*** sdague has joined #openstack-meeting-alt11:05
*** alexchadin has joined #openstack-meeting-alt11:09
*** shuyingy_ has quit IRC11:12
*** eliqiao has quit IRC11:12
*** shuyingya has joined #openstack-meeting-alt11:12
*** eliqiao has joined #openstack-meeting-alt11:15
*** daidv_ has joined #openstack-meeting-alt11:18
*** anilvenkata has joined #openstack-meeting-alt11:22
*** mickeys has joined #openstack-meeting-alt11:26
*** yamamoto has joined #openstack-meeting-alt11:27
*** dsariel_ has joined #openstack-meeting-alt11:28
*** mickeys has quit IRC11:30
*** markvoelker has quit IRC11:33
*** chhavi_ has quit IRC11:34
*** caowei has joined #openstack-meeting-alt11:34
*** salv-orlando has quit IRC11:35
*** shuyingy_ has joined #openstack-meeting-alt11:35
*** salv-orlando has joined #openstack-meeting-alt11:35
*** shuyingya has quit IRC11:38
*** salv-orlando has quit IRC11:39
*** shuyingy_ has quit IRC11:45
*** shuyingya has joined #openstack-meeting-alt11:46
*** tuanluong has quit IRC11:56
*** numans_ has quit IRC11:57
*** trinaths has quit IRC12:00
*** trinaths has joined #openstack-meeting-alt12:03
*** links has joined #openstack-meeting-alt12:04
*** zhurong has quit IRC12:04
*** trinaths has quit IRC12:07
*** julim has joined #openstack-meeting-alt12:08
*** rossella_s has joined #openstack-meeting-alt12:13
*** markvoelker has joined #openstack-meeting-alt12:16
*** julim has quit IRC12:18
*** rossella_s has quit IRC12:20
*** rossella_s has joined #openstack-meeting-alt12:20
*** shuyingya has quit IRC12:24
*** mickeys has joined #openstack-meeting-alt12:27
*** jtomasek|brb is now known as jtomasek12:28
*** tellesnobrega has joined #openstack-meeting-alt12:29
*** mickeys has quit IRC12:31
*** trinaths has joined #openstack-meeting-alt12:32
*** jpena is now known as jpena|lunch12:38
*** salv-orlando has joined #openstack-meeting-alt12:40
*** ansmith has joined #openstack-meeting-alt12:42
*** cleong has joined #openstack-meeting-alt12:44
*** caowei has quit IRC12:44
*** Guest58049 is now known as beagles12:45
*** dave-mccowan has joined #openstack-meeting-alt12:48
*** dizquierdo has joined #openstack-meeting-alt12:48
*** dustins has joined #openstack-meeting-alt12:51
*** jaypipes has joined #openstack-meeting-alt12:52
*** tellesnobrega has quit IRC12:52
*** shuyingya has joined #openstack-meeting-alt12:54
*** cknight has joined #openstack-meeting-alt12:56
*** chhavi_ has joined #openstack-meeting-alt12:57
*** shuyingya has quit IRC13:00
*** shuyingya has joined #openstack-meeting-alt13:00
*** fnaval has joined #openstack-meeting-alt13:02
*** alexchadin has quit IRC13:06
*** alexchadin has joined #openstack-meeting-alt13:06
*** alexchadin has quit IRC13:07
*** alexchadin has joined #openstack-meeting-alt13:07
*** alexchadin has quit IRC13:07
*** funzo has joined #openstack-meeting-alt13:08
*** alexchadin has joined #openstack-meeting-alt13:08
*** alexchadin has quit IRC13:08
*** alexchadin has joined #openstack-meeting-alt13:09
*** tellesnobrega has joined #openstack-meeting-alt13:09
*** jprovazn has quit IRC13:10
*** funzo has quit IRC13:12
*** baoli has joined #openstack-meeting-alt13:13
*** alexchadin has quit IRC13:13
*** brault_ has quit IRC13:16
*** lucasxu has joined #openstack-meeting-alt13:17
*** kumarmn has joined #openstack-meeting-alt13:17
*** cloudrancher has quit IRC13:21
*** cloudrancher has joined #openstack-meeting-alt13:22
*** salv-orlando has quit IRC13:23
*** warpc has quit IRC13:24
*** skramaja has quit IRC13:26
*** janki has quit IRC13:27
*** mickeys has joined #openstack-meeting-alt13:27
*** kozhukalov has quit IRC13:28
*** aroma has quit IRC13:28
*** rpodolyaka has quit IRC13:29
*** ashtokolov has quit IRC13:29
*** dizquierdo has quit IRC13:30
*** aglarendil has quit IRC13:30
*** mickeys has quit IRC13:32
*** jcoufal has joined #openstack-meeting-alt13:32
*** gouthamr has joined #openstack-meeting-alt13:33
*** brault has joined #openstack-meeting-alt13:36
*** jpena|lunch is now known as jpena13:37
*** funzo has joined #openstack-meeting-alt13:37
*** baoli has quit IRC13:38
*** baoli has joined #openstack-meeting-alt13:38
*** jprovazn has joined #openstack-meeting-alt13:41
*** brault has quit IRC13:43
*** zhurong has joined #openstack-meeting-alt13:46
*** namnh has joined #openstack-meeting-alt13:47
*** dtrainor has joined #openstack-meeting-alt13:48
*** felipemonteiro has joined #openstack-meeting-alt13:50
*** cdent has joined #openstack-meeting-alt13:51
*** felipemonteiro_ has joined #openstack-meeting-alt13:53
*** julim has joined #openstack-meeting-alt13:55
*** felipemonteiro has quit IRC13:56
*** zz_dimtruck is now known as dimtruck13:58
edleafe#startmeeting nova_scheduler14:00
*** lei-zh has joined #openstack-meeting-alt14:00
openstackMeeting started Mon Jun  5 14:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is edleafe. 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: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
edleafeWho's here today?14:00
*** bnemec has joined #openstack-meeting-alt14:00
alex_xuo/14:00
lei-zho/14:00
jaypipeso/14:01
cdento/14:01
*** diga has joined #openstack-meeting-alt14:01
*** shuyingya has quit IRC14:02
edleafeLooks like there is room enough for everyone to stretch their legs!14:02
*** shuyingya has joined #openstack-meeting-alt14:02
jaypipesindeed14:02
edleafe#topic Specs and Reviews14:02
*** openstack changes topic to "Specs and Reviews (Meeting topic: nova_scheduler)"14:02
edleafe** Claims in the Scheduler/Conductor14:02
edleafe*** #link Claims in the Scheduler/Conductor series: https://review.openstack.org/#/c/465171/14:02
edleafecrap14:02
edleafecopy paste fail!14:03
edleafeClaims in the Scheduler/Conductor14:03
edleafe#link Claims in the Scheduler/Conductor series: https://review.openstack.org/#/c/465171/14:03
*** dizquierdo has joined #openstack-meeting-alt14:03
edleafeThis seems to be moving forward14:03
edleafeAre there any overriding concerns about the direction?14:04
jaypipesnot from me14:04
cdentnor me14:04
edleafeJay has a +2 on the first in that series, so if we can get another core to agree..14:04
jaypipesbauzas: you in today?14:05
edleafeIAC, please review the next few in that series. I have cycles to update as needed14:05
edleafeMoving on...14:05
edleafeNested Resource Providers14:05
edleafe#link Nested RPs: https://review.openstack.org/#/c/41592014:05
dansmithedleafe: uber holiday today in .ey14:05
dansmith*eu14:05
digao/14:06
edleafedansmith: no ride sharing?14:06
dansmithuuuuuuber holiday14:06
jaypipesedleafe: been getting some good reviews from efried on that series.14:06
dansmithbig holiday14:06
* cdent is no longer in the eu :(14:06
jaypipesedleafe: plan to comment on the patches please.14:06
edleafejaypipes: sure thing - have them open in tabs with the latest updates14:07
*** shuyingya has quit IRC14:07
jaypipesedleafe: I also have a question on scheduler claims and shared resource providers to discuss if we time today14:07
edleafeI'm free after this meeting14:08
edleafeWe can either do it during Opens, or anytime after14:08
jaypipeskk14:08
alex_xujaypipes: a question, will change the API 'GET /resource_providers?resources=...' in the future for nested resource providers?14:08
jaypipesalex_xu: great question, and the answer is related to what I want to discuss about shared resource providers :)14:09
jaypipesalex_xu: so let's discuss that together14:09
alex_xujaypipes: ok14:09
edleafeLet's do it in Opens then. I don't want to keep alex_xu up too late :)14:09
jaypipesthere's another patch series: https://review.openstack.org/#/q/topic:cd/placement-api-ref+status:open14:09
alex_xuedleafe: thanks :)14:09
jaypipesfor avolkov's api-refs14:09
*** alexchadin has joined #openstack-meeting-alt14:10
edleafejaypipes: stop stealing my thunder!14:10
edleafe:)14:10
jaypipessorry!14:10
edleafethat's later in the list14:10
jaypipesk14:11
edleafeWell, since you brought it up...14:11
edleafePlacement API ref docs14:11
edleafe#link Placement API ref docs: https://review.openstack.org/#/q/topic:cd/placement-api-ref+status:open14:11
jaypipeshehe14:11
* edleafe tries to run a tight meeting14:11
edleafeAnything to add about that series?14:11
cdentonly that we'll need to start thinking about the publishing job14:12
cdentright now the job makes drafts14:12
cdentbut last I talked to andrey it wasn't ready to publish14:12
*** shuyingya has joined #openstack-meeting-alt14:13
edleafethat's always the fun part, no?14:14
jaypipescdent: ++14:14
*** alexchadin has quit IRC14:14
edleafeMoving on14:14
edleafeAdd project_id and user_id to placement DB14:14
edleafe#link project_id and user_id to placement DB: https://review.openstack.org/#/c/470645/14:14
jaypipeshold up on that one.14:15
jaypipes:)14:15
edleafeStill kind of WIPpy14:15
jaypipesI'm just fixing locally a postgreSQL oddity.14:15
jaypipesfinishing running tests now and should be pushed shortly.14:15
edleafecool14:15
jaypipesspent most of the weekend working on that14:15
jaypipesI wanted to normalize the consumers table properly.14:15
edleafeI spent most of my weekend not working :)14:16
jaypipesinstead of endlessly repeating VARCHAR(255) columns everywhere14:16
* edleafe finds it funny to see jaypipes and "normal" in the same sentence14:16
jaypipesedleafe: normalized != normal :)14:17
edleafeheh14:17
edleafeNext up is: Delete all inventory14:17
edleafe#link Delete all inventory: https://review.openstack.org/#/c/460147/14:17
*** persia has quit IRC14:17
cdentdid we know that mr date has the same initials as me? I'm sure that means something..14:17
edleafeThat's getting pretty close. We should be able to push that through this week14:17
jaypipesI did indeed know that.14:18
jaypipesI remember speaking to him around 2006 or so.14:18
jaypipeshe wanted $9000 to come do a keynote for the MySQL conference. I politely declined.14:18
cdenthawt14:18
*** alexchadin has joined #openstack-meeting-alt14:18
jaypipesnow... if his name was CJ Timestamp, I might have considered.14:19
edleafe<groan>14:19
jaypipesyes, I have turned into my father.14:19
jaypipesok, meeting guru, what's up next?14:19
edleafeSo we have a leaf, a dent, and some pipes making fun of a date14:20
jaypipesindeed.14:20
jaypipesIndy, bad dates.14:20
edleafeSync os-traits to DB14:20
edleafe#link Sync os-traits: https://review.openstack.org/#/c/469578/14:20
edleafeThis is cdent's patch14:20
*** trinaths has left #openstack-meeting-alt14:20
jaypipescdent: can you fix up that thing edleafe pointed to on ^^14:20
jaypipescdent: help a brother out? :)14:21
cdenti thought that was already done, and now it was a thing that alex pointed out?14:21
edleafejaypipes: you mean the thing that alex_xu pointed to?14:21
edleafejinx14:21
*** hongbin has joined #openstack-meeting-alt14:21
*** persia has joined #openstack-meeting-alt14:21
jaypipesdoh, yeah, sorry, was alex_xu :)14:22
cdentif he's correct, then sure, I can get that after this meeting14:22
cdentI was waiting for confirmation from folk14:22
edleafecdent: ok, I can take a look too14:23
edleafeLet14:23
alex_xucdent: I did a test in local :)14:23
edleafeLet's move on14:23
cdentletrec14:23
* edleafe can't type an apostrophe14:23
edleafe#topic Bugs14:24
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:24
edleafe#link Placement bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement14:24
cdentI made a few last week and then fixed most of them14:24
edleafeA few new ones14:24
edleafeah, good14:25
edleafeThen we're up to:14:25
cdentwas gonna do this one asap: https://bugs.launchpad.net/nova/+bug/169535614:25
openstackLaunchpad bug 1695356 in OpenStack Compute (nova) "placement allocations handler module does not use util.extract_json" [Low,Triaged]14:25
edleafe#topic Open discussion14:25
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:25
* cdent sits comfortable14:25
jaypipescdent: yes, alex_xu is correct. I'd forgotten oslo.db wraps that exception.14:26
edleafesorry to step on your bug, cdent14:26
* edleafe picture bug guts on my show14:26
*** shuyingya has quit IRC14:26
edleafeshoe, even14:26
jaypipesOK, so we ready to discuss shared and nested providers in the claims?14:26
cdentyes14:26
edleafego for it!14:26
jaypipesawesome.14:26
jaypipesalright, so here is the way I've been thinking about it.14:26
*** shuyingya has joined #openstack-meeting-alt14:26
jaypipesplease come along this journey with me and tell me if I'm smoking some crazypants.14:27
*** anilvenkata has quit IRC14:27
* cdent gets bong14:27
jaypipesalright, so the scheduler, after edleafe's placement claims series is merged, will be doing the POST /allocations, passing in a consumer ID (the instance UUID) and the resource provider UUID it selected from the list of providers returned from placement.14:28
edleafeso far so good...14:28
*** mickeys has joined #openstack-meeting-alt14:28
jaypipesNow, if the resource provider selected by the scheduler uses a shared provider for one of the requested resources (say, DISK_GB), then we need to allocate against that particular resource provider (the shared one) and obviously not the compute node resource provider.14:29
* cdent nods14:29
* edleafe hopes jaypipes is going to suggest that that logic go in the placement code14:29
* cdent cdent hopes not :)14:30
jaypipesSo, I'm thinking that the response from POST /allocations should include a list of resource providers that were consumed from, *including* the shared provider that the placement engine consumed from.14:30
cdentoops14:30
dansmithhope not14:30
cdentargh14:30
jaypipesThe alternative is that placement change the response for GET /resource_providers that it returns to the scheduler to include the shared resource providers that the scheduler should include in its POST /allocations call.14:31
* dansmith is confused14:31
edleafewhy is it important for POST /allocations to return anything?14:31
cdentI thought the point of the aggregates cache that the report client (or was it resource tracker) was going to maintain was going to be used to know who is being shared with14:31
cdentand thus we could write explicit allocations14:32
jaypipesedleafe: good point. technically, it's not.14:32
dansmithjaypipes: scheduler picks the things it wants to claim against, and tries in its POST.. either it works or doesn't.. no decision-making on the placement side right?14:32
edleafedansmith: it just gets back *root* providers14:32
edleafee.g., compute nodes14:32
dansmithoh the wrinkle is nested here?14:32
*** mickeys has quit IRC14:32
edleafeyes14:32
cdentalso shared14:32
cdent?14:32
jaypipesdansmith: no, not nested, though that will be a similar wrinkle.14:32
dansmithjaypipes: okay, but it sounds like you're describing some non-deterministic behavior on the placement side,14:33
edleafeok, good point14:33
dansmithif it matters what the post response is14:33
jaypipescdent: the idea of the aggregate cache in the report client was indeed to know what things were shared with the compute node and be able to claim against those shared providers.14:33
edleafedansmith: it shouldn't matter. POST should just return 204 if successful14:34
*** baoli has quit IRC14:34
dansmithedleafe: right, that's my thought14:34
*** baoli has joined #openstack-meeting-alt14:35
edleafedansmith: allocating disk resources on a compute node that uses shared storage should be transparent to scheduler14:35
jaypipescdent: the thing is, we need some way of telling the scheduler ("hey, this resource provider doesn't actually have room for X resource class. for that, you need to add a shared provider to the allocation")14:35
dansmithwhich is why I'm wondering what jaypipes' point/question is about returning the providers that got consumed from14:35
*** baoli has quit IRC14:35
edleafejaypipes: wait - that's not true14:35
jaypipesedleafe: how so?14:36
edleafejaypipes: scheduler asks placement for RPs that can satisfy a set of resource requirements14:36
edleafeplacement returns that list14:36
cdentI disagree with this statement: "allocating disk resources on a compute node that uses shared storage should be transparent to scheduler"14:36
*** bbzhao has quit IRC14:36
jaypipesno, it returns the list of providers that can satisfy that request OR are associated with a provider that shares.14:36
edleafewhen scheduler then tries to claim those resources against a RP, placement shouldn't reply "Oh, it can't satisfy that"14:36
dansmithright, it's not transparent to the scheduler14:37
*** baoli has joined #openstack-meeting-alt14:37
*** alexchadin has quit IRC14:37
dansmithscheduler is the thing that knows to claim against the shared provider in the same aggregate as the compute14:37
*** bzhao has joined #openstack-meeting-alt14:37
*** alexchadin has joined #openstack-meeting-alt14:37
dansmith(if we're doing it in scheduler vs. conductor)14:37
edleafedansmith: placement already determined that the compute node had shared storage in the same agg14:37
jaypipesdansmith: technically, no, the placement API is the thing that knows that stuff.14:37
dansmithjaypipes: you mean because it returned the shared provider in the initial GET right?14:38
jaypipesdansmith: no, we don't (currently) return shared providers. we only return providers that are shared *with*.14:38
edleafeThink of it this way: scheduler asks for resources. Placement has to have the logic to handle shared resources.14:38
dansmithum.14:39
jaypipesdansmith: now, I could change the return response of GET /resource_providers (my question above) if the scheduler does need to know that ionformation.14:39
edleafeScheduler then claims resources. Placement should have the logic to handle shared resources there, too14:39
edleafejaypipes: god no!14:39
jaypipesedleafe: having the placement API do the claim against the shared provider is what I think is the cleanest solution.14:39
cdenti'm not sure if I agree or disagree, edleafe, but why so strenuous?14:40
dansmithjaypipes: that is entirely contrary to what I've been thinking the plan is this whole time14:40
edleafeBecause it's a placement detail14:40
jaypipesperhaps it's worth doing a hangout on this. it's a complex topic and IRC threads are a pain for this..14:40
* dansmith is getting rather frustrated with the lack of actual vs. apparent consensuson all this14:40
edleafescheduler, or anything else talking to placement, shouldn't have to incorporate that nesting/shared logic14:40
jaypipesdansmith: please be patient :) we never discussed this in the specs or at summits.14:41
dansmithhuh? then I must be missing something even bigger14:41
edleafecdent: let me turn the question around14:41
jaypipeswould everyone be ok with a hangout?14:41
edleafecdent: why not have the scheduler determine shared resources when getting a list of hosts?14:42
cdenti can listen, but will struggle to talk14:42
* alex_xu is ok14:42
* edleafe would need a few minutes to set up14:42
cdentbut I'd prefer to listen at this stage anyway, so is cool14:42
* alex_xu will struggle to listen14:42
jaypipesok, we can continue on IRC then I suppose.14:42
jaypipesdansmith: so, to be clear, the GET /resource_providers currently returns resource providers that either have the inventory themselves or are associated with a provider that shares some resources with it.14:43
jaypipesdansmith: it does not currently return the sharing providers themselves.14:43
*** hrybacki is now known as hrybacki|afkish14:43
jaypipesdansmith: only the shared-with providers.14:43
edleafethe logic to determine the sharing is in placement14:43
dansmithjaypipes: okay, that's not what I was thinking we were doing14:44
dansmithjaypipes: because that precludes scheduler having filters for complex choosing of which shared thing to use14:44
jaypipesdansmith: did you think we were returning the sharing providers in addition to the shared-with providers?14:44
dansmithyeah14:44
dansmithI think it also maybe prevents scheduler from being able to say "okay I got three compute nodes, one with local disk, two with shared, and the user prefers not shared, so choose cn1"14:45
jaypipesdansmith: we have the infrastructure in place (via the provider_aggregate_map in the scheduler reporting client) to have the scheduler do some additional filtering logic. If that's what we want ti di,14:45
jaypipesto do...14:45
jaypipesdansmith: ok, fair point. would you want me to change the response of GET /resource_providers to indicate the shared-with relationship? or do you think it's appropriate for the scheduler to use the provider_aggregate_map stuff and "figure that out" for itself?14:47
dansmiththat seems like a lot of stabbing in the dark by the scheduler14:48
jaypipesdansmith: a similar question is going to need answered for nested providers. Do we modify the response of GET /resource_providers to indicate the tree relationship between providers? or do we rely on the reporting client to keep that tree information in memory?14:48
cdentGET /rps quickly gets very confused and confusing if we start trying to represent (and potentially optionally) shared and nested in the response14:48
dansmithI dunno, I thought a major tenant here was that the scheduler was picking "which one" and placement was keeping track of "how much"14:49
cdenton the other hand, the lack of explicitness is ... disarming14:49
jaypipeswell, this is complex stuff. no way around that.14:49
edleafedansmith: if the scheduler has a compute node, can't it tell if it is part of a shared resource agg?14:49
dansmithedleafe: it can by stabbing in the dark yes14:50
jaypipesedleafe: it can, but it's a lot more work for the scheduler (reporting client) to do that than it is for the placement API.14:50
*** namnh has quit IRC14:50
*** namnh has joined #openstack-meeting-alt14:50
edleafeit seems that a better request for GET RPs would be the solution14:51
edleafelike specifying a trait for shared/unshared14:51
* dansmith checks local fast food chains for openings14:51
jaypipeslook, there's tradeoffs in simplicity/complexity in each of the approaches here. we need to probably choose the one that has the placement API returning the most useful information to the scheduler in a single response. or at least, that's my opinion...14:51
edleafeThe only way to deal with messy details is to localize them in one place, rather than try to make every part of the application have to understand that14:52
cdentreturning everything was my original opinion14:52
edleafeRP relationships are messy14:52
cdent(months ago)14:52
jaypipescdent: not helping.14:53
cdentjaypipes: ? I was agreeing with you14:53
edleafePassing details of the messiness around will lead to more crap code all over the place14:53
dansmiththese details seem completely material to scheduler's day job14:53
jaypipesedleafe: could you be explicit about what "details of the messiness" means to you?14:53
dansmithto me at least14:53
edleafejaypipes: sure14:54
*** hieulq_ has joined #openstack-meeting-alt14:54
edleafeThe relationship between RPs, whether with shared aggs or nested providers, is something we've struggled with to get to a halfway-decent representation inside placement14:54
edleafeNow we're thinkning about adding that same logic to the scheduler? And possibly also the conductor?14:55
*** lujinluo has joined #openstack-meeting-alt14:56
*** yamahata has joined #openstack-meeting-alt14:57
edleafe(BTW, 3 minutes left)14:57
*** julim has quit IRC14:57
jaypipesedleafe: what about adding a separate GET /<something> API endpoint that would return all the things that the scheduler needs to make a decision?14:57
jaypipesedleafe: instead of hacking further the GET /resource_providers endpoint?14:58
* jaypipes just throwing out ideas14:58
edleafejaypipes: well, that would certainly suck a whole lot less14:58
*** julim has joined #openstack-meeting-alt14:58
cdentdo you mean one that would represent the structure more that the current representaiton does?14:58
cdentthan14:58
jaypipescdent: yes14:58
edleafecdent: maybe like /GET servers vs. /GET servers?uuid-AAAA...14:59
jaypipescdent: and possibly including things like traits and inventory/usage inforamtion14:59
edleafelist vs. detail14:59
*** manjeets__ has joined #openstack-meeting-alt14:59
*** ihrachys has joined #openstack-meeting-alt14:59
dansmiththis would effectively cement novaisms into placement?14:59
edleafedansmith: why?15:00
manjeets__hello15:00
edleafeOh, wait, times up. Let's move this to -nova15:00
dansmithedleafe: servers?15:00
edleafe#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Jun  5 15:00:22 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-06-05-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-06-05-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-06-05-14.00.log.html15:00
*** cdent has left #openstack-meeting-alt15:01
ihrachys#startmeeting neutron_upgrades15:01
openstackMeeting started Mon Jun  5 15:01:23 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:01
openstackThe meeting name has been set to 'neutron_upgrades'15:01
ihrachyso/ everyone15:01
lujinluoo/15:01
manjeets__o/15:02
ihrachysok seems like we don't have any specific action items from the prev meeting15:02
*** shuyingy_ has joined #openstack-meeting-alt15:02
ihrachysso we can move straight into reviewing the list of OVO patches maybe15:02
ihrachys#topic OVO15:02
*** openstack changes topic to "OVO (Meeting topic: neutron_upgrades)"15:02
*** julim has quit IRC15:02
ihrachyshttps://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db15:02
*** felipemonteiro has joined #openstack-meeting-alt15:03
ihrachysfor the record, we landed router-l3-agent-binding: https://review.openstack.org/37707415:03
ihrachysalso update_objects API: https://review.openstack.org/45226615:03
ihrachys(^ which I think means tunnel endpoints patch can be revived)15:03
*** gyee has joined #openstack-meeting-alt15:04
manjeets__ihrachys: as you noticed gate was not so nice last week15:04
ihrachyswe aslo have security groups OVO adoption in the gate but failing over and over because of unrelated gate issues :https://review.openstack.org/28473815:04
ihrachysyeah, gate is pretty bad15:04
ihrachysI mostly work on getting it back to normal right now15:04
*** julim_ has joined #openstack-meeting-alt15:05
ihrachysok, now, starting from the top, lujinluo has two patches for router object: https://review.openstack.org/#/c/466237/ and https://review.openstack.org/#/c/307964/15:05
ihrachysI presume that those two are the only bits needed?15:06
*** shuyingya has quit IRC15:06
*** sshnaidm|off has quit IRC15:06
*** felipemonteiro_ has quit IRC15:07
ihrachysI see both having some issues passing the gate that seem legit15:07
lujinluoi have not checked why the eager loading patch failed yet. will check after the meeting. as for the router ovo creation patch, i have a local patch which is not finished yet15:07
ihrachysok let's wait for the new version. for the relationship, functional test failure seems related, but worth a (re)check to be sure.15:07
lujinluoyeah15:08
ihrachysok next we have network-dhcp-agent-binding: https://review.openstack.org/#/c/370452/15:08
ihrachysthis one has +2 from kevin, good15:08
ihrachysand -1 from lujinluo15:08
lujinluoyes, i pointed out we only need to make a slight change in test_base.py15:08
ihrachys-1 seems to be a small test issue, correct?15:09
manjeets__ihrachys: I just noticed i'll address lujinluo 's comments today15:09
lujinluoihrachys, yes, very small issue15:09
ihrachysmanjeets__, ++ I will have a look at it after the meeting to make sure we can get it in on the next PS15:09
manjeets__++15:09
*** julim_ has quit IRC15:09
*** tobberydberg has quit IRC15:10
ihrachysok next in the list is neutron-db-manage command for data migration: https://review.openstack.org/#/c/432494/15:10
ihrachysI see there is some progress there, like stevedore alias added15:11
ihrachysmanjeets__, do you know the path forward, or we need to have another look at the latest?15:11
manjeets__i've also added a functional test using existing framework15:11
*** bzhao has quit IRC15:12
*** felipemonteiro has quit IRC15:12
*** bzhao has joined #openstack-meeting-alt15:14
ihrachysmanjeets__, so do you need us to eyeball the latest?15:14
*** manjeets___ has joined #openstack-meeting-alt15:14
*** jamesbenson has joined #openstack-meeting-alt15:14
manjeets___sorry internet outage for a moment15:14
manjeets___functional test passed locally but is failing over gate, need to debug it locally again15:15
ihrachysmanjeets___, do you need us to eyeball the latest?15:15
manjeets___sure that will help15:15
manjeets___if something is wrong with the approach i followed15:15
*** zhurong has quit IRC15:15
*** manjeets__ has quit IRC15:16
*** sshnaidm has joined #openstack-meeting-alt15:16
ihrachysok next in line is https://review.openstack.org/#/c/304873/ (dvr mac address OVO)15:16
ihrachysit's on Tony, and I believe he is not available for the work15:16
ihrachyswe probably need to take it over15:16
ihrachysthoughts? anyone heard from Tony lately?15:17
lujinluono, i do not15:17
ihrachysok, the patch doesn't seem huge15:18
*** jamesbenson has quit IRC15:18
ihrachysanyone want to polish it?15:18
lujinluoi can try, but i cannot promise i can do it this week15:18
ihrachysok I will take it myself, shouldn't take a lot of time15:19
lujinluook15:19
*** bnemec has quit IRC15:19
*** manjeets___ has quit IRC15:20
ihrachysnext in the list is port binding: https://review.openstack.org/#/c/407868/15:20
ihrachysthis one is kinda important since we have port binding changes in the pipeline15:20
*** felipemonteiro has joined #openstack-meeting-alt15:20
ihrachyslujinluo, what's the status there? I see lots of red in gate.15:20
lujinluoyeah, somehow i have a failed UT again besides functional test failures. have not figured out why15:21
lujinluoi will priotirize this PS this week15:22
ihrachyscoool15:22
*** manjeetsb has joined #openstack-meeting-alt15:22
lujinluoalso, reviews would be aprreciated15:22
ihrachysok let me add it to my list15:22
manjeetsbSorry my home network is not good today15:22
lujinluoit seems we have manjeetsb back now15:23
manjeetsbJoined over phone now15:23
ihrachysmanjeetsb, ack15:23
manjeetsbA review on dbmanage command will help ihrachys15:23
ihrachysmanjeetsb, + on my list now15:24
*** bnemec has joined #openstack-meeting-alt15:24
manjeetsbCool thanks15:24
manjeetsbI'll checkout dvr ovo patch from Tony today15:24
ihrachysnext in queue are two qos related objects from Rodolfo: https://review.openstack.org/#/c/468406/ and https://review.openstack.org/#/c/468837/15:24
ihrachysboth seem green in gate and well isolated15:24
ihrachysmanjeetsb, I am taking it over, so no need.15:25
manjeetsbOk15:25
ihrachysfor qos, I will just put it in my list but it may take a while till I get there15:25
*** lei-zh has quit IRC15:25
*** jamesbenson has joined #openstack-meeting-alt15:26
*** lei-zh has joined #openstack-meeting-alt15:26
ihrachysnext in the list is port binding level OVO: https://review.openstack.org/#/c/382037/15:26
ihrachysit was on shashank who I believe is no longer with openstack?15:27
ihrachysmanjeetsb, you should prolly know15:27
ihrachysoh I see a respin on May 2415:27
manjeetsbHe switched job15:27
manjeetsbHe is no longer working on openstack now15:27
ihrachysok let's check in gerrit if he is going to complete it; if no response in a week, we can take it over then15:28
manjeetsbSure I'll ask him he is in same building as I am in15:28
ihrachyscool15:29
ihrachysI also posted a question on his plans in gerrit15:29
manjeetsbOhk15:29
ihrachys#action manjeetsb to clarify if Shashank is going to complete port binding level OVO patch15:29
*** tobberydberg has joined #openstack-meeting-alt15:29
*** jamesbenson has quit IRC15:30
ihrachysnext in line are ip allocation OVOs: https://review.openstack.org/396718 and https://review.openstack.org/39671115:30
ihrachysthose were originally from Victor but I see lujinluo took over15:30
lujinluoI respinned these two. Please help with the reviews ;)15:30
ihrachys+ will do, thanks for taking over15:30
*** janki has joined #openstack-meeting-alt15:30
ihrachysthey seem green, good progress15:30
ihrachysok next is LIKE filter support: https://review.openstack.org/#/c/419152/15:31
ihrachysit's on Tony15:31
ihrachyswe should take it over15:31
ihrachysI believe it's mostly small things left, like a test missing and such15:32
ihrachysanyone willing to take it over and prepare for merge?15:32
manjeetsbI'll review it today15:32
*** kobis has quit IRC15:33
ihrachysmanjeetsb, review or take over/respin?15:33
manjeetsbAnd see try respining if need really small changes15:33
ihrachysok, thanks15:33
ihrachys#action manjeetsb to have a look at LIKE support patch and respin15:33
*** jamesbenson has joined #openstack-meeting-alt15:33
*** tobberydberg has quit IRC15:34
ihrachysnext in line is Anindita's endpoints OVO: https://review.openstack.org/#/c/367810/15:34
ihrachysI think this was waiting for update_objects API to merge15:34
ihrachysnow that it's in, we should be able to revive it15:34
*** marst has joined #openstack-meeting-alt15:34
ihrachyssince Anindita is no longer with us, we will need to take it over15:34
*** lucasxu has quit IRC15:35
*** julim has joined #openstack-meeting-alt15:35
*** reedip_ has joined #openstack-meeting-alt15:35
ihrachysI guess I can take it for respin15:35
ihrachys#action ihrachys to respin endpoints OVO patch: https://review.openstack.org/#/c/36781015:36
*** lei-zh has quit IRC15:36
ihrachysok, most other patches are in conflicts, and I think we have a lot on our hands for the week already, so I will skip those15:36
ihrachysthere is a small one for tests from manjeetsb : https://review.openstack.org/#/c/411981/15:37
*** shuyingy_ has quit IRC15:37
ihrachysit's nothing major, but seems like there is an issue with a test15:37
ihrachysmanjeetsb, what's your plan for the patch?15:37
*** shuyingya has joined #openstack-meeting-alt15:38
manjeetsbI'll revisit it this week and try to address it15:38
ihrachysok. no rush, it's definitely not top priority15:38
manjeetsbOk15:39
*** slaweq has joined #openstack-meeting-alt15:39
ihrachysok let's move to the next topic15:40
ihrachys#topic Linuxbridge multinode grenade job15:40
*** openstack changes topic to "Linuxbridge multinode grenade job (Meeting topic: neutron_upgrades)"15:40
*** dane_ has joined #openstack-meeting-alt15:40
ihrachysthe job is in check queue, not voting, and failing *sometimes* depending on the cloud15:40
ihrachyswe have this bug reported with proposed solution: https://bugs.launchpad.net/neutron/+bug/168325615:41
openstackLaunchpad bug 1683256 in neutron "linuxbridge multinode depending on multicast support of provider" [High,Confirmed]15:41
ihrachysI initially thought that Kevin will handle it himself, but now I am not sure15:41
ihrachysmaybe worth checking with him if he plans the implementation15:41
manjeetsbMay be we can nudge him and ask ??15:42
ihrachyssounds like a devstack-gate/project-config job15:42
ihrachyskevinbenton, what's your plan for https://bugs.launchpad.net/neutron/+bug/1683256 ?15:42
openstackLaunchpad bug 1683256 in neutron "linuxbridge multinode depending on multicast support of provider" [High,Confirmed]15:42
*** shuyingya has quit IRC15:42
ihrachysdo you plan to tackle it, or we should find someone to take it over?15:42
ihrachysit's prolly quite early for kevinbenton :)15:43
ihrachysok let's figure it out off band15:43
ihrachysI will talk to him15:43
ihrachys#action ihrachys to talk to Kevin about his plans for grenade linuxbridge multinode job setup15:43
ihrachys#topic Open discussion15:44
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:44
ihrachysanyone has anything to discuss?15:44
lujinluonone from me15:45
manjeetsbNone from me as well15:45
*** slaweq has quit IRC15:46
ihrachysok then let's wrap it up15:46
ihrachysoverall I think we do good progress lately15:46
ihrachyslet's complete this OVO saga this cycle ;)15:46
ihrachysthanks everyone15:47
ihrachys#endmeeting15:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:47
openstackMeeting ended Mon Jun  5 15:47:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
manjeetsbThanks15:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-06-05-15.01.html15:47
lujinluothanks15:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-06-05-15.01.txt15:47
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-06-05-15.01.log.html15:47
*** manjeetsb has quit IRC15:51
*** rcernin has quit IRC15:52
*** MapspaM is now known as SpamapS15:54
*** SpamapS has quit IRC15:55
*** SpamapS has joined #openstack-meeting-alt15:55
*** chhavi_ has quit IRC15:58
*** lujinluo has quit IRC16:00
*** julim has quit IRC16:07
*** salv-orlando has joined #openstack-meeting-alt16:07
*** hieulq_ has quit IRC16:08
*** hieulq_ has joined #openstack-meeting-alt16:09
*** reedip_ has quit IRC16:09
*** hieulq_ has quit IRC16:09
*** knangia_ has joined #openstack-meeting-alt16:12
*** rossella_s has quit IRC16:15
*** alexchadin has quit IRC16:17
*** diablo_rojo has joined #openstack-meeting-alt16:22
*** brault has joined #openstack-meeting-alt16:23
*** yamamoto has quit IRC16:24
*** namnh has quit IRC16:25
*** lucasxu has joined #openstack-meeting-alt16:28
*** mickeys has joined #openstack-meeting-alt16:30
*** mickeys has quit IRC16:34
*** sridharg has quit IRC16:34
*** slaweq has joined #openstack-meeting-alt16:34
*** lin_yang has joined #openstack-meeting-alt16:35
*** links has quit IRC16:35
*** diga has quit IRC16:35
*** chhavi has joined #openstack-meeting-alt16:35
*** ltomasbo is now known as ltomasbo|away16:37
*** iyamahat has joined #openstack-meeting-alt16:42
*** harlowja has joined #openstack-meeting-alt16:45
*** bogdando has quit IRC17:01
*** dsariel_ has quit IRC17:01
*** jkilpatr_ has joined #openstack-meeting-alt17:03
*** jkilpatr has quit IRC17:05
*** kzaitsev_ws has quit IRC17:11
*** lucasxu has quit IRC17:13
*** trinaths has joined #openstack-meeting-alt17:14
*** lucasxu has joined #openstack-meeting-alt17:14
*** oidgar has joined #openstack-meeting-alt17:17
*** yamahata has quit IRC17:19
*** iyamahat has quit IRC17:20
*** iyamahat has joined #openstack-meeting-alt17:20
*** yamamoto has joined #openstack-meeting-alt17:25
*** jpena is now known as jpena|off17:30
*** mickeys has joined #openstack-meeting-alt17:30
*** trinaths has quit IRC17:33
*** yamamoto has quit IRC17:33
*** Leo_ has joined #openstack-meeting-alt17:34
*** mickeys has quit IRC17:35
*** tonanhngo has joined #openstack-meeting-alt17:39
*** daidv_ has quit IRC17:44
*** iyamahat has quit IRC17:47
*** lucasxu has quit IRC17:51
*** lucasxu has joined #openstack-meeting-alt17:53
*** janki has quit IRC17:53
*** sambetts is now known as sambetts|afk17:57
*** chhavi has quit IRC18:01
*** MeganR has joined #openstack-meeting-alt18:02
*** rockyg has joined #openstack-meeting-alt18:02
*** salv-orlando has quit IRC18:02
*** salv-orlando has joined #openstack-meeting-alt18:03
*** dizquierdo has quit IRC18:06
*** iyamahat has joined #openstack-meeting-alt18:06
*** salv-orlando has quit IRC18:08
*** JudeC has joined #openstack-meeting-alt18:08
*** lucasxu has quit IRC18:08
*** lucasxu has joined #openstack-meeting-alt18:09
*** cloudrancher has quit IRC18:11
*** cloudrancher has joined #openstack-meeting-alt18:12
*** yamahata has joined #openstack-meeting-alt18:25
*** cloudrancher has quit IRC18:26
*** cloudrancher has joined #openstack-meeting-alt18:27
*** annabelleB has joined #openstack-meeting-alt18:30
*** jkilpatr has joined #openstack-meeting-alt18:31
*** mickeys has joined #openstack-meeting-alt18:31
*** jkilpatr_ has quit IRC18:32
*** mickeys has quit IRC18:36
*** slaweq has quit IRC18:45
*** rockyg has quit IRC18:59
*** bogdando has joined #openstack-meeting-alt19:01
*** brault has quit IRC19:04
*** lucasxu has quit IRC19:15
*** annabelleB has quit IRC19:16
*** slaweq has joined #openstack-meeting-alt19:18
*** annabelleB has joined #openstack-meeting-alt19:20
*** MeganR has quit IRC19:22
*** Leo_ has quit IRC19:22
*** armstrong has joined #openstack-meeting-alt19:22
*** egallen has joined #openstack-meeting-alt19:24
*** mickeys has joined #openstack-meeting-alt19:32
*** armstrong has quit IRC19:34
*** lucasxu has joined #openstack-meeting-alt19:34
*** Leo_ has joined #openstack-meeting-alt19:36
*** mickeys has quit IRC19:36
*** MarkBaker has joined #openstack-meeting-alt19:39
*** fnaval has quit IRC19:39
*** Leom has joined #openstack-meeting-alt19:40
*** Leo_ has quit IRC19:40
*** egallen has quit IRC19:41
*** tobberydberg has joined #openstack-meeting-alt19:45
*** julim has joined #openstack-meeting-alt19:46
*** oidgar has quit IRC19:49
*** tobberydberg has quit IRC19:49
*** rcernin has joined #openstack-meeting-alt19:49
*** namnh has joined #openstack-meeting-alt19:52
*** julim has quit IRC19:58
*** annabelleB has quit IRC19:58
*** blancos has joined #openstack-meeting-alt19:58
*** jprovazn has quit IRC19:59
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon Jun  5 20:00:36 2017 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
dave-mccowan#topic roll call20:00
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:00
*** fnaval has joined #openstack-meeting-alt20:01
*** panda is now known as panda|off20:01
*** jackie-truong has joined #openstack-meeting-alt20:01
namnhdave-mccowan: hello dave and everyone20:01
dave-mccowanhi namnh thanks for joining.  did you wake up early or stay up late?20:02
dave-mccowanno one else has joined yet20:03
namnhdave-mccowan: yead, I had to wake up early, in my country, it is 3 am for now20:03
*** salv-orlando has joined #openstack-meeting-alt20:03
dave-mccowanwe can get started... maybe others will read the minutes later.20:05
dave-mccowan#topic pike status20:05
*** openstack changes topic to "pike status (Meeting topic: barbican)"20:05
dave-mccowanthis week is Milestone 2 release20:05
dave-mccowanhttps://etherpad.openstack.org/p/barbican-tracker-pike20:05
*** Leom has quit IRC20:05
dave-mccowan#topic PTG20:05
*** openstack changes topic to "PTG (Meeting topic: barbican)"20:05
*** jkilpatr has quit IRC20:06
dave-mccowanthe ptg is coming up20:06
dave-mccowanhttps://www.openstack.org/ptg/20:06
*** fnaval has quit IRC20:06
dave-mccowanseptember 11-15 in Denver, CO.  Barbican has a room reserved, but we should confirm we will have enough interested attendees20:07
*** fnaval has joined #openstack-meeting-alt20:07
dave-mccowan#topic Offline Upgrade Discussion20:08
*** openstack changes topic to "Offline Upgrade Discussion (Meeting topic: barbican)"20:08
dave-mccowansorry more people didn't join namnh20:08
dave-mccowanplease go ahead though20:08
namnhFor now, we have a blocking point about grenade gate. Currently, one patch set was merged, we have another patch set need to merged on ocata branch20:10
*** kfarr has joined #openstack-meeting-alt20:10
namnhhttps://review.openstack.org/#/c/467388/20:10
dave-mccowanhi kfarr20:11
kfarr\o/20:11
*** dtrainor has quit IRC20:11
namnhI think we have to wait for Douglas's comment on it. is that right?20:11
*** MarkBaker has quit IRC20:11
namnhkfarr: hello kailtin20:11
*** dtrainor has joined #openstack-meeting-alt20:11
dave-mccowanwe need either douglas, or someone from the stable-branch team to merge20:12
*** MarkBaker has joined #openstack-meeting-alt20:12
dave-mccowando we know why so many gate jobs failed on that patch?  are there other patches that need merge first?20:12
*** mickeys has joined #openstack-meeting-alt20:12
kfarryes, the ones that are failing are the new ones that only stand up barbican and keystone20:14
kfarrbut the stable branches don't have the patch that made them work on master20:15
*** egallen has joined #openstack-meeting-alt20:15
*** bogdando has quit IRC20:15
kfarrso I think the solution is to keep the old gates only on the stable branches, and disable the new ones on stable20:15
namnhthat's why, you had this patch https://review.openstack.org/#/c/469648/ to don't allow run the gates on ocata newton mitaka.20:15
kfarrright right20:16
namnhbtw, I updated a new patch set on it.20:16
kfarryeah I saw20:16
dave-mccowanok.  i'll ping the stable team to merge 437388.20:16
dave-mccowannamnh do we need anything else?20:17
kfarrdave-mccowan would you like to be a member of the barbican stable team?20:17
namnhi have one patch set to make our docs more beautiful. https://review.openstack.org/#/c/470895/20:18
namnhkfarr: please help me to review it.20:18
kfarrthanks namnh !20:18
kfarrdave-mccowan I think each project is supposed to have a couple of people on the project team that can merge patches to stable branches20:19
kfarrso that we don't have to bug the stable team each time20:19
dave-mccowani asked a few months ago.  since at that point i didn't have a track record of reviewing stable patches, they weren't inclined to grant me +2, but they were more than happy to do it for me.  that's fine with me.  always good to have an extra set of eyes.  if it becomes an issue, i'll ask again.20:19
namnhdave-mccowan: after we finish the gate. I can make a patch to request a tag to TC and add you as reviewer. is that right?20:20
dave-mccowannamnh yes, that is great.20:20
*** slaweq has quit IRC20:21
namnhdave-mccowan: ok, I will do it, thanks20:21
*** Leo_ has joined #openstack-meeting-alt20:21
dave-mccowannamnh is there anything that needs to happen for upgrade when pike ships and we start queens?20:21
*** jkilpatr has joined #openstack-meeting-alt20:22
*** lucasxu has quit IRC20:22
namnhdave-mccowan: I think no. But don't worry about that, I will follow this feature.20:23
dave-mccowanthanks!  anything else?20:23
namnhthat's all my option20:23
namnhabout rolling upgrade, i will discuss later20:24
*** annabelleB has joined #openstack-meeting-alt20:24
dave-mccowan#topic any other business20:24
*** openstack changes topic to "any other business (Meeting topic: barbican)"20:24
jackie-truongHi barbican team. Would someone mind reviewing this patch? It's waiting on one more +2. Thanks! https://review.openstack.org/#/c/455459/20:24
dave-mccowanthanks jackie-truong i'll take a look20:25
*** slaweq has joined #openstack-meeting-alt20:25
jackie-truongthanks!20:25
*** annabelleB has quit IRC20:25
*** Leo_ has quit IRC20:26
*** dimtruck is now known as zz_dimtruck20:26
*** Leo_ has joined #openstack-meeting-alt20:27
dave-mccowanlooks like that's it for today.  thanks everyone!20:27
namnhdave-mccowan: wait a moment, are there something wrong on your opinion: " ok.  i'll ping the stable team to merge 437388."20:28
*** tobberydberg has joined #openstack-meeting-alt20:28
namnhi think that is 46738820:28
*** egallen has quit IRC20:28
namnhdave-mccowan: right?20:28
dave-mccowannamnh yes, that's right.20:28
*** slaweq has quit IRC20:29
dave-mccowani just asked in #openstack-stable20:30
namnhdave-mccowan:thanks for your help, I hope that it can be merged ASAP20:30
*** shuyingya has joined #openstack-meeting-alt20:31
dave-mccowan#endmeeting20:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:32
openstackMeeting ended Mon Jun  5 20:32:02 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-06-05-20.00.html20:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-06-05-20.00.txt20:32
*** slaweq has joined #openstack-meeting-alt20:32
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-06-05-20.00.log.html20:32
*** tobberydberg has quit IRC20:32
namnhthanks dave-mccowan, kfarr20:32
*** namnh has quit IRC20:34
*** jackie-truong has quit IRC20:34
*** cleong has quit IRC20:35
*** shuyingya has quit IRC20:36
*** slaweq has quit IRC20:36
*** blancos has left #openstack-meeting-alt20:43
*** fnaval has quit IRC20:43
*** markstur has joined #openstack-meeting-alt20:46
*** annabelleB has joined #openstack-meeting-alt20:47
*** rcernin has quit IRC20:47
*** lucasxu has joined #openstack-meeting-alt20:47
*** annabelleB has quit IRC20:48
*** zz_dimtruck is now known as dimtruck20:48
*** annabelleB has joined #openstack-meeting-alt20:50
*** dave-mccowan has quit IRC20:54
*** leong has joined #openstack-meeting-alt20:54
*** kfarr has quit IRC20:54
*** shamail has joined #openstack-meeting-alt20:55
*** annabelleB has quit IRC20:55
*** Arkady_Kanevsky has joined #openstack-meeting-alt20:58
*** ansmith has quit IRC20:58
*** annabelleB has joined #openstack-meeting-alt20:58
Arkady_Kanevskyhello PWG20:58
*** MeganR has joined #openstack-meeting-alt20:59
leong#startmeeting product_working_group21:00
openstackMeeting started Mon Jun  5 21:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is leong. 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: product_working_group)"21:00
openstackThe meeting name has been set to 'product_working_group'21:00
leong#chair shamail21:00
openstackCurrent chairs: leong shamail21:00
leonghi all21:00
MeganRHi21:00
leong#topic rollcall21:00
*** openstack changes topic to "rollcall (Meeting topic: product_working_group)"21:00
AndyUo/21:00
Arkady_Kanevskyhello all21:00
shamailhi21:00
leongthis is PWG meeting :)21:00
AndyUhi all21:00
annabelleBhello!21:00
leongtoday agenda can be found here:21:01
*** egallen has joined #openstack-meeting-alt21:01
MeganRo/21:01
leong#link Agenda https://wiki.openstack.org/wiki/Meetings/product-team21:01
leongif you have anything else not in the agenda, please feel free to shout out :-)21:01
*** rockyg has joined #openstack-meeting-alt21:01
leong#topic Review of action items from previous meeting21:02
*** openstack changes topic to "Review of action items from previous meeting (Meeting topic: product_working_group)"21:02
leong#link Previous minutes: http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-05-22-21.00.html21:02
leongis mrhillsman here?21:02
leongI have replied to JohnG email on the hashtag21:03
leongdidn't see any further diccussion on the thread21:03
Arkady_KanevskyWhat is the action for review the ##hashtag result?21:04
leonghave anyone look at the ##hashtag result?21:04
shamailI have not yet21:04
leongArkady: that would be on today Agenda item21:05
Arkady_Kanevskyme neither. But want to understand what are we looking for?21:05
Arkady_KanevskyDo we want to propose some new stories?21:05
leongi have submitted a patch to fix some ##hashtag, can core please review?21:05
Arkady_KanevskyI will take taht AI, Leong.21:05
MeganRI have not looked, either21:05
leong#link hashtag patch: https://review.openstack.org/#/c/469267/21:06
jamemccJamey here: I have - I find the ones we put #LCOO to be a really ueseful and quick cross reference to things taht got discussed and we want to carry forward21:06
AndyUI haven't read through them either. There's a lot there.21:06
leongthe patch also included the "python-program"21:06
leonganyone can contribute to improve that python-program if needed :)21:06
mrhillsmano/21:06
leonghi mrhillsman21:06
leongmrhillsman: previous meeting action item -> mrhillsman to follow up on the summaries and video/method of providing guidance on moderating21:07
leongany updates?21:07
*** lucasxu has quit IRC21:07
*** rockyg has quit IRC21:07
mrhillsmanI got the video from rockyg that was done21:07
mrhillsmanI think it with supplemental will suffice, as shooting another video is probably overkill21:08
leongok21:08
mrhillsmanWiki page consolidating all the things maybe?21:09
leongmrhillsman: Wiki page consolidating all the things? can you elaborate more?21:09
mrhillsmanWell, we have the video, moderator template, ops meetups moderator guide, FAQs, eyc21:10
mrhillsmanetc21:10
*** rockyg has joined #openstack-meeting-alt21:10
leongare you thiking putting at "PWG" wiki page or "UC" wiki page?21:10
Arkady_Kanevskywe do need to update out wiki. https://wiki.openstack.org/wiki/ProductTeam. It is still stuck on Ocata not Pike.21:11
mrhillsmanProbably standalone anyone cam link to may be best21:11
leongnot only update, but also "simplifying" :)21:11
shamailstandalone makes sense21:11
AndyUagree w /mrhillsman about standalone21:12
shamailand linked to from the Forum and Ops Meetup pages21:12
leonganyone interested to contribute to updating/simplifying the PWG wiki? including the video, moderator template, ops meetups moderator guide, FAQs?21:12
AndyUI am o/21:12
shamailWhy are the moderator templates, ops meetups moderator, etc in PWG?21:12
mrhillsmanleong I dont...^21:12
shamail(sorry if this has been covered already)21:12
leongshamail: that's my original question :)21:12
shamailAh ok21:13
leong[14:10] <leong> are you thiking putting at "PWG" wiki page or "UC" wiki page?21:13
*** tobberydberg has joined #openstack-meeting-alt21:13
shamailI think the content related to moderating sessions should be on its own page (not PWG or UC) as mrhillsman suggested. The content can be linked as needed to event pages in that case and anyone could edit it as well.21:13
leongi think it makes sense to put in a wiki "outside" PWG, maybe within UC? or a standalone wiki?21:14
mrhillsmanRight, neither, standalone and others can link to it.21:14
leongshamail: +!21:14
leong+121:14
*** rocky_g has joined #openstack-meeting-alt21:14
Arkady_Kanevsky+121:14
AndyUstandalone21:14
leongso we have two action item on wiki21:14
*** rockyg has quit IRC21:14
leong1. update and simplify PWG wiki21:14
Arkady_Kanevskybut how would people find standalone wiki? Do we have master index?21:14
leong2. create a standalone wiki for video, moderator template, ops meetups moderator guide, FAQs21:14
leongarkady, with standalone wiki, any other group can reference it21:15
leonganyone interest to take on (1) or (2) ?21:15
AndyUright. It would be linked to from other pages21:15
* leong the room seems quite....21:16
leonganyone interest to take on (1) or (2) ?21:16
leong:)21:16
mrhillsmanwe have this - https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide21:16
Arkady_KanevskyI will take 1.21:16
mrhillsmani can #221:16
Arkady_KanevskyWill send proposal to email reflector21:16
mrhillsmanwill start with that21:16
AndyUI'm willing to help with 1 or 221:16
mrhillsmanadd other stuff, email folks to modify/update as necessary21:17
leong#action Arkady_Kanevsky and AndyU to work on updating/simplifying PWG wiki21:17
leong#action mrhillsman and AndyU to work on standalone wiki page for video, moderator template, ops meetups moderator guide, FAQs21:18
leongmrhillsman: +1 on starting from the existing guide21:18
AndyUI see that "or" became an "and"  ;)  That's ok.21:18
*** tobberydberg has quit IRC21:18
leonghaha.. ops21:18
mrhillsmanhehe21:18
leongandyu: up to you to pick one :)21:19
Arkady_KanevskyThanks for help AndyU21:19
leongok.. let's move on to next topic21:19
AndyUI'm happy to help with both.21:19
*** annabelleB has quit IRC21:19
leong#topic Action Plan21:19
*** openstack changes topic to "Action Plan (Meeting topic: product_working_group)"21:19
*** julim has joined #openstack-meeting-alt21:19
leongin last meeting, we talked about two PWG value21:19
leong#info Value 1: Properly documenting ideas, getting a structured workflow, and integration into development workflow21:19
leong#info Value 2: Periodic coordination/collaboration across WGs/Product Managers21:19
*** rocky_g has quit IRC21:19
*** annabelleB has joined #openstack-meeting-alt21:19
leongi would like to turn that into some deliverables and action plan21:20
leongis there anything that we can do in order to "deliver" both the value?21:20
*** slaweq has joined #openstack-meeting-alt21:21
Arkady_KanevskyLeong are you thinking of some automated process?21:21
* shamail is in two meetings atm, sorry.21:21
leongfor example: would "updating/simplifying" wiki be an action items to achieve value 1?21:21
AndyUFor #1, I think that we need to do some marketing of the Dev Proposal flow, purpose, etc to wg's, project teams, etc.21:21
leongArkady_Kanevsky: anything that allow us to achieve the value21:21
*** dustins has quit IRC21:22
leongArkady_Kanevsky: is more about what sort of tactics we should do in order to deliver both value21:22
Arkady_Kanevskydo not think so Leong. Do not see how it will simplify the process. We will have a pointer to templated proposals.21:22
AndyUI the dev proposal forum session we found that no one there had even heard of it before21:22
leongArkady_Kanevsky: yeah.. u are thinking along the line :)21:22
leongso my question would be: what should we do in order to realize the value21:23
Arkady_Kanevskywe did change our nomenclature in Milan meeting.21:23
Arkady_KanevskyWe can update wiki and send email blast with details on proposal idea flow.21:23
leongArkady_Kanevsky: so we do need to update the wiki first....21:24
Arkady_KanevskyI think so.21:24
MeganRare we thinking of meeting with PTLs or with the TC to discuss our "value"21:24
AndyUNeed to increase awareness of the dev proposal flow and encourage quality participation21:24
*** slaweq has quit IRC21:25
Arkady_Kanevsky+1 AndyU.21:25
*** slaweq has joined #openstack-meeting-alt21:25
leongMeganR: i am thinking how can we get PTLs/core involved as part of the PWG workflow21:25
AndyUTo MeganR's point, PTL's and TC need to understand and support the dev prop flow21:26
MeganRhave we asked them directly?21:26
leongMeganR: that brought up a good question21:26
leongso far PTL/core seems not involved in the process21:27
leongapart that from the Baremetal use case, i do reach out to ex PTL and core of Ironic21:27
AndyUI only spoke with a few PTL and TC but none knew about the process21:27
*** rocky_g has joined #openstack-meeting-alt21:27
AndyUat the summit that is21:27
Arkady_KanevskyIt is too early whne we get proposal isea submitted till we decompose it and do gap analysis21:28
rocky_ghey again.21:28
MeganRAndyU: can we follow-up with those you spoke with - I'm thinking that we pick a few to "review" the process, and get their feeback and buy-in21:28
Arkady_KanevskyWe can add PTL for specific project to proposal review list.21:28
leongArkady_Kanevsky: +1.. i think PTL/core would only be interested after (or at) the Gap Analysis phase21:28
shamailIn order for them to support it they have to be aware of it but also it has to have value for them. We have to think about how to show value in “subscribing” to this process.21:29
*** marst has quit IRC21:29
shamailArkady_Kanevsky: +121:29
leongfor baremetal, we completed the gap-analysis21:29
AndyUMeganR - we can try21:29
leongbut not for the rest of development proposals21:29
*** annabelleB has quit IRC21:29
Arkady_KanevskyShould we add optionally to proposal template expected projects impacted.21:30
AndyU+1 Arkady21:30
Arkady_KanevskyWith that we will be able to add a core or PTL for these projects for review.21:30
leongArkady_Kanevsky: that was includd in the Gap Analysis (for Baremetal case)21:30
AndyUIn our forum session, project leads/cores expressed a desire to be aware and plugged in early.21:31
leong#link baremetal gap analysis: https://github.com/openstack/development-proposals/blob/master/gap-analysis/proposed/baremetal-service.rst21:31
Arkady_KanevskyWe definitely do that for gap analysis. But does it make sense to involve them at proposal review also?21:31
MeganRis that too late, adding them for the "review" if they don't know about the process now.  Should we be communicating with the PTL when we first receive a project, and let them know that we are working on it?21:31
AndyUI think waiting for Gap Analysis may be too late.21:32
shamailMeganR: +121:32
shamailThat would allow them to decide how involved they want to be and when21:32
leongagree: we should get PTL/core aware as early as possible21:32
*** mjura has quit IRC21:32
Arkady_KanevskyMy obejctive is to get PTL input if idea was circulatd before in the team and got feedback that we are not aware of.21:32
AndyUBut for it to be sooner we need to raise the bar on what qualifies a proposal to move forward. It's too easy to just write up the first part with no real will or ability to drive any farther. Don't wantg to waste peoples time.21:33
leongAndyU: +121:33
Arkady_Kanevsky+1 AndyU21:33
leongso who shall make the call that a proposal is "qualified/good-enough" to move forward? PWG?21:33
Arkady_Kanevskygreat quetsoin.21:34
AndyUMaybe we meet with proposal owners and ask them questions about how they plan to move it forward, assess if it seems viable21:34
Arkady_KanevskyI think it is PWG now/21:34
MeganRWhy don't we get it to an approved point with the PWG and then reach out to the PTL for their input21:34
*** baoli has quit IRC21:34
Arkady_KanevskyWe do that as part of gap analsyis stage21:34
MeganRI was thinking earlier21:35
leongso PWG need to take an "active" role to review all proposals21:35
MeganRdecide what is the "bare minimum" to move it forward and then engage the PTL21:35
Arkady_KanevskyLeong +121:35
AndyUThe current Approved/Accepted step perhaps should vbe thought of as approved DRAFT which then moves into a 2nd phase of revision with project stakeholders?21:36
leonganother question is: would PWG has enough skillset to review the proposal?21:36
Arkady_Kanevskyif we do not know if we can pull people from our companies for help21:37
Arkady_Kanevskyif we do not have enouhg skills we can pull people fomr our respective companies for help21:38
leongok. so can we take on existing Development Proposals and move forward from there?21:38
AndyUI think PWG definitely can determine when it is sufficiently clear and focused. When it is agreed to be addressing a significant need and so forth.21:38
leongcan we review this list and see which one is ready to move forward?21:39
leong#link Existing Proposal: https://github.com/openstack/development-proposals/tree/master/development-proposals/proposed21:39
leong#link Proposal working-in-progress: https://review.openstack.org/#/q/project:openstack/development-proposals+status:open21:40
leongi mean: can we review this list over the week (not now) and see which one is ready to move forward?21:41
*** Leo_ has quit IRC21:41
leong:)21:41
*** Leo_ has joined #openstack-meeting-alt21:41
Arkady_Kanevskywe need to review a few of them.21:41
leong#action all to review existing+wip proposals and decide which one is ready to move forward with wider participation from PTL/core21:41
Arkady_KanevskyCan use help for reveiw of https://review.openstack.org/44466421:42
*** shamail has quit IRC21:42
leongfor Value 2: Periodic coordination/collaboration across WGs/Product Managers21:42
AndyUWe're organizing some support behind the logging proposal and will be breathing new life into that21:42
Arkady_KanevskyLeong do you want everybody to send email on result of review?21:43
rocky_gAndyU, ++21:43
*** gouthamr has quit IRC21:43
leongArkady_Kanevsky: i am fine with it21:43
Arkady_KanevskyOK21:43
leongArkady_Kanevsky: for WIP proposal, we can review on gerrit21:43
*** iyamahat has quit IRC21:43
AndyUrocky_g - I didn't forget. We're mobilizing a lot of support now. Will reach out soon.21:44
leongfor those "merged" proposals, let's discuss over ML21:44
leongfor Value 2: Periodic coordination/collaboration across WGs/Product Managers21:44
*** fnaval has joined #openstack-meeting-alt21:44
*** shamail has joined #openstack-meeting-alt21:44
leongi think we need to work closely with UC and participate in cross-wg discussion21:44
*** cloudrancher has quit IRC21:45
leongi will keep that as an ongoing discussion item21:45
Arkady_KanevskyOK.21:45
leongi want to spend some time on next agenda21:45
jamemccPer previous desire for PWG to help the WG with their development proposal - we have this session on Wednesday: #link https://openstack-lcoo.atlassian.net/wiki/display/LCOO/2017.06.7-8+Specialty+-+Containerized+Control+Plane+User+Stories+-+kickoff21:45
leong#topic Post-forum report21:45
*** openstack changes topic to "Post-forum report (Meeting topic: product_working_group)"21:45
*** cloudrancher has joined #openstack-meeting-alt21:46
Arkady_Kanevskywhat do we need to do for cross-wg discussion?21:46
leongNext step on ##hashtag - https://github.com/openstack/development-proposals/tree/master/forum/201705-bos21:46
leongwhat do we want to get out from the ##hashtag result?21:46
leongare we going to create a post-forum report based on the ##hashtag result?21:46
leongor is the existing ##hashtag result sufficient enough?21:47
leongare we able to derive any new development proposals from the ##hashtag result?21:48
Arkady_Kanevskywe chaired a few UC sesson and collected data on it. Several of us sent email on it21:48
mrhillsmandid you say the scripts used to generate those are online?21:48
shamailI think we need to mine the data and search insights21:48
shamailversus just the raw results21:48
AndyUWe spoke of (1) making the various stakeholders aware of things in pads relevant to them21:48
mrhillsman+1 shamail21:48
AndyUyes, and what Shamail said21:48
leongwhat are we trying to "mining"?21:49
AndyUAlso spoke of looking for the bigger themes21:49
mrhillsmanit seems from there one could "get out" of it something21:49
shamailinteresting data, correlations, items with high discussion, recurrence, etc21:49
mrhillsmanmaybe which tags...^21:50
mrhillsmanalways faster than me hehe21:50
shamail:P21:50
leongso that would probably need "manual mining" i presume...21:50
shamailyea21:51
shamailat least the first time21:51
leonganyone interested to sign up for the data mining?21:51
shamailuntil we identify things to mine for21:51
Arkady_Kanevskyhow many pages do we have to mine?21:51
leongi can't do it alone :)21:51
AndyUhow do you propose to do it?21:51
mrhillsmanhehe, agreed leong21:51
MeganRI can help - just need a clear understanding of what I'm looking for21:52
leongactually the files are not too large for this first-time round21:52
*** julim has quit IRC21:52
AndyUalmost seems like we'd need to just skim the etherpads directly. We don't yet know if the hashtag's were even used effectively21:52
Arkady_KanevskyI thiunk each of us can review several. Just need to devide across us21:52
mrhillsmani am going to focus on the wiki page for moderators and can help once it takes a little bit of shapre21:52
mrhillsmanshape21:52
shamailyeah21:52
shamaillets divide etherpads21:53
shamailtotal # / volunteers21:53
leongMeganR: i think we are trying to mine/figure out "what are things we are looking for" :)21:53
shamaili’ll help21:53
Arkady_KanevskyI think we are looking for "new" requirements.21:53
*** slaweq has quit IRC21:53
AndyUlike mrhillsman, I'd like to focus on the wiki pages21:53
mrhillsmanunfulfilled/stale "old" requirements?21:53
Arkady_Kanevskyor refinement of existign ones - gaps21:54
MeganR@leong - thanks for the clarification, I think  :)21:54
mrhillsmanbetter said Arkady_Kanevsky21:54
leongok.. can we use this etherpad to focus on this effort?21:55
leonghttps://etherpad.openstack.org/p/PWG-forum-analysis21:55
*** diablo_rojo has quit IRC21:55
*** iyamahat has joined #openstack-meeting-alt21:55
leong#link PWG Forum Data Mining: https://etherpad.openstack.org/p/PWG-forum-analysis21:55
*** slaweq has joined #openstack-meeting-alt21:55
leongput up the list of etherpads/wiki pages and sign up for mining21:56
rocky_gAlso, as an FYI, dovetail, or some such, did you guys see https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA/edit#gid=021:56
rocky_gThe Public Cloud WG gaps list21:56
*** jcoufal has quit IRC21:57
AndyUrocky_g - thanks for sharing21:58
Arkady_Kanevskythis is for public cloud. DO we have one for each use case?21:58
leongalright, are we good with the plan for data mining?21:58
* leong 2 mins21:58
Arkady_Kanevsky2 min left.21:58
*** tristanC has joined #openstack-meeting-alt21:59
leongrocky_g: i would suggest if the public wg can define that in the PWG development proposals, we shall collaobrat with them21:59
rocky_gArkady_Kanevsky, the gaps can be organized and would turn into a story or three... but they aren't as yet.21:59
Arkady_KanevskyOK21:59
leongi guess we can wrap up here22:00
leongthanks everyone for joining the call22:00
mrhillsmanl8r22:00
mrhillsmanthx leong22:00
AndyUHave a good week all22:00
leong#endmeeting22:00
Arkady_KanevskyHave a great day22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Mon Jun  5 22:00:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-05-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-05-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-05-21.00.log.html22:00
*** Arkady_Kanevsky has quit IRC22:00
rocky_gThe biggest hole is really "roles"  as in cloud ops, domain ops, domain user, etc.  The whole nested, hierachical cloud management thing.22:00
*** slaweq has quit IRC22:00
*** shamail has quit IRC22:01
*** Shrews has joined #openstack-meeting-alt22:01
* fungi smells a zuul22:01
*** MeganR has quit IRC22:01
* jeblair sniffs around22:02
clarkbdoes it smell like a dinosaur?22:02
jeblairoh there it is22:02
fungimore like a wumpus22:02
mrhillsmanstinky22:02
fungihttps://en.wikipedia.org/wiki/Hunt_the_Wumpus22:02
jeblairSpamapS, jlk, mordred, Shrews, pabelanger, tristanC: courtesy ping22:03
* mrhillsman so wants to play now22:03
pabelangerpresent for atleast 30mins, then I have to board a train22:03
tristanCoh hai!22:03
* Shrews here, just also doing dinner things22:03
jeblair#startmeeting zuul22:03
openstackMeeting started Mon Jun  5 22:03:44 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
*** openstack changes topic to " (Meeting topic: zuul)"22:03
openstackThe meeting name has been set to 'zuul'22:03
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-22-22.04.html22:04
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:04
jeblair#topic Actions from last meeting22:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: zuul)"22:04
jeblairpabelanger create zuul-base-jobs and zuul-jobs repos22:04
pabelangerthey should be created22:04
jeblairw00t22:05
pabelangerconfirmed22:05
jeblairi think reviews there have probably taken a back seat to the server work22:05
SpamapSo/22:05
pabelangeryes, I haven't started migrating anything into them as of yet22:05
pabelangerlikely after new servers are online I can switch back to that22:05
jeblair#topic Status updates:  Zuul sample jobs22:05
*** openstack changes topic to "Status updates: Zuul sample jobs (Meeting topic: zuul)"22:05
jeblairlet's just segue into that...22:06
jeblairsince i think this rightly takes a back seat to the new server work right now22:06
*** jamesbenson has quit IRC22:06
jeblairsince we've just landed some changes that will prevent us running zuulv3 on the current dev server if we restart it22:06
pabelangerya, I haven't done much work over the last week on jobs22:06
* mordred waves22:06
pabelangerzuulv3.o.o is online, working on ze01.o.o next22:07
*** MarkBaker has quit IRC22:07
jeblairit makes sense to me to prioritize getting the xenial server up, then resume work on the jobs.22:07
jeblairthere's also one more config-breaking change that i think we need to land before we can really push on this22:07
pabelangerwfm, I plan on focusing on ze01 tomorrow22:08
jeblairit's the one that should let us more easily share repos across zuul installs22:08
SpamapSoooo like, puppetized zuulv3.o.o ?22:08
SpamapSthat's nice. :)22:08
*** tobberydberg has joined #openstack-meeting-alt22:08
jeblair(eg, share repos between zuul and bonnyci, etc)22:08
*** egallen has quit IRC22:08
jeblairSpamapS: yep!22:08
pabelangerpython3 too22:08
* SpamapS is playing with trying to get jlk's containerization work in zuulv3 deployed into Bluemix's shiny new k8s service.22:09
jeblair(in order to share repos effictively, we need to be able to indicate that we only want to load certain config objects from certain repos, eg, bonnyci does not want to load our pipeline config.  this is also important for third-party ci)22:09
*** egallen has joined #openstack-meeting-alt22:09
mordredjeblair: ++22:10
pabelangergreat22:10
jeblair#info zuul now requires bubblewrap which needs at lesat ubuntu xenial, and will require python3 soon22:10
jeblair#info work on puppetized production xenial zuulv3.openstack.org is in progress22:10
*** neil__ has quit IRC22:10
pabelanger469994 could use a review22:11
pabelangerthat is the puppet executor part22:11
pabelangersystem-config is ready22:11
jeblair#info effective use of sample jobs requires a change to zuul to specify which config objects should be loaded per-project22:12
jeblair#info work on sample jobs will resume when xenial server work and repo-config-object change is complete22:12
*** felipemonteiro has quit IRC22:12
pabelangerI have to step away for 20mins or so22:12
jeblairpabelanger: thanks!22:12
*** tobberydberg has quit IRC22:12
jeblair#topic Status updates: Zuul test enablement22:13
*** openstack changes topic to "Status updates: Zuul test enablement (Meeting topic: zuul)"22:13
*** rocky_g has quit IRC22:13
jeblairi know there are some outstanding changes in need of review22:13
SpamapSI don't think we have any left that are straight forward22:13
jeblairi hope to review them soon; i've just been trying to push some production-blockers through22:13
jeblairone of which might (depending on how you count) dispose of a number of tests22:14
*** cknight has quit IRC22:14
jeblair(it deals with the cloner tests)22:14
*** jamielennox has joined #openstack-meeting-alt22:14
jeblairi hope to have this bubble back up to the top of my list soon22:15
jeblairanything else related to test enablement?22:15
jeblair(as usual, if anyone is working on a test and has questions, feel free to ping me)22:15
SpamapSThe sshkey one is a bit confusing to me22:15
jeblairSpamapS: which one is that?22:16
SpamapSjeblair: test_timer_sshkey22:16
SpamapSit tries to find an SSH wrapper for gerrit when a job is started via timer22:16
SpamapSbut the code that makes ssh wrappers is gone? or something? I'm not sure.22:16
SpamapSI've bounced off of it twice.22:17
jeblairSpamapS: hrm, i'll look at that post-meeting22:17
SpamapSyeah it's the only one I'm still trying to tackle22:17
SpamapSthe others are related to your branch work and the cloner work22:17
SpamapS(I think if you count all in-flight we're down to 5 that have not been addressed)22:18
jeblair\o/22:18
jeblair#topic Status updates: Github22:18
*** openstack changes topic to "Status updates: Github (Meeting topic: zuul)"22:18
jeblairi propose we drop this from the fixed agenda, on account of the branch has landed :)22:19
jeblair(there's still more work to do, but we have something that, if not working, at least passes tests :)22:19
SpamapSSeconded.22:19
*** salv-orlando has quit IRC22:19
jeblairmotion carries, or something22:20
jeblair#topic Status updates: Bubblewrap22:20
*** openstack changes topic to "Status updates: Bubblewrap (Meeting topic: zuul)"22:20
jeblairditto :)22:20
jeblairi'm not sure anyone has run this in production yet, and we won't until we have the xenial server22:21
SpamapSThere is one minor topic here.. which is that with bubblewrap landing, we've made the zuul-executor difficult to run in a container22:21
jeblairbut that's rsn.22:21
jamielennoxomg, github AND bubblewrap landed? it's like christmas22:21
clarkbSpamapS: it currently needs to be privileged container?22:21
SpamapSContainers running zuul-executor need to be run privileged now.22:21
SpamapSOr you can use the nullwrap driver and drop bubblewrap22:22
mordredjamielennox: welcome back!22:22
jamielennoxo/22:22
pabelangerhave internet again22:22
jeblairSpamapS: how onerous a requirement would you say that is?22:23
pabelangerthey also need port 79/tcp right?22:23
*** gouthamr has joined #openstack-meeting-alt22:23
*** neil__ has joined #openstack-meeting-alt22:23
jamielennoxSpamapS: also do you know exactly why?22:23
SpamapSSo, that's why I started playing with deploying in Bluemix's k8s22:23
Shrewspabelanger: no, that's configurable now22:23
SpamapSWhich does allow your pods to be privileged.22:23
tristanCif zuul-executor needs to contains it's own execution, what's the issue with it running in a privileged container?22:23
pabelangerShrews: cool, wasn't following that. thanks22:23
mordredtristanC: that would make it harder to run in a public k8s service22:23
fungii guess the issue is that it becomes a nested containerization problem?22:24
SpamapStristanC: some container services don't allow you to run privileged.22:24
mordredSpamapS: oh -it does? neat22:24
SpamapSmordred: yeah, since your cluster is made up of VMs that you own.22:24
*** annabelleB has joined #openstack-meeting-alt22:24
SpamapSAnyway, it's just something I wanted to make sure we socialize.22:24
mordredSpamapS: sweet. that should buy a little time- I had some thoughts on this topic over the weekend I need to vomit out somewhere so that you can comment on them22:24
pabelangerusing nullwrap driver seems to be a good compromise for unprivileged containers22:25
jeblairpabelanger: compromise being the operative word22:25
pabelangerwould it make sense to run bwrap in a container?22:25
SpamapSThere's a thought I have also which is to possibly have untrusted-only and trusted-only executors which would make running w/ nullwrap possibly safer.22:25
SpamapSbut it's more of a high-scale high-class problem so I'll keep stewing on it.22:25
tristanCthen how difficult would it be to run a zuul-executor container for trusted config, and another one for untrusted config?22:25
tristanCto move the nested logic one layer up...22:26
SpamapSpabelanger: it definitely makes sense to run bwrap in a container, since the point is to shield executor data from untrusted playbooks.22:26
mordredtristanC, SpamapS: jobs can have trusted and untrusted content in the same job22:26
SpamapSmordred: I know, that's why this is still stewing. :)22:26
pabelangerSpamapS: right, I see what you are saying now22:26
mordredSpamapS: stew is tasty22:26
SpamapSand chunky22:26
jeblair(the use case for that is: consider a user may want to take the logs from an untrusted job and put them somewhere that requires special access to write to)22:27
jeblair(it's not farfetched :)22:27
jeblairSpamapS: i guess the action item at the moment is: once we write the operational docs, make sure we treat this subject.22:28
SpamapSjeblair: agreed22:29
jeblairi expect docs will be a standing agenda item in the near future... :)22:29
jeblairlet's move on to...22:29
jeblair#topic Progress summary22:30
*** openstack changes topic to "Progress summary (Meeting topic: zuul)"22:30
*** annabelleB has left #openstack-meeting-alt22:30
SpamapSso the board has been getting almost no attention from me lately22:30
SpamapS#link https://storyboard.openstack.org/#!/board/4122:30
jeblairi got a lot of emails from my cron script22:30
jeblairso *something* has been happening :)22:30
SpamapSYeah we're using storyboard for sure22:31
*** kumarmn has quit IRC22:31
jeblair#action triage new lane in storyboard22:31
jeblair#undo22:31
openstackRemoving item from minutes: #action triage new lane in storyboard22:31
jeblair#action jeblair triage new lane in storyboard22:31
SpamapSLots of New stuff22:31
jeblairand yeah, for me i've just been mostly head down trying to push stuff through :)22:32
jeblair#topic nodepool-drivers status22:33
*** openstack changes topic to "nodepool-drivers status (Meeting topic: zuul)"22:33
SpamapSI do think we may want to think about pruning the board down to just blockers for zuulv3 going into prod for infra22:33
jeblair#unfo22:33
jeblair#undo22:33
openstackRemoving item from minutes: #topic nodepool-drivers status22:33
jeblairSpamapS: yeah, we may be losing focus a bit there22:33
mordredSpamapS: ++22:33
jeblairmaybe a new lane or a new board?22:34
SpamapSI think a new tag and splitting of the things is in order22:34
* jeblair updates a task he's working on22:34
SpamapSzuulv30 maybe? like, zuulv3 is "zuulv3 running jobs in infra" and zuulv30 is "we finished the spec" ?22:35
*** leong has quit IRC22:35
jeblairSpamapS: can we boolean 'and' the tags?22:36
jeblairi can't remember if a board can do that22:36
jeblairzuulv3 and openstack-infra or something might be nice...22:37
*** neil__ has quit IRC22:37
SpamapSworth looking into22:37
jeblairanyway, whatever it takes, that sounds good to me.  :)22:37
fungii think as long as the query itself works you should be able to use it in an automatic worklist or board situation too22:37
jeblairok, let's move on to nodepool drivers22:37
jeblair#topic nodepool-drivers status22:37
*** openstack changes topic to "nodepool-drivers status (Meeting topic: zuul)"22:37
jeblairtristanC: i think you added this?22:38
jeblairtristanC: care to introduce it?22:38
tristanCindeed, well this is related to the nodepool-drivers spec22:38
tristanCi *tried* to hack something together to get static node support in nodepool22:38
* fungi notes that the spec in question has no assignees nor a storyboard story22:38
tristanCfungi: *cough* https://review.openstack.org/#/c/468623/ :)22:39
fungiawesome! rebasing my help-wanted change on top of that now22:39
jeblaircool22:39
tristanCso basically, if this what was expecting, then I could continue on this and start adding test22:40
ShrewstristanC: any chance you've been collaborating with smyers (also a RH person) on that? his team is very interested in that as well22:40
*** sshank has joined #openstack-meeting-alt22:40
jeblairwe can also add tristanC and smeyers if he's interested, (and maybe tobiash after he gets back?) to the spec as assignees too22:40
tristanCShrews: no, this is a one off change done over the week end, I can contact him for follow-ups22:41
jeblairfor my part, i very much want to look this over, but haven't had a chance yet.  i'm feeling some urgency to try to get some things out of the way that are blocking running zuulv3 in production (which should enable more folks to start working on other facets of using zuulv3 in openstack infra), so i've been trying to focus on that.22:41
clarkbI liked where the implementation of things started but then as the changes were added on top I felt that the driver api became very muddied. I think we just need to carefully write down some api contracts and stick with them until we decide they are wrong. (tristanC seemed to agree in review so not very controversial just wanted to point it out to bigger audience)22:42
*** Leo_ has quit IRC22:42
jeblairbasically, i'm trying to find a balance between staying focused on what we need to get into production asap, but i also don't want to block follow-on efforts for too long22:42
fungisounds like a reasonable approach22:42
SpamapSthat goes back to the /41 board22:43
SpamapSif we can push some of the things to "later", I think we're pretty close to saying zuulv3 does all the things infra needs22:43
pabelangerclarkb: I agree with your statement22:43
jeblairSpamapS: yeah, i feel like we ought to be able to clear my urgent list by the end of the week22:45
* mordred agrees with jeblair and SpamapS22:45
jeblairtristanC: can you give me till the end of the week to review your work so far?22:45
SpamapSjeblair: maybe if you could stop uncovering race conditions we could ship it. ;)22:45
fungiwe're going to need a bigger broom?22:45
jeblairtristanC: that might be a good opportunity to try to loop smeyers into the process as well22:46
tristanCclarkb: pabelanger: agreed, though this is quite difficult to do without disrupting too much the openstack driver22:46
*** gouthamr has quit IRC22:46
pabelangershould care be taken for linchpin driver when we are working on the nodepool driver? eg: some sort of ansible driver from nodepool?22:46
tristanCjeblair: sure thing!22:46
tristanCwell to be honest, I stoped when the static and oci driver started to work, I'm sure the interface can be improved22:47
Shrewspabelanger: yeah, i think linchpin is probably what smyers would be thinking of adding to it22:47
jeblairpossibly dumb question, but since folks are here, is "oci" something that can/should be handled by linchpin, or does it need its own driver?22:48
*** ihrachys has quit IRC22:48
pabelangerjeblair: that's one question I had, are we expecting people to write nodepool (python logic) drivers each time something new comes along or maybe abstract some of it via ansible22:49
jeblairi'm working from the assumption that linchpin would give us access to *many* clouds at small scale, and the reason we still need an openstack driver is for our large-scale needs22:49
*** gouthamr has joined #openstack-meeting-alt22:49
jeblairand then, if folks want to use, i dunno, aws at our scale, maybe they write an aws driver22:49
SpamapS+1 from me22:49
clarkbI think linchpin is largely new to the larger audience. If it uses ansible to provision instances in clouds I'd personally write a specific driver for $cloud just having tried to use ansible for that in the past22:50
clarkbyou run into a lot of fun problems like what I've hit with random networking stuff in say citycloud22:50
*** ansmith has joined #openstack-meeting-alt22:50
SpamapSmay as well libcloud, right?22:50
mordredjeblair: the way the oci driver tristanC put together opened up a way of thinking about that space I hadn't considered yet22:50
mordredSpamapS: that doens't work22:50
SpamapSwould that be a nice perfect full circle?22:50
mordred:)22:50
pabelangermy only concern for nodepool drivers, what is our plan for testing them. Ansible I think we have a good hold on now, but nodepool driver for aws?22:51
mordredjeblair: so I may have said linch-pin before, but there's some real nice possibilities with the simplicitiy of what's in that patch currently22:51
SpamapSpabelanger: there's a free tier22:51
jeblairpabelanger: i would definitely be looking for someone to sign up for ongoing test maintenance before we consider it.  :)22:51
mordredjeblair: oh - I mean "may have said linch-pin before for oci" - not talking in general22:51
tristanCpabelanger: it seems like what matter the most is a solid interface, then you can use what ever tool to do the implementation22:51
clarkbtristanC: ++22:52
jeblairpabelanger: but to bring that to the present...22:52
jeblairpabelanger, tristanC: how can we test an oci driver?22:52
clarkbjeblair: you have the nodepool driver test ssh into itselef and execute containers22:52
clarkbit should be straightfoward to do that22:53
mordredI think doing an linch-pin driver once we have a driver interface we're happy with, will open a door to folks experimenting. whether or not it winds up being a preferred way to get non-openstack resources or not will remain to be seen I'd guess22:53
mordredjeblair: yah. what clarkb said22:53
jeblairok22:53
mordredthe oci driver makes little oci processes running ssh - so it by-and-large looks a bunch like what we get from vms22:53
jeblairthanks for entertaining my questions even though i'm ignorant of the patch series contents.  that's some good background for me to have while i look at it.  :)22:54
tristanCjeblair: the oci driver I proposed needs ssh access to the "hypervisor", and the runc program installed22:54
pabelangerokay, we should be able to update nodepool dsvm for POC in that case22:54
tristanCand well i wrote it that way to check the initial driver interface could work for other things than openstack/static node22:55
*** kumarmn has joined #openstack-meeting-alt22:55
jeblairgoing from 1 to 3 drivers should give us a pretty good triangulation on the api.  :)22:56
*** neil__ has joined #openstack-meeting-alt22:56
pabelangerOh, we could do a multinode job then for oci test22:56
mordredyah- at first I was like "2 drivers" - but then it was helpful for looking at the api - yah22:56
*** slaweq has joined #openstack-meeting-alt22:56
clarkbpabelanger: multinode not required (nor desireable I don't think)22:56
clarkbpabelanger: single node will exercise all of the code just as well as multinode22:56
pabelangerclarkb: agree22:57
fungiyeah, trying to work out where multinode testing would even come into the picture22:57
fungiseems unwarranted22:57
fungiunless we somehow exceed the amount of resources we have available on one node22:57
fungiwhich i think is extremely unlikely22:58
pabelangerthe SSH to hypervisor part made me think about multi node22:58
pabelangerhowever, loopback should also work22:58
jeblairthis has been a good discussion23:00
jeblairand we're out of time23:00
jeblairtristanC: thanks!23:00
jeblairand everyone else, thanks too23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Mon Jun  5 23:00:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-05-22.03.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-05-22.03.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-05-22.03.log.html23:00
*** Shrews has left #openstack-meeting-alt23:00
tristanCjeblair: you're welcome!23:00
*** slaweq has quit IRC23:01
*** kumarmn has quit IRC23:01
pabelangertristanC: thanks for the patches23:02
jlkoh noes I missed the meeting!  I had to go pick up my kiddo :(23:06
*** tonanhngo has quit IRC23:14
*** neil__ has quit IRC23:14
*** marst has joined #openstack-meeting-alt23:25
*** sdague has quit IRC23:26
*** oidgar has joined #openstack-meeting-alt23:27
*** tobberydberg has joined #openstack-meeting-alt23:30
*** jamielennox is now known as jamielennox|away23:30
*** tobberydberg has quit IRC23:34
*** oidgar has quit IRC23:37
*** gouthamr has quit IRC23:43
*** jamielennox|away is now known as jamielennox23:46
*** sshank has quit IRC23:50
*** gouthamr has joined #openstack-meeting-alt23:52
*** baoli has joined #openstack-meeting-alt23:55
*** hongbin has quit IRC23:56
*** slaweq has joined #openstack-meeting-alt23:57

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