Monday, 2016-04-18

*** kei_yama_ has joined #openstack-meeting-alt00:01
*** EricGonczer_ has quit IRC00:01
*** kei_yama has quit IRC00:02
*** sdake_ has quit IRC00:02
*** Leom has quit IRC00:05
*** sdake has joined #openstack-meeting-alt00:06
*** salv-orlando has quit IRC00:06
*** ijw has joined #openstack-meeting-alt00:12
*** stingaci has quit IRC00:14
*** outofmemory is now known as reedip00:17
*** ijw has quit IRC00:18
*** Jae00 has quit IRC00:25
*** hughhalf_ is now known as hughhalf00:27
*** ekarlso has quit IRC00:32
*** j^2 has quit IRC00:40
*** Leo_ has joined #openstack-meeting-alt00:41
*** ekarlso has joined #openstack-meeting-alt00:45
*** Leo_ has quit IRC00:45
*** kzaitsev_mb has joined #openstack-meeting-alt00:50
*** kzaitsev_mb has quit IRC00:54
*** kei_yama_ has quit IRC00:58
*** zhurong has joined #openstack-meeting-alt01:00
*** j^2 has joined #openstack-meeting-alt01:01
*** ijw has joined #openstack-meeting-alt01:13
*** sdake_ has joined #openstack-meeting-alt01:14
*** sdake has quit IRC01:18
*** ijw has quit IRC01:19
*** kei_yama has joined #openstack-meeting-alt01:20
*** Leom has joined #openstack-meeting-alt01:22
*** edtubill has joined #openstack-meeting-alt01:23
*** stingaci has joined #openstack-meeting-alt01:26
*** wangqun has joined #openstack-meeting-alt01:36
*** gongysh has joined #openstack-meeting-alt01:48
*** kzaitsev_mb has joined #openstack-meeting-alt01:50
*** kzaitsev_mb has quit IRC01:55
*** ijw has joined #openstack-meeting-alt02:01
*** _amrith_ is now known as amrith02:06
*** banix has joined #openstack-meeting-alt02:08
*** banix has quit IRC02:08
*** alex_xu has quit IRC02:18
*** alex_xu has joined #openstack-meeting-alt02:22
*** tfukushima has joined #openstack-meeting-alt02:30
*** bana_k has joined #openstack-meeting-alt02:31
*** tfukushima has quit IRC02:33
*** kebray has joined #openstack-meeting-alt02:37
*** nadya has joined #openstack-meeting-alt02:39
*** kebray_ has quit IRC02:41
*** gongysh_ has joined #openstack-meeting-alt02:42
*** amrith is now known as _amrith_02:43
*** nadya has quit IRC02:43
*** bana_k has quit IRC02:46
*** dimtruck is now known as zz_dimtruck02:52
*** bana_k has joined #openstack-meeting-alt02:55
*** ccamacho has quit IRC02:55
*** yamamoto_ has joined #openstack-meeting-alt02:59
*** ccamacho has joined #openstack-meeting-alt03:02
*** amotoki has joined #openstack-meeting-alt03:11
*** yamamoto_ has quit IRC03:11
*** Sukhdev has joined #openstack-meeting-alt03:14
*** bana_k has quit IRC03:19
*** yamamoto_ has joined #openstack-meeting-alt03:21
*** sdake_ has quit IRC03:30
*** yamamoto_ has quit IRC03:43
*** neelashah has joined #openstack-meeting-alt03:44
*** dane_leblanc_ has quit IRC03:47
*** kzaitsev_mb has joined #openstack-meeting-alt03:52
*** tfukushima has joined #openstack-meeting-alt03:52
*** piet has joined #openstack-meeting-alt03:54
*** tfukushima has quit IRC03:56
*** kzaitsev_mb has quit IRC03:57
*** neelashah has quit IRC04:00
*** sgotliv_ has joined #openstack-meeting-alt04:06
*** tfukushima has joined #openstack-meeting-alt04:07
*** salv-orlando has joined #openstack-meeting-alt04:09
*** amotoki has quit IRC04:11
*** salv-orlando has quit IRC04:13
*** houming has joined #openstack-meeting-alt04:21
*** amotoki has joined #openstack-meeting-alt04:22
*** yamamoto_ has joined #openstack-meeting-alt04:27
*** ekarlso has quit IRC04:27
*** sdake has joined #openstack-meeting-alt04:28
*** amotoki has quit IRC04:30
*** gongysh_ has quit IRC04:34
*** tfukushima has quit IRC04:35
*** amotoki has joined #openstack-meeting-alt04:38
*** ekarlso has joined #openstack-meeting-alt04:41
*** salv-orlando has joined #openstack-meeting-alt04:48
*** gongysh_ has joined #openstack-meeting-alt04:50
*** kzaitsev_mb has joined #openstack-meeting-alt04:53
*** Poornima has joined #openstack-meeting-alt04:54
*** kzaitsev_mb has quit IRC04:58
*** amotoki has quit IRC05:01
*** edwardb_ has joined #openstack-meeting-alt05:03
*** rcernin has joined #openstack-meeting-alt05:03
*** sgotliv_ has quit IRC05:04
*** edwardb has quit IRC05:05
*** pgadiya has joined #openstack-meeting-alt05:06
*** Alex_Stef has joined #openstack-meeting-alt05:07
*** amotoki has joined #openstack-meeting-alt05:09
*** vilobhmm11 has joined #openstack-meeting-alt05:11
*** e0ne has joined #openstack-meeting-alt05:15
*** beslemon has joined #openstack-meeting-alt05:16
*** e0ne has quit IRC05:18
*** stingaci has quit IRC05:22
*** edwardb_ has quit IRC05:28
*** vilobhmm11 has quit IRC05:31
*** vilobhmm11 has joined #openstack-meeting-alt05:31
*** tpatzig_ has quit IRC05:35
*** mkoderer has quit IRC05:36
*** tfukushima has joined #openstack-meeting-alt05:36
*** lpetrut has joined #openstack-meeting-alt05:37
*** mkoderer has joined #openstack-meeting-alt05:39
*** tfukushima has quit IRC05:40
*** tfukushima has joined #openstack-meeting-alt05:45
*** kszukielojc has joined #openstack-meeting-alt05:47
*** edwardb has joined #openstack-meeting-alt05:47
*** davideagnello has joined #openstack-meeting-alt05:49
*** jprovazn has joined #openstack-meeting-alt05:50
*** edwardb_ has joined #openstack-meeting-alt05:51
*** davideagnello has quit IRC05:51
*** edwardb has quit IRC05:54
*** kzaitsev_mb has joined #openstack-meeting-alt05:54
*** gcb has quit IRC05:56
*** beslemon has quit IRC05:56
*** kzaitsev_mb has quit IRC05:58
*** tpatzig has joined #openstack-meeting-alt05:59
*** Sukhdev_ has joined #openstack-meeting-alt06:04
*** Sukhdev has quit IRC06:06
*** anilvenkata has joined #openstack-meeting-alt06:06
*** edtubill has quit IRC06:07
*** shadower has joined #openstack-meeting-alt06:09
*** Poornima has quit IRC06:16
*** paul-carlton2 has joined #openstack-meeting-alt06:16
*** numans has joined #openstack-meeting-alt06:22
*** piet has quit IRC06:28
*** scheuran has joined #openstack-meeting-alt06:30
*** zeih has joined #openstack-meeting-alt06:31
*** sridharg has joined #openstack-meeting-alt06:31
*** MarkBaker has quit IRC06:32
*** vilobhmm11 has quit IRC06:32
*** jtomasek has joined #openstack-meeting-alt06:33
*** pgadiya_ has joined #openstack-meeting-alt06:36
*** pgadiya has quit IRC06:36
*** pgadiya_ has quit IRC06:37
*** pgadiya has joined #openstack-meeting-alt06:37
*** alex_xu has quit IRC06:40
*** eliqiao has quit IRC06:40
*** alex_xu has joined #openstack-meeting-alt06:41
*** eliqiao has joined #openstack-meeting-alt06:42
*** dshakhray has joined #openstack-meeting-alt06:42
*** mickeys has joined #openstack-meeting-alt06:51
*** ihrachys has joined #openstack-meeting-alt06:52
*** kzaitsev_mb has joined #openstack-meeting-alt06:54
*** eranra has joined #openstack-meeting-alt06:55
*** kzaitsev_mb has quit IRC06:59
*** mickeys has quit IRC07:01
*** mickeys has joined #openstack-meeting-alt07:02
*** lpetrut has quit IRC07:06
*** ttx_ is now known as ttx07:06
*** mickeys has quit IRC07:07
*** dizquierdo has joined #openstack-meeting-alt07:09
*** paul-carlton2 has quit IRC07:12
*** dalgaaf has joined #openstack-meeting-alt07:13
*** e0ne has joined #openstack-meeting-alt07:16
*** ccamacho has quit IRC07:18
*** ijw has quit IRC07:20
*** matrohon has joined #openstack-meeting-alt07:21
*** MarkBaker has joined #openstack-meeting-alt07:21
*** ccamacho has joined #openstack-meeting-alt07:22
*** lpetrut has joined #openstack-meeting-alt07:26
*** paul-carlton2 has joined #openstack-meeting-alt07:26
*** Alex_Stef has quit IRC07:29
*** sridharg has quit IRC07:30
*** tremble has joined #openstack-meeting-alt07:31
*** tremble has quit IRC07:31
*** tremble has joined #openstack-meeting-alt07:31
*** shadower has quit IRC07:32
*** edwardb_ has quit IRC07:33
*** jschwarz has joined #openstack-meeting-alt07:34
*** thomas_ has joined #openstack-meeting-alt07:35
*** thomas_ is now known as shadower07:35
*** edwardb has joined #openstack-meeting-alt07:35
*** dizquierdo has quit IRC07:36
*** dukhlov has joined #openstack-meeting-alt07:37
*** sridharg has joined #openstack-meeting-alt07:41
*** edwardb has quit IRC07:42
*** dukhlov has quit IRC07:43
*** mikelk has joined #openstack-meeting-alt07:44
*** Sukhdev_ has quit IRC07:48
*** nadya has joined #openstack-meeting-alt07:48
*** rossella_s has joined #openstack-meeting-alt07:48
*** sgotliv_ has joined #openstack-meeting-alt07:49
*** lpetrut has quit IRC07:49
*** alex_xu has quit IRC07:49
*** lpetrut has joined #openstack-meeting-alt07:49
*** pnavarro has joined #openstack-meeting-alt07:50
*** alex_xu has joined #openstack-meeting-alt07:51
*** MarkBaker has quit IRC07:52
*** vgridnev has joined #openstack-meeting-alt07:54
*** MarkBaker has joined #openstack-meeting-alt07:54
*** kzaitsev_mb has joined #openstack-meeting-alt07:55
*** lpetrut has quit IRC07:56
*** vgridnev has quit IRC07:56
*** scheuran has quit IRC07:57
*** HeOS has joined #openstack-meeting-alt07:57
*** kzaitsev_mb has quit IRC08:00
*** kzaitsev_mb has joined #openstack-meeting-alt08:01
*** ndipanov has joined #openstack-meeting-alt08:03
*** MarkBaker has quit IRC08:03
*** paul-carlton2 has quit IRC08:06
*** kzaitsev_mb has quit IRC08:06
*** pnavarro has quit IRC08:08
*** scheuran has joined #openstack-meeting-alt08:11
*** sshnaidm has quit IRC08:12
*** dukhlov has joined #openstack-meeting-alt08:12
*** edwardb has joined #openstack-meeting-alt08:17
*** paul-carlton2 has joined #openstack-meeting-alt08:19
*** dukhlov has quit IRC08:20
*** edwardb has quit IRC08:21
*** ijw has joined #openstack-meeting-alt08:21
*** pnavarro has joined #openstack-meeting-alt08:22
*** paul-carlton2 has quit IRC08:24
*** dukhlov has joined #openstack-meeting-alt08:25
*** dukhlov has quit IRC08:27
*** ijw has quit IRC08:28
*** lpetrut has joined #openstack-meeting-alt08:31
*** neiljerram has joined #openstack-meeting-alt08:33
*** derekh has joined #openstack-meeting-alt08:40
*** sridharg has quit IRC08:53
*** sridharg has joined #openstack-meeting-alt08:59
*** sridharg has quit IRC08:59
*** yamamoto_ has quit IRC09:02
*** tfukushima has quit IRC09:02
*** yamamoto has joined #openstack-meeting-alt09:02
*** sridharg has joined #openstack-meeting-alt09:03
*** tesseract has joined #openstack-meeting-alt09:03
*** tesseract is now known as Guest3039409:03
*** tfukushima has joined #openstack-meeting-alt09:05
*** vgridnev has joined #openstack-meeting-alt09:06
*** sdake has quit IRC09:07
*** sdake has joined #openstack-meeting-alt09:07
*** lpetrut has quit IRC09:09
*** kzaitsev_mb has joined #openstack-meeting-alt09:22
*** lpetrut has joined #openstack-meeting-alt09:27
*** tfukushima has quit IRC09:28
*** tfukushima has joined #openstack-meeting-alt09:28
*** sshnaidm has joined #openstack-meeting-alt09:29
*** wangqun has quit IRC09:40
*** wangqun has joined #openstack-meeting-alt09:41
*** gcb has joined #openstack-meeting-alt09:42
*** dizquierdo has joined #openstack-meeting-alt09:42
*** zhurong has quit IRC09:44
*** ijw has joined #openstack-meeting-alt09:49
*** scheuran has quit IRC09:49
*** dukhlov has joined #openstack-meeting-alt09:52
*** clopez has quit IRC09:54
*** ijw has quit IRC09:54
*** pgadiya has quit IRC09:58
*** clopez has joined #openstack-meeting-alt09:59
*** lpetrut has quit IRC10:03
*** Alex_Stef has joined #openstack-meeting-alt10:03
*** sgotliv_ has quit IRC10:03
*** salv-orl_ has joined #openstack-meeting-alt10:04
*** scheuran has joined #openstack-meeting-alt10:04
*** salv-orlando has quit IRC10:07
*** lpetrut has joined #openstack-meeting-alt10:08
*** zhhuabj has quit IRC10:08
*** zhhuabj has joined #openstack-meeting-alt10:08
*** edwardb has joined #openstack-meeting-alt10:11
*** myoung has joined #openstack-meeting-alt10:11
*** wangqun has quit IRC10:14
*** wangqun has joined #openstack-meeting-alt10:14
*** sdague has joined #openstack-meeting-alt10:15
*** edwardb has quit IRC10:15
*** wangqun has quit IRC10:16
*** wangqun has joined #openstack-meeting-alt10:16
*** sgotliv_ has joined #openstack-meeting-alt10:22
*** wangqun has quit IRC10:22
*** dukhlov has quit IRC10:23
*** kzaitsev_mb has quit IRC10:24
*** qwebirc86264 has joined #openstack-meeting-alt10:32
*** qwebirc86264 has quit IRC10:34
*** lpetrut has quit IRC10:41
*** sgotliv_ has quit IRC10:43
*** ijw has joined #openstack-meeting-alt10:50
*** ijw has quit IRC10:56
*** dizquierdo has quit IRC10:59
*** dizquierdo has joined #openstack-meeting-alt11:00
*** jecarey has joined #openstack-meeting-alt11:00
*** kzaitsev_mb has joined #openstack-meeting-alt11:01
*** michchap_ has joined #openstack-meeting-alt11:01
*** vannif_ has joined #openstack-meeting-alt11:01
*** monester_ has joined #openstack-meeting-alt11:01
*** SlickN1k has joined #openstack-meeting-alt11:01
*** marcusvrn__ has joined #openstack-meeting-alt11:02
*** zhiyan_ has joined #openstack-meeting-alt11:02
*** serverascode_ has joined #openstack-meeting-alt11:02
*** xgerman_ has joined #openstack-meeting-alt11:02
*** agordeev_ has joined #openstack-meeting-alt11:02
*** wangqun has joined #openstack-meeting-alt11:02
*** judd7_ has joined #openstack-meeting-alt11:03
*** beekneemech has joined #openstack-meeting-alt11:04
*** yonglihe_ has joined #openstack-meeting-alt11:04
*** hrybacki_ has joined #openstack-meeting-alt11:04
*** aleksandr_null has joined #openstack-meeting-alt11:04
*** igordcard has joined #openstack-meeting-alt11:04
*** dmitryme2 has joined #openstack-meeting-alt11:04
*** krotscheck_ has joined #openstack-meeting-alt11:04
*** lbragstad_ has joined #openstack-meeting-alt11:04
*** njohnston_ has joined #openstack-meeting-alt11:04
*** a2hill has joined #openstack-meeting-alt11:04
*** CaptTofu_ has joined #openstack-meeting-alt11:05
*** cinerama` has joined #openstack-meeting-alt11:05
*** gnarld_ has joined #openstack-meeting-alt11:05
*** pmalik_ has joined #openstack-meeting-alt11:05
*** dmellado_ has joined #openstack-meeting-alt11:05
*** jasondotstar_ has joined #openstack-meeting-alt11:05
*** elmiko_ has joined #openstack-meeting-alt11:05
*** brain461_ has joined #openstack-meeting-alt11:05
*** MorAle__ has joined #openstack-meeting-alt11:05
*** clayton_ has joined #openstack-meeting-alt11:05
*** xgerman has quit IRC11:05
*** hrybacki has quit IRC11:05
*** marcusvrn_ has quit IRC11:05
*** carl_baldwin has quit IRC11:05
*** asilenkov has quit IRC11:05
*** njohnston has quit IRC11:05
*** tkhno has quit IRC11:05
*** yonglihe has quit IRC11:05
*** monester has quit IRC11:05
*** katyafervent_awa has quit IRC11:05
*** netapp has quit IRC11:05
*** aleksandr_null_ has quit IRC11:05
*** cFouts has quit IRC11:05
*** SlickNik has quit IRC11:05
*** judd7 has quit IRC11:05
*** mfranc213_ has quit IRC11:05
*** agordeev has quit IRC11:05
*** CaptTofu has quit IRC11:05
*** vmtyler has quit IRC11:05
*** MorAle_ has quit IRC11:05
*** lbragstad has quit IRC11:05
*** igordcar1 has quit IRC11:05
*** bookwar has quit IRC11:05
*** jasondotstar has quit IRC11:05
*** dmitryme has quit IRC11:06
*** mhayden has quit IRC11:06
*** zubchick has quit IRC11:06
*** kinrui has quit IRC11:06
*** serverascode has quit IRC11:06
*** Savemech has quit IRC11:06
*** zhiyan has quit IRC11:06
*** briancli1e has quit IRC11:06
*** harlowja has quit IRC11:06
*** nurla has quit IRC11:06
*** krotscheck has quit IRC11:06
*** dmellado has quit IRC11:06
*** vannif has quit IRC11:06
*** brain461 has quit IRC11:06
*** cinerama has quit IRC11:06
*** gongysh has quit IRC11:06
*** bnemec has quit IRC11:06
*** pmalik has quit IRC11:06
*** jecarey_ has quit IRC11:06
*** markmcclain has quit IRC11:06
*** elmiko has quit IRC11:06
*** ptoohill has quit IRC11:06
*** michchap has quit IRC11:06
*** jesusaur has quit IRC11:06
*** briancline has joined #openstack-meeting-alt11:06
*** clayton has quit IRC11:06
*** snackewm has quit IRC11:06
*** SlickN1k is now known as SlickNik11:06
*** brain461_ is now known as brain46111:06
*** markmcclain1 has joined #openstack-meeting-alt11:06
*** netapp_ has joined #openstack-meeting-alt11:06
*** monester_ is now known as monester11:06
*** jasondotstar_ is now known as jasondotstar11:06
*** agordeev_ is now known as agordeev11:06
*** MorAle__ is now known as MorAle_11:06
*** bookwar has joined #openstack-meeting-alt11:06
*** markmcclain1 is now known as markmcclain11:06
*** yonglihe_ is now known as yonglihe11:06
*** snackewm has joined #openstack-meeting-alt11:06
*** netapp_ is now known as netapp11:06
*** krotscheck_ is now known as krotscheck11:06
*** xgerman_ is now known as xgerman11:06
*** judd7_ is now known as judd711:06
*** clayton_ is now known as clayton11:07
*** marcusvrn__ is now known as marcusvrn_11:07
*** asilenkov has joined #openstack-meeting-alt11:07
*** dmitryme2 is now known as dmitryme11:07
*** hrybacki_ is now known as hrybacki11:07
*** mfranc213 has joined #openstack-meeting-alt11:08
*** katyafervent_awa has joined #openstack-meeting-alt11:08
*** nurla has joined #openstack-meeting-alt11:08
*** dougwig has quit IRC11:09
*** skath has quit IRC11:09
*** sweston has quit IRC11:09
*** zhiyan_ is now known as zhiyan11:10
*** CaptTofu_ has quit IRC11:10
*** rcernin has quit IRC11:12
*** serverascode_ is now known as serverascode11:12
*** zubchick has joined #openstack-meeting-alt11:13
*** tkhno has joined #openstack-meeting-alt11:13
*** skath has joined #openstack-meeting-alt11:13
*** Kennan has quit IRC11:13
*** sweston has joined #openstack-meeting-alt11:15
*** dougwig has joined #openstack-meeting-alt11:15
*** vmtyler has joined #openstack-meeting-alt11:16
*** kinrui has joined #openstack-meeting-alt11:17
*** carl_baldwin has joined #openstack-meeting-alt11:17
*** mugsie_ is now known as mugsie11:19
*** mhayden has joined #openstack-meeting-alt11:20
*** rcernin has joined #openstack-meeting-alt11:23
*** CaptTofu_ has joined #openstack-meeting-alt11:24
*** ByPasS has quit IRC11:27
*** dprince has joined #openstack-meeting-alt11:28
*** ByPasS has joined #openstack-meeting-alt11:28
*** brain461 has left #openstack-meeting-alt11:30
*** tfukushima has quit IRC11:30
*** Kennan has joined #openstack-meeting-alt11:32
*** dizquierdo has quit IRC11:33
*** iberezovskiy_afk is now known as iberezovskiy11:39
*** ccamacho is now known as ccamacho|lunch11:43
*** Savemech has joined #openstack-meeting-alt11:44
*** sgotliv_ has joined #openstack-meeting-alt11:44
*** dave-mccowan has joined #openstack-meeting-alt11:44
*** baoli_ has joined #openstack-meeting-alt11:49
*** tpsilva has joined #openstack-meeting-alt11:50
*** cdelatte has joined #openstack-meeting-alt11:52
*** ijw has joined #openstack-meeting-alt11:52
*** baoli has quit IRC11:52
*** weshay has joined #openstack-meeting-alt11:56
*** ijw has quit IRC11:58
*** yamamoto has quit IRC12:01
*** _amrith_ is now known as amrith12:03
*** mtreinish has joined #openstack-meeting-alt12:03
*** edwardb has joined #openstack-meeting-alt12:04
*** tellesnobrega is now known as tellesnobrega_af12:05
*** thomnico has joined #openstack-meeting-alt12:09
*** edwardb has quit IRC12:09
*** Poornima has joined #openstack-meeting-alt12:10
*** pgadiya has joined #openstack-meeting-alt12:10
*** zz_dimtruck is now known as dimtruck12:13
*** apetrich has joined #openstack-meeting-alt12:14
*** markvoelker has joined #openstack-meeting-alt12:19
*** prithiv has joined #openstack-meeting-alt12:23
*** rsyed_away is now known as rsyed12:25
*** tfukushima has joined #openstack-meeting-alt12:25
*** Poornima_K has joined #openstack-meeting-alt12:27
*** ddieterly has joined #openstack-meeting-alt12:29
*** ddieterly is now known as ddieterly[away]12:30
*** julim has joined #openstack-meeting-alt12:30
*** Poornima has quit IRC12:30
*** tfukushima has quit IRC12:34
*** zeih has quit IRC12:36
*** zeih has joined #openstack-meeting-alt12:37
*** yamamoto has joined #openstack-meeting-alt12:38
*** mageshgv has joined #openstack-meeting-alt12:39
*** dukhlov has joined #openstack-meeting-alt12:43
*** piet has joined #openstack-meeting-alt12:45
*** neelashah has joined #openstack-meeting-alt12:45
*** yamamoto has quit IRC12:45
*** yamamoto has joined #openstack-meeting-alt12:45
*** jdob has joined #openstack-meeting-alt12:46
*** gcb has quit IRC12:47
*** jecarey has quit IRC12:50
*** ninag has joined #openstack-meeting-alt12:50
*** Poornima_K has quit IRC12:50
*** yamamoto has quit IRC12:50
*** nelsnelson has quit IRC12:51
*** ddieterly[away] is now known as ddieterly12:53
*** lpetrut has joined #openstack-meeting-alt12:53
*** houming has quit IRC12:53
*** ijw has joined #openstack-meeting-alt12:54
*** yamamoto has joined #openstack-meeting-alt12:54
*** pradk has joined #openstack-meeting-alt12:55
*** ccamacho|lunch is now known as ccamacho12:55
*** reldan has joined #openstack-meeting-alt12:56
*** thomnico has quit IRC12:56
*** kei_yama has quit IRC12:56
*** dizquierdo has joined #openstack-meeting-alt12:56
*** jseiler_ has quit IRC12:56
*** yamamoto has quit IRC12:56
*** yamamoto has joined #openstack-meeting-alt12:57
*** dprince has quit IRC12:57
*** ninag_ has joined #openstack-meeting-alt12:58
*** ijw has quit IRC12:59
*** amotoki has quit IRC12:59
*** apetrich has quit IRC12:59
*** ninag__ has joined #openstack-meeting-alt13:00
*** _gryf has joined #openstack-meeting-alt13:00
*** jschwarz_ has joined #openstack-meeting-alt13:01
*** jschwarz has quit IRC13:01
*** yamamoto has quit IRC13:02
*** ninag has quit IRC13:02
*** tonytan4ever has joined #openstack-meeting-alt13:02
*** ninag_ has quit IRC13:03
*** edwardb has joined #openstack-meeting-alt13:04
*** dukhlov has quit IRC13:06
*** ddieterly has quit IRC13:07
*** egallen has joined #openstack-meeting-alt13:08
*** edwardb has quit IRC13:08
*** dshakhray has quit IRC13:08
*** kinrui is now known as fungi13:09
*** egallen has left #openstack-meeting-alt13:09
*** bryan_att has joined #openstack-meeting-alt13:09
*** edwardb has joined #openstack-meeting-alt13:09
*** nelsnelson has joined #openstack-meeting-alt13:11
*** elmiko_ is now known as elmiko13:11
*** reedip_ has joined #openstack-meeting-alt13:12
*** yamamoto has joined #openstack-meeting-alt13:13
*** edwardb has quit IRC13:14
*** tonytan_brb has joined #openstack-meeting-alt13:16
*** ninag has joined #openstack-meeting-alt13:16
*** Tal2 has joined #openstack-meeting-alt13:16
*** ninag_ has joined #openstack-meeting-alt13:17
*** tonytan4ever has quit IRC13:19
*** amotoki has joined #openstack-meeting-alt13:19
*** ninag__ has quit IRC13:19
*** zhurong has joined #openstack-meeting-alt13:20
*** ninag has quit IRC13:21
*** cknight has joined #openstack-meeting-alt13:23
*** ndipanov has quit IRC13:23
*** tonytan_brb has quit IRC13:24
*** tinbar has joined #openstack-meeting-alt13:24
*** ndipanov has joined #openstack-meeting-alt13:25
*** xyang1 has joined #openstack-meeting-alt13:26
*** amitgandhinz has joined #openstack-meeting-alt13:29
*** sayalilunkad has joined #openstack-meeting-alt13:30
*** shadower is now known as shadower_13:31
*** shadower_ is now known as shadower13:32
*** shadower is now known as shadower_13:32
*** jschwarz_ has quit IRC13:33
*** shadower_ is now known as shadower13:33
*** EricGonczer_ has joined #openstack-meeting-alt13:33
*** amotoki has quit IRC13:34
*** f1ller has quit IRC13:35
*** f1ller has joined #openstack-meeting-alt13:37
*** merooney has joined #openstack-meeting-alt13:40
*** amotoki has joined #openstack-meeting-alt13:40
*** nelsnelson has quit IRC13:41
*** fnaval_ has joined #openstack-meeting-alt13:41
*** numans has quit IRC13:42
*** zeih has quit IRC13:43
*** zeih has joined #openstack-meeting-alt13:43
*** moshele has joined #openstack-meeting-alt13:44
*** fnaval has quit IRC13:45
*** jaypipes has joined #openstack-meeting-alt13:47
*** jschwarz_ has joined #openstack-meeting-alt13:48
*** amotoki has quit IRC13:49
*** ddieterly has joined #openstack-meeting-alt13:51
*** ddieterly is now known as ddieterly[away]13:51
*** ddieterly[away] is now known as ddieterly13:51
*** ddieterly is now known as ddieterly[away]13:52
*** mlavalle has joined #openstack-meeting-alt13:52
jaypipesscheduler meeting anyone?13:52
moshelehi13:53
jaypipeshi moshele :)13:53
*** cknight has quit IRC13:53
*** derekh is now known as derekh_afk13:53
*** ddieterly[away] is now known as ddieterly13:54
mlavallejaypipes: yes, me13:54
*** mriedem has joined #openstack-meeting-alt13:55
*** dane_leblanc has joined #openstack-meeting-alt13:55
*** tonytan4ever has joined #openstack-meeting-alt13:55
*** ijw has joined #openstack-meeting-alt13:55
*** tfukushima has joined #openstack-meeting-alt13:56
*** anilvenkata has quit IRC13:56
*** tfukushima has quit IRC13:57
*** Alex_Stef has quit IRC13:57
Yingxinhey13:58
*** piet has quit IRC13:58
*** amotoki has joined #openstack-meeting-alt13:59
jaypipesevening Yingxin13:59
Yingxinjaypipes: good morning13:59
*** sarafraj has joined #openstack-meeting-alt14:00
*** ijw has quit IRC14:00
edleafe#startmeeting nova_scheduler14:01
openstackMeeting started Mon Apr 18 14:01:28 2016 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:01
openstackThe meeting name has been set to 'nova_scheduler'14:01
mriedemo/14:01
mlavalleo/14:01
edleafeJust FYI - having network problems today14:01
Yingxin\o14:01
jaypipes\o/14:01
edleafelots of thunderstorms moving through south texas14:01
sarafrajo/14:02
jaypipesedleafe: excuses, excuses...14:02
edleafeso if I disappear, I'm probably floating away somewhere14:02
*** coreyob_ is now known as coreyob14:02
jaypipesedleafe: :)14:02
mlavalleyeap, poring down in San Antonio14:02
edleafe#topic Meeting reminder14:02
edleafePlease note that there will be no meeting next Monday, as most of us will be in Austin for the OpenStack Summit.14:02
*** openstack changes topic to "Meeting reminder (Meeting topic: nova_scheduler)"14:02
*** reinaldo_ has joined #openstack-meeting-alt14:02
edleafe#topic Specs14:02
*** openstack changes topic to "Specs (Meeting topic: nova_scheduler)"14:02
edleafeJay's spec for Generic Resource pools is on hold until after the summit, but we can still review/comment now, so that when the hold is lifted, it can move forward quickly.14:02
edleafe#link https://review.openstack.org/#/c/300176/14:02
*** zeih has quit IRC14:03
edleafeJay - anything to add on that spec?14:03
* bauzas waves late14:03
_gryfo/14:03
*** dane_leblanc has quit IRC14:03
jaypipes++, same for resource allocation migrations: https://review.openstack.org/#/c/300177/14:03
edleafe#link https://review.openstack.org/#/c/300177/14:03
*** sigmavirus24_awa is now known as sigmavirus2414:03
edleafe#topic Reviews14:03
*** openstack changes topic to "Reviews (Meeting topic: nova_scheduler)"14:03
edleafeAdd name to ResourceProvider object14:03
edleafe#link https://review.openstack.org/#/c/281945/14:03
*** edwardb has joined #openstack-meeting-alt14:03
*** jecarey has joined #openstack-meeting-alt14:04
*** jecarey has quit IRC14:04
edleafeIs cdent here?14:04
jaypipesedleafe: I went ahead and made placeholder blueprints for a bunch of things to visualize the end state of a broken out scheduler. You can see the relationship of blueprints in the compute-node-inventory-newton LP blueprint page here:14:04
jaypipes#link https://blueprints.launchpad.net/nova/+spec/compute-node-inventory-newton14:04
edleafesaw him in -nova earlier14:04
*** jecarey has joined #openstack-meeting-alt14:04
*** sc68cal has quit IRC14:04
Yingxinsaw him replied my spec just now.14:05
edleafejaypipes: thanks, that's a good addition14:05
jaypipesbauzas: you will note in the link above in the dependency graph that I have *not* made the shceduler db filter nor the claims in scheduler a dependency for a broken out scheduler.14:05
*** muralia_ has joined #openstack-meeting-alt14:05
jaypipesI pinged cdent on slack.14:05
jaypipeshe'll be here shortly.14:06
*** ddieterly is now known as ddieterly[away]14:06
bauzasjaypipes: thanks14:06
bauzasjaypipes: I appreciate that :)14:06
YingxinI'm writing the spec for eventually-consistent-host-states, will be based on generic-resource-pools.14:06
*** egallen has joined #openstack-meeting-alt14:06
jaypipesbauzas: I'm still going to push for those, but made them not a dependency ;)14:06
Yingxin#link  https://review.openstack.org/#/c/306844/14:06
bauzasjaypipes: that's totally reasonable14:06
edleafejaypipes: yeah, they are kinda orthogonal to the split14:07
mlavallejaypipes: so code for resource pools will be in this gerrit topic: https://review.openstack.org/#/q/topic:bp/generic-resource-pools,n,z14:07
bauzasjaypipes: like I said multiple times, I'm not sold against or pro the idea, just feeling we need to be clear about what we land and why :)14:07
bauzasjaypipes: so those could be properly evaluated once we get the bits we want :)14:07
jaypipeson the routed networks spec... mlavalle and carl_baldwin I had long talks this weekend with dansmith and share some of his concerns on the spec around what to do in some of the special pre-allocated-pre-associated-ip ports.14:07
jaypipesbauzas: yup, totes.14:07
*** muralia has quit IRC14:08
*** reinaldo_ has quit IRC14:08
mlavallejaypipes: should we meet in Austin o discuss it face to face?14:08
*** dane_leblanc has joined #openstack-meeting-alt14:08
jaypipesmlavalle: erm, maybe? :) that branch/topic is light. there's other things that cdent was working on in a couple other branches.14:08
jaypipesmlavalle: I'll have cdent ping you links.14:08
*** edwardb has quit IRC14:08
*** tonytan4ever has quit IRC14:08
bauzasjaypipes: mlavalle: we will have 80 mins for discussing all the topics about that :)14:09
jaypipesmlavalle: no, on the routed networks spec, I will add comments to the review, you can read, then we can do a high-bw conversation with dansmith and carl_baldwin , ok?14:09
*** sc68cal has joined #openstack-meeting-alt14:09
* dansmith nods14:09
mlavallejaypipes: that's perfect. Thanks14:09
bauzasjaypipes: have you had time to focus on what you want to reach for the 2 sessions ?14:09
jaypipesmlavalle: that way by the time the summit rolls around we won't have too much (hopefully) back and forth that drains the session time.14:09
*** dslevin has joined #openstack-meeting-alt14:09
edleafebauzas: that's later on the agenda14:10
jaypipesbauzas: I was figuring that you and I would just argue about cheese most of that time slot.14:10
edleafeThere are two other reviews that I had marked14:10
bauzasjaypipes: that's a perfect time for that14:10
mlavallejaypipes: yeah. that sounds great. let's have that high bandwidth conversation this week14:10
edleafeAdd ResourcePool and ResourcePoolList objects14:10
edleafe#link https://review.openstack.org/#/c/284963/14:10
*** dslevin has quit IRC14:10
edleafeAdd Allocation and AllocationList objects14:10
edleafe#link https://review.openstack.org/#/c/282442/14:10
mriedemmlavalle: jaypipes: i expect routed networks to come up in the nova/neutron session on wed at the summit too14:10
*** gfidente has joined #openstack-meeting-alt14:10
*** nkrinner has quit IRC14:10
*** gfidente has left #openstack-meeting-alt14:11
mriedembut would be best to have that mostly ironed out beforehand14:11
jaypipesedleafe: yeah, that second one is for the resource-providers-allocations blueprint, which migrates usage data to the allocations table.14:11
mlavallemriedem: ++14:11
jaypipesyup, ++14:11
bauzas++14:11
*** dslevin has joined #openstack-meeting-alt14:11
edleafeagreed, the sessions always seem too short14:11
bauzasmlavalle: I also heard of a notion of QoS from Neutron to send to Nova, right?14:12
jaypipesbauzas: I've been chatting with ajo on that one.14:12
bauzasso we could filter based on those metrics AFAICS14:12
bauzasokay14:12
mlavallebauzas: ajo is the one to talk about that14:12
bauzasfair enough14:12
ajoji14:12
ajohi14:13
jaypipesbauzas: the routed networks is the higher priority use case at the moment, from what I can tell, but I thinkt he QoS requirements can be easily met by the generic-resource-pools functionality as well.14:13
*** snackewm has quit IRC14:13
bauzascool then14:13
ajomy only worry, is, that for what we were talking on the mail list14:13
ajowe end up adding another call to the neutron API,14:13
*** eranra has quit IRC14:13
ajoto translate a port id, to "resource usages"14:13
bauzas*to* the Neutron API ?14:13
ajobauzas, fron the port dictionary, you can't know exactly how much resources (BW in this case) is using14:14
ajobauzas, that's tied to the QoS policy the port is attached to14:14
bauzasI was seeing neutron updating us the resource information14:15
mriedemajo: what's the alternative?14:15
ajoso you can either call neutron qos, grab the policy, and make your own interpretation (in that case you need to tightly couple nova to the knowledge of that)14:15
jaypipesbauzas: as for the summit session, I plan to focus a good 30 minutes on getting a gameplan together for aligning when the quantitative and qualitative sides of the scheduler equation will meet. Right now, alex_xu, claudiub and a few others have been working on the qualitative side (host capabilities and other proposals) and obviously we've been focused on the resource amounts (quantitative) side. we need to ensure we understand when the two14:15
jaypipes sides will be aligned.14:15
ajoor..14:15
*** cknight has joined #openstack-meeting-alt14:15
bauzaswhat the semantics of the resource usage is not something the scheduler should know14:15
ajothe other option, is asking neutron to translate that object into "resource consumptions from you"14:15
ajobut14:15
*** nelsnelson has joined #openstack-meeting-alt14:15
ajothat defeats the original thinking of... "let's avoid scheduler calling other projects via API"14:15
ajois my only worry14:15
bauzasjaypipes: I agree with that, that's a good point14:15
edleafeOK, any other reviews to note?14:16
*** ski3 has joined #openstack-meeting-alt14:16
edleafemoving on...14:16
edleafe#topic Summit Schedule14:16
*** openstack changes topic to "Summit Schedule (Meeting topic: nova_scheduler)"14:16
ajojaypipes, I had this thought just today, I will translate it to the mail list for further discussion14:17
bauzasajo: what I'm feeling is that neutron should send us a quantitative amount of resources to pick from, but what the resources are is totally blind to the scheduler, hence not needing a callback14:17
*** pgadiya has quit IRC14:17
jaypipesajo: ++14:17
edleafe#undo14:17
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x9a1ea50>14:17
*** fnaval_ has quit IRC14:17
ajobauzas, but it's nova who creates the port, or grabs the port via ID... we can't send you all the info related to ports in advance, but, ok let's keep discussing14:18
*** tellesnobrega_af is now known as tellesnobrega14:18
jaypipesajo: yeah, let's save that for a ML thread, cool?14:19
bauzasajo: jaypipes: +114:19
edleafeYes, let's continue that discussion for email14:19
edleafejink!14:19
edleafejinx, even14:19
ajo+114:19
edleafe#topic Summit Schedule14:19
ajothank you guys14:19
*** openstack changes topic to "Summit Schedule (Meeting topic: nova_scheduler)"14:19
edleafeWe have two 40-minute sessions that start Wed. at 9am14:20
edleafejaypipes: anything else to add on your ideas for those slots?14:20
bauzassome great anonymous created the session etherpads :)14:20
edleafebauzas: link?14:20
bauzasI guess it's either mriedem or sdague14:20
bauzasedleafe: sure, once the summit schedule website will make me happy14:21
jaypipesedleafe: I had a nice hangout with timhinrichs about the policy scheduler proposal. He has abandoned that and based on our chat reworking a few things. I'd like to take 10-15 minutes at the end of the sessions to summarize long-term plans in the scheduler space.14:21
edleafebauzas: that'll never happen :(14:21
bauzashttps://www.openstack.org/summit/austin-2016/summit-schedule/events/9087?goback=114:21
bauzaswhich points to https://etherpad.openstack.org/p/newton-nova-scheduler14:21
mriedemthe nova summit etherpads are here https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Nova14:21
mriedemthey are mostly bare14:21
mriedemand we need to start filling them in,14:21
jaypipesmriedem: will do this week, promise.14:22
mriedemwhich if it's left to me, i'm going to just mostly copy the contents from the ideas etherpad14:22
edleafe#link https://etherpad.openstack.org/p/newton-nova-scheduler14:22
edleafe#link https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Nova14:22
bauzasjaypipes: cool, I appreciate discussing on leaving a bit of discussion for something else than resource-* :p14:22
edleafemriedem: huh, I thought you would have filled the sessions with obscure 80s music references14:23
bauzass/discussing on//14:23
jaypipeshehe14:23
*** ddieterly[away] is now known as ddieterly14:23
bauzasor my brain would litterally explose14:23
bauzas:p14:23
*** dshakhray has joined #openstack-meeting-alt14:23
edleafe#action jaypipes to fill out etherpad for scheduler discussion items14:23
jaypipesbauzas: added a TODO for you in the etherpad.14:24
bauzashah14:24
*** ddieterly is now known as ddieterly[away]14:24
bauzasI'm pretty sure I couldn't bring cheese with me14:24
bauzasor I would get kicked-off the border by the TSA guys :p14:24
mriedembtw the ideas etherpad is here https://etherpad.openstack.org/p/newton-nova-summit-ideas14:24
mriedem#link original newton summit session ideas etherpad https://etherpad.openstack.org/p/newton-nova-summit-ideas14:25
edleafebauzas: roquefort FTW!14:25
*** ajmiller has joined #openstack-meeting-alt14:25
edleafeSooooo... anything else to discuss about the summit?14:26
jaypipesnot from em.14:26
jaypipesme.14:26
YingxinPossible to add discussing about shared-state-scheduler?14:26
bauzasI was about to discuss a bit of the ReqSpec14:26
bauzasbut that's a bit consensual14:26
bauzas(basically passing it everywhere)14:26
bauzasso, it's not really a huge deal14:26
mosheleis it possible discuss to with Device Capabilities https://review.openstack.org/#/c/286073/ ?14:27
jaypipesYingxin: you will be in Austin?14:27
*** ddieterly[away] is now known as ddieterly14:27
*** rsyed has quit IRC14:27
edleafemoshele: that's next14:27
Yingxinjaypipes: yes14:27
jaypipesYingxin: cool, I will add it to the schedule14:27
edleafeYes, I'd like to hear more about shared-state scheduler14:27
Yingxinjaypipes: thanks14:27
Yingxinglad to meet you f2f14:27
jaypipesditto14:28
bauzaswhat I'd like is to identify the timeline we'd get for the changes we're going to introduce14:28
_gryfi'd like to discuss about not trivial resources14:28
*** rsyed has joined #openstack-meeting-alt14:28
_gryflike fpga or gpus14:28
edleafeheh, every time I try to type 'schedule', I end up adding an 'r' at the end14:28
bauzas_gryf: I would leave that for either the performance VM discussion or rather the friday timeslot14:28
mriedem_gryf: that will probably come up in the performance VMs session on wed14:28
mriedem++14:29
_gryfbauzas, oh, right :)14:29
mriedemi really really don't want the 2 scheduler sessions bogged down in far out new features14:29
_gryfmriedem, ++14:29
mriedemwhen we already have a large backlog14:29
bauzasand we wouldn't have time to discuss that property14:29
bauzasproperly (sorry, fat fingers)14:29
edleafeWe can continue the session ideas on the etherpad and/or in -nova14:30
edleafe#topic Open discussion14:30
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:30
edleafeOnly one added to the agenda: Scheduling with Device Capabilities14:30
edleafe#link https://review.openstack.org/#/c/286073/14:30
edleafemoshele: you're up14:30
*** tfukushima has joined #openstack-meeting-alt14:30
bauzasthat reminds me some spec from claudiub14:31
mosheleyes so I want to address the qualitative sides14:31
*** lbragstad_ is now known as lbragstad14:31
bauzasright, that's not something we consume14:31
mosheleof resource to be able to build like framework so it will be easy to add device/resource to nova14:31
mosheleso the idea it to create table which all the devices with all the qualitative capabilities14:33
jaypipesmoshele: the *very* first step I'd like to see from you and others in this space (alex_xu, malini bhandaru, etc) is to have a *single* agreed-upon set of codes that describe capabilities of things.14:33
jaypipesmoshele: there has been a suggestion in the past to use CIM, which was roundly rejected, though using the bottom-level string codes within some CIM namespaces might be doable for describing things like CPU features. What need this otherwise there will be no portability or interoperability between clouds running OpenStack.14:34
moshelejaypipes: so I am familiar with nic and PCI and I want to make it more generic for all resource14:35
*** ddieterly is now known as ddieterly[away]14:35
jaypipesmoshele: so, to summarize, it's cool to propose a schema or object model for storing such capabilities, but first things first, those capabilities codes need to be standardzed and placed in a library or common consts file.14:35
bauzasjaypipes: moshele: https://review.openstack.org/#/c/222200/ is the spec I was thinking about14:35
*** fnaval has joined #openstack-meeting-alt14:35
jaypipesbauzas: yup, I'm familiar with that one, and alex_xu's proposal that is dependent on it.14:36
bauzasokay14:36
*** jdob has quit IRC14:36
*** jdob has joined #openstack-meeting-alt14:36
*** kebray has quit IRC14:36
*** rsyed is now known as rsyed_away14:37
*** fnaval has quit IRC14:37
jaypipesbauzas: claudiu's spec is more about a discovery API for hypervisor functionality, whereas moshele is more interested in the PCI device capabilities and flags.14:37
bauzasI agree14:37
bauzas(just reading moshele's spec proposal14:37
moshelenot just pci for every device14:37
mosheledevices that we would add in the future as well14:38
edleafejaypipes: good point. Looks like an abstraction needs to be created so we don't keep one-offing these14:38
bauzasbut that's very related to the session I want to discuss in the performance VM session14:38
*** rsyed_away is now known as rsyed14:38
bauzasbecause that PCI tracking is honestly a PITA to me14:38
bauzashttps://etherpad.openstack.org/p/newton-nova-performance-vms14:38
*** ddieterly[away] is now known as ddieterly14:39
johnthetubaguyoh, that what we mean by performance vms then, I did want to go look that up14:39
bauzasjaypipes: I was taking the PCI resource tracking in that session because I was feeling it was requiring a full dedicated session and not polluting the sched sessions14:39
*** kebray has joined #openstack-meeting-alt14:40
*** Guest11043 is now known as redrobot14:40
mosheleI think the PCI problem is  different story  legacy problem, but we should look also for new devices and resources and how to plug them to the scheduler14:40
* bauzas bbiab, just kicking-off my cat's butt14:40
*** tellesnobrega is now known as tellesnobrega_af14:41
moshelelooking on the qualitative sides14:41
jaypipesmoshele: I prioritize cleaning up the cruft we have in the resource tracker and PCI handling code over adding new features around PCI devices.14:41
bauzas++14:41
*** spotz_zzz is now known as spotz14:41
*** cdent has joined #openstack-meeting-alt14:42
jaypipesmoshele: that said, if you can shape your proposal to be about a common, consistent representation of these capabilities (and a library that would allow any service project to agree on what a code for a capability means), I would think that would be a great first step.14:42
jaypipesmoshele: think of it kind of like our discussion around the osinfo library.14:42
mosheleosinfo?14:42
jaypipesmoshele: we needed a place to standardize how we described operating system capabilities and definitions. osinfo was that library (for better or worse, but it was what we decided upon)14:43
moshelejaypipes: can you send me a link to osinfo library14:44
*** fnaval has joined #openstack-meeting-alt14:44
*** jschwarz_ is now known as jschwarz14:45
jaypipesmoshele: sure, gimme a sec14:45
*** merooney has quit IRC14:46
jaypipesmoshele: https://libosinfo.org/ and it is utilized in Nova here: https://github.com/openstack/nova/blob/master/nova/virt/osinfo.py14:46
*** edtubill has joined #openstack-meeting-alt14:47
moshelejaypipes: by the way I am working on fixing the pci code for resize and migration and I saw you proposal of removing the pci.stats module and moving the logic to the scheduler, so this should clean the pci code or there is something else14:47
*** paul-carlton2 has joined #openstack-meeting-alt14:47
jaypipesmoshele: yes, that is my proposal (or most of it). I need to refactor that original spec to include the device.tags mess that ndipanov rightfully brought up in code review and resubmit the spec for Newton.14:47
edleafeAnything else for opens?14:47
*** jdob has quit IRC14:48
Yingxinedleafe: yes14:48
*** jdob has joined #openstack-meeting-alt14:48
edleafeYingxin: go ahead14:48
*** ajmiller_ has joined #openstack-meeting-alt14:48
YingxinAnyone interested in nova scheduler performance profiling, here is an advertisement:14:48
Yingxinhttp://paste.openstack.org/show/494336/14:48
Yingxinfor the summit session14:48
Yingxinedleafe: done14:49
edleafeok14:49
edleafeanything else?14:49
edleafeOr should we return to bug scrubbing?14:49
jaypipesYingxin: wait, this is a conference session or a design summit session?14:49
Yingxinjaypipes: conference session14:50
Yingxinhttps://www.openstack.org/summit/austin-2016/summit-schedule/events/712914:50
jaypipesYingxin: k, I will try my best to attend.14:50
bauzasargh14:50
jaypipesYingxin: I'll sit in the front row and heckle you :P14:50
bauzaspossibly the least possible session to attend14:51
Yingxinjaypipes: :)14:51
jaypipesbauzas: conflict?14:51
bauzasone of the last nova design dessions14:51
jaypipesguh, shit.14:51
bauzasjaypipes: well, I'm just trying to figure out which one in conflict14:51
*** ajmiller has quit IRC14:52
bauzasnow, everyone should know how I hate the new sched website14:52
bauzasplease, please, free us sched.org14:52
edleafebauzas: ++++14:52
bauzasI could even make a donation campaign14:52
*** ajmiller has joined #openstack-meeting-alt14:53
bauzasif that's a cost problem14:53
*** asingh has joined #openstack-meeting-alt14:53
bauzasaaaaand, my browser crashed on trying to get my sched14:53
edleafeI'm sure the foundation can afford a decent schedule app14:53
edleafeAny other topics for Opens?14:54
bauzasyeah, so Yingxin's session is conflicting with the nova-ironic joint session :/14:54
*** korzen__ has joined #openstack-meeting-alt14:54
Yingxinbauzas: I can write a summary to maillist for you14:54
jaypipesbauzas: yeah :(14:54
bauzasYingxin: not needed, it should be recorded14:54
edleafeNow you know why I resist management's insisting on giving talks at a summit14:55
bauzasYingxin: in general, I prefer attending design sessions for the exact reason that conf sessions are recorded while design sessions aren't14:55
*** zhurong has quit IRC14:55
bauzastrying to get the consensus on something you didn't attended is hard14:55
bauzasanyway14:56
*** ajmiller_ has quit IRC14:56
edleafebauzas: yeah, not every agreement is written down14:56
bauzasI enough ranted for today14:56
edleafeok, let's move on14:56
Yingxinbauzas: good suggestion14:56
edleafesee you all (or at least most of you) in Austin next week!14:56
*** ijw has joined #openstack-meeting-alt14:56
edleafe#endmeeting nova_scheduler14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Mon Apr 18 14:57:06 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-04-18-14.01.html14:57
jaypipesindeed :)14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-04-18-14.01.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-04-18-14.01.log.html14:57
bauzasshall I bring some Chartreuse? :)14:57
_gryfbauzas, chaource would be better ;)14:57
edleafeDoes it go well with barbecue?14:57
*** kebray_ has joined #openstack-meeting-alt14:57
edleafe'cause that's all they eat in Texas14:57
*** sshnaidm has quit IRC14:58
edleafe(says the vegetarian Texan)14:58
*** mlavalle has left #openstack-meeting-alt14:58
*** mriedem has left #openstack-meeting-alt14:58
bauzasheh, Chartreuse is an alcohol14:58
bauzaschaource is a cheese14:58
_gryfbauzas, oh14:58
_gryfmy bad14:58
_gryfanyway chaource is my fav14:58
edleafebring 'em both!14:58
_gryffrom french cheese14:58
bauzasokay, I'll see what I can do :)14:59
_gryfbauzas, \o/14:59
*** mhickey has joined #openstack-meeting-alt14:59
*** cdent has left #openstack-meeting-alt14:59
*** ddieterly is now known as ddieterly[away]15:00
*** merooney has joined #openstack-meeting-alt15:00
*** kebray has quit IRC15:00
ihrachys#startmeeting neutron_upgrades15:01
openstackMeeting started Mon Apr 18 15:01:10 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:01
openstackThe meeting name has been set to 'neutron_upgrades'15:01
*** ansmith has joined #openstack-meeting-alt15:01
ihrachyshi everyone!15:01
korzen__hello15:01
sayalilunkadhello15:01
*** moshele has left #openstack-meeting-alt15:01
ihrachysrossella_s:15:02
saisrikihi15:02
ski3hey!15:02
*** ijw has quit IRC15:02
mhickeyHello15:02
rossella_shi all!15:02
*** electrocucaracha has joined #openstack-meeting-alt15:02
pmathhi15:02
asinghHey15:02
ihrachysok. it's nice to see everyone here :) let's roll15:03
ihrachys#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam Agenda (sortof)15:03
*** edwardb has joined #openstack-meeting-alt15:03
*** snackewm has joined #openstack-meeting-alt15:03
ihrachys#topic Summit planning15:03
*** openstack changes topic to "Summit planning (Meeting topic: neutron_upgrades)"15:03
*** korzen has joined #openstack-meeting-alt15:03
rossella_sOS_AUS_RIBF6ZE15:03
ihrachysI remind that we will have a design session that should cover upgrade matters, among other things15:04
*** korzen__ has left #openstack-meeting-alt15:04
rossella_ssorry wrong window15:04
ihrachys#link #link https://etherpad.openstack.org/p/newton-neutron-future-neutron-architecture etherpad15:04
*** ozamiatin has joined #openstack-meeting-alt15:04
*** EricGonc_ has joined #openstack-meeting-alt15:04
ihrachys#topic Actions from the last meeting15:04
*** openstack changes topic to "Actions from the last meeting (Meeting topic: neutron_upgrades)"15:04
ihrachysthe only action we had is "#action ihrachys to talk to armax about bp for ovo work"15:04
ihrachysso I talked to armax, and he agreed we better have a blueprint for ovo work15:05
ihrachysso here you go:15:05
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/adopt-oslo-versioned-objects-for-db15:05
ihrachysplease use the blueprint in commit messages for ovo work from now on15:05
ihrachysexample: https://review.openstack.org/#/c/268274/15:05
ihrachysthough it should probably be 'Partially-Implements'15:05
ihrachysanyway, it should not matter that much15:06
*** doug-fish has joined #openstack-meeting-alt15:06
ihrachysquestions on that one?15:06
ihrachysok, let's move on15:06
*** zhongjun_ has quit IRC15:06
ihrachys#topic Partial Multinode Grenade15:06
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:06
*** ddieterly[away] is now known as ddieterly15:06
ihrachyswe have a patch to enable voting for the existing job:15:07
ihrachys#link https://review.openstack.org/#/c/299843/15:07
*** cinerama` is now known as cinerama15:07
ihrachyssc68cal will need to respin it, he planned to reach me on the matter today.15:07
*** snackewm has quit IRC15:07
*** zhongjun_ has joined #openstack-meeting-alt15:07
ihrachysanother thing is dvr job15:07
ihrachyswhich now is moved into check queue:15:07
ihrachys#link https://review.openstack.org/#/c/299844/15:07
*** snackewm has joined #openstack-meeting-alt15:07
ihrachyskorzen: ^ we may need to track its success rate and consider test coverage.15:08
*** EricGonczer_ has quit IRC15:08
ihrachysthe idea is that eventually it will replace non-dvr flavour15:08
ihrachys#topic Object implementation15:08
korzenihrachys nice:)15:08
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:08
ihrachyson objects front, a lot of progress is done. we are not there yet with huge resources, but we move in the right direction.15:08
ihrachys#link https://review.openstack.org/#/q/topic:ovo+status:open15:09
korzensubnet patch had no reviews :( except for electrocucaracha15:09
electrocucarachaeven when we have the bp, we're going to be using the ovo for topic right?15:09
ihrachyselectrocucaracha: yes, topic is the same15:09
ihrachyskorzen: ack. it's a bad time of the cycle :(15:10
*** edwardb has quit IRC15:10
ihrachysfolks, please review subnet patch when you have spare cycles:15:10
ihrachys#link https://review.openstack.org/26427315:10
rossella_skorzen I will try to review it tomorrow15:10
ihrachysanother thing that should be ready is allowed address pairs:15:10
ihrachys#link https://review.openstack.org/28775615:10
ihrachys(and patches below the dependency stack)15:10
korzenok, thx, I guess we are and will be busy for summit/design15:11
*** tfukushima has quit IRC15:11
*** julim has quit IRC15:11
ihrachysone thing I wanted to run with you15:11
mhickeyihrachys, rossella_s: thanks for picking up allow addr pairs! :-)15:11
ihrachysit turned out that just using netaddr.* is not enough to fulfill our API guarantees15:11
ihrachysmhickey: np15:11
rossella_sihrachys, more details please15:12
ihrachysspecifically, netaddr.* has a bad habit of changing string representation passed into some 'standard' form15:12
ihrachysso when you do str(netaddr.EUI(<mac_address>)15:12
*** Tal2 has quit IRC15:12
ihrachysthe result is not the same as what you originally passed15:12
ihrachysnow, we have API tests that rely on that being the same value15:12
mhickeyihrachys: what is the format?15:12
rossella_sbut you can specify the format15:12
electrocucarachadepends on the version?15:12
*** tonytan4ever has joined #openstack-meeting-alt15:13
ihrachysmhickey: there are multiple ways to represent it, like ff:00:... or ff00ff, or ff:0:...15:13
ihrachysrossella_s: you can specify the format, yes15:13
ihrachysrossella_s: the problem is that you still hardcode it to a specific format then15:13
rossella_sihrachys, right15:13
ihrachysrossella_s: and you should return whatever is valid for netaddr.* that is passed by user15:14
*** merooney has quit IRC15:14
ihrachysrossella_s: so if they pass fffff, you return that; otherwise if they pass ff:ff:, you return ff:ff:. etc.15:14
mhickeyihrachys: ok15:14
ihrachysso, long story short, to make API tests happy, I introduced some smart subclasses for netaddr*15:14
ihrachys#link https://review.openstack.org/#/c/287756/13/neutron/common/utils.py15:14
*** edwardb has joined #openstack-meeting-alt15:14
rossella_sihrachys, if they pass fffff we convert it and then pass back the standard format? how does it work now?15:15
ihrachysthey override __str__ to output whatever was passed into __init__ in the first place15:15
ihrachysrossella_s: currently we don't pass those values thru netaddr.* so it does not affect the format.15:15
*** julim has joined #openstack-meeting-alt15:15
rossella_sihrachys, so currently there's no enforcement on the format15:16
ihrachysrossella_s: currently we allow anything that passes thru netaddr.valid_mac15:16
ihrachyswhich is any random stuff that netaddr can interpret15:16
*** _gryf has left #openstack-meeting-alt15:16
ihrachyshttp://git.openstack.org/cgit/openstack/neutron/tree/neutron/api/v2/attributes.py#n18815:17
rossella_sihrachys, then bear with me...maybe we should change the MACField to do just that15:17
ihrachys^ that's where validation on API level occurs15:17
rossella_sihrachys, let me look at your patch15:17
*** armax has joined #openstack-meeting-alt15:17
*** sarafraj has left #openstack-meeting-alt15:17
*** wangqun has quit IRC15:17
ihrachysrossella_s: well, our field requires netaddr.EUI, so database code already need to initialize it before passing into Field15:18
*** spzala has joined #openstack-meeting-alt15:18
*** amitgandhinz has quit IRC15:18
ihrachysso it's a bit twisted. the point is, I need your eyes on that, it's a bit tricky.15:18
rossella_sihrachys, I am just wondering if it should be of type string in the end + validation15:18
rossella_sihrachys, to mirror what's currently done in the codebase15:19
*** tonytan_brb has joined #openstack-meeting-alt15:19
*** tonytan_brb is now known as tonytan4ever_15:19
mhickeyihrachys: re https://review.openstack.org/#/c/287756/, good work in patch!15:19
ihrachysrossella_s: for IP addresses too?15:20
mhickeyihrachys: will take another look as well..15:20
ihrachysrossella_s: I mean, we will end up with all fields string :)15:20
rossella_sihrachys, just talking out loud15:20
ihrachysrossella_s: sure. I will be glad to see your reviews on the patch. it needs some good eyes.15:21
*** jungleboyj has joined #openstack-meeting-alt15:21
pmathI was hoping to get more reviews on https://review.openstack.org/#/c/304862, savailability zones ovo, looks like I didn't put it on the ovo branch/topic15:21
ihrachyspmath: aye. I changed the topic for you.15:22
pmaththanks15:22
*** pnavarro has quit IRC15:22
ihrachyspmath: please make sure all your patches are using the topic.15:22
pmathk15:22
rossella_sihrachys, anyway I didn't mean to go back to the plain string field. I'd just modify the current MAC field to be less string and to save the string passed after validation15:22
ihrachysI mean, not all, just ovo :)15:22
rossella_sjbr+15:22
rossella_sihrachys, let's keep discussing on the patch15:22
ihrachysI am all for it :) ok, let's move on15:23
*** tonytan4ever has quit IRC15:23
ihrachysone more thing that I stumbled upon for ovo work15:23
korzendoes anybody know when are the milestones for newton?15:23
ihrachyskorzen: http://releases.openstack.org/newton/schedule.html15:24
*** tonytan4ever_ has quit IRC15:24
*** EricGonc_ has quit IRC15:24
ihrachysok, so the thing I stumbled upon is: we need to support advanced pagination/sorting criteria for resources we switch to objects15:25
ihrachysand current get_objects() API does not allow for that15:25
ihrachysI have a patch for just that at:15:25
ihrachys#link https://review.openstack.org/30005515:25
ihrachysI would be glad to see more eyes on that one15:25
ihrachysspecifically, it blocks adoption for subnetpool15:25
*** mtanino has joined #openstack-meeting-alt15:25
ihrachysbut I believe other resources will need it as well15:26
ihrachysone thing to note is that test coverage for the features [sorting + pagination] is non-existent15:26
rossella_sihrachys, thanks for raising this point and for working on it!15:26
ihrachysso we will need to introduce api test coverage before touching that15:26
*** armax has quit IRC15:26
ihrachysI have a first set of tests for networks at:15:26
ihrachys#link https://review.openstack.org/30627215:26
*** EricGonczer_ has joined #openstack-meeting-alt15:27
ihrachysI tried to write ^ in a way that would be easily extensible to other resources15:27
ihrachysso... I just beg for reviews :)15:27
*** shadower has quit IRC15:27
ihrachys#topic Next meetings15:28
*** openstack changes topic to "Next meetings (Meeting topic: neutron_upgrades)"15:28
ihrachysfor the next meetings, we will need to skip the next week and the week after it15:28
ihrachysI will post an email with the info to openstack-dev@ after the meeting15:28
korzenihrachys, can we add this to the Backlog in wiki page? I guess that giving an example and then point people where to follow the OVO implementation would be helpfull15:28
ihrachys#action ihrachys to cancel next meetings in openstack-dev@15:29
ihrachyskorzen: this == ?15:29
*** armax has joined #openstack-meeting-alt15:29
korzenthis == API tests, OVO API and OVO core Neutron code adoption15:29
*** ddieterly is now known as ddieterly[away]15:29
ihrachysnot sure I follow the suggestion.15:30
ihrachysyou mean mention those patches on the wiki?15:30
korzenfor example I'm working on subnet and network OVO and I guess that there are a lot of steps to be done in order to fully adopt the objects15:30
ihrachysoh, ok, general check list15:31
ihrachysI will do it15:31
korzenwhat does mean to integrate the object in Neutron core15:31
ihrachys#action ihrachys to update wiki page with the check list for object adoption (object, database access code, API test coverage, ...)15:31
*** matrohon has quit IRC15:31
ihrachysso, speaking of the next meetings...15:32
*** numans has joined #openstack-meeting-alt15:32
ihrachysthe first meeting we will have after the summit, I will be on PTO15:32
ihrachysanyone willing to step in and handle the chair burden?15:32
ihrachysalternatively, we just cancel. but I suspect that it may be not ideal for the team.15:32
electrocucarachaPTO?15:32
korzenPTO?15:33
saisrikiPaid Time off15:33
ihrachyssorry. PTO == vacation15:33
mhickeyleave15:33
mhickeyHoliday in Ireland! :-)15:33
ihrachyskorzen: rossella_s: anyone of you willing to run that one?15:33
korzenI can run15:33
rossella_sihrachys, I can too15:33
electrocucarachaI'll be on Paternity leave 8 weeks starting on May 915:33
*** armax has quit IRC15:33
ihrachysit will be May 9th15:33
*** amrith is now known as _amrith_15:33
*** reed has quit IRC15:34
*** reed has joined #openstack-meeting-alt15:34
ihrachyselectrocucaracha: oh. congrats ;)15:34
mhickeyelectrocucaracha: Congrats! :-)15:34
rossella_selectrocucaracha, congrats!!15:34
electrocucarachathanks ihrachys and mhickey15:34
electrocucarachaand rossella_s15:34
sayalilunkadI will also be off for two weeks after the summit15:34
*** woodster_ has joined #openstack-meeting-alt15:34
ihrachyshm. do we have enough people to have a meeting then? should we then cancel indeed?15:34
*** e0ne has quit IRC15:34
ihrachysoh sorry15:35
rossella_sihrachys, it seems it's jst me and korzen15:35
ihrachysrossella_s: you can run a short one. :)15:35
ihrachysyou decide, I don't mind.15:35
mhickeyrossella_s, korzen: will you be in form after long haul flight?!15:35
ihrachysrossella_s: it's not the first week after summit.15:35
korzenin 9th May?15:35
ihrachyssorry.15:35
ihrachysmy fingers type wrong letters.15:36
ihrachyskorzen: yes, that's the date.15:36
rossella_sok so, let's have a meeting, even a short one15:36
ihrachysok, cool15:36
ihrachys#topic Open discussion15:36
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:36
ihrachysanything else to discuss?15:36
*** beslemon has joined #openstack-meeting-alt15:36
korzenmhickey 9th May I will be a week after flying ;)15:36
*** EricGonczer_ has quit IRC15:36
mhickeykorzen: my bad. yu maybe in the drunk tank though! :)15:37
saisrikiI want to understand how to handle mixin classes for porting to OVO? Any general steps to follow?15:37
ihrachyssaisriki: what specifically?15:37
korzenmhickey I'm planning to clean my house and garage the after I arrive in Poland :D15:38
ihrachyssaisriki: for allowed address pairs, it was quite smooth15:38
saisrikiI was trying to look at extra_routes for example15:38
*** EricGonczer_ has joined #openstack-meeting-alt15:38
ihrachyssaisriki: is it part of some other object?15:38
saisrikiIt is part of RouterRoute #link https://github.com/openstack/neutron/blob/master/neutron/db/extraroute_db.py15:38
*** dizquierdo has quit IRC15:39
*** tremble has quit IRC15:39
ihrachyssaisriki: I think it's similar.15:39
ihrachyssaisriki: see: https://review.openstack.org/#/c/287756/13/neutron/db/allowedaddresspairs_db.py15:39
ihrachysbasically, you just switch every instance of direct model usage to the object interface.15:40
*** kevo has quit IRC15:40
saisrikiyes. I will try and follow the allowed address pairs15:40
ihrachysthat's assuming you have an object for RouterRoute and don't embed it into the Router itself.15:40
ihrachysif that's the latter case, I don't think we had it before, so we would need more thought.15:40
saisrikiihrachys: ok15:41
ihrachysok, cool, I hope that covers your needs for now.15:41
ihrachysanything else?15:41
ihrachysok, let's call it a day. see some of you on the summit, else in several weeks!15:43
ihrachys#endmeeting15:43
korzenI hope to see you all in Austin and have a good design discussions!15:43
mhickeyihrachys: sure will15:43
mhickeysee you all there.15:43
sayalilunkadsee you all, bye!15:43
korzenbye15:43
mhickeybye15:43
saisrikibye15:43
electrocucarachabyt15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:43
openstackMeeting ended Mon Apr 18 15:43:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-04-18-15.01.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-04-18-15.01.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-04-18-15.01.log.html15:43
*** gyee has joined #openstack-meeting-alt15:43
*** Akis_ has joined #openstack-meeting-alt15:44
*** armax has joined #openstack-meeting-alt15:44
*** vgridnev has quit IRC15:44
*** vgridnev has joined #openstack-meeting-alt15:45
*** ddieterly[away] is now known as ddieterly15:46
*** markmcclain has quit IRC15:47
*** electrocucaracha has left #openstack-meeting-alt15:47
*** vgridnev has quit IRC15:47
*** markmcclain has joined #openstack-meeting-alt15:47
*** ddieterly is now known as ddieterly[away]15:47
*** Sukhdev has joined #openstack-meeting-alt15:47
*** akiskourtis has quit IRC15:48
*** harlowja_at_home has joined #openstack-meeting-alt15:49
*** Leom has quit IRC15:50
*** dprince has joined #openstack-meeting-alt15:50
*** Leo_ has joined #openstack-meeting-alt15:51
*** jschwarz has quit IRC15:51
*** egallen has quit IRC15:53
*** tonytan4ever has joined #openstack-meeting-alt15:53
*** sshnaidm has joined #openstack-meeting-alt15:53
*** blogan_ is now known as blogan15:53
*** Leom has joined #openstack-meeting-alt15:54
*** paul-carlton2 has quit IRC15:55
*** mikelk has quit IRC15:56
*** egallen has joined #openstack-meeting-alt15:57
*** Leo_ has quit IRC15:57
*** stingaci has joined #openstack-meeting-alt15:57
*** ijw has joined #openstack-meeting-alt15:58
*** johnsom has joined #openstack-meeting-alt15:59
*** ddieterly[away] is now known as ddieterly15:59
*** ddieterly has quit IRC15:59
harlowja_at_home#startmeeting oslo16:00
openstackMeeting started Mon Apr 18 16:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is harlowja_at_home. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
openstackThe meeting name has been set to 'oslo'16:00
*** ddieterly has joined #openstack-meeting-alt16:00
johnsomo/16:00
harlowja_at_homehowdy folks, let's see if anyone shows up today :)16:00
*** _amrith_ is now known as amrith16:00
*** ddieterly has quit IRC16:00
jecareyo/16:00
harlowja_at_homecourtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims, dougwig, e0ne, flaper87, garyk, haypo,16:00
harlowja_at_homecourtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps16:00
harlowja_at_homecourtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb, Nakato16:00
bknudsonhi16:00
rpodolyakao/16:00
ozamiatino/16:00
stevemaro/16:00
harlowja_at_homehi hi, i'm guessing light attendance today (because summit) but let's see16:00
redroboto/16:00
*** kgiusti has joined #openstack-meeting-alt16:00
stevemarharlowja_at_home: ya never know !16:01
*** kebray_ has quit IRC16:01
harlowja_at_homestevemar, agreed, will wait a few seconds to see who all shows :-P16:01
bknudsontake a week-long nap to prepare for the summit16:01
johnsomI bet it will be a lot lighter next week....16:01
harlowja_at_home;)16:01
stevemarjohnsom: yeah, probably :)16:01
harlowja_at_homeit will be keynote or something next time around, ha16:02
harlowja_at_home(next week at this time)16:02
harlowja_at_homeok, guess we should do some meeting stuffs16:02
harlowja_at_home#topic Red flags for/from liaisons16:02
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:02
harlowja_at_homeso i guess keystone + oslo.log had some issues16:02
harlowja_at_homeor that's what i saw from dims16:02
bknudsonI haven't had a chance to look at it.16:03
stevemarharlowja_at_home: yep, ajeager summed it up on the ML16:03
johnsomNothing here, though I am still interested in a taskflow release16:03
harlowja_at_homestevemar, agreed, seems like a few options to resolve that, babel can release, oslo.i8ln can16:03
stevemarthere were a few factors at play, keystone wasn't respecting upper constraints, but oslo.log was pulling in a new version of babel, via oslo.i18n16:03
jungleboyjo/16:03
bknudsonI proposed a change to debtcollector to get keystoneclient, etc., docs generating correctly: https://review.openstack.org/#/c/305489/16:03
jungleboyjharlowja_at_home: No flags from Cinder.16:04
harlowja_at_homebknudson, thx16:04
harlowja_at_homejungleboyj, thx16:04
*** andymaier has joined #openstack-meeting-alt16:04
*** salv-orlando has joined #openstack-meeting-alt16:04
*** ijw has quit IRC16:04
ihrachysno flags from neutron. though I saw some failure in oslo master jobs that may be related to late changes in oslo.versionedobjects. I would need to look into logs.16:04
harlowja_at_homehmmm16:05
*** Guest30394 has quit IRC16:05
harlowja_at_homeihrachys, thx, let's investigate that before i do much of any release proposals16:05
harlowja_at_home#topic Release proposals16:05
*** openstack changes topic to "Release proposals (Meeting topic: oslo)"16:05
*** raginbajin has quit IRC16:05
harlowja_at_homeso i've made a little script to make a bunch of release proposals automatically, so i'll probably start uploading that to the release repo soon16:05
*** gyee has quit IRC16:06
*** andymaier has quit IRC16:06
harlowja_at_homei just don't want to start releasing to much before the summit and when people aren't around, lol16:06
harlowja_at_hometool @ https://review.openstack.org/#/c/306648/16:06
ihrachysnice of you :)16:06
harlowja_at_homeihrachys, ya, i'm all about the niceness16:06
*** salv-orl_ has quit IRC16:06
harlowja_at_homeso i might just run that script/tool and upload the change but will put WIP on it, because of summit16:06
harlowja_at_homeand people can let me know if they want me to split off any release change from that bigger release16:07
*** paul-carlton2 has joined #openstack-meeting-alt16:07
harlowja_at_homejohnsom, i think u qualify for that :)16:07
harlowja_at_homesince i think certain releases will be ok this week, just i think other ones have alot of changes backlogged and i'd rather not this week ;)16:07
johnsomYeah, I can wait until after the summit though.  It's not a burning issue, just helps with our docs16:08
*** Swami has joined #openstack-meeting-alt16:08
harlowja_at_homek16:08
ihrachysharlowja_at_home: yeah, just validated, new o.vo breaks neutron test. will look right now.16:08
harlowja_at_homea few like debtcollector with bknudson changes and taskflow probably are ok16:08
harlowja_at_homeihrachys, thx16:08
kgiustiI've got a minor 'tweak' to liberty stable https://review.openstack.org/#/c/307207/16:08
harlowja_at_homekgiusti, cool16:08
kgiustimaybe too little too late.16:09
kgiustithere's been confusion about what exactly happens to qpidd in mitaka16:09
harlowja_at_home:)16:09
bknudsonsince we've got a stable/mitaka that would put stable/liberty in the security-fixes-only mode16:09
harlowja_at_homeah16:09
*** egallen has left #openstack-meeting-alt16:09
ihrachysbknudson: not really. it's High+ bugs16:09
kgiusti:(16:09
bknudsonaka phase 216:09
bknudsonhttp://docs.openstack.org/project-team-guide/stable-branches.html16:09
ihrachysbknudson: CVE only is N-216:10
ihrachys"Phase II (6-12 months): Only critical bugfixes and security patches are acceptable"16:10
*** nadya has quit IRC16:10
*** raginbajin has joined #openstack-meeting-alt16:10
*** mickeys has joined #openstack-meeting-alt16:10
*** zzzeek has joined #openstack-meeting-alt16:11
kgiustidims et.al. are doing a 'what's new in oslo' preso at summit16:11
zzzeek\o16:11
harlowja_at_homekgiusti, oh nice16:11
kgiustiI wonder how much it would take in kickbacks to get him to talk a bit about amqp1016:11
harlowja_at_home#topic Summit preparation(s)16:11
*** openstack changes topic to "Summit preparation(s) (Meeting topic: oslo)"16:11
kgiustiat least let people know there's still support for qpidd in mitaka16:11
harlowja_at_homeso that's a good point, what else are people going to be doing at the summit that is possibly oslo related ?16:12
harlowja_at_homebesides the oslo sessions :-P16:12
harlowja_at_home#link http://lists.openstack.org/pipermail/openstack-dev/2016-April/092423.html (oslo stuffs)16:12
kgiustimy preso is wait-listed, FWIW16:12
harlowja_at_home:(16:13
*** beslemon has quit IRC16:13
harlowja_at_homei'm also looking for folks to take lead on some of the sessions in https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Oslo16:13
*** sridharg has quit IRC16:13
johnsomLBaaS/Octavia is presenting, but I don't think we plan to talk much about taskflow this time.16:13
harlowja_at_homeeach one of those etherpads i put a little template format in (it'd be nice to expand it a little)16:13
harlowja_at_homeany volunteers to fill some of those out ;)16:14
harlowja_at_homei'll fill out the ones that people don't (eventually, ha)16:14
zzzeekdoes anyone want to talk about oslo.db stuff16:14
kgiustiI've slapped a little verbage on this one: https://etherpad.openstack.org/p/newton-oslo-messaging-drivers16:14
harlowja_at_homezzzeek, at the summit or here?16:14
zzzeekat the summit16:14
harlowja_at_homesure16:14
harlowja_at_homei'm all for talking about it16:14
harlowja_at_homewhat do we want to talk about :)16:14
* zzzeek doesnt have much to talk about :) but can answer questions16:14
* rpodolyaka too :)16:14
harlowja_at_homewe should have a part of the dev lounge called 'oslo IT support'16:15
zzzeekrpodolyaka: you coming ?16:15
harlowja_at_homewe can get a desk from somewhere and have someone doing 'oslo q/a'16:15
* harlowja_at_home only sort of joking, lol16:15
rpodolyakayeah, will be there16:17
zzzeekrpodolyaka: great16:17
jungleboyj:-)  Just reboot.  THat fixes everything.16:17
harlowja_at_home;)16:17
harlowja_at_hometurn it on and off again, lol16:17
bknudsondo I have to get a session just to get the engine? http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/sql/migration_helpers.py#n17816:17
dmitrymere doing anything something beside Oslo design sessions - I am going to attend Operators sessesions related to messaging16:17
harlowja_at_homedmitryme, cool16:17
dmitrymeI guess it might turn into messaging Q&A session :-)16:17
*** piet_ has joined #openstack-meeting-alt16:17
harlowja_at_home:)16:17
*** neelashah has quit IRC16:17
rpodolyakabknudson: not necessary, https://specs.openstack.org/openstack/oslo-specs/specs/kilo/make-enginefacade-a-facade.html#core-connection-methods16:17
harlowja_at_homeok, so i guess if folks have any oslo or neat sessions, feel free to let others in #openstack-oslo know so that some of us can be show up and heckle (and/or be supportive)16:18
*** tinbar has quit IRC16:18
harlowja_at_home#topic Stuck reviews and/or specs16:18
*** openstack changes topic to "Stuck reviews and/or specs (Meeting topic: oslo)"16:18
harlowja_at_homeanything that folks here should be aware of to help review16:18
*** Kiall has quit IRC16:18
harlowja_at_homeguess everyone preparing for the summit then, lol16:19
harlowja_at_homemore slides, less code, lol16:19
*** sgotliv_ has quit IRC16:20
harlowja_at_home#topic Open discussion16:21
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:21
harlowja_at_homeanything else that people want to bring up16:21
harlowja_at_homeotherwise i guess we will all see everyone in austin (for those who are going, for those who are not we will virtually see u)16:22
*** scheuran has quit IRC16:22
*** Kiall has joined #openstack-meeting-alt16:22
*** amrith is now known as _amrith_16:23
*** enriquetaso has joined #openstack-meeting-alt16:23
harlowja_at_homeok, anything else from folks?16:23
harlowja_at_homespeak now or forever hold your peace :-P16:24
* harlowja_at_home wonders if a netsplit happened, because its oddly quiet now, lol16:25
kgiustizzzZZZZZzzzzz....16:25
harlowja_at_homelol16:25
*** markmcclain has quit IRC16:25
*** stingaci has quit IRC16:25
harlowja_at_homeok, i guess we'll see everyone next week :-P16:25
*** markmcclain has joined #openstack-meeting-alt16:25
kgiustisee ya16:25
harlowja_at_home#endmeeting16:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:26
openstackMeeting ended Mon Apr 18 16:26:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-04-18-16.00.html16:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-04-18-16.00.txt16:26
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-04-18-16.00.log.html16:26
*** stingaci has joined #openstack-meeting-alt16:26
*** kgiusti has left #openstack-meeting-alt16:26
*** johnsom has left #openstack-meeting-alt16:26
*** harlowja_at_home has quit IRC16:26
*** piet_ has quit IRC16:26
*** Kiall has quit IRC16:27
*** vilobhmm11 has joined #openstack-meeting-alt16:27
*** korzen has quit IRC16:28
*** ozamiatin has quit IRC16:29
*** vgridnev has joined #openstack-meeting-alt16:29
*** spotz is now known as spotz_zzz16:29
*** tonytan_brb has joined #openstack-meeting-alt16:29
*** fnaval has quit IRC16:31
*** spotz_zzz is now known as spotz16:32
*** tonytan4ever has quit IRC16:32
*** korzen has joined #openstack-meeting-alt16:35
*** neelashah has joined #openstack-meeting-alt16:35
*** fnaval has joined #openstack-meeting-alt16:36
*** ihrachys has quit IRC16:37
*** ccamacho has quit IRC16:38
*** reldan has quit IRC16:38
*** Kiall has joined #openstack-meeting-alt16:38
*** korzen has quit IRC16:39
*** derekh_afk is now known as derekh16:41
*** rcernin has quit IRC16:43
*** Kiall has quit IRC16:43
*** Kiall has joined #openstack-meeting-alt16:44
*** ccamacho has joined #openstack-meeting-alt16:46
*** reedip_ has quit IRC16:47
*** derekh has quit IRC16:48
*** vgridnev_ has joined #openstack-meeting-alt16:52
*** davideagnello has joined #openstack-meeting-alt16:54
*** mhickey has quit IRC16:57
*** sputnik13 has joined #openstack-meeting-alt16:57
*** ijw has joined #openstack-meeting-alt17:00
*** mickeys has quit IRC17:00
*** clopez has quit IRC17:00
*** egallen has joined #openstack-meeting-alt17:00
*** ccamacho has quit IRC17:00
*** mickeys has joined #openstack-meeting-alt17:00
*** rossella_s has quit IRC17:03
*** banix has joined #openstack-meeting-alt17:03
*** rossella_s has joined #openstack-meeting-alt17:04
*** baoli_ has quit IRC17:04
*** mickeys has quit IRC17:05
*** ijw has quit IRC17:05
*** egallen has left #openstack-meeting-alt17:06
*** kevo has joined #openstack-meeting-alt17:07
*** reldan has joined #openstack-meeting-alt17:08
*** amitgandhinz has joined #openstack-meeting-alt17:09
*** kfarr has joined #openstack-meeting-alt17:10
*** Alex_Stef has joined #openstack-meeting-alt17:10
*** tonytan_brb has quit IRC17:10
*** zzzeek has left #openstack-meeting-alt17:11
*** harlowja has joined #openstack-meeting-alt17:11
*** shelz007 has joined #openstack-meeting-alt17:12
*** clopez has joined #openstack-meeting-alt17:12
*** shelz007 has quit IRC17:14
*** rsyed is now known as rsyed_away17:14
*** vgridnev has quit IRC17:18
*** dizquierdo has joined #openstack-meeting-alt17:19
*** prithiv has quit IRC17:20
*** eilert has joined #openstack-meeting-alt17:21
*** DandyPandy has joined #openstack-meeting-alt17:21
*** prithiv has joined #openstack-meeting-alt17:22
*** reldan has quit IRC17:25
*** sigmavirus24 is now known as sigmavirus24_awa17:26
*** jesusaur has joined #openstack-meeting-alt17:26
*** kzaitsev_mb has quit IRC17:28
*** sigmavirus24_awa is now known as sigmavirus2417:28
*** yamahata has joined #openstack-meeting-alt17:29
*** iyamahat has joined #openstack-meeting-alt17:31
*** mfedosin_ has joined #openstack-meeting-alt17:32
mfedosin_hey! today's glare meeting is skipped17:33
*** paul-carlton2 has quit IRC17:33
mfedosin_next one will be on 16th of May17:33
*** dprince has quit IRC17:36
*** EricGonczer_ has quit IRC17:37
*** kairat_ has joined #openstack-meeting-alt17:37
*** numans has quit IRC17:37
*** neelashah has quit IRC17:39
*** snackewm has quit IRC17:41
*** snackewm has joined #openstack-meeting-alt17:41
*** stevemar has quit IRC17:41
*** neelashah has joined #openstack-meeting-alt17:41
*** lpetrut has quit IRC17:43
*** vilobhmm11 has quit IRC17:43
*** stevemar has joined #openstack-meeting-alt17:44
*** mfedosin_ has quit IRC17:48
*** reldan has joined #openstack-meeting-alt17:50
*** s3wong has joined #openstack-meeting-alt17:51
*** dprince has joined #openstack-meeting-alt17:52
*** pvaneck has joined #openstack-meeting-alt17:56
*** muralia_ has quit IRC17:57
*** muralia has joined #openstack-meeting-alt17:57
*** EricGonczer_ has joined #openstack-meeting-alt17:57
*** baoli has joined #openstack-meeting-alt17:58
*** prithiv has quit IRC17:58
*** neelashah has quit IRC17:59
*** korzen has joined #openstack-meeting-alt18:00
*** gyee has joined #openstack-meeting-alt18:07
*** Sukhdev has quit IRC18:09
*** Sukhdev has joined #openstack-meeting-alt18:09
*** Sukhdev has quit IRC18:10
*** sgotliv_ has joined #openstack-meeting-alt18:10
*** neelashah has joined #openstack-meeting-alt18:11
*** yamahata has quit IRC18:11
*** beslemon has joined #openstack-meeting-alt18:11
*** ajmiller_ has joined #openstack-meeting-alt18:12
*** salv-orlando has quit IRC18:13
*** MarkAtwood has joined #openstack-meeting-alt18:13
*** salv-orlando has joined #openstack-meeting-alt18:13
*** ajmiller has quit IRC18:15
*** tellesnobrega_af is now known as tellesnobrega18:18
*** salv-orlando has quit IRC18:18
*** mfedosin_ has joined #openstack-meeting-alt18:18
*** lpetrut has joined #openstack-meeting-alt18:22
*** salv-orlando has joined #openstack-meeting-alt18:24
*** mickeys has joined #openstack-meeting-alt18:25
*** ninag_ has quit IRC18:25
*** tango has joined #openstack-meeting-alt18:25
*** ninag has joined #openstack-meeting-alt18:27
*** mickeys has quit IRC18:28
*** mickeys has joined #openstack-meeting-alt18:29
*** ninag has quit IRC18:29
*** mickeys has quit IRC18:33
*** ninag has joined #openstack-meeting-alt18:39
*** lpetrut has quit IRC18:39
*** ninag has quit IRC18:41
*** catherineD has joined #openstack-meeting-alt18:42
*** ijw has joined #openstack-meeting-alt18:42
*** MarkAtwood has quit IRC18:43
*** nadya has joined #openstack-meeting-alt18:43
*** lpetrut has joined #openstack-meeting-alt18:45
*** baoli has quit IRC18:46
*** ajmiller_ is now known as ajmiller18:48
*** ijw has quit IRC18:48
*** korzen has quit IRC18:49
*** kzaitsev_mb has joined #openstack-meeting-alt18:50
*** andtey-mp has joined #openstack-meeting-alt18:52
*** baoli has joined #openstack-meeting-alt18:54
*** Rockyg has joined #openstack-meeting-alt18:54
*** lpetrut has quit IRC18:55
*** vilobhmm11 has joined #openstack-meeting-alt18:59
*** tinbar has joined #openstack-meeting-alt18:59
*** Guest16848 has quit IRC19:00
*** ijw has joined #openstack-meeting-alt19:01
*** rods has joined #openstack-meeting-alt19:02
catherineD#startmeeting refstack19:03
openstackMeeting started Mon Apr 18 19:03:06 2016 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: refstack)"19:03
openstackThe meeting name has been set to 'refstack'19:03
pvanecko/19:03
catherineDsilly me I started the meeting in the DefCore channel :-)19:03
Rockygo/19:03
pvaneckagain?19:03
pvanecklol19:03
catherineDyea :-(19:04
catherineDRockyg: Hi19:04
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-04-1819:05
*** baoli has quit IRC19:07
Rockygit sucks to waste your weekend being sick19:07
catherineDRockyg: oh ... hope you feel better now ..19:07
andtey-mphi19:07
sslypushenkoo/19:07
Rockygcold.  getting better.19:08
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-04-1819:08
catherineDlet's start19:10
catherineD#topic No meeting for the next 2 weeks19:10
*** openstack changes topic to "No meeting for the next 2 weeks (Meeting topic: refstack)"19:10
catherineDThe next meeting iwill be on May 09, 201619:10
andtey-mpok )19:11
sslypushenkocatherineD:  I'll have a day-off on May 919:11
catherineDI also want to check whether everyone here is OK if we move the meeting from Monday to Tuesday at the same time 19:00 UTC and #openstack-meeting-alt?19:11
andtey-mpI think we will have many conversations on the summit19:11
sslypushenkoActually, our Russian colleagues, too)19:11
catherineDsslypushenko: if we move the meeting to Tues day are you OK?19:11
andtey-mpI'm ok with moving19:11
sslypushenkoYeap19:11
sslypushenkoTuesday, same time sounds good19:12
catherineDsslypushenko: Rockyg: pvaneck: how about you on movinmg19:12
pvanecktuesday is fine for me. is a slot available for 19:00 utc tuesday?19:12
catherineDyes the slot is available19:12
*** MarkAtwood has joined #openstack-meeting-alt19:13
Rockygok by me, but better grab the slot fast19:13
catherineDgreat ...19:13
catherineDI will grab the slot after this meeting ...19:13
catherineD#agreed Move RefStack IRC meeting to Tuesday 19:00 UTC #openstack-meeting-alt19:14
catherineD#action Catherine to submit patch for the move19:14
catherineDthat is really great that all of us are available19:14
catherineD#topic RefStack Newton summit discussion topics19:15
*** openstack changes topic to "RefStack Newton summit discussion topics (Meeting topic: refstack)"19:15
catherineD#link     Please add your topics to https://etherpad.openstack.org/p/refstack-newton-summit19:15
catherineDandtey-mp: agree that we have a lot to discuss during the summit ...19:15
catherineDI am so glad that all of us will be there this time ...19:16
*** raginbajin has quit IRC19:16
Rockygyay!19:16
catherineDandtey-mp: I see your comments on the product REST API patch... Thanks... I will response so we get the conversation going ... but I think it is best that we discuss face-2-face19:17
*** lpetrut has joined #openstack-meeting-alt19:17
andtey-mpcatherineD: ok. I've started implementation of product REST API and I though about this questions19:18
catherineDjust want to confirm  if meeting at May 10 ok for andtey-mp: and sslypushenko: ?19:18
catherineDandtey-mp: yup that is really great ..19:18
catherineDthe more issues we found now the better because we can discuss face-2-face ..19:19
sslypushenkoMay 10 works for me19:19
andtey-mpit's ok for me but I don't know right now about my availability at May 10...19:19
andtey-mpbut it works for me too19:19
catherineDRockyg: is May 10 Mother's day?  just noted that :-)19:19
*** vilobhmm11 has quit IRC19:20
catherineDandtey-mp: that is fine ...19:20
catherineDmoving on ...19:20
Rockygmothers day is always a sunday19:20
catherineDRockyg: oh19:20
catherineD#topic Vendor registation19:21
*** openstack changes topic to "Vendor registation (Meeting topic: refstack)"19:21
*** raginbajin has joined #openstack-meeting-alt19:21
*** beslemon has quit IRC19:22
catherineDandtey-mp: https://review.openstack.org/#/c/302436/ is ready to merge ... but we just want to hold on so that we can merge https://review.openstack.org/#/c/306923/ to cut a release for the live site19:22
catherineDspeaking of release ... we may as well moving to the next topic ...19:23
catherineD#topic RefStack releases update to the live public website.19:23
*** openstack changes topic to "RefStack releases update to the live public website. (Meeting topic: refstack)"19:23
andtey-mpi don't understand what does it mean exactly )19:24
catherineDso we used to update the live site with refstack master ... true CICD process :-) ..whatever merge to master will be updated to the live site 15 mins after19:24
*** sputnik13 has quit IRC19:25
catherineDa couple months ago , we change to update the live site with tag release only ... that means that  the live site only get updated whenever we push a new tag19:25
*** mfedosin_ has quit IRC19:26
*** neelashah has quit IRC19:26
catherineDwith the we have total control of when to push what changes to the live site ... because we are the one who push the tag19:26
*** dizquierdo has quit IRC19:26
*** neelashah has joined #openstack-meeting-alt19:27
catherineDpvaneck: and I usually push new changes to the live site on Friday afternoon ..when the activity on the RefStack site is less and we have the weekend to fix issues if there is any ..19:27
*** sputnik13 has joined #openstack-meeting-alt19:28
catherineDHowever, last week .. there is a change that ..from now on only the release team can create a tag (based on request from the project by submttng a patch to the releases repository for review ...19:29
*** lpetrut has quit IRC19:29
*** weshay has quit IRC19:29
catherineDwe basically can not control when the tag is being created (as we prefer on Friday)19:29
pvaneckI don't think we'll be pushing releases too often, and release patches are merged fairly quickly. let's just stick with the new release pattern for now.19:29
*** dshakhray has quit IRC19:30
catherineDok for the time being ... I am more concern about when we have big changes19:31
RockygYou could also request that the push happens on a specific day and probable with a four hour window.19:31
*** ninag has joined #openstack-meeting-alt19:31
*** ninag has quit IRC19:31
*** jprovazn has quit IRC19:31
catherineDRockyg: that would be good ..19:31
RockygIf you go to the openstack-release IRC channel, you can usually get someone who can act quickly, also.19:31
catherineDRockyg: and sometime if there is a problem we may want to push a new remedy release after that ..19:32
catherineDRockyg: great suggestion ...19:32
RockygRight.  IRC channel is good for that and if you can't find someone there, the infra folks can help19:32
catherineDI guess we will stick with the official release for now ..19:33
catherineD#action RefStack will update live site using the new release pattern19:33
*** pt_15 has joined #openstack-meeting-alt19:33
catherineDany other thoughts on this topic before we move on?19:34
RockygI think it would be good to meet with release at summit and discuss this as I think we're the only live website relying on them19:34
RockygMight want to flesh out an emergency procedure with them.19:34
*** dukhlov has joined #openstack-meeting-alt19:35
catherineDRockyg: yea let's do that .. I know that they have a cross project session ... I will add out topic there19:35
catherineDRockyg: thx19:35
catherineD#topic Product registration19:35
*** openstack changes topic to "Product registration (Meeting topic: refstack)"19:35
catherineDandtey-mp: thanks for all the comments and implementing the patch ...19:36
*** kzaitsev_mb has quit IRC19:36
catherineDI guess this is one of the topic we will discuss a lot face-2-face at the summit19:36
andtey-mpsure19:36
*** dukhlov has quit IRC19:37
catherineDanything else before we move to the next very important topic ...19:37
*** eilert has quit IRC19:37
*** dukhlov has joined #openstack-meeting-alt19:38
catherineD#topic Proposal to add Andrey Pavlov as RefStack core19:38
*** openstack changes topic to "Proposal to add Andrey Pavlov as RefStack core (Meeting topic: refstack)"19:38
catherineD#link http://lists.openstack.org/pipermail/openstack-dev/2016-April/092470.html19:38
catherineDRockyg: pvaneck: thanks for your response ...19:39
*** ihrachys has joined #openstack-meeting-alt19:39
*** yamamoto has quit IRC19:39
catherineDI am so happy that andtey-mp: has joined us for  this cycle ...19:39
andtey-mpthank you :)19:39
RockygCongratulations!!!!19:40
sslypushenkoCool!19:40
catherineDandtey-mp: you of 100% of the RefStack team's vote ...19:41
andtey-mpthank you very much :)19:41
catherineDEveryone please welcome our core andtey-mp:   ...19:41
*** dukhlov has quit IRC19:42
pvaneckglad to have you andrey!19:42
*** dukhlov has joined #openstack-meeting-alt19:42
sslypushenkoThat is really great! andtey-mp, congrats !19:42
andtey-mpthank you all!19:43
RockygWelcome aboard!19:43
catherineDandtey-mp: just some house keeping ...19:43
catherineDwe try to only merge code with two +219:43
* docaedo catches up late and is glad to see meeting moving to Tuesday (works better for him!)19:43
andtey-mpsure, its a common OpenStack rule as I know19:44
catherineDwe try to not have the 2 +2  for a patch that is summited by a person from the same company (19:44
RockygOr the coder ;-)19:45
pvaneckyou mean merge?19:45
pvaneckah nvm. i got it19:45
*** ian_ott has joined #openstack-meeting-alt19:45
catherineDandtey-mp: I just add you could you try to see whether the +2 appears for you ...19:45
catherineDRockyg: yea ... again .. we try but sometime we may have exception ...19:46
andtey-mpok ) I see that you and Paul from IBM. maybe someone else?19:46
catherineDdocaedo: glad that the new time will be better for you :-)19:46
*** eilert has joined #openstack-meeting-alt19:46
RockygIt is getting easier to not have exceptions as the core team continues to grow:-)19:47
*** kairat_ has quit IRC19:47
catherineDRockyg: yea that is exactly the reason why we have exception ...19:47
andtey-mpcatherineD: yeah, I  have +2 from now in review19:47
*** salv-orlando has quit IRC19:47
catherineDandtey-mp: that is great !!19:47
*** enriquetaso has quit IRC19:48
catherineDandtey-mp: I guess we need to check the email or member profile to see which company  ..19:48
catherineDthat is all I have today ...19:49
catherineD#topic Open discussion19:49
*** openstack changes topic to "Open discussion (Meeting topic: refstack)"19:49
RockygI've got something19:49
RockygLots of devs are now running test clouds that aren't devstack and wondering how to use tempest with them19:50
RockygWe have the solution, we just need to advertise it.19:50
*** Sukhdev has joined #openstack-meeting-alt19:50
catherineDRockyg: yea thanks for promoting us ....19:50
RockygMaybe an email to the dev list with all, tempest, refstack that introduces the client and points to repo and docs?19:51
catherineDRockyg: any suggestion on how to do that19:51
catherineDRockyg:  ok that would be a good start19:51
RockygAlso go to one of the QA sessions and let the QA PTL and others know about it.  Maybe have a demo in a brownbag session or lightning talk?  A lightning talk in the Ops sessions would also be good.19:52
*** ddieterly has joined #openstack-meeting-alt19:52
*** e0ne has joined #openstack-meeting-alt19:52
catherineDRockyg: we have a speaker session at Austin19:53
catherineDwith demo19:53
RockygAlso, after the summit, I'd be happy to sponsor a meetup at Huawei where folks can demo it to the SV openstack crowd.19:53
andtey-mpGood example will be RefStack when we will finish new model - wher anyone can register his Cloud and run tests with any Guidelines )19:53
RockygYeah, but the speaker session is for the enduser stuff.  Not too many devs go to that.19:53
catherineDRockyg: a lighting talk in the Ops session would be a good addition too19:53
*** yamamoto has joined #openstack-meeting-alt19:54
catherineDandtey-mp: yea19:54
Rockygandtey-mp, most of the devs just want to run tests and look at results.  No interaction with the server19:54
catherineDRockyg: register lighting talk is done on site right?19:55
andtey-mpRockyg: in any case - they will need a Cloud to run on )19:55
docaedorefstack-client still requires multiple users in the cloud being tested, right?19:55
RockygFor ops lightning, you go to ops etherpad and just add your talk there.19:55
catherineDRockyg: ok I will do that... thanks19:56
catherineDanything else?19:56
andtey-mpdocaedo: it depends on tempest.conf19:57
pvaneckdocaedo: at least for defcore tests, i think only one user is needed19:57
Rockygdocaedo, to run all tempest, yeah.  But if it's your test cloud, shouldn't be an issue.  Part of tempest config19:57
docaedook - for the sake of making it easy on newcomers, definitely suggest a little more help with tempest.conf19:57
docaedoon my first pass that was the only trouble I had19:57
*** dukhlov has quit IRC19:57
*** delattec has joined #openstack-meeting-alt19:57
Rockygdocaedo, +100019:57
catherineDdocaedo: tempest.conf is one of the topic on the speaker session ..19:57
docaedobut big +1 on telling people they can use the client to test their non-devstack clouds easily19:58
*** kzaitsev_mb has joined #openstack-meeting-alt19:58
catherineDnext release we will add a help link to RefStack sit and include all RefStack doc ... hopefully it will provide some help19:58
docaedotempest.conf as taken direct from devstack did not work for me - only worked when I changed it to use the accounts yaml and added additional accounts FYI19:58
*** dukhlov has joined #openstack-meeting-alt19:59
docaedocatherineD: I'll gladly review and test those doc changes19:59
catherineDdocaedo: thx19:59
Rockygdocaedo, could you make sure your experience is reflected in the docs?19:59
catherineDneed to end meeting now19:59
*** cdelatte has quit IRC19:59
docaedoRockyg: will do19:59
RockygGood meeting!19:59
Rockygthanks, docaedo !19:59
catherineDsee you all at the summit !!!!20:00
pvanecksafe travels everyone20:00
catherineD#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Mon Apr 18 20:00:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-04-18-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-04-18-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-04-18-19.03.log.html20:00
*** mp1 has joined #openstack-meeting-alt20:00
*** jmckind has joined #openstack-meeting-alt20:00
redrobot#startmeeting barbican20:00
openstackMeeting started Mon Apr 18 20:00:30 2016 UTC and is due to finish in 60 minutes.  The chair is redrobot. 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
*** ddieterly is now known as ddieterly[away]20:00
redrobot#topic Roll Call20:00
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:00
jmckindo/20:00
edtubillo/20:00
mp1o /20:00
*** andtey-mp has left #openstack-meeting-alt20:00
woodster_o/20:01
redrobotAs usual the agenda can be found here:20:01
redrobot#link https://wiki.openstack.org/wiki/Meetings/Barbican#Agenda20:01
*** catherineD has left #openstack-meeting-alt20:01
*** arunkant has joined #openstack-meeting-alt20:02
*** delattec has quit IRC20:02
arunkanto/20:02
kfarro/20:02
redrobotNot a whole lot of barbicaneers here today20:03
redrobot#topic Design Summit20:03
*** openstack changes topic to "Design Summit (Meeting topic: barbican)"20:03
*** ninag has joined #openstack-meeting-alt20:03
redrobot#link https://etherpad.openstack.org/p/newton-barbican-design-sessions20:04
redrobotThe design summit is next week.20:04
redrobotLooking forward to seeing everyone in Ausin!20:04
redrobot*Austin20:04
*** alex_xu has quit IRC20:04
redrobotI added the Barbican schedule to the etherpad20:04
redrobotThursday is going to be a long day20:04
redrobotalso godo news arunkant we did get the 1/2 day meetup on Friday morning.20:05
redrobot*good20:05
* redrobot can't type today20:05
*** Sukhdev has quit IRC20:05
arunkantredrobot: just noticed that..great20:05
*** tango has quit IRC20:05
panatlo/20:05
*** ddieterly[away] is now known as ddieterly20:05
redrobotIt appears there was some miscommunication with the Security folks, since they also have a BYOK fishbowl20:06
*** alex_xu has joined #openstack-meeting-alt20:06
redrobotThinking we can go to their fishbowl on Wednesday and then continue the conversation during our fishbowl.20:06
redrobotnot sure that we'll have 2 fishbowls worth of things to discuss though...20:07
*** sdake has quit IRC20:07
redrobotany questions/comments about the summit?20:07
arunkantredrobot: what is the agenda for other wednesday sessions. I see byok on afternoon20:07
*** delattec has joined #openstack-meeting-alt20:07
*** ninag has quit IRC20:08
redrobotarunkant for the regular (non-fishbowls) sessions we'll be going through the etherpad like previous summits.20:08
arunkantredrobot: okay20:08
*** e0ne has quit IRC20:08
redrobotok, moving on20:08
*** ninag has joined #openstack-meeting-alt20:09
redrobot#topic Bugfix Backports20:09
*** openstack changes topic to "Bugfix Backports (Meeting topic: barbican)"20:09
*** reedip_ has joined #openstack-meeting-alt20:09
*** ninag has quit IRC20:09
redrobotlet's do these one at a time:20:09
redrobot#link https://review.openstack.org/#/c/303648/20:10
*** kzaitsev_mb has quit IRC20:10
*** ninag has joined #openstack-meeting-alt20:10
*** dukhlov has quit IRC20:10
*** ninag has quit IRC20:11
arunkantpanatl has these changes related to sql password and token printed in logs in debug20:11
*** ninag has joined #openstack-meeting-alt20:11
redrobotI don't think fixing a debug statement merits spinning up a new release of barbican20:11
* redrobot realizes that's the other bug20:11
redrobotLiberty backport:20:12
redrobot#link https://review.openstack.org/#/c/303845/20:12
panatl303648 . ia all done i guess20:12
redrobotMitaka backport:20:12
redrobot#link https://review.openstack.org/#/c/304335/20:12
*** beekneemech is now known as bneme20:12
*** bneme is now known as bnemec20:12
*** baoli has joined #openstack-meeting-alt20:13
panatlredroot: it is a security concerns .. so nee to patch both Liberty and mitaka20:13
*** ninag has quit IRC20:13
redrobotpanatl I understand it's a security concern, but it's not a critical issue20:13
panatlwe talked seperatly on that .. and u said just rephrase statement and avoid secret in logs20:13
redrobotI imagine most people won't ever run production environments in debug mode20:14
redrobotpanatl I think it's a good fix20:14
panatlthanks20:14
*** _amrith_ has quit IRC20:14
redrobotjust not critical enough to re-release Mitaka and Liberty20:14
*** ian_ott has quit IRC20:14
*** tonytan4ever has joined #openstack-meeting-alt20:14
arunkantredrobot: Yes..but if somebody just runs barbican in debug logs for debugging perspective, they will be able to see other people's token .20:15
*** amrith has joined #openstack-meeting-alt20:15
*** kzaitsev_mb has joined #openstack-meeting-alt20:15
panatlbarbican is about security ... i think this is critical.. need to protect sensitive informaiton :)20:15
panatl+1 to arunkant:20:16
*** dprince has quit IRC20:16
redrobotpanatl by not critical, I mean this is a Class B3 vuln https://security.openstack.org/vmt-process.html#publish-ossa20:17
*** lpetrut has joined #openstack-meeting-alt20:17
redrobotpanatl we could just issue a OSSN and not have to re-release Mitaka and Liberty20:17
*** maxabidi has joined #openstack-meeting-alt20:17
redrobotpanatl so not a Class A vulnerability20:17
panatlok ... we should atleast do the mitaka20:18
*** SlickNik has left #openstack-meeting-alt20:18
redrobotpanatl I think we can fix in master and write up OSSNs for Mitaka and Liberty20:18
redrobotpanatl mitaka was just released, and I don't think this level of vulnerability merits a re-release of mitaka either.20:19
panatlok thanks20:19
*** dukhlov has joined #openstack-meeting-alt20:20
redrobotpanatl do you want to write the OSSN?20:20
panatlsure ... never done that.. but like to get involved20:20
*** diazjf has joined #openstack-meeting-alt20:20
redrobotpanatl cool20:20
redrobot#action panatl to write OSSN for Mitaka and Liberty regarding Bug #156750020:21
openstackbug 1567500 in Barbican "Barbican server discloses SQL Connection String containing a Password via LOG.debug()" [Low,Fix released] https://launchpad.net/bugs/1567500 - Assigned to Pankaj Khandar (pankaj-khandar)20:21
*** neelashah has quit IRC20:21
edtubilln20:21
edtubillfinger slipped. ignore that.20:22
*** kzaitsev_mb has quit IRC20:22
*** vishwanathj has joined #openstack-meeting-alt20:22
redrobotI think that covers the backports?20:22
redrobotI just noticed the first link was not a backport patch20:23
*** diazjf has quit IRC20:23
panatlyes that coveres BP20:23
arunkantredrobot: does this merit a backport https://review.openstack.org/#/c/303648/  .20:23
*** ddieterly is now known as ddieterly[away]20:23
*** ninag has joined #openstack-meeting-alt20:24
arunkantredrobot: It a critical error logged if client sends json-home header to http://localhost:9311/v1 call.20:24
redrobotarunkant critical log?  as in a 500 happens?20:24
*** dukhlov has quit IRC20:24
arunkantYes..it reports error on client side and then log 'CRITICA' level log in barbican log20:25
*** lpetrut has quit IRC20:26
*** kzaitsev_mb has joined #openstack-meeting-alt20:26
redrobotarunkant if the service returns a 500 instead of a 406 Not Acceptable, then we should backport it20:26
*** ddieterly[away] is now known as ddieterly20:26
redrobotarunkant but if the issue is just an incorrect log level, then I don't think it's critical.20:26
*** matrohon has joined #openstack-meeting-alt20:27
*** tonytan_brb has joined #openstack-meeting-alt20:28
arunkantredrobot: It does not return 406..it returns error . Change is to handle the issue correctly..so no 406 is returned20:28
redrobot> returns error ?  does that mean 500 response?20:29
* redrobot is confused because bot 4XX and 5XX responses are errors20:29
arunkantredrobot : It returns "Internal server error" ..see the trace ..https://bugs.launchpad.net/barbican/+bug/156814120:30
openstackLaunchpad bug 1568141 in Barbican "Unhandled CRITICAL error raised for json-home request to /v1 resource" [Medium,Fix released] - Assigned to Arun Kant (arunkant-uws)20:30
arunkantredrobot: So yes 500 error20:30
*** tonytan4ever has quit IRC20:31
redrobotarunkant yeah, I think that should be backported to Mitaka then20:31
redrobotarunkant and/or liberty if it's also affected20:31
arunkantredrobot: Okay..I will add the patch for both of branches20:31
redrobotarunkant awesome, thanks20:32
redrobotok, moving on20:32
redrobot#topic  Should creator be allowed to delete related barbican resources?20:32
*** openstack changes topic to "Should creator be allowed to delete related barbican resources? (Meeting topic: barbican)"20:32
*** ninag has quit IRC20:33
*** yamahata has joined #openstack-meeting-alt20:33
*** salv-orlando has joined #openstack-meeting-alt20:33
redrobot#info No, "creator" should not be allowed to delete resources20:33
arunkantredrobot: this is the case we observed when people are using cinder envrypted volumes. We ask them to use creator role for creating keys..but then when user deletes the volume, it failed with 403 error on barbican side20:33
*** baoli has quit IRC20:33
redrobotarunkant that is expected20:34
*** baoli has joined #openstack-meeting-alt20:34
redrobotthe only difference between admin and creator is that admin can delete and creator cannot20:34
arunkantredrobot: the reason is for deleting the key, they require admin role ..20:34
redrobotarunkant yes, that is by design20:34
*** tonytan4ever has joined #openstack-meeting-alt20:34
arunkantredrobot: why is that ? I mean from client perspective, which role they should be assigned ..creator or admin ..20:34
*** kzaitsev_mb has quit IRC20:35
redrobotarunkant from a client perspective, the client should have at least one user with the "admin" role on their tenant20:35
redrobotarunkant that user can add/delete secrets within that tenant20:35
redrobot"creator" was added as a role that can guarantee that secrets can't be deleted20:35
arunkantredrobot: But cinder allows creation of volume to any user with *any* role in a tenant.. https://github.com/openstack/cinder/blob/master/etc/cinder/policy.json#L920:36
redrobot"creator" is intended for automation systems that create keys for example.  It helps guarantee that such a system can't run amok and delete a bunch of secrets20:36
*** nadya has quit IRC20:36
redrobotarunkant cinder roles != barbican roles20:36
arunkantredrobot: Yes..but then if user is using cinder volumes..do they all be assigned 'admin' role as cinder does allow user to delete volume20:37
*** tonytan_brb has quit IRC20:37
arunkantI meant barbican 'admin' role. I think it defeats the purpose if every used needs barbican admin role to work it properly.20:38
redrobotI'm not super knowledgeable about the cinder workflow, maybe kfarr can chime in...20:38
redrobotarunkant "work it properly"?20:38
*** e0ne has joined #openstack-meeting-alt20:38
redrobotas I was saying, the only difference between admin and creator is that creator cannot delete20:38
redrobotif we let creator also delete, then there is no difference between the "admin" role and the "creator" role20:39
redrobotso what would be the point of defining two roles with the same set of permissions?20:39
arunkantredrobot: In horizon, a user can create cinder volume and can delete that volume for that tenant. If they use encrypted volumes, then they need admin role to do both20:39
redrobotarunkant cinder workflow aside, why do you want two roles with the same permissions?20:40
redrobotarunkant is this a problem in a devstack integration test between cinder and barbican?20:40
arunkantredrobot: creator role is not sufficient alone. Or may be we change barbican policy such that user with creator role who created the secret can delete it.20:40
*** rickflare has quit IRC20:40
*** rickflare has joined #openstack-meeting-alt20:41
arunkantredrobot: No this is a actual deployment with cinder and barbican. I am trying to see the reason why we don't allow user who created the secret ..is allowed to delete it20:41
redrobotarunkant because secrets are scoped to projects20:42
kfarrjust chiming in that arunkant is right, a non-admin cinder user can create volumes, but needs to have barbican admin role assigned in order to create the keys necessary for encrypted volumes20:42
redrobotarunkant all RBAC has been designed around the tenant roles20:42
*** eggmaster has quit IRC20:43
arunkantredrobot: We capture creator id in secrets..so we can easily limit access to user with creator role and matching that token user id == secret.creator_id20:43
kfarr* to delete the keys20:43
redrobotarunkant you can re-write your policy to fit your use case... I thought we were talking about changing the default policy file that is used in devstack20:43
woodster_arunkant: so are you asking that there be an 'or' clause for the secret's user on this line (for example)?: https://github.com/openstack/barbican/blob/master/etc/barbican/policy.json#L3320:43
arunkantwoodster_ : yes..similar to that...add creator role to allow that .20:45
redrobotarunkant It sounds to me like you're wanting to add policy around user-identity as well as role-within-tenant20:45
*** dane_leblanc has quit IRC20:45
woodster_cinder doesn't appear to care much about roles it seems. It seems Barbican should be more stringent than that20:46
redrobotwoodster_ +120:46
arunkantredrobot: I am asking if it make sense to make change in master as this is a cinder use case..20:46
arunkantwoodster_ : Yes, stringent is fine..but then what we are saying to user who wants to use encrypted volume, they have barbican admin role ..20:47
redrobotarunkant yes, because you need the barbican admin role to be able to delete secrets20:47
arunkantwoodster_ : And as cinder allows every user to have encrpyted volume..that means all users needs to have barbican admin role..which defeats the purpose of admin vs creator on barbican side.20:48
woodster_well, I think there is a desire to simplify openstack configuration in general, so I would presume that means out of the box configs being fit to purpose. But that could also mean that we should be adding role usage where it hasn't been used, in the name of enhanced security. Seems design session/cross-project ish to me :)20:48
redrobotarunkant again, you never answered my question:  If the only difference between admin and creator is that creator cannot delete, then if we add delete capabilities to creator what is the difference between the two?20:49
redrobotarunkant is it just a naming issue?20:49
redrobotarunkant does cinder have a "creator" role?20:49
woodster_ I think by 'creator' it is in the cinder context, so really the user who created the secret20:50
woodster_...not 'creator' in the barbican roles sense20:50
*** cknight has quit IRC20:50
*** e0ne has quit IRC20:50
arunkantredrobot: May be there are other differences..will need to check it. But from client usage perspective, as I said all users wil need to have admin role if they want to work with encrypted volumes20:50
*** shamail has joined #openstack-meeting-alt20:51
* woodster_ though this Cinder policy line refers to a project match, not user ID match, correct?: "admin_or_owner": "is_admin:True or project_id:%(project_id)s",20:51
*** carolbarrett has joined #openstack-meeting-alt20:51
redrobotarunkant understood, we can revisit this if you can identify how creator+delete would be different than admin20:51
*** zeih has joined #openstack-meeting-alt20:51
*** kzaitsev_mb has joined #openstack-meeting-alt20:51
arunkantwoodster_ : Yes , I am surprised as well as cinder allows access to most of its resource with just any role on that tenant20:52
woodster_it would be good to get the security group's opinion about these things too20:52
*** ninag has joined #openstack-meeting-alt20:52
woodster_arunkant: my read is that no role is needed at all, but not sure how their middleware is connected20:53
redrobotwoodster_ I think you made a good point about having more narrowly scoped roles within devstack20:53
redrobotwoodster_ I think there's a cross-project meeting to that effect20:53
woodster_well, my overall point is to balance ease of integration/adoption of barbican, with appropriate security constraints...some sort of happy medium in there perhaps20:54
*** cloudtrainme has joined #openstack-meeting-alt20:54
*** dronshaw has joined #openstack-meeting-alt20:55
arunkant redrobot: If we allow creator user (user who created the secret) to delete secret, will that be okay. S20:55
*** Sukhdev has joined #openstack-meeting-alt20:55
redrobotarunkant my point was that if we do that, then there would be no difference between a creator and an admin.  The only difference would be the role name.20:56
arunkantredrobot: So it means that other users with creator role in same project..cannot delete other user's secrets..only their own20:56
*** ninag has quit IRC20:56
woodster_I think the 'creator' role is the red herring here...I think we are really talking about the user who created the secret20:57
woodster_...so perhaps with no role on the project20:57
*** hichihara has joined #openstack-meeting-alt20:57
*** fawadkhaliq has joined #openstack-meeting-alt20:57
*** njohnston_ is now known as njohnston20:57
*** baoli has quit IRC20:57
redrobotI guess we'd be expanding the ownership of the secret to one user (the one who uploaded the secret) + project ...20:57
arunkantwoodster_ , creator or admin can only create entities..so that's why was using creator role..but yes essentially its the user who created the secret at first place.20:58
redrobotit complicates the RBAC matrix a bit20:58
redrobot... aaand we're almost out of time20:58
woodster_arunkant: it seems cinder's ask is to not have any role for this create/delete flow20:58
arunkantredrobot: yes..but it can handle cinder use case.20:58
redrobotinteresting conversation though... we should add it to the etherpad for things to discuss in Austin.20:58
*** kei_ has joined #openstack-meeting-alt20:58
*** weshay has joined #openstack-meeting-alt20:58
*** neelashah has joined #openstack-meeting-alt20:59
woodster_maybe hockeynut could bring cinnamon roles for that discussion like at the midcycle a while back20:59
redrobotno IRC meeting next week because Summit.20:59
*** leong has joined #openstack-meeting-alt20:59
*** kzaitsev_mb has quit IRC20:59
*** MeganR has joined #openstack-meeting-alt21:00
redrobot#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Mon Apr 18 21:00:12 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-04-18-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-04-18-20.00.txt21:00
redrobotThanks everyone!21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-04-18-20.00.log.html21:00
*** sdake has joined #openstack-meeting-alt21:00
shamailping carolbarrett21:01
*** mp1 has left #openstack-meeting-alt21:01
*** carolbarrett_ has joined #openstack-meeting-alt21:02
*** kzaitsev_mb has joined #openstack-meeting-alt21:02
carolbarrett_#startmeeting Product Working Group21:03
openstackMeeting started Mon Apr 18 21:03:08 2016 UTC and is due to finish in 60 minutes.  The chair is carolbarrett_. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: Product Working Group)"21:03
openstackThe meeting name has been set to 'product_working_group'21:03
carolbarrett_Hi Folks - Who's here for the Product WG Meeting?21:03
shamailHi Carol.21:03
MeganRo/21:03
shamailHi all.21:03
leongo/21:03
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:03
*** rossella_s has quit IRC21:03
kei_o/21:03
Arkady_Kanevskyare we using phone bridge today?21:03
carolbarrett_arkady_kanesvky - No bridge today....21:04
Arkady_Kanevskylooking at slides https://docs.google.com/presentation/d/1zD3sc90WtcdCIwOsCPIrY1fsEvmk1wHmUTFmRE8mChc/edit#slide=id.p321:04
Arkady_KanevskyOK on phoen21:04
*** carolbarrett has quit IRC21:04
*** rossella_s has joined #openstack-meeting-alt21:04
carolbarrett_arkady_kanevsky - Which session are those slides for?21:04
Arkady_Kanevskythe first agenda item for today - board meeting21:05
carolbarrett_OK21:05
carolbarrett_You can find the agenda for today here21:05
carolbarrett_#link https://wiki.openstack.org/wiki/Meetings/product-team#April_18.2C_2016_Product_Team_Meeting_Agenda21:05
carolbarrett_#topic Joint TC/Board Slide review21:05
*** openstack changes topic to "Joint TC/Board Slide review (Meeting topic: Product Working Group)"21:05
*** rsyed_away is now known as rsyed21:05
carolbarrett_#link https://docs.google.com/presentation/d/1zD3sc90WtcdCIwOsCPIrY1fsEvmk1wHmUTFmRE8mChc/edit#slide=id.p321:06
*** tango has joined #openstack-meeting-alt21:06
Arkady_Kanevskydo we want to add themese as separate row for slide 2? or it is hidden in roadmap?21:06
shamailArkady_Kanevsky: we are reviewing the Board/TC deck currently21:06
sgordonArkady_Kanevsky, i think this just a high level overview of what the group is doing21:06
*** edwardb has quit IRC21:06
Arkady_Kanevskyyes21:06
Arkady_Kanevskyok21:07
shamailDo you mean the topic of themes at the BoD discussion?21:07
sgordonArkady_Kanevsky, the roadmap themes and contents belong in the roadmap, not this deck21:07
carolbarrett_These slides are meant to provide an update as well as background on challenges we are working through to get a work flow established for bringing requirements into the community and using them as a basis for creating specs.21:07
shamailsgordon: +121:07
sgordoncarolbarrett_, understood21:07
carolbarrett_sgordon: you are right.21:07
*** banix has quit IRC21:07
carolbarrett_arkady_kanevsky: pls add your session into the spreadsheet that we reference in the slides21:07
carolbarrett_#link https://docs.google.com/spreadsheets/d/1Z5GbBueeE6sf1gpcrcYRZg-DqdrPda-VzkUami0zTiU/edit?usp=sharing21:08
*** arunkant has left #openstack-meeting-alt21:08
*** kfarr has quit IRC21:08
carolbarrett_Slide 2 sets the agenda for the following slides; we are going to focus on the yellow items21:08
carolbarrett_Any comments on slide 2?21:09
carolbarrett_Shamail - do you have a user story work flow picture we can add to slide 3?21:09
shamailcarolbarrett_: I sent you an updated version (in powerpoint) last night21:10
shamaillet me upload it to drive real quick21:10
*** nateziemann has joined #openstack-meeting-alt21:10
*** dukhlov has joined #openstack-meeting-alt21:10
carolbarrett_ok - I'll grab it and post a link21:10
*** tango has quit IRC21:10
carolbarrett_shamail - I don't see it...21:11
shamailuploading to drive21:11
shamailand ill resend to you21:11
shamail#link https://drive.google.com/open?id=0B_yCSDGnhIbzcnpGQ3R5UUZoZTQ21:11
*** ddieterly is now known as ddieterly[away]21:12
shamailsorry about that21:12
carolbarrett_spoke too soon - think it's this one21:12
carolbarrett_#link https://docs.google.com/presentation/d/1zD3sc90WtcdCIwOsCPIrY1fsEvmk1wHmUTFmRE8mChc/edit#slide=id.p721:12
*** travisb has joined #openstack-meeting-alt21:12
carolbarrett_but I still don't see a user story work flow....21:12
shamailPlease check the link that I posted (I just emailed the PPT to you again as well)21:13
carolbarrett_Got it - sorry21:13
carolbarrett_OK - let'21:13
shamailnp, I must’ve sent the original message to an incorrect email address.21:13
Arkady_Kanevskybut box on 3rd sldie under usre story is empty.21:13
*** ansmith has quit IRC21:14
*** Akis_ has quit IRC21:14
shamailUser Story Workflow is on slide 4 of https://drive.google.com/file/d/0B_yCSDGnhIbzcnpGQ3R5UUZoZTQ/view?pref=2&pli=121:14
*** spzala has quit IRC21:14
Arkady_Kanevskyneeds editing so text stay in the box and readable21:14
carolbarrett_Shamail: This is the work flow post midcycle, correct?21:15
shamailYes21:15
carolbarrett_I wonder if we need to highlight the areas in the flow associated with the Risks, so that folks don't try to read the whole thing...?21:15
Arkady_KanevskyIf the PWG creates the Implementation details and Blue Prints, will that be credible and acceptable to the Project Teams? - this feels wrong.21:16
Arkady_Kanevskywe shoudl leave impl details to projects21:16
shamailgood idea carolbarrett_21:16
shamailI can change the color or draw a box around it21:16
Arkady_KanevskyI think we can submit high level blueproints to each affected projects and developers will help provide details and feel specs for it.21:17
carolbarrett_arkady_kanevsky: I think we all agree that the PWG is not the right group to do that...but the way cross-projects spec are defined today, we would need to do that.21:17
sgordonArkady_Kanevsky, how would you frame it?21:17
sgordonArkady_Kanevsky, it seems like a valid concern21:17
carolbarrett_shamail +121:17
*** gyee has quit IRC21:17
sgordonArkady_Kanevsky, instead what should be happening is product wg participants assign developer resources to write the specs21:17
Arkady_Kanevsky<sgordon> +121:17
*** ccamacho has joined #openstack-meeting-alt21:18
shamailsgordon: +121:18
carolbarrett_and what forum do they user for that? Cross Project Team?21:18
leong+121:18
shamailbut cross-project is still useful for coordination in the community21:18
shamailcoordinate overall need as a cross-project spec, develop project level specs/blueprints to realize the work needed in each project.21:18
Arkady_Kanevskyfirst we work in cross-project team to identify each effected projects for user story21:18
sgordoncarolbarrett_, if it is cross project - then yes21:18
sgordoncarolbarrett_, that is after all what they do now21:18
Arkady_KanevskyThen to blueprints and dedicated resourecs21:19
shamailThis wouldn’t be done by the PWG itself but rather the developers working as the implementation team for the user story on behalf of the PWG21:19
sgordoncarolbarrett_, e.g. that is why the instance HA spec proposal already exists21:19
sgordonshamail +121:19
Arkady_Kanevskywe need to get instance HA to all projects.21:19
carolbarrett_sgordon: I agree that the Cross Project Team seems like the right place to do it...today, their requirements only allow specs to be defined where the functionality exists in a project - not something new to all projects21:20
*** julim has quit IRC21:20
sgordonthere is of course still room for use cases, but if we cant identify devs to write the specs - then frankly that is the least of our worries21:20
Arkady_Kanevskyall effected projects. Nova is the start21:20
*** amitgandhinz has quit IRC21:20
carolbarrett_No problem on writing specs, if we can get a forum that supports it.21:20
shamail#link https://review.openstack.org/#/c/295940/21:20
carolbarrett_thanks shamail21:20
sgordonwhere that forum is not cross-project then it is the individual projects21:21
shamailthingee has updated the new definition to include new features as well (but we still need to figure out how much of the concept needs to be designed)21:21
shamailsgordon: +121:21
Arkady_KanevskyWe have 2 flows. One from projects where they start the work. Then we create user story and with cross-project team fill the gaps for other effecte dprojects21:21
*** KrishR has joined #openstack-meeting-alt21:21
sgordoni dont see a model where the projects will sign up to be told what to do functionality wise from a central point21:21
Arkady_Kanevskydown-> up->down21:21
sgordonthat is not really the way the governance is structure21:21
sgordond21:21
*** neiljerram has quit IRC21:21
shamailThere are two types of cross project needs: 1) capabilities that could benefit all projects equally (rolling upgrades) 2) capabilities that need a sub-set of projects to work together (e.g. neutron + ironic integration)21:21
*** reedip_ has quit IRC21:22
carolbarrett_sgordon - to me, it's about how we design/architect new capabilities into OpenStack so they are resilient, scalable and consistent21:22
Arkady_KanevskyAnother flow from user/product WGs pridyuct wg-> corss-> projects (down all the way)21:22
sgordoncarolbarrett_, sure but if we dont have contributors to each project to actually do the work (yes including writing per-project specs) then it seems kind of moot to me21:22
shamailIf the entire scope of the work can be completed in a single project then we should only need a spec for the project, but this also goes against the types of needs PWG wants to focus on (multi-project, multi-release)21:23
Arkady_Kanevskydo we need a usre story it is in a single project?21:23
carolbarrett_sgordon - True, but I believe we (cross-PWG companies) have the resources21:23
Arkady_Kanevskyleave it to project. Maybe help them prioritize requests.21:23
shamailWe need the ability to use cross project specs as a way to do “open design” for these multi-project/cross-project items21:23
sgordoncarolbarrett_, yes which is what i am saying - i dont see why then there is an issue with writing specs where they actually belong21:23
carolbarrett_This is the discussion we want to have in the cross project session - I hope you all are planning to attend that21:23
carolbarrett_#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/947721:24
carolbarrett_and help shape the direction21:24
shamailsgordon: There would also be a spec at the project but if there are dependencies across projects then wouldn’t it make sense to coordinate at that level and then each team go do their piece of it?21:24
Arkady_Kanevskycarol - excellent call.21:24
*** cloudtrainme has quit IRC21:24
sgordonshamail, co-ordination does not require a spec anywhere21:25
sgordonshamail, co-ordination happens today21:25
carolbarrett_we need to move on - lots more content to cover. Do we want to setup a call to review the BoD/TC slides later this week?21:25
Arkady_Kanevskycaril +121:25
sgordonshamail, it seems like what is desired is somewhere to put a central spec to make it "official" so folks can *tell* projects what to do21:25
shamailindeed but having one helps everyone align on the needs and gives transparency to non-developers as well21:25
Arkady_Kanevskycarol +1 on slides reveiw21:25
carolbarrett_#action carol to send out doodle to set time to review BoD/TC slides this week.21:26
carolbarrett_sgordon - interested to discuss further, not trying to cut it off.21:26
shamailsgordon: we will have to be clear then that is not the intent, the intention is to have a forum to collaborate on design using cross-project as the collaboration point… cross project specs aren’t mandatory today anyway21:27
shamailWe’ll park this for now and pick up at the cross project design session, good discussion sgordon!21:27
carolbarrett_#topic Content for Cross-Project Design Session21:27
*** openstack changes topic to "Content for Cross-Project Design Session (Meeting topic: Product Working Group)"21:27
carolbarrett_here's the link again21:27
carolbarrett_#link: https://www.openstack.org/summit/austin-2016/summit-schedule/events/947721:28
carolbarrett_There's also a session on splitting the design summit right after that21:28
carolbarrett_#link  https://www.openstack.org/summit/austin-2016/summit-schedule/events/947821:28
Arkady_Kanevskyfor story prioritization do we want to point to google forms (https://docs.google.com/forms/d/1P0yNXuvdAI5BVUe6y7EINPks_3l6VFkJ8Ty_QLWz4rs/edit?usp=forms_home&ths=true#responses) or to speradsheet?21:28
carolbarrett_who thinks they will be able to join the 1st session?21:28
shamailcarolbarrett_: I can make it.21:29
carolbarrett_excellent! Others ?21:29
sgordoni had both on my schedule assuming nobody schedules a meeting over it21:29
*** edtubill has quit IRC21:29
leongi will try to21:29
carolbarrett_sgordon - great!21:29
carolbarrett_Leong - Thanks!21:29
Arkady_Kanevskyhave it on my calendar - but maybe prevented by customer meetings21:29
*** jecarey has quit IRC21:30
carolbarrett_I'll be there too - so it sounds like we should have good participation21:30
*** tinbar has quit IRC21:30
carolbarrett_Will you all be able to stay for the design summit split discussion too?21:30
*** leong_ has joined #openstack-meeting-alt21:31
carolbarrett_really? no one?21:31
Arkady_KanevskyI have conflict at that time.21:31
shamailI am21:32
carolbarrett_shamail +121:32
nateziemannshamail, will you be there for IBM?  I'm booked in sponsor track + prepping VIP event at StackCity Party21:32
Arkady_KanevskyAnd frankly I feel that that decision was made already irrespective of the consequences...21:32
shamailI was answering for both earlier21:32
carolbarrett_I'm planning to be there too.21:32
shamailnateziemann: yeah, already had it on my calendar21:32
*** dukhlov has quit IRC21:32
nateziemanngreat, thnx.21:32
*** reldan has quit IRC21:32
carolbarrett_OK - We'll use the TC/BoD slides to frame up the 1st session discussion and participate in the 2nd.21:33
carolbarrett_let's move on21:33
sgordontheoretically i am attending that session as well21:33
carolbarrett_sgordon +121:33
sgordoni have to see how many clashes i gave myself when i load it up in one view21:33
carolbarrett_#topic Agenda review for Product WG working session21:33
*** openstack changes topic to "Agenda review for Product WG working session (Meeting topic: Product Working Group)"21:33
carolbarrett_#link  https://etherpad.openstack.org/p/PWG_Austin_Working_Session_Planning21:33
*** leong has quit IRC21:33
carolbarrett_that's our planning ether pad21:33
carolbarrett_the session info is21:33
carolbarrett_#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/835821:34
*** dukhlov has joined #openstack-meeting-alt21:34
sgordonare these other sessions meant to also have pads?21:34
sgordone.g. https://www.openstack.org/summit/austin-2016/summit-schedule/events/9477 doesnt seem to21:34
Arkady_Kanevskylock friday session on my agenda.21:34
Arkady_KanevskyWe are a bit short on new projects involvement21:35
carolbarrett_sgordon - which sessions are you referring to?21:35
Arkady_Kanevsky https://www.openstack.org/summit/austin-2016/summit-schedule/events/835821:35
carolbarrett_arkady_kanevksy: as soon as we settle on the agenda I'll post a link to the etherpad21:36
*** spzala has joined #openstack-meeting-alt21:36
*** spzala has quit IRC21:36
*** spzala has joined #openstack-meeting-alt21:36
*** zeih_ has joined #openstack-meeting-alt21:36
carolbarrett_What do people think of the 5 topics we have for our 4 hr working session?21:36
sgordoncarolbarrett_, the one i linked for example21:36
shamailsgordon: here is the etherpad for the cross project design summits (https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Cross-Project_workshops)21:36
shamailThey just didn’t include it in the description21:37
carolbarrett_#link https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Cross-Project_workshops21:37
carolbarrett_it came out on the ML21:37
leong_i think the agenda is sufficient for the 4-hr session, and always leave an "open"21:37
carolbarrett_leong +121:38
*** ddieterly[away] is now known as ddieterly21:38
Arkady_Kanevskywe need a separate etherpad for friday working session - with its agenda in it. We can add it to session (as all other projects do)21:38
Arkady_Kanevskyadd to session decsription21:38
carolbarrett_arkady_kanesvsky: will do after we finalize today21:39
Arkady_Kanevsky+121:39
carolbarrett_any other feedback on the agenda?21:39
shamailnone from me21:39
*** zeih has quit IRC21:40
carolbarrett_ok, moving on...21:40
carolbarrett_#topic BoF Session21:40
*** openstack changes topic to "BoF Session (Meeting topic: Product Working Group)"21:40
carolbarrett_#link21:40
*** jungleboyj has quit IRC21:40
*** leong_ is now known as leong21:40
carolbarrett_#link https://docs.google.com/presentation/d/1sv6ipcZ97mVBMRM70pLWK6c8mowXCQ8ntCSzTEkB4oc/edit#slide=id.p321:40
carolbarrett_that's the content21:40
carolbarrett_this is the session21:40
*** reldan has joined #openstack-meeting-alt21:40
*** zeih_ has quit IRC21:40
carolbarrett_#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/904121:40
carolbarrett_It's a short overview of the WG, who we are, what we do - want to bring new members into our WG21:41
carolbarrett_comments?21:41
Arkady_Kanevskyslide 4 - lets emphasis open process. google forms votes. email for votes - part of OOOO process21:41
carolbarrett_+121:42
shamailWho will be at the BoF?21:42
Arkady_Kanevskywaht about roadmaps & CPL?21:42
*** dimtruck is now known as zz_dimtruck21:42
carolbarrett_I'll be there21:42
shamailcarolbarrett_: I removed Hitachi from the BoD deck logo slide21:43
carolbarrett_arkady_kanevsky: that's on slide 421:43
*** gyee has joined #openstack-meeting-alt21:43
shamailThey participate in EWG but not PWG21:43
*** matrohon has quit IRC21:43
carolbarrett_shamail - OK, will do here too.21:43
shamailthanks21:43
*** mageshgv has quit IRC21:43
Arkady_Kanevskysldie 4 need feedback from status back to user story21:44
carolbarrett_will update that work flow to be the same as the BoD/TC one21:44
shamailcarolbarrett_: +121:44
Arkady_Kanevskywith clear steps to closure of usre story (upon completion)21:44
carolbarrett_OK - If you have other feedback, feel free to put comments on slides. We will want to finalize by Thursday.21:45
leonglooks good to me21:45
carolbarrett_I'd like to move to the Community Roadmap21:45
shamailon slide 5 (user stories)… does it make sense to also include the overall user story count and link to either gerrit or specs.openstack.org?21:45
*** sgotliv_ has quit IRC21:46
shamailThis way people can see the overall number and topics as well to see if they have interest in any existing ones21:46
*** edtubill has joined #openstack-meeting-alt21:46
shamailsgordon: Are the ones submitted by yourself and Callum aligned with any OPNFV stories?21:46
shamailIt would be good to call out that alignment for them I think21:46
sgordonshamail, they are individual contributions21:47
*** matrohon has joined #openstack-meeting-alt21:47
shamailalright, thanks!21:47
sgordonshamail, some of them may or may not have also been submitted to OPNFV but i can not claim alignment21:47
carolbarrett_shamail: I will make the additions21:47
Arkady_Kanevskysuggest renaming Tempest to QA. It will cover all 14 QA projects including tempest and Grenade21:47
shamailcarolbarrett_: thanks21:47
sgordonshamail, OPNFV folks are working directly in the community21:47
sgordonshamail, OPNFV requirements project -> openstack project21:47
carolbarrett_#topic Community Roadmap21:47
shamailsgordon: yep, I was trying to determine if these are from OPNFV or individual. You answered my question, thanks21:48
*** openstack changes topic to "Community Roadmap (Meeting topic: Product Working Group)"21:48
carolbarrett_Shamail - Can you take this?21:48
Arkady_Kanevskyno slide #s hard to refer to slides21:48
shamailSure21:48
*** travisb has quit IRC21:48
shamailCan you please link the content carolbarrett_ ?21:48
Arkady_KanevskyLet's sync themes slide to the one pete and I created21:48
shamailI don’t have the link handy21:48
carolbarrett_#link  https://drive.google.com/open?id=0B_yCSDGnhIbzTDZTN1lwT3A1M1E21:49
carolbarrett_sure21:49
shamailcarolbarrett_: thanks!21:49
Arkady_Kanevskyshamai, thanks for updating 1000ft view to include QA21:49
shamailThe community roadmap documents all of data that we collected for the most recent refresh of the roadmap.  I took all of the items from the 100 ft views and added them to themes to create the 1000 ft views.  The 10,000 ft view shows which projects had work against which themes in each release.21:50
shamailnp Arkady_Kanevsky21:50
shamailAny questions on the content?  We will be reviewing it on the roadmap sub-team meeting tomorrow at 1800 UTC (2P ET)21:50
Arkady_Kanevskyshould we split managability into managability and user experience. The latter is the theme in board presentation.21:50
shamailPlease email me if you do not have an invite to that meeting but would like to participate in the content review21:50
*** reldan has quit IRC21:51
Arkady_KanevskyShamail - feel that we need to align roadmap and themes presentations21:51
shamailArkady_Kanevsky: I think the next release (after this) will probably include more themes and break down manageability into more consumable themes21:51
*** sdake has quit IRC21:51
shamailFor this version, we will stick with the ones we have been using but will use the feedback from your themes session to revisit the topic for the next refresh21:51
Arkady_Kanevskylet's cross reference 2 presentations21:51
carolbarrett_shamail +121:51
Arkady_Kanevskythey need to be consistent21:51
shamailThis deck will not be presented at the summit21:52
shamailit will be posted to openstack.org/roadmap after we finalize it21:52
carolbarrett_arkady_Kanevsky: will you be able to attend the roadmap team meeting tomorrow?21:52
carolbarrett_Let's look at the roadmap session content next21:52
shamailI am thinking about sending the link to the final draft to all of the PTLs just to ensure they agree with how we categorize features into themes21:52
Arkady_Kanevskycan you send me invite? do not have on my calendar21:52
shamailI will probably do that after the roadmap sub-team meeting tomorrow21:53
carolbarrett_shamail +121:53
carolbarrett_#topic Community Roadmap Session Content21:53
*** openstack changes topic to "Community Roadmap Session Content (Meeting topic: Product Working Group)"21:53
carolbarrett_#link:  https://drive.google.com/open?id=1OVDC9-u4fVM_XcfskMiVVutfsUHQO_gyML12u7_Ljis21:53
carolbarrett_That's the current draft of the content21:53
carolbarrett_the session info is here21:53
carolbarrett_#link  https://www.openstack.org/summit/austin-2016/summit-schedule/events/902921:53
Arkady_Kanevskydo we present https://drive.google.com/open?id=0B_yCSDGnhIbzTDZTN1lwT3A1M1E there?21:53
*** IlyaG has joined #openstack-meeting-alt21:54
*** ddieterly is now known as ddieterly[away]21:54
Arkady_KanevskyI see it is subset of roadmap for the wiki21:54
Arkady_Kanevskyneed to update slide 5 Tempest-> QA21:55
carolbarrett_It is a subset of the slides.21:55
carolbarrett_Purpose is to educate people that a roadmap exists and what it contains and then to cover some of the Mitaka highlights21:55
shamailcarolbarrett_: you’ll be reviewing this content on the roadmap call as well right or will you schedule a separate review call?21:56
*** muralia has quit IRC21:56
carolbarrett_Would like to do it in the Roadmap call if you can fit us in21:56
*** amrith is now known as _amrith_21:56
shamailWe can fit it in, 30 min each :)21:56
*** muralia has joined #openstack-meeting-alt21:56
carolbarrett_perfect21:57
carolbarrett_Ok - let's move on21:57
Arkady_Kanevskyhow do you want to get feedback on all these presentations?21:57
*** mageshgv has joined #openstack-meeting-alt21:57
carolbarrett_either in the meeting tomorrow or email21:57
Arkady_Kanevskysend to team mail reflector with pointer to the decK?21:57
carolbarrett_Arkady_kanevsky - do you have slides for the Themes presentation to review?21:57
shamailFor community roadmap: either on the call tomorrow or by email (if you review slides but cant make the call).. please send all feedback no later than 4/2021:57
Arkady_Kanevskythanks21:58
*** tonytan4ever has quit IRC21:58
*** bana_k has joined #openstack-meeting-alt21:58
Arkady_Kanevskyfinal topic - https://docs.google.com/presentation/d/1jAtkJVMYua7v9t0gaHJbwFMIvg-AuRLiDPzyX5f3YRg/edit#slide=id.g129bd00c3d_3_921:58
Arkady_Kanevskystill in draft. looking for feedback.21:58
carolbarrett_#topic Themes update session review21:58
*** openstack changes topic to "Themes update session review (Meeting topic: Product Working Group)"21:58
Arkady_Kanevskywill sync up with Shamail to align common slides21:58
carolbarrett_#link https://docs.google.com/presentation/d/1jAtkJVMYua7v9t0gaHJbwFMIvg-AuRLiDPzyX5f3YRg/edit#slide=id.g129bd00c3d_3_921:58
Arkady_Kanevskydrop presentors?21:59
carolbarrett_on slide 2 - it says the content is from 10/2015, are you going to update to the newer stuff?21:59
Arkady_Kanevskyyes.21:59
Arkady_Kanevskywill sync up to Shamail slide21:59
Arkady_Kanevskyditto for slide 421:59
Arkady_Kanevskymeat starts from slide 622:00
carolbarrett_for slide 8 - is that User Experience theme a proposal for discussion in that session?22:00
*** fawadkhaliq has quit IRC22:00
Arkady_KanevskyYES22:00
shamailArkady_Kanevsky: I was hoping that we would solicit the attendees for future themes22:00
*** leong has quit IRC22:00
Arkady_Kanevsky7->8->9 transformation, discussion and feedback from audience22:01
shamailsuggest a few and then ask for more22:01
shamailawesome22:01
carolbarrett_Good! I like slides 10 and 11 too22:01
Arkady_Kanevskyshamail - that is slide 9.22:01
Arkady_Kanevskywill add explicit ask for other themese22:01
carolbarrett_It seems like a lot of slides for a 40 min session where you want lots of discussion...22:02
carolbarrett_maybe include just 2 of the 1K foot views22:02
Arkady_Kanevskywill drop most of them after 12.22:02
carolbarrett_Sounds good22:02
*** cknight has joined #openstack-meeting-alt22:02
Arkady_Kanevskyone slide for sample of 1000ft view and ask to attend Tu session22:02
carolbarrett_Folks we're over time and need to give this channel up22:03
Arkady_Kanevskythanks and bye22:03
carolbarrett_Arkady_Kanevsky - will you send draft to ML for review?22:03
shamailThanks everyone!22:03
carolbarrett_Next IRC meeting will be 5/9 - see you in Austin22:03
MeganRthank you - see you in Austin!22:03
carolbarrett_#endmeeting22:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:03
openstackMeeting ended Mon Apr 18 22:03:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-04-18-21.03.html22:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-04-18-21.03.txt22:03
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-04-18-21.03.log.html22:03
Arkady_Kanevskysee you all in Austin - my home town22:03
*** MeganR has quit IRC22:03
*** shamail has quit IRC22:04
*** ccamacho has quit IRC22:05
*** jecarey has joined #openstack-meeting-alt22:07
*** nikhil_k has joined #openstack-meeting-alt22:07
*** neelashah has quit IRC22:08
*** pmalik_ is now known as pmalik22:09
*** ccamacho has joined #openstack-meeting-alt22:11
*** _amrith_ is now known as amrith22:11
*** nikhil_k has quit IRC22:11
*** jecarey has quit IRC22:12
*** hichihara has quit IRC22:14
*** dronshaw has quit IRC22:15
*** pt_15 has quit IRC22:16
*** nateziemann has quit IRC22:16
*** ddieterly[away] is now known as ddieterly22:16
*** ninag has joined #openstack-meeting-alt22:17
*** tpsilva has quit IRC22:17
*** ninag has quit IRC22:19
*** ninag has joined #openstack-meeting-alt22:19
*** dave-mccowan has quit IRC22:19
*** Sukhdev has quit IRC22:20
*** ddieterly is now known as ddieterly[away]22:20
*** sigmavirus24 is now known as sigmavirus24_awa22:20
*** MarkAtwood has quit IRC22:21
*** reldan has joined #openstack-meeting-alt22:22
*** spotz is now known as spotz_zzz22:23
*** ddieterly[away] is now known as ddieterly22:26
*** hichihara has joined #openstack-meeting-alt22:26
*** matrohon has quit IRC22:27
*** tango has joined #openstack-meeting-alt22:27
*** yamahata has quit IRC22:27
*** markvoelker has quit IRC22:28
*** Adri2000 has quit IRC22:29
*** vgridnev_ has quit IRC22:30
*** ihrachys has quit IRC22:31
*** ddieterly is now known as ddieterly[away]22:31
*** tango has quit IRC22:32
*** yamahata has joined #openstack-meeting-alt22:34
*** ddieterly[away] is now known as ddieterly22:35
*** ddieterly is now known as ddieterly[away]22:42
*** ddieterly[away] is now known as ddieterly22:44
*** eliqiao_ has joined #openstack-meeting-alt22:44
*** eliqiao has quit IRC22:45
*** sdague has quit IRC22:45
*** cknight has quit IRC22:50
*** ddieterly is now known as ddieterly[away]22:51
*** sdague has joined #openstack-meeting-alt22:57
*** ddieterly[away] is now known as ddieterly23:04
*** ddieterly is now known as ddieterly[away]23:04
*** ddieterly[away] has quit IRC23:04
*** doug-fish has quit IRC23:06
*** mageshgv has quit IRC23:07
*** xyang1 has quit IRC23:07
*** cknight has joined #openstack-meeting-alt23:08
*** MarkAtwood has joined #openstack-meeting-alt23:12
*** cknight has quit IRC23:12
*** EricGonc_ has joined #openstack-meeting-alt23:13
*** EricGonczer_ has quit IRC23:13
*** edwardb has joined #openstack-meeting-alt23:14
*** carolbarrett_ has quit IRC23:14
*** Sukhdev has joined #openstack-meeting-alt23:15
*** IlyaG has quit IRC23:17
*** edwardb has quit IRC23:19
*** reldan has quit IRC23:21
*** dukhlov has quit IRC23:21
*** zz_dimtruck is now known as dimtruck23:22
*** bana_k has quit IRC23:23
*** kszukielojc has quit IRC23:24
*** stingaci has quit IRC23:26
*** MarkBaker has joined #openstack-meeting-alt23:27
*** rsyed is now known as rsyed_away23:27
*** EricGonc_ has quit IRC23:27
*** edwardb has joined #openstack-meeting-alt23:28
*** markvoelker has joined #openstack-meeting-alt23:28
*** mickeys has joined #openstack-meeting-alt23:29
*** stingaci has joined #openstack-meeting-alt23:29
*** tango has joined #openstack-meeting-alt23:31
*** reldan has joined #openstack-meeting-alt23:31
*** amrith is now known as _amrith_23:33
*** markvoelker has quit IRC23:33
*** edtubill has quit IRC23:33
*** Adri2000 has joined #openstack-meeting-alt23:33
*** Adri2000 has quit IRC23:33
*** Adri2000 has joined #openstack-meeting-alt23:33
*** mickeys has quit IRC23:34
*** ddieterly has joined #openstack-meeting-alt23:35
*** ddieterly is now known as ddieterly[away]23:35
*** kei_yama has joined #openstack-meeting-alt23:35
*** salv-orlando has quit IRC23:35
*** tango has quit IRC23:35
*** MarkAtwood has quit IRC23:36
*** ddieterly[away] is now known as ddieterly23:37
*** Arkady_Kanevsky has quit IRC23:47
*** s3wong has quit IRC23:47
*** asingh has quit IRC23:48
*** asingh has joined #openstack-meeting-alt23:48
*** ddieterly has quit IRC23:53

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