Monday, 2017-05-22

*** kzaitsev_mb has quit IRC00:03
*** markvoelker has quit IRC00:11
*** mickeys has joined #openstack-meeting-alt00:30
*** EricGonczer_ has joined #openstack-meeting-alt00:35
*** mickeys has quit IRC00:36
*** trungnv has quit IRC00:43
*** links has joined #openstack-meeting-alt00:54
*** tovin07_ has joined #openstack-meeting-alt01:04
*** reedip__ has joined #openstack-meeting-alt01:17
*** cknight has joined #openstack-meeting-alt01:19
*** cloudrancher has joined #openstack-meeting-alt01:19
*** bzhao has quit IRC01:22
*** cloudrancher has quit IRC01:24
*** EricGonczer_ has quit IRC01:24
*** trungnv has joined #openstack-meeting-alt01:25
*** cloudrancher has joined #openstack-meeting-alt01:26
*** anilvenkata has quit IRC01:29
*** baoli has joined #openstack-meeting-alt01:30
*** cloudrancher has quit IRC01:30
*** cloudrancher has joined #openstack-meeting-alt01:32
*** mickeys has joined #openstack-meeting-alt01:33
*** cloudrancher has quit IRC01:36
*** mickeys has quit IRC01:37
*** cknight has quit IRC01:39
*** baoli has quit IRC01:46
*** Sukhdev has joined #openstack-meeting-alt01:47
*** fzdarsky_ has joined #openstack-meeting-alt01:48
*** fzdarsky has quit IRC01:50
*** trungnv has quit IRC01:59
*** bzhao has joined #openstack-meeting-alt02:02
*** kzaitsev_mb has joined #openstack-meeting-alt02:02
*** funzo has joined #openstack-meeting-alt02:03
*** gcb has joined #openstack-meeting-alt02:04
*** shuyingya has joined #openstack-meeting-alt02:05
*** funzo has quit IRC02:08
*** EricGonczer_ has joined #openstack-meeting-alt02:15
*** kzaitsev_mb has quit IRC02:17
*** bzhao has quit IRC02:18
*** julim has joined #openstack-meeting-alt02:21
*** adam_g has quit IRC02:24
*** shuyingy_ has joined #openstack-meeting-alt02:24
*** bzhao has joined #openstack-meeting-alt02:24
*** adam_g has joined #openstack-meeting-alt02:25
*** beekhof has joined #openstack-meeting-alt02:25
*** shuyingya has quit IRC02:28
*** adam_g has quit IRC02:32
*** mickeys has joined #openstack-meeting-alt02:34
*** mickeys has quit IRC02:34
*** julim has quit IRC02:34
*** mickeys has joined #openstack-meeting-alt02:34
*** adam_g has joined #openstack-meeting-alt02:35
*** reedip__ has quit IRC02:41
*** EricGonczer_ has quit IRC02:41
*** trungnv has joined #openstack-meeting-alt02:51
*** salv-orlando has joined #openstack-meeting-alt02:54
*** cloudrancher has joined #openstack-meeting-alt02:55
*** trungnv has quit IRC02:58
*** cloudrancher has quit IRC02:59
*** baoli has joined #openstack-meeting-alt03:00
*** jhesketh_ is now known as jhesketh03:08
*** trungnv has joined #openstack-meeting-alt03:08
*** anilvenkata has joined #openstack-meeting-alt03:09
*** markstur has joined #openstack-meeting-alt03:09
*** markstur has quit IRC03:10
*** kzaitsev_mb has joined #openstack-meeting-alt03:14
*** kzaitsev_mb has quit IRC03:19
*** EricGonczer_ has joined #openstack-meeting-alt03:21
*** EricGonczer_ has quit IRC03:21
*** hongbin has joined #openstack-meeting-alt03:23
*** caowei has joined #openstack-meeting-alt03:23
*** adam_g has quit IRC03:24
*** adam_g has joined #openstack-meeting-alt03:24
*** SumitNaiksatam has quit IRC03:46
*** baoli has quit IRC03:48
*** salv-orlando has quit IRC03:58
*** caowei has quit IRC04:06
*** yamamoto has quit IRC04:12
*** rwsu has joined #openstack-meeting-alt04:18
*** adisky_ has joined #openstack-meeting-alt04:21
*** trinaths has joined #openstack-meeting-alt04:28
*** mickeys has quit IRC04:28
*** adam_g has quit IRC04:30
*** adam_g has joined #openstack-meeting-alt04:32
*** caowei has joined #openstack-meeting-alt04:37
*** markstur has joined #openstack-meeting-alt04:39
*** caowei has quit IRC04:41
*** cloudrancher has joined #openstack-meeting-alt04:43
*** markstur has quit IRC04:44
*** hiro-kobayashi has joined #openstack-meeting-alt04:44
*** caowei has joined #openstack-meeting-alt04:45
*** cloudrancher has quit IRC04:47
*** yamamoto has joined #openstack-meeting-alt04:56
*** bzhao has quit IRC04:57
*** bzhao has joined #openstack-meeting-alt04:57
*** janki has joined #openstack-meeting-alt04:59
*** markstur has joined #openstack-meeting-alt04:59
*** JudeC has joined #openstack-meeting-alt05:01
*** pgadiya has joined #openstack-meeting-alt05:03
*** markstur has quit IRC05:04
*** pgadiya has quit IRC05:06
*** caowei has quit IRC05:08
*** skramaja has joined #openstack-meeting-alt05:11
*** hongbin_ has joined #openstack-meeting-alt05:13
*** hongbin has quit IRC05:14
*** kzaitsev_mb has joined #openstack-meeting-alt05:15
*** hongbin_ has quit IRC05:17
*** salv-orlando has joined #openstack-meeting-alt05:17
*** reedip__ has joined #openstack-meeting-alt05:17
*** kzaitsev_mb has quit IRC05:20
*** stingaci has joined #openstack-meeting-alt05:20
*** sridharg has joined #openstack-meeting-alt05:20
*** stingaci has quit IRC05:25
*** reedip__ has quit IRC05:28
*** mickeys has joined #openstack-meeting-alt05:29
*** mickeys has quit IRC05:33
*** caowei has joined #openstack-meeting-alt05:34
*** rarcea has joined #openstack-meeting-alt05:42
*** JudeC has quit IRC05:54
*** tobberydberg has joined #openstack-meeting-alt05:56
*** cloudrancher has joined #openstack-meeting-alt05:58
*** funzo has joined #openstack-meeting-alt06:02
*** cloudrancher has quit IRC06:02
*** salv-orlando has quit IRC06:04
*** funzo has quit IRC06:06
*** ltomasbo|away is now known as ltomasbo06:06
*** belmoreira has joined #openstack-meeting-alt06:07
*** salv-orlando has joined #openstack-meeting-alt06:07
*** gyee has joined #openstack-meeting-alt06:08
*** fzdarsky_ is now known as fzdarsky06:08
*** shuyingy_ has quit IRC06:13
*** shuyingya has joined #openstack-meeting-alt06:13
*** shuyingy_ has joined #openstack-meeting-alt06:19
*** rcernin has joined #openstack-meeting-alt06:19
*** bzhao has quit IRC06:21
*** bzhao has joined #openstack-meeting-alt06:22
*** shuyingya has quit IRC06:22
*** jprovazn has joined #openstack-meeting-alt06:23
*** gyee has quit IRC06:31
*** markstur has joined #openstack-meeting-alt06:35
*** mickeys has joined #openstack-meeting-alt06:39
*** markstur has quit IRC06:40
*** andreas_s has joined #openstack-meeting-alt06:41
*** adam_g has quit IRC06:42
*** adam_g has joined #openstack-meeting-alt06:43
*** ccamacho has quit IRC06:49
*** mjura has joined #openstack-meeting-alt06:54
*** hiro-kobayashi has quit IRC06:55
*** matrohon has joined #openstack-meeting-alt06:57
*** kzaitsev_mb has joined #openstack-meeting-alt07:01
*** ccamacho has joined #openstack-meeting-alt07:01
*** salv-orlando has quit IRC07:01
*** salv-orlando has joined #openstack-meeting-alt07:03
*** tobberyd_ has joined #openstack-meeting-alt07:03
*** markstur has joined #openstack-meeting-alt07:05
*** florianf has joined #openstack-meeting-alt07:05
*** tobberydberg has quit IRC07:06
*** kzaitsev_mb has quit IRC07:07
*** salv-orlando has quit IRC07:08
*** markstur has quit IRC07:09
*** rcernin has quit IRC07:14
*** rcernin has joined #openstack-meeting-alt07:14
*** dizquierdo has joined #openstack-meeting-alt07:19
*** cloudrancher has joined #openstack-meeting-alt07:28
*** bnemec has quit IRC07:29
*** cloudrancher has quit IRC07:32
*** markstur has joined #openstack-meeting-alt07:34
*** bnemec has joined #openstack-meeting-alt07:35
*** david-lyle has quit IRC07:36
*** markstur has quit IRC07:39
*** bogdando has joined #openstack-meeting-alt07:42
*** david-lyle has joined #openstack-meeting-alt07:42
*** mickeys has quit IRC07:42
*** jpena|off is now known as jpena07:46
*** david-lyle has quit IRC07:46
*** Sukhdev has quit IRC07:50
*** gouthamr has joined #openstack-meeting-alt07:51
*** ralonsoh has joined #openstack-meeting-alt07:55
*** trungnv has quit IRC07:56
*** SumitNaiksatam has joined #openstack-meeting-alt07:59
*** rossella_s has joined #openstack-meeting-alt07:59
*** trungnv has joined #openstack-meeting-alt08:02
*** david-lyle has joined #openstack-meeting-alt08:03
*** tobberyd_ has quit IRC08:14
*** ralonsoh has quit IRC08:15
*** rossella_s has quit IRC08:15
*** bobmel has joined #openstack-meeting-alt08:17
*** gouthamr has quit IRC08:19
*** markstur has joined #openstack-meeting-alt08:19
*** ralonsoh has joined #openstack-meeting-alt08:19
*** caowei has quit IRC08:21
*** rossella_s has joined #openstack-meeting-alt08:21
*** markstur has quit IRC08:23
*** caowei has joined #openstack-meeting-alt08:24
*** alexchadin has joined #openstack-meeting-alt08:25
*** neiljerram has joined #openstack-meeting-alt08:28
*** lpetrut has joined #openstack-meeting-alt08:31
*** derekh has joined #openstack-meeting-alt08:34
*** iyamahat has joined #openstack-meeting-alt08:35
*** janki has quit IRC08:35
*** janki has joined #openstack-meeting-alt08:36
*** jchhatbar has joined #openstack-meeting-alt08:37
*** markstur has joined #openstack-meeting-alt08:38
*** janki has quit IRC08:40
*** pbourke has joined #openstack-meeting-alt08:43
*** mickeys has joined #openstack-meeting-alt08:43
*** markstur has quit IRC08:43
*** jchhatbar is now known as janki08:44
*** iyamahat has quit IRC08:45
*** mickeys has quit IRC08:48
*** tobberydberg has joined #openstack-meeting-alt08:50
*** adam_g has quit IRC08:54
*** tobberydberg has quit IRC08:54
*** adam_g has joined #openstack-meeting-alt08:55
*** chhavi has joined #openstack-meeting-alt08:55
*** nijaba has quit IRC09:01
*** dsariel has joined #openstack-meeting-alt09:02
*** tobberydberg has joined #openstack-meeting-alt09:02
*** rarcea_ has joined #openstack-meeting-alt09:02
*** rarcea_ has quit IRC09:02
*** rarcea_ has joined #openstack-meeting-alt09:03
*** itamaro has joined #openstack-meeting-alt09:04
*** kzaitsev_ws has joined #openstack-meeting-alt09:06
*** nijaba has joined #openstack-meeting-alt09:09
*** nijaba has quit IRC09:09
*** nijaba has joined #openstack-meeting-alt09:09
*** rossella_s has quit IRC09:09
*** vds has joined #openstack-meeting-alt09:12
*** dizquierdo has quit IRC09:21
*** pnavarro has joined #openstack-meeting-alt09:22
*** dalgaaf has quit IRC09:25
*** sshnaidm|off is now known as sshnaidm09:26
*** dalgaaf has joined #openstack-meeting-alt09:27
*** kevinz has quit IRC09:32
*** rossella_s has joined #openstack-meeting-alt09:33
*** gongysh has joined #openstack-meeting-alt09:35
*** stingaci has joined #openstack-meeting-alt09:42
*** mickeys has joined #openstack-meeting-alt09:44
*** mickeys has quit IRC09:49
*** sambetts_ is now known as sambetts09:51
*** adam_g has quit IRC09:54
*** adam_g has joined #openstack-meeting-alt09:55
*** tovin07_ has quit IRC09:55
*** funzo has joined #openstack-meeting-alt10:03
*** funzo has quit IRC10:07
*** adam_g has quit IRC10:09
*** rossella_s has quit IRC10:09
*** adam_g has joined #openstack-meeting-alt10:10
*** alexchad_ has joined #openstack-meeting-alt10:10
*** alexchadin has quit IRC10:10
*** tuanluong has joined #openstack-meeting-alt10:15
*** adam_g has quit IRC10:19
*** tenobreg has quit IRC10:20
*** rossella_s has joined #openstack-meeting-alt10:20
*** stingaci has quit IRC10:21
*** adam_g has joined #openstack-meeting-alt10:23
*** caowei has quit IRC10:28
*** markstur has joined #openstack-meeting-alt10:29
*** sdague has joined #openstack-meeting-alt10:31
*** jkilpatr has quit IRC10:31
*** adam_g has quit IRC10:32
*** neiljerram has quit IRC10:33
*** aspiers has joined #openstack-meeting-alt10:34
*** neiljerram has joined #openstack-meeting-alt10:34
*** markstur has quit IRC10:34
*** adam_g has joined #openstack-meeting-alt10:35
*** mickeys has joined #openstack-meeting-alt10:45
*** tobberydberg has quit IRC10:45
*** ganso has joined #openstack-meeting-alt10:46
*** adam_g has quit IRC10:48
*** mickeys has quit IRC10:49
*** adam_g has joined #openstack-meeting-alt10:49
*** cloudrancher has joined #openstack-meeting-alt10:50
*** alexchad_ has quit IRC10:53
*** dizquierdo has joined #openstack-meeting-alt10:53
*** julim has joined #openstack-meeting-alt10:53
*** gongysh has quit IRC10:54
*** jkilpatr has joined #openstack-meeting-alt10:57
*** numans has joined #openstack-meeting-alt10:59
*** markstur has joined #openstack-meeting-alt10:59
*** markstur has quit IRC11:03
*** tuanluong has quit IRC11:04
*** anilvenkata has quit IRC11:07
*** rossella_s has quit IRC11:09
*** ccamacho is now known as ccamacho|lunch11:10
*** cloudrancher has quit IRC11:12
*** cloudrancher has joined #openstack-meeting-alt11:19
*** gcb has quit IRC11:19
*** chhavi has quit IRC11:20
*** tenobreg has joined #openstack-meeting-alt11:21
*** cloudrancher has quit IRC11:23
*** rossella_s has joined #openstack-meeting-alt11:23
*** lennyb_ has quit IRC11:24
*** lennyb has quit IRC11:24
*** lennyb has joined #openstack-meeting-alt11:25
*** lennyb has quit IRC11:27
*** lennyb has joined #openstack-meeting-alt11:28
*** lennyb_ has joined #openstack-meeting-alt11:29
*** lennyb has quit IRC11:29
*** lennyb_ has quit IRC11:29
*** lennyb has joined #openstack-meeting-alt11:30
*** dave-mccowan has joined #openstack-meeting-alt11:30
*** mickeys has joined #openstack-meeting-alt11:46
*** jchhatbar has joined #openstack-meeting-alt11:47
*** ansmith has quit IRC11:48
*** janki has quit IRC11:49
*** mickeys has quit IRC11:50
*** dprince has joined #openstack-meeting-alt12:04
*** pradk has joined #openstack-meeting-alt12:15
*** rossella_ has joined #openstack-meeting-alt12:15
*** rossella_s has quit IRC12:15
*** rfolco has joined #openstack-meeting-alt12:16
*** jaypipes has joined #openstack-meeting-alt12:18
*** rossella_ has quit IRC12:23
*** ccamacho|lunch is now known as ccamacho12:24
*** markstur has joined #openstack-meeting-alt12:25
*** rarcea_ has quit IRC12:29
*** markstur has quit IRC12:29
*** rossella_ has joined #openstack-meeting-alt12:33
*** jpena is now known as jpena|lunch12:34
*** stingaci has joined #openstack-meeting-alt12:38
*** chhavi has joined #openstack-meeting-alt12:39
*** yamahata has quit IRC12:40
*** funzo has joined #openstack-meeting-alt12:42
*** bfernando has joined #openstack-meeting-alt12:43
*** ansmith has joined #openstack-meeting-alt12:43
*** mickeys has joined #openstack-meeting-alt12:46
*** mickeys has quit IRC12:51
*** trinaths has quit IRC12:55
*** markstur has joined #openstack-meeting-alt12:55
*** markstur has quit IRC12:59
*** shuyingy_ has quit IRC13:00
*** jheroux has joined #openstack-meeting-alt13:01
*** salv-orlando has joined #openstack-meeting-alt13:01
*** salv-orlando has quit IRC13:07
*** salv-orlando has joined #openstack-meeting-alt13:07
*** salv-orlando has quit IRC13:21
*** markvoelker has joined #openstack-meeting-alt13:22
*** trinaths has joined #openstack-meeting-alt13:24
*** trinaths has left #openstack-meeting-alt13:24
*** markstur has joined #openstack-meeting-alt13:25
*** xyang1 has joined #openstack-meeting-alt13:27
*** gcb has joined #openstack-meeting-alt13:28
*** markstur has quit IRC13:29
*** kylek3h has quit IRC13:30
*** jpena|lunch is now known as jpena13:31
*** jchhatbar has quit IRC13:33
*** baoli has joined #openstack-meeting-alt13:34
*** markvoelker has quit IRC13:35
*** markvoelker has joined #openstack-meeting-alt13:35
*** dimtruck is now known as zz_dimtruck13:40
*** shuyingya has joined #openstack-meeting-alt13:40
*** zz_dimtruck is now known as dimtruck13:40
*** shuyingya has quit IRC13:44
*** markstur has joined #openstack-meeting-alt13:44
*** shuyingya has joined #openstack-meeting-alt13:45
*** cloudrancher has joined #openstack-meeting-alt13:45
*** tenobreg has quit IRC13:45
*** mickeys has joined #openstack-meeting-alt13:47
*** myoung|pto is now known as myoung_13:48
*** felipemonteiro has joined #openstack-meeting-alt13:49
*** markstur has quit IRC13:49
*** dimtruck is now known as zz_dimtruck13:49
*** felipemonteiro_ has joined #openstack-meeting-alt13:51
*** cloudrancher has quit IRC13:51
*** mickeys has quit IRC13:52
*** sridharg has quit IRC13:52
*** markstur has joined #openstack-meeting-alt13:52
*** rossella__ has joined #openstack-meeting-alt13:54
*** felipemonteiro has quit IRC13:54
*** rossella_ has quit IRC13:55
*** cdent has joined #openstack-meeting-alt13:56
*** kylek3h has joined #openstack-meeting-alt13:56
*** cloudrancher has joined #openstack-meeting-alt13:56
*** links has quit IRC13:57
*** tenobreg has joined #openstack-meeting-alt13:58
*** mmedvede has quit IRC13:58
*** anilvenkata has joined #openstack-meeting-alt13:59
*** dtantsur has joined #openstack-meeting-alt14:00
*** diga has joined #openstack-meeting-alt14:01
*** lei-zh has joined #openstack-meeting-alt14:01
*** mmedvede has joined #openstack-meeting-alt14:01
cdentedleafe: you back from pycon or you need someone else on this gig?14:01
*** cloudrancher has quit IRC14:01
cdent#startmeeting nova_scheduler14:01
openstackMeeting started Mon May 22 14:01:57 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:02
openstackThe meeting name has been set to 'nova_scheduler'14:02
cdentjaypipes, bauzas anyone else, shall we do this, or is there no need today?14:02
jaypipessorry, was emailng ;)14:02
bauzaswell14:02
bauzasgood question14:02
bauzasedleafe is not there14:02
bauzasso I wonder if we really need it14:03
digao/14:03
jaypipescdent: spent this morning getting all my scheduler-related patches in order (other then the nested resource providers stuff).14:03
*** salv-orlando has joined #openstack-meeting-alt14:03
cdent#action everyone review all of jaypipes' updated stuff14:03
*** cloudrancher has joined #openstack-meeting-alt14:03
bauzasjust one thing we discussed last week was around letting people know what we discussed during Summit14:03
bauzasand we postponed it14:03
*** bogdando_ has joined #openstack-meeting-alt14:03
jaypipescdent: so reviews on those series (https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/shared-resources-pike) and https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/resource-provider-traits) would be appreciated.14:03
bauzasso, not sure we would really need that given mriedem's emails14:03
*** rossella__ has quit IRC14:03
* alex_xu reads some recap email, that is helpful14:04
cdent#link shared rps https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/shared-resources-pike14:04
jaypipesalex_xu: indeed. I'm reading a bunch of those emails todya...14:04
*** rossella__ has joined #openstack-meeting-alt14:04
cdent#link last bits of traits https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/resource-provider-traits14:04
alex_xujaypipes: :)14:04
*** bogdando has quit IRC14:04
*** bogdando_ is now known as bogdando14:04
jaypipesalex_xu: now that the GFWoC is not blocking me from emailing people ;)14:04
alex_xuhah14:05
cdentbauzas: I agree that mriedem's email provided good coverage14:05
cdentbauzas: you reported in the nova channel that your stuff is ready for review, correct?14:06
bauzasyup, until the last one about the conductor change14:06
cdent#link claims in * https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/placement-claims14:06
bauzasI just discovered a bug with ChanceScheduler14:06
cdentas ya do14:06
bauzasso I provided a bugfix given it's needed for functionaltests14:06
bauzascdent: series starts with https://review.openstack.org/#/c/460177/914:07
cdent#link fixing chance scheduler: https://review.openstack.org/#/c/46672514:07
bauzasas we have an alternative series possibly confusing for reviews14:07
*** cloudrancher has quit IRC14:07
cdent#link main series of claims starts at https://review.openstack.org/#/c/460177/14:07
*** salv-orlando has quit IRC14:08
cdentso other than doing a bunch of reviewing, anyone have anything else?14:08
bauzasI have a question for continuing the series14:09
*** rossella__ has quit IRC14:09
cdentI'll say that there are a fair few changes in last week's rp update email message that are not in the mainline of stuff (bug fixes etc) that could do with some review to get them moved along14:09
bauzasnow that we agreed on passing the alternative hosts to the compute node for rescheduling needs, should we pass the ReqSpec object to compute node ?14:09
bauzasI tend to think so14:09
*** zz_dimtruck is now known as dimtruck14:09
bauzasbecause it would cleanup the compute RPC interface14:09
bauzasbut it would require a bit more of work14:10
*** lujinluo has joined #openstack-meeting-alt14:10
*** bogdando has quit IRC14:10
* alex_xu and lei-zh plans to restore the spec https://review.openstack.org/351063, and plan some PoC14:10
*** bogdando has joined #openstack-meeting-alt14:11
*** adisky_ has quit IRC14:11
cdentbauzas: i thought we decided we'd avoid changing the compute rpc interface?14:11
bauzascdent: for the spec, yes14:11
cdent#link request standardized capabilities spec: https://review.openstack.org/#/c/460177/14:12
cdent#undo14:12
openstackRemoving item from minutes: #link https://review.openstack.org/#/c/460177/14:12
bauzascdent: now that we discussed at the Forum and operators agreed on using alternative hosts, then it would mean that we would need to persist the alternatives somewhere instead of passing them thru RPC14:12
cdent#link request standardizd capabilities spec to be restarted: https://review.openstack.org/#/c/351063/14:12
bauzasan alternative approach would be to store the alternatives in the Spec object (and persist those) so that a reschedule would lookup those by getting the former Spec14:13
bauzasthat wouldn't require any RPC change14:13
cdentwhich services need to know about the alternatives?14:15
cdenti thought it was just the conductor?14:17
*** rossella__ has joined #openstack-meeting-alt14:17
*** skramaja has quit IRC14:18
bauzasyup, agreed14:18
bauzasokay, so, let's see what other think about persisting the alternatives by the conductor so reschedules within the conductor will lookup those14:18
cdentwhen you say persisted, are you meaning "written to disk so some other process might be able to pick them up later"?14:19
cdentif so, let's not do that, if possible14:19
bauzascdent: the problem is that we have distributed conductors14:20
cdenti know14:20
cdentbut we also have a shared data store14:20
bauzascdent: so persisting in memory would mean that if we reschedule to another conductor, it doesn't know the former Spec14:20
cdentI think it may be better to avoid data duplication at the cost of a slight loss of performance.14:21
bauzascdent: which is ?14:21
*** johnma has quit IRC14:21
bauzascdent: sorry for my ignorance14:21
bauzaswhen I said "persisted", I meant written in DB14:21
bauzasbut I'm open to ideas14:21
cdentcorrect, but we can already "calculate" that information from the data in placement14:22
cdentpersisting placement's decisions in the conductor's view of the db is an early optimization (to me)14:22
bauzascdent: unfortunately, it's not a placement information14:22
cdentyou're talking about the clumping into cell's, right?14:23
bauzascdent: because placement returns all acceptable nodes, and then we pick only a few of them and we sort them14:23
bauzasnope, about the fact we pass alternative hosts to the conductor based on filtering/weighting feedback14:23
bauzasfor placement, all hosts are equal14:23
cdentright, but what I'm getting at is that that filtering/weighing (and the additional cell clumping) should be treated as if it is fast14:24
cdentif it is not, we should fix that, not come up with additional architectural complexity to compensate for it14:24
bauzascdent: filtering/weighting is fast, yes14:25
cdentor, if we do need architectural complexity, we should just leapfrog to having a real global shared cache14:25
bauzascdent: and later will be something done by conductor hopefully14:25
cdentIf we reschedule to another conductor, I really don't see that much of a problem with re-creating the result set that it needs14:26
cdentor we should at least write that first, and then tune it up later14:27
bauzascdent: meaning calling again the scheduler to get the new list of alternatives ?14:27
cdentyes14:27
bauzasmaybe14:27
bauzasI see your point14:27
bauzasas the claim is done by the conductor, I'm fine with both possibilities14:27
bauzasbut keep in mind that cell-local conductors can't upcall scheduler14:28
jaypipesagree with cdent on this.14:28
bauzaswhich is all the crux of the problem14:28
bauzasjaypipes: agreeing on calling again the scheduler ? that can't work for the reason I just said :(14:29
*** markvoelker_ has joined #openstack-meeting-alt14:29
bauzasmid-term, I see filters and weighers as part of the conductor, so it's fine14:30
cdentunder what circumstances does a reschedule go to a different conductor?14:30
bauzascdent: in a cells v2 world14:30
bauzascdent: schedule_and_build_instances() is a super-conductor method14:30
*** cknight has joined #openstack-meeting-alt14:30
bauzascdent: while build_instances() is just purely local14:31
cdentyes, I know that much14:31
cdentwhen would a build_instances happen in a same cell, but on a different conductor?14:31
*** EricGonczer_ has joined #openstack-meeting-alt14:31
bauzasif you have 2 conductors, you can end up on a separate worker, right?14:32
bauzasunless I misunderstand your question14:32
jaypipesbauzas: I was agreeing on the premature optimization comment by cdent.14:32
*** markvoelker has quit IRC14:33
bauzasanyway, seems we're having a design discussion now and I didn't wanted to diverge that much14:33
cdentsub-conductor A has received a build_instances call that fails for some reason. Now at this point can it be a different conductor that tries to recover from that? If so, who/what is making that decision?14:33
cdentbauzas: Thanks for indulding me here, I'm trying to understand the process a bit more clearly because some of these details sometimes get left out.14:34
cdent(and anyway, we've got nothing else on the agenda)14:34
*** david-lyle has quit IRC14:34
bauzascdent: schedule_and_build_instances() call the compute node thru cells V2 MQ switching14:34
bauzascdent: if the compute node fails, it triggers a call to a conductor.build_instances() method which is not MQ switching to the global MQ14:34
*** david-lyle has joined #openstack-meeting-alt14:35
*** dustins has joined #openstack-meeting-alt14:35
cdentah, this is the detail that was unclear to me: I was assuming the compute node returned some form of results to the same conductor, but I guess that wouldn't make sense because we want the request and the response to be async14:36
bauzascdent: I can point you to some code if you will, but let's do that offline14:36
cdentI think that's given me enough to do my own digging14:37
*** dustins has quit IRC14:37
cdentI just wanted to make sure I had a more clear view on the situation than I did before14:37
bauzasokay np14:37
cdentanybody got anything else or should we end the meeting?14:38
bauzasalso, let's state that here, as said in the nova channel, I'll offline for Tuesday afternoon my time to Friday included14:38
*** diablo_rojo has joined #openstack-meeting-alt14:41
*** shuyingy_ has joined #openstack-meeting-alt14:41
*** dustins has joined #openstack-meeting-alt14:41
*** cloudrancher has joined #openstack-meeting-alt14:41
cdenteverybody good?14:42
cdentjaypipes, alex_xu ?14:42
jaypipescdent: yup14:42
cdentcool14:42
cdent#endmeeting14:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:42
openstackMeeting ended Mon May 22 14:42:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-05-22-14.01.html14:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-05-22-14.01.txt14:42
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-05-22-14.01.log.html14:43
jaypipescdent: thx for running the meeting.14:43
cdentpleasure was all mine14:43
*** shuyingya has quit IRC14:43
*** dtantsur has left #openstack-meeting-alt14:43
*** EricGonczer_ has quit IRC14:44
*** cloudrancher has quit IRC14:46
*** tenobreg has quit IRC14:47
*** lei-zh has quit IRC14:47
*** mickeys has joined #openstack-meeting-alt14:48
*** yamahata has joined #openstack-meeting-alt14:51
*** david-lyle has quit IRC14:52
*** salv-orlando has joined #openstack-meeting-alt14:52
*** mickeys has quit IRC14:52
*** diablo_rojo has quit IRC14:54
*** diablo_rojo has joined #openstack-meeting-alt14:54
*** salv-orlando has quit IRC14:57
*** d0ugal has quit IRC14:57
*** fzdarsky is now known as fzdarsky|afk14:58
*** shuyingy_ has quit IRC14:58
*** andreas_s has quit IRC14:59
*** dizquierdo has quit IRC14:59
*** ihrachys has joined #openstack-meeting-alt15:01
ihrachys#startmeeting neutron_upgrades15:01
openstackMeeting started Mon May 22 15:01:22 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/15:01
lujinluoo/15:01
ihrachyshi lujinluo15:02
ihrachysanyone else?15:02
lujinluohi ihrachys , maybe we can wait for a while15:02
manjeetshi15:04
*** cdent has left #openstack-meeting-alt15:04
manjeetssorry for being late15:04
ihrachyshi manjeets15:04
lujinluohi manjeets15:05
ihrachyslet's have a look at the action items from the last time we met15:05
ihrachys#topic Action items from prev meeting15:05
*** openstack changes topic to "Action items from prev meeting (Meeting topic: neutron_upgrades)"15:05
ihrachysfirst was "ihrachys to respin metering OVO patch: https://review.openstack.org/#/c/433125/"15:05
ihrachysthe patch is merged, good15:05
ihrachysnext was "tonytan4ever to respin LIKE patches"15:06
*** bobmel has quit IRC15:06
ihrachysthe patch went through several iterations since then: https://review.openstack.org/#/c/419152/15:06
*** d0ugal has joined #openstack-meeting-alt15:07
*** andreas_s has joined #openstack-meeting-alt15:08
ihrachyswe can discuss it later in OVO section15:09
ihrachysnext was "manjeets to take over neutron-db-manage CLI command for data migration"15:09
manjeetsI did few changes but i had one question how are we gonna populate migration scripts15:10
ihrachysI saw manjeets respinned the patch, thanks for that.15:10
manjeetsas victor had only one example script and using that15:10
manjeetsare we gonna have a separate folder for all those scripts and call from there ?15:10
ihrachysmanjeets, well I thought that we will have a stevedore namespace where we would expose those 'scripts'15:11
ihrachysand then it's a matter of taste where we keep the code in-tree15:11
ihrachysa separate dir probably makes sense15:12
manjeetsohk, i'll work on that this week15:12
ihrachysbut there should still be some level of indirection15:12
ihrachysfor external projects to be able to provide their own scripts15:12
ihrachysok cool15:12
ihrachysnext was "manjeets to try craft out cycles for SG adoption patch"15:12
ihrachysit's this patch:15:13
ihrachyshttps://review.openstack.org/#/c/28473815:13
ihrachysoh I see it has two +2s15:13
ihrachysI gotta review and merge it after the meeting then ;)15:13
*** rossella__ has quit IRC15:13
ihrachysthanks for respin15:13
ihrachysand that's all we had15:13
ihrachysfor work items I mean15:14
ihrachys#topic OVO15:14
*** openstack changes topic to "OVO (Meeting topic: neutron_upgrades)"15:14
ihrachyshttps://review.openstack.org/#/q/topic:bp/adopt-oslo-versioned-objects-for-db+status:open15:14
manjeetsmay be we should start taking ownership of these patches and get it done15:15
manjeetsas most of them have changed their jobs15:15
ihrachysyeah15:15
*** dane_ has joined #openstack-meeting-alt15:15
lujinluoagree. now I am not sure which patches are unmaintained15:16
ihrachyslet's walk through those that fell through cracks15:16
ihrachysRouter: https://review.openstack.org/#/c/307964/15:16
ihrachysI think lujinluo started looking at it correct?15:16
lujinluoyes15:16
ihrachysok. what's missing besides the eager load thing? https://review.openstack.org/#/c/466237/15:17
lujinluol3 agents as a synthetic field15:17
ihrachysis it something router-l3-agent-binding patch helps with? https://review.openstack.org/#/c/377074/15:18
lujinluothis is may due to my lack of knowledge, but i'm not sure how to load only l3 agents but not all agents..15:18
lujinluoi have not checked that patch. will do after the meeting15:18
ihrachysand why is it needed that we expose agents through synthetic field exactly?15:19
lujinluohttps://github.com/openstack/neutron/blob/master/neutron/db/models/l3.py#L62-#L64 here and https://github.com/openstack/neutron/blob/master/neutron/db/l3_agentschedulers_db.py#L560 here15:20
lujinluoin my current integration patch, I can call through router.db_obj.l3_agents but i am not sure if it is a good idea to keep it calling from db15:20
*** mjura has quit IRC15:21
ihrachysif it's exposed on db_obj.l3_agents you should be able to extract it from there on from_db_object.15:22
*** yamahata has quit IRC15:22
lujinluothen we do not need to expose l3 agents as synthetic field?15:23
ihrachysI think your links suggest that there is a use case to extract the list of agents from the router. so I now merely say that probably you should have all needed to implement such a field15:25
ihrachyslet's continue in the review, I will have a look. I also take over the binding patch since Anindita left.15:26
lujinluook, thanks15:27
ihrachysmanjeets, is Toni still with us to follow up on LIKE patch? https://review.openstack.org/41915215:27
manjeetsihrachys, I am not sure about he was with rackspace15:27
*** johnma has joined #openstack-meeting-alt15:27
ihrachysI don't see him in this channel right now.15:28
ihrachyslet me ask him on gerrit. if not, I will take over, the patch is very close.15:28
*** fzdarsky|afk is now known as fzdarsky15:28
manjeetsok sounds good15:28
*** ccamacho is now known as ccamacho|brb15:29
*** namnh has joined #openstack-meeting-alt15:29
ihrachysthe dvr mac address is also on Tony, I will try to understand if he is still with us, and we can discuss that next time.15:30
ihrachysnext is allocation/endpoints from Anindita: https://review.openstack.org/#/c/367810/15:30
ihrachysit's on WIP15:30
*** trungnv has quit IRC15:30
manjeetsihrachys, I may take over one or two, I have to attend a conference this week15:30
ihrachysoh that's because of update_objects missing.15:30
manjeetsi'll comment on gerrit after reviewing15:30
manjeetsfor taking over15:31
ihrachysmanjeets, which one do you want to take?15:31
*** myoung_ is now known as myoung15:31
ihrachysallocations?15:31
ihrachysit depends on https://review.openstack.org/#/c/452266/ that is on me right now.15:32
ihrachysI will bubble up that one in my todo list15:32
*** pnavarro has quit IRC15:32
manjeetsohk I'll take allocations15:32
ihrachysas for endpoints, it may need to wait until the update_objects completion.15:32
ihrachysmanjeets, note it's not clear if update_objects is ok in the shape it is right now.15:33
*** dizquierdo has joined #openstack-meeting-alt15:33
manjeetsI'll spare some time to review these15:33
ihrachysok good15:34
ihrachysnext in the queue is dhcp agent network binding: https://review.openstack.org/#/c/370452/15:34
ihrachysI believe Nakul is no longer15:34
ihrachysKevin tried to respin it in the past15:34
manjeetsyes he left15:34
*** markvoelker_ has quit IRC15:35
manjeetsseems like patch is close just need to address few comments from kevin15:35
*** lpetrut has quit IRC15:35
ihrachysthe patch would really benefit from someone taking over it.15:35
ihrachysyeah and those comments seem to be nit15:35
ihrachysmanjeets, so maybe you can look at it instead of endpoints?15:35
manjeetssure15:35
*** cloudrancher has joined #openstack-meeting-alt15:35
ihrachysnice15:35
*** salv-orlando has joined #openstack-meeting-alt15:36
ihrachysnext is ip allocation pool: https://review.openstack.org/#/c/39671115:36
ihrachysthis one seems to be a no-brainer really15:36
ihrachysvery small, very simple15:37
ihrachysshame it's not in yet15:37
ihrachysanyone want to take it? maybe lujinluo ?15:37
lujinluosure :)15:37
*** dizquierdo has quit IRC15:38
ihrachysthanks l15:38
ihrachysmeh :) that was awkward. thanks lujinluo15:38
*** shuyingya has joined #openstack-meeting-alt15:39
ihrachysthe next was ip allocation: https://review.openstack.org/#/c/396718/15:39
ihrachysthat one seemed fine, but has some functional test issue15:39
*** rossella__ has joined #openstack-meeting-alt15:39
*** cloudrancher has quit IRC15:40
ihrachysshould be an easy thing to land if we tackle the test15:40
lujinluoi can try to take care of it too15:40
ihrachysthanks!!15:40
lujinluono problem!15:41
ihrachysdo we want to go forward in the list or we have enough on our plates already?15:41
*** gyee has joined #openstack-meeting-alt15:42
ihrachysmanjeets, lujinluo ?15:42
manjeetsI'd say lets get these done first, if anyone wants to take ove, just comment over gerrit and go ahead with re spinning15:42
*** SumitNaiksatam has quit IRC15:42
lujinluoi think i have enough15:42
ihrachysok, let's focus on those, and we will revisit the list next time.15:43
*** shuyingya has quit IRC15:43
ihrachysthere are no new UpgradeImpact tagged patches.15:43
ihrachysI am also not aware of any ongoing work in gate for upgrade use cases.15:44
ihrachyswith that...15:44
ihrachys#topic Open discussion15:44
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:44
ihrachys...do we have anything else to discuss?15:44
lujinluoi have 1 question15:44
ihrachysshoot15:44
lujinluomy employer is pushing about this for a long time. are we still target OVO for Pike?15:44
*** belmoreira has quit IRC15:45
ihrachysI think we have a good chance to complete most of the OVO work this cycle. I should have some more time, again, to work on it.15:46
ihrachyslujinluo, that being said, who's the employer, and which use cases do they have in mind?15:46
ihrachysare we talking more about online-upgrades as the real thing they are interested in? because OVO is just code restructuring/framework thing.15:47
ihrachysthey are interrelated but not the same15:47
lujinluoi am employed by fujitsu. i do not think my manager has any specific use cases for OVO yet, but he purely wants to see it land asap15:47
lujinluoi also explained that online-upgrades do not really require OVO15:47
ihrachysI see. this work is definitely on the high priority radar for Pike. PTL is supportive and even said he will have some cycles to push it forward which is promising.15:48
*** mickeys has joined #openstack-meeting-alt15:49
ihrachysdoes it answer the question?15:49
lujinluook, i will try to explain this to him too, thanks15:49
lujinluosure, it does15:49
ihrachysok cool15:49
lujinluosorry, i have one more to manjeets15:49
manjeetssure15:49
ihrachysshoot again ;)15:49
*** andreas_s has quit IRC15:50
lujinluoregarding online data migration, i have a patch under reviewing that may be used as another script migration example. https://review.openstack.org/#/c/288271/  i hope so15:50
*** bobmel_ has joined #openstack-meeting-alt15:51
ihrachysmmm, thanks for pointing it out. I need to have a look at how it will play with rolling upgrades. it seems very similar to multiple port bindings case in terms of database evolution.15:51
lujinluoihrachys, yes, please, this is why I link it here15:52
manjeetsi'll review that15:52
lujinluoand that's all from me ;)15:53
*** bogdando has quit IRC15:53
*** mickeys has quit IRC15:53
*** JudeC has joined #openstack-meeting-alt15:53
ihrachysgreat. you seem busy with different things. :)15:54
ihrachysI bet you are also good at juggling :)15:54
ihrachysok15:54
lujinluo;)15:54
ihrachysif nothing else, I end the meeting in 315:54
ihrachys215:54
manjeets115:55
ihrachys115:55
ihrachysboom!15:55
lujinluo015:55
ihrachysthanks everyone15:55
manjeetsthanks !!15:55
ihrachys-115:55
ihrachys#endmeeting15:55
lujinluothank you!15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Mon May 22 15:55:13 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-05-22-15.01.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-05-22-15.01.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-05-22-15.01.log.html15:55
*** lujinluo has quit IRC15:57
*** cloudrancher has joined #openstack-meeting-alt16:01
*** slaweq has joined #openstack-meeting-alt16:01
*** david-lyle has joined #openstack-meeting-alt16:03
*** slaweq has quit IRC16:04
*** adrian_otto has joined #openstack-meeting-alt16:04
*** matrohon has quit IRC16:06
*** fnaval has joined #openstack-meeting-alt16:06
*** SumitNaiksatam has joined #openstack-meeting-alt16:07
*** trungnv has joined #openstack-meeting-alt16:12
*** dizquierdo has joined #openstack-meeting-alt16:12
*** florianf has quit IRC16:14
*** mikal has quit IRC16:14
*** rcernin has quit IRC16:14
*** mikal has joined #openstack-meeting-alt16:16
*** mickeys has joined #openstack-meeting-alt16:18
*** SumitNaiksatam has quit IRC16:24
*** neiljerram has quit IRC16:30
*** rcernin has joined #openstack-meeting-alt16:31
*** ltomasbo is now known as ltomasbo|away16:32
*** slaweq has joined #openstack-meeting-alt16:34
*** kjw3 has joined #openstack-meeting-alt16:37
*** neiljerram has joined #openstack-meeting-alt16:39
*** salv-orlando has quit IRC16:40
*** trungnv has quit IRC16:45
*** diga has quit IRC16:46
*** pbourke has quit IRC16:46
*** jpena is now known as jpena|off16:47
*** bfernando has quit IRC16:53
*** ralonsoh has quit IRC16:57
*** derekh has quit IRC16:59
*** namnh has quit IRC16:59
*** dprince has quit IRC17:00
*** salv-orlando has joined #openstack-meeting-alt17:01
*** kzaitsev_ws has quit IRC17:04
*** slaweq has quit IRC17:05
*** salv-orlando has quit IRC17:05
*** trinaths has joined #openstack-meeting-alt17:06
*** sshank has joined #openstack-meeting-alt17:09
*** crazymozart1 has joined #openstack-meeting-alt17:10
*** rarcea has quit IRC17:11
*** marst_ has joined #openstack-meeting-alt17:13
*** crazymozart has quit IRC17:13
*** jprovazn has quit IRC17:14
*** trinaths has quit IRC17:14
*** dprince has joined #openstack-meeting-alt17:14
*** anilvenkata has quit IRC17:22
*** reedip__ has joined #openstack-meeting-alt17:32
*** markstur has quit IRC17:36
*** Sukhdev has joined #openstack-meeting-alt17:43
*** tonanhngo has joined #openstack-meeting-alt17:48
*** cloudrancher has quit IRC17:49
*** yamahata has joined #openstack-meeting-alt17:49
*** cloudrancher has joined #openstack-meeting-alt17:49
*** kjw3 has quit IRC17:49
*** dizquierdo has quit IRC17:56
*** sambetts is now known as sambetts|afk17:59
*** Sukhdev has quit IRC18:01
*** kjw3 has joined #openstack-meeting-alt18:02
*** crazymozart1 has quit IRC18:09
*** crazymozart1 has joined #openstack-meeting-alt18:09
*** ijw has quit IRC18:09
*** ganso has left #openstack-meeting-alt18:13
*** stingaci has quit IRC18:17
*** stingaci has joined #openstack-meeting-alt18:18
*** crazymozart1 has quit IRC18:18
*** gouthamr has joined #openstack-meeting-alt18:24
*** trinaths has joined #openstack-meeting-alt18:30
*** bobmel_ has quit IRC18:31
*** trinaths has left #openstack-meeting-alt18:31
*** dsariel has quit IRC18:31
*** sshank has quit IRC18:32
*** reedip__ has quit IRC18:35
*** harlowja has joined #openstack-meeting-alt18:37
*** markstur has joined #openstack-meeting-alt18:38
*** dave-mccowan has quit IRC18:41
*** cloudrancher has quit IRC18:41
*** markstur has quit IRC18:42
*** harlowja has quit IRC18:43
*** yamahata has quit IRC18:45
*** dprince has quit IRC18:47
*** cloudrancher has joined #openstack-meeting-alt18:48
*** cloudrancher has quit IRC18:52
*** gouthamr has quit IRC18:54
*** kzaitsev_mb has joined #openstack-meeting-alt18:57
*** dprince has joined #openstack-meeting-alt18:57
*** MeganR has joined #openstack-meeting-alt18:59
*** AndyU has joined #openstack-meeting-alt19:03
*** markstur has joined #openstack-meeting-alt19:05
*** salv-orlando has joined #openstack-meeting-alt19:18
*** pnavarro has joined #openstack-meeting-alt19:23
*** slaweq has joined #openstack-meeting-alt19:24
*** bobmel has joined #openstack-meeting-alt19:25
*** salv-orlando has quit IRC19:28
*** mickeys has quit IRC19:32
*** SumitNaiksatam has joined #openstack-meeting-alt19:33
*** mathiasb has quit IRC19:42
*** stingaci has quit IRC19:44
*** mathiasb has joined #openstack-meeting-alt19:44
*** cloudrancher has joined #openstack-meeting-alt19:45
*** adrian_otto has quit IRC19:46
*** chhavi has quit IRC19:48
*** slaweq has quit IRC19:49
*** slaweq has joined #openstack-meeting-alt19:49
*** JudeC has quit IRC19:50
*** slaweq has quit IRC19:55
*** slaweq__ has joined #openstack-meeting-alt19:55
*** johnma has quit IRC19:56
*** JudeC has joined #openstack-meeting-alt19:56
*** salv-orlando has joined #openstack-meeting-alt19:56
*** cloudrancher has quit IRC19:57
*** johnma has joined #openstack-meeting-alt19:58
*** blancos has joined #openstack-meeting-alt19:59
*** MeganR has quit IRC20:03
*** stingaci has joined #openstack-meeting-alt20:04
*** johnma has quit IRC20:06
*** stingaci has quit IRC20:08
*** blancos has left #openstack-meeting-alt20:11
*** arunkant_ has joined #openstack-meeting-alt20:12
*** arunkant_ has quit IRC20:13
*** stingaci has joined #openstack-meeting-alt20:14
*** stingaci has quit IRC20:14
*** stingaci has joined #openstack-meeting-alt20:14
*** dimtruck is now known as zz_dimtruck20:14
*** ijw has joined #openstack-meeting-alt20:21
*** crazymozart1 has joined #openstack-meeting-alt20:24
*** stingaci has quit IRC20:29
*** dprince has quit IRC20:32
*** bobmel has quit IRC20:39
*** salv-orlando has quit IRC20:39
*** bobmel has joined #openstack-meeting-alt20:39
*** salv-orlando has joined #openstack-meeting-alt20:40
*** leong has joined #openstack-meeting-alt20:44
*** salv-orlando has quit IRC20:44
*** mickeys has joined #openstack-meeting-alt20:47
*** ansmith has quit IRC20:48
*** ijw_ has joined #openstack-meeting-alt20:51
*** jlk has joined #openstack-meeting-alt20:53
*** adrian_otto has joined #openstack-meeting-alt20:53
*** ijw has quit IRC20:55
*** gouthamr has joined #openstack-meeting-alt20:55
*** Shrews has joined #openstack-meeting-alt20:56
*** MeganR has joined #openstack-meeting-alt20:57
*** shamail has joined #openstack-meeting-alt20:57
*** felipemonteiro_ has quit IRC20:59
*** s3wong has joined #openstack-meeting-alt20:59
*** armstrong has joined #openstack-meeting-alt20:59
*** rockyg has joined #openstack-meeting-alt20:59
leong#startmeeting product_working_group21:00
openstackMeeting started Mon May 22 21:00:29 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
leong#topic Rollcall21:01
*** openstack changes topic to "Rollcall (Meeting topic: product_working_group)"21:01
leonghi welcome to PWG meeting :)21:01
leongroll calling....21:01
rockygo/21:01
MeganRo/21:01
shamailHi everyone21:01
leong#link Agenda https://wiki.openstack.org/wiki/Meetings/product-team21:02
jamemccHi21:02
leongtoday agenda can be found at the above link21:02
leongbefore we start.. anybody has any agenda item to add?21:02
leonglet's get going...21:03
leong#topic Boston Forum/Summit Recap21:03
*** openstack changes topic to "Boston Forum/Summit Recap (Meeting topic: product_working_group)"21:03
leongi set this topic so that the team can do a quick recap from Boston Forum/Summit21:04
jamemccOn March 14 we were going to talk about Feature Tracker status - not sure if we have the right people - but if so - lets cover that21:04
*** dave-mccowan has joined #openstack-meeting-alt21:05
leongjamemcc? March 14?21:05
jamemccAt our agenda link - just scroll down to "CANCELLED March 14th..."21:05
leongjamemcc: that was the regional meeting21:06
*** jlk has left #openstack-meeting-alt21:06
leongi recalled that was about writing the feature tracker json for baremetal user story21:06
jamemccOK, if not appropriate but I think there seems to be a lot of confusion on why the various Feature Tracker stories are not implemented and wanted to get status or issue out on that.21:07
*** bobmel has quit IRC21:08
*** bobmel has joined #openstack-meeting-alt21:08
leongon the Summit/Forum, anyone has any feedback?21:09
rockygActually, good point.  I think we need to list the barriers for each of the features.  I think that would help in figuring out what is blocking them.21:09
shamailI think the forum went well and we had a good mix of participants in each session. Lots of dialogue on how to more closely collaborate between users and developers. On the flipside, there were a lot of team including this one that saw a decline in active contributors.21:09
jamemccI think we dont' ahve the right people - I'll try to start in mail21:09
rockygThanks, jamemcc21:09
rockygYes,  this group seems to be losing participants quickly.21:09
shamailJamemcc: Adam wants to create a tracker for HA VMs. I'll forward his email to us again.21:10
leonghow should we deal with the decline in PWG active contributors?21:11
shamailrockyg: yes, even BoF only had like 8 people21:11
rockygI think it might be because the roadmap is running smoothly, mostly and the user stories are not moving well.  So, the view is the PWG is not getting stuff done because people don't attribute the roadmp to us any more.21:11
leongwe have tried presented the challenges to Board, and also seek support from Board companies21:11
shamailrockyg: +121:12
leongrockyg: +121:12
rockygI have an idea, but first I have to present it to myh management and see if they will give me the time to do it.  I am going to ask them to put me 80% on PWG only for a cycle.21:13
leongit seems to be lots of challenges in "gettting stuff done"21:13
shamailI don't know how to solve this but we either need new members or a change in scope21:13
*** gouthamr has quit IRC21:13
rockygI think we had the manpower/time to get the roadmap rolling and now it takes less.  We need to do the same to jumpstart the development proposals21:13
leongAnni and I are going to have a talk at OpenStack China Day about Product WG, that "might" help to get some new members...21:14
leongfrom the Dev Proposals, we need to collaborate with other WG such as LCOO, Scientific, Public Cloud21:14
rockygThat's why I'm asking for 80% time.  So I can do some of that research/chasing bits/etc to get some of the features to something acceptable to devs.21:14
shamailThere were a lot of great action items for us coming out of the summit like making the roadmap bidirectional, helping teams prioritize21:14
leongwe should get resoures/help from those WG21:15
rockygleong, ++ but I think they are mostly in the same boat as us.21:15
leongi think we need to shift from a focus to "driving user story" to "providing a platform for WG so that WG themselves can drive the user story"21:16
leongalso alignment with the UC "unanswered requirements"21:17
shamailWe also discussed helping newer companies to OpenStack find the big rocks to work on21:17
*** gouthamr has joined #openstack-meeting-alt21:17
shamailleong:+121:17
*** adrian_otto has quit IRC21:17
rockyg++21:18
leongso maybe the next action item for PWG can focus more around "collaborating with various WG based on the same PWG dev proposal platform"?21:18
jamemccAgreed with "platform for the WG to drive their own user stories"  but I also think that most - LCOO certainly may struggle to find the right ways to get together with the project tems and that Rocky's suggestion seems helpful.21:19
shamailPlatform would include our team helping make the right connections at the project level21:20
jamemccGreat21:20
leongshamail: +121:20
shamailWe would help with properly documenting ideas, getting a structured workflow, and integration into development workflow21:21
leongwill be great if we can get the right people both from the project team and working groups to discuss on the Dev Proposal21:21
leongshamail: +121:21
leongwould that change our overall mission statement or goal?21:22
jamemccI have to admit I hadnt' thought to invite PWG to the Development proposal discussions - Can and will do that21:23
shamailI think it does slightly, we would no longer represent the needs of the users ourselves but help teams that do get their voices heard21:23
*** ijw_ has quit IRC21:23
AndyU_Hi all. Sorry I'm late21:24
jamemccFYI - possibly one on the LCOO Containerized OpenStack management on Wednesday.21:24
shamailThanks jamemcc21:24
leongother than LCOO, that are also work that we can work with Public Cloud and Scientific WG21:25
*** shamail has quit IRC21:25
*** kaisers1 has quit IRC21:25
jamemcc#link https://review.openstack.org/#/c/445386/21:26
leongand interestingly that some features discussed in various WG can potentially the same with commonatilities21:26
leongthat can help "project team" to prioritize works that fit mulitple WG21:26
AndyU_Ok, I think I'm getting caught up skimming the above.21:26
AndyU_I think PWG can play a key role as an enabler of Dev proposals and similar efforts in general.21:27
*** shamail has joined #openstack-meeting-alt21:27
AndyU_Certainly one is to be actively engaged in the Dev Proposal process as enablers, SME's , etc., like we already have discussed.21:28
* leong looks like shamail was kicked out and rejoin :)21:28
shamail:)21:28
AndyU_But something that was a PWG muission initially (I heard at Summit) but not happening is very needed. More than 70% of all commits for Ocata were made by the 12 top contributing companies.21:29
*** jheroux has quit IRC21:30
*** stingaci has joined #openstack-meeting-alt21:30
leongi think the very initial mission for PWG is to get involvement from Vendor Product Managers, but that was not happening over the past year21:30
shamailWe had that, we lost it because we could not deliver on user stories21:30
shamailWe should've gotten both product managers and engineering managers so decisions could be made21:31
AndyU_All the working groups had a common there woven across about the problem of "unanswered requirements". The PWG can facilitate discussions with the big contributors to align around gap analysis, implementation plans for delivery21:31
leonghowever, i do think that we did deliver one user story which is the baremetal :)21:31
shamailRolling upgrades too21:31
AndyU_I don't think that the Product Managers fro Red Hat, Mirantis, etc. need to be PWG Members for the PWG to coordinate periodic meetings with them.21:32
leongRolling upgrade can be debatable because it was exist/already-dicussed prior to PWG user story21:32
shamailTrue21:32
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:32
shamailAndyU_: +121:33
Arkady_KanevskyHello Product WG21:33
leonganyway, instead of sticking to initial mission that aim for Product Managers from vendors, i think we need to move forward with "who we have today"21:33
AndyU_What's needed is to bring the right people together around the right issues and only perhaps a couple tuimes during each cycle (we'd have to figure that out).21:33
shamailLeong: Who we have/who we need21:34
AndyU_Askingall those Product Managers to be PWG members is too much. But asking them to join periodic coordination meetings hosted by the PWG is not. And it would be very valuable.21:35
*** stingaci has quit IRC21:35
rockygAndyU_, ++21:35
shamailAndyu_:agree, great idea 21:35
leongAndyu_: +1 coordination meetings21:36
AndyU_Basically coordinating that connection between the work being done in working groups/teams (Sigs?) and Key development players like Product Managers for big contribs and Key leaders in impacted dev teams21:36
shamailSo leong how is that for your forum recap?21:36
leonglet's wrap up this agenda topic21:37
leong#info PWG value: properly documenting ideas, getting a structured workflow, and integration into development workflow21:37
AndyU_That would be invaluable because it's needed, no one is doing it and the PWG has all the legitimacy to do it where perhaps no other group does?21:37
AndyU_Leong +11  :)21:37
mrhillsmansorry so late, i'm here21:37
leong#info PWG value: Periodic coordination meeting across WGs/Product Managers21:37
AndyU_Yes.21:38
leongthose are the two key items i can summarized from our discussion21:38
shamailIt's OK mrhillsman , you just missed the fun part of the meeting21:38
AndyU_PWG could also host/coordinate periodic syncs BETWEEN working groups as well. The need for that came out of the Forum session about avoiding wg redundancy21:38
leongAndyU_: +121:39
leong#info PWG value: coordinate/collaborate between WGs21:39
Arkady_Kanevskyother WG within user WG?21:39
leongWG can be within either UC or TC21:40
AndyU_We could analize what's being worked on, proposed, etc and help to get the right people connected, help the working parties to be focused (advise on strategy) and in alignment with other stakeholders21:40
leongone of the key action is to get those WG aware about PWG workflow and value21:40
AndyU_Leong, I agree. Doesn't matter where wg falls in UC vs TC21:40
*** kaisers has joined #openstack-meeting-alt21:40
AndyU_+1 to Dev Proposal workflow awareness21:41
*** gouthamr has quit IRC21:41
Arkady_KanevskyI think we should bring characterization of stories for UC WG to them.21:41
AndyU_In the Forum session about the Dev proposal process, it turned oyut no one but Leong and I had ever even heard of it ;)21:41
leongok.. let's think of some action plan for the 3 value mention earlier21:41
Arkady_KanevskyAs well as show that reqs we got from forum are perculating to stories21:42
leongi will summary and email to ML to get inputs21:42
leonglet's move on to the next agenda topic21:42
leong#topic Post-forum Report21:43
*** openstack changes topic to "Post-forum Report (Meeting topic: product_working_group)"21:43
leongi have run the hashtag program and generated the result, and submit a patch to upload those result to PWG repo21:43
leong#link Hashtag results: https://review.openstack.org/#/c/466401/21:44
AndyU_Here's another (maybe you discussed it already). What about the PWG creating Dev proposals ourselves if we know of a key need not being addressed and take on actually CREATING (or trying :) ) a wg to carry it forward?21:44
shamailThanks for doing it leong21:44
leongshamail: thanks for the +221:44
leongAndyU_: let's push that discussion to ML21:45
AndyU_I still need to read it. Anything jumping out?21:45
AndyU_got it21:45
mrhillsmani think one of the key things missing is maybe what rockyg was mentioning earlier; getting those who have developers to buy-in to the "process"21:45
leonggiven the hashtag result is ready, what and how do we want to deal with those data21:46
AndyU_Does it seem they were pretty well used or not so much?21:46
*** ijw has joined #openstack-meeting-alt21:46
rockygI looked over some of the results.  Interesting.  It also might be worthwhile to get the PTLs to add hashtags where they think they might be useful when they review their forum sessions to summarize on the mailing list.21:46
shamailleong: can you reply to John G's email aboutibg21:47
rockygAnd maybe put a link to the mailing list thread in the etherpad?21:47
AndyU_It almost seems like we'd have to look at Leong's data along side skimming the actual etherpads to get a sense for how well it's working and where we need to tune21:47
shamailPlans to email moderators21:47
leongshamail: yes i will reply to John G21:47
leong#action Leong to reply JohnG email on hashtag result21:47
mrhillsmana lot of the summaries are being only sent to openstack-dev21:48
mrhillsmani forwarded quite a few to openstack-operators but pretty sure i missed some21:48
leongi think it is critically important to have the summaries sent to both dev + uc21:48
mrhillsmanwe should have a tag [bos-forum-summary] or something too no?21:49
shamailThanks... we should analyze hash tags and also ask them what they think was the summary from their sessionand encourage them to email the mailing list21:49
leongone thing missing from the ##hashtag is project21:49
AndyU_did we miss that? Darn.21:49
shamailCouldn't that be derived from the either pad name?21:50
leongi only see "nova" and "ironic" called out from the discussion21:50
leongmrhillsman: what do you mean tag [bos-forum-summary]?21:50
rockygThis is the first use.  So, let's go easy.  We can get better over iterations.21:50
AndyU_We should have had ##project with some examples in our template. Will need to add it for next time if we left it out.21:50
leongrockgy: +121:51
mrhillsmanleong: email summaries to multiple mailing lists21:51
leong##project is included in the examples21:51
rockygAnother useful iteration would be to setup all the etherpads for all the sessions ahead of time so that naming is consistent and each has the template21:51
AndyU_oh... well :)21:51
mrhillsmanright now i have a number of summaries that are crowded in with other emails, suggesting a tag21:51
rockygmrhillsman, ++21:51
shamailmrhillsman: +1, maybe [Forum Summary]21:52
mrhillsmanworks :)21:52
AndyU_Rocky +1 to creating etherpads in advance. I'd also add that we should build the wiki page referencing them too.  but maybe just alphabetize them rather than including day/time since that changed a lot.21:52
leongI believe we can continue to propose using ##hashtag in next forum, or maybe PTG prior to forum21:53
mrhillsmanhow about a video on moderating a session at the forum?21:53
*** cknight has quit IRC21:53
AndyU_+1 mrhillsmann21:53
leongcan i suggest everyone in this team to look at the ##hashtag results and provide feedback in the ML or in next PWG meeting?21:54
rockygThere is actually a video created a while back.21:54
mrhillsmani wonder how useful/beneficial/cumbersome hashtag will be for PTG?21:54
mrhillsmanrockyg: have link?21:54
rockygI can find it.21:54
mrhillsmanwould love to check it out21:54
AndyU_+1 mrhillsmann to both the summaries and video or some method of providing guidance on moderating.21:54
leongmrhillsman: can you take the action and follow up on the summaries and video/method?21:55
mrhillsmansure21:55
leongthanks!21:55
shamailI gotta go21:55
leong#action mrhillsman to follow up on the summaries and video/method of providing guidance on moderating21:55
shamailTake care everyone!21:56
mrhillsmanl8r21:56
*** shamail has quit IRC21:56
leongthe hashtag result is merged to the repo now21:56
leong#action all to review the ##hashtag result at https://github.com/openstack/development-proposals/tree/master/forum/201705-bos21:56
*** tristanC has joined #openstack-meeting-alt21:57
AndyU_to the earlier point. ##hashtag should be promoted for PTG too. The more the concept can be institutionalized the more effective it will become21:57
AndyU_Meaning... I agree with mrhillsman21:57
leongagree21:57
mrhillsmandoes it make sense to comment in github leong?21:58
leongmrhillsman: i think it would be great to try out ##hashtag at PTG and also get feedback from Project Team21:58
mrhillsmanagreed21:59
leongmrhillsman: that's the one "hosted" place that i can think of to share the result in ".md" with hyperlink21:59
leong:)21:59
mrhillsmani'm ok with leaving github comments :)22:00
leongmrhillsman: it is 'tentatively' and we can move it somewhere if needed... :-)22:00
*** pabelanger has joined #openstack-meeting-alt22:00
*** jlk has joined #openstack-meeting-alt22:00
mrhillsmancool22:00
leongand yes.. can commet :-)22:00
leongalright, i think we hit the hour22:00
Arkady_Kanevsky+122:00
*** Arkady_Kanevsky has quit IRC22:00
leongthanks all for joining the meeting22:00
leongwe shall meet again next week22:00
leong#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Mon May 22 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-05-22-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-05-22-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-05-22-21.00.log.html22:01
*** MeganR has quit IRC22:01
AndyU_bye all22:01
mrhillsmanthanks everyone! l8r :)22:01
* fungi braces for impending zuulishness22:02
rbergeronlol22:02
*** clarkb has joined #openstack-meeting-alt22:02
jeblairany other zuul folks around?22:03
jlko/22:03
tristanCo/22:03
clarkbme22:03
jeblairmordred, pabelanger, SpamapS, Shrews: courtesy ping22:04
rbergeronmordred and i just finished 1.75 hours of meetings so he should be here soonishly i would expect if not already22:04
pabelangerready now!22:04
jeblaira meeting chaser!22:04
* Shrews is here, but concurrent with dinner22:04
rbergeron:)22:04
jeblair#startmeeting zuul22:04
openstackMeeting started Mon May 22 22:04:18 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:04
*** openstack changes topic to " (Meeting topic: zuul)"22:04
* mordred waves22:04
openstackThe meeting name has been set to 'zuul'22:04
*** leong has quit IRC22:04
* jeblair searches pockets for agenda22:04
jeblairah here we are22:04
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:04
SpamapSo/22:05
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-01-22.05.html22:05
jeblair#topic  Announcements22:05
*** jamielennox has joined #openstack-meeting-alt22:05
*** openstack changes topic to "Announcements (Meeting topic: zuul)"22:05
jeblairI have been reliably informed that22:05
jeblair#info SpamapS has been added to Zuul and Nodepool core teams22:05
mordred\o/22:05
fungithanks for agreeing to pitch in on that!22:05
* mordred hands SpamapS a fish he found laying on the ground22:05
* jlk claps 22:05
tristanCnice, congrats SpamapS!22:06
jeblairSpamapS: thanks for the reviews!  and stuff!22:06
SpamapSMmmm fish22:06
SpamapSThanks for the code!22:06
fungicondolences seem more appropriate for core duties ;)22:06
jeblairfungi: you used your outside voice again22:06
fungioops!22:07
* rbergeron sends a nice package of stay-puft marshmallows as a honorarium22:07
jeblair#topic Actions from last meeting22:07
*** openstack changes topic to "Actions from last meeting (Meeting topic: zuul)"22:07
SpamapSI did roast marshmallows this weekend in zuul's honor22:07
jeblairpabelanger create new ppa under openstack-ci-core and add bubblewrap to it; copy existing source package from ansible bubblewrap ppa.22:07
rbergeronyou were camping :)22:07
jeblairpabelanger: if you've shaken the summit off... what's the status of the bubblewrap ppa thingie?22:08
*** jkilpatr has quit IRC22:08
pabelangerjeblair: it is done22:08
fungii think i ended up creating the ppa in the end due to silly lp permissions22:08
pabelangerhttps://review.openstack.org/#/c/461849/22:08
jeblaircool.  one point for pabelanger and one for fungi then.22:08
jeblairtwo points from slytherin just cause.22:09
fungiminus one point for lp's permissions model22:09
clarkbya project owners can only create them22:09
clarkband the openstack-admins group owns it22:09
pabelangerYa, I wasn't part of that22:09
*** zz_dimtruck is now known as dimtruck22:09
*** kzaitsev_mb has quit IRC22:09
*** ijw has quit IRC22:10
jeblairpabelanger: is that held up on the since-fixed sphinx thing?22:10
jeblairyeah, looks like pabelanger just rechecked it22:10
pabelangerya, it should be green now22:10
jeblair#info bubblewrap testing can commence once  https://review.openstack.org/#/c/461849/  lands22:10
jeblairpabelanger, fungi: thanks!22:11
jeblair#topic Status updates: Zuul test enablement22:11
*** openstack changes topic to "Status updates: Zuul test enablement (Meeting topic: zuul)"22:11
SpamapSI took last week off from that to focus on py3k :)22:11
jeblairSpamapS: good choice, as it turns out22:11
SpamapSindeed, we're now py35 compatible :)22:12
mordredtobiash even has a v3 running in python3 now!22:12
*** kylek3h has quit IRC22:12
SpamapS*nice*22:12
SpamapSI tried to do the same for Bonny but we have some delta still for github22:12
jesusaurw00t, new pythons22:13
jeblairone of the next things i want to do is finish moving the cloner branch logic into the executor (along with adding some bits to the job language).  that will move/obsolete most of the cloner tests (and the cloner itself, as it exists today).22:13
*** rfolco has quit IRC22:13
mordred++22:13
*** baoli has quit IRC22:13
SpamapSon that topic, the tests left are a few hairy ones22:13
jeblairi'm not sure how many tests the cloner accounts for in our deficit (is that 15 or just one? anyway...)22:13
*** xyang1 has quit IRC22:13
jesusaurjeblair: is that part of the effort to make the executors push git repos to the workers?22:13
SpamapSwell we have skips for py3 now22:14
SpamapSso we really have two re-enablement efforts22:14
jeblairjesusaur: yep22:14
mordredSpamapS: hopefully the py3 skips are easy to pick off22:14
SpamapS"Fails on py3" tests in test_scheduler should be prioritized as first.22:14
jeblairjesusaur: (to be fair, we're doing that part now; so this is more "doing it right" :)22:14
SpamapSThey were really confusing fails, not obvious at all.22:15
mordredSpamapS: ++ - there was a thing tobiash thought was a bug earlier, but was a config bug ... but it was of hte order of "confusing bug"22:15
jeblairalso worth noting -- it *seems* something about the GC/lifecycle of git repo objects we were counting on in py2 has changed in py3, causing sporadic failures22:15
jeblair#link debugging python3 git repo gc issues: https://review.openstack.org/46681022:16
SpamapSindeed, so we're not going to backslide on py3 but we still have the last mile to go22:16
SpamapSI'd very much appreciate some fresh eyes on those skipped tests.22:17
pabelangerNodepool should also been python3 compat now too, just need a few more reviews22:17
jeblairShrews brought up the suggestion of making the py3 tests nonvoting if we can't catch that one soon.  i'd like to spend some more time trying to figure it out before we do that though.22:17
SpamapSpabelanger: I'll take a look :)22:17
pabelangeralso have experimental dsvm jobs in progress22:17
SpamapSI'd say take a day or two to debug before we demote the tests.22:18
mordredSpamapS: my stack is still stupid long, but I just added looking with fresh eyes to my list22:18
SpamapSSince it's racey... we need data22:18
SpamapSbut I guess non-voting would still provide data22:18
clarkbalso worth noting that python3 garbage colelctor has had at least one nasty bug in the past22:19
* Shrews cannot mordred.stack.pop() faster than all the mordred.stack.push()'s22:19
jeblair(another option is that we disable the git repo gc check; however, it has always shown legit bugs in the past)22:19
rbergeronshrews: lol22:20
jeblairanything else?22:20
*** ijw has joined #openstack-meeting-alt22:20
jeblair#topic Status updates: Zuul sample jobs22:20
*** openstack changes topic to "Status updates: Zuul sample jobs (Meeting topic: zuul)"22:20
jeblairpabelanger has been doing a lot of work here (some of which just merged)22:21
mordred\o/22:21
*** JudeC has quit IRC22:21
jeblairi think it's getting tricky to keep track of the bits that we expect to share and the bits that we don't with all of the jobs in the same repo22:22
jeblairi think we should go ahead and create the zuul-base-jobs and zuul-jobs repos, and move things we expect to share in there22:23
mordred++22:23
*** ijw has quit IRC22:23
mordredI think having them be future theoretical things is hard22:23
jeblairyep, i keep tripping over myself saying "well, this job when it's in the other repo will be like..."22:23
fungiwfm22:24
jlkmore repos, more chances to test cross-repo testing!22:24
*** AndyU is now known as Guest9308322:24
*** AndyU_ is now known as AndyU22:24
jeblairpabelanger: is pushing up the repo creation requests on your plate?22:24
pabelangercurrently no, but I can add it22:24
jeblairpabelanger: thanks!22:25
*** adrian_otto has joined #openstack-meeting-alt22:25
jeblair#action pabelanger create zuul-base-jobs and zuul-jobs repos22:25
jeblairconsidering we're not sure we like the separate openstack-zuul-jobs and openstack-zuul-roles repos, let's just start with "-jobs" for now, and not create any more "-roles" atm.22:25
jeblairi think once that's done, and we have some basic structure set up, we should dust off the devstack ansiblification soon.  we're going to be ready for that soon.22:27
*** jkilpatr has joined #openstack-meeting-alt22:27
jeblair(probably shortly after i finish this "check out the right branch" stuff :)22:27
jeblairanything else on jobs?22:28
*** ijw has joined #openstack-meeting-alt22:28
SpamapSI don't remember why we split roles and jobs. Is that written down somewhere?22:28
pabelangernothing on myside22:28
jeblairSpamapS: experimenting with how best to set up these sorts of repos?22:29
rbergeronbecause roles should hopefully be reusable in different jobs?22:30
rbergeron(maybe?)22:30
jeblairrbergeron: yeah... maybe you want the tox roles but no tox jobs?22:31
mordredI have a hunch there will be many repo-organization learning experiences over the next 6 months22:31
jeblair(though ponting at a zuul repo to get roles without jobs is also a thing we need to do for third-party ci)22:31
jeblairmordred: yep.22:32
clarkbthe jobs are explicitly enabled per project though right? so just including the repo will get you the roles but not necessarily the jobs?22:32
*** dustins has quit IRC22:32
jeblairand even at this point, i don't think that we've learned much more than "it's annoying having them in two repos when you're starting out and keep re-orging the entire system".  :)22:32
* jlk would suggest not pre-emptively exploding the repo count22:32
jeblairclarkb: yeah, but they are still *defined* as soon as zuul sees a .zuul.yaml22:33
jeblairso fundamentally the question addressed by two repos is "i want to use the zuul stdlib tox role, but not the zuul stdlib tox job definition.  how do i do that?"22:33
*** JudeC has joined #openstack-meeting-alt22:33
pabelangerya, right now our base job points to openstack-zuul-roles, so today all jobs get the roles22:33
rbergeroni think the "experimenting" to figure otu what makes sense... makes sense. imo22:34
rbergeron:)22:34
jeblair(where the actor in my question is a zuul operator)22:34
jeblairright now, the only way is "split them into two repos".  in the future, we will have that option and also "zuul operators can specify which configuration objects to load from which projects"22:34
*** ijw has quit IRC22:34
*** ijw has joined #openstack-meeting-alt22:35
*** adrian_otto has quit IRC22:35
jeblairjlk: yeah, it's easier to add later than delete them22:35
jlkcan jobs in one repo mask jobs in another? Is there a priority stack?22:35
jeblairjlk: they can not; job definitions with the same name in multiple repos is a configuration error22:35
jlkOIC22:35
clarkbwhich caused trouble when moving jobs around22:36
* rbergeron would almost wonder if having a openstack-galaxy might be interesting but it may be early for that -- but i also think that if we want to leverage (or even enhance) the ansible ecosystem... following those patterns might be good / wise / sane22:36
jeblair(thus, this is sort of important :)22:36
*** slaweq__ has quit IRC22:36
rbergeron(or even if role -- even if it looks like a role -- needs a better type of terminology here, might be a thing)22:36
jeblairrbergeron: indeed, a lot of these are pretty specialized roles, and we occasionally run into confusion around that22:37
*** adrian_otto has joined #openstack-meeting-alt22:37
jeblairlet's move on so we don't starve other topics22:38
jeblair#topic Status updates: Github22:38
* mordred is hungry22:38
*** openstack changes topic to "Status updates: Github (Meeting topic: zuul)"22:38
jeblair(or our developers!)22:38
mordredoh - I reviewed your rework of the plugin interface - did I vote on it?22:38
jeblairmordred: yes!22:38
mordredyay!22:38
mordredI forget to click the button sometimes22:39
jlkI think we have enough votes for W+22:39
jeblair#link https://review.openstack.org/466105 is the change in question22:39
jlkwhich will allow me to more easily rebase the rest of the stack on it.22:39
jeblairwe paused the github branch review/merging process to do that22:39
jlkI have few obligations this week so I should be able to get the rebase done quickly and up for review again.22:40
jeblairit cleans up one of the larger areas which we knew was pretty gnarly.  it's a smallish user-facing change as well as an api cleanup, so i asked a few other folks to give it a quick once-over22:40
mordredI have the gh follow up patch open in the browser for review22:40
jeblairthings are starting to feel actually extensible like we have a real api now.  almost.  :)22:41
rbergeronjlk: huge kudos on that, btw -- /me sends you a candy bar or a bicycle or something exciting. virtual bicycle. that is. :)22:41
mordredikr?22:41
rbergeronall the hugs22:41
jlkI'll settle for a round in London :D22:41
rbergeronjlk: i can do that. i will be expensing it but the love is all the same22:41
jeblair#topic Status updates: Bubblewrap22:42
*** openstack changes topic to "Status updates: Bubblewrap (Meeting topic: zuul)"22:42
jeblairSpamapS: once pabelanger's change merges, are we completely unblocked on this?22:42
*** ijw has quit IRC22:42
*** adrian_otto has quit IRC22:42
jlkbubble wrap to bindep just merged22:42
jeblairha!22:42
jeblair22:42 < openstackgerrit> Merged openstack-infra/zuul feature/zuulv3: Add bubblewrap to bindep / test-setup.sh  https://review.openstack.org/46184922:42
jeblairopenstackgerrit has comic timing22:43
rbergeronlol22:43
funginice22:43
pabelangerdid we figure out the zuul.paths issue for bubblewrap?22:44
* SpamapS +A'd22:44
SpamapSpabelanger: what issue was that?22:44
* SpamapS has been fighting ssh-agent for a bit22:44
jeblairah, ssh-agent, that's the next blocker i guess22:44
pabelangerpip install uses symlinks, which are outside bubblewrap for testing22:44
jeblair#link next step in bubblewrap https://review.openstack.org/46271222:45
pabelangerhttps://review.openstack.org/#/c/461881/22:45
SpamapSpabelanger: oh that, no we didn't figure that out22:45
* jlk read that as zuul.pants22:45
mordredjlk: you NEVER want to get zuul.pants wrong22:45
jeblair#link other next step in bubblewrap https://review.openstack.org/46188122:45
jlkmordred: that's what the belt and suspenders are for.22:45
SpamapSI think the two thoughts were 1) library/pypi for the shared bits, 2) just copy pasta into the actions22:45
clarkbpabelanger: thats due to pip install -e right?22:45
clarkbpabelanger: could just stop doing that22:45
pabelangerya22:45
*** rossella__ has quit IRC22:46
jeblairi like copy pasta into actions22:46
jeblairthere's no reason the action plugins actually need to *import zuul itself*22:46
*** ijw has joined #openstack-meeting-alt22:46
SpamapSjeblair: +122:46
*** dimtruck is now known as zz_dimtruck22:47
*** zz_dimtruck is now known as dimtruck22:48
jeblair#topic  Progress summary22:49
*** openstack changes topic to "Progress summary (Meeting topic: zuul)"22:49
SpamapS#link https://storyboard.openstack.org/#!/board/4122:49
SpamapSfeels a little stalled22:50
rbergeronwe did just come out of summit and all that crap.22:50
SpamapSTrue22:50
* rbergeron uses her backspace key wisely with a more appropriate word22:50
SpamapShttps://storyboard.openstack.org/#!/story/2000792 is almost done22:50
jeblairit would be great if folks looking for a way to help would check that board22:51
SpamapSI forgot to mention it in the patches22:51
jeblairand if you identify an issue that needs to be worked on before we can start minimally using v3 in production, please add it to that list22:51
*** ijw has quit IRC22:51
* SpamapS moves it to in progress22:51
*** ansmith has joined #openstack-meeting-alt22:52
jeblairwe're pretty close, but there's still a good chunk to be done, and we need to stay focused22:52
jeblair#topic Open Discussion22:53
*** openstack changes topic to "Open Discussion (Meeting topic: zuul)"22:53
Shrewsmordred: pretty sure i know the answer, but has there been any movement on the gear-zk shim?22:53
rbergeronI haz a thing also22:53
mordredShrews: nope - sorry22:54
mordredjeblair: so - 2 questions came up earlier today that it seemed we should have an answer for22:54
tristanCregarding static node support, is there a spec/change already?22:55
jeblairShrews, mordred: if mordred finishes the shim, it'll still be useful for the transition, however, i'm fairly happy with the load testing nodepool is getting, and we will be able to ramp it up slowly.22:55
mordredjeblair: one is where to put tobiash's Dockerfile -- it seemed the thing people liked the most so far as "in another repo, such as zuul-docker or docker-zuul or something"22:55
jeblairtristanC: yes, see https://review.openstack.org/461509 (which i should add to tomorrows infra team meeting to get approved)22:55
jeblairtristanC: (spec yes, change no)22:55
clarkbfwiw, I think that adding a ton of extra repos makes it harder for people jumping in to discover/use tools like that which seem largely aimed at make quickstart quick and easy22:56
tristanCperfect, thanks!22:56
jeblairtristanC: tobiash was interested in potentially doing some work related to that; we should sync with him if you're also interested22:56
clarkb(can document, but no one reads the docs :P )22:56
jeblairmordred: yeah, i feel like we're all probably on the same page about not wanting to mislead people in thinking that "docker", "vagrant", etc are the way to run zuul22:57
jlkclarkb: I agree, but it may be too early to dump a definitive docker file in the zuul repo. There are a lot of things to sort out around deploy/run zuul/nodepool22:57
jeblairso either in-repo in contrib/$file, or in another repo.22:57
jeblairsee, jlk just said "definitive" :)22:57
jeblairwhich i think illustrates the problem22:57
clarkbI'm not sure why it would be definitive... especially if its in eg contrib/docker22:57
tristanCand regarding a zuul dashboard, are people interested to define the rest api?22:57
mordredyah. I can see a day in the future where we may want to provide a docker image for people - but I don't think we're there yet22:57
jlkcontrib/ makes that somewhat clear22:58
mordredcontrib does not bother me at all22:58
jeblairmordred: yeah if/when that happens, easy to promote it up.22:58
mordred++22:58
jlkI _do_ hope we get to the point (soon) where we can document Docker/k8s as a way to deploy and run Zuul in production.22:58
jeblairi can live with contrib/ but i'd like to know if we have some folks willing to approve patches to that22:58
jeblairbecause i will not be22:58
rbergeron:)22:58
jlkI'll be reviewing them22:59
* rbergeron will throw in before the hour is up --22:59
Shrewsi feel any deploy thing should be separate from the thing being deployed22:59
rbergeronso: I have been utter crap on the zuul-updates mail lately -- between travel and boss having emergency surgery crap and filling on for everything on both fronts, life sucked :D -- but i would like to get on that train again, so I will chat with ppl tomorrow in channel about coallating the last... 1.5 months of that, or so. so heads up that i will beep tomorrow. :)22:59
jlkI left numerous commentary in the existing changes.22:59
jeblair(on account of i can't review them)22:59
pabelangerShrews: +122:59
* rbergeron apologizes for sucking22:59
jeblairrbergeron: a new update would be great, thank you!22:59
mordredthe other thing is tristanC's dashboard patch - but I think we're out of meeting time to dig in to it ... I can try to send an email to the mailing-list with thoughts I had in my brain for folks22:59
jlkshoot I really need to get on that list23:00
jeblairmordred, tristanC: can you add items to the agenda next time?23:00
jeblairi didn't know we had things queued up for the meeting23:00
mordredjeblair: yah - I totaly forgot to pre-add this time23:00
mordredthat's my bad23:00
jeblairthere's a place " General topics (add agenda items here)" where you can add them :)23:00
fungithanks for starting that back up rbergeron!23:00
jeblairi will happily push things around to accomodate stuff there23:00
mordred++23:00
tristanCthanks!23:00
jeblairunfortunately, i don't know that we have come to a consensus on the docker thing23:00
mordredwell - I'll start a thread - and maybe we won't even need a topic next time23:00
jeblairso let's put docker back on next week's agenda23:01
mordred++23:01
rbergeronfungi: np. it's one of the things i can actually do to help atm, it's just .. worklife has been a juggling game lately :)23:01
rbergeronbut it's useful to have folks know what's coming (vital, kinda, really ;D)23:01
jeblairthanks all!23:01
jeblair#endmeeting23:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:01
openstackMeeting ended Mon May 22 23:01:38 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-22-22.04.html23:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-22-22.04.txt23:01
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-22-22.04.log.html23:01
*** tristanC has left #openstack-meeting-alt23:01
*** Shrews has left #openstack-meeting-alt23:01
*** ijw has joined #openstack-meeting-alt23:02
*** sdague has quit IRC23:03
*** neiljerram has quit IRC23:05
*** rockyg has quit IRC23:07
*** dane_leblanc has joined #openstack-meeting-alt23:10
*** dane_ has quit IRC23:10
*** fnaval has quit IRC23:10
*** armstrong has quit IRC23:10
*** ijw has quit IRC23:14
*** ijw has joined #openstack-meeting-alt23:33
*** ijw has quit IRC23:34
*** ijw has joined #openstack-meeting-alt23:34
*** rwsu has quit IRC23:34
*** arnewiebalck__ has joined #openstack-meeting-alt23:35
*** arnewiebalck_ has quit IRC23:38
*** felipemonteiro has joined #openstack-meeting-alt23:39
*** rwsu has joined #openstack-meeting-alt23:41
*** salv-orlando has joined #openstack-meeting-alt23:41
*** JudeC has quit IRC23:43
*** diablo_rojo has quit IRC23:57

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