Monday, 2017-06-26

*** reedip has quit IRC00:07
*** salv-orlando has joined #openstack-meeting-alt00:07
*** salv-orlando has quit IRC00:12
*** felipemonteiro__ has quit IRC00:12
*** kzaitsev_mb has joined #openstack-meeting-alt00:18
*** cloudrancher has quit IRC00:18
*** cloudrancher has joined #openstack-meeting-alt00:19
*** cloudrancher has quit IRC00:21
*** reedip has joined #openstack-meeting-alt00:21
*** cloudrancher has joined #openstack-meeting-alt00:22
*** kzaitsev_mb has quit IRC00:22
*** jkilpatr has quit IRC00:40
*** zhurong has joined #openstack-meeting-alt00:45
*** tuanluong has joined #openstack-meeting-alt00:48
*** slaweq has joined #openstack-meeting-alt00:51
*** slaweq has quit IRC00:55
*** salv-orlando has joined #openstack-meeting-alt01:08
*** salv-orlando has quit IRC01:13
*** caowei has joined #openstack-meeting-alt01:18
*** kzaitsev_mb has joined #openstack-meeting-alt01:18
*** reedip has quit IRC01:23
*** gcb has joined #openstack-meeting-alt01:32
*** hongbin has joined #openstack-meeting-alt01:33
*** reedip has joined #openstack-meeting-alt01:35
*** apetrich has quit IRC01:42
*** apetrich has joined #openstack-meeting-alt01:42
*** zhurong has quit IRC02:01
*** salv-orlando has joined #openstack-meeting-alt02:09
*** salv-orlando has quit IRC02:14
*** gouthamr has joined #openstack-meeting-alt02:15
*** beekhof has joined #openstack-meeting-alt02:41
*** zhurong has joined #openstack-meeting-alt02:44
*** slaweq has joined #openstack-meeting-alt02:53
*** zhurong has quit IRC02:56
*** slaweq has quit IRC02:58
*** zhurong has joined #openstack-meeting-alt03:08
*** gcb has quit IRC03:14
*** gcb has joined #openstack-meeting-alt03:15
*** gouthamr has quit IRC03:22
*** zhurong has quit IRC03:23
*** zhurong has joined #openstack-meeting-alt03:35
*** julim has quit IRC03:41
*** spzala has quit IRC03:45
*** spzala has joined #openstack-meeting-alt03:47
*** cartik has joined #openstack-meeting-alt03:47
*** cartik has quit IRC03:47
*** spzala has quit IRC03:52
*** yamamoto has joined #openstack-meeting-alt03:54
*** arnewiebalck_ has joined #openstack-meeting-alt03:54
*** lpetrut has joined #openstack-meeting-alt03:56
*** yamahata has joined #openstack-meeting-alt04:00
*** amotoki_away is now known as amotoki04:02
*** hiro-kobayashi has joined #openstack-meeting-alt04:04
*** apetrich has quit IRC04:10
*** salv-orlando has joined #openstack-meeting-alt04:10
*** hongbin has quit IRC04:11
*** apetrich has joined #openstack-meeting-alt04:11
*** salv-orlando has quit IRC04:15
*** shu-mutou-AWAY is now known as shu-mutou04:21
*** caowei_ has joined #openstack-meeting-alt04:21
*** adisky__ has joined #openstack-meeting-alt04:23
*** caowei has quit IRC04:24
*** caowei_ is now known as caowei04:24
*** caowei has quit IRC04:36
*** lpetrut has quit IRC04:38
*** links has joined #openstack-meeting-alt04:40
*** kzaitsev_mb has quit IRC04:40
*** caowei has joined #openstack-meeting-alt04:45
*** julim has joined #openstack-meeting-alt04:51
*** slaweq has joined #openstack-meeting-alt04:55
*** lpetrut has joined #openstack-meeting-alt04:55
*** slaweq has quit IRC04:59
*** salv-orlando has joined #openstack-meeting-alt05:04
*** yangyapeng has joined #openstack-meeting-alt05:06
*** arnewiebalck_ has quit IRC05:12
*** marios has joined #openstack-meeting-alt05:19
*** yangyapeng has quit IRC05:35
*** reedip has quit IRC05:45
*** tobberydberg has joined #openstack-meeting-alt05:46
*** yangyapeng has joined #openstack-meeting-alt05:47
*** kobis has joined #openstack-meeting-alt05:52
*** mjura has joined #openstack-meeting-alt05:56
*** rcernin has joined #openstack-meeting-alt05:59
*** caowei_ has joined #openstack-meeting-alt05:59
*** julim has quit IRC06:01
*** caowei has quit IRC06:03
*** caowei_ is now known as caowei06:03
*** yangyape_ has joined #openstack-meeting-alt06:08
*** caowei_ has joined #openstack-meeting-alt06:10
*** yangyapeng has quit IRC06:10
*** caowei has quit IRC06:13
*** caowei_ is now known as caowei06:13
*** yangyape_ has quit IRC06:14
*** yangyapeng has joined #openstack-meeting-alt06:17
*** yangyapeng has quit IRC06:18
*** salv-orlando has quit IRC06:19
*** salv-orlando has joined #openstack-meeting-alt06:19
*** jprovazn has joined #openstack-meeting-alt06:20
*** florianf has joined #openstack-meeting-alt06:21
*** vds has joined #openstack-meeting-alt06:22
*** tesseract has joined #openstack-meeting-alt06:24
*** salv-orlando has quit IRC06:24
*** andreas_s has joined #openstack-meeting-alt06:27
*** reedip has joined #openstack-meeting-alt06:28
*** salv-orlando has joined #openstack-meeting-alt06:28
*** yangyapeng has joined #openstack-meeting-alt06:34
*** yangyape_ has joined #openstack-meeting-alt06:35
*** salv-orl_ has joined #openstack-meeting-alt06:37
*** yangyapeng has quit IRC06:39
*** salv-orlando has quit IRC06:39
*** iyamahat has joined #openstack-meeting-alt06:41
*** bogdando has joined #openstack-meeting-alt06:41
*** yamahata has quit IRC06:43
*** reedip has quit IRC06:48
*** reedip has joined #openstack-meeting-alt06:48
*** jpena|off is now known as jpena06:50
*** vds has quit IRC06:50
*** lpetrut has quit IRC06:53
*** iyamahat has quit IRC06:54
*** slaweq has joined #openstack-meeting-alt06:56
*** matrohon has joined #openstack-meeting-alt06:59
*** slaweq has quit IRC07:00
*** vds has joined #openstack-meeting-alt07:03
*** yangyape_ has quit IRC07:04
*** kzaitsev_ws has joined #openstack-meeting-alt07:05
*** rarcea has joined #openstack-meeting-alt07:06
*** lpetrut has joined #openstack-meeting-alt07:09
*** ccamacho has joined #openstack-meeting-alt07:21
*** reedip is now known as reedip_afk07:24
*** oidgar has joined #openstack-meeting-alt07:35
*** lpetrut has quit IRC07:42
*** ralonsoh has joined #openstack-meeting-alt07:44
*** lkoranda has quit IRC07:52
*** yangyapeng has joined #openstack-meeting-alt07:55
*** rossella_ has joined #openstack-meeting-alt07:57
*** jprovazn has quit IRC07:58
*** rcernin has quit IRC07:59
*** lkoranda has joined #openstack-meeting-alt08:02
*** jprovazn has joined #openstack-meeting-alt08:12
*** itamaro has quit IRC08:12
*** rcernin has joined #openstack-meeting-alt08:12
*** hiro-kobayashi has quit IRC08:14
*** rossella_ has quit IRC08:18
*** yangyapeng has quit IRC08:18
*** rossella_ has joined #openstack-meeting-alt08:19
*** junbo has quit IRC08:21
*** spzala has joined #openstack-meeting-alt08:21
*** MarkBaker has quit IRC08:23
*** junbo has joined #openstack-meeting-alt08:25
*** MarkBaker has joined #openstack-meeting-alt08:25
*** bfernando has joined #openstack-meeting-alt08:25
*** spzala has quit IRC08:26
*** spzala has joined #openstack-meeting-alt08:37
*** yamamoto has quit IRC08:38
*** bauwser is now known as bauzas08:39
*** yamamoto has joined #openstack-meeting-alt08:39
*** spzala has quit IRC08:41
*** derekh has joined #openstack-meeting-alt08:42
*** yamamoto has quit IRC08:45
*** rwsu has joined #openstack-meeting-alt08:47
*** yangyapeng has joined #openstack-meeting-alt08:52
*** yangyape_ has joined #openstack-meeting-alt08:54
*** slaweq has joined #openstack-meeting-alt08:57
*** yangyapeng has quit IRC08:57
*** lpetrut has joined #openstack-meeting-alt08:58
*** itamaro has joined #openstack-meeting-alt08:59
*** nijaba has quit IRC09:01
*** slaweq has quit IRC09:02
*** yamamoto has joined #openstack-meeting-alt09:03
*** spzala has joined #openstack-meeting-alt09:05
*** dalgaaf has quit IRC09:07
*** dalgaaf has joined #openstack-meeting-alt09:08
*** nijaba has joined #openstack-meeting-alt09:08
*** spzala has quit IRC09:09
*** tobberyd_ has joined #openstack-meeting-alt09:11
*** noslzzp has quit IRC09:11
*** tobberydberg has quit IRC09:15
*** yangyapeng has joined #openstack-meeting-alt09:22
*** yangyape_ has quit IRC09:23
*** rwsu has quit IRC09:26
*** shu-mutou is now known as shu-mutou-AWAY09:30
*** sambetts|afk is now known as sambetts09:35
*** rwsu has joined #openstack-meeting-alt09:42
*** rcernin has quit IRC09:46
*** aarefiev_afk is now known as aarefiev09:47
*** spzala has joined #openstack-meeting-alt09:48
*** reedip_afk is now known as reedip09:49
*** spzala has quit IRC09:53
*** rossella_ has quit IRC09:54
*** salv-orl_ has quit IRC09:56
*** tobberyd_ has quit IRC09:57
*** salv-orlando has joined #openstack-meeting-alt09:57
*** tobberydberg has joined #openstack-meeting-alt09:57
*** tobberydberg has quit IRC09:59
*** slaweq has joined #openstack-meeting-alt09:59
*** tobberydberg has joined #openstack-meeting-alt09:59
*** salv-orlando has quit IRC10:01
*** rcernin has joined #openstack-meeting-alt10:03
*** slaweq has quit IRC10:03
*** spzala has joined #openstack-meeting-alt10:04
*** spzala has quit IRC10:08
*** yangyapeng has quit IRC10:09
*** rossella_ has joined #openstack-meeting-alt10:09
*** yamamoto has quit IRC10:17
*** spzala has joined #openstack-meeting-alt10:19
*** rmart04 has joined #openstack-meeting-alt10:21
*** dizquierdo has joined #openstack-meeting-alt10:22
*** spzala has quit IRC10:24
*** pbourke has quit IRC10:30
*** pbourke has joined #openstack-meeting-alt10:31
*** lpetrut_ has joined #openstack-meeting-alt10:32
*** lpetrut has quit IRC10:34
*** florianf has quit IRC10:36
*** florianf has joined #openstack-meeting-alt10:41
*** spzala has joined #openstack-meeting-alt10:48
*** lkoranda has quit IRC10:51
*** spzala has quit IRC10:52
*** jprovazn has quit IRC10:54
*** yamamoto has joined #openstack-meeting-alt10:59
*** rossella_ has quit IRC10:59
*** slaweq has joined #openstack-meeting-alt10:59
*** lkoranda has joined #openstack-meeting-alt11:00
*** ccamacho is now known as ccamacho|lunch11:03
*** tobberydberg has quit IRC11:03
*** tobberydberg has joined #openstack-meeting-alt11:04
*** slaweq has quit IRC11:04
*** jkilpatr has joined #openstack-meeting-alt11:06
*** tobberydberg has quit IRC11:09
*** tobberydberg has joined #openstack-meeting-alt11:10
*** tobberydberg has quit IRC11:11
*** tobberydberg has joined #openstack-meeting-alt11:11
*** sdague has joined #openstack-meeting-alt11:12
*** gcb has quit IRC11:15
*** rossella_ has joined #openstack-meeting-alt11:15
*** tobberydberg has quit IRC11:16
*** tobberydberg has joined #openstack-meeting-alt11:16
*** lpetrut_ has quit IRC11:21
*** lpetrut has joined #openstack-meeting-alt11:24
*** yangyapeng has joined #openstack-meeting-alt11:24
*** jaypipes has joined #openstack-meeting-alt11:26
*** yangyapeng has quit IRC11:28
*** slagle_ is now known as slagle11:30
*** alexchadin has joined #openstack-meeting-alt11:31
*** yangyapeng has joined #openstack-meeting-alt11:34
*** yamamoto has quit IRC11:37
*** pradk has quit IRC11:38
*** dizquierdo has quit IRC11:47
*** jprovazn has joined #openstack-meeting-alt11:55
*** sshnaidm is now known as sshnaidm|afk11:58
*** slaweq has joined #openstack-meeting-alt12:00
*** dprince has joined #openstack-meeting-alt12:00
*** rossella_ has quit IRC12:01
*** rcernin has quit IRC12:02
*** rcernin has joined #openstack-meeting-alt12:04
*** slaweq has quit IRC12:04
*** reedip has quit IRC12:07
*** cleong has joined #openstack-meeting-alt12:09
*** rossella_ has joined #openstack-meeting-alt12:13
*** yamamoto has joined #openstack-meeting-alt12:13
*** jpena is now known as jpena|lunch12:14
*** slaweq has joined #openstack-meeting-alt12:17
*** reedip has joined #openstack-meeting-alt12:19
*** rcernin has quit IRC12:21
*** rcernin has joined #openstack-meeting-alt12:21
*** ccamacho|lunch is now known as ccamacho12:25
*** salv-orlando has joined #openstack-meeting-alt12:29
*** ralonsoh has quit IRC12:30
*** baoli has joined #openstack-meeting-alt12:31
*** dsariel has quit IRC12:31
*** ansmith has joined #openstack-meeting-alt12:31
*** jcoufal has joined #openstack-meeting-alt12:32
*** janki has joined #openstack-meeting-alt12:32
*** sridharg has joined #openstack-meeting-alt12:33
*** salv-orlando has quit IRC12:33
*** tobberydberg has quit IRC12:34
*** rfolco has joined #openstack-meeting-alt12:34
*** tobberydberg has joined #openstack-meeting-alt12:35
*** baoli has quit IRC12:35
*** tobberydberg has quit IRC12:36
*** tobberydberg has joined #openstack-meeting-alt12:37
*** lpetrut has quit IRC12:44
*** spzala has joined #openstack-meeting-alt12:48
*** dsariel has joined #openstack-meeting-alt12:48
*** tuanluong has quit IRC12:50
*** janki has quit IRC12:50
*** spzala has quit IRC12:53
*** jkilpatr has quit IRC12:54
*** sridharg has quit IRC12:55
*** hrybacki is now known as hrybacki|trainin12:55
*** cloudrancher has quit IRC12:58
*** cloudrancher has joined #openstack-meeting-alt12:59
*** rossella_ has quit IRC13:04
*** lpetrut has joined #openstack-meeting-alt13:06
*** jkilpatr has joined #openstack-meeting-alt13:08
*** tenobreg has quit IRC13:08
*** tenobreg has joined #openstack-meeting-alt13:09
*** tenobreg is now known as tellesnobrega13:09
*** lucasxu has joined #openstack-meeting-alt13:13
*** oidgar has quit IRC13:13
*** julim has joined #openstack-meeting-alt13:14
*** florianf has quit IRC13:16
*** gouthamr has joined #openstack-meeting-alt13:16
*** slaweq has joined #openstack-meeting-alt13:18
*** florianf has joined #openstack-meeting-alt13:18
*** jheroux has joined #openstack-meeting-alt13:19
*** ralonsoh has joined #openstack-meeting-alt13:21
*** slaweq has quit IRC13:22
*** jpena|lunch is now known as jpena13:24
*** rossella_ has joined #openstack-meeting-alt13:25
*** gouthamr has quit IRC13:26
*** felipemonteiro has joined #openstack-meeting-alt13:28
*** salv-orlando has joined #openstack-meeting-alt13:30
*** felipemonteiro_ has joined #openstack-meeting-alt13:30
*** rossella_ has quit IRC13:32
*** spzala has joined #openstack-meeting-alt13:34
*** salv-orlando has quit IRC13:34
*** felipemonteiro has quit IRC13:34
*** felipemonteiro_ has quit IRC13:37
*** kylek3h has joined #openstack-meeting-alt13:37
*** felipemonteiro has joined #openstack-meeting-alt13:38
*** netapp has quit IRC13:38
*** diablo_rojo has joined #openstack-meeting-alt13:38
*** spzala has quit IRC13:39
*** ijw has joined #openstack-meeting-alt13:41
*** diga has joined #openstack-meeting-alt13:42
*** gcb has joined #openstack-meeting-alt13:42
*** spzala has joined #openstack-meeting-alt13:42
*** xyang1 has joined #openstack-meeting-alt13:43
*** rossella_ has joined #openstack-meeting-alt13:48
*** fzdarsky has joined #openstack-meeting-alt13:48
*** superdan is now known as dansmith13:50
*** dtantsur has joined #openstack-meeting-alt13:50
*** kobis has quit IRC13:54
*** noslzzp has joined #openstack-meeting-alt13:57
*** links has quit IRC13:58
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Jun 26 14:00:11 2017 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
edleafeWho's here today?14:00
dtantsuro/14:00
alex_xuo/14:00
jaypipeshola14:01
*** lei-zh has joined #openstack-meeting-alt14:01
edleafePretty empty this morning - everyone can stretch out!14:01
edleafe#topic Specs & Reviews14:02
*** openstack changes topic to "Specs & Reviews (Meeting topic: nova_scheduler)"14:02
* alex_xu lay down on the ground14:02
* jaypipes currently rebasing the placement-allocation-requests series14:02
jaypipesrunning tests...14:02
edleafeI was out Friday, so I'm not as up-to-date on the status of many of these patches14:02
edleafe#link Allocation Candidates https://review.openstack.org/#/c/475448/14:03
edleafejaypipes: should be ready for review in a little while?14:03
jaypipesedleafe: yup. 15 minutes.14:03
edleafekewl14:04
edleafe#link Nested Resources: series starting with https://review.openstack.org/#/c/415920/14:04
edleafeLooks like there was some action on this14:04
* bauzas waves14:04
* edleafe waves back14:05
*** salv-orlando has joined #openstack-meeting-alt14:05
bauzasyeah, I can review the nested RP series, but I thought it was needing allocation candidates series to be merged first?14:05
bauzasof course, we can merge some of the changes14:05
bauzasat least the ones related to the caching object in the compute service14:06
edleafesure, but reviews to catch mistakes or clarify what the code is doing is always useful14:06
jaypipesbauzas, edleafe: nested resource providers needs to come after allocation requests, yes.14:07
jaypipesI've been delaying rebasing the n-r-p series.14:07
alex_xuso the goal in the release is allocation requets?14:08
jaypipeshttps://review.openstack.org/#/c/469147/ is a standalone change that would be great to merge.14:08
jaypipesalex_xu: no, the goal is allocation requests, placement claims, shared providers, traits and then nested providers if we get to them.14:08
*** lpetrut has quit IRC14:08
edleafeHeh, that was next up14:08
edleafe#link Delete all inventory: https://review.openstack.org/#/c/460147/14:08
alex_xujaypipes: ok...only one month left14:09
*** felipemonteiro_ has joined #openstack-meeting-alt14:09
edleafeoh wait - that's different14:09
edleafeoh wait - that's different14:09
edleafedoh!14:09
jaypipesalex_xu: yes, I know...14:09
edleafe#link Add UUID field to PciDevice Object https://review.openstack.org/#/c/469147/14:10
*** oidgar has joined #openstack-meeting-alt14:11
bauzasjaypipes: added to my review queue ^14:11
jaypipesmerci14:11
edleafeThe last link I have on the agenda is14:12
edleafe#link Placement API ref docs: https://review.openstack.org/#/q/topic:cd/placement-api-ref+status:open14:12
edleafeAnyone have any other specs or reviews to discuss?14:12
*** felipemonteiro has quit IRC14:12
alex_xuI have question about why we put resource-class into extra spec14:12
edleafealex_xu: where else could we put it?14:13
alex_xusounds like new functionality add to the API without Microversion, also think about what I can do for request traits14:13
edleafeAFAIK, extra_specs is not versioned14:14
alex_xu#link request traits in Nova https://review.openstack.org/#/c/468797/14:14
edleafeAnd it's not part of the defined API. It's part of the Flavor object14:14
alex_xuyea, I guess one of extra_specs problems is not versioned14:16
edleafeAlso, a flavor is not supposed to change14:16
edleafeIf you associate a trait like SSD with a an existing flavor, now you get something different14:16
edleafeeven though you are requesting the same flavor14:17
alex_xubut the user have no way to know the current nova deployment whether support traits or not without microversion14:17
edleafealex_xu: I hate flavors, but until we can totally re-work them, we're stuck14:17
bauzasI thought we agreed on that a couple of releases earlier :)14:18
edleafewhat do you mean about a user needing to know about traits?14:18
alex_xubauzas: yea, I try to know the orignal reason which I missed...14:18
bauzasthere are 3 ways to inject quantitative or qualitative requests14:19
*** slaweq has joined #openstack-meeting-alt14:19
edleafealex_xu: the use case we're trying to handle is requesting an Ironic machine14:19
bauzas1/ is the image, which is user-based14:19
bauzas2/ is using hints, which is user-based and per instance14:19
bauzas3/ is using flavor, which is admin-based14:19
alex_xubauzas: sorry, actually my question is why we add an new attributes to the flavor instead of extra specs14:20
bauzassince admins manage their capacity, it's understandable for them to propose flavors that can match their clouds14:20
alex_xus/why/why no/14:20
alex_xu...s/why no/why not/..14:20
bauzasalex_xu: why we use extra specs instead of Flavor attributes ?14:20
bauzasbecause of the interoperability between clouds, I'd say14:21
alex_xubauzas: this spec add resource class into the extra spec http://specs.openstack.org/openstack/nova-specs/specs/pike/approved/custom-resource-classes-in-flavors.html14:21
edleafealex_xu: yes, that's the spec I was working from14:22
bauzasI don't disagree with that14:22
alex_xuso...that won't be a interoperability problem?14:22
*** alexchadin has quit IRC14:22
bauzasI'm really sorry, I'm not sure I'm getting your concern with the above spec14:23
*** slaweq has quit IRC14:23
edleafealex_xu: I don't think anyone *likes* doing it this way. It's just the least terrible way, given what we have to work with14:23
alex_xuah sorry, my question is that why we didn't add new attributes like flavor.resources in the API instead of adding resources into the extra spec in that proposal.14:24
*** hongbin has joined #openstack-meeting-alt14:24
*** sshnaidm|afk is now known as sshnaidm14:24
edleafealex_xu: see the 'Alternatives' section of that spec14:24
alex_xuoh...14:25
alex_xulooks like is for ironic transion14:28
edleafealex_xu: yeah, if we can get Ironic working with placement this cycle, that's a big win14:29
*** jamemcc has quit IRC14:29
*** ijw has quit IRC14:29
*** JillS has quit IRC14:30
*** AndyU has quit IRC14:30
*** rarora has quit IRC14:30
*** ijw has joined #openstack-meeting-alt14:30
*** bobmel has quit IRC14:30
alex_xuok, I guess in longterm, we want to get those out of flavor14:30
*** yangyape_ has joined #openstack-meeting-alt14:30
*** tobberyd_ has joined #openstack-meeting-alt14:31
edleafelong term we want to burn flavors to the ground14:31
alex_xustill sounds we add new feature to the API without microversion. or we would say that is feature we didn't support offically...14:32
*** markmcclain has quit IRC14:32
*** ijw has quit IRC14:32
*** jtomasek is now known as jtomasek|afk14:32
*** ijw has joined #openstack-meeting-alt14:32
*** yangyapeng has quit IRC14:33
edleafeWell, it's not an API change; it's a flavor change14:33
*** markmcclain has joined #openstack-meeting-alt14:33
alex_xuok14:33
*** tobberydberg has quit IRC14:34
edleafeWell, it seems like we've already been here, so let's make it official14:34
edleafe#topic Open discussion14:34
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:34
*** noslzzp has quit IRC14:34
edleafeAnything else to discuss?14:35
*** tobberyd_ has quit IRC14:35
edleafeGoing once...14:36
bauzassave me time for homeworking with my daughter :)14:36
edleafe:)14:37
edleafeGoing twice...14:37
edleafe#endmeeting14:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:37
openstackMeeting ended Mon Jun 26 14:37:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-06-26-14.00.html14:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-06-26-14.00.txt14:37
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-06-26-14.00.log.html14:37
*** rossella_ has quit IRC14:38
*** dtrainor has quit IRC14:38
*** dtantsur has left #openstack-meeting-alt14:38
*** dtrainor has joined #openstack-meeting-alt14:39
*** nibalizer has quit IRC14:40
*** yamahata has joined #openstack-meeting-alt14:41
*** dizquierdo has joined #openstack-meeting-alt14:43
*** dtrainor has quit IRC14:43
*** chyka has joined #openstack-meeting-alt14:43
*** dtrainor has joined #openstack-meeting-alt14:45
*** namnh has joined #openstack-meeting-alt14:47
*** pradk has joined #openstack-meeting-alt14:47
*** pradk has quit IRC14:47
*** rossella_ has joined #openstack-meeting-alt14:53
*** felipemonteiro_ has quit IRC14:57
*** rcernin has quit IRC15:04
*** fnaval has joined #openstack-meeting-alt15:07
*** kobis has joined #openstack-meeting-alt15:09
*** rmart04 has quit IRC15:11
*** markstur has joined #openstack-meeting-alt15:11
*** rossella_ has quit IRC15:12
*** ijw has quit IRC15:16
*** ijw has joined #openstack-meeting-alt15:16
*** marst has joined #openstack-meeting-alt15:17
*** links has joined #openstack-meeting-alt15:17
*** slaweq has joined #openstack-meeting-alt15:19
*** aarefiev is now known as aarefiev_afk15:20
*** yamamoto has quit IRC15:21
*** yamahata has quit IRC15:21
*** julim_ has joined #openstack-meeting-alt15:23
*** slaweq has quit IRC15:24
*** yamamoto has joined #openstack-meeting-alt15:24
*** markstur has quit IRC15:25
*** links has quit IRC15:25
*** rossella_ has joined #openstack-meeting-alt15:25
*** felipemonteiro has joined #openstack-meeting-alt15:25
*** julim has quit IRC15:25
*** felipemonteiro_ has joined #openstack-meeting-alt15:27
*** yamamoto has quit IRC15:29
*** felipemonteiro has quit IRC15:30
*** oidgar has quit IRC15:32
*** markstur has joined #openstack-meeting-alt15:32
*** markstur_ has joined #openstack-meeting-alt15:32
*** ijw has quit IRC15:34
*** andreas_s has quit IRC15:35
*** markstur has quit IRC15:36
*** dizquierdo has quit IRC15:39
*** gcb has quit IRC15:41
*** markstur_ has quit IRC15:42
*** markstur has joined #openstack-meeting-alt15:43
*** kzaitsev_ws has quit IRC15:44
*** bobmel has joined #openstack-meeting-alt15:46
*** rossella_ has quit IRC15:51
*** eanxgeek|log has joined #openstack-meeting-alt15:54
*** eanxgeek|log is now known as eanxgeek15:54
*** lei-zh has quit IRC15:54
*** armstrong has joined #openstack-meeting-alt15:57
*** MarkBaker has quit IRC15:57
*** sridharg has joined #openstack-meeting-alt15:58
*** annegentle has joined #openstack-meeting-alt15:58
*** rossella_ has joined #openstack-meeting-alt16:00
*** lkoranda has quit IRC16:01
*** namnh has quit IRC16:02
*** armstrong has quit IRC16:04
*** lpetrut has joined #openstack-meeting-alt16:04
*** amotoki is now known as amotoki_away16:05
*** ijw has joined #openstack-meeting-alt16:06
*** iyamahat has joined #openstack-meeting-alt16:06
*** sridharg has quit IRC16:07
*** marios has quit IRC16:07
*** ijw has quit IRC16:08
*** lucasxu has quit IRC16:08
*** matrohon has quit IRC16:09
*** gyee has joined #openstack-meeting-alt16:11
*** lkoranda has joined #openstack-meeting-alt16:13
*** rarcea has quit IRC16:13
*** shobhar has joined #openstack-meeting-alt16:18
*** shobhar_ has joined #openstack-meeting-alt16:18
*** noslzzp has joined #openstack-meeting-alt16:20
*** slaweq has joined #openstack-meeting-alt16:20
*** diga has quit IRC16:21
*** jtomasek|afk is now known as jtomasek16:24
*** jpena is now known as jpena|off16:24
*** slaweq has quit IRC16:25
*** mjura has quit IRC16:26
*** rarcea has joined #openstack-meeting-alt16:26
*** yamamoto has joined #openstack-meeting-alt16:27
*** tobberydberg has joined #openstack-meeting-alt16:28
*** yamamoto has quit IRC16:32
*** slaweq has joined #openstack-meeting-alt16:35
*** slaweq has quit IRC16:37
*** slaweq has joined #openstack-meeting-alt16:39
*** iyamahat has quit IRC16:41
*** dizquierdo has joined #openstack-meeting-alt16:44
*** ircuser-1 has joined #openstack-meeting-alt16:46
*** slaweq has quit IRC16:46
*** mnementh has joined #openstack-meeting-alt16:46
*** rossella_ has quit IRC16:47
*** SumitNaiksatam has quit IRC16:47
*** iyamahat has joined #openstack-meeting-alt16:47
*** iyamahat has quit IRC16:48
*** iyamahat has joined #openstack-meeting-alt16:49
*** mnementh has quit IRC16:53
*** mnementh has joined #openstack-meeting-alt16:53
*** bobmel_ has joined #openstack-meeting-alt16:54
*** annegentle has quit IRC16:55
*** bobmel_ has quit IRC16:57
*** iyamahat has quit IRC16:57
*** bobmel has quit IRC16:57
*** bobmel has joined #openstack-meeting-alt16:57
*** dprince has quit IRC16:58
*** derekh has quit IRC16:59
*** dprince has joined #openstack-meeting-alt17:00
*** slaweq has joined #openstack-meeting-alt17:01
*** kzaitsev_mb has joined #openstack-meeting-alt17:04
*** bobmel has quit IRC17:05
*** bogdando has quit IRC17:05
*** slaweq has quit IRC17:05
*** lkoranda has quit IRC17:09
*** dizquierdo has quit IRC17:11
*** dizquierdo has joined #openstack-meeting-alt17:11
*** rarcea has quit IRC17:13
*** Swami has joined #openstack-meeting-alt17:14
*** mnementh has quit IRC17:17
*** SumitNaiksatam has joined #openstack-meeting-alt17:17
*** lkoranda has joined #openstack-meeting-alt17:21
*** lucasxu has joined #openstack-meeting-alt17:24
*** rarcea has joined #openstack-meeting-alt17:26
*** fzdarsky has quit IRC17:27
*** jcoufal has quit IRC17:35
*** jcoufal has joined #openstack-meeting-alt17:39
*** HeOS has quit IRC17:40
*** ralonsoh has quit IRC17:41
*** tonanhngo has joined #openstack-meeting-alt17:48
*** dizquierdo has quit IRC17:48
*** felipemonteiro_ has quit IRC17:49
*** felipemonteiro has joined #openstack-meeting-alt17:49
*** felipemonteiro_ has joined #openstack-meeting-alt17:50
*** rarcea has quit IRC17:50
*** felipemonteiro has quit IRC17:53
*** tobberydberg has quit IRC17:57
*** tobberydberg has joined #openstack-meeting-alt17:57
*** rarcea has joined #openstack-meeting-alt17:58
*** Rockyg has joined #openstack-meeting-alt18:00
*** tobberydberg has quit IRC18:02
*** rmart04 has joined #openstack-meeting-alt18:03
*** MarkBaker has joined #openstack-meeting-alt18:05
*** julim_ has quit IRC18:05
*** salv-orlando has quit IRC18:07
*** rarcea has quit IRC18:08
*** salv-orlando has joined #openstack-meeting-alt18:08
*** rasca has quit IRC18:08
*** lpetrut has quit IRC18:09
*** kzaitsev_mb has quit IRC18:10
*** fzdarsky has joined #openstack-meeting-alt18:10
*** kobis has quit IRC18:10
*** kobis has joined #openstack-meeting-alt18:11
*** rasca has joined #openstack-meeting-alt18:11
*** salv-orlando has quit IRC18:12
*** kobis has quit IRC18:15
*** slaweq has joined #openstack-meeting-alt18:16
*** rarcea has joined #openstack-meeting-alt18:16
*** julim has joined #openstack-meeting-alt18:20
*** madhukar has joined #openstack-meeting-alt18:21
*** felipemonteiro_ has quit IRC18:23
*** slaweq has quit IRC18:24
*** julim has quit IRC18:25
*** madhukar has quit IRC18:26
*** rarcea has quit IRC18:26
*** felipemonteiro has joined #openstack-meeting-alt18:28
*** rmart04 has quit IRC18:28
*** florianf has quit IRC18:29
*** felipemonteiro_ has joined #openstack-meeting-alt18:29
*** JudeC has joined #openstack-meeting-alt18:29
*** felipemonteiro has quit IRC18:33
*** kzaitsev_mb has joined #openstack-meeting-alt18:33
*** janki has joined #openstack-meeting-alt18:35
*** markmcclain has quit IRC18:35
*** bfernando has quit IRC18:36
*** annegentle has joined #openstack-meeting-alt18:37
*** julim has joined #openstack-meeting-alt18:38
*** markmcclain has joined #openstack-meeting-alt18:38
*** kzaitsev_mb has quit IRC18:38
*** MarkBaker has quit IRC18:39
*** kzaitsev_mb has joined #openstack-meeting-alt18:44
*** salv-orlando has joined #openstack-meeting-alt18:49
*** adisky__ has quit IRC18:58
*** bogdando has joined #openstack-meeting-alt18:58
*** lpetrut has joined #openstack-meeting-alt19:03
*** tellesnobrega has quit IRC19:04
*** tellesnobrega has joined #openstack-meeting-alt19:06
*** slaweq has joined #openstack-meeting-alt19:11
*** shobhar_ has quit IRC19:17
*** shobhar has quit IRC19:17
*** sdague has quit IRC19:17
*** jcoufal has quit IRC19:17
*** shobhar has joined #openstack-meeting-alt19:22
*** shobhar_ has joined #openstack-meeting-alt19:22
*** salv-orlando has quit IRC19:29
*** salv-orlando has joined #openstack-meeting-alt19:30
*** ChanServ has quit IRC19:30
*** Rockyg has quit IRC19:31
*** matrohon has joined #openstack-meeting-alt19:33
*** salv-orlando has quit IRC19:35
*** ChanServ has joined #openstack-meeting-alt19:35
*** card.freenode.net sets mode: +o ChanServ19:35
*** sdague has joined #openstack-meeting-alt19:37
*** spzala has quit IRC19:39
*** spzala has joined #openstack-meeting-alt19:40
*** spzala has quit IRC19:40
*** spzala has joined #openstack-meeting-alt19:40
*** jprovazn has quit IRC19:43
*** slaweq has quit IRC19:45
*** slaweq has joined #openstack-meeting-alt19:45
*** yamahata has joined #openstack-meeting-alt19:47
*** sshnaidm is now known as sshnaidm|afk19:52
*** xyang1 has quit IRC19:55
*** spzala has quit IRC19:57
*** tobberydberg has joined #openstack-meeting-alt19:58
*** spzala has joined #openstack-meeting-alt19:58
*** xyang1 has joined #openstack-meeting-alt19:59
*** shobhar__ has joined #openstack-meeting-alt19:59
*** jkilpatr has quit IRC20:00
*** marst has quit IRC20:01
*** marst has joined #openstack-meeting-alt20:01
*** shobhar has quit IRC20:02
*** shobhar_ has quit IRC20:03
*** spzala has quit IRC20:03
*** shobhar has joined #openstack-meeting-alt20:03
*** matrohon has quit IRC20:12
*** bogdando has quit IRC20:13
*** yamahata has quit IRC20:18
*** tonanhngo has quit IRC20:19
*** shobhar has quit IRC20:21
*** shobhar__ has quit IRC20:21
*** tesseract has quit IRC20:21
*** jcoufal has joined #openstack-meeting-alt20:21
*** tonanhngo has joined #openstack-meeting-alt20:23
*** shobhar__ has joined #openstack-meeting-alt20:23
*** shobhar has joined #openstack-meeting-alt20:24
*** caowei_ has joined #openstack-meeting-alt20:26
*** tonanhngo has quit IRC20:28
*** salv-orlando has joined #openstack-meeting-alt20:28
*** caowei has quit IRC20:29
*** caowei_ is now known as caowei20:29
*** tonanhngo has joined #openstack-meeting-alt20:31
*** annegentle has quit IRC20:33
*** felipemonteiro has joined #openstack-meeting-alt20:33
*** felipemonteiro_ has quit IRC20:34
*** tonanhngo has quit IRC20:35
*** tonanhngo has joined #openstack-meeting-alt20:35
*** julim has quit IRC20:36
*** felipemonteiro_ has joined #openstack-meeting-alt20:38
*** slaweq has quit IRC20:41
*** felipemonteiro has quit IRC20:41
*** slaweq has joined #openstack-meeting-alt20:42
*** leong has joined #openstack-meeting-alt20:44
*** slaweq has quit IRC20:46
*** annabelleB has joined #openstack-meeting-alt20:47
*** jheroux has quit IRC20:49
*** ansmith has quit IRC20:49
*** Shrews has joined #openstack-meeting-alt20:52
*** tonanhngo has quit IRC20:55
*** caowei_ has joined #openstack-meeting-alt20:55
*** cleong has quit IRC20:58
*** caowei has quit IRC20:59
*** caowei_ is now known as caowei20:59
leong#startmeeting product_working_group21:01
openstackMeeting started Mon Jun 26 21:01: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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: product_working_group)"21:01
openstackThe meeting name has been set to 'product_working_group'21:01
leong#topic Rollcall21:01
*** openstack changes topic to "Rollcall (Meeting topic: product_working_group)"21:01
leonganyone here for PWG meeting?21:01
annabelleBhere!21:01
leonghi annabelleB21:02
leongi forgot to send out meeting reminder... wondering if folks will be joining today..21:02
*** tonanhngo has joined #openstack-meeting-alt21:02
leonglet's wait for a couple minutes and see if we have quorum21:02
*** annegentle has joined #openstack-meeting-alt21:03
annabelleBsounds good!21:03
*** annegentle has quit IRC21:03
*** HeOS has joined #openstack-meeting-alt21:05
*** rockyg has joined #openstack-meeting-alt21:05
leonganyone here for PWG meeting?21:05
rockygo/21:05
leonghi rockyg21:05
leongstill waiting for folks to join in....21:06
rockygHey!21:06
*** tonanhngo has quit IRC21:07
rockygseems the week is getting off to a slow start21:08
leongi guess so...21:08
*** AndyU has joined #openstack-meeting-alt21:08
*** felipemonteiro_ has quit IRC21:08
*** slaweq has joined #openstack-meeting-alt21:08
leongshamail and arkady won't join today21:08
AndyUWill we be having a meeting?21:09
leong9 min past the hour... so far i believe we have leong, rockyg AndyU and annabelleB21:09
rockygwhat about mrhillsman ?21:09
AndyUI just joined21:09
mrhillsmano/21:09
rockygWe've got 5!21:10
leonghi mrhillsman21:10
leongi suppose we can get started :-)21:10
mrhillsmanhey, overly busy week unfortunately hehe21:10
rockygYeah, life happens when you're having work21:10
leonghaha21:10
leong#link Agenda: https://wiki.openstack.org/wiki/Meetings/product-team21:10
leong#topic Review of action items21:11
*** openstack changes topic to "Review of action items (Meeting topic: product_working_group)"21:11
leonganyone got a chance to look at the moderator guide?21:11
leongi think arkady did. :-)21:12
*** kevinbenton has quit IRC21:12
rockygoops.  Nope.  Running slow.  Got a sinus infection.21:12
mrhillsmanyep, will make some changes today21:12
leongcool...21:13
leongi haven't send the email for teleconf option for midcycle yet...21:13
leongi presume that we will not have F2F this time...21:14
leongif we want to host a telecon, we also need to decide a date and time21:14
leongand also need to  figure out how to run the teleconf across timezone21:15
*** kevinbenton has joined #openstack-meeting-alt21:15
leongany comments?21:15
rockygWe might consider something like two hours at US beginning of day and 2 hours at the end.  Do it for a couple of days?21:16
leongthat can be an option21:16
leong#info Midcycle Teleconf Option 1: 2 hours at US beginning of day and 2 hours at the end, run for couple of days21:17
AndyUMaybe we could start by trying out the webmeeting format now to close up some of these action items that have been dragging on?  Such as take an hour together to do a live review/edit of wiki pages?21:17
rockyg++21:18
leongAndyU: +1 i think that will be part of Agenda21:18
leongwe need to decide the format/time first, then can work on agenda21:18
*** annegentle has joined #openstack-meeting-alt21:18
leongi will send the email on this21:19
AndyUOh... and I just remembered I said I'd add the etherpad template to mrhillsmans's moderator guide...21:19
leong#action leong to email about teleconf midcycle and format21:19
leong#topic Development Proposals21:20
*** openstack changes topic to "Development Proposals (Meeting topic: product_working_group)"21:20
leongas per last meeting, we need to build a plan to breakdown the proposal readiness assessment21:20
leongdo we want to take some time today to brainstorm a bit?21:21
*** dprince has quit IRC21:21
AndyUI'm game21:21
leongso in general, i suppose the goal is to derive a "readiness assessment checklist"21:23
rockygYes.21:23
rockygBut what should be on it?  Will the gaps analysis need to have been done?21:24
rockygCertainly use cases should be there.21:24
AndyUWe have 4 phases to a 'Development Proposal'.  The first phase produces an artifact (what do we call it?) according to the dev proposal template. What are the steps that the artifact goes through?21:24
leongrockyg: i think we are refering to the "proposal".. gap-analysis is the phase after a proposal been accepted21:25
AndyUfor example, there is a WIP stage, then what to we call the stage after that and what are the criteria for moving to it?21:25
rockygAh, thanks.21:25
leongrockyg: so the "readiness" is to make sure that such proposal is (1) the impact of it (2) valid to move forward, (3) enough resource? (4) sufficient info to move into gap-analysis phase21:26
AndyURight. I look at the Phases as (1) Requirements Definition  (2) Gap Analysis  (3) Implementation Planning  (4) Development/Delivery21:26
*** tonanhngo has joined #openstack-meeting-alt21:26
*** tonanhngo has quit IRC21:27
mrhillsmanwhy not call it a blueprint21:27
mrhillsmanor is proposal == blueprint21:28
*** spzala has joined #openstack-meeting-alt21:28
*** tonanhngo has joined #openstack-meeting-alt21:29
mrhillsmanor is that zooming in too far at this point21:29
leongmrhillsman: if you refer the standard openstack blueprint. then a proposal != blueprint21:29
leongmrhillsman: a proposal potentially can generate multiple blueprint21:29
rockygYeah.  At this point, it's use cases and/or requirements21:29
AndyUEach 'phase' has an Artifact that needs to be produced such as the 'Dev proposal' thing doc, the Gap Anaysis doc, the implementation plan and 4th is the actual delivered code21:29
rockygSo BP to detailed21:29
leongmrhillsman: however, it can be a blueprint with respect to PWG21:30
rockygtoo detailed.21:30
AndyUAnd the community is moving away from BP's to Storyboard 'Stories' right?21:30
mrhillsmani guess it makes sense to you different terminology; i'm not thinking of overlap with standard openstack def21:30
rockygAt least in OpenStack parlance as was pointed out.21:30
mrhillsmans/you/use21:30
leongthe key thing is not about calling it blueprint or proposal... the key thing is need to determine "is such proposal ready to move forward"21:31
mrhillsmanyeah, going to that21:31
AndyUthe phase one doc will contain multiple use cases which would likelely become multiople blueprints later on21:31
mrhillsmanso back to the readiness assessment21:31
rockygImplementation plan could be:  Spec (referring to multiple BPs and/or RFEs) or BP (smaller, single task) or RFE (like BP but filed in the bug tracker)21:31
mrhillsmani think thinking backwards will help21:32
mrhillsmanif it is moving to gap analysis, what does it require to be there21:32
rockygSo, review of Use cases.  Do they cover the workflow/tasks encompassed by the description?21:32
AndyUright. And I think there are steps to get there. Like going from (1) WIP to (2) PWG Analysis? to (3) Stakeholdering with impacted people/projects in the community?  What says it's been sufficiently stakeholdered and all key players agree?21:34
leongmrhillsman: +121:35
leongso we need to define a checklist for that21:35
rockygAndyU, +121:35
mrhillsmani am looking at #link https://wiki.openstack.org/wiki/ProductTeam/Development_Proposals21:35
AndyUyes, I think so, high level at least21:35
mrhillsmanand i see #link https://github.com/openstack/development-proposals/blob/master/development-proposal-template.rst21:36
mrhillsmanunless i am wrong, something in the template is the first step, and there are mandatory sections, all looks good functionally21:37
*** tobberydberg has quit IRC21:37
mrhillsmanwhat qualifies the information i put in that template?21:37
*** bfernando has joined #openstack-meeting-alt21:37
*** tobberydberg has joined #openstack-meeting-alt21:37
mrhillsmanif that is a review by the pwg, what is the criteria for the sections?21:37
AndyUCan we agree that before phase 1 can go to phase 2 (gap analysis) there should be stakeholdering and concensus among key impacted players over that phase 1 proposal/requirements?21:37
leongthe question is: how details the "content itself" must be include before we call it "ready"21:38
mrhillsmanexactly21:38
leongAndyU: +121:38
leonghey.. i created this etherpad... can we collect these points there?21:38
*** tobberydberg has quit IRC21:38
leong#link Proposal Readiness Checklist: https://etherpad.openstack.org/p/PWG-development-proposal-readiness21:38
mrhillsmanwas just thinking the same21:39
AndyUDoes the PWG seek to get it in good order (initial triaging) before pulling in stakeholders for a boader review?21:39
*** tobberydberg has joined #openstack-meeting-alt21:39
*** spzala has quit IRC21:39
rockygYes.  We do first vetting.  Or should.21:40
leongAndyU: i think that can be part of the role of PWG ..21:40
mrhillsmani want to +1 but battling the scaling with code vs people in the back of my mind21:40
*** lucasxu has quit IRC21:41
*** xyang1 has quit IRC21:41
leongto me, all proposal must have "sufficient level" of details so that such proposal can be derived into specific bp/spec for each openstack projects21:42
*** tobberydberg has quit IRC21:43
leonga proposal cannot be too "broad" , having a 10000 footview is good as an abstract but is not sufficient to dive down into feature implementation21:43
*** lpetrut has quit IRC21:43
*** tobberydberg has joined #openstack-meeting-alt21:43
rockygAgreed.  So, consider each as if they were requesting a whole new set of functionality.  Have all the requirements been covered?  Then, the gap analysis will identify what already exists that meet the new funtionality needs.21:44
rockygSo, a development proposal should not assume any of the funtionality already exists.  This is the requirements phase.  What we need, not how.21:44
AndyULeong +121:45
leongrockyg: +121:45
AndyURight. Keep solutioning out of the requirements phase21:45
leongrockyg: gap analysis will identify what already existing and what is not21:45
rockygRight.  What I said.21:46
leongrockyg: +1 Proposal is to determine "what"21:46
rockygI just didn't add the negative.21:46
rockyg;-)21:46
leonglol21:46
AndyUPhase 1 would seek to define the problem and what is desired in order to alleviate it (Problem/Requirments). Then get buy-in from all key stakeholders (and or revise until you do).21:47
*** jlk has joined #openstack-meeting-alt21:47
*** caowei_ has joined #openstack-meeting-alt21:47
*** tobberydberg has quit IRC21:48
rockyg++21:48
leongalso, it will be good if these "readiness checklist" can be quantifiable...21:49
rockygSo, key items here:  Complete problem description but not to include extraneous issues.21:49
AndyUI think you would not want to move on to Gap Analyisis until after all the key stakeholders agree on the phase 1 proposal. Need to have that concensus/buy-in21:49
rockygComprehensive requirements.  Does it have to be in the form of use cases only, or can they take other forms, too?21:50
mrhillsmanis there another word that can be used besides requirement(s)? i know it is semantics, but at this phase requirements are not known, though there is/are/could be desired outcome(s)21:50
*** caowei has quit IRC21:50
*** caowei_ is now known as caowei21:50
rockygIn some proposals, the requirments may not be known.  In others, they are.21:51
rockygThere are also a whole slew of implied requirements that emerge out of the general requirements or use cases.21:51
AndyUI think in phase 1, we need to understand that the "requirements" are more like "business requirements". They're not specifying any technical solution yet (how), jus the What21:52
rockygAndyU, ++  Good point.  Biz req's21:52
leongi tried to put the above discussion point in the etherpad https://etherpad.openstack.org/p/PWG-development-proposal-readiness21:53
leongwe can later summarized them and hopefully generate a checklist :)21:53
AndyULeong - good idea to start the etherpad21:54
rockyg++21:54
*** kzaitsev_mb has quit IRC21:54
*** caowei_ has joined #openstack-meeting-alt21:54
mrhillsman++21:54
leongthat gives other folks to express their points offline after this meeting as well :)21:55
leongwe have 5 mins to the hour21:55
leongthat's a good brainstorming session21:55
rockygagreed21:56
leongplease keep contributing to that etherpad and we can summarize that next week or so21:56
AndyUDoes this link work for you all?  https://docs.google.com/presentation/d/1FWuIModYuIxNOYFne7y-yfF70UDKOMQ2JEUeEwTtt20/edit#slide=id.p1421:56
leongAndyU: works for me21:56
rockygIt does when I'm not on the corp net ;-)21:57
leongAndyU: but you might want to double check if you "share with specific person" or "share with EVERYONE"21:57
AndyUok, good.  I offer that as a way to help conceptualize the different phases and how they connect to community cycles21:57
leongrockyg: that seems like your corp firewall/proxy issue :)21:57
mrhillsmanworks for me21:57
AndyUI selected shared with anyone who has the link21:57
*** caowei has quit IRC21:57
*** caowei_ is now known as caowei21:57
leong#action all to continue brainstorming proposal readiness on the etherpad https://etherpad.openstack.org/p/PWG-development-proposal-readiness21:58
AndyUI'll make it group editable21:58
AndyU#link https://docs.google.com/presentation/d/1FWuIModYuIxNOYFne7y-yfF70UDKOMQ2JEUeEwTtt20/edit#slide=id.p1421:58
annabelleBworks for me21:58
leongwe shall continue the proposal conversation next week21:58
leong#topic open21:58
*** openstack changes topic to "open (Meeting topic: product_working_group)"21:58
leongdoes anyone has any open?21:59
*** diablo_rojo has quit IRC21:59
mrhillsmannothing here21:59
leongalright.. good conversation!22:00
leong#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Mon Jun 26 22:00:18 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-26-21.01.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-26-21.01.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-06-26-21.01.log.html22:00
AndyUbye all!22:00
jeblairany zuul folks around?22:00
clarkbhello22:00
*** AndyU has quit IRC22:00
*** annabelleB has left #openstack-meeting-alt22:00
Shrewso/22:01
* mordred waves to jeblair22:01
*** jamielennox has joined #openstack-meeting-alt22:01
*** leong has left #openstack-meeting-alt22:01
*** kylek3h has quit IRC22:01
*** kylek3h has joined #openstack-meeting-alt22:02
jeblair#startmeeting zuul22:02
openstackMeeting started Mon Jun 26 22:02:54 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
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:03
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-12-22.04.html22:03
jeblair#topic Status updates: Standard job library22:03
*** openstack changes topic to "Status updates: Standard job library (Meeting topic: zuul)"22:03
jlko/22:04
jeblairi don't think we've made substantial progress on this since last meeting, though pabelanger did do a lot of work to get gearman running with ssl which we will need for secrets support22:04
*** smyers has joined #openstack-meeting-alt22:04
jeblairmordred and i are planning on pushing pretty hard on this in the next week or two, i believe22:05
*** rockyg has quit IRC22:05
jeblaironce we get going, hopefully we can get the bonnyci folks, and software factory too, looking at the shared jobs repo22:06
Shrews++22:06
*** kylek3h has quit IRC22:06
jeblairanything else to add on this?22:06
*** tonanhngo has quit IRC22:07
jlkReady to review! :)22:08
jeblair#topic Status updates: Documentation22:08
*** openstack changes topic to "Status updates: Documentation (Meeting topic: zuul)"22:08
jeblairi did a lot of work on documentation over the past week22:09
jeblair#link https://review.openstack.org/46332822:09
jeblair#link https://review.openstack.org/47592822:09
mordredyah. them's a lot of words22:09
jeblairthose are the biggest changes, but they are at the top of a stack.22:09
jlkI just spent a significant chunk of today (re)reading the first one.22:10
SpamapSvery excited to see docs starting to form22:10
mordred++22:10
mordredme too22:10
Shrewsi LOVE when others write much needed documentation22:10
jeblairthe whole stack is ready for review, and it was green earlier today, though i merged tristanC's config default change which conflicts with some of them.  they will be easy to fix, so expect new revs tomorrow.22:10
jeblairi know there's still a lot more to do (especially we need more examples, some of which should be in-line, some of which should be appendices)22:10
*** rwsu has quit IRC22:11
jeblairand i think there's still some polish that could happen on higher-level overview stuff22:11
*** tonanhngo has joined #openstack-meeting-alt22:11
* Shrews read that as "Polish"22:11
jeblairbut i'm hoping that's enough of a skeleton for us to build on  (i mean, it's more than a skeleton, it is pretty substantial, but you get the idea)22:11
jeblairShrews: reverse polish?22:11
jlkjeblair: hopefully you can refrain from rebasing the changes, right? So that sub-patchset level comparisons can still be used if/when you make changes?22:11
jeblairjlk: i will need to rebase most of the stack in order to fix the conflicts, but i will do a two-step rebase to make it easier22:12
jeblairjlk: i'll rebase without changes first, and annotate that so you can ignore that inter-patchset diff22:12
jlkkk22:12
jeblairjlk: then i'll fix the conflicts in its own chaneg22:13
jeblairmaybe.  if possible.22:13
jeblairif i can't, i'll just make sure that i only change the minimum to fix conflicts in the rebase.22:13
*** tonanhngo has quit IRC22:13
*** tonanhngo has joined #openstack-meeting-alt22:14
jlkappreciated22:14
jeblairi've tried to build a narrative structure in each of the user/admin guides so we're sort of taking users or admins through a learning process.22:14
jeblairi'm sure it's not fully there yet, but that's what i was aiming for22:15
*** kzaitsev_mb has joined #openstack-meeting-alt22:15
jlkit's a good read22:15
jlkThey're good words, Jom.22:16
jeblairi'm very eager to land these asap, and then resume our practice of changing docs with code.  :)22:16
mordredyes. this will be quite nice22:16
*** fzdarsky has quit IRC22:16
* Shrews will review Jom's words tomorrow22:17
*** yamahata has joined #openstack-meeting-alt22:17
*** janki has quit IRC22:17
jeblairthe second change is all kinds of reorg, much of which changes again later.  i don't know how to make that better, sorry.22:18
jeblairalso, keep in mind that the docs job renders everything, so folks may enjoy reading the final rendered form in later changes.  :)22:18
jeblairi've consulted it several times today22:19
jeblairanything else?22:19
clarkbif you pull the second change and look at it locally I think git itself might be able to better show you the file moves?22:19
clarkbmaybe not22:19
*** kzaitsev_mb has quit IRC22:20
jeblairclarkb: yeah, i'm not sure.  i took notes while writing it.  :|22:21
*** mrhillsman is now known as codebauss22:22
jeblair#topic Status updates: Github parity22:22
*** openstack changes topic to "Status updates: Github parity (Meeting topic: zuul)"22:22
*** codebauss is now known as mrhillsman22:22
jeblairjlk: do you have any outstanding changes related to this?22:23
jlkThere are a couple open.22:23
jlkDepends-On for github, and a fix to support push events better (non pull-request)22:23
jlkI also noticed while reading through docs that we could do a better job of supporting statsd metrics in the github driver22:24
jeblairgood point; now's probably a good time to add that22:24
jlkOh, and Depends-On is partial, it does not do the helpful thing of back-searching to discover needed-by changes to re-enqueue.22:24
jlkthe back searching is going to be limited by what github supports in search, as we discussed at AnsibleFest.22:25
jlkWe might be able to get partially there just by checking our own cache of change information, but that could lead to non-deterministic behavior.22:25
jeblairyeah, we still need to decide how to handle that.  we brainstormed some ideas about that; i think our choices are roughly: (a) don't support it; (b) move depends-on into pull request messages rather than commits; (c) perform some kind of local memoization so we just ask ourselves for the info22:26
jeblair(c) is growing on me22:26
jeblairthe amount of data we would need to keep is tiny, i think.22:26
mordredI believe b and c are better outcomes than a22:26
jlkC feels fairly easy to implement, if we ignore lost cache during restarts.22:26
jamielennoxc is useful as we should know, but aren't we already doing (b)22:26
clarkbbigger problem is probably making sure that you've collected all the data right?22:26
clarkbfor c22:27
jeblairjlk: i think we can have the scheduler go ahead and store the data on disk to persist between restarts.22:27
jamielennoxi don't think it makes sense to have depends-on in commit messages for github22:27
mordredclarkb: well - the only thing that could be blocked on a depends-on is a previously-gotten event22:27
jlkclarkb: so far, we are. Every change we runtime cache we grab every commit message of every commit on the change.22:27
mordredah - different question. jlk's answer is better than mine22:27
jlkjamielennox: you prefer that they be read from pull request comments instead?22:28
mordredI thought we did not get an event when a PR summary changes?22:28
jamielennoxi thought we were doing from the pull request body, i mean you have to merge the full PR22:28
jlkI'll have to test.22:28
jamielennoxbut not comments on a PR22:29
clarkbjlk: right but hat happens when you take a 4 hours downtime and github changes a bunch?22:29
mordredbtw - I think we should do c even if we do b - because gh rate-limiting means if we can avoid the extra query it would be valuable22:29
jlkwell.... lets take a step back here22:29
clarkbor are you saying that its ok because next eent you'd just repopulate complete cache?22:29
jlkclarkb: (yes that)22:29
mordred++ to that22:29
mordredif there's a zuul downtime people are going to need to recheck anyway22:30
jlkIf we listen to jamielennox , and shift the data source to pull comments22:30
jeblair(or admin enqueue events or something)22:30
jlkwe can avoid some of this problem22:30
mordredwell- I think pull comments are the wrong place - pull summary would be the more similar place, no?22:30
jlk(it'll introduce some new problems, but not insurmountable)22:30
jamielennoxmordred: right, not arbitrary comments added to the PR22:31
mordredsummary goes into merge commit message22:31
jamielennoxjust the summary22:31
mordredjamielennox: ++22:31
jlkhah, well, okay22:31
*** yamahata has quit IRC22:31
mordredI thought we did not get events when that updates?22:31
jlkyes, we'd just have to be aware when that changs.22:31
jlkes22:31
jlkone sec22:31
jamielennoxnot sure22:31
*** slaweq has quit IRC22:31
*** caowei_ has joined #openstack-meeting-alt22:31
jamielennoxalso, it seems right to me on the PR, but i'm used to gerrit so all my PRs are one commit long22:31
*** marst has quit IRC22:32
jamielennoxbut there are some great/shocking examples of 200 commits to a PR that i think mean PR is about the only place they make sense22:32
jlkChanging the PR summary generates a comment event with an action of "edited"22:32
mordredcool. so we can react to that and notice a depends-on has been added or removed22:32
jlksure, we'd just have to ensure we're only looking at the "special" comment22:33
jlkwhich is the PR summary22:33
jeblairjamielennox: i think the behavior is that if any of those 200 events have a depends-on footer, then the pr depends on that.  but putting it in the commit lets you say "this commit depends on this functionality", and that's something that will transit through multiple git repos, etc.  it's a property of the commit, rather than the (somewhat more transient) pull request.22:33
mordredjeblair: yah - I think I'm coming to the other pov on that ... for github users, the PR is the unit of work, not the commit - removing a depends-on footer if it stops being true would also become potentially hard22:34
mordredfor folks who do not rebase their branches but instead push new patches on top of a branch22:34
clarkbespecially since old commits and comments go away when you rebase right?22:34
jamielennoxyea, ok, i see it's useful to reference it in the commit that uses it. but everything else we do is via PR, like you can't address a commit in a PR like BonnyCI/zuul#32@1 so your PR is really your unit in GH22:34
*** caowei has quit IRC22:34
jlkThe PR Summary is implemented as the first comment of the PR, we'd have to identify this and make it "special"22:34
jamielennoxjlk: there's nothing that identifies the PR body as special at all in an event?22:35
mordredclarkb: old commits do - old comments stay around22:35
jlknot that I've seen :(22:35
*** marst has joined #openstack-meeting-alt22:35
clarkbmordred: only top level comments though right?22:36
jlkugh22:36
*** spzala has joined #openstack-meeting-alt22:36
mordredclarkb: hrm. I thought in-line comments also stuck around and were marked as "for a previous revision" with a red x22:36
jlkhaha22:36
jlkguys you're on a tangent22:36
mordredwe are indeed22:36
jlkthose are "different" as they're "review comments"22:36
jlknot to be confused with Pull Request Review comments22:36
jlkThere's comments to the PR which you see on the front page22:37
*** caowei has joined #openstack-meeting-alt22:37
mordredah22:37
jlkthere's review comments which are made in-line with the source code22:37
jlkand then there's Pull Request Review comments22:37
jamielennoxwhich GH implemented as a special type of issue, which confuses this more - but digression22:37
*** caowei_ has quit IRC22:37
jlkFrom the webhook data I'm looking at, I don't even see an identifier for _which_ comment was edited.22:38
mordredjlk: you can edit comments other than the summary?22:38
jlkyes22:38
jamielennoxjlk: so you could still say a comment was editted on this PR and fetch it again? not greatest but it would catch it22:38
jlkhttp://paste.openstack.org/show/613760/ is hte payload22:39
mordredoh wow. you really can edit comments. that's so weird to me22:39
jlkjamielennox: yeah, we could fetch and then re-examine the "first" comment.22:39
jeblairokay, so there's some support for moving this to PR summary.  how about we dive deeper into this and make sure that doing so is both workable and a solution to the needed-by problem, and regroup?22:40
jamielennoxhmm, crazy that the PR body is only considered a comment22:40
mordred++22:40
mordredto both jeblair and jamielennox22:40
jamielennox++22:40
jlk++22:40
*** AndyU has joined #openstack-meeting-alt22:40
*** spzala has quit IRC22:40
jeblairjlk: okay if i action you with that?22:41
jlkworksforme22:41
jeblair#action jlk look into moving depends-on to pull-request summary to see if it is both workable and a solution to the needed-by problem22:41
jeblaircool, thanks.. let's move on to make sure we don't run out of time22:42
jeblair#topic Status updates: (web) console streaming22:42
*** openstack changes topic to "Status updates: (web) console streaming (Meeting topic: zuul)"22:42
*** caowei has quit IRC22:42
Shrewsoh, hey. that's an agenda item now22:42
*** caowei has joined #openstack-meeting-alt22:43
Shrewsnot sure what to say except that i've hit a roadblock and had to swallow my pride and ask for help from the original author and Dear Leader22:44
*** chyka_ has joined #openstack-meeting-alt22:44
*** caowei has quit IRC22:44
* mordred is also going to help swear at things22:44
*** caowei has joined #openstack-meeting-alt22:45
clarkbhave the problems been described anywhere yet?22:45
Shrewsclarkb: not publicly, no22:45
*** rarora has joined #openstack-meeting-alt22:45
jeblairhopefully we can figure out in the next couple days if the problems are "merely technical" or something more fundamental that would cause us to re-evaluate our approach22:46
jeblairi think we're at the "this doesn't seem to work; not sure what's going on" stage22:46
*** chyka has quit IRC22:46
Shrewsyeah. if it's a stupid programmer (aka, me) error, we can move forward. if it's an architectural thing, then public input may be needed22:46
*** annegentle has quit IRC22:47
jeblairi'm going to skip some topics and move on to...22:48
jeblair#topic Removing py2 support from v3 nodepool (Shrews)22:48
*** openstack changes topic to "Removing py2 support from v3 nodepool (Shrews) (Meeting topic: zuul)"22:48
SpamapSOne thing I've never liked about async "futures" style coding is that it is often just hard to see wtf is going on inside the machine.22:48
jeblair#link https://review.openstack.org/47668322:48
SpamapS(that was regarding the web streaming)22:48
Shrewsmordred and I were discussing https://review.openstack.org/476683 this morning, and it came up that maybe we should stop supporting py2 in feature/zuulv3 nodepool22:48
jeblairSpamapS: [me too; part of why i want to keep that kind of code in its own sandbox]22:49
mordredyah - if we don't support py2 in zuulv3 of zuul, I'm not sure why we should support it in nodepool - of course, we need to start running infra's nodepool in v3 before we drop it22:49
clarkbShrews: mordred my concern with that right now is python35 integration test does not work on nodepool22:49
mordredclarkb: that's a great concern!22:50
clarkbI think we need to get the testing solid on python3 first then make that assertion22:50
mordredclarkb: we sohuld, you know fix that :)22:50
mordred++22:50
clarkbbecause right now python2 is what works based on testing22:50
Shrewsclarkb: that's a very valid point22:50
jeblairclarkb: the devstack one, or the zuul one?22:50
clarkb(I think it may work on feature branch but not master)22:50
clarkbjeblair: the devstack one22:50
mordredoh. yah - I only mean on feature/22:50
clarkbmordred: so I think you have to do both at the same time actually22:51
mordredbut we should _definitely_ make sure testing is solid before doing anything22:51
clarkband the reason for that is we have a habit of fixing things on feature first then maybe backporting to master22:51
clarkband you can't backport anymore if different pythons are supported22:51
Shrewsdevstack, from what i've seen. weird errors, like: http://logs.openstack.org/23/476223/2/check/gate-dsvm-nodepool-py35-src-nv/af51324/logs/devstacklog.txt.gz#_2017-06-26_17_03_17_40222:51
clarkbShrews: ya it has to do with setuptools and permissions and stuff I think22:52
clarkbShrews: its good python fun22:52
mordredso - let's maybe reframe this to "before we release nodepool v3, we should drop python2 support" - largely because I dont' think we want to grow new python2 based users that makes it hard to drop support22:52
Shrewsmordred: yes, that's a good way to put it. A goal to move towards22:52
mordredand between now and then, we should definitely make sure that all the python3 testing is solid and that infra is running nodepool v3 on python322:52
mordredsince those are both just good ideas for sanity and consistency22:53
jeblairmordred: i'm okay with that, though i note that it doesn't address the immediate need, which was driven by "we want to land some code in v3 that is much simpler (like, a hundred lines plus an external dependency) with py322:53
SpamapSdoes this maybe up the priority of shimming?22:53
mordredjeblair: indeed22:53
Shrewsjeblair: to be fair, i *really* like harlowja's change, but it isn't something that's needed RIGHT NOW.22:54
clarkbI'm ok with doing it I just think it has to be done on both branches together with working tests22:54
clarkbShrews: also that, it may save like a second on shutdown22:54
harlowjai save all the seconds, lol22:54
clarkbnot super urgent but a nice code cleanliness thing22:54
Shrewswell, could be several seconds, but yeah22:54
jeblairSpamapS: i think the main gains of shimming were load testing plus ease of transition for openstack-infra; so i don't see this as driving a further need for that.22:55
SpamapSOh I thought maybe shimming would let us get onto feature/ sooner.22:55
SpamapSso we wouldn't be backporting so much22:55
jeblairSpamapS: oh, hrm.  i guess it would?22:56
jeblairlike, we could go ahead and merge feature back into master22:56
*** sdague has quit IRC22:56
*** JillS has joined #openstack-meeting-alt22:56
jeblairbut it sounds like our immediate needs aren't important enough to push that though22:57
jeblairwe can shelve harlowja's change until we're ready to do that anyway, and we'll survive22:57
harlowjawfm22:58
jeblairi will buy harlowja a cookie22:58
Shrewsso, is it a goal that we remove py2 support from nodepool before release then?22:58
jeblair+122:58
jeblair#topic Surprise bonus topic: should we meet next week?22:59
*** openstack changes topic to "Surprise bonus topic: should we meet next week? (Meeting topic: zuul)"22:59
jeblairi just realized i'm going to be sitting around watching a smoker all day next monday22:59
jeblair(it's the day before a holiday, so i will probably make it a 4 day weekend)23:00
Shrewsi'm considering taking all of next week off, so +1 from me23:00
jeblairwould folks like to cancel the meeting, or someone else want to chair?23:00
*** fnaval_ has joined #openstack-meeting-alt23:00
*** fnaval_ has quit IRC23:00
jlkI'm okay w/out a meeting23:00
*** fnaval_ has joined #openstack-meeting-alt23:00
jlkI'll report my investigations by way of a gerrit change23:00
jeblairokay, i'll wait for a volunteer chair until tomorrow and without one, i will send a cancellation notice23:01
jeblairthanks all!23:01
* SpamapS is +023:01
jeblair#endmeeting23:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:01
openstackMeeting ended Mon Jun 26 23:01:46 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-06-26-22.02.html23:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-26-22.02.txt23:01
*** fnaval has quit IRC23:01
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-06-26-22.02.log.html23:01
*** Shrews has left #openstack-meeting-alt23:01
*** bfernando has quit IRC23:08
*** annegentle has joined #openstack-meeting-alt23:09
*** iyamahat has joined #openstack-meeting-alt23:11
*** marst has quit IRC23:13
*** iyamahat has quit IRC23:13
*** kzaitsev_mb has joined #openstack-meeting-alt23:20
*** hongbin has quit IRC23:20
*** fzdarsky has joined #openstack-meeting-alt23:27
*** tonanhngo has quit IRC23:30
*** SumitNaiksatam has quit IRC23:32
*** tonanhngo has joined #openstack-meeting-alt23:32
*** fzdarsky has quit IRC23:32
*** Swami has quit IRC23:41
*** tonanhngo has quit IRC23:42
*** marst has joined #openstack-meeting-alt23:44
*** tonanhngo has joined #openstack-meeting-alt23:46
*** tonanhngo has quit IRC23:51
*** MarkBaker has joined #openstack-meeting-alt23:57
*** JudeC has quit IRC23:58

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