Monday, 2017-07-10

*** ircuser-1 has quit IRC00:08
*** diablo_rojo has quit IRC00:18
*** funzo_ has quit IRC00:39
*** zhurong has joined #openstack-meeting-alt00:48
*** tovin07_ has joined #openstack-meeting-alt00:52
*** trungnv has quit IRC00:53
*** trungnv has joined #openstack-meeting-alt00:57
*** cloudrancher has quit IRC00:57
*** cloudrancher has joined #openstack-meeting-alt00:58
*** ijw has joined #openstack-meeting-alt00:59
*** gouthamr has quit IRC01:13
*** achadha has joined #openstack-meeting-alt01:22
*** achadha_ has joined #openstack-meeting-alt01:23
*** achadha has quit IRC01:26
*** julim has joined #openstack-meeting-alt01:27
*** ijw_ has joined #openstack-meeting-alt01:28
*** ijw has quit IRC01:31
*** ijw has joined #openstack-meeting-alt01:32
*** dave-mccowan has joined #openstack-meeting-alt01:33
*** ijw_ has quit IRC01:36
*** hongbin has joined #openstack-meeting-alt01:36
*** fzdarsky_ has joined #openstack-meeting-alt01:53
*** fzdarsky__ has quit IRC01:56
*** achadha_ has quit IRC02:05
*** ijw has quit IRC02:12
*** julim has quit IRC02:17
*** caowei has joined #openstack-meeting-alt02:20
*** baoli has joined #openstack-meeting-alt02:21
*** baoli has quit IRC02:28
*** ijw has joined #openstack-meeting-alt02:36
*** ijw_ has joined #openstack-meeting-alt02:37
*** ijw has quit IRC02:41
*** ijw__ has joined #openstack-meeting-alt02:41
*** zhurong has quit IRC02:43
*** ijw_ has quit IRC02:44
*** esikachev has joined #openstack-meeting-alt02:46
*** ijw__ has quit IRC02:46
*** esikachev has quit IRC02:50
*** ijw has joined #openstack-meeting-alt02:56
*** ijw has quit IRC03:01
*** julim has joined #openstack-meeting-alt03:05
*** julim has quit IRC03:09
*** gcb has joined #openstack-meeting-alt03:12
*** reedip has quit IRC03:13
*** reedip has joined #openstack-meeting-alt03:25
*** ijw has joined #openstack-meeting-alt03:41
*** yamamoto has joined #openstack-meeting-alt03:47
*** slaweq has joined #openstack-meeting-alt03:47
*** slaweq has quit IRC03:52
*** hongbin has quit IRC03:58
*** julim has joined #openstack-meeting-alt03:59
*** dave-mccowan has quit IRC04:05
*** achadha has joined #openstack-meeting-alt04:06
*** dsariel has joined #openstack-meeting-alt04:06
*** achadha has quit IRC04:11
*** ijw has quit IRC04:20
*** sridharg has joined #openstack-meeting-alt04:22
*** gcb has quit IRC04:30
*** arnewiebalck_ has joined #openstack-meeting-alt04:45
*** zhurong has joined #openstack-meeting-alt04:47
*** trinaths has joined #openstack-meeting-alt04:48
*** arnewiebalck_ has quit IRC05:00
*** arnewiebalck_ has joined #openstack-meeting-alt05:02
*** trinaths has quit IRC05:04
*** trinaths has joined #openstack-meeting-alt05:08
*** hiro-kobayashi has joined #openstack-meeting-alt05:08
*** janki has joined #openstack-meeting-alt05:08
*** achadha has joined #openstack-meeting-alt05:08
*** achadha has quit IRC05:10
*** achadha has joined #openstack-meeting-alt05:10
*** achadha has joined #openstack-meeting-alt05:11
*** esikachev has joined #openstack-meeting-alt05:17
*** skramaja has joined #openstack-meeting-alt05:20
*** pgadiya has joined #openstack-meeting-alt05:28
*** tobberydberg has joined #openstack-meeting-alt05:29
*** mjura has joined #openstack-meeting-alt05:33
*** marios has joined #openstack-meeting-alt05:37
*** jbadiapa has joined #openstack-meeting-alt05:43
*** achadha has quit IRC05:50
*** achadha has joined #openstack-meeting-alt05:51
*** achadha has quit IRC05:55
*** kobis has joined #openstack-meeting-alt06:06
*** jprovazn has joined #openstack-meeting-alt06:07
*** dfflanders has joined #openstack-meeting-alt06:09
*** kzaitsev_ws has joined #openstack-meeting-alt06:17
*** andreas_s has joined #openstack-meeting-alt06:20
*** vds has joined #openstack-meeting-alt06:22
*** jtomasek has joined #openstack-meeting-alt06:26
*** alexchadin has joined #openstack-meeting-alt06:27
*** dfflanders has quit IRC06:29
*** rarcea has joined #openstack-meeting-alt06:31
*** matbu has quit IRC06:32
*** matbu has joined #openstack-meeting-alt06:35
*** lpetrut has joined #openstack-meeting-alt06:37
*** janki has quit IRC06:38
*** lpetrut has quit IRC06:43
*** coolsvap has joined #openstack-meeting-alt06:47
*** rcernin has joined #openstack-meeting-alt06:47
*** belmoreira has joined #openstack-meeting-alt06:54
*** ccamacho has joined #openstack-meeting-alt07:02
*** fzdarsky has joined #openstack-meeting-alt07:05
*** amotoki_away is now known as amotoki07:11
*** harlowja has quit IRC07:11
*** bogdando has joined #openstack-meeting-alt07:23
*** hiro-kobayashi has quit IRC07:23
*** oidgar has joined #openstack-meeting-alt07:33
*** rarcea has quit IRC07:34
*** tesseract has joined #openstack-meeting-alt07:36
*** trungnv has quit IRC07:36
*** trungnv has joined #openstack-meeting-alt07:39
*** fzdarsky has quit IRC07:44
*** trungnv has quit IRC07:47
*** rarcea has joined #openstack-meeting-alt07:47
*** sambetts is now known as sambetts|afk07:47
*** dsariel has quit IRC07:48
*** radeks has joined #openstack-meeting-alt07:56
*** sambetts|afk is now known as sambetts07:57
*** _pewp_ has quit IRC08:10
*** fzdarsky_ has quit IRC08:11
*** dizquierdo has joined #openstack-meeting-alt08:13
*** _pewp_ has joined #openstack-meeting-alt08:14
*** fzdarsky has joined #openstack-meeting-alt08:26
*** hieulq has quit IRC08:39
*** daidv has quit IRC08:39
*** tovin07_ has quit IRC08:40
*** dizquierdo has quit IRC08:43
*** radeks has quit IRC08:47
*** vipul has joined #openstack-meeting-alt08:47
*** ralonsoh has joined #openstack-meeting-alt08:51
*** anilvenkata has joined #openstack-meeting-alt08:51
*** kobis has quit IRC08:54
*** felipemonteiro has joined #openstack-meeting-alt08:56
*** kobis has joined #openstack-meeting-alt08:58
*** slunkad has joined #openstack-meeting-alt08:59
*** felipemonteiro has quit IRC09:01
*** radeks has joined #openstack-meeting-alt09:02
*** dsariel has joined #openstack-meeting-alt09:04
*** esikachev has quit IRC09:04
*** lpetrut has joined #openstack-meeting-alt09:07
*** esikachev has joined #openstack-meeting-alt09:09
*** trungnv has joined #openstack-meeting-alt09:14
*** hieulq has joined #openstack-meeting-alt09:15
*** daidv has joined #openstack-meeting-alt09:16
*** daidv has quit IRC09:21
*** dizquierdo has joined #openstack-meeting-alt09:28
*** daidv has joined #openstack-meeting-alt09:34
*** karthiks has joined #openstack-meeting-alt09:38
*** vipul has quit IRC09:38
*** dalgaaf has quit IRC09:46
*** vipul has joined #openstack-meeting-alt09:47
*** dalgaaf has joined #openstack-meeting-alt09:48
*** caowei has quit IRC10:08
*** achadha has joined #openstack-meeting-alt10:14
*** radeks has quit IRC10:18
*** achadha has quit IRC10:18
*** sdague has joined #openstack-meeting-alt10:21
*** arnewiebalck_ has quit IRC10:27
*** fzdarsky has quit IRC10:30
*** sridharg has quit IRC10:34
*** hieulq has quit IRC10:57
*** pbourke has quit IRC10:57
*** ansmith has quit IRC10:58
*** daidv has quit IRC10:58
*** pbourke has joined #openstack-meeting-alt10:59
*** jkilpatr has joined #openstack-meeting-alt11:01
*** alexchadin has quit IRC11:10
*** daidv has joined #openstack-meeting-alt11:12
*** hieulq has joined #openstack-meeting-alt11:12
*** shukixxxx has joined #openstack-meeting-alt11:14
*** shukixxxx has quit IRC11:14
*** julim has quit IRC11:30
*** tobberyd_ has joined #openstack-meeting-alt11:31
*** shuyingya has joined #openstack-meeting-alt11:34
*** tobberydberg has quit IRC11:35
*** tobberyd_ has quit IRC11:36
*** trinaths has left #openstack-meeting-alt11:40
*** danpawlik has quit IRC11:48
*** danpawlik has joined #openstack-meeting-alt11:54
*** dave-mccowan has joined #openstack-meeting-alt11:55
*** janki has joined #openstack-meeting-alt11:56
*** jkilpatr has quit IRC11:57
*** pradk has joined #openstack-meeting-alt12:02
*** trungnv has quit IRC12:04
*** hieulq has quit IRC12:04
*** daidv has quit IRC12:04
*** d0ugal has joined #openstack-meeting-alt12:04
*** d0ugal has quit IRC12:04
*** d0ugal has joined #openstack-meeting-alt12:04
*** jcoufal has joined #openstack-meeting-alt12:06
*** shu-mutou is now known as shu-mutou-AWAY12:07
*** dprince has joined #openstack-meeting-alt12:07
*** fzdarsky has joined #openstack-meeting-alt12:07
*** d0ugal has quit IRC12:12
*** jprovazn has quit IRC12:18
*** krtaylor_ has joined #openstack-meeting-alt12:19
*** daidv has joined #openstack-meeting-alt12:19
*** trungnv has joined #openstack-meeting-alt12:19
*** hieulq has joined #openstack-meeting-alt12:19
*** krtaylor has quit IRC12:20
*** cartik has joined #openstack-meeting-alt12:22
*** baoli has joined #openstack-meeting-alt12:25
*** alexchadin has joined #openstack-meeting-alt12:25
*** baoli has quit IRC12:27
*** baoli has joined #openstack-meeting-alt12:28
*** jkilpatr has joined #openstack-meeting-alt12:29
*** cartik has quit IRC12:30
*** shuyingya has quit IRC12:33
*** esikachev has quit IRC12:36
*** zhurong has quit IRC12:36
*** sambetts has quit IRC12:38
*** jprovazn has joined #openstack-meeting-alt12:38
*** itamaro has quit IRC12:41
*** sambetts has joined #openstack-meeting-alt12:42
*** ansmith has joined #openstack-meeting-alt12:44
*** jaypipes has joined #openstack-meeting-alt12:46
*** Guest9640 is now known as beagles12:47
*** sridharg has joined #openstack-meeting-alt12:51
*** d0ugal has joined #openstack-meeting-alt12:54
*** d0ugal has quit IRC12:54
*** d0ugal has joined #openstack-meeting-alt12:54
*** d0ugal has quit IRC12:59
*** baoli has quit IRC13:00
*** MarkBaker has quit IRC13:00
*** funzo has joined #openstack-meeting-alt13:01
*** MarkBaker has joined #openstack-meeting-alt13:02
*** oidgar has quit IRC13:04
*** egallen has joined #openstack-meeting-alt13:14
*** trungnv has quit IRC13:16
*** hieulq has quit IRC13:16
*** daidv has quit IRC13:17
*** oidgar has joined #openstack-meeting-alt13:19
*** shuyingya has joined #openstack-meeting-alt13:19
*** shuyingya has quit IRC13:24
*** dustins has joined #openstack-meeting-alt13:25
*** sdague has quit IRC13:30
*** sshnaidm is now known as sshnaidm|mtg13:30
*** gcb has joined #openstack-meeting-alt13:31
*** belmorei_ has joined #openstack-meeting-alt13:32
*** belmoreira has quit IRC13:32
*** sdague has joined #openstack-meeting-alt13:33
*** arnewiebalck_ has joined #openstack-meeting-alt13:33
*** felipemonteiro has joined #openstack-meeting-alt13:34
*** xyang1 has joined #openstack-meeting-alt13:34
*** felipemonteiro_ has joined #openstack-meeting-alt13:36
*** hieulq has joined #openstack-meeting-alt13:36
*** daidv has joined #openstack-meeting-alt13:36
*** trungnv has joined #openstack-meeting-alt13:36
*** esikachev has joined #openstack-meeting-alt13:36
*** felipemonteiro has quit IRC13:39
*** sridharg has quit IRC13:42
*** sridharg has joined #openstack-meeting-alt13:44
*** sridharg has quit IRC13:44
*** sridharg has joined #openstack-meeting-alt13:46
*** sridharg has quit IRC13:47
*** sridharg has joined #openstack-meeting-alt13:49
*** sridharg has quit IRC13:49
*** dtantsur has joined #openstack-meeting-alt13:50
*** sridharg has joined #openstack-meeting-alt13:50
*** sridharg has quit IRC13:50
*** sridharg has joined #openstack-meeting-alt13:51
*** sridharg has quit IRC13:52
*** sridharg has joined #openstack-meeting-alt13:54
*** cdent has joined #openstack-meeting-alt13:59
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Jul 10 14:00:35 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
edleafeGood UGT morning!14:00
edleafeWho's here?14:00
*** pbourke has quit IRC14:01
*** anilvenkata has quit IRC14:01
dtantsuro/14:01
cdento/14:01
*** arnewiebalck_ has quit IRC14:02
*** skramaja has quit IRC14:02
edleafejaypipes, alex_xu, bauzas - around?14:02
alex_xuo/14:02
jaypipesyuppers.14:02
*** superdan is now known as dansmith14:02
edleafeGuess we'll start14:03
edleafe#topic Specs and Reviews14:03
*** openstack changes topic to "Specs and Reviews (Meeting topic: nova_scheduler)"14:03
*** arnewiebalck_ has joined #openstack-meeting-alt14:03
edleafeThere is a new spec14:03
edleafeor rather an amendment to one14:03
edleafe#link Amend spec for Custom Resource Classes in Flavors: https://review.openstack.org/#/c/481748/14:03
edleafeThis was going to be done by jroll14:04
edleafeLooks like it's now on me14:04
cdenti can probably be your off hours buddy on that?14:04
jaypipesedleafe: didn't you already have code for that?14:04
jaypipesI thought I remember reviewing that already?14:04
edleafejaypipes: for my half, yes14:04
edleafejroll was going to handle what needed to happen for migration14:05
edleafeso that when Pike starts up, the correct resources are allocated14:05
jaypipesah14:05
*** mkucia has joined #openstack-meeting-alt14:05
dtantsurFYI I've tried it with a devstack change, and still cannot make the tests pass: https://review.openstack.org/#/c/476968/. It may be my mistake, of course, or it may be this missing migration14:05
*** baoli has joined #openstack-meeting-alt14:05
edleafedtantsur: tried what?14:05
dtantsuredleafe: sorry :) using resource classes for scheduling ironic instances14:06
edleafeOK, I haven't looked at that patch.14:06
*** jkilpatr has quit IRC14:06
edleafeI'll take a look at it later14:06
jaypipesI will as well.14:07
jaypipesboth the spec and the patch14:07
*** gyee has joined #openstack-meeting-alt14:07
edleafejaypipes: do we have the code merged to use the custom RC?14:08
edleafeI know it was mine, but I thought there was another piece needed14:08
jaypipesedleafe: oh yes, since Ocata.14:08
*** kzaitsev_ has joined #openstack-meeting-alt14:08
jaypipesedleafe: oh, sorry, you're talking about the flavor thing14:08
jaypipesedleafe: not sure on the flavor thing... need to check14:09
edleafejaypipes: yeah, the patch I wrote grabbed the custom RC from extra_specs14:09
edleafeand added it to the 'resources' dict.14:09
jaypipesright14:09
*** kzaitsev_ws has quit IRC14:10
edleafeWell, I'll be digging into what's needed for the migration. And I'd be happy to have cdent's help (and anyone else's)14:10
*** gouthamr has joined #openstack-meeting-alt14:10
bauzasoh snap, forgot meeting \o14:11
cdentyou know where to find me and I’ll look for you14:11
* edleafe waves to bauzas 14:11
jaypipesstalker alert!14:11
* bauzas bows to edleafe14:11
edleafe:)14:11
edleafeOK, next up...14:11
edleafe#link Claims in the Scheduler: https://review.openstack.org/#/c/476632/14:11
edleafeThe first part is +W'd, so this is the only active one14:12
edleafejaypipes: anything to note?14:12
*** kobis has quit IRC14:12
jaypipesedleafe: I'll respond to mriedem's comments on there.14:13
edleafeok14:13
jaypipesedleafe: did you have further comments on it?14:13
*** janki has quit IRC14:13
bauzastechnically, we have not yet merged the bottom patch but okay14:13
*** hongbin has joined #openstack-meeting-alt14:14
edleafejaypipes: I haven't looked at it since Friday morning, so when I do I'll respond on the patch14:14
jaypipesk14:14
edleafeOh, I almost forgot to note:14:14
edleafe#link Devstack to use resource classes by default https://review.openstack.org/#/c/476968/14:15
* edleafe wants to keep the record up-to-date14:15
edleafeMoving on...14:15
edleafe#link Nested Resource Providers: series starting with https://review.openstack.org/#/c/470575/14:15
edleafeThis is still pretty much on hold, right?14:15
*** mriedem has joined #openstack-meeting-alt14:16
*** oidgar has quit IRC14:16
* edleafe pokes jaypipes 14:17
jaypipesedleafe: yeah14:17
jaypipesedleafe: it will pick up steam once claims are in.14:17
edleafeok, just making sure14:17
* mriedem joins late14:17
jaypipesedleafe: and I add some more functional testing around the scheduler -> conductor -> compute interactions.14:17
edleafeFinally...14:17
edleafe#link Placement api-ref docs https://review.openstack.org/#/q/topic:cd/placement-api-ref+status:open14:17
edleafejaypipes: let us know how we can help (besides reviews, of course)14:18
*** sshnaidm|mtg is now known as sshnaidm14:18
edleafeAnything else for specs/reviews?14:19
alex_xuthe traits support in the allocation candidates are submitted14:19
alex_xu#link the first patch https://review.openstack.org/47846414:19
alex_xu#link the last one https://review.openstack.org/#/c/479776/14:20
jaypipesmriedem: responded to your comments on ^14:21
jaypipesmriedem: sorry, on https://review.openstack.org/#/c/476632/14:21
edleafeOK, thanks alex_xu - added to my review list14:21
alex_xuedleafe: I also remember there is one patch from you for 'GET /resources' with traits14:21
alex_xuedleafe: thanks14:21
*** beekneemech is now known as bnemec14:22
mriedemjaypipes: ok, i guess i'm missing something then because when originally planning this all out,14:22
mriedemi thought we were going for some minimum nova-compute service version check before doing allocations in the scheduler14:22
mriedemsuch that we would no longer do the claim in the compute14:22
mriedemonce we do the allocation in the scheduler, the claim in the compute is at best redundant but not a problem,14:23
mriedemat worst the claim fails because of something like the overhead calculation14:24
*** klipka has joined #openstack-meeting-alt14:24
mriedemor pci or whatever we don14:24
mriedem*don't handle yet in the scheduler14:24
*** alexchadin has quit IRC14:25
jaypipesmriedem: we can do the *removal of the claim on the compute node* once we know all computes are upgraded. but that's a different patch to what's up there now, which just does the claim in the scheduler.14:25
*** pgadiya has quit IRC14:25
*** kzaitsev_ has quit IRC14:27
*** kzaitsev_ has joined #openstack-meeting-alt14:27
edleafejaypipes: so if the scheduler starts doing claims, will that cause a problem with older computes?14:27
jaypipesedleafe: no.14:27
edleafeOr will the compute claim just be a duplicate14:28
mriedemit's a duplicate14:28
jaypipesedleafe: not even duplicate. it just won't be done.14:28
*** shuyingya has joined #openstack-meeting-alt14:28
mriedemwhat do you mean it won't be done?14:28
jaypipesedleafe: b/c the report client only writes allocations that are not already existing.14:28
edleafejaypipes: even on an old compute?14:28
jaypipesedleafe: yes. on ocata computes, we already do this.14:28
mriedemwriting the allocations is part of the claim process that happens on the compute *today* yes?14:29
edleafejaypipes: ok, I'll have to re-read that code14:29
jaypipesmriedem: yes, and the periodic audit job.14:29
mriedembut before we have the RT call the report client to write allocations, we're doing pci and overhead calculations14:29
jaypipesmriedem: correct.14:29
mriedemso we are still going to go through the same old claim process14:29
*** zhurong has joined #openstack-meeting-alt14:29
mriedemwhich may fail, and trigger a retry14:29
*** oidgar has joined #openstack-meeting-alt14:30
jaypipesmriedem: correct. if that happens, the allocations are deleted from the placement API.14:30
mriedemwhere?14:30
jaypipesin the periodic audit job.14:30
jaypipesupdate_available_resource()14:30
jaypipeswill pick that uyp.14:30
*** cartik has joined #openstack-meeting-alt14:30
mriedemwhen does the alternates stuff for retries come in?14:31
mriedemon top of https://review.openstack.org/#/c/476632/ ?14:31
cdenteven if something writes allocations for the same instance multiple times, it is a replace action14:31
cdentPUT /allocations/consumer_uuid is replace14:31
jaypipesmriedem: yes, the alternatives stuff needs to come after this.14:32
jaypipescdent: right, but we look up existing allocations first and do nothing if nothing changed: https://github.com/openstack/nova/blob/master/nova/scheduler/client/report.py#L86314:32
cdentjaypipes: yeah, I know, I was just saying that’s it’s safe even if that wasn’t happening14:33
jaypipesgotcha14:33
mriedemok so if we leave the allocation cleanup to the periodic task,14:33
mriedemthere is a chance you could "fill up" allocations for a compute node after a couple of failed attempts within a minute or something,14:33
jaypipesmriedem: yep.14:34
*** kzaitsev_68 has joined #openstack-meeting-alt14:34
mriedemwhich if you've got a lot of compute nodes and a busy cloud, should be ok...14:34
jaypipesmriedem: and I wrote in that comment that I could try and "undo" successful allocations in the scheduler _claim_resources() method, but that meh, eventually it'll get cleaned up by the periodic audit task on the compute14:34
*** dizquierdo has quit IRC14:34
*** kzaitsev_ has quit IRC14:35
mriedemi have a bad feeling about relying on that14:35
mriedemespecially when someone does nova boot with min-count 10014:35
mriedeme.g. you get to 99 and novalidhost, and we don't cleanup the allocations for the first 9814:36
jaypipesmriedem: I'm happy to take a go at that cleanup if you'd like.14:37
*** shuyingya has quit IRC14:37
dansmiththe retry part of conductor could accelerate that14:37
jaypipesmriedem: just say the word.14:37
mriedemwill needing to undo allocations in the scheduler slow it down for other incoming requests? we're still single worker right?14:37
mriedemdansmith: in this case we wouldn't get to conductor,14:37
dansmithmriedem: single worker but we yield when making a call to placement14:37
mriedemit's novalidhost14:37
jaypipesmriedem: there's no reason at all why the scheduler needs to be single process.14:37
dansmithmriedem: you mean for a failed boot that never gets retried?14:38
mriedemdansmith: yes14:38
mriedemscheduler raises NoValidHost14:38
*** kzaitsev_ has joined #openstack-meeting-alt14:39
dansmithokay I'm confused about why we'd still have stale allocations in that case14:39
dansmithbut we can discuss outside of the meeting14:39
jaypipesdansmith: he's talking about this code:14:39
mriedemhttps://review.openstack.org/#/c/476632/19/nova/scheduler/manager.py@12814:39
jaypipesya14:39
jaypipesdanke mriedem14:39
dansmithoh I see, just in the n-instances case, I gotca14:40
*** kzaitsev_68 has quit IRC14:40
jaypipesmriedem: like I said, I'm happy to give a go at cleaning up already-successful allocations in that block.14:40
jaypipesmriedem: just say the word.14:40
dansmithcleanup there would be easy I think, yeah14:40
mriedemin general i think we should cleanup when we can14:40
jaypipesyeah, I'll just keep track of the instance UUIDs that succeeded.14:40
dansmithyep14:41
mriedemincluding when we retry from the comptue to the conductor with the alternates14:41
jaypipesmriedem: well, and we'll eventually want to be retrying *within* the scheduler.14:41
dansmithmriedem: yeah that's the case I was thinking of and have always described it as "cleanup the old, claim the next alternate"14:41
jaypipesbut whatevs, I hear ya, I'll fix that section up.14:41
*** belmorei_ has quit IRC14:41
dansmithjaypipes: no, we can't retry in the scheduler once we've failed on the compute node14:41
*** cloudrancher has quit IRC14:41
jaypipesdansmith: retry on the allocation_request...14:41
mriedemi think jay is talking about pre-compute14:42
mriedemyeah14:42
dansmiththat, yes14:42
jaypipesright.14:42
dansmithfigured he meant: [07:41:04]  <mriedem>including when we retry from the comptue to the conductor with the alternates14:42
*** cloudrancher has joined #openstack-meeting-alt14:42
jaypipesyeah, sorry, no I mean the allocation candidates thing.14:42
mriedemretrying within the scheduler is the whole reason we decided to do it in the scheduler and not conductor14:42
dansmithack14:42
mriedemso yeah we should do that :)14:42
edleafewell, that's not really a retry when the scheduler can't claim14:42
dansmithyeah14:42
edleafejust validating the host14:42
*** arnewiebalck_ has quit IRC14:42
jaypipesanyway, mriedem, besides the cleaning up successful allocations in that failure block, is there anything big you want changed on the patch? if not, I'll go and work on this.14:43
mriedemjaypipes: i think you already replied on my other things14:43
jaypipesthe other little nits I'll get, yep14:43
edleafeLet's continue this in -nova14:43
mriedembtw, we create the allocations after the filters right?14:43
edleafe#topic Bugs14:43
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:43
edleafe#undo14:43
openstackRemoving item from minutes: #topic Bugs14:43
jaypipesmriedem: yes.14:44
jaypipesmriedem: and the weighers.14:44
bauzassorry was a bit afk14:44
bauzasbut I have a point about the above14:44
edleafeLet's keep it quick14:44
*** kzaitsev_ has quit IRC14:45
*** annegentle has joined #openstack-meeting-alt14:45
bauzasgiven the time we still have for Pike, do folks agree with me about possibly not having the conductor passing alternatives for Pike ?14:45
*** kzaitsev_ has joined #openstack-meeting-alt14:45
dansmithno I don't agree14:45
jaypipesbauzas: no, I think it's absoltelyuy doable for Pike to have the alternatives done.14:45
edleafeme too14:46
bauzaswould it be a problem not having that for Pike ?14:46
jaypipesbauzas: I think we can have claims merged and ready by Wednesday and patches up for alternatives by EOW14:46
bauzaswhile I agree with all of us about why it's important, I'm just trying to be pragramatic14:46
dansmithbauzas: yes, without that we're toast for the proper cellsv2 arrangement14:46
*** rarcea has quit IRC14:46
cdentyeah, we pretty much have to do it14:47
dansmithbauzas: we can be pragmatic when we're out of time, but we're not there, IMHO14:47
bauzasokay14:47
jaypipeswe need to get alternatives done, flavors for resource classes complete, and claims done.14:47
dansmithack14:47
jaypipesthose are absolutes for Pike.14:47
*** kobis has joined #openstack-meeting-alt14:47
jaypipesnested stuff is nice to have, and we've made a bit of progress on it already.14:47
bauzasand shared-RP, and custom-RP? :)14:47
bauzasyeah, that's my point14:47
mriedemshared is done14:47
bauzaswell, agreed14:48
mriedemallocation candidates takes care of shared, at least for disk14:48
*** chyka has joined #openstack-meeting-alt14:48
edleafemriedem: well, not completely done14:48
edleafemriedem: we don't handle complex RPs14:48
*** priteau has joined #openstack-meeting-alt14:48
jaypipesmriedem: well, almost... still need a way to trigger the compute node to not want to claim the disk when shared provider is used...14:48
bauzasokay, tbc, I don't disagree with the direction, I'm just trying to see what is left for Pike14:48
edleafemriedem: like a compute with both local and shared14:48
* alex_xu puts the trait's priority low, focus on review the priority stuff14:48
jaypipesmriedem: but that is a short patch that all the plumbing is ready for.14:48
*** chyka has quit IRC14:48
jaypipesedleafe: we don't *currently* handle that.14:49
jaypipesedleafe: so that's not something I'm worried about yet14:49
edleafejaypipes: exactly - which was going to be the subject I wanted to discuss in Opens14:49
jaypipeskk14:49
*** chyka has joined #openstack-meeting-alt14:49
edleafebut we are quickly running out of time14:49
jaypipesthere is always #openstack-nova, ed :)14:49
* edleafe blinks14:50
edleafeReally??14:50
edleafe:)14:50
bauzasanyway14:50
bauzasI don't want to confuse people14:50
edleafeLet's try to move on again...14:50
edleafe#topic Bugs14:50
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:50
edleafe#link https://bugs.launchpad.net/nova/+bugs?field.tag=placement14:50
edleafeOnly one new bug:14:50
edleafe#link The AllocationCandidates.get_by_filters returned wrong combination of AllocationRequests https://bugs.launchpad.net/nova/+bug/170242014:50
openstackLaunchpad bug 1702420 in OpenStack Compute (nova) "The AllocationCandidates.get_by_filters returned wrong combination of AllocationRequests" [High,In progress] - Assigned to Alex Xu (xuhj)14:51
*** hieulq has quit IRC14:51
edleafealex_xu reported this one, and is working on it.14:51
*** trungnv has quit IRC14:51
*** daidv has quit IRC14:51
edleafealex_xu: any problems with that?14:51
alex_xuedleafe: no, just waiting for review14:51
edleafegreat14:51
edleafeAnything else on bugs?14:51
edleafe#topic Open Discussion14:52
*** openstack changes topic to "Open Discussion (Meeting topic: nova_scheduler)"14:52
edleafeI had one concern: the change to return a list of HostState objects from the scheduler driver to the manager. IMO, we really need the host to be associated with its Allocation object so that a proper claim can be made. The current design just returns hosts, and then picks the first allocation that matches the hosts RP id.14:52
edleafeIn the case of a host that has both local and shared storage, there will be two allocation candidates for that host. The current design will choose one of those more or less at random.14:52
edleafeJay has said that when we begin to support such complex RPs, we will make the change then. Since we are changing the interface between manager and driver now, wouldn't it be best to do it so that when we add complex RPs, we don't have to change it again?14:52
dansmithif you haven't requested a trait of shared or not-shared, then at-random is fine right?14:53
*** fnaval has joined #openstack-meeting-alt14:53
edleafedansmith: in that case, yes14:53
edleafebut in the case of local vs. public net for PCI, probably not14:53
jaypipesto be clear, the code just selects the first allocation request containing the host's RP ID. so yeah, there's no order to it.14:54
*** kzaitsev_ has quit IRC14:54
mkuciaHi. I am wondering how the driver will be handling ResourceProviders? Will there be a dedicated class (ResourceProviderDriver) for each provider type?14:54
dansmithin the case of network, if your flavors say "give me a pci net device but I don't care which kind" then you're asking for at random, no?14:54
edleafejaypipes: you can keep the randomness for now14:54
dansmithagree it would be a dumb thing to do, but..14:54
edleafejaypipes: I was concerned about having to change the interface yet again in Queens14:55
edleafedansmith: again, in that particular case, you would be correct14:55
edleafebut that's not my point14:55
jaypipesedleafe: this is an internal interface. I'm not concerned at all about that.14:55
mriedemme neither14:55
mriedemand this is no worse than what we have today right?14:55
jaypipesedleafe: I mean, we need to change the RPC interface for alternatives support, and that's major surgery. This stuff was just a botox injection compared to that.14:56
mriedemi'm more concerned about the <3 weeks to FF14:56
dansmithmriedem: ++14:56
bauzasbotox, heh14:56
edleafeok, fine.14:56
bauzasmriedem: me too, hence my previous point14:56
jaypipesedleafe: you agree the RPC change is much more yes?14:56
edleafeIt just wasn't what we had originally discussed, and it raised a flag for me14:56
*** zhurong has quit IRC14:56
edleafejaypipes: of course14:56
jaypipesunderstod.14:56
jaypipesunderstood, edleafe and I appreciate your concerns on it. As you saw, I went through a bunch of iterations on thinking about those internal changes14:57
*** rcernin has quit IRC14:57
jaypipesedleafe: but returning the HostState objects instead of the host,node tuples allowed us to isolate pretty effectively the claims code in the manager without affecting the drivers at all.14:57
edleafeAs long as we all realize that this will have to change yet again in Queens, sure14:58
cdentchange is and always will be inevitable14:58
jaypipesedleafe: certainly it may. but again, I'm less concerned about internal interfaces than the RPC ones.14:58
edleafehow trite14:58
* cdent is trite14:58
cdentalways has been, always will be14:58
*** rarcea has joined #openstack-meeting-alt14:59
edleafejaypipes: I was more concerned about saying we will do X, and finding Y14:59
bauzas1 min left14:59
*** yamahata has quit IRC14:59
edleafeAs long as we get to X eventually14:59
edleafeThat's it - thanks everyone!15:00
edleafe#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Jul 10 15:00:07 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-07-10-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-07-10-14.00.txt15:00
*** dtantsur has left #openstack-meeting-alt15:00
cdentthanks edleafe15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-07-10-14.00.log.html15:00
*** yamahata has joined #openstack-meeting-alt15:00
*** mkucia has left #openstack-meeting-alt15:00
*** mjura has quit IRC15:00
*** cdent has quit IRC15:00
*** oidgar has quit IRC15:02
*** mriedem has left #openstack-meeting-alt15:03
*** achadha has joined #openstack-meeting-alt15:03
*** achadha has quit IRC15:04
*** ircuser-1 has joined #openstack-meeting-alt15:05
*** jkilpatr has joined #openstack-meeting-alt15:06
*** cartik has quit IRC15:06
*** diablo_rojo has joined #openstack-meeting-alt15:08
*** trungnv has joined #openstack-meeting-alt15:08
*** daidv has joined #openstack-meeting-alt15:08
*** hieulq has joined #openstack-meeting-alt15:09
*** dtrainor has joined #openstack-meeting-alt15:09
*** dtrainor has quit IRC15:09
*** dtrainor has joined #openstack-meeting-alt15:10
*** fzdarsky is now known as fzdarsky|afk15:11
*** cloudrancher has quit IRC15:12
*** cloudrancher has joined #openstack-meeting-alt15:12
*** klipka has left #openstack-meeting-alt15:16
*** lkoranda has quit IRC15:19
*** oidgar has joined #openstack-meeting-alt15:20
*** d0ugal has joined #openstack-meeting-alt15:20
*** d0ugal has quit IRC15:20
*** d0ugal has joined #openstack-meeting-alt15:20
*** markstur has joined #openstack-meeting-alt15:20
*** dizquierdo has joined #openstack-meeting-alt15:23
*** lkoranda has joined #openstack-meeting-alt15:23
*** ccamacho has quit IRC15:27
*** trungnv has quit IRC15:28
*** hieulq has quit IRC15:28
*** daidv has quit IRC15:28
*** ccamacho has joined #openstack-meeting-alt15:29
*** kobis has quit IRC15:38
*** oidgar has quit IRC15:40
*** daidv has joined #openstack-meeting-alt15:43
*** hieulq has joined #openstack-meeting-alt15:43
*** trungnv has joined #openstack-meeting-alt15:43
*** fzdarsky|afk is now known as fzdarsky15:44
*** ccamacho has quit IRC15:47
*** jkilpatr has quit IRC15:48
*** gongysh has joined #openstack-meeting-alt15:51
*** baoli has quit IRC15:55
*** d0ugal has quit IRC15:56
*** baoli has joined #openstack-meeting-alt15:56
*** achadha has joined #openstack-meeting-alt15:56
*** achadha has quit IRC15:57
*** achadha has joined #openstack-meeting-alt15:57
*** kobis has joined #openstack-meeting-alt16:00
*** noslzzp has joined #openstack-meeting-alt16:02
*** achadha has quit IRC16:04
*** achadha has joined #openstack-meeting-alt16:05
*** marios has quit IRC16:06
*** achadha has quit IRC16:09
*** cdent has joined #openstack-meeting-alt16:10
*** ijw has joined #openstack-meeting-alt16:10
*** bogdando has quit IRC16:11
*** annegentle has quit IRC16:12
*** jkilpatr has joined #openstack-meeting-alt16:13
*** kobis has quit IRC16:15
*** gongysh has quit IRC16:15
*** ijw has quit IRC16:15
*** cloudrancher has quit IRC16:16
*** coolsvap has quit IRC16:16
*** cloudrancher has joined #openstack-meeting-alt16:17
*** cdent has left #openstack-meeting-alt16:17
*** dsariel has quit IRC16:20
*** baoli has quit IRC16:23
*** achadha has joined #openstack-meeting-alt16:31
*** annegentle has joined #openstack-meeting-alt16:34
*** esikachev has quit IRC16:35
*** hieulq has quit IRC16:36
*** daidv has quit IRC16:36
*** trungnv has quit IRC16:36
*** harlowja has joined #openstack-meeting-alt16:37
*** achadha has quit IRC16:39
*** julim has joined #openstack-meeting-alt16:40
*** slaweq has joined #openstack-meeting-alt16:48
*** trungnv has joined #openstack-meeting-alt16:51
*** daidv has joined #openstack-meeting-alt16:51
*** hieulq has joined #openstack-meeting-alt16:51
*** slaweq has quit IRC16:54
*** daidv has quit IRC16:59
*** xyang1 has quit IRC16:59
*** hieulq has quit IRC16:59
*** trungnv has quit IRC17:00
*** tesseract has quit IRC17:01
*** iyamahat has joined #openstack-meeting-alt17:05
*** kobis has joined #openstack-meeting-alt17:05
*** xyang1 has joined #openstack-meeting-alt17:09
*** tellesnobrega has quit IRC17:12
*** achadha has joined #openstack-meeting-alt17:12
*** achadha has quit IRC17:13
*** achadha has joined #openstack-meeting-alt17:13
*** sshnaidm has quit IRC17:17
*** shobhar has joined #openstack-meeting-alt17:18
*** shobhar_ has joined #openstack-meeting-alt17:18
*** jkilpatr has quit IRC17:19
*** yamamoto has quit IRC17:19
*** cloudrancher has quit IRC17:20
*** slaweq has joined #openstack-meeting-alt17:20
*** cloudrancher has joined #openstack-meeting-alt17:21
*** sridharg has quit IRC17:22
*** slaweq has quit IRC17:24
*** tellesnobrega has joined #openstack-meeting-alt17:25
*** lpetrut has quit IRC17:26
*** esikachev has joined #openstack-meeting-alt17:31
*** dustins has quit IRC17:33
*** esikachev has quit IRC17:35
*** daidv has joined #openstack-meeting-alt17:39
*** trungnv has joined #openstack-meeting-alt17:40
*** hieulq has joined #openstack-meeting-alt17:40
*** EricGonczer_ has joined #openstack-meeting-alt17:40
*** EricGonczer_ has quit IRC17:41
*** julim has quit IRC17:41
*** trungnv has quit IRC17:43
*** hieulq has quit IRC17:43
*** tellesnobrega has quit IRC17:44
*** ralonsoh has quit IRC17:44
*** tellesnobrega has joined #openstack-meeting-alt17:47
*** dprince has quit IRC17:48
*** dizquierdo has quit IRC17:48
*** yamahata has quit IRC17:49
*** iyamahat has quit IRC17:49
*** tenobreg has joined #openstack-meeting-alt17:50
*** slaweq has joined #openstack-meeting-alt17:51
*** tenobreg has quit IRC17:51
*** tellesnobrega has quit IRC17:56
*** annegentle has quit IRC17:56
*** tellesnobrega has joined #openstack-meeting-alt17:56
*** trungnv has joined #openstack-meeting-alt17:58
*** hieulq has joined #openstack-meeting-alt17:58
*** annegentle has joined #openstack-meeting-alt17:59
*** tenobreg has joined #openstack-meeting-alt18:00
*** tenobreg has quit IRC18:00
*** shamail has joined #openstack-meeting-alt18:01
*** tenobreg has joined #openstack-meeting-alt18:01
*** tenobreg has quit IRC18:01
*** dmellado has quit IRC18:02
*** dmellado has joined #openstack-meeting-alt18:02
*** esikachev has joined #openstack-meeting-alt18:03
*** shobhar_ has quit IRC18:03
*** iyamahat has joined #openstack-meeting-alt18:05
*** shobhar has quit IRC18:05
*** sambetts is now known as sambetts|afk18:05
*** tenobreg has joined #openstack-meeting-alt18:06
*** tellesnobrega has quit IRC18:07
*** tenobreg has quit IRC18:07
*** tenobreg has joined #openstack-meeting-alt18:07
*** tenobreg is now known as tellesnobrega18:07
*** sshnaidm has joined #openstack-meeting-alt18:08
*** shobhar_ has joined #openstack-meeting-alt18:08
*** shobhar has joined #openstack-meeting-alt18:08
*** kylek3h has joined #openstack-meeting-alt18:11
*** shamail has quit IRC18:13
*** Swami has joined #openstack-meeting-alt18:14
*** tonanhngo has joined #openstack-meeting-alt18:15
*** lpetrut has joined #openstack-meeting-alt18:15
*** diablo_rojo has quit IRC18:18
*** dprince has joined #openstack-meeting-alt18:19
*** yamamoto has joined #openstack-meeting-alt18:19
*** diablo_rojo has joined #openstack-meeting-alt18:20
*** bobmel has joined #openstack-meeting-alt18:20
*** shobhar_ has quit IRC18:20
*** shobhar has quit IRC18:21
*** Sukhdev has joined #openstack-meeting-alt18:24
*** yamahata has joined #openstack-meeting-alt18:24
*** yamamoto has quit IRC18:27
*** shobhar_ has joined #openstack-meeting-alt18:29
*** shobhar has joined #openstack-meeting-alt18:29
*** baoli has joined #openstack-meeting-alt18:31
*** shobhar__ has joined #openstack-meeting-alt18:32
*** mnementh has joined #openstack-meeting-alt18:32
*** rarcea has quit IRC18:32
*** shobhar has quit IRC18:34
*** shobhar_ has quit IRC18:34
*** shobhar has joined #openstack-meeting-alt18:35
*** lpetrut has quit IRC18:35
*** shobhar__ has quit IRC18:36
*** lpetrut has joined #openstack-meeting-alt18:42
*** dsariel has joined #openstack-meeting-alt18:49
*** annabelleB has joined #openstack-meeting-alt18:57
*** ansmith_ has joined #openstack-meeting-alt18:58
*** ansmith_ has quit IRC18:58
*** ansmith_ has joined #openstack-meeting-alt19:01
*** arnewiebalck_ has joined #openstack-meeting-alt19:02
*** annegentle has quit IRC19:03
*** arnewiebalck_ has quit IRC19:19
*** shobhar_ has joined #openstack-meeting-alt19:24
*** shobhar has quit IRC19:27
*** shobhar_ has quit IRC19:28
*** shobhar_ has joined #openstack-meeting-alt19:36
*** tobberydberg has joined #openstack-meeting-alt19:38
*** daidv has quit IRC19:38
*** trungnv has quit IRC19:38
*** hieulq has quit IRC19:38
*** shobhar_ has quit IRC19:42
*** annegentle has joined #openstack-meeting-alt19:42
*** tobberydberg has quit IRC19:43
*** fnaval has quit IRC19:48
*** cloudrancher has quit IRC19:50
*** cloudrancher has joined #openstack-meeting-alt19:51
*** leong has joined #openstack-meeting-alt19:55
*** shobhar_ has joined #openstack-meeting-alt19:56
*** fnaval has joined #openstack-meeting-alt19:56
*** fnaval has quit IRC19:57
*** d0ugal has joined #openstack-meeting-alt19:57
*** fnaval has joined #openstack-meeting-alt19:57
*** fzdarsky is now known as fzdarsky|afk19:58
*** markstur_ has joined #openstack-meeting-alt20:00
leonghi.. is anyone here for Product WG meeting?20:00
leong#startmeeting product_working_group20:01
openstackMeeting started Mon Jul 10 20:01:18 2017 UTC and is due to finish in 60 minutes.  The chair is leong. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: product_working_group)"20:01
openstackThe meeting name has been set to 'product_working_group'20:01
leong#chair shamail20:01
openstackWarning: Nick not in channel: shamail20:01
openstackCurrent chairs: leong shamail20:01
*** markstur has quit IRC20:03
* leong waiting for rest to join in before we have quorum20:05
leong#endmeeting20:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:06
openstackMeeting ended Mon Jul 10 20:06:52 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-10-20.01.html20:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-10-20.01.txt20:06
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-10-20.01.log.html20:06
*** dizquierdo has joined #openstack-meeting-alt20:08
*** jkilpatr has joined #openstack-meeting-alt20:08
*** lpetrut has quit IRC20:17
*** arnewiebalck_ has joined #openstack-meeting-alt20:19
*** jkilpatr has quit IRC20:21
*** kobis has quit IRC20:21
*** dizquierdo has quit IRC20:22
*** tonanhngo has quit IRC20:27
*** tonanhngo has joined #openstack-meeting-alt20:31
*** esikachev has quit IRC20:33
*** tonanhngo has quit IRC20:35
*** tonanhngo has joined #openstack-meeting-alt20:35
*** ansmith has quit IRC20:38
*** leong has left #openstack-meeting-alt20:38
*** ansmith_ has quit IRC20:38
*** tonanhngo has quit IRC20:40
*** lpetrut has joined #openstack-meeting-alt20:40
*** tonanhngo has joined #openstack-meeting-alt20:42
*** arnewiebalck_ has quit IRC20:44
*** tonanhngo has quit IRC20:46
*** lpetrut has quit IRC20:47
*** jkilpatr has joined #openstack-meeting-alt20:47
*** jkilpatr has quit IRC20:48
*** jkilpatr has joined #openstack-meeting-alt20:48
*** annabelleB has quit IRC20:49
*** jprovazn has quit IRC20:50
*** d0ugal has quit IRC20:52
*** tonanhngo has joined #openstack-meeting-alt20:54
*** lpetrut has joined #openstack-meeting-alt20:54
*** rockyg has joined #openstack-meeting-alt20:54
*** MeganR has joined #openstack-meeting-alt20:55
*** annabelleB has joined #openstack-meeting-alt20:57
*** leong has joined #openstack-meeting-alt20:57
*** hichihara has joined #openstack-meeting-alt20:58
*** tonanhngo has quit IRC20:58
*** tonanhngo has joined #openstack-meeting-alt21:00
leong#startmeeting product_working_group21:00
openstackMeeting started Mon Jul 10 21:00:23 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
*** pchadwick has joined #openstack-meeting-alt21:00
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:00
leong#chair shamail21:00
openstackWarning: Nick not in channel: shamail21:00
openstackCurrent chairs: leong shamail21:00
*** annegentle has quit IRC21:01
Arkady_Kanevskyhello PWG21:01
pchadwickHello all21:01
leonghi Arkady_Kanevsky pchadwick21:01
*** annegentle has joined #openstack-meeting-alt21:01
rockygHey all!21:01
* leong waiting for folks to join in....21:01
leonghi rockyg21:01
MeganRHello!21:02
* leong joined the meeting an hour ago and realize nobody is there LOL21:02
leonghi MeganR21:02
leong#topic Rollcall21:02
*** openstack changes topic to "Rollcall (Meeting topic: product_working_group)"21:02
leonglet's wait for another 2 minutes for other folks to join in21:03
leongi have Leong Arkady_Kanevsky pchadwick rockyg MeganR21:03
leongam i missing anyone?21:03
rockygdon't see mrhillsman or AndyU21:04
*** shamail has joined #openstack-meeting-alt21:04
shamailo/21:04
leong#chair shamail21:04
openstackCurrent chairs: leong shamail21:04
annabelleBhello!21:04
leongi think we have quorum to start now.. :)21:04
Arkady_Kanevskylets go21:04
*** tonanhngo has quit IRC21:04
leong#link Agenda https://wiki.openstack.org/wiki/Meetings/product-team21:04
leongplease find the above link for today Agenda21:04
leong#topic Review of action items21:05
*** openstack changes topic to "Review of action items (Meeting topic: product_working_group)"21:05
leong#link Previous Meeting Notes: http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-26-21.01.html21:05
Arkady_KanevskyI had se nt email on wiki change.21:05
Arkady_KanevskyWaiting for feedback21:05
leongthanks Arkady_Kanevsky, i saw that email and generally looks good to me21:06
Arkady_Kanevskylet's setup feedback deadline date and I will start making chnages after it21:06
shamail+121:06
rockygLGTM21:06
leongi also sent email regarding the PWG teleconf midcycle, so far feedback is "ok", no objection..21:06
leongArkady_Kanevsky: what about end of this week or next?21:07
mrhillsmano/21:07
Arkady_Kanevskyfor midcycle did we agreed on full day(s) or a few hputs over multiple days?21:07
leongwelcome mrhillsman21:07
Arkady_KanevskyLeong +1 on deadline on feedback21:07
leongArkady_Kanevsky: i think we first need to agree to be "teleconf" ?21:07
rockyg++21:07
leongArkady_Kanevsky: end of this Fri?21:07
Arkady_Kanevskyagree. But think we have that alerady.21:07
Arkady_KanevskyYes on end of friday.21:08
leong#action all PWG please review the Wiki changes proposal from Arkady_Kanevsky by end of this Friday EOD21:08
leong#topic Midcycle video conferencing21:08
*** openstack changes topic to "Midcycle video conferencing (Meeting topic: product_working_group)"21:08
leonglet's discuss about the midcycle plan21:09
leongi believe the general consensus is to organise Teleconf, can we agreed on this?21:09
Arkady_Kanevsky+1 on teleconf21:09
pchadwick+121:09
*** shamail has quit IRC21:09
MeganR+121:09
rockyg+121:10
* leong looks like shamail just kicked out while we are making a decision.. lol :)21:10
*** shamail has joined #openstack-meeting-alt21:10
shamailI'd be interested in a virtual midcycle (sry connection issues)21:10
leong#agreed PWG agreed to organize a midcycle Teleconf21:11
leongnow let's talk about the date, time, full/half-day/multiple days21:11
leongwhat's your thoughts?21:11
shamailShould we send a doodle poll?21:11
pchadwickDoodle makes sense21:12
leongany preferences on dates, give me a few, at least say in Aug or Sep?21:12
shamailSept is better for me personally21:12
pchadwickSept +121:12
Arkady_KanevskyAugust 29 Tu second half of the day21:12
leongMy preferences also Sep21:13
Arkady_KanevskyDo we want to block the week of PTL? Spet 10-15?21:13
leongwhat about the rest? MeganR rockyg ?21:13
leongmrhillsman:21:13
leong?21:13
*** mnementh has quit IRC21:13
leongArkady_Kanevsky: +121:14
mrhillsmani will be at ptg21:14
rockygHalf days are good.  I think AndyU suggested that.21:14
MeganRI have a tough time knowing exact dates at the moment, will need to travel Aug/Sep, but do not have specific dates yet.21:14
MeganRI would prefer half days.21:14
leongare we going to have multiple "half day"?21:14
pchadwickDoesn't that depend on how much we put on the agenda?21:15
shamailpchadwick: +121:15
Arkady_KanevskyTuesday and Friday afternoons are better for me.21:15
leong3 half-days? US friendly, EU friendly + APAC friendly?21:15
shamailLet's start building an agenda and then determine how many days21:15
Arkady_Kanevsky2 topics per 1/2 day on agenda sound good.21:15
leongshamail / pchadwick : +121:16
rockygI would suggest not doubling up over the PTG or Ops Midcycle, but otherwise.... before 9/2121:16
Arkady_KanevskyI think majority is US. but let's see who will respond to doodle21:16
pchadwickOK21:16
rockygA few may be in EU, but most in US.21:17
leongok folks, i just created an etherpad here for midycle agenda: https://etherpad.openstack.org/p/VIR-pwg-meetup21:17
*** mnementh has joined #openstack-meeting-alt21:17
shamailThanks!21:17
leong#link Virtual Midcycle Planning: https://etherpad.openstack.org/p/VIR-pwg-meetup21:17
*** jkilpatr has quit IRC21:17
*** dklyle has joined #openstack-meeting-alt21:18
*** david-lyle has quit IRC21:19
leong#action All please propose agenda on the midcycle etherpad link https://etherpad.openstack.org/p/VIR-pwg-meetup21:19
*** tonytan4ever has joined #openstack-meeting-alt21:19
*** AndyU has joined #openstack-meeting-alt21:19
mrhillsmanwhat would the link be if there was another?21:19
shamailVIR2 :) or VIR-(cycle)21:20
Arkady_KanevskyLet's send etherpad pointer on email and request agedna items.21:20
mrhillsmanmaybe VIR-pwg-meetup-sept-2017 or yeah ^21:20
rockygArkady_Kanevsky, ++21:21
mrhillsmanminor thing really but just thinking21:21
leongmrhillsman: just append to the top :)21:21
Arkady_Kanevskycan we change etherpad page name? do not think etherpad support aliases21:22
leongok.. let's do it now ...21:22
shamailNo, it would have to be a new etherpad.21:22
leonghand on21:22
*** tonanhngo has joined #openstack-meeting-alt21:24
leong#link New PWG virtual midcycle etherpad link: https://etherpad.openstack.org/p/VIR-pwg-meetup-2017q321:24
shamailHey, my Q3 may not be the same your Q3!21:24
* shamail sees himself out of the room21:24
shamail:)21:24
mrhillsmanhehe21:24
Arkady_KanevskyLeong, are you goint to transfer content between etherpads?21:24
leongArkady_Kanevsky: just done21:24
shamailThanks leong21:25
MeganRShamail: you laugh, but that is actually true for me :)21:25
leong #action All please propose agenda on the midcycle etherpad link https://etherpad.openstack.org/p/VIR-pwg-meetup-2017q321:25
leongshamail: lol..21:26
shamailMeganR: I know a lot of companies like that so it jumped out at me.21:26
shamailAnyway, this name is fine. We get it. :)21:26
MeganRwe have to be different!21:26
leongsorry MeganR and shamail ...:p21:26
shamailI'm calendar aligned!21:26
shamailI'll add items throughout the week, thanks for creating it.21:27
MeganRI'll adjust!21:27
leongthanks :)21:27
AndyUSorry to have joined late, but should we be voting for preferred date(s)?21:27
leongAndyU: the team suggested to define the Agenda first before we decide how many days are required21:27
AndyUok. makes good sense21:28
*** tonanhngo has quit IRC21:28
leongok.. let's move on next topic21:28
leong#topic Sydney Summit/Forum preparation21:28
*** priteau has quit IRC21:28
*** openstack changes topic to "Sydney Summit/Forum preparation (Meeting topic: product_working_group)"21:28
Arkady_Kanevskyusual roamdap update submission?21:29
leong#info Summit proposal submission CFP deadline - July 14 at 11:59 pm PT21:29
*** esikachev has joined #openstack-meeting-alt21:29
annabelleBI’ve submitted a CFP for the roadmap on behalf of the group21:29
annabelleBHappy to add in additional presenters as people confirm their Sydney travel plans21:29
shamailThanks for that annabelleB21:29
annabelleBnp!21:30
leongthanks annabelleB , are you going to co-present with shamail / or maybe pchadwick ?21:30
pchadwickThanks annabelleB - I am pretty sure I will be there.21:30
Arkady_KanevskyI plan to be there also21:30
annabelleBpchadwick: perfect! was going to drop you an email today :)21:30
leongi also plan to be there but subject to travel approval :)21:30
Arkady_Kanevskyany other submission from the group?21:30
shamailleong: I will most likely not be in Sydney so pchadwick, annabelleB, +121:30
leongshamail: sure!21:31
shamailI just would like to ensure that the presenters actively participate in the roadmap creation21:31
pchadwickshamail +121:31
Arkady_Kanevsky+121:31
leongpchadwick: i assume you are comfortable with that? :)21:31
pchadwickYes21:31
AndyUSydney is still up in the air for me21:31
shamailAnyone think we should propose a PWG overview session?21:31
leongI assume we should also submit a BoF and Working Session?21:31
*** tonanhngo has joined #openstack-meeting-alt21:32
AndyUBoF +121:32
Arkady_Kanevskydo we want to submit status of proposal we are driving?21:32
shamailleong: +121:32
pchadwickDo we have any idea if there is an expectation that we will get a lot of new attendees due to the location?21:32
leongshamail: is "overview session" = BoF?21:32
shamailannabelleB: do you know if we need to submit BoF and Working session through CFP or Forum process?21:32
annabelleBpchadwick: I have a hunch so. But also think it will be newcomers to OpenStack and on some level cloud entirely21:33
shamailleong: yes, overview = BoF21:33
annabelleBshamail: I believe so, but I’ll double check right now21:33
shamailpchadwick: every Summit has been ~50% first time attendees for several years now21:33
AndyUBoF was via Conference process21:33
leongshamail: i believe BoF and WG fall under the same CFP process (as per previous experience)21:33
shamailThanks annabelleB21:33
pchadwickOK - so overview/BOF makes sense.21:33
Arkady_Kanevsky+ for BOF21:34
rockygNope.  I looked at the website for submissions.  Says the Bofs are different.21:34
*** esikachev has quit IRC21:34
rockygBut Forum is through the CFP.  Last time, BoFs used same process, but after the summit submissions were through21:34
leongi think the "submission" is through CFP, but "selection" is different from CFP process21:35
shamailForum is separate from CFP, we will open Forum registration in Fall21:35
annabelleB::pinged team for clarification, awaiting response::21:35
Arkady_Kanevskywhat about sessions on upgrade, HA, others?21:35
rockygI think we should propose a Forum session for how to empower sigs, wgs to work with devs to get to specs and/or bps21:35
shamail+1 for the Forum session21:36
leongannabelleB: thanks! please ask and let us know :-)21:36
AndyUDev proposals should submit for Forum session21:36
*** mnementh has quit IRC21:36
leong#action annabelleB to verify if we should submit BoF and WG session through the same CFP process21:36
*** baoli has quit IRC21:36
rockygAh.  Then Forum should also get a * next to it on the CFP page?21:36
Arkady_Kanevskymelvin, do we have an etherpad for forum ideas?21:36
mrhillsmannot yet21:36
leongother than BoF, WG working session and Roadmap, anything else?21:37
*** baoli has joined #openstack-meeting-alt21:37
AndyUMight bneed a forum session to INTRODUCE sigs21:37
mrhillsmanwe have a timeline and will send general announcement when ready21:37
shamailArkady_Kanevsky: stay tuned. We decided to launch Forum scheduling in Sept.21:37
mrhillsman++21:37
Arkady_KanevskyOK21:37
leongdo we plan to run the "hashtag" program again at Sydney forum?21:38
shamailAny other CFP submissions?21:38
rockyg++21:38
*** Shrews has joined #openstack-meeting-alt21:38
rockygWe should21:38
mrhillsmanif i can drop a line here, please add sessions for the ops midcycle21:38
*** tonanhngo has quit IRC21:38
rockygMaybe we can get the devs to, also at the PTG21:38
mrhillsmanhttps://etherpad.openstack.org/p/MEX-ops-meetup21:38
shamailleong: I am hesitant since we never delivered any outputs from the previous summit. It seems like we don't have the resources to own that process for now.21:38
mrhillsmansince we are talking about sessions and most times they carry-over21:38
*** tonanhngo has joined #openstack-meeting-alt21:39
AndyUwhat about trying to meet with product managers for major contributors to discuss priorities/objecvtives / seek alignmnet around dev proposals?21:39
shamailThanks mrhillsman21:39
leongshamail: from previous summit, the output we delivered is the individual hashtag data generated from each etherpad21:39
leongbut we didn't get a chance to "summarize" it21:39
rockygAndyU, that should be added to Forum etherpad21:39
shamail#link https://etherpad.openstack.org/p/MEX-ops-meetup21:39
leongshamail: i agree with you that we might have limited resources to own that hashtag process now21:40
shamailleong: sorry, that is what I meant. I know we have the output but we didn't share anything beyond the raw data.21:40
*** mnementh has joined #openstack-meeting-alt21:40
pchadwickAndyU - is your proposal re PMs for Sydney or Mexico City?21:40
shamailA more efficient path might be for us to just help reach out to moderators after the event so they can send a summary.21:41
mrhillsman^ was just typing that21:41
mrhillsmanwould have been great to have a summary from mods21:41
AndyU@Rocky - I added the topic to the mid-cycle agenda21:41
shamailYeah, plus they have all the context21:41
mrhillsman++21:41
leongmrhillsman / shamail : agreed :-)21:41
*** priteau has joined #openstack-meeting-alt21:41
rockygAndyU, yeah.  We need to talk about it before we schedule a forum session for it ;)21:41
shamailpchadwick: I think he was referring to Forum (not Ops)21:42
leongso my conclusion is that we ran the ##hashtag program and didn't find it effective to summarize the context ?21:42
*** hichihara has quit IRC21:42
pchadwickshamail - makes sense21:42
shamailWe ran the program, it gave us raw data but we didn't have resources to generate summaries. The value for the community is in the summary.21:42
AndyU+1 to asking moderatoprs to provide Summary, but need to communicate the expectation up front (as a responsibility of a moderator)21:42
mrhillsmani don't think it was onboarded well enough, easier to control during ops midcycle vs forum21:42
Arkady_KanevskyI think we have raw data and no resources to convert it to action21:43
mrhillsman^21:43
*** tonanhngo has quit IRC21:43
leongmrhillsman: so do you plan to run that ##hashtag again in upcoming midcycle?21:43
mrhillsmanyes21:44
AndyUAlso about Forum Summaries - would be nice to have them in a wiki page linked to the page with the etherpads. Have them in one place vs fragmented across various mailing lists?21:44
shamailAwesome mrhillsman21:44
leongawesome mrhillsman21:44
mrhillsmani think most folks found the idea not too obtrusive and we can use midcycle to continue to move it to being useful21:44
shamailGood idea AndyU21:44
leongalso a great path/way to start from small group of folks before turning into forum?21:45
leongplus soliciting feedback/improvement21:45
shamailThey can post summaries to a centralized wiki page but still share it out via ML so there can be discussion if needed.21:45
shamailleong: +121:46
leongmrhillsman: let me know if there is any way that i can help with the hashtag program in the upcoming Ops midcycle...21:46
AndyUtrue - and emails could link to the wiki and be less verbose ;21:46
shamailAndyU: +121:46
mrhillsmandefinitely21:46
leong#agreed Continue to adopt the ##hashtag program at Ops midcycle21:46
*** priteau has quit IRC21:47
AndyUWe'll need to provide a template and some guidance I think. I added Forum planning to the mid-cycle agenda21:47
* shamail sneaks out (have to be somewhere in 10 min)21:47
leong#agreed Will drop ##hashtag program for forum, we pilot at Boston summit, generate some raw data but didn't have resources to generate summaries.21:47
rockygSo, for Forum summaries, you'll get push back from some Devs.  Some would like to kill Wikis21:47
*** gongysh has joined #openstack-meeting-alt21:47
leongthat's true rockyg21:47
*** shamail has quit IRC21:47
AndyUThe hashtag output could also be linked from the Forum session/etherpad wiki page21:48
rockygThey don't like that old info sits out there that becomes false info.21:48
rockygSo, many PTLs will just send to ML.  We could link to the archive of the email on the Wiki page, though.21:48
leonganything else to discuss for Sydney?21:49
rockygI think a Wiki is a lot more useful for nondevs and noncommunity members.  Much easier to find stuff.21:50
AndyU+1 Rocky21:50
Arkady_Kanevsky+ rocky21:50
leongas long as the wiki provide "accurate/up-to-date" info :-)21:50
AndyUMANY operators who will be at the Summit are not in the mailing lists. Also the volume of mail can be overwhelming to sift through.21:50
pchadwickAndyU +121:51
AndyUSo I like the cross linking idea21:51
*** vishwanathj has joined #openstack-meeting-alt21:52
AndyUMaybe we could also propose using an email tag like [Forum Update] or some such in mail lists?21:52
rockygYeah.  It gives non-dev folks a way to see what happened.  And as long as we make the top level Forum page identified with *which* forum, and a date, the info never *gets* outdated21:52
mrhillsmangot to jet so i will catch the rest of the notes this evening21:52
leong#topic Community Roadmap21:52
*** openstack changes topic to "Community Roadmap (Meeting topic: product_working_group)"21:52
rockygthanks mrhillsman !21:52
leongannabelleB / pchadwick : do you have any update for community roadmap?21:53
leongttyl mrhillsman21:53
pchadwickI do not21:53
annabelleBme either21:53
*** trungnv has joined #openstack-meeting-alt21:53
pchadwickBut would propose that we start with the Boston version21:53
*** daidv has joined #openstack-meeting-alt21:53
pchadwickthat format seemed to work well.21:53
leongannabelleB / pchadwick : so do we have enough info to generate the upcoming community roadmap?21:54
mrhillsmanside note, we have an official if it channel, #openstack-uc so feel free to drop anything there21:54
mrhillsmanttyl21:54
mrhillsmanofficial irc channel21:54
*** hieulq has joined #openstack-meeting-alt21:54
annabelleBtimeline wise, i imagine we’ll get most of our info for the queens roadmap post-Denver, but I’m new to the process :)21:55
*** slaweq has quit IRC21:55
pchadwickleong I have not started looking closely yet, but assume we can follow a similar process to get data from PTLs21:55
*** slaweq has joined #openstack-meeting-alt21:55
rockygannabelleB, Yeah.  You're right there.  I think a key will be to make sure the PTLs know how to pass on their Queens decisions to the PWG Roadmap folks21:56
Arkady_Kanevskydo we do interviews or questionare for PTL this time?21:56
Arkady_Kanevskywe need to pair down projects list and only deal with "offocial" projetcs21:56
leongannabelleB: you might want to check with Heidi on the timeline21:56
annabelleBIt sounded like the questionare worked well21:56
rockygArkady_Kanevsky, I think mostly the questionnaires21:56
*** tonanhngo has joined #openstack-meeting-alt21:57
leongbtw, the link to the community roadmap is broken: https://www.openstack.org/software/roadmap/21:57
pchadwickQuestionnaire worked well.21:57
pchadwickleong works for me21:57
leongif you go to the above link ,and scroll down to "Read the community-generated roadmap", <-- this link is broken21:57
annabelleBleong: to that landing page or to a specific asset there? i have no problem with the page21:57
annabelleBah, i’ll sort that out21:58
leongthanks annabelleB21:58
*** lpetrut has quit IRC21:58
leong#action annabelleB to check the asset link "Read the community-generated roadmap" at https://www.openstack.org/software/roadmap/21:58
pchadwickleong - it gets me to here: https://www.openstack.org/assets/software/roadmap/Community-Generated-Roadmap-PQR-cycles.pdf21:58
leongpchadwick: yup. that link is missing21:58
leongi mean: that pdf21:59
leongi hit 40421:59
pchadwickI'm looking at it now ;)21:59
rockygBefore you all leave, just wanted to relay some humorous info... it seems there are some in the community spreading the false info that the PWG is dead.21:59
Arkady_Kanevskyi have access to https://www.openstack.org/assets/software/roadmap/Community-Generated-Roadmap-PQR-cycles.pdf21:59
*** slaweq has quit IRC21:59
rockygI get the 40421:59
*** kylek3h has quit IRC22:00
leong#topic open22:00
*** openstack changes topic to "open (Meeting topic: product_working_group)"22:00
*** slaweq has joined #openstack-meeting-alt22:00
leongall please continue to review readiness accessment: https://etherpad.openstack.org/p/PWG-development-proposal-readiness22:00
leongwe just hit the hour.. thanks everyone for your time!22:00
Arkady_Kanevskythanks all22:00
leongtalk to you next time!22:00
*** Arkady_Kanevsky has quit IRC22:00
pchadwickthanks - ttyl22:00
rockygCYa!22:00
*** pchadwick has left #openstack-meeting-alt22:01
leong#endmeeting22:01
*** tonanhngo has quit IRC22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
*** jlk has joined #openstack-meeting-alt22:01
openstackMeeting ended Mon Jul 10 22:01:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-10-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-10-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-10-21.00.log.html22:01
AndyUbye All22:01
jeblairhowdy zuul folks22:01
fungihowdy dr nick!22:01
* rbergeron passes out meat for meeting time since she's here22:01
jeblairmeating time22:01
jlko/22:01
* mordred waves22:01
Shrewshola22:01
*** dprince has quit IRC22:01
* jlk was just seconds away from passing out.22:01
* rockyg wonders if that's red meat or....22:02
*** MeganR has quit IRC22:02
jeblairjlk: if you haven't passed out by the end, then it's not a proper meeting22:02
jeblair#startmeeting zuul22:02
openstackMeeting started Mon Jul 10 22:02:46 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: zuul)"22:02
openstackThe meeting name has been set to 'zuul'22:02
* fungi needs to start drinking asap in that case22:02
*** tonanhngo has joined #openstack-meeting-alt22:02
rbergeronit's whateever your favorite meat is. veggiemeat or beef-meat or fish-meat or ... popsicle-meat. your call :)22:03
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:03
jeblair#link previous meating http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-26-22.02.html22:03
jeblair#topic Actions from last meeting22:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: zuul)"22:03
jeblairjlk look into moving depends-on to pull-request summary to see if it is both workable and a solution to the needed-by problem22:03
jlkDone and done.22:03
mordredwow. last meeting was a long time ago it feels22:03
jeblairmordred: it was 2 weeks ago, which is ages in zuul time!22:04
jlkTurns out it was easier all around to use the pull request summary.22:04
fungithat's at least 6mos in zuul years22:04
jlkso, thanks to those of you that pushed in that direction.22:04
jeblairjlk: and i belive that merged, right?22:04
jlkcorrect22:04
jeblair#topic Status update: standard job library22:05
*** openstack changes topic to "Status update: standard job library (Meeting topic: zuul)"22:05
jeblairmordred: this thing is starting to be a thing, eh?22:05
mordredyah!22:05
mordredwe have jobs in zuul-jobs, and they're running tests on zuul22:05
*** jamielennox has joined #openstack-meeting-alt22:06
fungiit's true, i saw one22:06
mordredand the speculative job stuff totally works - AND - they're parameterized and not openstack specific :)22:06
jeblairi have an outstanding change related to this...22:06
mordredI'm cranking currently on getting all of the standard tox jobs done, as well as the copied-in-shell-scripts ansible-ified22:06
jeblair#link config shadowing https://review.openstack.org/47908422:07
mordredbut we're self-aware enough that hacking on the jobs using zuul to test that the jobs work is neat22:07
jlkmordred: do you want some help with that? Divide and conquer mode, or just fast follow reviews?22:07
jeblaironce that change merges, we'll be able to move the base job into zuul-jobs and have a local override version of it in project-config22:07
*** xyang1 has quit IRC22:07
Shrewsmordred: that's so meta22:07
*** tonanhngo has quit IRC22:07
mordredbtw - I added a job o the zuul-jobs repo called tox-py35-on-zuul - which grabs the zuul repo and runs the tox py35 job content on it - on changes to the zuul-jobs repo22:07
mordredjlk: Id' love some! let's sync up after the meeting to divy up the list22:08
jlkack22:08
jeblair#info tox-py35-on-zuul job runs the zuul py35 job on changes to zuul-jobs to better exercise unittest jobs on changes to zuul-jobs22:08
mordredjeblair: you enjoyed writing that didn't you? :)22:09
jeblairmordred: i like saying the words "zuul" and "jobs"22:09
jeblairso yes22:09
jeblairafter the config-shadowing change merges, i'd like to ask other folks (bonnyci, tobiash, tristanC) to try using zuul-jobs locally as well22:09
mordred++22:10
mordredwon't THAT be exciting?22:10
jlkack22:10
jeblairit should be reasonable to do so once that lands, and it will be really good to have a wide corpus of reviewers on that repo -- it's the future zuul commons.  :)22:10
mordrednext we'll need to figure out how to write  ajob that validates that changes to zuul-jobs don't break something in bonnyci22:11
jeblair(the config shadowing gives folks an escape hatch so that zuul-jobs doesn't take over anything you don't want it to)22:11
*** trungnv has quit IRC22:12
*** daidv has quit IRC22:12
*** hieulq has quit IRC22:12
jeblair#info after config shadowing change lands, non-openstack users should try using zuul-jobs22:12
jeblairanything else in this topic?22:12
jeblair#topic Status updates: Documentation22:13
*** openstack changes topic to "Status updates: Documentation (Meeting topic: zuul)"22:13
*** leong has left #openstack-meeting-alt22:13
jeblair#info big documentation refactor landed22:13
jeblair#link zuul v3 docs https://docs.openstack.org/infra/zuul/feature/zuulv3/22:13
jeblairthere is *a lot* more we can do there22:13
jlkit's really nice to have docs to point to again though22:14
*** deep-book-gk_ has joined #openstack-meeting-alt22:14
jeblairin particular, there's lots of room for examples (both in-line, and longer examples in the form of appendixes)22:14
jeblairbut yeah, it's a thing.  :)22:14
mordredoh - did we update the README to link to that?22:15
jeblairalso, i need to do something to get us anchors on all the job keywords, etc, so we can deep link to them22:15
jeblairmordred: no that's a good idea though22:15
*** slaweq has quit IRC22:16
jeblaira while back we suspended the "changes should have docs" rule to facilitate faster iteration.  i think that's no longer required, so i think we should reinstate that rule now.22:16
jlkI owe an action to add more meat to the github docs, particularly app vs API key and depends-on22:16
*** shobhar_ has quit IRC22:16
*** deep-book-gk_ has left #openstack-meeting-alt22:17
jeblairi think we should make allowances for changes which have been in development for a while -- we can add documentation for those in followup patches22:17
fungithat seems like a reasonable compromise22:17
jlk+1 on the rule + compromise22:17
jeblairbut let's at least remind ourselves that we should do that, and start leaving -1s on patches which need doc updates and don't have them22:18
jeblairleaving -1s on *new* patches...22:18
jeblair#info now that the new doc structure has merged, new changes should once again be accompanied with documentation updates22:18
jeblair#action jlk add meat to github docs re app setup and depends-on22:19
jeblair#action jeblair make anchors for keywords22:19
jeblair#action mordred add v3 doc link to readme22:20
jeblairother than that, i think we can drop this section from the standing agenda.22:20
jeblairany objections to that or anything else on this topic?22:20
*** shobhar_ has joined #openstack-meeting-alt22:20
*** tonanhngo has joined #openstack-meeting-alt22:20
fungisounds fine to me22:21
jeblair#topic Status update: GitHub parity22:21
*** openstack changes topic to "Status update: GitHub parity (Meeting topic: zuul)"22:21
jeblairjlk: are we at parity? :)22:21
jlkI think it's time for a parity party!22:21
rbergeroncan we do parodies at the parity party?22:21
jlkDepends-on was the last bit to land I think.22:22
jeblairi'm going to dress up as a stop bit22:22
rbergeronwhile wearing parrot-tees?22:22
*** felipemonteiro_ has quit IRC22:22
jlkI'm going to wear a pair of Ts22:22
jeblairjlk: woot!22:22
rbergeronOMG22:22
* fungi wants to be flow control22:22
rbergeronyou are in my head22:22
rbergeronsorry, i interrupted the flow of actual things22:23
jeblairrbergeron: just for that, i'm dropping this topic from the agenda too!22:23
mordred\o/22:23
jlk+122:23
fungierror correction will just add it back you know22:23
jeblair#topic Status updates: (web) console streaming22:23
*** openstack changes topic to "Status updates: (web) console streaming (Meeting topic: zuul)"22:23
mordredjlk, jeblair: we still need cross-source depends-on right? but that's not a parity thing - that's a whole new thing both drivers need22:23
jeblairmordred: ya22:23
jlkyup22:23
jeblairShrews: your websocket server has merged!22:24
ShrewsLet us all rejoice and hail our new websocket overlord!22:24
Shrewsthe new thing is zuul-web, which conjures up images of the spider from LoTR in my head22:24
mordred\o/22:24
jeblairShrews: shelob?22:24
SpamapScan we rejoice all at once or are we single threaded but async rejoicing?22:25
rbergeronyes.22:25
mordredSpamapS: YES22:25
ShrewsSpamapS: you are so terrible22:25
jeblairwe need to do some puppet work in infra in order to run it  (any volunteers?)22:25
* rbergeron hides22:25
* SpamapS poll()'d the channel22:25
*** tonanhngo has quit IRC22:25
mordredjeblair: I'll do it if nobody else does - I'm kinda getting annoyed at our current init script situation anyway22:26
jeblairtobiash handed us some html we can run, and i think Shrews is going to work on incorporating that into zuul + status page so we can actually have links and stuff22:26
jlkಠ_ಠ22:26
Shrewsyes22:26
Shrewsto the status page stuff22:26
jeblairmordred: ack -- though i think some of the problems are actually zuul problems22:26
*** trungnv has joined #openstack-meeting-alt22:27
*** daidv has joined #openstack-meeting-alt22:27
jeblair#action mordred make infra init script for zuul-web in puppet-zuul22:27
*** hieulq has joined #openstack-meeting-alt22:27
mordredjeblair: some of them may be zuul problems for sure - but before we go live they need to stop being problems wheever they are22:27
jeblairmordred: yes.  just chat with me about them before you go change everything.  :)22:27
mordredjeblair: too late. already done in production ;)22:28
jamielennoxhaving zuul-web be it's own repo with some proper deployment tools would actually be kind of useful22:28
jamielennoxansible downloading jquery and copying files into apache is pretty ugly22:28
jamielennoxbut not super important22:29
jeblairi don't think zuul-web has any jquery yet, but the old webapp does, so i guess you mean when we port that over to zuul-web22:29
mordredwe poked a long time ago at using bower, etc for the javascript thigns, but there were so few of them it didn't seem worth it22:30
*** esikachev has joined #openstack-meeting-alt22:30
fungiso looknig for some sort of (hopefully ecosystem-standard) javascript dependency management solution?22:30
jamielennoxoh, sorry confusing bits, but yes preferably before making it any more complicated22:30
mordredit may be getting to be time to think about the strategy for managing those22:30
mordredfungi: yah - that22:30
fungicould always borrow the design storyboard is using for teh webclient i suppose22:31
*** shobhar_ has quit IRC22:32
mordredone of the interesting outcomes of that is the ability to point test-patch versions of html/js at the live storyboard api endpoint - which is a thing we could certainly also do here as well22:32
fungiseems to use bower/grunt22:32
*** tonanhngo has joined #openstack-meeting-alt22:32
fungi#link http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/tree/package.json storyboard webui packaging metadata22:33
fungifor reference22:33
jeblairmordred: that may be useful for the dashboard functionality22:33
jeblairwhatever we come up with needs to be comprehensible by everyone.  i do not want to end up in a situation where no one on the team understands the tooling.  i'd rather have crappy shell scripts than something that no one knows how to use.22:33
fungiup side is we already have (granted jjb) job definitions for dealing with that stuff22:33
mordredjeblair: agree22:34
*** esikachev has quit IRC22:34
jeblair(and i'm not saying that's not bower/grunt, it may well be.  i'm just saying let's be realistic about the number of folks on the team that are interested in working on fashionable js technlogies.  otherwise we will dig a hole for ourselves.)22:34
jeblairanyway, i think we at least have the next few steps of this laid out.22:35
jeblairand i'm very excited about seeing our first websocket log streamed :)22:36
fungiyep, my suggestion was more around common tooling and community building vs some bespoke tooling that only the zuul reviewers understand ;)22:36
*** slaweq has joined #openstack-meeting-alt22:37
jeblairanything else?22:37
fungii'm also not opposed to what we did in v2 and just provided instructions for setting up the status page (plus a convenience script for downloading javascript deps)22:37
funginothing else on my end22:37
*** tonanhngo has quit IRC22:37
Shrewsawait mordred.install_zuul_web()22:37
jeblairShrews has the lingo22:38
jeblair#topic Status update: Zuul test enablement22:38
*** openstack changes topic to "Status update: Zuul test enablement (Meeting topic: zuul)"22:38
jeblairi think this topic took a vacation22:38
jeblairmaybe next week22:39
jeblair#topic Progress summary22:39
*** openstack changes topic to "Progress summary (Meeting topic: zuul)"22:39
jeblair#link https://storyboard.openstack.org/#!/board/4122:39
jeblairi think we've actually been doing a reasonable job keeping the board up to date22:40
jeblairi've been putting a bunch of my punchlist items in there, and jlk added some stuff from our meeting with ansible folks22:40
jeblairanyway, there's still stuff out there if folks want to pick things up22:41
*** slaweq has quit IRC22:41
SpamapSsorry I looked away at the wrong moment22:41
SpamapSI did a sweep through and updated a few stale bits last week22:42
jeblairSpamapS: you were looking into a new tag... any news on that?22:42
SpamapSjeblair: I think we should still do it, but I don't have a definitive plan written up yet. Basically we need to combine mordred's roadmap idea with my zuulv3.0 tag or something like that.22:43
SpamapSand then we can start kicking a few things off zuulv3 onto zuulv3022:43
jeblairSpamapS: ok, let's bat some ideas around later.22:44
mordred++22:44
jeblairanything else?22:44
jeblair#topic Open Discussion22:45
*** openstack changes topic to "Open Discussion (Meeting topic: zuul)"22:45
jeblairmordred: want to talk about openstack rollout?22:47
mordredI do!22:47
mordredSO .....22:47
mordred*drum roll*22:47
mordredwe're getting close everybody22:47
mordredso close that I started writing up thoughts on openstack rollout process and timetable22:48
fungiooh!22:48
mordredI was hoping to have them ready by today's meeting - but I didn't quite get there22:48
mordredbut - the tl;dr is that I believe we're in a position to actually start making plans and projecting completion times22:49
mordredI'll try to have the first draft of the proposal done by tomorrow22:49
rbergeron"speculative future state of zuul"22:49
jeblairmordred, fungi: let's add that to the infra meeting agenda maybe?22:49
mordredfungi: do you think it should be in the form of an infra-spec? a mailing list email? or both?22:49
fungiwfm22:49
mordredjeblair: that's a great idea22:49
*** shobhar_ has joined #openstack-meeting-alt22:49
jeblair(i'll edit the wiki)22:50
rbergeroniguess it's not speculative but just when it will land :) also, me with the words today is bad at this moment22:50
fungiwe can touch on it in the priority efforts section of the meeting tomorrow and see where we want to go with specs, mailing list threads, what have you22:50
mordredit's also worth noting that with that, we're also getting to the point where folks may wantto start paying attention to patches to zuul-jobs22:50
mordredfungi: cool22:50
Shrewsrbergeron: is good. hard is the words when end day of is near22:51
mordredwords22:51
*** annabelleB has quit IRC22:52
*** egallen has quit IRC22:52
*** markstur_ has quit IRC22:52
* jlk has to sneak out. Cheers.22:53
*** priteau has joined #openstack-meeting-alt22:54
jeblairmordred: would it be useful to take your plan in progress and have it in an etherpad for tommorow's infra meeting?22:54
mordredjeblair: that's a great idea. yes22:54
fungiexcellent. feel free to link it on the agenda if you get a moment22:54
jeblaircool, seems like that might be a good place to start, then we can decide whether that's ready to just go to the list, or bake in a spec or become a wiki page, or an entry in system-config or what... :)22:55
jeblair(or maybe even remain an etherpad :)22:55
*** AndyU has quit IRC22:56
fungiawesome22:56
jeblairi'm excited.  i think we're really close to getting this rolling.  :)22:57
jeblairif that's all, let's use the remaining 2 minutes to pass out.22:58
mordred++22:58
*** priteau has quit IRC22:58
fungii'd like to start pondering what we might be able to do with zuul jobs at the ptg in denver22:58
mordredwriting jobs for v3 has actually been quite pleasant22:58
mordredfungi: I think you'll like my document then22:59
fungii'm sure i'd like it anyway22:59
*** annabelleB has joined #openstack-meeting-alt22:59
jeblairoh good.  let's make a decision about how much zuuling we're going to do at the ptg soon so we make sure folks who want to come have time to plan.22:59
jeblairthanks everyone!23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Mon Jul 10 23:00:14 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-07-10-22.02.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-07-10-22.02.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-07-10-22.02.log.html23:00
*** shobhar__ has joined #openstack-meeting-alt23:01
fungithanks jeblair!23:01
*** egallen has joined #openstack-meeting-alt23:02
*** egallen has quit IRC23:02
*** shobhar_ has quit IRC23:04
*** annabelleB has quit IRC23:07
*** rockyg has quit IRC23:08
*** jcoufal has quit IRC23:09
*** markstur has joined #openstack-meeting-alt23:19
*** jkilpatr has joined #openstack-meeting-alt23:24
*** esikachev has joined #openstack-meeting-alt23:31
*** Swami has quit IRC23:34
*** esikachev has quit IRC23:35
*** hongbin has quit IRC23:42
*** amotoki is now known as amotoki_away23:43
*** annegentle has quit IRC23:45
*** chyka has quit IRC23:54
*** caowei has joined #openstack-meeting-alt23:55
*** shobhar__ has quit IRC23:55
*** chyka has joined #openstack-meeting-alt23:55
*** shobhar has joined #openstack-meeting-alt23:55
*** shobhar_ has joined #openstack-meeting-alt23:57
*** chyka has quit IRC23:59

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