Monday, 2017-03-27

*** amotoki has quit IRC00:01
*** baoli has joined #openstack-meeting-alt00:16
*** mtanino has joined #openstack-meeting-alt00:19
*** bbbzhao has quit IRC00:20
*** bzhao has joined #openstack-meeting-alt00:21
*** jesusaur has quit IRC00:26
*** mtanino has quit IRC00:26
*** baoli has quit IRC00:29
*** jesusaur has joined #openstack-meeting-alt00:30
*** jesusaur has quit IRC00:31
*** jkilpatr has quit IRC00:31
*** jkilpatr has joined #openstack-meeting-alt00:31
*** kzaitsev_mb has quit IRC00:40
*** mickeys has joined #openstack-meeting-alt01:01
*** markvoelker has joined #openstack-meeting-alt01:01
*** hiro-kobayashi has joined #openstack-meeting-alt01:03
*** amotoki has joined #openstack-meeting-alt01:04
*** yuanying_ has joined #openstack-meeting-alt01:04
*** mickeys has quit IRC01:06
*** yuanying has quit IRC01:07
*** cloudrancher has quit IRC01:07
*** cloudrancher has joined #openstack-meeting-alt01:08
*** reedip has quit IRC01:10
*** EricGonczer_ has quit IRC01:15
*** jesusaur has joined #openstack-meeting-alt01:15
*** gcb has joined #openstack-meeting-alt01:15
*** ihrachys has quit IRC01:16
*** tonytan4ever has joined #openstack-meeting-alt01:17
*** EricGonczer_ has joined #openstack-meeting-alt01:19
*** caowei has joined #openstack-meeting-alt01:22
*** amotoki has quit IRC01:27
*** daidv has joined #openstack-meeting-alt01:30
*** jesusaur has quit IRC01:34
*** kzaitsev_mb has joined #openstack-meeting-alt01:37
*** tuanluong has joined #openstack-meeting-alt01:37
*** jesusaur has joined #openstack-meeting-alt01:40
*** tovin07 has joined #openstack-meeting-alt01:41
*** reedip has joined #openstack-meeting-alt02:00
*** dave-mccowan has quit IRC02:09
*** gouthamr has quit IRC02:16
*** EricGonczer_ has quit IRC02:18
*** kzaitsev_mb has quit IRC02:21
*** yamamoto has joined #openstack-meeting-alt02:25
*** yuanying has joined #openstack-meeting-alt02:30
*** yuanying_ has quit IRC02:33
*** amotoki has joined #openstack-meeting-alt02:42
*** yamamoto has quit IRC02:43
*** yamamoto has joined #openstack-meeting-alt02:43
*** amotoki has quit IRC02:53
*** reedip has quit IRC02:58
*** cdearborn has quit IRC02:59
*** mickeys has joined #openstack-meeting-alt03:02
*** amotoki has joined #openstack-meeting-alt03:06
*** mickeys has quit IRC03:06
*** dimtruck is now known as zz_dimtruck03:07
*** zz_dimtruck is now known as dimtruck03:07
*** links has joined #openstack-meeting-alt03:09
*** caowei has quit IRC03:12
*** caowei has joined #openstack-meeting-alt03:12
*** yamamoto has quit IRC03:16
*** dimtruck is now known as zz_dimtruck03:16
*** kzaitsev_mb has joined #openstack-meeting-alt03:17
*** yamamoto has joined #openstack-meeting-alt03:18
*** reedip has joined #openstack-meeting-alt03:30
*** amotoki has quit IRC03:31
*** gcb has quit IRC03:33
*** yamamoto has quit IRC03:35
*** gongysh has joined #openstack-meeting-alt03:45
*** kzaitsev_mb has quit IRC03:51
*** amotoki has joined #openstack-meeting-alt03:52
*** gcb has joined #openstack-meeting-alt03:58
*** gongysh has quit IRC04:03
*** hiro-kobayashi has quit IRC04:05
*** zz_dimtruck is now known as dimtruck04:07
*** dimtruck is now known as zz_dimtruck04:17
*** adisky_ has joined #openstack-meeting-alt04:21
*** yamamoto has joined #openstack-meeting-alt04:22
*** radeks has joined #openstack-meeting-alt04:28
*** mickeys has joined #openstack-meeting-alt04:51
*** jrobinson has quit IRC04:55
*** jrobinson has joined #openstack-meeting-alt05:04
*** zz_dimtruck is now known as dimtruck05:06
*** pgadiya has joined #openstack-meeting-alt05:10
*** anilvenkata has joined #openstack-meeting-alt05:12
*** sshank has quit IRC05:14
*** sshank has joined #openstack-meeting-alt05:14
*** dimtruck is now known as zz_dimtruck05:16
*** gongysh has joined #openstack-meeting-alt05:19
*** rcernin has joined #openstack-meeting-alt05:26
*** tobiash_ has left #openstack-meeting-alt05:28
*** tonytan4ever has quit IRC05:41
*** pgadiya has quit IRC05:41
*** caowei has quit IRC05:42
*** caowei has joined #openstack-meeting-alt05:42
*** mjura has joined #openstack-meeting-alt05:43
*** rwsu has quit IRC05:47
*** skramaja has joined #openstack-meeting-alt05:48
*** caowei has quit IRC05:49
*** ltomasbo|away is now known as ltomasbo05:56
*** trinaths has joined #openstack-meeting-alt05:58
*** dsariel has joined #openstack-meeting-alt06:01
*** florianf has joined #openstack-meeting-alt06:05
*** zz_dimtruck is now known as dimtruck06:07
*** mickeys has quit IRC06:16
*** dimtruck is now known as zz_dimtruck06:17
*** lpetrut has joined #openstack-meeting-alt06:18
*** sridharg has joined #openstack-meeting-alt06:19
*** nadya has joined #openstack-meeting-alt06:20
*** reedip has quit IRC06:24
*** jprovazn has joined #openstack-meeting-alt06:26
*** nkrinner_afk is now known as nkrinner06:28
*** andreas_s has joined #openstack-meeting-alt06:29
*** dsariel has quit IRC06:36
*** tuanluong has quit IRC06:50
*** nadya has quit IRC06:55
*** ralonsoh has joined #openstack-meeting-alt06:55
*** reedip has joined #openstack-meeting-alt06:56
*** ltomasbo is now known as ltomasbo|away06:57
*** kobis has joined #openstack-meeting-alt06:59
*** zz_dimtruck is now known as dimtruck07:01
*** mickeys has joined #openstack-meeting-alt07:02
*** vAlexa has quit IRC07:07
*** alexchadin has joined #openstack-meeting-alt07:07
*** dimtruck is now known as zz_dimtruck07:11
*** dsariel has joined #openstack-meeting-alt07:13
*** acabot has quit IRC07:17
*** sankarshan has quit IRC07:19
*** sankarshan has joined #openstack-meeting-alt07:19
*** jrobinson has quit IRC07:19
*** tuanluong has joined #openstack-meeting-alt07:31
*** jpena|off is now known as jpena07:34
*** bfernando has joined #openstack-meeting-alt07:38
*** tonytan4ever has joined #openstack-meeting-alt07:41
*** caowei has joined #openstack-meeting-alt07:42
*** tesseract has joined #openstack-meeting-alt07:44
*** aarefiev_afk is now known as aarefiev07:47
*** jpena is now known as jpena|off07:47
*** vAlexa has joined #openstack-meeting-alt07:51
*** acabot has joined #openstack-meeting-alt07:52
*** kzaitsev_ws has joined #openstack-meeting-alt07:54
*** jpena|off is now known as jpena07:54
*** rossella_s has joined #openstack-meeting-alt08:02
*** zz_dimtruck is now known as dimtruck08:02
*** nadya has joined #openstack-meeting-alt08:04
*** matrohon has joined #openstack-meeting-alt08:04
*** rarcea has joined #openstack-meeting-alt08:09
*** dimtruck is now known as zz_dimtruck08:11
*** itamaro has joined #openstack-meeting-alt08:11
*** itamaro has quit IRC08:12
*** mickeys has quit IRC08:16
*** irenab has left #openstack-meeting-alt08:17
*** irenab_ has joined #openstack-meeting-alt08:20
*** tovin07_ has joined #openstack-meeting-alt08:22
*** reedip has quit IRC08:23
*** irenab_ has quit IRC08:23
*** IgorYozhikov has quit IRC08:25
*** akuznetsova has quit IRC08:25
*** rakhmerov has quit IRC08:26
*** mattymo has quit IRC08:26
*** rakhmerov has joined #openstack-meeting-alt08:26
*** reedip has joined #openstack-meeting-alt08:27
*** IgorYozhikov has joined #openstack-meeting-alt08:27
*** akuznetsova has joined #openstack-meeting-alt08:27
*** mattymo has joined #openstack-meeting-alt08:27
*** dizquierdo has joined #openstack-meeting-alt08:32
*** derekh has joined #openstack-meeting-alt08:37
*** tonytan4ever has quit IRC08:42
*** rossella_s has quit IRC08:42
*** rossella_s has joined #openstack-meeting-alt08:43
*** caowei has quit IRC08:43
*** ccamacho has joined #openstack-meeting-alt08:44
*** lpetrut has quit IRC08:45
*** lpetrut has joined #openstack-meeting-alt08:45
*** lpetrut has quit IRC08:48
*** lpetrut has joined #openstack-meeting-alt08:51
*** zz_dimtruck is now known as dimtruck09:02
*** apetrich has quit IRC09:06
*** bogdando has joined #openstack-meeting-alt09:09
*** arxcruz has quit IRC09:11
*** dimtruck is now known as zz_dimtruck09:12
*** mickeys has joined #openstack-meeting-alt09:17
*** mickeys has quit IRC09:21
*** arxcruz has joined #openstack-meeting-alt09:22
*** egallen has joined #openstack-meeting-alt09:23
*** iyamahat has joined #openstack-meeting-alt09:23
*** yamahata has quit IRC09:26
*** dizquierdo has quit IRC09:26
*** bogdando has quit IRC09:30
*** bogdando has joined #openstack-meeting-alt09:31
*** iyamahat has quit IRC09:33
*** r-mibu has quit IRC09:40
*** ozamiatin has joined #openstack-meeting-alt09:44
*** sambetts_ is now known as sambetts09:51
*** reedip has quit IRC09:54
*** lpetrut has quit IRC09:57
*** lpetrut has joined #openstack-meeting-alt09:57
*** ozamiatin has quit IRC09:59
*** nadya has quit IRC10:02
*** zz_dimtruck is now known as dimtruck10:03
*** dimtruck is now known as zz_dimtruck10:13
*** daidv has quit IRC10:15
*** bauwser is now known as bauzas10:17
*** mickeys has joined #openstack-meeting-alt10:18
*** mickeys has quit IRC10:22
*** neiljerram has joined #openstack-meeting-alt10:23
*** tovin07 has quit IRC10:27
*** tovin07_ has quit IRC10:27
*** fzdarsky has joined #openstack-meeting-alt10:30
*** amotoki has quit IRC10:30
*** yatinkarel has quit IRC10:34
*** gongysh has quit IRC10:35
*** panda|pto is now known as panda10:35
*** sdague has joined #openstack-meeting-alt10:38
*** sdague_ has joined #openstack-meeting-alt10:38
*** sdague has quit IRC10:39
*** sdague_ is now known as sdague10:40
*** nadya has joined #openstack-meeting-alt10:40
*** tonytan4ever has joined #openstack-meeting-alt10:42
*** fzdarsky has quit IRC10:43
*** dstepanenko has joined #openstack-meeting-alt10:43
*** yatinkarel has joined #openstack-meeting-alt10:47
*** r-mibu has joined #openstack-meeting-alt10:50
*** yatinkarel has quit IRC10:53
*** reedip has joined #openstack-meeting-alt10:54
*** florianf has quit IRC10:57
*** ccamacho is now known as ccamacho|lunch11:02
*** yatinkarel has joined #openstack-meeting-alt11:05
*** apetrich has joined #openstack-meeting-alt11:07
*** ansmith has quit IRC11:08
*** dstepanenko has quit IRC11:13
*** reedip has quit IRC11:15
*** florianf has joined #openstack-meeting-alt11:16
*** dave-mccowan has joined #openstack-meeting-alt11:19
*** bfernando has quit IRC11:19
*** yatinkarel has quit IRC11:24
*** gcb has quit IRC11:25
*** florianf has quit IRC11:31
*** florianf has joined #openstack-meeting-alt11:31
*** zhurong has joined #openstack-meeting-alt11:31
*** yatinkarel has joined #openstack-meeting-alt11:36
*** zz_dimtruck is now known as dimtruck11:40
*** dizquierdo has joined #openstack-meeting-alt11:40
*** tonytan4ever has quit IRC11:42
*** amotoki has joined #openstack-meeting-alt11:46
*** rfolco has joined #openstack-meeting-alt11:53
*** lpetrut has quit IRC11:54
*** lpetrut has joined #openstack-meeting-alt11:54
*** jaypipes has joined #openstack-meeting-alt11:55
*** tuanluong has quit IRC11:56
*** EricGonczer_ has joined #openstack-meeting-alt11:57
*** yatinkarel has quit IRC12:08
*** dprince has joined #openstack-meeting-alt12:10
*** erlon has joined #openstack-meeting-alt12:11
*** lpetrut has quit IRC12:11
*** lpetrut has joined #openstack-meeting-alt12:11
*** dave-mccowan has quit IRC12:12
*** trinaths has left #openstack-meeting-alt12:12
*** zhurong has quit IRC12:12
*** apetrich has quit IRC12:15
*** ccamacho|lunch is now known as ccamacho12:16
*** yatinkarel has joined #openstack-meeting-alt12:20
*** gouthamr has joined #openstack-meeting-alt12:21
*** alexchadin has quit IRC12:22
*** yatinkarel has quit IRC12:28
*** xyang1 has joined #openstack-meeting-alt12:28
*** dsariel has quit IRC12:30
*** haleyb has quit IRC12:32
*** jpena is now known as jpena|lunch12:39
*** links has quit IRC12:40
*** ansmith has joined #openstack-meeting-alt12:40
*** yatinkarel has joined #openstack-meeting-alt12:42
*** rossella_s has quit IRC12:42
*** rossella_s has joined #openstack-meeting-alt12:43
*** dsariel has joined #openstack-meeting-alt12:43
*** EricGonczer_ has quit IRC12:44
*** tonytan4ever has joined #openstack-meeting-alt12:45
*** markvoelker has quit IRC12:47
*** tonytan4ever has quit IRC12:48
*** reedip has joined #openstack-meeting-alt12:48
*** michapma_dsk has joined #openstack-meeting-alt12:51
*** bfernando has joined #openstack-meeting-alt12:52
*** apetrich has joined #openstack-meeting-alt12:58
*** cknight has joined #openstack-meeting-alt13:00
*** jpena|lunch is now known as jpena13:02
*** baoli has joined #openstack-meeting-alt13:03
*** apetrich has quit IRC13:03
*** jcoufal has joined #openstack-meeting-alt13:05
*** mickeys has joined #openstack-meeting-alt13:10
*** cdearborn has joined #openstack-meeting-alt13:12
*** ihrachys has joined #openstack-meeting-alt13:12
*** haleyb has joined #openstack-meeting-alt13:14
*** apetrich has joined #openstack-meeting-alt13:15
*** alexchadin has joined #openstack-meeting-alt13:16
*** mickeys has quit IRC13:16
*** treiz has quit IRC13:17
*** gcb has joined #openstack-meeting-alt13:25
*** gongysh has joined #openstack-meeting-alt13:26
*** michapma_dsk has quit IRC13:28
*** jprovazn has quit IRC13:31
*** tonytan4ever has joined #openstack-meeting-alt13:31
*** cknight has quit IRC13:36
*** gouthamr_ has joined #openstack-meeting-alt13:36
*** cknight has joined #openstack-meeting-alt13:36
*** gouthamr has quit IRC13:36
*** dimtruck is now known as zz_dimtruck13:38
*** zz_dimtruck is now known as dimtruck13:38
*** dsariel has quit IRC13:41
*** tommylikehu_ has joined #openstack-meeting-alt13:44
*** jianghuaw_ has joined #openstack-meeting-alt13:47
*** dimtruck is now known as zz_dimtruck13:47
*** IgorYozhikov has quit IRC13:49
*** mriedem has joined #openstack-meeting-alt13:50
*** IgorYozhikov has joined #openstack-meeting-alt13:51
*** gcb has quit IRC13:54
*** gcb has joined #openstack-meeting-alt13:54
*** nadya has quit IRC13:55
*** anilvenkata has quit IRC13:55
*** treiz has joined #openstack-meeting-alt13:55
*** egallen has quit IRC13:56
*** akuznetsova has quit IRC13:56
*** mtanino has joined #openstack-meeting-alt13:57
*** pashkin has quit IRC13:59
*** jprovazn has joined #openstack-meeting-alt13:59
*** pashkin has joined #openstack-meeting-alt13:59
*** vAlexa has quit IRC14:00
*** markvoelker has joined #openstack-meeting-alt14:00
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Mar 27 14:00:28 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
mriedemo/14:00
*** hongbin has joined #openstack-meeting-alt14:00
edleafeGood UGT morning! Who's here?14:00
alex_xuo/14:00
macszhello Monday world14:00
edleafe#link Agenda: https://wiki.openstack.org/wiki/Meetings/NovaScheduler14:01
edleafeI know that cdent is on PTO today.14:01
edleafeHope jaypipes is around...14:02
alex_xuand bauzas :)14:02
jroll\o14:03
*** akuznetsova has joined #openstack-meeting-alt14:03
jaypipesedleafe: I'm not unfortunately. I know I need to do reviews on traits stuff, and I will be spending 4 hours today doing those.14:03
alex_xujaypipes: thanks14:03
edleafejaypipes: ok. I have a POC for the auto-import14:03
edleafe#link autoimport: https://github.com/EdLeafe/autoimport14:04
jaypipesedleafe: awesome.14:04
*** zz_dimtruck is now known as dimtruck14:04
edleafe#topic Specs & Reviews14:04
*** openstack changes topic to "Specs & Reviews (Meeting topic: nova_scheduler)"14:04
edleafe#link Traits series: https://review.openstack.org/#/c/376201/14:04
edleafealex_xu?14:04
alex_xumy colleague is working on the 'placement-manage' cl14:05
alex_xu#link https://review.openstack.org/#/c/450125/114:05
alex_xuit is still in WIP14:05
alex_xutwo problems found for that14:05
*** cknight has quit IRC14:06
*** cknight has joined #openstack-meeting-alt14:06
edleafealex_xu: any major blocks for your series?14:06
alex_xufirst, that cmd want to use Trait object to create standard trait in db14:06
alex_xu#link https://review.openstack.org/#/c/376199/28/nova/objects/resource_provider.py@149614:06
*** jianghuaw__ has joined #openstack-meeting-alt14:06
alex_xuedleafe: ^ I probably need to remove that check from the obj layer, and move into api layer14:07
*** bzhao has quit IRC14:07
edleafealex_xu: I'm confused: I thought all standard traits were going to be in the os-traits module?14:08
*** bzhao has joined #openstack-meeting-alt14:08
edleafealex_xu: but yeah, that seems more like an API-level check14:08
alex_xuedleafe: yes, but we need to import all the standard trait fro os-traits into placement db14:08
mriedemit is in the api already via json schema14:08
*** knangia has joined #openstack-meeting-alt14:08
alex_xumriedem: ah, yea, I probably just need to remove that check14:09
mriedemhttps://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/resource_class.py#L3314:09
edleafealex_xu: what was the second problem?14:10
alex_xusecond problem, do we want to consider remove standard trait which removed from os-traits in the placement-manange cmd now?14:10
edleafeheh14:10
*** diablo_rojo has joined #openstack-meeting-alt14:10
edleafeI think once something is in os-traits, it's there for good. Removing it from the DB for a local modification might be OK, though14:11
alex_xuif yes, we need to take care the case trait may already associated with specific resource provider14:11
edleafealex_xu: agreed. This would seem to be an ultra-low priority, though14:12
*** zhurong has joined #openstack-meeting-alt14:12
edleafeRemoving traits was never part of the main design14:12
alex_xuI thought we should return fault for any trait associated with resource provider. If the user still want to remove that, the user needs to specify '--force'14:12
edleafeWell, we should probably move the discussion to the review14:13
edleafeso more people can comment14:13
edleafeMoving on...14:13
edleafe#link os-traits reorg: https://review.openstack.org/#/c/448282/14:13
alex_xuedleafe: also agree remove is low priority, just think of if implement that as above ^, we didn't have interface in the object layer to query, the trait assicated with which resource provider14:13
*** gyee has joined #openstack-meeting-alt14:13
*** gyee has quit IRC14:13
alex_xufor the object layer to support such query, it is still a WIP patch https://review.openstack.org/#/c/429364/14:14
edleafejaypipes is breaking up os-traits from a single large file to a logical nesting of smaller files14:14
*** skramaja has quit IRC14:14
edleafeThere were issues with the design for importing those sub-packages14:14
*** cknight has quit IRC14:15
edleafecdent had a POC, and I made another (linked above)14:15
edleafe#link cdent POC: https://github.com/cdent/pony14:15
*** cknight has joined #openstack-meeting-alt14:15
alex_xuyea, just better than one single huge file14:16
edleafeNothing earth-shattering there; just trying to make computers do the boring repetitive stuff instead of humans14:16
*** dave-mccowan has joined #openstack-meeting-alt14:16
edleafebauzas has an early WIP spec for making claims from placement:14:17
edleafe#link WIP placement doing claims: https://review.openstack.org/43742414:17
edleafeComments there are always welcome.14:17
edleafe#link Show sched. hints in server details: https://review.openstack.org/44058014:18
edleafeThere is some discussion as to whether this should be done14:18
*** cknight has quit IRC14:18
edleafeor keep scheduler hints an internal thing only14:18
*** cknight has joined #openstack-meeting-alt14:18
edleafeNested Resource provider series pretty much on hold until traits is done14:18
edleafe#link Nested RPs: https://review.openstack.org/#/c/415920/14:18
edleafeAny other specs or reviews to discuss?14:19
*** diga has joined #openstack-meeting-alt14:19
digao/14:19
mriedemi have re-proposed the nested RPs spec,14:19
mriedemdo we anticipate changes to that?14:19
mriedemor should we just re-approve?14:20
mriedemhttps://review.openstack.org/#/c/449381/14:20
edleafemriedem: I'd have to re-review14:20
edleafeto make sure that the traits usage is current14:20
mriedemif we don't expect changes, but it's just lower priority,14:20
mriedemthen we should still re-approve before p-114:20
* bauzas waves super-late (thanks DST)14:20
edleafeok, I'll look over that after the meeting14:21
* macsz was late to add item for specs reviews14:21
edleafeI saw a late addition just now:14:21
edleafeUse local-scheduler spec14:21
edleafe#link Add use-local-scheduler spec https://review.openstack.org/#/c/438936/14:21
macszJohn started it, left me to finish it14:21
edleafejohnthetubaguy: any comments on that?14:21
edleafemacsz: ah!14:22
mriedemthat came up at the ptg,14:22
mriedemlike local conductor14:22
mriedemso run nova-scheduler local to conductor14:22
mriedemand don't require a separate nova-scheduler service14:22
mriedemi think is the gist14:22
macszyeah, basically it is about dropping scheduler process and move it's logic to the condiuctor14:22
macszmriedem: yeah14:22
*** EricGonczer_ has joined #openstack-meeting-alt14:23
edleafeok, added to my growing list of tabs...14:23
*** dsariel has joined #openstack-meeting-alt14:23
macszJohn had planned more in this spec14:23
macszbut we decided to split it up14:23
macszand created two additional specs as follow up, but it;s not scheduler related14:23
bauzasthe only issue I see with that is that we agreed to have a global scheduler for cellsv2 vs. local conductors for each cell14:23
macszso i think we can skip it today14:23
johnthetubaguythat sounds correct14:24
johnthetubaguyits all about making things simpler for operators14:24
mriedemplacement is the global scheduler now,14:24
mriedembut yeah we still have n-sch global too14:24
mriedemusing host mappings14:25
bauzasmriedem: not really given we still need to look at filters14:25
bauzasso, it could be merged with the super-conductor14:25
*** cknight has quit IRC14:25
bauzasnot the local conductors to make it clear14:25
johnthetubaguyright, placement is the key change here, there i no longer a benefit from the separate single nova-scheduler process (with active/passive HA, or whatever)14:25
*** ccamacho is now known as ccamacho|brb14:25
johnthetubaguyyes, its an api cell thing still14:25
bauzasjohnthetubaguy: that's another point14:26
bauzasbecause conductors are A/A14:26
bauzaswhile schedulers are A/P14:26
johnthetubaguybauzas: thats not always true14:26
johnthetubaguyits required only for the caching scheduler14:26
bauzaswell14:26
johnthetubaguynow the move to placement makes most of these reasons go away, as nova-scheduler is no longer "single threaded" in the way it once was (and that was a good thing)14:27
bauzasjohnthetubaguy: the problem is about the HostState14:27
* alex_xu thought nova-scheduler is A/A...14:28
bauzasI mean, HostState.consume_from_request()14:28
bauzasbut lemme provide my thoughts in the review14:28
johnthetubaguybauzas: yes, the idea is claims will eventually get rid of that14:29
edleafeGood idea - let's all review that spec and add our comments14:29
bauzaslastly, the point is about the scheduler fanout14:29
johnthetubaguyto be clear, the current goal is make running as part of conductor possible14:29
johnthetubaguydeprecating the old way is a follow on step14:29
mriedemalex_xu: i don't think it's recommended to run more than one scheduler worker14:29
bauzasmriedem: it's possible if you have a good capacity14:29
mriedemthe main reason is what? collisions?14:29
bauzasmriedem: but we don't recommend A/A for example with Ironic14:29
* johnthetubaguy points at stack vs spread14:30
bauzasyup14:30
mriedemwe should doc this,14:30
mriedembecause i'm reminded of it frequently,14:30
mriedembut forget what the reasons are14:30
bauzasit's already documented AFAIR14:30
* alex_xu needs to check the doc14:30
bauzasbut agreed with johnthetubaguy, possibly something we could fix by scheduler claims :)14:30
*** marst has quit IRC14:30
bauzasas I said, my last concern is the scheduler fanout that computes do14:30
bauzasfor providing instances and aggregates knowing14:31
bauzasto the scheduler14:31
johnthetubaguyI thought we killed that? I guess it came back14:31
bauzasbut again, let's put that in the spec14:31
bauzasjohnthetubaguy: we added it somewhere around Juno/Liberty14:31
johnthetubaguyso maybe we are a cycle early with the spec14:31
johnthetubaguybauzas: I thought it got killed soon after14:32
bauzasbut now we have placement, so we could be doing that using placement14:32
*** EricGonc_ has joined #openstack-meeting-alt14:32
*** hongbin_ has joined #openstack-meeting-alt14:32
bauzasjohnthetubaguy: well, not what I know14:32
*** cknight has joined #openstack-meeting-alt14:32
mriedemi have no idea what this means:14:32
mriedem(9:30:59 AM) bauzas: as I said, my last concern is the scheduler fanout that computes do14:32
mriedem(9:31:13 AM) bauzas: for providing instances and aggregates knowing14:32
mriedem(9:31:18 AM) bauzas: to the scheduler14:32
* alex_xu thought the multiple schedulers is ok, only have problem when resource starve14:33
bauzasmriedem: talking of https://github.com/openstack/nova/blob/master/nova/scheduler/client/query.py#L4114:33
johnthetubaguyyeah, I guess we added more stuff into that14:33
johnthetubaguyalex_xu: if you stack, you are always resource starved14:33
*** cknight has quit IRC14:33
*** EricGonczer_ has quit IRC14:33
bauzasrelated to https://github.com/openstack/nova/blob/master/nova/scheduler/rpcapi.py#L13414:34
johnthetubaguymacsz: sounds like we are a cycle too soon for that spec14:34
*** hongbin has quit IRC14:34
johnthetubaguybut good to aim that way sooner rather than later14:34
mriedemi added some godaddy ops guys,14:34
bauzasjohnthetubaguy: tbc, I'm agreing with you14:34
alex_xujohnthetubaguy: ah, i got the point, but the nova-scheduler is stack?14:35
bauzasjohnthetubaguy: for the direction14:35
mriedembecause the size of the conductor service has come up over time in the ops ml14:35
mriedemalex_xu: depends on config14:35
johnthetubaguyalex_xu: you can go both ways, there is a config to choose14:35
bauzasjohnthetubaguy: we don't honestly need a separate RPC service for running filters14:35
macszjohnthetubaguy: well, better start sooner than later :)14:35
bauzasjohnthetubaguy: I'm just trying to put my thoughts for explaining the tech debtt14:35
bauzasie. how to go from here to there :)14:35
mriedemalex_xu: this is why i was saying i hope these conditions are all clearly documented somewhere, which i don't think they are14:35
bauzasbut I'm definitely +1 on the idea to merge the scheduler14:35
johnthetubaguymriedem: its fair we have a general process size issue14:36
johnthetubaguymriedem: +1 for better dev focused docs on this14:36
alex_xuyea, I always thought I clear about all of that, for now, I think no :(14:36
*** dr_dolphm is now known as dolphm14:37
mriedembauzas: if you can find any existing docs on guidelines about when you can or shouldn't run multiple schedulers, that'd be helpful,14:37
mriedemif you can't find that, we should doc it14:37
mriedemsuperdan pointed out something to me last week wrt multiple schedulers and using ironic, and why you can't,14:37
bauzasmriedem: https://docs.openstack.org/developer/nova/scheduler_evolution.html#parallelism-and-concurrency14:37
mriedemsomething with the hacks we were talking about last week14:37
*** superdan is now known as dansmith14:38
bauzasmriedem: which points to http://specs.openstack.org/openstack/nova-specs/specs/backlog/approved/parallel-scheduler.html14:38
bauzasalex_xu: ^ worth reading14:38
mriedembut if i'm not using NUMA or i'm using spread vs pack, then...14:38
alex_xubauzas: thanks14:38
mriedemor i'm using ironic,14:38
mriedemwe could expand that doc a bit14:38
bauzasmriedem: of course, we can document that further14:39
bauzasideally in the ops guide14:39
bauzasrunning multiple schedulers can be acceptable *if you know the limitations*14:39
mriedemyeah, i don't know the limitations :)14:39
mriedemhence why i'm asking for docs14:39
mriedembut anyway14:40
bauzasa large cloud with good capacity is reasonable to run multiple schedulers14:40
mriedemi'll take a todo to sort through the docs14:40
bauzasa small cloud using NUMA or Ironic isn't :)14:40
mriedemi also wonder how valid http://specs.openstack.org/openstack/nova-specs/specs/backlog/approved/parallel-scheduler.html is anymore14:40
*** jianghuaw has joined #openstack-meeting-alt14:40
bauzasmriedem: it was written pre-placement14:40
mriedemthat's what i mean,14:40
bauzasand I guess jaypipes never revisited it14:40
mriedemlots of this is probably old14:40
bauzaswell, there are still some idea that are valuable14:41
*** zhurong has quit IRC14:41
bauzasif we consider placement as not being feature-parity with scheduler/conductor, which is what I think14:41
bauzasplacement is good for getting a list of hosts14:41
bauzasbut then we could still having filters/weighters14:41
*** jianghuaw__ has quit IRC14:42
bauzasusing the conductor if we merge mid-term johnthetubaguy's spec, which I agree14:42
bauzasanyway14:42
mriedemi've got a todo written down,14:42
mriedemi'll bug people later14:42
bauzasjust saying those are the docs describing the current problems with the scheduler14:42
johnthetubaguysounds like time to refresh something14:43
bauzasI still need to log my comments on johnthetubaguy's spec :)14:43
*** treiz has quit IRC14:43
johnthetubaguycould help us with the claims discussions14:43
johnthetubaguyits macsz's spec now14:43
*** lpetrut has quit IRC14:43
johnthetubaguylike I say, sounds like something for next cycle, or something we need more work to make it possible14:43
bauzasyeah, hence me pushing for scheduler claims, not placement claims14:43
johnthetubaguyor both14:43
bauzasscheduler using placement for that tho14:44
johnthetubaguybauzas: I have lost track of the claims debates myself14:44
*** marst has joined #openstack-meeting-alt14:44
bauzasjohnthetubaguy: the main debate was about why we should merge that *before* placement cut14:44
edleafejohnthetubaguy: it's here: https://review.openstack.org/43742414:44
*** szaher has quit IRC14:45
bauzasI was long-opposed to the idea of scheduler claims, but now I see placement, I think it could be nice using placement for having scheduler claims14:45
*** jpena is now known as jpena|brb14:45
*** dsariel has quit IRC14:45
bauzasso I turned my opinion14:46
bauzasanyway14:46
bauzas15 mins to the ned14:46
edleafeLet's move on14:46
bauzasand I'm diverting14:46
edleafe#topic Bugs14:46
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:46
*** szaher has joined #openstack-meeting-alt14:46
edleafeDidn't see any new ones.14:46
edleafeAnything to discuss about bugs?14:46
macszdid not see anything worth as well, but i just started my day :)14:47
edleafeok then14:47
edleafe#topic Open discussion14:47
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:47
edleafeWhat's on your mind?14:47
*** dsariel has joined #openstack-meeting-alt14:48
* edleafe only hears crickets14:48
edleafeGuess that's a wrap. Back to work/sleep/fun!14:49
*** cloudrancher has quit IRC14:49
edleafe#endmeeting14:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:49
openstackMeeting ended Mon Mar 27 14:49:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-03-27-14.00.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-03-27-14.00.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-03-27-14.00.log.html14:49
*** fnaval has joined #openstack-meeting-alt14:55
*** dsariel has quit IRC14:55
*** dsariel has joined #openstack-meeting-alt14:55
*** yamahata has joined #openstack-meeting-alt14:56
*** iyamahat has joined #openstack-meeting-alt14:56
*** manjeets_ has joined #openstack-meeting-alt14:59
*** electrocucaracha has joined #openstack-meeting-alt15:00
ihrachys#startmeeting neutron_upgrades15:01
openstackMeeting started Mon Mar 27 15:01:27 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
ihrachyso/15:01
manjeets_o/15:01
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:01
openstackThe meeting name has been set to 'neutron_upgrades'15:01
electrocucarachao/15:01
sshanko/15:02
ihrachys#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam Agenda15:02
ihrachys#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:02
ihrachysnothing specific to upgrades, just a note that Pike-1 is in 2-3 weeks. it doesn't change much in what we do and track, so moving on.15:03
ihrachys#topic Linuxbridge multinode grenade job15:03
*** openstack changes topic to "Linuxbridge multinode grenade job (Meeting topic: neutron_upgrades)"15:03
ihrachysmanjeets_: your stage15:03
manjeets_ihrachys, tried couple of things there15:03
manjeets_forcing concurrency = 215:03
manjeets_seems like that is not the issue15:03
*** mriedem has left #openstack-meeting-alt15:03
*** treiz has joined #openstack-meeting-alt15:04
manjeets_I've increased the test timeout but unfortunately did not get job placed on rax node yet15:04
*** marst has quit IRC15:04
manjeets_i've checked timestamps it is taking so much time to bring up fip and test timesout15:04
ihrachysok, let's say you indeed see that it shows up on rax only. what next? you can't just stop landing the job there, right?15:05
*** ijw has joined #openstack-meeting-alt15:05
manjeets_it fails only on rax-node cloud, I've made one other patch dependent on patch where I exported increased time out15:05
*** jpena|brb is now known as jpena15:05
ihrachysmanjeets_: how do you know that it indeed takes long to set up fip? do you see router updates slowly handled?15:05
manjeets_ihrachys, I checked timestamps from tests15:05
ihrachysI mean in agent logs15:05
*** ijw_ has joined #openstack-meeting-alt15:06
manjeets_and compared when it succeed vs fail15:06
ihrachyswell tempest output won't show you if FIP is configured by the agent or now15:06
ihrachys*or not15:06
ihrachysto know that, you may need to find exact place in the agent log where the router update event corresponding to FIP creation/attachment is handled in agent side15:06
*** tonytan_brb has joined #openstack-meeting-alt15:06
*** tonytan4ever has quit IRC15:07
*** rcernin has quit IRC15:07
manjeets_ohk I'll check l3 agents logs today15:07
*** nkrinner is now known as nkrinner_afk15:08
ihrachyscool, let me know if you struggle finding where the router update event handler is on the agent side15:08
*** annegentle has joined #openstack-meeting-alt15:08
manjeets_ok15:09
*** ijw has quit IRC15:09
ihrachys#topic Mixed server versions15:10
*** openstack changes topic to "Mixed server versions (Meeting topic: neutron_upgrades)"15:10
*** kobis has quit IRC15:10
ihrachysI had an action item to follow up here, writing the spec. it's still not in gerrit. :-x15:10
* ihrachys was consumed by other internal matters for most of the week15:10
ihrachysalso dolphm in the RFE expressed some questions about how critical the proposal is: https://bugs.launchpad.net/neutron/+bug/167285215:11
openstackLaunchpad bug 1672852 in neutron "[RFE] Make controllers with different list of supported API extensions to behave identically" [Wishlist,New] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)15:11
electrocucarachabut at least it's only matters of provide documentation for deployers right?15:11
ihrachyssuggesting affinity aware LBs used in all production envs15:12
*** jianghuaw__ has joined #openstack-meeting-alt15:12
ihrachyselectrocucaracha: no I am talking about the RFE ^15:12
ihrachyssomething internal to neutron-server that makes all cluster nodes to report identical /extensions/15:12
ihrachysdolphm: also has concerns about the complexity of this thing. I guess we will need to resolve those in gerrit when the spec is up.15:13
manjeets_afaik spec or rfe for maintaining minimum subset of extensions b/w mixed versions15:13
manjeets_right ?15:13
ihrachysyes15:14
*** jianghuaw has quit IRC15:15
ihrachysthere is also somewhat related online data migration CLI command: https://review.openstack.org/#/c/432494/15:16
ihrachyselectrocucaracha: I reviewed it like 15 mins before the meeting :)15:16
dolphmihrachys: just caught up on your comments in that bug; i just wanted to voice alternative approaches and see the pro's and con's weighed out, not push you toward one solution. it sounds like your approach is pretty welll thought out as-is15:16
ihrachyselectrocucaracha: there is definitely some code polishing to do in the implementation, also the mechanism of registering new migrations is not ideal, we will need to open it for external plugins.15:17
ihrachysdolphm: I will try to capture your comment in the spec and will reach out to you for feedback.15:17
dolphmihrachys: i'm not sure i've seen the spec; link?15:18
dolphm(it's not linked in the bug)15:18
ihrachysdolphm: there is none just yet15:18
dolphmihrachys: gotcha15:18
ihrachysit's in progress15:18
dolphmihrachys: yeah, ping me when it's up for review15:18
electrocucarachaihrachys: ok, I'm going to check your comments and thanks dolphm for the feedback on that patch15:18
ihrachyselectrocucaracha: what I basically wanted for the plugins is so that we don't need to modify the tool when an external plugin wants to define their own migration15:18
ihrachysack, thanks for working on it15:19
ihrachys#topic Object implementation15:19
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:19
ihrachyshttps://review.openstack.org/#/q/topic:bp/adopt-oslo-versioned-objects-for-db15:19
ihrachysquotas landed: https://review.openstack.org/33862515:19
*** jianghuaw has joined #openstack-meeting-alt15:19
ihrachysalso gate fix for unit tests landed: https://review.openstack.org/#/c/447600/15:20
*** jaugustine has joined #openstack-meeting-alt15:20
ihrachysthere is also LIKE patch that we wanted to get back but I failed: https://review.openstack.org/#/c/419152/15:21
ihrachysI see electrocucaracha left some comments, nice15:21
*** jianghuaw__ has quit IRC15:22
electrocucarachaihrachys: I haven't had time to review or create an UT for unique keys test data generation15:23
*** beslemon has joined #openstack-meeting-alt15:24
electrocucarachaand in terms of metrics we have 82% of the model classes have their corresponding OVO class merged in master15:25
electrocucarachaand 53% are using OVO to do CRUD operations15:25
* electrocucaracha long journey15:25
ihrachyswell not that bad, I thought it's lower ;)15:26
*** mdong has joined #openstack-meeting-alt15:26
ihrachysgotta get more serious about NetworkSegment, SG and such15:26
* manjeets_ thought it must be around 65 for usage15:26
electrocucarachaihrachys: well, actually Allocation and Endponits will give us more15:27
electrocucarachahttps://review.openstack.org/#/c/367810/15:27
ihrachysit's WIP15:29
ihrachysdasanind: are you working on it?15:29
dasanindihrachys: Yeah I am working on it15:29
dasanindihrachys: I put a WIP for the lock mode. Will respin it this week and complete it15:30
ihrachysI see it's still using locsk15:30
ihrachysyea15:30
ihrachysok, send it my way when ready15:30
dasanindihrachys: ack15:30
ihrachys#topic Other patches on review15:31
*** openstack changes topic to "Other patches on review (Meeting topic: neutron_upgrades)"15:31
ihrachyshttps://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron15:31
ihrachysthe haproxy switch gone in, so no longer in the query15:32
ihrachysthere is nothing else to discuss here really, let's move on15:32
ihrachys#topic Review priorities for the week15:32
*** openstack changes topic to "Review priorities for the week (Meeting topic: neutron_upgrades)"15:32
ihrachyselectrocucaracha: I figured it helps to have that discussion weekly15:32
manjeets_review priorities discussion ?15:33
electrocucarachaihrachys: definitely,15:33
ihrachysofc, the spec for /extensions handling for mixed server versions and the CLI are in the focus: https://review.openstack.org/#/c/432494/15:33
ihrachysmanjeets_: yes15:33
manjeets_++15:33
electrocucarachaihrachys: I was checking the spreadsheet https://docs.google.com/spreadsheets/d/1FeeQlQITsZSj_wpOXiLbS36dirb_arX0XEWBdFVPMB8/edit#gid=143417011215:33
ihrachysbeyond, that, realistically, we should be able to land the LIKE support: https://review.openstack.org/419152 and maybe endpoints if dasanind is quick to respin: https://review.openstack.org/36781015:34
ihrachysall of those are still work in progress15:34
ihrachysanything ready to land NOW?15:34
sshankRouter Extra Attrs integration seems like its ready.15:35
sshankIs it in priority?15:35
electrocucarachaI remember that Meterings was fine, but I need to address the dasm comments15:35
ihrachyssshank: it's not priority but if it's ready it can get focused attention15:36
ihrachysthe link to extra_attrs patch: https://review.openstack.org/#/c/381209/15:36
ihrachyselectrocucaracha: https://review.openstack.org/#/c/350387/? it's abandoned15:36
dasmihrachys: i think electrocucaracha mentioned about this one: https://review.openstack.org/#/c/433125/15:37
ihrachysoh ok15:37
electrocucarachaihrachys: for no reason he abandoned but I reopened a new one ^^15:37
*** jianghuaw__ has joined #openstack-meeting-alt15:37
ihrachyswhat's the relation to the former?15:37
ihrachysok we will need to maintain the authorship15:37
ihrachysCo-Authored-By15:37
electrocucarachaihrachys: well, he decided to abandoned because he was not doing anything15:38
electrocucarachaihrachys: I took that patch since the beginning15:38
electrocucarachabut I can add his name15:38
ihrachyselectrocucaracha: sure. all I am saying is, if you reused the code, make sure the author is mentioned in the commit message15:38
electrocucarachaihrachys: ok, no problem15:39
*** dsariel has quit IRC15:39
*** jianghuaw has quit IRC15:39
ihrachysok I think realistically it's already more than enough to review for the week15:40
ihrachys#topic Open discussion15:40
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:40
*** andreas_s has quit IRC15:41
ihrachysanything specific to discuss that was not covered in any other section?15:41
sshankihrachys, I think the error similar to session expunge in port binding level is seen in router l3 binding integration as well.15:41
electrocucarachatalking about dates, when starts the next release?15:41
*** beslemon has quit IRC15:41
ihrachyselectrocucaracha: you mean Queens? it's like +6 months since PTG15:42
ihrachyswhich was a month ago15:42
ihrachyssshank: ack15:43
*** sridharg has quit IRC15:43
electrocucarachaihrachys: ok, in that case we still have time for landing more patches, as long as we keep the same cadence15:44
manjeets_electrocucaracha, ++15:45
*** mickeys has joined #openstack-meeting-alt15:45
ihrachys+15:45
ihrachysok let's use the 15 mins for something useful like drinking coffee ;)15:45
ihrachysthanks everyone15:45
electrocucarachathanks ihrachys15:45
ihrachys#endmeeting15:46
manjeets_thanks15:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:46
sshankThanks ihrachys15:46
openstackMeeting ended Mon Mar 27 15:46:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-03-27-15.01.html15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-03-27-15.01.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-03-27-15.01.log.html15:46
*** electrocucaracha has left #openstack-meeting-alt15:46
dasanindthanks15:46
*** jianghuaw has joined #openstack-meeting-alt15:47
*** jianghuaw__ has quit IRC15:49
*** benj_ has quit IRC15:51
*** dsariel has joined #openstack-meeting-alt15:54
*** lpetrut has joined #openstack-meeting-alt15:55
*** amotoki has quit IRC15:57
*** tommylikehu_ has quit IRC15:58
*** dsariel has quit IRC15:58
*** alexchadin has quit IRC15:58
*** dizquierdo has quit IRC15:58
*** tonytan_brb has quit IRC16:03
*** tonytan4ever has joined #openstack-meeting-alt16:03
*** beslemon has joined #openstack-meeting-alt16:04
*** haleyb has quit IRC16:05
*** aarefiev is now known as aarefiev_afk16:05
*** nadya has joined #openstack-meeting-alt16:06
*** MapspaM is now known as SpamapS16:08
*** dsariel has joined #openstack-meeting-alt16:11
*** diga has quit IRC16:11
*** cinerama has joined #openstack-meeting-alt16:12
*** beslemon_ has joined #openstack-meeting-alt16:13
*** beslemon has quit IRC16:15
*** dsariel has quit IRC16:16
*** haleyb has joined #openstack-meeting-alt16:20
*** matrohon has quit IRC16:23
*** trinaths1 has joined #openstack-meeting-alt16:27
*** nadya has quit IRC16:30
*** dsariel has joined #openstack-meeting-alt16:31
*** Swami has joined #openstack-meeting-alt16:35
*** annegentle has quit IRC16:35
*** rcernin has joined #openstack-meeting-alt16:37
*** adrian_otto has joined #openstack-meeting-alt16:38
*** dsariel has quit IRC16:38
*** rossella_s has quit IRC16:42
*** rossella_s has joined #openstack-meeting-alt16:43
*** bfernando has quit IRC16:43
*** felipemonteiro_ has joined #openstack-meeting-alt16:46
*** rwsu has joined #openstack-meeting-alt16:48
*** derekh has quit IRC16:49
*** cleong has joined #openstack-meeting-alt16:53
*** gyee has joined #openstack-meeting-alt16:54
*** amotoki has joined #openstack-meeting-alt16:58
*** tesseract has quit IRC16:59
*** dsariel has joined #openstack-meeting-alt17:00
*** annegentle has joined #openstack-meeting-alt17:00
*** armax has joined #openstack-meeting-alt17:02
*** amotoki has quit IRC17:03
*** skramaja has joined #openstack-meeting-alt17:07
*** rcernin has quit IRC17:08
*** kzaitsev_ws has quit IRC17:11
*** jpena is now known as jpena|off17:16
*** harlowja has quit IRC17:18
*** markvoelker has quit IRC17:23
*** harlowja has joined #openstack-meeting-alt17:24
*** trinaths1 has left #openstack-meeting-alt17:27
*** arxcruz has quit IRC17:31
*** gouthamr_ is now known as gouthamr17:32
*** lpetrut has quit IRC17:33
*** cknight has joined #openstack-meeting-alt17:34
*** rossella_s has quit IRC17:34
*** armax_ has joined #openstack-meeting-alt17:39
*** armax has quit IRC17:39
*** armax_ is now known as armax17:39
*** sshnaidm is now known as sshnaidm|afk17:40
*** mtanino has quit IRC17:44
*** tonanhngo has joined #openstack-meeting-alt17:44
*** ozamiatin has joined #openstack-meeting-alt17:44
*** ccamacho|brb is now known as ccamacho17:46
*** XinBai has joined #openstack-meeting-alt17:46
*** dave-mccowan has quit IRC17:46
*** tonanhngo_ has joined #openstack-meeting-alt17:47
*** tonanhngo has quit IRC17:48
*** dsariel has quit IRC17:48
*** baoli has quit IRC17:49
*** tonanhngo has joined #openstack-meeting-alt17:50
*** tonanhngo_ has quit IRC17:51
*** panda is now known as panda|bbl17:51
*** adrian_otto has quit IRC17:57
*** s3wong has joined #openstack-meeting-alt17:57
*** amotoki has joined #openstack-meeting-alt17:59
*** baoli has joined #openstack-meeting-alt17:59
*** MeganR has joined #openstack-meeting-alt18:01
*** dave-mccowan has joined #openstack-meeting-alt18:01
*** HeOS has quit IRC18:01
*** amotoki has quit IRC18:03
*** sshnaidm|afk is now known as sshnaidm18:04
*** anilvenkata has joined #openstack-meeting-alt18:05
*** ralonsoh has quit IRC18:11
*** mtanino has joined #openstack-meeting-alt18:12
*** marst has joined #openstack-meeting-alt18:12
*** beslemon_ has quit IRC18:12
*** armax has quit IRC18:13
*** bogdando has quit IRC18:13
*** gongysh has quit IRC18:15
*** arxcruz has joined #openstack-meeting-alt18:16
*** ozamiatin has quit IRC18:17
*** pvaneck has joined #openstack-meeting-alt18:21
*** armax has joined #openstack-meeting-alt18:22
*** baoli_ has joined #openstack-meeting-alt18:24
*** baoli has quit IRC18:25
*** jprovazn has quit IRC18:26
*** fzdarsky has joined #openstack-meeting-alt18:29
*** d0ugal has quit IRC18:31
*** stanchan has joined #openstack-meeting-alt18:32
*** iyamahat has quit IRC18:35
*** yamahata has quit IRC18:36
*** alexchadin has joined #openstack-meeting-alt18:38
*** arxcruz has quit IRC18:39
*** armax has quit IRC18:41
*** AlanClark has joined #openstack-meeting-alt18:45
*** bswartz has quit IRC18:47
*** d0ugal has joined #openstack-meeting-alt18:47
*** bswartz has joined #openstack-meeting-alt18:48
*** sridharg has joined #openstack-meeting-alt18:54
*** fzdarsky has quit IRC18:55
*** dizquierdo has joined #openstack-meeting-alt18:55
*** stanchan has quit IRC18:59
*** amotoki has joined #openstack-meeting-alt19:00
*** iyamahat has joined #openstack-meeting-alt19:00
*** stanchan has joined #openstack-meeting-alt19:00
*** beekneemech is now known as bnemec19:00
*** yamahata has joined #openstack-meeting-alt19:01
*** amotoki has quit IRC19:05
*** jkilpatr has quit IRC19:11
*** adrian_otto has joined #openstack-meeting-alt19:12
*** sambetts is now known as sambetts|afk19:13
*** panda|bbl is now known as panda19:14
*** erlon has quit IRC19:15
*** florianf has quit IRC19:15
*** florianf has joined #openstack-meeting-alt19:18
*** kobis has joined #openstack-meeting-alt19:20
*** jkilpatr has joined #openstack-meeting-alt19:22
*** anilvenkata has quit IRC19:22
*** skramaja has quit IRC19:24
*** arxcruz has joined #openstack-meeting-alt19:25
*** kzaitsev_mb has joined #openstack-meeting-alt19:26
*** radeks has quit IRC19:29
*** mjura has quit IRC19:31
*** baoli_ has quit IRC19:32
*** beslemon has joined #openstack-meeting-alt19:32
*** kzaitsev_mb has quit IRC19:35
*** baoli has joined #openstack-meeting-alt19:39
*** aimeeu__ has joined #openstack-meeting-alt19:41
*** aimeeu has quit IRC19:41
*** aimeeu__ is now known as aimeeu19:41
*** annegentle has quit IRC19:44
*** annegentle has joined #openstack-meeting-alt19:46
*** kfarr has joined #openstack-meeting-alt19:47
*** jackie-truong has joined #openstack-meeting-alt19:47
*** iberezovskiy has quit IRC19:48
*** kobis has quit IRC19:48
*** raddaoui_____ has quit IRC19:49
*** raddaoui_____ has joined #openstack-meeting-alt19:49
*** rfolco has quit IRC19:50
*** tonytan4ever has quit IRC19:51
*** florianf has quit IRC19:51
*** tonytan4ever has joined #openstack-meeting-alt19:53
*** rfolco has joined #openstack-meeting-alt19:54
*** iberezovskiy has joined #openstack-meeting-alt19:54
*** namnh has joined #openstack-meeting-alt19:57
*** florianf has joined #openstack-meeting-alt19:58
*** ozamiatin has joined #openstack-meeting-alt19:58
*** TxGirlGeek has joined #openstack-meeting-alt19:58
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon Mar 27 20:00:24 2017 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
dave-mccowan#topic roll call20:00
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:00
hockeynuto/20:00
dave-mccowanhi hockeynut!20:00
namnhhi everyone20:01
hockeynutgreetings and salutations!20:01
dave-mccowanhi namnh20:01
jackie-truongHi everyone20:01
*** diazjf has joined #openstack-meeting-alt20:01
kfarro/20:01
diazjfo/20:01
* hockeynut has to disappear in 30 mins for another meeting - sadness20:01
dave-mccowanhockeynut i saw you at the ptg, but when i went looking for you again to say hi, you'd already left town.20:01
*** dsariel has joined #openstack-meeting-alt20:01
*** baoli has quit IRC20:02
*** HeOS has joined #openstack-meeting-alt20:02
hockeynutwe were only allowed to go for Mon and Tues :-(  Budgets suck...20:02
*** baoli has joined #openstack-meeting-alt20:02
*** annegentle has quit IRC20:02
dave-mccowanthanks for coming everyone!  our agenda is in the usual place: https://wiki.openstack.org/wiki/Meetings/Barbican20:03
*** alexchadin has quit IRC20:03
dave-mccowan#topic backlog review20:03
*** openstack changes topic to "backlog review (Meeting topic: barbican)"20:03
dave-mccowanwe're making great progress on both bugs and reviews.  the queues are shrinking every week. :-)20:04
dave-mccowani don't have much else to say on that, except Thanks!20:04
dave-mccowan#topic Pike Status20:04
*** openstack changes topic to "Pike Status (Meeting topic: barbican)"20:04
namnh:-)20:04
dave-mccowanWe have two weeks left until Milestone 1.  We've already got a bunch stuff in and more in progress.20:05
dave-mccowanhttps://etherpad.openstack.org/p/barbican-tracker-pike20:05
dave-mccowanhttps://launchpad.net/barbican/+milestone/pike-120:05
dave-mccowanthe second link shows what we've schedule for Pike 1.20:05
dave-mccowanthe first link is our plan for Pike overall.20:06
*** XinBai has quit IRC20:06
dave-mccowandoes anyone have an update on their work items?20:06
kfarrThe KMIP gate check merged (yay!)20:07
kfarrIs there a way you want to cross things off the pike tracker etherpad?20:07
dave-mccowankfarr \o/20:07
kfarrOr otherwise note that they've been completed?20:08
dave-mccowani added a new gate job for functional tests on python 3.  it's part of a "community goal" for Pike.   i fixed one bug, and have the functional tests running locally.  the gate job still isn't working yet... i'm working on the yaml foo to fix it.20:08
*** markvoelker has joined #openstack-meeting-alt20:09
dave-mccowankfarr yes, let's update this etherpad with status as we go.20:09
kfarr+1 +120:10
dave-mccowani think we've already done more this cycle than last, :-)  but let's keep at it... the summit is taking a big bite out of the middle of the schedule this time.20:10
dave-mccowannamnh how are upgrades looking?20:11
namnhdave-mccowan: I think I have a good process for the feature :)20:12
dave-mccowannamnh thanks for working on this.  we'll get another point on the maturity index when you're done. :-)20:12
namnhdave-mccowan, kfarr: by the way, could you please review and leave your comment on two patch set: https://review.openstack.org/#/c/449022/ https://review.openstack.org/#/c/447689/20:13
dave-mccowanany thing else pike related?20:13
kfarrOh, yes, namh, I had a question about the grenade gate20:13
kfarrDid you want the Barbican functional tests to run, or the Barbican tempest plugin? Or both?20:14
namnhkfarr: I mean do you need run barbican tempest during offline upgrade using grenade?20:14
namnhs/you/we/20:15
kfarrI am not sure20:16
dave-mccowandoes anyone know what other project typically do with grenade to verify it "worked"?20:16
namnhkfarr: as your comment on this patch: https://review.openstack.org/#/c/446870/20:16
kfarrMy understanding is that for the core services, the grenade tests will launch a stable devstack, migrate to the latest dev version, then run the tempest tests20:17
hockeynutdave-mccowan its normally tempest tests run before and after the upgrade20:17
*** baoli has quit IRC20:17
hockeynutnote that grenade isn't going to be useful for rolling or zero downtime upgrades - the OSIC team is working on a replacement tool20:18
kfarrSo we can run the barbican tempest plugin tests, but also I thought the barbican functional tests would be more thorough20:19
dave-mccowankfarr i agree, functional tests would give better coverage.20:20
hockeynutno reason you can't put up a CR for grenade to add the barbican functional tests - I am sure others do something similiar20:20
*** MeganR has quit IRC20:20
dave-mccowanif we do a cross project tempest run, would we also need to upgrade the other projects?20:20
kfarrWe probably do?20:21
*** markvoelker has quit IRC20:22
*** raj_singh has quit IRC20:23
*** AlanClark has quit IRC20:23
dave-mccowanlet's take this question back to the barbican channel.  i think we need to dig more into what the normal workflow is for upgrade testing.20:23
*** baoli has joined #openstack-meeting-alt20:23
*** raj_singh has joined #openstack-meeting-alt20:23
dave-mccowanmoving on...20:23
dave-mccowan#topic summit20:23
*** openstack changes topic to "summit (Meeting topic: barbican)"20:23
dave-mccowanthe summit has two parts:  The main summit and a new thing, The Forum, that's kind of a skinny design summit.20:24
*** matrohon has joined #openstack-meeting-alt20:24
dave-mccowanFor the Forum, Barbican has one session confirmed: an onboarding room to meet/greet and help new contributors get started.20:24
hockeynutgee, what if they scrap the PTG idea and just combine it with the Forum/Summit?  Then everyone is in the same place at the same time?  :-)20:24
dave-mccowanI have submitted a request for an additional Fishbowl session.  I requested it genericly:  "Key Management Contributor/Operator/Community Discussion", or something like that.20:25
dave-mccowanI think there are another couple days to submit other suggestions, if you have any.20:26
dave-mccowanthe link in the email list.  if you want it and can't find it, let me know.20:26
dave-mccowandoes anyone want to discuss our other Summit presentation?  i think between us, barbicaneers have 4 sessions to prepare for summit.20:27
dave-mccowan#topic Any Other Business20:29
*** openstack changes topic to "Any Other Business (Meeting topic: barbican)"20:29
*** gouthamr has quit IRC20:29
*** cleong has quit IRC20:30
dave-mccowanOK.  We'll wrap up for this week.  Thanks everyone!20:31
dave-mccowan#endmeeting20:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:31
openstackMeeting ended Mon Mar 27 20:31:51 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-03-27-20.00.html20:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-03-27-20.00.txt20:31
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-03-27-20.00.log.html20:31
namnhthank dave-mccowan20:32
*** TxGirlGeek has quit IRC20:34
*** jackie-truong has quit IRC20:36
*** ihrachys has quit IRC20:39
*** annegentle has joined #openstack-meeting-alt20:39
*** baoli has quit IRC20:43
*** sridharg has quit IRC20:45
*** rockyg has joined #openstack-meeting-alt20:47
*** jcoufal has quit IRC20:48
*** ansmith has quit IRC20:49
*** baoli has joined #openstack-meeting-alt20:51
*** shamail has joined #openstack-meeting-alt20:52
*** cknight has quit IRC20:52
*** dprince has quit IRC20:58
shamail#startmeeting product_working_group21:00
openstackMeeting started Mon Mar 27 21:00:14 2017 UTC and is due to finish in 60 minutes.  The chair is shamail. 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
shamailHi, anyone here for the PWG meeting?21:00
*** GeraldK has joined #openstack-meeting-alt21:00
shamailHi GeraldK21:00
*** MeganR has joined #openstack-meeting-alt21:01
GeraldKhi21:01
*** gouthamr has joined #openstack-meeting-alt21:01
*** AndyU has joined #openstack-meeting-alt21:01
shamailSeems like we have 4-5 people here so far.. let’s give it another minute or two.21:01
MeganRHi21:02
AndyUokeydokey21:02
AndyUHi Megan  :)21:02
MeganRHi AndyU!21:02
*** baoli has quit IRC21:02
*** Sukhdev has joined #openstack-meeting-alt21:03
*** dimtruck is now known as zz_dimtruck21:03
shamailAlrighty21:03
shamailWho’s here for the PWG meeting?21:03
shamail#topic roll call21:03
*** openstack changes topic to "roll call (Meeting topic: product_working_group)"21:03
GeraldKo/21:03
AndyUhi all21:03
MeganRo/21:03
shamailAgenda for today:21:04
shamail#link https://wiki.openstack.org/wiki/Meetings/product-team21:04
shamail#topic Recap from Ops midcycle21:04
*** openstack changes topic to "Recap from Ops midcycle (Meeting topic: product_working_group)"21:04
shamailA bunch of us were in Milan the week before last for the Product WG midcycle and Ops meetup21:04
shamailThe meetup was well-attended and an overall great event21:04
shamail#link https://etherpad.openstack.org/p/MIL-ops-meetup21:05
shamailIn this etherpad, there are links to etherpads from all the sessions in case you want to catch up21:05
shamailWe also discussed using ‘hash tags’ to identify items that require follow-up and Leong created a small program to parse through etherpads and extract them21:06
shamail#link https://drive.google.com/drive/folders/0B733UR8kbomaSVhqQ3Y4NkFxTmc21:06
jamemcco/ Jamey here as well21:06
shamailHi jamemcc21:06
*** diazjf has quit IRC21:06
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:06
Arkady_Kanevskyhello21:06
shamailIn the linked folder, we have each hash-tag in a separate file along with line number information from the etherpad in which it was referenced21:07
shamailThis is still a work in progress but it is a good starting point towards being able to aggregate feedback from etherpads at events like the Ops meetup and Forum21:07
shamailDoes anyone who was at the ops meetup want to give their perspective on the event or areas/sessions they found enlightening?21:08
shamailI personally thought the container sessions (both running containers on OpenStack or running OpenStack on containers) were interesting.. it seemed like there was a lot of discussion happening on the topics but few adopters so far21:09
GeraldKfrom the files it looks like few projects made nice use of the hashtags21:09
shamailThe trend for adoption seemed to be there though21:09
shamailAgreed GeraldK21:09
shamailMoving on to the PWG midcycle topic...21:09
shamail#topic Action item from PWG meetup21:10
*** openstack changes topic to "Action item from PWG meetup (Meeting topic: product_working_group)"21:10
shamail#link https://etherpad.openstack.org/p/MIL-pwg-meetup21:10
shamail#link https://drive.google.com/drive/folders/0B733UR8kbomabGpidlBBUDdNQ1E21:10
shamailSo we used the same hashtag method for our midcycle as well and the linked google drive folder contains hashtags used in our etherpad21:10
shamailThe PWG mid-cycle was VERY productive and we had several discussions on topics that will shape our future21:11
*** florianf has quit IRC21:11
*** ccamacho has quit IRC21:12
shamailThe key discussions were on evolving the roadmap process (to make it a bit more bi-directional in the future), renaming user stories, revisiting the workflow and how to foster idea submission, and how to increase participation/awareness of this WG21:12
shamailAs you can see from the Google drive folder, most action items have owners listed so I am going to be skipping those… but I did want to bring attention to other action items that currently do not have owners.21:13
Arkady_KanevskyI was impressed by HPC participation on multiple sessions.21:13
rockygo/  Sorry I'm late.  Involved in a deep convo21:13
shamailhi rockyg21:13
*** namnh has quit IRC21:13
shamail+1 Arkady_Kanevsky21:13
shamailAction item: Use adoption data as weight to apply on themes 100K view21:14
shamailSo this one doesn’t have an owner but will most likely be incorporated into the bundle of ‘things to do’ for the next roadmap.21:14
Arkady_Kanevsky+121:14
shamailThe general premise behind this action item is to add weights to the responses we get from projects on which themes they are pursuing21:14
shamailThe current process counts each entry equally so if Nova, Kuryr, Zaqar say they are working on theme #1, it would show the count as 321:15
Arkady_Kanevskyshould we give "core" components hight weitght?21:16
shamailin the future, we want to weigh the feedback so that (in the same example) it would Nova = 1 * <adoption rate> + Kuryr = 1 * adoption rate + Zaqar = 1 * adoption rate21:16
Arkady_Kanevskyjust adoption rate as multiplier?21:16
shamailso that we say which theme was the most relevant based on the projects being adopted21:16
shamailYes Arkady_Kanevsky21:16
shamailAdoption rate is a large part of the “core” component and therefore those lists would probably overlap21:17
*** MeganR_ has joined #openstack-meeting-alt21:17
Arkady_Kanevskyso we are looking in late #s for adoption from previous released to prioritize future work?21:17
*** panda is now known as panda|zZ21:17
Arkady_KanevskyI guess - as good as we can do now21:18
shamailArkady_Kanevsky: Just for weighing the themes, not for development proposal priortization21:18
Arkady_Kanevsky+221:18
shamailWe can refine if we get better inputs in the future but its a good starting point without creating too much additional work21:18
Arkady_Kanevskyagree21:18
shamailAction item: Summary and next steps/ project out line & working plan:21:18
shamail#link https://etherpad.openstack.org/p/PTLupdatesBoston21:18
shamailHeidi Joy shared plans about the PTL updates track scheduled for Boston (which will replace our Design Series Webinars with PTLs)21:19
shamailPlease add your name to the list if you would like to participate in those interviews/roadmap creation21:19
shamailAction item: update wiki with glossary/template-with-examples21:20
*** MeganR has quit IRC21:20
shamailThis one currently has no owner but the general discussion was to create examples in our wiki and repository that show what a completed development proposal (formerly called user story), tracker, gaps analysis, etc. might look like21:21
shamailthis is to help newcomers understand those artifacts21:21
shamailAction item: Categorizing openstack projects21:22
Arkady_KanevskyIf nobody will take it I will see if can do on weekend.21:23
*** matrohon has quit IRC21:23
shamailThanks Arkady_Kanevsky!21:23
GeraldKI could take the previous one on updating the Wiki with glossary/templates21:23
shamail#action Build sample development proposal, tracker, and gaps analysis for illustration purposes (Arkady_Kanevsky)21:23
*** diazjf has joined #openstack-meeting-alt21:24
shamail#action Update wiki with Glossary and overview of templates (GeraldK)21:24
shamailThanks GeraldK21:24
shamailThe next action item is to help the OpenStack Foundation with building categories for the various OpenStack projects to make navigation simpler for new users21:24
shamailWe will need volunteers to help with this sub-team/task21:25
shamailI will be glad to help with this one along with others who are interested21:25
Arkady_KanevskySHamail - what kind of categories you arethinking?21:25
shamailThey already have a list of categories created, we just need to review and help simplify project descriptions where applicable21:25
shamailhttps://etherpad.openstack.org/p/MIL-pwg-meetup21:26
shamailArkady_Kanevsky: Look at line 43621:26
Arkady_Kanevskygot it - Configuration Management, Containers, Virtual Machines, Databases, Networking, Monitoring, Big Data, Storage, Service Catalog, etc.21:26
shamailThat’s about it on the unassigned action items21:27
shamail#topic Storyboard21:27
*** openstack changes topic to "Storyboard (Meeting topic: product_working_group)"21:27
*** dave-mccowan has quit IRC21:27
shamailIn our discussion about simplifying the (initial) idea submission process, we discussed and settled on storyboard as a possible solution21:27
shamail#link https://storyboard.openstack.org/#!/page/about21:28
shamailPlease look through the site to familarize yourself with it for now, but we will follow-up in a future meeting to review what works, what doesn’t, etc.21:28
jamemccI joined to talk about User Story Tracker (not exaclty Storyboard, but related I believe)21:28
shamailSounds good jamemcc, i’ll make sure we get to the opens so we can discuss.21:29
jamemccIf nothing else- to announce there is a project meeting tomorrow21:29
*** adisky_ has quit IRC21:29
shamailjamemcc: Go ahead and share the details21:29
Arkady_KanevskyNeed to clean up defintions - It all begins with a story. A story is a bug report or proposed feature. Stories are then further split into tasks, which affect a given project and branch.21:30
shamailI’ll add it as ‘info’ to our log21:30
Arkady_KanevskyNeed extend "proposed feature" to proposal definition. with single project feature reqyuest a subset of it21:30
Arkady_KanevskyI guess I can create a bug for it?21:31
shamailArkady_Kanevsky: Yes, I think the current thought is to use storyboard as an area where users (not active PWG members) can post an idea and associate it with a project labelled ‘development proposal’… our team would then review that queue and the ones that seem to be a significant need will be picked up for development proposal creation by us.21:31
jamemccFour User Story Tracker meeting: The open question for the project team is any enhancements needed and when / how can we get pointed at production repository.21:31
jamemccPurpose: Ongoing status tracking and collaboration for the Product Working Group driven development and rollout of the User Story Tracker.  Meeting will occur every 2 weeks at 2PM Pacific Time.21:31
jamemccEtherpad link: https://etherpad.openstack.org/p/User_Story_Tracker21:31
jamemccTool link: http://featuretracker.openstack.org/21:31
shamail#link https://etherpad.openstack.org/p/User_Story_Tracker21:32
shamail#link http://featuretracker.openstack.org/21:32
jamemccTuesday, March 28, 2017 4:00 PM-5:00 PM (UTC-06:00)21:32
jamemcchttps://join.att.com/meet/jm6819/672FQ2YC21:32
jamemccWeb conference21:32
jamemccurl: https://join.att.com/meet/jm6819/672FQ2YC21:32
shamail#info Feature Tracker tool team meeting: Tuesday, March 28, 2017 4:00 PM-5:00 PM (UTC-06:00) [https://join.att.com/meet/jm6819/672FQ2YC]… Please join if able.21:33
AndyUWe also talked about letting posting an initial abstract and get feedback on whether or not it was worth putting in the further effort. Or will it be eclipsed by other priorities.21:33
shamailAndyU: +121:33
jamemcc#link https://join.att.com/meet/jm6819/672FQ2YC21:33
shamailThe submission into storyboard is an entry point into gauging broader need for an idea… if it doesn’t get much traction then we will note that in the submission comments21:33
AndyUI'm very motivated to help with the Dev Proposal (aka Story) process enhancements. Having to multi-task in two meetings right now so not following the PTG meeting very well.21:34
shamailThanks jamemcc, I think it would be good to get a demo scheduled for those that are interested in the Feature Tracker to see if there are any remaining gaps/enhancements that could be made for V121:34
shamailNo problem AndyU, I was just sharing Storyboard with everyone for familiarity… we can dive deeper into the impact on process in a future meeting.21:35
shamailOkay to move to the next topic?21:35
AndyUThx. Just would like to pitch in. Don't want to miss it ;-)21:35
rockygjamemcc, also, is there a link to a wiki page or a calendar that hast the meeting info on it?  Be nice to be able to bookmark the meeting info.21:35
shamailrockyg: +1! jamemcc: It might be good to add a page to our wiki on Feature Tracker21:36
Arkady_KanevskyAdding the pointer from agenda wiki page will be goode for storyboard item21:36
*** diazjf has quit IRC21:37
jamemccSure - I will21:37
Arkady_Kanevskythanks21:37
shamailjamemcc: Making it a sub-page here might be ideal [https://wiki.openstack.org/wiki/ProductTeam/User_Stories]21:37
jamemcc#action Jamey to update PWG wiki for Feature Tracker project meetings21:37
AndyU+1 to adding more detail to wiki on all facets of Dev Proposal workflow21:37
shamail#action Update PWG wiki to add a page on Feature Tracker and meeting info (jamemcc)21:37
shamail#topic https://wiki.openstack.org/wiki/Meetings/product-team21:38
*** openstack changes topic to "https://wiki.openstack.org/wiki/Meetings/product-team (Meeting topic: product_working_group)"21:38
shamailCopy Fial.21:38
shamailFail*21:38
shamail#topic Forum session submission21:38
*** openstack changes topic to "Forum session submission (Meeting topic: product_working_group)"21:38
shamail#info Deadline for Forum Topic submissions is 11:59PM UTC on SUNDAY April 2nd21:38
shamail#link http://forumtopics.openstack.org/21:39
shamail#action User Story owners should submit a forum session for their respective stories (all user story owners)21:39
shamailIf anyone has additional ideas, please submit them as well.21:39
shamailI think we had discussed submitting a session on PWG overview and workflow.21:40
shamailArkady_Kanevsky: Did you volunteer to submit that one?21:40
Arkady_KanevskyYes. I have it in https://etherpad.openstack.org/p/BOS-UC-brainstorming21:40
shamailAlso, please note that if you submitted a topic to the brainstorming etherpad for the Forum that it won’t be automatically transferred into the tool21:40
Arkady_KanevskyNeed to formally submit it.21:40
shamailPlease take any ideas from the etherpad to formal submission via the tool21:41
shamailThanks Arkady_Kanevsky21:41
AndyUI have a few to submit yet21:41
shamailAwesome AndyU, you have a few days left :)21:41
shamailAnything else on this topic?21:41
Arkady_KanevskyActual proposal is at https://etherpad.openstack.org/p/BOS-PTG-proactive linek from BOS-UC-brainstorming one as agreed21:41
shamailArkady_Kanevsky: thanks!21:42
AndyUWhen we do, what's expected?  An abstract, create an etherpad(?) for the session, etc?21:42
shamail#link https://etherpad.openstack.org/p/BOS-UC-brainstorming21:42
shamail#link https://etherpad.openstack.org/p/BOS-PTG-proactive21:42
*** sshnaidm is now known as sshnaidm|off21:43
shamailAn abstract is ideal, etherpads can be created after the session is accepted BUT if you already have an etherpad on the topic (like Arkady_Kanevsky just linked) then I would recommend including it in the abstract to show the discussions already happening21:43
shamailAndyU: ^21:43
AndyUthx!21:43
shamail#topic Vote on biweekly dial-in and IRC meeting21:43
*** openstack changes topic to "Vote on biweekly dial-in and IRC meeting (Meeting topic: product_working_group)"21:43
GeraldKdo we have a list of owners for the different user stories?21:44
shamailGeraldK: Good question, we did at one point: https://wiki.openstack.org/wiki/ProductTeam/User_Stories/Rolling_Upgrades21:44
shamailbut those pages are out-dated21:44
shamailWe know who are the owners but, to your point, there is no wiki page as a “source of truth”21:45
shamailmight be worth adding as well21:45
GeraldKI see team members, but no "owner".21:45
*** felipemonteiro_ has quit IRC21:45
shamailKenny is the owner, but to your point, not noted as such on the page21:45
GeraldKwe should capture the owners to avoid submission overlaps or no submission as no one felt like the owner21:45
AndyUyes21:46
shamailI think we should probably remove the user story sub-pages and add a general one with a list of stories (link to the actual entry in the repo) along with the owner21:46
*** ijw_ is now known as ijw21:46
GeraldKshamail: +121:46
shamail#action Remove user story sub-pages and add a new page that lists user story link and owner information (shamail)21:46
shamailI can handle that one21:47
GeraldKI can do this as part of the Wiki updates assigned to me earlier on in this meeting21:47
shamailOh cool21:47
AndyUalso need to be able to reflect some sense of if it's moving forward or lagging. Also Priority21:47
GeraldKokay21:47
Arkady_Kanevsky+121:47
shamailLet me know if you need to know who the owners are via email21:47
*** haleyb has quit IRC21:47
shamail#action Remove user story sub-pages and add a new page that lists user story link and owner information (GeraldK as a part of the other wiki AI)21:47
GeraldKshamail: yes. can you pls share via email?21:47
shamailWill do21:47
GeraldKAndyU: +121:48
shamail#action email list of user story owners to GeraldK (shamail/leong)21:48
shamailAndyU: That is where the Feature Tracker comes into play… up to the completion of gaps analysis, we have to relay on data from Gerrit, etc.21:48
Arkady_Kanevskyand what do we do with stories with no owners (owner left PTG)?21:48
GeraldKAndyU: however, I am not sure we should capture this on the Wiki page as this information is too dynamic21:48
shamailAfter that, we can use the Feature Tracker to see if its active21:48
AndyUWe should think about how we can assess/provide priority.  Via action of UC, TC, Board? Community voting? User Survey?21:49
shamailGeraldK: +121:49
AndyUYes, to big for just a wiki page at this point  :-)21:49
Arkady_KanevskyThat why we had a subpages in the first place21:49
AndyUJust suggesting we do some more brainstoriming around that21:49
shamailAndyU: That is a difficult topic since user stories generally move forward when someone volunteers to “own” it.. The only way to get external prioritization is if we basically agree that we will staff user stories based on the prioritized list that is determined by whatever means21:50
*** rocky_g has joined #openstack-meeting-alt21:50
*** rockyg has quit IRC21:50
shamailI think this is where the “Feature Triage” team will play a role but details for that don’t exist yet21:50
Arkady_KanevskyI htink we had categorization of 3 stories in driven state others ad hoc21:50
*** Shrews has joined #openstack-meeting-alt21:51
shamailWe do Arkady_Kanevsky but my point was that those states are a result of who is willing work on a user story and not necessarily based on the priority of the feature being delivered21:51
AndyUUnderstood. But I think they need some kind of legitimation. Something to help motivate projects to support them. Else only Owners who can do it all on their own (like OSIC maybe) will be successful.21:51
rocky_gsorry. got disconnected and missed the previous 5 minutes.21:51
shamailAndyU: +100021:51
*** diazjf has joined #openstack-meeting-alt21:51
*** tonytan4ever has quit IRC21:51
shamailIt would be much better to have an external review of the list of stories being worked on21:51
rocky_gI think feature triage will be important to move forward faster.21:51
Arkady_KanevskyShamail it was a combinatoin of both: owner willingness tpo drive and prioritization.21:51
shamailThis is something we can definitely discuss again in a future meeting (large topic) and continue in our next face to face as well.21:52
shamail#action Add discussion on story staffing, prioritization/drivers to a future PWG meeting21:53
AndyUWe could also use priorities that get identified as a basis for requesting Dev proposals if not exist to address the need yet.21:53
shamail+121:53
shamail#topic opens21:53
*** openstack changes topic to "opens (Meeting topic: product_working_group)"21:53
shamailDo we have anything else to discuss?21:54
Arkady_Kanevskyneed to drop - have a great day everbody21:54
shamailThe prioritization topic needs to be a future topic because it will take awhile :)21:54
AndyUWe discussed starting to have some voice meetings. Those big brainstorming topics would be good for that format.21:54
shamailAndyU: +121:54
*** Swami has quit IRC21:54
rocky_g+10021:55
shamailWill have to send an email to gauge whether people prefer a bi-weekly IRC/voice cadence or just IRC (we don’t have enough members in the meeting today)21:55
GeraldKcan someone have a look at https://review.openstack.org/#/c/434577/21:55
shamailIt is always an option to setup one-off phone meetings too… we normally do this for roadmap or other sub-team activities21:55
shamail#action Please review https://review.openstack.org/#/c/434577/21:56
*** zz_dimtruck is now known as dimtruck21:56
shamailI put it down GeraldK so that I remember21:56
GeraldKthanks shamail21:56
shamailThank you everyone!21:56
shamailHave a great evening/day21:56
shamail#endmeeting21:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:57
openstackMeeting ended Mon Mar 27 21:57:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-03-27-21.00.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-03-27-21.00.txt21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-03-27-21.00.log.html21:57
*** MeganR_ has quit IRC21:57
GeraldKbye everyone.21:57
shamailbye21:57
rocky_gThanks!21:57
*** shamail has quit IRC21:57
AndyUBye!!  :)21:57
Shrewsjeblair: before you start, https://review.openstack.org/447814 has nothing to do with nodepool :)  (bad link on the agenda)22:00
*** jrobinson has joined #openstack-meeting-alt22:00
pabelangerohai22:00
jheskethHowdy22:00
fungiohai22:00
jesusaurhullo22:00
* clarkb is around22:00
* fungi notices pabelanger already ohai'd, so switches to 'allo22:01
SpamapSahoy!22:01
jeblairShrews: thanks, fixed :)22:01
jeblair#startmeeting zuul22:01
openstackMeeting started Mon Mar 27 22:01:57 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: zuul)"22:02
*** kfarr has quit IRC22:02
openstackThe meeting name has been set to 'zuul'22:02
jeblair#topic  Actions from last meeting22:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: zuul)"22:02
*** GeraldK has quit IRC22:02
jeblairoh whoops22:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/Zuul#Agenda_for_next_meeting agenda22:02
*** amotoki has joined #openstack-meeting-alt22:02
jeblair#link http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-03-20-22.02.html previous meeting22:02
jeblairmordred to let ppl know when to review changes he's working on that the details are long to share while metal tubing22:02
jeblairmordred: i think that was you were expecting to hack on the nodepool-zk shim and ping us when ready22:02
jeblairi don't remember being pinged, so i guess that didn't happen22:03
mordredyes - this is correct22:03
mordredI was goign to work on that, and worked on other things instead - I now expect to hack on the shim _this_ week22:03
jeblairokay22:04
jeblairi'm not sure it's useful to re-action that22:04
jeblairif a shim shows up one day, that's great.22:04
*** david-lyle has quit IRC22:04
jeblair#topic Status updates (nodepool)22:05
*** openstack changes topic to "Status updates (nodepool) (Meeting topic: zuul)"22:05
jeblairthat's the status of the shim i guess :)22:05
*** david-lyle has joined #openstack-meeting-alt22:05
* rbergeron arrives late 22:06
mordredthe shim loves you all22:06
*** jamielennox has joined #openstack-meeting-alt22:06
jeblairi put a bunch of things on the agenda which i thought we should make sure to make progress on this week22:06
jeblairthey all merged22:06
jeblairso, neat trick.  i'll have to try that again.22:06
mordred\o/22:06
Shrewsnot all22:06
Shrewsdocs changes are still up22:06
Shrewsbut some of those merged22:06
mordredShrews: ssssshhhhhh22:07
pabelangerI can review again22:07
*** jaugustine has quit IRC22:07
jeblair#link https://review.openstack.org/447647 legacy openstack setting removed22:07
ShrewsAt SpamapS's's'ss urging, I went through the current nodepool docs and made several updates. Those are the result22:07
SpamapSlovely22:07
*** jkilpatr has quit IRC22:07
jeblair#link https://review.openstack.org/448814 update nodepool config syntax22:07
SpamapSI'll try urging more too22:08
jeblairthose are the ones that merged22:08
jeblair(those are the tips of stacks of related changes -- so those were significant efforts)22:08
jeblairjust like the docs changes22:08
pabelangerjeblair: Shrews: trivial, but did we want make the zookeeper host settings the same between zuul and nodepool? because today are a little different22:08
jeblairwhich we should be able to merge now:22:08
jeblair#link https://review.openstack.org/449140 nodepool docs changes22:08
*** cdearborn has quit IRC22:09
jeblairpabelanger: yeah, it would be nice if we can normalize that.22:09
Shrewspabelanger: what's different?22:09
jeblairthere was some technical obstacle to using nodepool's way in zuul which i don't recall22:09
jeblairShrews: nodepool has a data structure in yaml, zuul has a connect string. iirc22:10
clarkbif I haven't flipped things around zuul's way was chosen ebcause that way we didn't have to construct the string for kazoo for it22:10
jeblairoh!22:10
clarkband we did that because zuul's config is ini22:10
jeblairit's because zuul uses ini conf  files22:10
jeblairya22:10
clarkbwe could do the same for nodepool just store string in yaml22:11
pabelangerzuul: zookeeper_hosts=127.0.0.1:2181,example.org:218122:11
pabelangernodepool is list22:11
jeblairalso, when we consider that we may need to put ZK credentials in the nodepool secret file, that may affect what we want to do too.22:11
clarkbya its a yaml list of all the things that get concatenated together tiwh commas to pass to kazoo22:11
*** amotoki has quit IRC22:12
Shrewsif we do the secrets thing for nodepool, the structure still seems best IMO22:12
Shrewsbut i'm not strongly tied to i22:13
Shrewst22:13
*** xyang1 has quit IRC22:13
jeblairso maybe we should poke at doing zk authentication while keeping this in mind.22:13
Shrewsspeaking of which, the nodepool secrets file is now optional22:14
pabelangerI can poke at zk auth things22:14
Shrewsb/c there is nothing read from it  :)22:14
Shrewspabelanger: awesome. thx22:14
clarkbdo we want to keep it optional and allow unauthenticated zk going forward?22:15
clarkb(I don't actually knwo)22:15
mordredunauth zk for people running a local nodepool might be nice22:15
pabelangerya22:15
mordredlike, if you wante to run a nodepool in your house for some reason22:15
rbergeron(who wouldn't?)22:15
SpamapSmy house is a node pool22:15
mordred(this is probably more important for zuul all-in-one on a laptop)22:15
jeblairi think optional authentication is probably okay.  i think we should at least use ssl in openstack-infra.  possibly auth.22:16
jeblairi also am somewhat more inclined than previously to have things like zk connection info in a separate config file from the image/provider config.22:17
pabelangersure22:17
jeblairi was hopeful we could drop the 'secrets' file entirely, but i doubt we will be able to do that.22:18
*** sdague has quit IRC22:18
fungiit's nice to be able to rely on unix file permissions to protect things which absolutely need it without protecting lots of other things that don22:18
fungi't22:18
jeblairanyway, we can bikeshed on that later, anything else we should cover on nodepool?22:19
jeblair#action pabelanger look at zk authentication for nodepool22:19
jeblair#info consider reconciling nodepool and zuul zookeeper configuration syntaxes22:19
jeblair#topic Status updates (Devstack-gate roles refactoring)22:19
*** openstack changes topic to "Status updates (Devstack-gate roles refactoring) (Meeting topic: zuul)"22:19
jeblairdid anyone want to push on this or should we skip to next topic?22:20
clarkbone thing22:20
*** EricGonc_ has quit IRC22:20
clarkbrelated to this we broke third party CIs22:20
*** rfolco has quit IRC22:20
clarkbI haven't looked to see if the old code would've broken them too (likely)22:20
clarkbbut just something to keep in mind as review happens for these22:21
jeblairi think it's premature to say this broke third party cis22:21
jeblairbut i agree that is worth keeping in mind22:21
clarkbya I think it likely the old code would've broken on them too22:21
clarkbI just haven't had a chance to check22:22
jeblairthird-party ci operators are welcome to participate in this and review code22:22
jeblair(i think we've been pretty clear that we're happy to accomodate the use case in devstack-gate but we will not take operational responsibility for 100 ci systems on our own)22:23
fungiclarkb: actually, if this is the change i think you're talking about, it was part of a series to try to fix the pbr integration tests22:24
clarkbfungi: yes, but only the first chagne was needed to fix pbr22:24
clarkbfungi: the code that broke ci was our network ping test which now failed after we checked return codes22:24
jeblairbut back to the topic -- last week we agreed this was important, but i'm not sure we signed anyone up to drive it.22:24
*** Arkady_Kanevsky has quit IRC22:25
clarkbthe current change to do network overlays is really close22:25
jeblairshould we do that now, or should we revisit how important we think it is?22:25
clarkbIf someone wants to pick it up I can help with it22:25
*** fnaval has quit IRC22:25
clarkbI can also push patches if someone else wants to review the cahnges22:25
clarkbbut so far I haven't seen a ton of interest in reviewin them (by cores at least)22:25
jeblairwould anyone like to volunteer for either of those things?22:27
pabelangerare we at the step where we want to run devstack (current layout) under zuulv3?22:27
clarkbold code would've broken too22:27
jeblairi don't think so22:27
jeblairpabelanger: ^22:27
clarkbit relied on region and cloud being set in the /etc/nodepool/provider file which doesn't necessarily imply mirror exists22:27
jeblairthis is still trying to get it organized into roles so that we can have a first-rate example of how we think a complex job can be set up22:28
jeblairthis is something we've all said we want and is important22:28
jeblairso i'd love it if someone would volunteer for one of those things22:28
jeblairbut i'm not going to pretend it's a priority if no one is going to do it, so if no one steps up now, i'm dropping it from the agenda and moving it to backlog on the board.22:29
*** Adri2000 has quit IRC22:29
jheskethI'd like to help but I don't think I understand the parts well enough sorry22:30
fungiit's worth noting that the early changes serve as good examples for how to split more of it up22:30
pabelangerif we are not going to do more tox jobs or other jobs for openstack-infra, I can start working on devstack22:31
fungiand we have loads of testing (granted we react retroactively to third-party breakage)22:31
pabelangerI would have like to get another project going and iterate on our stdlib for tox22:31
pabelangerbut if devstack is important, I can shift22:31
fungiso you can mostly know if what you're splitting out will change overall behavior22:31
pabelangerif not devstack, I was planning on working on our roles for nodepool / zuul / etc all in one22:33
jeblairthat's pretty important too22:33
jeblairi thought we had more folks interested in writing ansible22:33
pabelangerI would prefer to focus on that22:33
jeblairwe've been on this topic for 14 minutes and no one has said "i volunteer to drive this"22:34
* rbergeron would think more folks might be interested in writing ansible as well -- maybe we are not being explicit enough? 22:35
rbergeron(not that i'm biased or anything)22:35
jeblairrbergeron: maybe they aren't showing up to this meeting or otherwise participating22:35
jeblairwe've been pretty clear about this topic when it's come up in prior meetings and other areas22:35
*** jkilpatr has joined #openstack-meeting-alt22:35
Shrewsan email to the ML for volunteers?22:35
clarkbfwiw I'm happy to help, but so far have done so as a reviewer and actually think careful independent review has been good on this task so far22:35
jeblairit's strictly ansible work; almost nothing to do with zuul at all22:36
clarkbso don't want to transitition to writing the patches unless someone lese is willing to also do the review22:36
clarkbbut happy to do either task if someone else will do the other :)22:36
pabelangerI can help review22:36
jeblairShrews: yeah, let's send an email to the ML22:36
rbergeroni just wonder if ... people know that's the possibility at hand and/or understand that perhaps other perceptions about "the bar is xyz high" ... is not so high for this? i would think maybe asking at least hte openstack-ansible folks, kolla folks, bifrost folks, etc. might yield some humans :)22:36
clarkbI think part of it for the osa/kolla/et al folks is devstack is such a dirty word22:37
fungiwe have a big, complex shell script (well, okay it;s a couple of shell scripts) that need ansibling. sounds pretty compelling anyway ;)22:37
clarkbeven though this really doesn't have much to do with devstack22:37
rbergeroni mean there's a pretty decently sized # of ansible users (who would probably also be great as far as sanity checking anyway)22:37
rbergeronclarkb: yeah, but i think they all <3 ansible enough that... yeah. i think they all know how this benefits a lot of folks.22:37
jeblairrbergeron: do you want to see if you can wrangle anyone via ML, etc?22:37
rbergeronjeblair: i can do that -- is ML really the best place for that?22:38
rocky_gcc the operators list on the email.  They may be willing...22:38
jeblairrbergeron: i have no idea :|22:38
* rbergeron hesitates to be like "hey ansible this stuff we need halp" because .. i mean, all projects always need help22:38
rbergeronbut I am sure i can figure out the appropriate wording for such things22:39
jeblairrbergeron: if you want to wrangle by asking people behind the scenes, that's fine too22:39
rbergeronand am always unafraid of looking silly anyway, mostly22:39
rbergeronjeblair: i may do that first -- i do have the mental list of humans22:39
*** beslemon has quit IRC22:39
jeblairi'm just at a place where there's this think we pretend is a priority every week during this meeting and nothing's moving.  so i'm going to stop pretending.22:39
* rbergeron nods22:39
jeblairs/think/thing/22:39
rbergeronokay, i will do the recruitment :) (I mean, this is one thing i'm decent at :D)22:40
jeblair#action rbergeron try to find someone to work on ansiblification of devstack-gate22:40
jeblairrbergeron: thank you :)22:40
jeblair#topic Status updates (Zuul test enablement)22:40
*** openstack changes topic to "Status updates (Zuul test enablement) (Meeting topic: zuul)"22:40
SpamapSWe landed some more!22:41
jeblairyay!22:41
SpamapS#link https://etherpad.openstack.org/p/zuulv3skips22:41
SpamapSI updated that22:41
* rbergeron apologizes for not being more meeting-note-taking tonigght but schedule is all weird being on east coast (meeting at 6pm instead of 3pm; dear lord, no idea how shrews does this :D) 22:41
rbergeronyassss :)22:41
SpamapScovered landed tests with strikethroughs22:41
*** AndyU has quit IRC22:41
SpamapSand linked a few of the in-flight ones22:41
Shrewsrbergeron: i suffer with alcohol in hand22:42
jeblairjesusaur: are you still hacking on 446275 -- the merge check thing?22:42
SpamapSwe're down to about 18 that aren't being worked22:42
SpamapSand most are in the "Straightforward" category.22:42
SpamapSfeels like progress. :)22:42
jeblairi think some of those might inadvertently depend on 446275, though i haven't checked on how many22:42
*** tommylikehu_ has joined #openstack-meeting-alt22:42
SpamapSthat makes sense22:42
jesusaurjeblair: yeah, but it's turning out to be quite a game of whack-a-mole22:43
ShrewsSpamapS: how many people do we have actively working zuul tests now?22:43
jeblairjesusaur: okay, let me know if i can help or if you need me to clean up my own mess :)22:43
jesusaurif anyone would like to help debug failures on 446275 I would appreciate it, otherwise I will slowly work through them22:43
SpamapSShrews: me, jesusaur, pabelanger, adam_g, eggshell22:43
SpamapSmaybe more22:43
*** rarcea has quit IRC22:43
jeblairjesusaur: okay, i'll take a look at what's failing22:44
pabelangerI haven't touched a zuul test is some time, apologies for that22:44
jesusaurawesome22:44
SpamapSI don't know how I'll find tasks to do once they're all re-enabled. ;)22:44
ShrewsSpamapS: ah, ok. about to envelope myself in the warm arms of zuul, so was wondering if it would be a good place to step into22:44
SpamapSpabelanger: you are listed as owning a couple22:44
pabelangerSpamapS: yes, I keep saying I will fix them.  I will do this tomorrow22:45
SpamapSShrews: I think it's a good place yeah, though there's a bit of a learning curve on the test harness that might be easier climbed by writing new tests.22:45
jeblairwe only have 15 mins left, so i'm going to perform some emergency agenda surgery22:45
jeblair#Status updates (Zuul secrets)22:45
jeblair#topic Status updates (Zuul secrets)22:45
*** openstack changes topic to "Status updates (Zuul secrets) (Meeting topic: zuul)"22:45
Shrewsjeblair: we can skip my topic22:45
Shrewsif it helps22:45
jeblairShrews: i want to make sure we get yours :)22:46
jeblair#link http://lists.openstack.org/pipermail/openstack-infra/2017-March/005252.html22:46
jeblairi think the results of that thread were basically "do the rsa thing for now, maybe do something else later also"22:46
*** tommylikehu_ has quit IRC22:47
jeblairso i think that's our plan for the moment -- continue with pkcs1-oaep, and defer hybrid or other approaches for later22:47
jeblairsound right?22:47
pabelangerno objections from me22:48
jeblairclarkb, fungi, SpamapS: ^ ?22:48
SpamapSconcur22:48
mordred++22:48
fungiyeah, that's what i got from it22:48
clarkbI don't recall the thread reaching a consensus but I think thats probably fine place to start22:48
clarkbalso maybe use a 8096 bit key?22:49
jesusaurjeblair: if there are still concerns about payload size, could we potentially use an 8192 bit rsa key?22:49
jesusaurclarkb: yep22:49
clarkber22:49
clarkbjesusaur: can math better than me22:49
fungithe discussion basically went the same direction i'd already supported in irc, so just sort of sat on the sidelines22:49
SpamapS5120 bit would work fine22:49
jeblairclarkb: yeah, it was more like SpamapS advocated that and no one else objected or advocated anything else :)22:49
SpamapSif we really really really want to be able to store 4096 bit privkeys22:49
clarkbSpamapS: there is more than just ssh keys though so I think being generous is probably a good idea22:50
jeblair#agreed proceed with pkcs1-oaep, consider other forms of encryption later22:50
jeblairthat makes all the secrets twice as large22:50
jeblair#info consider changing the rsa keysize22:51
jeblairlet's talk about that more later22:51
fungiyeah, you're basically trading field capacity for extra overhead of all crypted data22:51
pabelangerbecause I don't know, what is the downside to that? more CPU?22:51
SpamapS8192 just evokes the image of a hobbit wielding a claymore in my mind22:51
clarkbpabelanger: ya thats probably the biggest one22:51
jeblairso the changes to implement this are in this stack:22:51
jeblair#link https://review.openstack.org/406382 encryption stack22:51
fungipabelanger: even harder to read yaml files, but they'll already be pretty bad even with 4096-bit22:51
jesusaurpabelanger: yeah, main reason it's not used is increased computation time with negligible increase in security22:51
jeblair#link https://review.openstack.org/447087 crypto review22:51
jeblair#link https://review.openstack.org/447088 crypto review22:52
jeblairi think it would be great if we could find someone who understands what some of those magic numbers mean to review those 2 changes22:52
jeblairthose really nicely put all the crypto decisions front and center22:52
jeblair(the rest are about integrating into zuul)22:52
*** markvoelker has joined #openstack-meeting-alt22:52
fungijesusaur: but also it's more often used for encrypting common-length (short) bits of data like hashes. if we want to encrypt variable length stuff the key size determines how long that can be22:53
jeblairso if anyone here feels they can take a look and say "yes, this is how you should invoke the rsa algorithm", please look at 447087 and 44708822:53
* fungi stars those22:53
*** tommylikehu_ has joined #openstack-meeting-alt22:53
jeblairand if we feel that we should reach out to anyone outside our community to review these, those are the two i think would be most profitable22:54
jeblairSpamapS, fungi, rbergeron: ^ maybe you have ideas about that?22:54
jeblairanyone else too.  just trying to put some likely folks on the spot.  :)22:54
jeblair#topic ZuulV3 @ Boston Summit (Shrews)22:55
SpamapSjeblair: I'm not sure who I'd reach out to22:55
*** openstack changes topic to "ZuulV3 @ Boston Summit (Shrews) (Meeting topic: zuul)"22:55
ShrewsSo, we touched on this very briefly last week, but I wanted to get some hard confirmation on whether or not we plan to do any zuulv3 team dev gathering at the summit like we did at the ptg.22:55
ShrewsSounded like we were leaning "no"22:55
clarkbalex gaynor and dstufft maybe?22:55
mordredShrews: I also got that sense22:56
jeblairi also got that sense22:56
fungithere will be some flexible hacking space in boston if people want to take advantage of it, but the tone of the summit/forum is to reach outside existing per groups and get into discussions with other segments of the community22:57
fungis/per/peer/22:57
Shrewsok, i think that answers the question definitively enough for me22:57
jeblairi plan on attending wearing my general openstack-infra hat22:57
fungiso there's not much emphasis on structured team-oriented activities22:57
*** Adri2000 has joined #openstack-meeting-alt22:57
*** Adri2000 has quit IRC22:57
*** Adri2000 has joined #openstack-meeting-alt22:57
*** tommylikehu_ has quit IRC22:58
mordredI plan on wearing my general openstack-infra hat - and also my "large consumer of OpenStack APIs" hat22:58
fungiand yeah, i'll be there with infra ptl, tc, vmt, foundation staff, et cetera hats on. not sure how to wear them at the same time22:58
Shrewsfwiw, i'm glad that i'm not important enough to have to wear other hats that divert my attention from fun stuff22:58
mordred(which are the same hat, to be fair)22:58
mordredfungi: oh, yeah - I suppose I'll also have my tc hat on22:59
fungimaybe i'll just wear a sombrero22:59
pabelangerSame, still waiting on travel funding from manager22:59
jeblairmordred: it's the one right next to your "loud consumer of openstakc apis" hat?22:59
mordredjeblair: I'M ALWAYS LOUD IT'S A GIVEN22:59
fungipretty sure that's a trucker hat22:59
*** rfolco has joined #openstack-meeting-alt22:59
SpamapSI'll be there to speak on Tuesday about Zuul things23:00
SpamapSand Forum as a user23:00
jeblairthanks everyone!23:00
*** rfolco has quit IRC23:00
fungii have a firehose infra talk with mtreinish and then am on a security panel23:00
jeblairwe'll talk about neglected agenda topics next week23:00
SpamapScheerio23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Mon Mar 27 23:00:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-03-27-22.01.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-03-27-22.01.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-03-27-22.01.log.html23:00
*** rocky_g has quit IRC23:01
*** Shrews has left #openstack-meeting-alt23:03
*** marst has quit IRC23:04
*** dsariel has quit IRC23:05
*** Sukhdev has quit IRC23:06
*** jrobinson has quit IRC23:06
*** ozamiatin has quit IRC23:06
*** rfolco has joined #openstack-meeting-alt23:08
*** rfolco has quit IRC23:09
*** annegentle has quit IRC23:16
*** marst has joined #openstack-meeting-alt23:18
*** jaypipes has quit IRC23:24
*** benj_ has joined #openstack-meeting-alt23:25
*** diablo_rojo has quit IRC23:26
*** dizquierdo has quit IRC23:39
*** annegentle has joined #openstack-meeting-alt23:42
*** diazjf has quit IRC23:43
*** annegentle has quit IRC23:49
*** EricGonczer_ has joined #openstack-meeting-alt23:52
*** tommylikehu_ has joined #openstack-meeting-alt23:54
*** dimtruck is now known as zz_dimtruck23:59
*** jamielennox has left #openstack-meeting-alt23:59
*** tommylikehu_ has quit IRC23:59

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