Monday, 2016-02-01

*** dims_ has joined #openstack-meeting-alt00:02
*** salv-orlando has quit IRC00:03
*** dims has quit IRC00:05
*** vilobhmm11 has joined #openstack-meeting-alt00:07
*** tpeoples has quit IRC00:08
*** ogelbukh_ has quit IRC00:08
*** tkhno has quit IRC00:08
*** kgalanov has quit IRC00:08
*** evgenyl has quit IRC00:08
*** dklenov has quit IRC00:08
*** ogelbukh_ has joined #openstack-meeting-alt00:09
*** tkhno has joined #openstack-meeting-alt00:09
*** evgenyl has joined #openstack-meeting-alt00:09
*** kgalanov has joined #openstack-meeting-alt00:10
*** ihrachys has quit IRC00:10
*** tpeoples has joined #openstack-meeting-alt00:10
*** dklenov has joined #openstack-meeting-alt00:11
*** nug has joined #openstack-meeting-alt00:11
*** gnarld_ has joined #openstack-meeting-alt00:11
*** gnarld_ is now known as cFouts00:12
*** GheRivero has quit IRC00:12
*** ChrisPriceAB has quit IRC00:12
*** GheRivero has joined #openstack-meeting-alt00:12
*** ChrisPriceAB has joined #openstack-meeting-alt00:12
*** agordeev has quit IRC00:12
*** agordeev has joined #openstack-meeting-alt00:13
*** DuncanT has quit IRC00:15
*** ChrisPriceAB has quit IRC00:16
*** evgenyl has quit IRC00:16
*** ChrisPriceAB has joined #openstack-meeting-alt00:16
*** DuncanT has joined #openstack-meeting-alt00:16
*** evgenyl has joined #openstack-meeting-alt00:17
*** sgotliv has quit IRC00:19
*** Sukhdev has joined #openstack-meeting-alt00:28
*** bana_k has joined #openstack-meeting-alt00:28
*** rmoe_ has joined #openstack-meeting-alt00:31
*** rmoe has quit IRC00:31
*** ihrachys has joined #openstack-meeting-alt00:36
*** woodster_ has quit IRC00:36
*** ihrachys has quit IRC00:39
*** markvoelker has joined #openstack-meeting-alt00:46
*** kei_yama has quit IRC00:46
*** neilus has joined #openstack-meeting-alt00:48
*** kebray has joined #openstack-meeting-alt00:49
*** salv-orlando has joined #openstack-meeting-alt00:49
*** baojg has quit IRC00:50
*** baojg has joined #openstack-meeting-alt00:50
*** markvoelker has quit IRC00:50
*** outofmemory is now known as reedip00:51
*** neilus has quit IRC00:52
*** baojg has quit IRC00:55
*** hogepodge has quit IRC00:56
*** hogepodge has joined #openstack-meeting-alt00:59
*** kzaitsev_mb has quit IRC01:00
*** hoangcx has joined #openstack-meeting-alt01:00
*** ihrachys has joined #openstack-meeting-alt01:01
*** markmcclain has quit IRC01:02
*** vilobhmm11 has quit IRC01:03
*** dims_ has quit IRC01:04
*** markmcclain has joined #openstack-meeting-alt01:05
*** HenryG_ is now known as HenryG01:08
*** banix has joined #openstack-meeting-alt01:18
*** salv-orlando has quit IRC01:23
*** markmcclain has quit IRC01:43
*** ashleighfarnham has joined #openstack-meeting-alt01:44
*** markmcclain has joined #openstack-meeting-alt01:45
*** salv-orlando has joined #openstack-meeting-alt01:45
*** markvoelker has joined #openstack-meeting-alt01:47
*** ashleighfarnham has quit IRC01:49
*** markvoelker has quit IRC01:52
*** boris-42 has quit IRC01:53
*** yamamoto has joined #openstack-meeting-alt01:54
*** bana_k has quit IRC01:57
*** tonytan4ever has joined #openstack-meeting-alt02:00
*** yamamoto has quit IRC02:00
*** baoli has joined #openstack-meeting-alt02:02
*** dims has joined #openstack-meeting-alt02:02
*** houming has joined #openstack-meeting-alt02:04
*** baoli has quit IRC02:04
*** baojg has joined #openstack-meeting-alt02:06
*** zhurong has joined #openstack-meeting-alt02:07
*** balajiiyer has joined #openstack-meeting-alt02:08
*** tonytan_brb has joined #openstack-meeting-alt02:10
*** dims has quit IRC02:12
*** tonytan4ever has quit IRC02:12
*** dims has joined #openstack-meeting-alt02:12
*** tonytan4ever has joined #openstack-meeting-alt02:13
*** dims has quit IRC02:13
*** tonytan_brb has left #openstack-meeting-alt02:17
*** vilobhmm11 has joined #openstack-meeting-alt02:17
*** salv-orlando has quit IRC02:17
*** tfukushima has joined #openstack-meeting-alt02:17
*** tonytan4ever has quit IRC02:18
*** tonytan4ever has joined #openstack-meeting-alt02:18
*** tonytan4ever has quit IRC02:19
*** tonytan4ever has joined #openstack-meeting-alt02:19
*** kebray has quit IRC02:22
*** Sukhdev has quit IRC02:22
*** Sukhdev has joined #openstack-meeting-alt02:23
*** tonytan_brb has joined #openstack-meeting-alt02:23
*** yamamoto has joined #openstack-meeting-alt02:23
*** ihrachys has quit IRC02:24
*** baoli has joined #openstack-meeting-alt02:27
*** yamamoto has quit IRC02:28
*** MarkAtwood has joined #openstack-meeting-alt02:28
*** MarkAtwood has quit IRC02:29
*** houming has quit IRC02:29
*** baoli has quit IRC02:33
*** vilobhmm11 has quit IRC02:33
*** bana_k has joined #openstack-meeting-alt02:35
*** houming has joined #openstack-meeting-alt02:35
*** neilus has joined #openstack-meeting-alt02:36
*** minwang2 has quit IRC02:37
*** tonytan4ever has quit IRC02:37
*** boris-42 has joined #openstack-meeting-alt02:38
*** MarkAtwood has joined #openstack-meeting-alt02:38
*** neilus has quit IRC02:41
*** salv-orlando has joined #openstack-meeting-alt02:42
*** harshs has joined #openstack-meeting-alt02:48
*** gcb has joined #openstack-meeting-alt02:49
*** balajiiyer has quit IRC02:52
*** banix has quit IRC02:53
*** gcb has quit IRC02:55
*** jecarey has joined #openstack-meeting-alt02:55
*** shashank_hegde has joined #openstack-meeting-alt02:57
*** tonytan_brb has quit IRC02:59
*** tonytan4ever has joined #openstack-meeting-alt03:00
*** coolsvap|away is now known as coolsvap03:02
*** neelashah has joined #openstack-meeting-alt03:02
*** tonytan4ever has quit IRC03:11
*** gcb has joined #openstack-meeting-alt03:12
*** banix has joined #openstack-meeting-alt03:17
*** Sukhdev has quit IRC03:22
*** Sukhdev has joined #openstack-meeting-alt03:23
*** salv-orlando has quit IRC03:26
*** tfukushima has quit IRC03:32
*** yamamoto_ has joined #openstack-meeting-alt03:33
*** tfukushima has joined #openstack-meeting-alt03:34
*** shwetaap has joined #openstack-meeting-alt03:36
*** tfukushima has quit IRC03:36
*** gongysh_ has joined #openstack-meeting-alt03:38
*** tfukushima has joined #openstack-meeting-alt03:42
*** tfukushima has quit IRC03:47
*** markvoelker has joined #openstack-meeting-alt03:47
*** tfukushima has joined #openstack-meeting-alt03:49
*** markvoelker has quit IRC03:52
*** MarkAtwood has quit IRC03:54
*** spags has joined #openstack-meeting-alt03:56
*** spags has quit IRC04:00
*** shwetaap1 has joined #openstack-meeting-alt04:01
*** vilobhmm11 has joined #openstack-meeting-alt04:05
*** shwetaap has quit IRC04:05
*** kebray has joined #openstack-meeting-alt04:08
*** houming_ has joined #openstack-meeting-alt04:24
*** salv-orlando has joined #openstack-meeting-alt04:24
*** neilus has joined #openstack-meeting-alt04:24
*** houming has quit IRC04:25
*** houming_ is now known as houming04:25
*** Sukhdev_ has joined #openstack-meeting-alt04:25
*** gcb has quit IRC04:26
*** julim_ has quit IRC04:26
*** shashank_hegde has quit IRC04:27
*** Sukhdev has quit IRC04:27
*** neilus has quit IRC04:29
*** Sukhdev_ has quit IRC04:29
*** kebray has quit IRC04:30
*** Sukhdev has joined #openstack-meeting-alt04:30
*** kebray has joined #openstack-meeting-alt04:30
*** tfukushima has quit IRC04:31
*** banix has quit IRC04:37
*** gcb has joined #openstack-meeting-alt04:38
*** irenab_ has joined #openstack-meeting-alt04:40
*** yonglihe has quit IRC04:42
*** irenab has quit IRC04:43
*** irenab_ is now known as irenab04:43
*** achanda has quit IRC04:44
*** Sukhdev has quit IRC04:44
*** baoli has joined #openstack-meeting-alt04:45
*** minwang2 has joined #openstack-meeting-alt04:46
*** Sukhdev has joined #openstack-meeting-alt04:48
*** neelashah has quit IRC04:49
*** baoli has quit IRC04:50
*** zz_dimtruck is now known as dimtruck04:51
*** achanda has joined #openstack-meeting-alt04:55
*** amotoki has joined #openstack-meeting-alt04:58
*** amotoki has quit IRC04:58
*** shwetaap1 has quit IRC05:00
*** hyamauchi has joined #openstack-meeting-alt05:01
*** shwetaap has joined #openstack-meeting-alt05:03
*** Poornima has joined #openstack-meeting-alt05:04
*** salv-orlando has quit IRC05:06
*** hyamauchi has quit IRC05:06
*** tfukushima has joined #openstack-meeting-alt05:08
*** tfukushima has quit IRC05:09
*** amotoki has joined #openstack-meeting-alt05:10
*** tfukushima has joined #openstack-meeting-alt05:11
*** bana_k has quit IRC05:16
*** salv-orlando has joined #openstack-meeting-alt05:17
*** numans has joined #openstack-meeting-alt05:20
*** amotoki has quit IRC05:33
*** amotoki has joined #openstack-meeting-alt05:34
*** salv-orlando has quit IRC05:35
*** gongysh_ has quit IRC05:36
*** rmoe_ has quit IRC05:39
*** rmoe has joined #openstack-meeting-alt05:39
*** jecarey_ has joined #openstack-meeting-alt05:40
*** coolsvap is now known as coolsvap|away05:40
*** Sukhdev has quit IRC05:41
*** jjmb1 has joined #openstack-meeting-alt05:41
*** minwang2 has quit IRC05:42
*** asaprykin_ has joined #openstack-meeting-alt05:42
*** DuncanT_ has joined #openstack-meeting-alt05:42
*** rmoe has quit IRC05:43
*** wendar_ has joined #openstack-meeting-alt05:43
*** tfukushima has quit IRC05:44
*** matt6434 has joined #openstack-meeting-alt05:44
*** gus_ has joined #openstack-meeting-alt05:45
*** gibi_ has joined #openstack-meeting-alt05:45
*** rmoe has joined #openstack-meeting-alt05:45
*** lifeless_ has joined #openstack-meeting-alt05:45
*** ashleighfarnham has joined #openstack-meeting-alt05:45
*** amotoki has quit IRC05:47
*** achanda_ has joined #openstack-meeting-alt05:47
*** tobasco_ has joined #openstack-meeting-alt05:47
*** Sukhdev has joined #openstack-meeting-alt05:47
*** rpodolyaka_ has joined #openstack-meeting-alt05:48
*** krugg_ has joined #openstack-meeting-alt05:48
*** rods_ has joined #openstack-meeting-alt05:48
*** markvoelker has joined #openstack-meeting-alt05:48
*** sarob_ has joined #openstack-meeting-alt05:48
*** vkmc- has joined #openstack-meeting-alt05:48
*** dimtruck_ has joined #openstack-meeting-alt05:48
*** leifz- has joined #openstack-meeting-alt05:48
*** jecarey has quit IRC05:49
*** DuncanT has quit IRC05:49
*** zhhuabj has quit IRC05:49
*** jjmb has quit IRC05:49
*** lifeless has quit IRC05:49
*** asaprykin has quit IRC05:49
*** kertis1 has quit IRC05:49
*** pmalik has quit IRC05:49
*** agireud has quit IRC05:49
*** shadower has quit IRC05:49
*** bswartz has quit IRC05:49
*** tobasco has quit IRC05:49
*** gibi has quit IRC05:49
*** sreshetnyak has quit IRC05:49
*** mattoliverau has quit IRC05:49
*** dimtruck has quit IRC05:49
*** gus has quit IRC05:49
*** sarob has quit IRC05:49
*** vkmc has quit IRC05:49
*** rods has quit IRC05:49
*** rpodolyaka has quit IRC05:49
*** krugg has quit IRC05:49
*** sigmavirus24_awa has quit IRC05:49
*** wendar has quit IRC05:49
*** leifz has quit IRC05:49
*** fungi has quit IRC05:49
*** krugg_ is now known as krugg05:49
*** dimtruck_ is now known as dimtruck05:49
*** rods_ is now known as rods05:49
*** vkmc- is now known as vkmc05:49
*** vkmc has joined #openstack-meeting-alt05:49
*** achanda has quit IRC05:49
*** asaprykin_ is now known as asaprykin05:49
*** sarob_ is now known as sarob05:49
*** leifz- is now known as leifz05:49
*** coolsvap|away is now known as coolsvap05:49
*** rods is now known as Guest4421705:50
*** rpodolyaka_ is now known as rpodolyaka05:50
*** ashleighfarnham has quit IRC05:50
*** pmalik has joined #openstack-meeting-alt05:50
*** DuncanT_ is now known as DuncanT05:51
*** agireud has joined #openstack-meeting-alt05:51
*** tobasco_ has quit IRC05:52
*** sreshetnyak has joined #openstack-meeting-alt05:52
*** rmoe has quit IRC05:52
*** tobasco has joined #openstack-meeting-alt05:52
*** markvoelker has quit IRC05:53
*** rmoe has joined #openstack-meeting-alt05:53
*** amotoki has joined #openstack-meeting-alt05:54
*** MarkAtwood has joined #openstack-meeting-alt05:55
*** zhhuabj has joined #openstack-meeting-alt05:56
*** sigmavirus24_awa has joined #openstack-meeting-alt05:57
*** fungi has joined #openstack-meeting-alt05:57
*** kertis has joined #openstack-meeting-alt05:58
*** rmoe has quit IRC06:00
*** vilobhmm11 has quit IRC06:01
*** minwang2 has joined #openstack-meeting-alt06:01
*** rmoe has joined #openstack-meeting-alt06:02
*** amotoki has quit IRC06:05
*** rmoe has quit IRC06:07
*** rmoe has joined #openstack-meeting-alt06:08
*** markmcclain has quit IRC06:13
*** salv-orlando has joined #openstack-meeting-alt06:13
*** amotoki has joined #openstack-meeting-alt06:14
*** markmcclain has joined #openstack-meeting-alt06:15
*** rmoe has quit IRC06:17
*** toabctl is now known as toabctl_06:17
*** rmoe has joined #openstack-meeting-alt06:19
*** kebray has quit IRC06:20
*** markmcclain has quit IRC06:21
*** dave-mccowan has quit IRC06:21
*** MarkAtwood has quit IRC06:24
*** SridharG has joined #openstack-meeting-alt06:25
*** rmoe has quit IRC06:26
*** akuznetsov has joined #openstack-meeting-alt06:28
*** harshs has quit IRC06:29
*** akuznetsov has quit IRC06:29
*** akuznetsov has joined #openstack-meeting-alt06:30
*** rossella_s has quit IRC06:31
*** rossella_s has joined #openstack-meeting-alt06:31
*** rmoe has joined #openstack-meeting-alt06:32
*** mrmartin has joined #openstack-meeting-alt06:33
*** akuznetsov has quit IRC06:35
*** rmoe has quit IRC06:37
*** rmoe has joined #openstack-meeting-alt06:39
*** markmcclain has joined #openstack-meeting-alt06:43
*** harshs has joined #openstack-meeting-alt06:45
*** _nadya_ has joined #openstack-meeting-alt06:46
*** markmcclain has quit IRC06:48
*** rmoe has quit IRC06:48
*** rmoe has joined #openstack-meeting-alt06:50
*** nkrinner has joined #openstack-meeting-alt06:54
*** tfukushima has joined #openstack-meeting-alt06:55
*** gcb has quit IRC06:56
*** salv-orlando has quit IRC06:57
*** achanda_ is now known as achanda06:57
*** rmoe has quit IRC06:57
*** harshs has quit IRC06:58
*** rmoe has joined #openstack-meeting-alt06:58
*** hyamauchi has joined #openstack-meeting-alt07:02
*** [HeOS] has quit IRC07:05
*** [HeOS] has joined #openstack-meeting-alt07:05
*** minwang2 has quit IRC07:06
*** hyamauchi has quit IRC07:06
*** neilus has joined #openstack-meeting-alt07:07
*** SridharG has quit IRC07:08
*** shwetaap has quit IRC07:08
*** gcb has joined #openstack-meeting-alt07:08
*** shwetaap has joined #openstack-meeting-alt07:08
*** salv-orlando has joined #openstack-meeting-alt07:09
*** rmoe has quit IRC07:10
*** rmoe has joined #openstack-meeting-alt07:11
*** neilus has quit IRC07:11
*** shwetaap has quit IRC07:13
*** paul-carlton1 has joined #openstack-meeting-alt07:13
*** sbalukoff has joined #openstack-meeting-alt07:15
*** markmcclain has joined #openstack-meeting-alt07:17
*** rmoe has quit IRC07:17
*** rmoe has joined #openstack-meeting-alt07:17
*** yamahata has joined #openstack-meeting-alt07:21
*** iyamahat has joined #openstack-meeting-alt07:21
*** rmoe has quit IRC07:22
*** markmcclain has quit IRC07:22
*** rmoe has joined #openstack-meeting-alt07:23
*** scheuran has joined #openstack-meeting-alt07:26
*** mrmartin has quit IRC07:26
*** j___ has joined #openstack-meeting-alt07:28
*** jtomasek has joined #openstack-meeting-alt07:32
*** vilobhmm11 has joined #openstack-meeting-alt07:32
*** rmoe has quit IRC07:33
*** rmoe has joined #openstack-meeting-alt07:34
*** salv-orlando has quit IRC07:43
*** _degorenko|afk is now known as degorenko07:46
*** safchain has joined #openstack-meeting-alt07:47
*** markvoelker has joined #openstack-meeting-alt07:49
*** vilobhmm11 has quit IRC07:50
*** SridharG has joined #openstack-meeting-alt07:50
*** rmoe has quit IRC07:50
*** rmoe has joined #openstack-meeting-alt07:51
*** shashank_hegde has joined #openstack-meeting-alt07:52
*** amotoki has quit IRC07:52
*** ttx has joined #openstack-meeting-alt07:52
*** markvoelker has quit IRC07:54
*** vilobhmm11 has joined #openstack-meeting-alt07:55
*** belmoreira has joined #openstack-meeting-alt07:55
*** egallen has joined #openstack-meeting-alt07:57
*** rmoe has quit IRC07:58
*** shashank_hegde has quit IRC07:59
*** zeih has joined #openstack-meeting-alt08:00
*** rmoe has joined #openstack-meeting-alt08:00
*** jprovazn has joined #openstack-meeting-alt08:02
*** dimtruck is now known as zz_dimtruck08:03
*** yamamoto_ has quit IRC08:05
*** gongysh has quit IRC08:06
*** salv-orlando has joined #openstack-meeting-alt08:06
*** mikelk has joined #openstack-meeting-alt08:08
*** yamamoto_ has joined #openstack-meeting-alt08:08
*** hoangcx has quit IRC08:09
*** bgaifullin has joined #openstack-meeting-alt08:09
*** c00p3r- has left #openstack-meeting-alt08:13
*** yamamoto_ has quit IRC08:13
*** rmoe has quit IRC08:14
*** mkoderer has quit IRC08:14
*** rmoe has joined #openstack-meeting-alt08:14
*** ozamiatin_ has joined #openstack-meeting-alt08:15
*** evgenyf has joined #openstack-meeting-alt08:16
*** [1]evgenyf has joined #openstack-meeting-alt08:17
*** gongysh has joined #openstack-meeting-alt08:18
*** rmoe has quit IRC08:19
*** tfukushima has quit IRC08:19
*** rmoe has joined #openstack-meeting-alt08:20
*** tfukushima has joined #openstack-meeting-alt08:20
*** evgenyf has quit IRC08:21
*** [1]evgenyf is now known as evgenyf08:21
*** yamamoto_ has joined #openstack-meeting-alt08:23
*** ozamiatin_ has quit IRC08:24
*** yamamoto_ has quit IRC08:24
*** gongysh has quit IRC08:24
*** amotoki has joined #openstack-meeting-alt08:24
*** shadower has joined #openstack-meeting-alt08:25
*** salv-orlando has quit IRC08:25
*** rcernin has joined #openstack-meeting-alt08:26
*** yamamoto_ has joined #openstack-meeting-alt08:27
*** yamamoto_ has quit IRC08:28
*** thomnico has joined #openstack-meeting-alt08:29
*** d0ugal_ has quit IRC08:30
*** d0ugal has joined #openstack-meeting-alt08:30
*** achanda has quit IRC08:31
*** rmoe has quit IRC08:33
*** amotoki has quit IRC08:33
*** vilobhmm11 has quit IRC08:33
*** rmoe has joined #openstack-meeting-alt08:33
*** iyamahat has quit IRC08:34
*** yamahata has quit IRC08:34
*** sylweste_ has joined #openstack-meeting-alt08:34
*** sylweste_ is now known as sylwesterB_08:35
*** sshnaidm has quit IRC08:35
*** coolsvap is now known as coolsvap|away08:36
*** gongysh has joined #openstack-meeting-alt08:36
*** Sukhdev has quit IRC08:36
*** achanda has joined #openstack-meeting-alt08:37
*** amotoki has joined #openstack-meeting-alt08:38
*** achanda has quit IRC08:39
*** rmoe has quit IRC08:41
*** mkoderer has joined #openstack-meeting-alt08:44
*** rmoe has joined #openstack-meeting-alt08:44
*** yamamoto_ has joined #openstack-meeting-alt08:44
*** samuelBartel has joined #openstack-meeting-alt08:45
*** yamamoto_ has quit IRC08:45
*** zz_dimtruck is now known as dimtruck08:47
*** davidlenwell has quit IRC08:47
*** yamamoto_ has joined #openstack-meeting-alt08:48
*** rmoe has quit IRC08:49
*** rmoe has joined #openstack-meeting-alt08:49
*** macsz1 has joined #openstack-meeting-alt08:50
*** yamamoto_ has quit IRC08:53
*** rmoe has quit IRC08:53
*** rmoe has joined #openstack-meeting-alt08:53
*** davidlenwell has joined #openstack-meeting-alt08:56
*** yamamoto_ has joined #openstack-meeting-alt08:56
*** dimtruck is now known as zz_dimtruck08:56
*** hoangcx has joined #openstack-meeting-alt08:58
*** sylwesterB_ has quit IRC09:01
*** rmoe has quit IRC09:02
*** rmoe has joined #openstack-meeting-alt09:03
*** yamamoto_ has quit IRC09:04
*** zhurong has quit IRC09:06
*** salv-orlando has joined #openstack-meeting-alt09:07
*** rmoe has quit IRC09:09
*** shwetaap has joined #openstack-meeting-alt09:09
*** rmoe has joined #openstack-meeting-alt09:10
*** iyamahat has joined #openstack-meeting-alt09:12
*** yamamoto_ has joined #openstack-meeting-alt09:12
*** yamamoto_ has quit IRC09:13
*** shwetaap has quit IRC09:13
*** houming has quit IRC09:19
*** macsz1 has quit IRC09:19
*** rmoe has quit IRC09:20
*** macsz1 has joined #openstack-meeting-alt09:20
*** amotoki has quit IRC09:20
*** yamamoto_ has joined #openstack-meeting-alt09:21
*** fzdarsky has joined #openstack-meeting-alt09:22
*** macsz1 has quit IRC09:22
*** houming has joined #openstack-meeting-alt09:23
*** paul-carlton1 has quit IRC09:23
*** rmoe has joined #openstack-meeting-alt09:24
*** salv-orlando has quit IRC09:27
*** MarkBaker has joined #openstack-meeting-alt09:29
*** rmoe has quit IRC09:29
*** gongysh has quit IRC09:29
*** markmcclain has joined #openstack-meeting-alt09:31
*** sshnaidm has joined #openstack-meeting-alt09:31
*** kszukielojc has joined #openstack-meeting-alt09:33
*** rmoe has joined #openstack-meeting-alt09:34
*** houming has quit IRC09:35
*** paul-carlton1 has joined #openstack-meeting-alt09:37
*** ajo has joined #openstack-meeting-alt09:37
*** houming has joined #openstack-meeting-alt09:39
*** markmcclain has quit IRC09:40
*** ajo has quit IRC09:42
*** ajo has joined #openstack-meeting-alt09:43
*** rvyalov has joined #openstack-meeting-alt09:44
*** egallen has quit IRC09:44
*** matrohon has joined #openstack-meeting-alt09:45
*** ashleighfarnham has joined #openstack-meeting-alt09:47
*** ajo has quit IRC09:48
*** ajo has joined #openstack-meeting-alt09:48
*** rmoe has quit IRC09:49
*** ajo has quit IRC09:49
*** rmoe has joined #openstack-meeting-alt09:49
*** markvoelker has joined #openstack-meeting-alt09:50
*** egallen has joined #openstack-meeting-alt09:50
*** neiljerram has joined #openstack-meeting-alt09:51
*** ashleighfarnham has quit IRC09:52
*** artem_panchenko_ has joined #openstack-meeting-alt09:52
*** ramishra_ is now known as ramishra09:53
*** markvoelker has quit IRC09:54
*** amotoki has joined #openstack-meeting-alt09:56
*** rmoe has quit IRC09:59
*** rmoe has joined #openstack-meeting-alt10:00
*** vgridnev has joined #openstack-meeting-alt10:02
*** salv-orlando has joined #openstack-meeting-alt10:03
*** zeih has quit IRC10:05
*** sc68cal__ has joined #openstack-meeting-alt10:07
*** rmoe has quit IRC10:07
*** prasa has joined #openstack-meeting-alt10:07
*** yamamoto_ has quit IRC10:08
*** rmoe has joined #openstack-meeting-alt10:08
*** neiljerram has quit IRC10:08
*** matrohon has quit IRC10:08
*** neiljerram has joined #openstack-meeting-alt10:09
*** gongysh has joined #openstack-meeting-alt10:09
*** achanda has joined #openstack-meeting-alt10:09
*** matrohon has joined #openstack-meeting-alt10:10
*** shwetaap has joined #openstack-meeting-alt10:10
*** achanda has quit IRC10:14
*** shwetaap has quit IRC10:14
*** rmoe_ has joined #openstack-meeting-alt10:14
*** rmoe has quit IRC10:16
*** gcb has quit IRC10:16
*** sc68cal__ is now known as sc68cal10:17
*** sc68cal is now known as Guest6916410:18
*** Guest69164 has quit IRC10:19
*** Guest69164 has joined #openstack-meeting-alt10:19
*** rmoe_ has quit IRC10:19
*** mrmartin has joined #openstack-meeting-alt10:20
*** ttx_ has joined #openstack-meeting-alt10:21
*** mkoderer__ has joined #openstack-meeting-alt10:22
*** hoangcx has quit IRC10:23
*** ttx has quit IRC10:23
*** rmoe has joined #openstack-meeting-alt10:24
*** tfukushima has quit IRC10:24
*** ttx_ is now known as ttx10:24
*** paul-carlton1 has quit IRC10:24
*** macsz1 has joined #openstack-meeting-alt10:25
*** tfukushima has joined #openstack-meeting-alt10:26
*** tfukushima has quit IRC10:26
*** rmoe has quit IRC10:30
*** rmoe has joined #openstack-meeting-alt10:31
*** rossella_s has quit IRC10:31
*** rossella_s has joined #openstack-meeting-alt10:32
*** gongysh has quit IRC10:33
*** artem_panchenko_ has quit IRC10:34
*** zynzel has quit IRC10:34
*** rmoe has quit IRC10:38
*** paul-carlton1 has joined #openstack-meeting-alt10:38
*** ozamiatin has quit IRC10:40
*** salv-orlando has quit IRC10:40
*** rmoe has joined #openstack-meeting-alt10:40
*** artem_panchenko_ has joined #openstack-meeting-alt10:42
*** zynzel has joined #openstack-meeting-alt10:42
*** ozamiatin has joined #openstack-meeting-alt10:42
*** tfukushima has joined #openstack-meeting-alt10:46
*** macsz1 has quit IRC10:46
*** zz_dimtruck is now known as dimtruck10:47
*** rmoe has quit IRC10:48
*** rmoe has joined #openstack-meeting-alt10:48
*** salv-orlando has joined #openstack-meeting-alt10:50
*** rmoe has quit IRC10:53
*** macsz1 has joined #openstack-meeting-alt10:56
*** rmoe has joined #openstack-meeting-alt10:56
*** macsz1 has quit IRC10:58
*** paul-carlton1 has quit IRC10:59
*** dimtruck is now known as zz_dimtruck11:01
*** baojg has quit IRC11:04
*** baojg has joined #openstack-meeting-alt11:05
*** tpsilva has joined #openstack-meeting-alt11:06
*** rmoe has quit IRC11:06
*** rmoe has joined #openstack-meeting-alt11:09
*** dims has joined #openstack-meeting-alt11:09
*** baojg has quit IRC11:09
*** achanda has joined #openstack-meeting-alt11:11
*** egallen has quit IRC11:11
*** egallen has joined #openstack-meeting-alt11:13
*** Guest69164 has quit IRC11:13
*** matt6434 is now known as mattoliverau11:14
*** rmoe has quit IRC11:14
*** rmoe has joined #openstack-meeting-alt11:15
*** iyamahat has quit IRC11:16
*** yamamoto has joined #openstack-meeting-alt11:17
*** achanda has quit IRC11:17
*** lifeless_ is now known as lifeless11:17
*** rmoe has quit IRC11:20
*** rmoe has joined #openstack-meeting-alt11:20
*** yamamoto has quit IRC11:23
*** yamamoto has joined #openstack-meeting-alt11:24
*** rmoe has quit IRC11:24
*** rmoe has joined #openstack-meeting-alt11:25
*** egallen has quit IRC11:26
*** ikutukov has joined #openstack-meeting-alt11:28
*** yamamoto has quit IRC11:28
*** gongysh has joined #openstack-meeting-alt11:28
*** yamamoto has joined #openstack-meeting-alt11:31
*** yamahata has joined #openstack-meeting-alt11:32
*** rmoe has quit IRC11:32
*** rmoe has joined #openstack-meeting-alt11:34
*** paul-carlton1 has joined #openstack-meeting-alt11:34
*** yamamoto has quit IRC11:36
*** Poornima has quit IRC11:37
*** gongysh has quit IRC11:37
*** houming has quit IRC11:38
*** rmoe has quit IRC11:40
*** rmoe has joined #openstack-meeting-alt11:42
*** zynzel has quit IRC11:44
*** zynzel has joined #openstack-meeting-alt11:44
*** rmoe has quit IRC11:47
*** rmoe has joined #openstack-meeting-alt11:50
*** markvoelker has joined #openstack-meeting-alt11:50
*** mrmartin has quit IRC11:51
*** rmoe has quit IRC11:54
*** rmoe has joined #openstack-meeting-alt11:55
*** markvoelker has quit IRC11:55
*** ikutukov has quit IRC11:56
*** prithiv has joined #openstack-meeting-alt11:59
*** rmoe has quit IRC11:59
*** rmoe has joined #openstack-meeting-alt12:01
*** prithiv has quit IRC12:01
*** salv-orl_ has joined #openstack-meeting-alt12:03
*** baoli has joined #openstack-meeting-alt12:04
*** rmoe has quit IRC12:05
*** baoli has quit IRC12:05
*** yamahata has quit IRC12:06
*** salv-orlando has quit IRC12:06
*** thomnico has quit IRC12:06
*** rmoe has joined #openstack-meeting-alt12:06
*** baoli has joined #openstack-meeting-alt12:08
*** baoli has quit IRC12:08
*** ikutukov has joined #openstack-meeting-alt12:09
*** neiljerram has quit IRC12:10
*** rmoe has quit IRC12:11
*** rmoe has joined #openstack-meeting-alt12:11
*** tellesnobrega_af is now known as tellesnobrega12:12
*** neiljerram has joined #openstack-meeting-alt12:15
*** egallen has joined #openstack-meeting-alt12:18
*** rmoe has quit IRC12:19
*** rmoe has joined #openstack-meeting-alt12:20
*** rmoe has quit IRC12:24
*** rmoe has joined #openstack-meeting-alt12:25
*** zynzel has quit IRC12:28
*** artem_panchenko_ has quit IRC12:31
*** rmoe has quit IRC12:32
*** artem_panchenko_ has joined #openstack-meeting-alt12:32
*** weshay has quit IRC12:32
*** zynzel has joined #openstack-meeting-alt12:34
*** rmoe has joined #openstack-meeting-alt12:36
*** weshay_xchat has joined #openstack-meeting-alt12:40
*** bswartz has joined #openstack-meeting-alt12:41
*** artem_panchenko_ has quit IRC12:44
*** salv-orl_ has quit IRC12:47
*** sshnaidm has quit IRC12:50
*** rmoe has quit IRC12:51
*** rmoe has joined #openstack-meeting-alt12:51
*** markvoelker has joined #openstack-meeting-alt12:51
*** artem_panchenko_ has joined #openstack-meeting-alt12:52
*** zz_dimtruck is now known as dimtruck12:52
*** weshay_xchat is now known as weshay12:52
*** baojg has joined #openstack-meeting-alt12:53
*** mrmartin has joined #openstack-meeting-alt12:53
*** markvoelker has quit IRC12:56
*** MarkAtwood has joined #openstack-meeting-alt12:56
*** rmoe has quit IRC12:57
*** rmoe has joined #openstack-meeting-alt12:57
*** mrmartin has quit IRC13:00
*** mrmartin has joined #openstack-meeting-alt13:01
*** dimtruck is now known as zz_dimtruck13:01
*** salv-orlando has joined #openstack-meeting-alt13:02
*** balajiiyer has joined #openstack-meeting-alt13:02
*** prithiv has joined #openstack-meeting-alt13:03
*** balajiiyer has quit IRC13:04
*** zeih has joined #openstack-meeting-alt13:04
*** iyamahat has joined #openstack-meeting-alt13:05
*** dims has quit IRC13:06
*** prithiv has quit IRC13:08
*** prithiv has joined #openstack-meeting-alt13:09
*** dims has joined #openstack-meeting-alt13:09
*** shwetaap has joined #openstack-meeting-alt13:10
*** xek__ is now known as xek13:12
*** markvoelker has joined #openstack-meeting-alt13:14
*** shwetaap has quit IRC13:15
*** rmoe has quit IRC13:17
*** rmoe has joined #openstack-meeting-alt13:19
*** dave-mccowan has joined #openstack-meeting-alt13:22
*** jecarey_ has quit IRC13:23
*** rmoe has quit IRC13:25
*** baoli has joined #openstack-meeting-alt13:27
*** rmoe has joined #openstack-meeting-alt13:27
*** piet has joined #openstack-meeting-alt13:30
*** grimlock86 has quit IRC13:30
*** amrith is now known as _amrith_13:35
*** egallen has quit IRC13:36
*** thomnico has joined #openstack-meeting-alt13:36
*** wznoinsk has joined #openstack-meeting-alt13:37
*** rmoe has quit IRC13:39
*** kzaitsev_mb has joined #openstack-meeting-alt13:40
*** sshnaidm has joined #openstack-meeting-alt13:41
*** egallen has joined #openstack-meeting-alt13:42
*** rmoe has joined #openstack-meeting-alt13:42
*** [HeOS] is now known as HeOS13:45
*** prithiv1 has joined #openstack-meeting-alt13:46
*** prithiv has quit IRC13:46
*** yamamoto has joined #openstack-meeting-alt13:46
*** bauzas has quit IRC13:47
*** ashleighfarnham has joined #openstack-meeting-alt13:48
*** thomnico has quit IRC13:51
*** zynzel has quit IRC13:52
*** rmoe has quit IRC13:52
*** rmoe has joined #openstack-meeting-alt13:53
*** ashleighfarnham has quit IRC13:53
*** zynzel has joined #openstack-meeting-alt13:53
*** jaypipes has joined #openstack-meeting-alt13:54
*** yamamoto has quit IRC13:55
*** sgotliv has joined #openstack-meeting-alt13:55
*** neelashah has joined #openstack-meeting-alt13:55
*** egallen has quit IRC13:56
*** egallen has joined #openstack-meeting-alt13:57
n0ano_#startmeeting nova-scheduler14:00
openstackMeeting started Mon Feb  1 14:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is n0ano_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova-scheduler)"14:00
*** rmoe has quit IRC14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
n0ano_anyone here to talk about the scheduler?14:00
edleafe\o14:00
Yingxino/14:00
n0ano_edleafe, looks like you had a long, involved meeting last week :-)14:01
*** rmoe has joined #openstack-meeting-alt14:01
edleafeit was tough, but I made it through somehow14:01
n0ano_:-)14:02
*** iyamahat has quit IRC14:03
*** yamamoto has joined #openstack-meeting-alt14:03
*** esheffield has joined #openstack-meeting-alt14:03
*** bauzas has joined #openstack-meeting-alt14:03
*** jaypipes has quit IRC14:03
n0ano_well, it's fast approaching 5 after, let's get started14:03
*** zynzel has quit IRC14:03
n0ano_#topic mid-cycle meetup report back14:03
*** zynzel has joined #openstack-meeting-alt14:03
*** openstack changes topic to "mid-cycle meetup report back (Meeting topic: nova-scheduler)"14:03
* bauzas waves14:03
n0ano_was anyone at the meetup who can comment on it?14:03
bauzasI was having some IRC bouncer issue14:03
*** sriram has joined #openstack-meeting-alt14:04
bauzasI was14:04
n0ano_bauzas, I always just blame microsoft, it's always their fault somehow.14:04
bauzasnot sure I'm the only folk here14:04
n0ano_edleafe, & I didn't make it, you might be the only one here who attended14:04
johnthetubaguyI am lurking14:04
bauzasoh snap :)14:04
bauzassooo14:05
johnthetubaguyI am writing a quick midcycle summary to the ML at the moment14:05
bauzasall the tracked records are in https://etherpad.openstack.org/p/mitaka-nova-midcycle14:05
bauzasfor the sched bits, we mostly discussed about three things14:05
*** yamamoto has quit IRC14:05
n0ano_cooo, any high points that apply to the scheduler14:05
* carl_baldwin lurking...14:06
*** rmoe has quit IRC14:06
bauzas#1 the status of all our changes => L26414:06
bauzas#2 the longest blueprint series ever, aka. jay's resource-providers14:07
bauzaset al.14:07
bauzas#3 having scheduler functional tests in-tree14:07
bauzasabout #1, we're on-board with what we promised, except check-destination-on-migrations which I'm taking it back14:07
*** yamamoto has joined #openstack-meeting-alt14:08
bauzasfor #2, it took us mostly 3 days to get it covered14:08
n0ano_but I see jay's BP finally got merged14:08
*** _gryf has joined #openstack-meeting-alt14:08
bauzasthat's very large, so I'd prefer folks lurking here to read L102 of https://etherpad.openstack.org/p/mitaka-nova-midcycle14:08
bauzasn0ano_: 2 of 714:08
*** gcb has joined #openstack-meeting-alt14:09
*** rmoe has joined #openstack-meeting-alt14:09
n0ano_we should update https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking to reflect all 7 then14:09
*** prasa has quit IRC14:09
bauzasand #3, it's totally possible to have functional tests in-tree for the scheduler like gibi_ made for servergroups14:09
*** amitgandhinz has joined #openstack-meeting-alt14:09
bauzasn0ano_: not sure it's the right etherpad, but yes to that14:10
bauzasI was more thinking of https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking14:10
bauzass/more/rather14:11
n0ano_it's the one I've been going by, as long as we have a definitive list somewhere that's what's important14:11
bauzasone point I forgot to mention is the intersection with carl_baldwin's spec for Tenant networks in Neutron14:12
*** zz_dimtruck is now known as dimtruck14:12
*** pbelamge has joined #openstack-meeting-alt14:12
bauzasthat interaction is mostly covered by https://review.openstack.org/#/c/253187/14:13
carl_baldwinThanks for the discussion there.  My spec is here:14:13
bauzasoh man14:13
* bauzas typing too fast14:13
*** prithiv1 has quit IRC14:13
bauzass/tenant networks/routed networks14:13
carl_baldwin#link https://review.openstack.org/#/c/263898/14:13
bauzasthanks14:13
*** prithiv has joined #openstack-meeting-alt14:13
bauzasthat's it for me14:14
bauzasquestions ?14:14
carl_baldwinJay added a section on it to his spec, can't remember which one of the series.14:14
*** julim has joined #openstack-meeting-alt14:14
bauzascarl_baldwin: the one I mentioned above14:14
bauzasie. 25318714:14
*** zynzel has quit IRC14:15
carl_baldwinThanks!14:15
bauzasyet subject to review14:15
n0ano_sounds like there's no major problems, just a lot of work that needs to be done14:15
*** tellesnobrega is now known as tellesnobrega_af14:15
YingxinIs there a detailed test requirement of #3? I'm interested in it.14:16
*** zynzel has joined #openstack-meeting-alt14:16
*** shwetaap has joined #openstack-meeting-alt14:16
bauzasYingxin: that has been replied by ML, lemme find it14:16
*** nelsnelson has joined #openstack-meeting-alt14:16
*** iyamahat has joined #openstack-meeting-alt14:16
Yingxinbauzas: is it http://lists.openstack.org/pipermail/openstack-dev/2016-January/085182.html ?14:17
bauzashttp://lists.openstack.org/pipermail/openstack-dev/2016-January/085107.html14:17
bauzasyup14:17
*** nelsnels_ has quit IRC14:17
*** fawadkhaliq has joined #openstack-meeting-alt14:17
bauzaswhich I totally forgot to mention, although I remember having reviewing that :=)14:17
*** fawadkhaliq has quit IRC14:18
Yingxinyes, so any idea about the requirement I drafted?14:18
n0ano_Yingxin, and you're mentioned specifically in that thread so it's great that you're still interested14:18
*** edtubill has joined #openstack-meeting-alt14:19
johnthetubaguycarl_baldwin: thanks for the updates on that, I added a few comments yesterday14:19
*** zhangjn has joined #openstack-meeting-alt14:19
Yingxinn0ano_: :)14:19
*** rsyed_away is now known as rsyed14:19
carl_baldwinjohnthetubaguy: just reading then this morning.  Thank you.14:19
*** fawadkhaliq has joined #openstack-meeting-alt14:20
*** nelsnelson has quit IRC14:20
bauzasYingxin: which draft?14:20
*** rmoe has quit IRC14:21
*** nelsnelson has joined #openstack-meeting-alt14:21
Yingxin#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085182.html14:21
Yingxinbauzas: the input output and boundary things.14:21
*** wendar_ is now known as wendar14:22
bauzasYingxin: well, I don't disagree with your email :)14:22
*** jecarey has joined #openstack-meeting-alt14:22
*** jecarey has quit IRC14:22
bauzasYingxin: what I forgot was https://github.com/openstack/nova/blob/master/nova/tests/functional/test_server_group.py14:23
*** jecarey has joined #openstack-meeting-alt14:23
Yingxinbauzas: thanks I'm looking at it14:23
bauzasmoving on ?14:23
n0ano_bauzas, looks like14:24
n0ano_#topic Specs/BPs/Patches14:24
*** openstack changes topic to "Specs/BPs/Patches (Meeting topic: nova-scheduler)"14:24
n0ano_Any of these need discussing today?14:24
YingxinI implemented a prototype as described in https://blueprints.launchpad.net/nova/+spec/eventually-consistent-scheduler-host-state and proposed a related session in Austin summit.14:24
*** rmoe has joined #openstack-meeting-alt14:25
YingxinThe prototype shows a great decision time improvement and the decreasing chances of retries. It could be a shared-state version of filter scheduler.14:25
YingxinHowever, according to bp https://review.openstack.org/#/c/271823/1/specs/mitaka/approved/resource-providers-scheduler.rst  , it will remove host-state and make claims directly to db in the future.14:25
YingxinSo I'm not sure whether I should continue this effort.14:25
n0ano_hmm, without knowing the details sounds like that's an excellent Austin topic14:26
*** kfarr has joined #openstack-meeting-alt14:26
Yingxinn0ano_: thanks14:26
n0ano_Yingxin, you can start a ML discussion if you want to get some feedback before then14:27
Yingxinok14:27
n0ano_if there's nothing else on this14:28
n0ano_#topic bugs14:28
*** openstack changes topic to "bugs (Meeting topic: nova-scheduler)"14:28
n0ano_beyond encouraging everyone to take a bug (and fix it) I have some good news14:28
bauzasYingxin: so, resource-providers-scheduler is subject to change14:29
bauzasYingxin: at least where the claims are done14:29
bauzasYingxin: I'm more concerned by how your BP could be impacting the main effort of the resource-providers epic14:29
*** banix has joined #openstack-meeting-alt14:30
*** rmoe has quit IRC14:30
Yingxinbauzas: well it can also apply to resource-providers if the scheduler needs in-memory cache14:31
*** rossella_s has quit IRC14:31
YingxinAnd when there is a requirement to have multiple scheduler instances.14:31
bauzasYingxin: I'd be interested in seeing the prototype14:31
*** rossella_s has joined #openstack-meeting-alt14:31
*** rmoe has joined #openstack-meeting-alt14:32
n0ano_Yingxin, would it be possible to post a WIP gerrit review for your prototype?14:32
Yingxinbauzas: thanks, it is only a quick prototype, no unit tests and may have naming problems14:33
bauzasYingxin: that's not really a problem :)14:33
bauzasjust mark it WIP / DNM14:34
bauzasand put the -W button14:34
YingxinI'll modify it before it is uploaded to gerrit14:34
Yingxinwell, OK14:34
YingxinThe most important thing is that it is runnable.14:34
bauzasbut if your prototype wouldn't throw the resource-providers epic under the bus, it could be interesting to see it in Newtopn14:34
*** zhangjn has quit IRC14:35
YingxinYup, so I'll continue14:36
n0ano_so, back to bugs14:37
n0ano_Intel has a large group in Austin and I've talked management into prioritizing scheduler bugs for that group, we should be getting some progress on reducing the scheduler bugs list (soon)14:37
n0ano_#topic opens14:38
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:38
n0ano_so, anyone have anything else they'd like to discuss?14:38
edleafen0ano_: Austin or San Antonio?14:38
*** rmoe has quit IRC14:38
n0ano_edleafe, both in Texas, what's the question?14:38
*** rmoe has joined #openstack-meeting-alt14:39
edleafen0ano_: I knew someone hired to work in SA for Intel14:39
n0ano_edleafe, my bad, yes the group is ini San Antoio14:39
edleafen0ano_: ah, just wondered if he would have to move :/14:39
n0ano_they're Texas cities, who can keep them straight :-)14:39
*** mrmartin has quit IRC14:39
n0ano_I'm trying to blot it out of my mind, Intel tried to send me there for a 6 month rotation (I talked them out of it)14:40
bauzasn0ano_: some people are trying to group their efforts, company-unbiased14:40
bauzasn0ano_: you should talk to markus_z14:41
bauzasI remember he made a call for help14:41
n0ano_WFM, I just want to get progress on reducing the bug list14:41
bauzasn0ano_: http://lists.openstack.org/pipermail/openstack-dev/2016-January/083456.html14:42
n0ano_bauzas, tnx, I'll see if we can't get some help for that14:43
*** dane has joined #openstack-meeting-alt14:43
*** lazy_prince has joined #openstack-meeting-alt14:43
n0ano_anything else for today?14:43
n0ano_hearing crickets14:44
*** sgotliv has quit IRC14:44
n0ano_OK, tnx everyone, talk to you all next week14:45
n0ano_#endmeeting14:45
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"14:45
openstackMeeting ended Mon Feb  1 14:45:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-02-01-14.00.html14:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-02-01-14.00.txt14:45
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-02-01-14.00.log.html14:45
*** lazy_prince has quit IRC14:47
*** lazy_prince has joined #openstack-meeting-alt14:47
*** _gryf has left #openstack-meeting-alt14:47
*** rvyalov has quit IRC14:48
*** rmoe has quit IRC14:49
*** roaet has joined #openstack-meeting-alt14:50
*** dimtruck is now known as zz_dimtruck14:50
*** Prem_ has joined #openstack-meeting-alt14:50
*** rmoe has joined #openstack-meeting-alt14:51
*** kencjohnston has joined #openstack-meeting-alt14:52
*** piet has quit IRC14:52
*** dguitarbite has joined #openstack-meeting-alt14:53
*** yamamoto has quit IRC14:54
*** njohnston_ has joined #openstack-meeting-alt14:55
*** jprovazn has quit IRC14:57
*** rmoe has quit IRC14:57
*** jjmb1 has quit IRC14:58
*** piet has joined #openstack-meeting-alt14:58
*** KarthikB has joined #openstack-meeting-alt14:58
*** vkmc_ has joined #openstack-meeting-alt14:58
*** _amrith_ is now known as amrith14:59
*** jmckind has joined #openstack-meeting-alt14:59
*** rmoe has joined #openstack-meeting-alt14:59
*** balajiiyer has joined #openstack-meeting-alt14:59
*** korzen has joined #openstack-meeting-alt15:00
*** mhickey has joined #openstack-meeting-alt15:00
*** Akis_ has joined #openstack-meeting-alt15:00
*** ajo has joined #openstack-meeting-alt15:01
*** Sam-I-Am has joined #openstack-meeting-alt15:01
*** pc_m has joined #openstack-meeting-alt15:01
Sam-I-Amhello15:01
mhickeyhello15:01
roaethowdy15:01
korzenHi15:01
rossella_s#startmeeting neutron_upgrades15:01
openstackMeeting started Mon Feb  1 15:01:55 2016 UTC and is due to finish in 60 minutes.  The chair is rossella_s. 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:02
dguitarbitehello15:02
rossella_shi all! thanks for joining15:02
*** amotoki has quit IRC15:02
rossella_sIhar is traveling today so I will replace him15:02
rossella_s#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:02
mhickeyrossella_s: go for it! :)15:03
*** kfarr has quit IRC15:03
rossella_sas you might have read in the dev mailing list there will be an upgrade code sprint in Brno, March 14-1615:03
*** Akis__ has quit IRC15:03
rossella_sI hope to see you all there!15:04
mhickeyrossella_s: tentative15:04
*** spotz_zzz is now known as spotz15:04
* pc_m lurking15:04
*** kencjohnston has quit IRC15:04
korzenrossella_s: I'm planning to be there, needs to get approval for travelling15:04
rossella_smhickey, right, I should have stated it more clearly15:04
rossella_skorzen, go for it15:05
mhickeyI need approval too15:05
rossella_sI guess it's time to start asking for it15:06
rossella_slet's move on15:06
rossella_s#topic partial grenade15:06
*** openstack changes topic to "partial grenade (Meeting topic: neutron_upgrades)"15:06
rossella_ssc68cal seems to be not here15:06
*** sgotliv has joined #openstack-meeting-alt15:07
*** KarthikB has quit IRC15:08
rossella_sI don't have any fresh info, only what was shared in the dev mailing list...there are still test failures when ssh-ing into an instance, might be another MTU issue15:08
rossella_s#topic versioned objects15:08
*** openstack changes topic to "versioned objects (Meeting topic: neutron_upgrades)"15:08
*** sigmavirus24_awa is now known as sigmavirus2415:09
rossella_sI pushed an update for the port object patch https://review.openstack.org/#/c/253641/ mhickey helped me in fixing the UT failures15:09
roaetHi. Re OVO: electrocucaracha and saisriki are selecting two other OVO objects to convert. They will update the wiki asap.15:10
rossella_snow we have the allowed_address_pairs extension that is included in the port object, to make sure we can manage extension the right way15:10
rossella_sroaet, we discussed that earlier, we want to start porting port and network. After we finish the port for those objects we can start moving to other ones15:11
korzenhttps://review.openstack.org/#/c/264273 subnet OVO thanks for the review rossella_s :) I have replied and pushed new patch, still working on UT and final touches15:11
rossella_skorzen, thanks a lot!15:11
roaetrossella_s: ok so don't start on the other objects. Got it. I'll have them look at those patches and help where they can.15:12
korzenroaet, I think that SubnetPool OVO can be taken15:12
korzenI did not start working on it15:12
rossella_sroaet, it would be great if electrocucaracha and saisriki join our meeting15:12
rossella_skorzen, would you mind updating the backlog then?15:13
mhickeyrossella_s: extrac dhcp opt https://review.openstack.org/#/c/273072/, patch on the way to fix gate and ut issues.15:13
korzenrossella_s, OK I will add it to the backlog15:13
roaetThere appear to be many objects in work. korzen I will tell them to check out SubnetPool.15:13
rossella_smhickey, how are the UT for the other patches going? can you update us since you were so brave to volunteer to fix them?15:13
mhickeyrossella_sok...15:14
mhickeyallowed address pairs (https://review.openstack.org/#/c/268274/): has now passed15:14
rossella_sroaet, there are only 2 objects: port and network...of course the objects that compose them need to be ported too. Please tell them that we can coordinate better if they join this meeting.15:15
mhickeyport (https://review.openstack.org/#/c/253641): I will need to take a look at. still an issue15:15
*** Aish has joined #openstack-meeting-alt15:15
mhickeydhcp extra: details above ^^^15:15
rossella_sthanks mhickey !15:15
mhickeyThats it for the moment15:15
mhickeyno problem! :)15:16
rossella_sdguitarbite, do you have any update?15:16
*** woodster_ has joined #openstack-meeting-alt15:16
dguitarbiterossella_s: Not much done as of now.15:16
mhickeyrossella_s: one last thing...15:16
rossella_sdguitarbite, I can't see your name in the list under Object implementation in the team page, can you update it if you are working on some object please?15:17
dguitarbiterossella_s: I have some code written but not good enough to discuss it for the time being. I should send a PR by day after if time permits.15:17
dguitarbiterossella_s: yes, Ill do that.15:17
rossella_sdguitarbite, thanks15:18
rossella_smhickey, go on please :)15:18
*** ozamiatin_ has joined #openstack-meeting-alt15:18
*** electrocucaracha has joined #openstack-meeting-alt15:18
*** achanda has joined #openstack-meeting-alt15:18
mhickeyI just tried to get the ut's working on port and allowed address pairs patches. I will tackle the good review comments from korzen and others shortly.15:18
*** DandyPandy has left #openstack-meeting-alt15:19
*** paul-carlton1 has quit IRC15:19
rossella_smhickey, good job!15:19
rossella_sdguitarbite, which port extension are you working on?15:19
*** yamamoto has joined #openstack-meeting-alt15:20
dguitarbiteSecurity Groups and port security both of them. I thought its one task here.15:20
dguitarbiterossella_s: I can give away port security I have not touched anything in there yet15:20
rossella_sdguitarbite, nope it's two separate extensions15:20
rossella_sdguitarbite, ok, then please update the team page accordingly15:21
rossella_sdguitarbite, thanks!15:21
dguitarbiterossella_s: Ok, Ill update it. No sweat15:21
rossella_sanything else regarding objects?15:22
korzenI've got 2 opens15:22
*** kebray has joined #openstack-meeting-alt15:22
saisriki@rossella_s, myself and electrocucaracha just joined15:23
korzen1) support for multiple primary keys15:23
rossella_ssaisriki, electrocucaracha welcome!15:23
*** dprince has joined #openstack-meeting-alt15:23
rossella_skorzen, good point15:23
korzen2) Add IP address type decorator for sqlalchemy, nova style15:23
*** achanda has quit IRC15:23
rossella_skorzen, very good points15:23
*** electrocucarach_ has joined #openstack-meeting-alt15:24
korzensomeone interested?15:24
*** j___ has quit IRC15:24
rossella_skorzen, for the first one if I good remember you have a way to handle that in the network ovo, we just need to make it general15:24
*** SridharG has quit IRC15:25
korzenrossella_s yea, not so much general I think15:25
*** numans has quit IRC15:25
saisrikikorzen: I can take a look at IP address type decorator for sqlalchemy15:25
*** rvyalov has joined #openstack-meeting-alt15:25
rossella_sthanks saisriki !15:26
korzenrossella_s, do you think it can be merged in Mitaka? the IP address decorator?15:26
*** numans has joined #openstack-meeting-alt15:26
*** dprince has quit IRC15:26
korzenit would require the migration script15:26
*** EricGonczer_ has joined #openstack-meeting-alt15:27
*** tellesnobrega_af is now known as tellesnobrega15:27
rossella_skorzen, we can make it but we need to work on it and finish it up quickly15:27
korzensaisriki thanks, the details are in my commit: https://review.openstack.org/#/c/264273/10/neutron/objects/subnet.py@15115:28
korzenit would be beneficial to have it ready in Mitaka, the IP address and IP network CIDR15:29
saisrikiI guess, the idea for me and electrocucaracha was to look at OVO migration of SubnetPools15:29
saisrikiI don't think I can work on two items at the same time!!\15:29
*** achanda has joined #openstack-meeting-alt15:30
rossella_ssaisriki, feel free to pick the item that it's most convenient for you. We have plenty of work to distribute15:30
saisrikirossella_s: thank you15:30
korzensaisriki, I will take a look in near future in the IP address decorator so feel free to start the SubnetPool OVO first15:31
rossella_skorzen, thanks for stepping up15:31
saisrikikorzen: ok, thanks!!\15:31
rossella_sanything else?15:32
rossella_s315:32
rossella_s215:32
rossella_s115:32
electrocucarach_me15:32
electrocucarach_sorry, I have the patch for the documentation15:32
rossella_selectrocucarach_, can you paste the link?15:33
electrocucarach_should I create a bug and attach that patch to that bug?15:33
rossella_splease15:33
electrocucarach_well, this is the commit that I did in my own repo... but should I create the bug in launchpad?15:34
electrocucarach_https://github.com/electrocucaracha/neutron/commit/a1e0ad83539cb912b3b51dbacedfe7c417d9d7a915:34
rossella_selectrocucarach_, yes please create the bug15:34
electrocucarach_It's for autogenerate the db schemas in the documentation15:34
rossella_selectrocucarach_, that's a very nice improvement, thanks for that!15:35
electrocucarach_well, that was the idea of roaet15:35
rossella_sthanks roaet too15:35
rossella_sanything else?15:36
mhickeyno15:36
electrocucarach_no15:36
rossella_sso let's move on15:36
rossella_s#topic open discussion15:37
*** openstack changes topic to "open discussion (Meeting topic: neutron_upgrades)"15:37
rossella_sthere's one thing to discuss if we want to have a specif tag to track the ovo work15:37
rossella_sI think this was asked by pc_m15:37
rossella_ss/tag/rfe sorry15:38
pc_myeah, could just be a bug # so that items can be tracked, or use a tag on the commits.15:38
*** egallen has quit IRC15:38
mhickeypc_m: good idea15:38
korzenfor me it is a good step, lets inform others what we are working on15:38
*** zeih has quit IRC15:39
rossella_sit seems we all agree here15:39
roaetAgree a tag is a good idea15:39
pc_mcool15:39
rossella_sthat was easy. pc_m thanks for your input!15:39
*** mtanino has joined #openstack-meeting-alt15:39
pc_msure15:39
pc_mhelps those lurking to see what is going on :)15:40
*** zeih has joined #openstack-meeting-alt15:40
rossella_spc_m, I perfectly agree...it actually helps people involved too to keep track of what's going on15:40
korzenthe question is are we going to have 1 RFE15:40
korzenor RFE per OVO15:40
mhickeywelcome pc_m15:40
rossella_skorzen, I think one RFE...we can then use the Partial-bug tag in the commit15:41
*** achanda has quit IRC15:41
pc_mmhickey: hi15:41
mhickeykorzen, I think ihrachys suggested 1?15:41
pc_mCould just use a topic on the commits15:41
korzenrossella_s mhickey, ok fine for me15:41
pc_mOr a bug so that there is a place to see the commits. The topic is nice for searches. (could do both, if desired).15:42
rossella_spc_m, a topic requires a blueprint15:42
pc_mah15:43
*** Sukhdev has joined #openstack-meeting-alt15:43
pc_mI thought you could create one w/o.15:43
pc_mMaybe it's a manually process, if not using a BP.15:44
rossella_spc_m, well the topic is set by the branch name you use15:44
*** zeih has quit IRC15:44
rossella_spc_m, for convention we use to set the topic to bp/bp_name15:44
pc_mrossella_s: I used to do it for bugs too.15:44
*** dalgaaf has joined #openstack-meeting-alt15:45
rossella_swe can agree that we set a specific topic for ovo but there's no way to reinforce it...I think it's better to use an RFE then15:45
*** mspreitz has joined #openstack-meeting-alt15:45
pc_mit would most like need to be a team convention.15:46
pc_mlikely15:46
rossella_syep...so I prefer using "stardard" way to group patches, either RFE or blueprint...15:47
pc_mrossella_s: sure. np. just a thought15:47
*** rvyalov has quit IRC15:47
rossella_spc_m, mine it's just a thought too15:48
rossella_sanything else we want to discuss?15:49
mhickeyok, from me15:49
korzenabout https://review.openstack.org/#/c/273517 OVO common enum classes for IP version and IPv6 modes15:49
mhickeykorzen: yes15:50
*** hyamauchi has joined #openstack-meeting-alt15:50
korzenlike I said in the review, we should sync with Ihar on that one, he requested the strict versioning15:50
mhickeykorzen: sure, I agree.15:50
rossella_skorzen, agreed, let's wait for his feedback15:51
korzenI'm ok with both approaches: the integer or enum field15:51
mhickeykorzen: I am just caught between whether 2 int values are worth it.15:51
mhickeykorzen: thanks! :)15:52
rossella_sanything else?15:52
rossella_s315:53
rossella_s215:53
rossella_s115:53
mhickeybye, thanks rossella_s15:53
rossella_sthanks all for attending!15:53
korzenbye, thx all :)15:53
rossella_sI am very happy regarding the progress so let's keep going like this!15:53
saisrikithank you15:53
rossella_s#endmeeting15:53
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"15:53
openstackMeeting ended Mon Feb  1 15:53:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-02-01-15.01.html15:53
roaetbye all15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-02-01-15.01.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-02-01-15.01.log.html15:53
pc_mbye15:54
*** pc_m has left #openstack-meeting-alt15:54
*** electrocucarach_ has quit IRC15:54
dguitarbitebye15:54
*** harshs has joined #openstack-meeting-alt15:54
*** Sam-I-Am has left #openstack-meeting-alt15:56
*** salv-orlando has quit IRC15:57
*** browne has joined #openstack-meeting-alt15:57
*** rcernin has quit IRC15:58
*** kgiusti has joined #openstack-meeting-alt15:59
*** johnsom has joined #openstack-meeting-alt15:59
*** harlowja_at_home has joined #openstack-meeting-alt15:59
dimsstarting oslo meeting in a minute15:59
*** roaet has left #openstack-meeting-alt15:59
*** AndreyPavlov has joined #openstack-meeting-alt15:59
dhellmanno/16:00
ozamiatin_o/16:00
gcbo/16:00
dims#startmeeting oslo16:00
dimscourtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo,16:00
openstackMeeting started Mon Feb  1 16:00:24 2016 UTC and is due to finish in 60 minutes.  The chair is dims. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
dimscourtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps16:00
dimscourtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** korzen has quit IRC16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
dimscourtesy ping for dukhlov, lxsli, rbradfor, mikal, nakato, tcammann116:00
openstackThe meeting name has been set to 'oslo'16:00
johnsomo/16:00
browneo/16:00
dhellmanno/16:00
bknudsonhi16:00
ozamiatin_o/16:00
harlowja_at_homesup16:00
flaper87o/16:00
kgiustio/16:00
jecareyo/16:00
amrith./16:00
stevemaro/16:00
dukhlovo/16:00
lxslio/16:00
dims#topic welcome to new cores - rbradfor and lxsli for Oslo and dukhlov for Oslo-Messaging16:01
*** markmcclain has joined #openstack-meeting-alt16:01
*** openstack changes topic to "welcome to new cores - rbradfor and lxsli for Oslo and dukhlov for Oslo-Messaging (Meeting topic: oslo)"16:01
bknudsonyay!16:01
dimshurray! join the fun16:01
rbradforo/16:01
rpodolyakao/16:01
lxsliWoo, thank you all!16:01
ozamiatin_welcome!!16:01
*** numans has quit IRC16:01
johnsomWelcome16:01
dukhlovthank you!16:01
rbradfordims, thanks for including me in the Oslo team16:02
*** haypo has joined #openstack-meeting-alt16:02
*** egallen has joined #openstack-meeting-alt16:02
*** nkrinner has quit IRC16:02
harlowja_at_homewelcome!!!!16:03
dimsrbradfor : hope you have as much fun as i do :) thanks goes to the team16:03
*** dave-mccowan has quit IRC16:03
harlowja_at_homelol16:03
haypo_o/16:03
*** mrmartin has joined #openstack-meeting-alt16:03
dims#topic Red flags for/from liaisons16:03
*** fawadkhaliq has quit IRC16:03
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:03
stevemarcongrats rbradfor16:03
amrithnothing from trove at this time.16:03
bknudsonnone for keystone that I know of16:03
gcbwelcome rbradfor, lxsli and dukhlov16:03
johnsomNothing to report Octavia/LBaaS16:03
amrithcongratulations to all new cores.16:03
rbradforstevemar, gcb thanks, and thanks  to all16:04
harlowja_at_homejohnsom, have u guys started using the new taskflow stuff?16:04
*** degorenko is now known as _degorenko|afk16:04
johnsomYes!16:04
harlowja_at_homecool16:04
johnsomLooking good so far16:04
harlowja_at_homenice nice16:04
haypo[off-topic] FYI glance, designate  & solum now work on python 316:04
dimshaypo : great!16:04
harlowja_at_homeis python 4 out yet?16:04
bknudsonwe'll get python 3 on keystone one of these days16:05
haypoharlowja_at_home: ...16:05
harlowja_at_homelol16:05
stevemarbknudson: when we get ldap support for py316:05
haypobknudson: tell me if i can help16:05
haypostevemar: what? the ldap project was ported to py3, like 2 months ago16:05
bknudsonwe need to switch off python-ldap to ldap316:06
dims#topic - python3 support :)16:06
*** openstack changes topic to "- python3 support :) (Meeting topic: oslo)"16:06
stevemarhaypo: ^16:06
haypostevemar: https://github.com/pyldap/pyldap/ some colleagues work on it16:06
*** Guest44217 has quit IRC16:06
dimsnow its' on topic16:06
harlowja_at_homelol16:06
stevemarhaypo: what bknudson said, we have to actually switch over16:06
haypobknudson: nope. my colleague told me that ldap3 lacks important features for FreeIPA16:06
*** rods has joined #openstack-meeting-alt16:06
haypodims: to come back to Oslo, oslo.context has a bug fixed on the request_id attribute16:06
haypodims: see https://review.openstack.org/#/c/274719/ for a release bumping major version to 2.0 ;-)16:07
bknudsonok, maybe we can switch to pyldap rather than ldap316:07
haypostevemar: it's just a matter of replacing import lines, no?16:07
haypostevemar: i'm talking about pyldap16:07
*** vgridnev has quit IRC16:07
haypostevemar: pyldap is a fork of python-ldap, no API change16:07
stevemarhaypo: oh nice16:07
*** jprovazn has joined #openstack-meeting-alt16:08
stevemarhaypo: we were looking at ldap316:08
stevemarmaybe i'll poke around it in the afternoon16:08
haypostevemar: tell me if you need more precise information, i'm not in the FreeIPA at Red Hat16:08
haypoi'm just repeating what i heard16:08
dimsstevemar : bknudson : there's a #openstack-python3 irc channel as well to find like-minded folks later16:09
hayporbradfor: congrats (i'm late)16:09
dims#topic Releases for Mitaka16:09
dimsNo scheduled releases for this week. Please file reviews in openstack/releases repo if/when you need something16:09
haypodims: yeah, we should continue the discussion there, sorry for the noise16:09
*** openstack changes topic to "Releases for Mitaka (Meeting topic: oslo)"16:09
dimshaypo : no worries, it's relevent16:09
haypodims: https://review.openstack.org/#/c/274719/ oslo.context 2.016:09
haypodims: https://review.openstack.org/#/c/274726/ oslo.concurrency 3.4.016:09
stevemarhaypo: cool, i'm reading the pyldap docs now i'll poke around later16:10
dimsi am expecting a review for oslo.messaging as well16:10
dimshaypo : ack will review them16:10
ozamiatin_dims: in progress16:10
*** belmoreira has quit IRC16:10
rbradfordims, and I'd like an included part of oslo.context 2.016:10
*** pbelamge has quit IRC16:10
toabctl_hi16:10
dimsrbradfor : check the list changes job in that oslo.context 2.0 review to see if the changes you need are in there16:10
*** pbelamge has joined #openstack-meeting-alt16:10
stevemardims: i'd love a new oslo.config release :)16:10
dimstoabctl_ Hi16:11
dimsstevemar : push a releases repo request please?16:11
stevemardims: ack16:11
*** kairat_ has joined #openstack-meeting-alt16:11
rbradfordims, it is listed in oslo.context 2.016:11
hayporbradfor: which change do you need?16:11
rbradforhaypo, 22ad2c2 Define method for oslo.log context parameters16:11
rbradforwork on the app-agnostic-parameters blueprint which I need for work in oslo.log16:12
hayporbradfor: https://review.openstack.org/#/c/274186/ hum ok16:12
dimsrbradfor : haypo : looks like we need a requirements bump too16:12
*** minwang2 has joined #openstack-meeting-alt16:12
rbradforhaypo, yes16:12
haypodims: for what?16:12
dimsoslo.context 2.016:12
dimsbump the upper-constraints.txt?16:13
dhellmannif rbradfor needs something in that for oslo.log, we should raise the minimum in global-requiremenst.txt too16:13
*** pbelamge has quit IRC16:13
haypodims: it can be done later, no? what needs olso.context 2.0?16:13
dhellmannhaypo : the release process calls for having the requirements patch filed before the release is done to ensure that it is available to merge shortly after the relase16:14
dimssorry global-requirements... +1 to dhellmann's coment16:14
dhellmannhaypo : http://docs.openstack.org/releases/instructions.html#requesting-a-release16:14
*** Leom has joined #openstack-meeting-alt16:14
haypodhellmann: "to ensure the new release is tested in the gate" ah ok, now i understand :)16:15
stevemardims: did both the release and the requirements patch16:15
hayposorry, i'm still tired of my long week-end at FOSDEM ;)16:15
dimsstevemar : thanks!16:15
dhellmannhaypo : np, that's why we have the review process in place :-)16:15
*** vahidh has joined #openstack-meeting-alt16:17
*** vahidh has quit IRC16:17
dims#topic Encourage PTL candidates for Newton16:17
dimsFolks, Thanks for all the help and encouragement during my PTL stint. I'd like someone else to take over. If folks are interested, i can show the ropes over the next few weeks before the PTL elections. Please ping me.16:17
*** openstack changes topic to "Encourage PTL candidates for Newton (Meeting topic: oslo)"16:17
*** jesusaurus has quit IRC16:18
*** dave-mccowan has joined #openstack-meeting-alt16:18
*** mrmartin has quit IRC16:18
harlowja_at_homeuh oh16:18
harlowja_at_homefor he was a jolly good fellow16:18
harlowja_at_homeand no one shall deny16:18
dimsLOL harlowja_at_home16:18
kgiustihere here!16:18
rbradforhe still is a jolly good fellow16:18
*** lxsli has quit IRC16:18
*** tcammann1 has quit IRC16:18
harlowja_at_homelol16:18
*** anteaya has quit IRC16:18
harlowja_at_home*for he is a jolly good fellow16:19
*** cody-somerville- has quit IRC16:19
dims#topic Open discussion16:19
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:19
dimsAny other stuck reviews?16:19
*** epheo has quit IRC16:19
dimsbefore this gets out of hand :)16:19
harlowja_at_homeha16:19
*** tcammann_ has quit IRC16:19
dimsSo there was a thread about -2's in oslo project16:19
harlowja_at_homeya, about that16:20
dimsi'd like folks to revisit that thread -16:20
dims#link http://markmail.org/message/xcenlg4lrgjoyfiy16:20
dimsto see if we can do something better16:21
johnsomharlowja_at_home Just another thanks for that taskflow patch.  It really makes a difference in our code.16:21
harlowja_at_homeit'd be nice if a person that posts a -2 that it would initiate a phone call with the person that makes the code, lol16:21
bknudsonif someone asks you to remove a -2 then remove it... that's what I do.16:21
harlowja_at_homejohnsom, np16:21
johnsomIt will make more when I get around to cleaning up the old hacks16:21
bknudsonsometimes I don't have a lot of time to do a new review16:21
*** lxsli_web has joined #openstack-meeting-alt16:21
harlowja_at_home:)16:22
dimsbknudson : +116:22
dhellmannthe person who started that thread was involved in 2 patches with -2 in a short time, which is not just unusually high for an individual it's unusually high for oslo I think16:22
dhellmannI'm not sure I want to call it a fluke, but it doesn't seem like we have a persistent ongoing issue, either16:23
dimsdhellmann : agree.16:23
*** harshs has quit IRC16:23
haypoit looks like oslo.versionedobjects is somehow different, because it linked to nova16:23
dhellmannso it's unfortunate, but I stand by my -2 on the utc time logging change16:23
haypoand nova is more conservative, no?16:23
dhellmannyeah16:23
rbradforit seemed inappropriate this was not started in a separate ML thread.16:23
harlowja_at_homean idea, if a -2 gets added, we could try to have the policy be that said -2 being done automatically requires a ML email16:23
bknudsonthe -2 also shows a lack of trust of other core reviewers.16:23
dimsdhellmann : am with you on that16:23
harlowja_at_homea ML email either by the code reviewer or the code creator16:24
bknudsonif you don't trust cores to not merge something when you -1 then we have another problem.16:24
dhellmannhaypo: and I think it's reasonable for us to be saying in general "prove there's utility in that feature by running it in your app" for a time16:24
dimshow about when we -2, we tell them to bring it to the next weekly oslo meeting?16:24
dhellmannhaypo : esp. in vo, where it's easy to add a type class locally16:24
dimsso at least they know what to do16:24
rbradforso a suggestion is if anybody gives a -2 they ask for a ML discussion to be started.16:24
harlowja_at_homedims,  that seems fair also16:24
dhellmanndims : that's a good procedural tweak, sure16:24
harlowja_at_homerbradfor,  ya, either that or we talk about -2 here16:24
dhellmanneither ML or meeting16:24
rbradfordims and bring to oslo meeting16:24
hayporbradfor: good idea16:24
rbradfordhellmann, I think both16:25
*** jjmb has joined #openstack-meeting-alt16:25
dimscool. guess part of the frustration was not knowing what to do next16:25
dimsso this will help16:25
rbradforthe ML enables inputs, the meeting should be to finalize any decisions16:25
hayposorry, i didn't have time to read the thread. but maybe the problem is the messaging explaining the -2 vote? we should write a template :)16:25
harlowja_at_homewe are very good at templates :-P16:25
haypofor example, "-2 your code sucks" is not good :)16:25
dhellmannhaypo : I will admit that I assumed the submitter knew what to do next, and didn't explicitly ask. I'll be more careful about that in the future.16:26
haypo"-2 you code sucks, because ... try maybe ... or come to the ML or oslo meeting to discuss" is maybe beetter :-D16:26
dimsdhellmann : y not sure if they knew16:26
haypoi understand that it can be *very* frustrating to get a -216:26
haypoi always hate getting -2 (yeah, it occurred me, like multiple times!)16:26
dimsanother one...16:26
*** jungleboyj has joined #openstack-meeting-alt16:26
harlowja_at_homehaypo, ya, something like that template seems ok16:27
jungleboyjo/16:27
dimsAnother observation was in the thread for Alexis' nomination16:27
dims#link http://markmail.org/message/i5hfaknvpgxyhvrg16:27
haypoharlowja_at_home: or maybe just a link to a wiki page, somewhere16:27
harlowja_at_homehaypo, possibly16:27
dimswe as a team would like to welcome both specialists and generalists16:27
dimsand get people to grow their expertise16:27
rbradforto be more positive, rather than "your code sucks" I really liked sdague who said elsewhere "violates the principle of least surprise?"16:27
harlowja_at_homedims, haypo also started a whole new thread on that16:27
dimswe've done a great job at shepherding all the technical debt from oslo-incubator days16:28
dhellmann++16:28
haypodims: i'm in favor of trusting people, see my "It's better to ask forgiveness than permission" thread :)16:28
bknudsonI was concerned when somebody +2d a change in oslo.policy that I didn't think keystone would agree with... needed more discussion16:28
harlowja_at_home#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/085467.html16:28
haypoif we are welcoming newcomers, it's more likely that they start to look at other oslo projects, not only the one they started to hack16:28
*** _nadya_ has quit IRC16:28
dimsbknudson : let's bring instances like that to be more visible. would that work?16:29
haypoi'm proud of being part of oslo, but i also feel guilty if it don't review enough changes :)16:29
haypomore powers means more responsabilities :)16:29
bknudsondims: yes. I don't want to make a big deal out of it.16:29
dimsoslo.policy and oslo.versionedobjects need to be looked at by keystone folks and nova folks respectively16:29
*** sbalukoff has quit IRC16:30
dimsfor sure16:30
dimsbknudson : ack16:30
harlowja_at_home(although i'd still like to figure out how to avoid nova having downstream patch-like-things in ovo)16:30
harlowja_at_homebut i gotta investigate that one more16:30
dimsharlowja_at_home +116:30
haypoi can also understand that other projects like nova have motivation to be more conservative, but being conservative has serious side effect (technical debt)16:31
harlowja_at_homemaybe ovo needs experimental features, idk16:31
haypoat least, i want oslo to remain as open as possible :)16:31
*** minwang2 has quit IRC16:31
lxsli_webo.vo is a really special case because a breaking patch there ruins everything so badly16:31
*** kebray has quit IRC16:31
dimshaypo : +100016:31
haypodims: they are plan to use oslo.versionedobjects in other proejcts, no?16:31
dhellmannlxsli_web : that applies to a lot of the oslo libs :-/16:31
haypodims: i don't recall which ones :-/ cinder?16:31
dimslxsli_web : right, so good test matrix16:31
dimsdhellmann : well said :)16:32
harlowja_at_homehaypo, ironic, cinder, nova i thnk16:32
lxsli_webalso because it's more growing out of nova than being separately developed, hence the up/downstream relationship16:32
jungleboyjhaypo: Yes, Cinder is working hard to move to ovo .16:32
haypoharlowja_at_home: ah cool. are you aware of any concrete progress on these projects?16:32
harlowja_at_homehaypo, unsure16:32
haypojungleboyj: cool :)16:32
lxsli_webdhellmann: fair point16:32
haypojungleboyj: thanks for the confirmation ;)16:32
dimsdansmith : around? (just in case :)16:32
jungleboyjhaypo: We have a bunch of patches that dulko has been working on and we just agreed in the meetup to work to get them in.16:32
harlowja_at_homelxsli_web, perhaps ovo has a ovo.experimental module, idk16:33
dansmithdims: only barely.. running a meeting at the moment16:33
haypolxsli_web: my point is that it's ok to break the world16:33
dimsdansmith : no worries. just making sure you know we are raising the concerns :)16:33
haypolxsli_web: shit happens, it's part of the development process16:33
haypolxsli_web: working hard to avoid shit is pointless16:33
lxsli_webharlowja_at_home: the way rlrossit explained it, the "experimental" features are already in Nova, he's just tweaking them slightly before porting to o.vo16:33
dansmithdims: thanks, I'll read the scrollback here when I'm done :)16:33
haypolxsli_web: it's better to be reactive when bugs are noticed16:33
*** rlrossit has joined #openstack-meeting-alt16:34
dhellmannhaypo : it's ok to have accidents. it's not ok to willfully break things.16:34
lxsli_webharlowja_at_home: so an ovo.experimental would just clutter the process16:34
haypolxsli_web: (well, i'm not asking to remove all tests :-))16:34
stevemarhaypo: breaking the world let's you figure out exactly how things break!16:34
harlowja_at_homelxsli_web, fair enough16:34
*** kebray has joined #openstack-meeting-alt16:34
haypodhellmann: "willfully break things" nobody said that16:34
lxsli_webhaypo: there's a fine line between "move fast" and being careless :)16:34
dimshaypo : right, the idea is to make sure specialists get first preference at some of the project reviews16:34
dhellmannhaypo : 'working hard to avoid shit is pointless'?16:34
*** absubram has quit IRC16:35
haypodhellmann: hum ok. i picked the wrong words :)16:35
harlowja_at_homelol16:35
dhellmannhaypo : :-)16:35
dimshaypo :) i know translation and then typing quickly at irc meeting is hard16:35
haypodhellmann: i mean that we should not deny people to contribute just because of a theoric risk of regressions. there is a grey arreay in code reviews and development16:36
haypodhellmann: for the grey area, i prefer to trust people and having more core reviewers able to fix issues quickly16:36
dhellmannhaypo : ok, I can agree with that. We should still be reviewing for potential issues, but dealing with them when they get through16:36
haypodhellmann: rather than letting reviews rotten for months16:36
dimshaypo : so we continue what we have done recruiting both folks specific to projects and oslo cores as appropriate i think16:37
lxsli_webTrust has been given, it's now up to rbradfor + me to be careful and ask for help when needed16:37
dhellmannlxsli_web : +116:37
haypodhellmann: the thread started by a vote to welcome a new core reviewer16:37
harlowja_at_homegroup hug16:37
dimslxsli_web : +10016:37
dims:)16:37
rbradforspeaking as a newcomer I'm only really comfortable in about 3 oslo projects, I look and comment in reviews in about 3 more, and while I look into other projects, I'm only observing, certainly not voting.16:37
haypolxsli_web: in my experience, new (core) contributors are too afraid to make mistake, so the problem doesn't exist :)16:38
rbradforuntil I become more comfortable.16:38
haypolxsli_web: if you break the world, it's because we failed to be good mentors16:38
dimsright rbradfor16:38
dhellmannrbradfor : that's ideal16:38
haypoin python, we have a mentoring process for new core developers16:38
haypothe mentor is responsible to watch changes made new core developers16:38
*** kebray has quit IRC16:38
*** snackewm has joined #openstack-meeting-alt16:39
haypobut also help to handle practical things, to reply to simple questions if the contributor is too shy to ask in public16:39
* rbradfor goes to comment on a review and now I see +2 for the first time, it's a bit too close to the +1.16:39
*** sigmavirus24 is now known as sigmavirus24_awa16:39
*** ninag has joined #openstack-meeting-alt16:39
*** rcernin has joined #openstack-meeting-alt16:39
dimshaypo : y, here the major question was if Nova folks were uncomfortable with size of oslo core since there's a possiblity that "bad" reviews may get in16:39
hayporbradfor: FYI i prefer to restrict myself to +1 (no +2) for some oslo projects16:39
rbradforhaypo, I agree16:40
lxsli_webhaypo: +1 :)16:40
dimshaypo : good tip at least for starters16:40
haypodims: is the risk theorical? or is it common that oslo break the [nova] world?16:40
*** bana_k has joined #openstack-meeting-alt16:40
bknudsonif you don't understand the change, don't +2... this means some reviews are going to sit around for months since nobody understands it. (probably due to the code or commit message)16:40
dhellmannhaypo : it used to be far more common than it is, but it's still quite easy16:40
haypodims: and if oslo break things, is it possible to detect these issues earlier?16:40
bknudsonwe don't have any code that's so complicated a reasonably skilled reviewer can't figure it out.16:40
dimshaypo : we have been good at not breaking Nova or the core project masters. stable is a whole another story16:40
dansmithbknudson: you have to know a lot to know that you don't know, in a lot of cases16:40
*** shashank_hegde has joined #openstack-meeting-alt16:41
haypodhellmann: in my experience, it's really hard to predict during a code review that a change will break a random openstack project16:41
lxsli_webbknudson: but by increasing core team size, hopefully someone will comment and ask for clarity16:41
haypodhellmann: sometimes, even "experts" need several hours to investigate a regression16:41
*** sigmavirus24_awa is now known as sigmavirus2416:41
haypodhellmann: that's what i'm  calling the "grey area"16:41
*** jjmb has quit IRC16:42
dimsdansmith : "you have to know a lot to know that you don't know, in a lot of cases" :)16:42
dhellmannhaypo : I agree, it's hard16:42
rbradfordims, a suggestion to point threads to in the future, lets expand "Generalist Core reviewers" in https://wiki.openstack.org/wiki/Oslo#Generalist_Code_Reviewers,  we could even create a table for "core reviews primary projects", especially for newer cores.16:42
*** salv-orlando has joined #openstack-meeting-alt16:42
*** baoli has quit IRC16:42
harlowja_at_homeand even then u get old, and admit u don't know alot16:42
harlowja_at_homelol16:42
lxsli_web15min warning16:42
haypodhellmann: IMHO we made huge progress on testing oslo changes on other projects (as dims said, especially on nova) last 12 months16:42
dhellmannhaypo : oh, definitely, the work dims has done on that is superb16:42
*** baoli has joined #openstack-meeting-alt16:43
*** ashleighfarnham has joined #openstack-meeting-alt16:43
haypodhellmann: dims has a travis job, we added more tests on requirements updates16:43
*** tfukushima has quit IRC16:43
haypoetc.16:43
dimsrbradfor : i'll let you all self-organize :)16:43
dhellmannyep, all of that is really helpful16:43
rbradfordims, I'll take on expanding the public wiki.16:43
dimshaypo : dhellmann : my next step is to figure out how to get the stuff out from travis into regular CI16:43
dimsrbradfor : ack thanks16:44
haypodims: oh, huge project, no?16:44
haypodims: you should ask help to the infra team16:44
dhellmanndims : it would be interesting to see if we could set up some jobs to run for release requests of oslo things16:44
harlowja_at_homerbradfor, http://truben.no/table/ has a nice GUI table generator that i think u can use to make the wiki markdown16:44
dimsdhellmann : right16:44
harlowja_at_home(vs having to create it manually)16:45
haypoas usual, many people complain of oslo regressions, but nobody is volunteer to work on more tests or help on code review ;-)16:45
dhellmanndims : you'd have everything you need to set up libs from source16:45
rbradforharlowja_at_home, thanks.16:45
*** mhickey has quit IRC16:45
haypo(i'm talking about people *consuming* Oslo)16:45
dimsdhellmann : true16:45
dhellmanndims : anyway, just thinking out loud16:45
haypodims, dhellmann : maybe we need to discuss all of this by email, to include the whole OpenStack community16:46
dimshaypo : before the oslo regressions, i'd ask for gate failure volunteers, that's even more critical.16:46
haypoit's wider than this short meeting, no?16:46
*** baoli has quit IRC16:46
haypo(ok, and also, i have to go :-))16:47
haypodims: sorry, what is a "gate failure volunteer"?16:47
dimshaypo : feel free to start appropriate threads. i just wanted to get a sense here if we are all on the same page and appropriate heads up for some specific projects with concerns16:47
*** mfedosin has joined #openstack-meeting-alt16:48
dimshaypo : let's talk about that after the meeting, it's mostly diagnosing quickly when things go wrong in the zuul gate16:48
dimsso anyone else have things to discuss?16:49
rbradfordims, I should mention I've picked up the older app-agnostic-parameters spec and will be working on pre-requisites in a number of TC projects to cleanup oslo.log usage16:49
dimsrbradfor : sounds good! thanks16:49
rbradfordims, I see it as pre-requisite for other things discussed at tokyo.16:50
dimswrapping up for today then. thanks everyone.16:50
bknudsonthanks16:50
harlowja_at_homenp16:50
*** vahidh has joined #openstack-meeting-alt16:50
dims#endmeeting16:50
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"16:50
openstackMeeting ended Mon Feb  1 16:50:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-02-01-16.00.html16:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-02-01-16.00.txt16:50
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-02-01-16.00.log.html16:50
*** HeOS has quit IRC16:50
*** gcb has quit IRC16:50
*** johnsom has left #openstack-meeting-alt16:50
*** rlrossit has left #openstack-meeting-alt16:50
*** zeih has joined #openstack-meeting-alt16:50
*** harlowja_at_home has quit IRC16:51
*** dshakhray has joined #openstack-meeting-alt16:51
*** evgenyf has quit IRC16:52
*** ashleighfarnham has quit IRC16:52
*** mikelk has quit IRC16:54
*** mspreitz has quit IRC16:54
*** ijw has joined #openstack-meeting-alt16:56
*** baoli has joined #openstack-meeting-alt16:56
*** AndreyPavlov has quit IRC16:56
*** dingboopt has quit IRC16:57
*** dingboopt has joined #openstack-meeting-alt16:57
*** Swami has joined #openstack-meeting-alt16:57
*** yamamoto has quit IRC16:58
*** kencjohnston has joined #openstack-meeting-alt16:59
mfedosinCourtesy meeting reminder: nikhil_k, ativelkov, mfedosin, docaedo, dshakhray, kfox111, kairat, nikhil17:00
nikhilo/17:00
docaedohello17:00
*** pballand has joined #openstack-meeting-alt17:00
mfedosino/17:00
dshakhrayo/17:00
mfedosin#startmeeting glance_artifacts_sub_team17:00
openstackMeeting started Mon Feb  1 17:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is mfedosin. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** hyamauchi has quit IRC17:00
*** openstack changes topic to " (Meeting topic: glance_artifacts_sub_team)"17:00
mfedosin#link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda17:00
*** EricGonczer_ has quit IRC17:00
openstackThe meeting name has been set to 'glance_artifacts_sub_team'17:00
docaedoo/17:00
kairat_O/17:01
mfedosinglad to see you here today :)17:01
mfedosinso, we have several topics to discuss17:01
mfedosinbut before I have to mention that I'm writing a document about glare architecture17:02
*** browne has left #openstack-meeting-alt17:02
*** rcernin has quit IRC17:02
mfedosinit's almost done and I'll publish it tomorrow after today's decisions17:02
nikhilexcellent, can't want to see17:02
mfedosinyou can see a picture from there17:03
nikhilyes, the pic is pretty cool indeed17:03
mfedosinlast Friday Nikhil asked me to write some thoughts about glare...17:03
mfedosinlike brainstorming the architecture17:04
mfedosin#link https://etherpad.openstack.org/p/mitaka-glare-api-brainstorm17:04
mfedosinI did it, but here we can discuss it17:04
mfedosinfirst think about public and private api17:04
mfedosinI think it's unnecessary and we can have only one public api17:05
*** armax has joined #openstack-meeting-alt17:05
*** vgridnev has joined #openstack-meeting-alt17:05
mfedosinand if DefCore wants some standardization we can do it with images api only17:06
*** davidsha has joined #openstack-meeting-alt17:06
mfedosinother plugins are optional17:06
mfedosinnikhil, your thoughts?17:06
nikhilyeah, mfedosin and I had a brief starter discussion on what the architecture looks like. I wanted to see how the "schema on schema" idea looks like.17:06
nikhilMy feeling is that we need to have a structured scope around the API (only public API)17:07
nikhiland for that we need semantics17:07
*** dshakhray has quit IRC17:07
nikhilthere are two ways of doing it17:07
nikhilthe oslo.vo is one way17:07
mfedosinnikhil absolutely agree with you17:07
*** dshakhray has joined #openstack-meeting-alt17:07
*** zz_dimtruck is now known as dimtruck17:07
nikhilbut the primary origination of oslo.vo is17:07
*** EricGonczer_ has joined #openstack-meeting-alt17:07
*** dshakhray has quit IRC17:07
nikhilhaving a static feeling to dynamic language (ie python)17:08
*** dshakhray has joined #openstack-meeting-alt17:08
*** dshakhray has quit IRC17:08
nikhilthat helps with the DB upgrades and asynchronous calls (Bcast and multi cast) etc17:08
*** dshakhray has joined #openstack-meeting-alt17:08
*** ashleighfarnham has joined #openstack-meeting-alt17:08
nikhilI think it might be worth adding the scope of our requirements and bring that to the oslo.vo core team17:08
*** kgiusti has left #openstack-meeting-alt17:08
*** davidsha has left #openstack-meeting-alt17:09
*** dshakhray has quit IRC17:09
nikhilgiven we choose to take that route17:09
*** dshakhray has joined #openstack-meeting-alt17:09
mfedosinalso oslo.vo helps with architecture17:09
nikhilif all works out that seems like a good idea17:09
nikhilagreed17:09
*** esker has joined #openstack-meeting-alt17:09
mfedosinI mean we can map Blob type directly to store with coercing17:09
*** matrohon has quit IRC17:09
mfedosinyou may see my example from the etherpad17:09
*** pballand has quit IRC17:09
mfedosinI think we need to investigate how oslo.vo behaves in our case17:10
nikhilI need more time to absorb that example and fit it into bigger pic17:10
nikhilyes17:10
mfedosinbut we can leave oslo.vo as the main priority for glare17:11
mfedosinif it doesn't fir we can return to the idea of 'schema-on-schema'17:11
mfedosin*fit17:12
nikhilare there more comments that we might expect on the etherpad ?17:12
mfedosinI asked kairat to look there too17:12
nikhilah cool17:12
nikhilhopefully we can get something today17:12
*** pballand has joined #openstack-meeting-alt17:13
mfedosinbut we discussed it today and he agrees we the direction17:13
nikhilelse, let's move forward with oslo.vo17:13
mfedosinokay, about the documentation17:13
mfedosinas I mentioned last week it's called What is Glare?17:14
*** baojg_ has joined #openstack-meeting-alt17:14
*** HeOS has joined #openstack-meeting-alt17:14
mfedosinand it provides an eagle view on the service17:14
kairat_Does it describe current doc?)17:14
mfedosinit will help community members to be more familiar with Glare17:14
*** weshay has quit IRC17:14
*** baojg has quit IRC17:15
kairat_Current impl17:15
kairat_or future implementation17:15
mfedosinand also will describe some usecases for our customers17:15
nikhilgreat17:15
mfedosinkairat_: it's something between Alex wanted to see and something that will work :)17:16
*** hyamauchi has joined #openstack-meeting-alt17:16
*** SumitNaiksatam has quit IRC17:16
kairat_Heh17:16
mfedosinso, I have a picture of that17:16
*** paul-carlton1 has joined #openstack-meeting-alt17:16
mfedosin#link https://dl.dropboxusercontent.com/u/13626875/glare.png17:17
*** gyee has joined #openstack-meeting-alt17:17
mfedosinit's based on oslo.vo17:17
*** scheuran has quit IRC17:17
mfedosinidea is that we have unified api for all plugins (or 'oslo versioned objects' if you want)17:18
mfedosinthen we have a unified api that all plugins must implement17:18
mfedosinbut each plugin may have it's own data_api17:19
kairat_That's simple and great imo17:19
kairat_Good to hear17:19
mfedosinfor example, for images it will be current Image tables17:19
nikhilwhat is a data_api ?17:19
*** HeOS has quit IRC17:19
kairat_Api to database17:20
mfedosinnikhil: the same thing we have in glance-api.conf17:20
nikhilah17:20
nikhilseems logical17:20
mfedosinthat's how heat does it https://github.com/openstack/heat/blob/master/heat/objects/stack.py#L2517:21
*** hyamauchi has quit IRC17:22
mfedosinso, we need to think about 2 things17:22
mfedosin1. REST api - Alex almost did it for us17:22
*** bgaifullin has quit IRC17:23
mfedosinwe just need to add there requests for data upload/download17:23
mfedosinand we're cool :)17:23
nikhilyeah, not sure where  heat separates it's data but glance does for metadefs and imgaes17:23
*** minwang2 has joined #openstack-meeting-alt17:23
mfedosin2. Interface for oslo.vo classes17:24
mfedosinlike 'save' data to db, 'get' from db, 'add_tag' and so on17:24
mfedosinalso there is a patch from Alex to move glance v3 api to Glare v0.117:25
mfedosinnikhil: if you have time please review it and let's merge it17:26
nikhilsounds good17:26
*** samuelBartel has quit IRC17:26
mfedosin#link https://review.openstack.org/#/c/255274/17:26
mfedosinafter that we will be able to start the development of glare v1 :)17:27
*** prithiv has quit IRC17:27
nikhil++17:27
kairat_We need to merge glare xlient code as well17:27
mfedosinand also - no Glance/Glare separation!17:27
mfedosinwe will stay in glance repo17:28
*** safchain has quit IRC17:28
kairat_But it is not a blocker17:28
mfedosinkairat_: you will be a core member tomorrow17:28
kairat_What about murano requirements17:28
kairat_Oops, cool))17:29
mfedosinyou will be able to merge everything17:29
kairat_Heh17:29
mfedosinwe will help you17:29
*** iyamahat has quit IRC17:29
nikhilhi I have a small request17:29
mfedosinbut let's begin with a standalone service17:29
nikhilgiven we have a min or so17:29
mfedosinnikhil shoot17:29
nikhilcan we move this meeting to 1730 UTC17:30
nikhilin this channel17:30
nikhiljust checked and the slot is open17:30
nikhilI have a conflict at this time17:30
mfedosinI think it easy17:30
kairat_Ok for me17:30
mfedosinsame for me17:30
nikhilawesome, will send a review and email ML17:30
kairat_Need to notify to dec mail17:30
nikhilthanks guys17:30
mfedosinnikhil please do17:30
kairat_Dev mail17:30
nikhilyeah17:30
mfedosinokay, thank you all :)17:31
mfedosinglare is coming!17:31
mfedosin#endmeeting17:31
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"17:31
openstackMeeting ended Mon Feb  1 17:31:44 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:31
*** dshakhray has quit IRC17:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2016/glance_artifacts_sub_team.2016-02-01-17.00.html17:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2016/glance_artifacts_sub_team.2016-02-01-17.00.txt17:31
openstackLog:            http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2016/glance_artifacts_sub_team.2016-02-01-17.00.log.html17:31
*** dshakhray has joined #openstack-meeting-alt17:31
*** piet has quit IRC17:33
*** absubram has joined #openstack-meeting-alt17:33
*** _nadya_ has joined #openstack-meeting-alt17:33
*** mrmartin has joined #openstack-meeting-alt17:34
*** harshs has joined #openstack-meeting-alt17:36
*** salv-orl_ has joined #openstack-meeting-alt17:36
*** merooney has joined #openstack-meeting-alt17:38
*** zeih has quit IRC17:39
*** salv-orlando has quit IRC17:39
*** kertis has left #openstack-meeting-alt17:40
*** balajiiyer has quit IRC17:41
*** shashank_hegde has quit IRC17:41
*** jjmb has joined #openstack-meeting-alt17:42
*** zeih has joined #openstack-meeting-alt17:43
*** electrocucaracha has quit IRC17:44
*** thomnico has joined #openstack-meeting-alt17:44
*** _nadya_ has quit IRC17:47
*** rvyalov has joined #openstack-meeting-alt17:48
*** numans has joined #openstack-meeting-alt17:48
*** reedip_ has joined #openstack-meeting-alt17:48
*** mrmartin has quit IRC17:49
*** tonytan4ever has joined #openstack-meeting-alt17:49
*** rvyalov has quit IRC17:51
*** weshay_xchat has joined #openstack-meeting-alt17:51
*** tonytan_brb has joined #openstack-meeting-alt17:51
*** kebray has joined #openstack-meeting-alt17:51
*** tonytan_brb is now known as tonytan4ever_17:51
*** weshay_xchat is now known as weshay17:51
*** jjmb has quit IRC17:52
*** lazy_prince has quit IRC17:53
*** AndreyPavlov has joined #openstack-meeting-alt17:53
*** prithiv has joined #openstack-meeting-alt17:53
*** paul-carlton1 has quit IRC17:53
*** prithiv has quit IRC17:53
*** tonytan4ever has quit IRC17:54
*** jjmb has joined #openstack-meeting-alt17:55
*** kfarr has joined #openstack-meeting-alt17:55
*** Sukhdev has quit IRC17:55
*** cody-somerville- has joined #openstack-meeting-alt17:57
*** dshakhray has quit IRC17:57
*** tcammann_ has joined #openstack-meeting-alt17:57
*** Sukhdev has joined #openstack-meeting-alt17:57
*** Aish has quit IRC17:57
*** tcammann has joined #openstack-meeting-alt17:58
*** jjmb1 has joined #openstack-meeting-alt17:58
*** epheo has joined #openstack-meeting-alt17:58
*** Sukhdev has quit IRC17:59
*** ninag has quit IRC17:59
*** jjmb has quit IRC17:59
*** ninag has joined #openstack-meeting-alt17:59
*** Sukhdev has joined #openstack-meeting-alt18:00
*** Sukhdev has quit IRC18:00
*** jmckind has quit IRC18:01
*** ninag_ has joined #openstack-meeting-alt18:01
*** ninag has quit IRC18:04
*** tcammann has quit IRC18:05
*** tcammann_ has quit IRC18:05
*** cody-somerville- has quit IRC18:05
*** tcammann_ has joined #openstack-meeting-alt18:06
*** tcammann has joined #openstack-meeting-alt18:06
*** epheo has quit IRC18:06
*** jjmb1 has quit IRC18:06
*** ikutukov has quit IRC18:07
*** paul-carlton1 has joined #openstack-meeting-alt18:07
*** ikutukov has joined #openstack-meeting-alt18:07
*** mfedosin has quit IRC18:08
*** cody-somerville- has joined #openstack-meeting-alt18:08
*** ninag_ has quit IRC18:09
*** epheo has joined #openstack-meeting-alt18:09
*** ninag has joined #openstack-meeting-alt18:09
*** ninag has quit IRC18:10
*** ninag has joined #openstack-meeting-alt18:10
*** ninag has quit IRC18:10
*** Aish has joined #openstack-meeting-alt18:10
*** ninag has joined #openstack-meeting-alt18:11
*** ashleighfarnham has quit IRC18:11
*** tcammann has quit IRC18:11
*** tcammann has joined #openstack-meeting-alt18:12
*** zeih has quit IRC18:13
*** paul-carlton1 has quit IRC18:13
*** egallen has quit IRC18:14
*** ashleighfarnham has joined #openstack-meeting-alt18:14
*** yamahata has joined #openstack-meeting-alt18:14
*** cody-somerville- has quit IRC18:15
*** tcammann_ has quit IRC18:15
*** ninag has quit IRC18:15
*** davideagnello has joined #openstack-meeting-alt18:15
*** epheo has quit IRC18:15
*** tcammann_ has joined #openstack-meeting-alt18:16
*** jesusaurus has joined #openstack-meeting-alt18:16
*** tcammann has quit IRC18:17
*** mrmartin has joined #openstack-meeting-alt18:18
*** iyamahat has joined #openstack-meeting-alt18:18
*** rsyed is now known as rsyed_away18:19
*** xyang1 has joined #openstack-meeting-alt18:19
*** jesusaurus has quit IRC18:21
*** dims_ has joined #openstack-meeting-alt18:21
*** tcammann_ has quit IRC18:22
*** dims has quit IRC18:22
*** yamahata has quit IRC18:23
*** yamahata has joined #openstack-meeting-alt18:24
*** pballand has quit IRC18:24
*** apetrich_ has joined #openstack-meeting-alt18:25
*** baoli has quit IRC18:27
*** apetrich has quit IRC18:27
*** mrmartin has quit IRC18:30
*** vkmc_ has quit IRC18:30
*** rossella_s has quit IRC18:31
*** tonytan4ever has joined #openstack-meeting-alt18:31
*** rossella_s has joined #openstack-meeting-alt18:32
*** tonytan_brb has joined #openstack-meeting-alt18:33
*** tonytan4ever has quit IRC18:33
*** tonytan4ever_ has quit IRC18:34
*** tonytan_brb has quit IRC18:34
*** tonytan4ever has joined #openstack-meeting-alt18:34
*** bana_k has quit IRC18:36
*** zeih has joined #openstack-meeting-alt18:37
*** balajiiyer has joined #openstack-meeting-alt18:37
*** shashank_hegde has joined #openstack-meeting-alt18:37
*** neelashah has quit IRC18:38
*** neelashah has joined #openstack-meeting-alt18:38
*** _nadya_ has joined #openstack-meeting-alt18:38
*** andrey-mp has joined #openstack-meeting-alt18:40
*** tonytan4ever has quit IRC18:42
*** tonytan4ever has joined #openstack-meeting-alt18:43
*** thomnico has quit IRC18:43
*** fnaval has quit IRC18:44
*** s3wong has joined #openstack-meeting-alt18:45
*** tonytan_brb has joined #openstack-meeting-alt18:45
*** SumitNaiksatam has joined #openstack-meeting-alt18:45
*** pballand has joined #openstack-meeting-alt18:45
*** rockyg has joined #openstack-meeting-alt18:45
*** bana_k has joined #openstack-meeting-alt18:46
*** Aish has quit IRC18:47
*** pvaneck has joined #openstack-meeting-alt18:48
*** tonytan4ever has quit IRC18:48
*** Aish has joined #openstack-meeting-alt18:49
*** catherineD|2 has joined #openstack-meeting-alt18:50
*** alexandrelevine has joined #openstack-meeting-alt18:50
*** hyamauchi has joined #openstack-meeting-alt18:51
*** tonytan_brb has quit IRC18:54
*** tonytan4ever has joined #openstack-meeting-alt18:55
*** johnbelamaric1 has joined #openstack-meeting-alt18:56
*** johnbelamaric1 has left #openstack-meeting-alt18:58
*** ihrachys has joined #openstack-meeting-alt18:59
*** gjayavelu has joined #openstack-meeting-alt19:00
*** salv-orl_ has quit IRC19:00
catherineD|2#startmeeting refstack19:01
openstackMeeting started Mon Feb  1 19:01:12 2016 UTC and is due to finish in 60 minutes.  The chair is catherineD|2. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: refstack)"19:01
openstackThe meeting name has been set to 'refstack'19:01
*** vilobhmm11 has joined #openstack-meeting-alt19:01
pvanecko/19:02
alexandrelevineo/19:02
*** neelashah has quit IRC19:02
catherineD|2#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-02-0119:03
*** ihrachys has quit IRC19:04
*** ninag has joined #openstack-meeting-alt19:04
*** julim has quit IRC19:04
alexandrelevineHi, everybody. FYI: thanks to Andrey, here is the RefStack with implemented Vendors (you'll have to click fake Sign-In to see all) - http://52.49.129.72:8000/#/19:05
*** ninag has quit IRC19:06
catherineD|2alexandrelevine: that is great... yea thx to Andrey ...19:06
*** ninag has joined #openstack-meeting-alt19:06
catherineD|2should foundation be listed in the vendor list?19:07
*** ddecapit has joined #openstack-meeting-alt19:07
*** ddecapit is now known as DuaneDeC719:07
*** reedip_ has quit IRC19:07
alexandrelevineIt will.19:07
*** sslypushenko has joined #openstack-meeting-alt19:07
catherineD|2but should it?19:07
alexandrelevineWhen it'll register Vendor OpenStack - it'll show.19:08
sslypushenkoo/19:08
alexandrelevineWhy not?19:08
catherineD|2in fact that is one of the topic for today;s discussion ...19:08
catherineD|2sslypushenko: #link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-02-0119:08
*** julim_ has joined #openstack-meeting-alt19:08
alexandrelevineIsn't it a Vendor? I'd say it's the most important one. And should be proudly displayed :)19:08
*** ikutukov has quit IRC19:08
sslypushenkocatherineD|2:  thx19:08
*** jmckind has joined #openstack-meeting-alt19:09
andrey-mpI list Foundation in the list to make a link to Foundation page where user management will be.19:09
catherineD|2#link Andrey's prototyp vendor UI http://52.49.129.72:8000/#/19:09
catherineD|2alexandrelevine: andrey-mp: we will discuss this later ..19:10
catherineD|2#topic Organization and product entities19:10
*** openstack changes topic to "Organization and product entities (Meeting topic: refstack)"19:10
catherineD|2#link     Database tables spec :  https://review.openstack.org/#/c/268922/19:10
*** zeih has quit IRC19:10
catherineD|2once sslypushenko: review the spec .. we should be ready to merge ...19:11
catherineD|2next could every one review Andrey's implementation ...19:11
sslypushenkosslypushenko: Will do it after this meeting19:11
*** rsyed_away is now known as rsyed19:12
*** baoli has joined #openstack-meeting-alt19:12
catherineD|2#link organizatio/product data model implementation :  https://review.openstack.org/#/c/269066/19:12
catherineD|2sslypushenko: thx19:12
*** julim_ has quit IRC19:12
catherineD|2next I would liketo go to topic #3 first19:13
catherineD|2#topic Product types:19:13
*** openstack changes topic to "Product types: (Meeting topic: refstack)"19:13
catherineD|2I suggest we use the same terms as used in the OpenStack Marketplace ...19:14
sslypushenkocatherineD|2:  +119:14
catherineD|2in that way the marketplace can just is a link from refstack for detail data of the certifiication ...19:14
alexandrelevinecatherineD: What do we gain? Are there any reqs motivating this?19:14
catherineD|2so software product is actually distor19:15
alexandrelevine"distro" is fine but I don't see what's wrong with "software"19:15
*** baoli_ has joined #openstack-meeting-alt19:15
alexandrelevinedistribution - is just a subset of software products. If I create my own Hello world script, put it into my cloud and register it for myself to test - it's not a distro, right?19:16
catherineD|2I would like to replace the link (full results) in this page https://www.openstack.org/marketplace/distros/distribution/ibm/ibm-cloud-manager-with-openstack with a link to RefStack19:17
*** baoli has quit IRC19:18
catherineD|2and I do not want to confuse openstack user19:18
*** kzaitsev_mb has quit IRC19:18
sslypushenkoalexandrelevine:  using the same terms with openstack.org will reduce user confusing.  It is enough  reason for such naming. Don't you think so?19:18
*** egallen has joined #openstack-meeting-alt19:18
alexandrelevinesslypushenko: No, because it expands a number of types which will cause more problems. We'll need to define use-cases to work with those types. User will have to define it. What happens, when some private cloud becomes public. And so on.19:19
catherineD|2if you clich "show full result link" on that page it goes to a table ... I would like that link to go to refstack19:19
*** vishwanathj has joined #openstack-meeting-alt19:20
*** julim has joined #openstack-meeting-alt19:20
alexandrelevinecatherineD: I don't see how it relates to our naming in DB. I still think terms software and cloud are the most generic, native and safe. If we decide to somehow display them by political reasons later with other names - we'll have the chance.19:20
*** gjayavelu has quit IRC19:20
sslypushenkoalexandrelevine:  If product type changes, we should change it in DB. Do we have other options?19:20
alexandrelevinecatherineD: And again - the software we're speaking of not only "distros"19:21
catherineD|2alexandrelevine: on the box where you lable software you  can put (software, distro, appliances) ,,, they are the names of the entities that are privately held .. that is the main point ...19:21
*** neelashah has joined #openstack-meeting-alt19:21
alexandrelevinesslypushenko: Exactly. Which will create even more problems. All of this should be documented, thought of and (most important) traced to requirements. Do we have such requirements for such complications?19:21
*** zynzel has quit IRC19:21
*** artem_panchenko_ has quit IRC19:21
*** smillward has joined #openstack-meeting-alt19:21
rockygoops.  here now.19:22
catherineD|2rockyg: #link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-02-0119:22
alexandrelevinecatherineD: I don't see what's wrong with software as a type in DB opposing cloud. I'm against "distro"19:22
sslypushenkoalexandrelevine:  we don't have such kind of issues now and I don't get why we can not change type in if it changes...19:23
catherineD|2andrey-mp: what are the constants that you used for product?19:23
sslypushenkoalexandrelevine:  What is your point here?19:23
andrey-mpright now I defined two constants - software and cloud :)19:24
alexandrelevinesslypushenko: Right now in the requirements and in the model we have just two types: software and cloud. Now 3 are suggested - software (or distro) and two kinds of cloud types. Model will change. UI will change. All of it should be described in requirements, no?19:24
sslypushenkoIt looks like I missed some part of discussion)19:24
andrey-mpbecause implementation doesn't need more than two19:24
alexandrelevinesslypushenko: What do you mean what is my point? :)19:24
alexandrelevinesslypushenko: I thought it's obvious. I don't want to have to types of clouds because it's not motivated by requirements.19:25
sslypushenkoHow it is effects UI? It should be agnostic to number of product types19:25
alexandrelevine"two types"19:25
alexandrelevinesslypushenko: How during cloud registration we determine which type to use - public or private_host_cloud?19:25
catherineD|2alexandrelevine: you do ...19:26
catherineD|2vendor know what kind of product they have ...19:26
sslypushenkoUnder "we" you means RefStack?19:26
alexandrelevinecatherineD: Sorry, I lost you :) What "I do"?19:26
*** kebray has quit IRC19:26
*** rsyed is now known as rsyed_away19:26
alexandrelevinesslypushenko: Yes19:26
*** kebray has joined #openstack-meeting-alt19:27
alexandrelevinecatherineD: sslypushenko asked how it affects UI. Vendor will have to manually enter the type of the cloud which he doesn't have to currently.19:27
catherineD|2RefStack won't know which kind of product ... type  is a user input19:27
*** davideagnello has quit IRC19:28
sslypushenkoUser will input this info. Visibility of product does not depend ob product type. So product type should not affect UI19:28
alexandrelevinePlease don't get me wrong. I'll gladly accept N types of clouds. Let's ask our stakeholder (DefCore) about related requirements. If they formulate them, like "Vendor has to specify what kind of cloud he registers - public or private" - we'll comply.19:28
*** nikhil_k has joined #openstack-meeting-alt19:28
*** dkalleg has quit IRC19:28
catherineD|2alexandrelevine: I will be gladly to take that to DefCore19:29
alexandrelevinesslypushenko: How user enters this info? Where? He/she uses UI to register a Cloud. There should be a checkbox, dropdown or something for him/her to choose. That's how.19:29
alexandrelevinecatherineD: Absolutely, please do, if you think it's important and we want to have it right now.19:29
sslypushenkoalexandrelevine:  I think it can be kind of select or of product type and checkbox for private/public19:30
catherineD|2#action Catherine will confirm with DefCore whether a vendor has to specifu what hind of product he registers -- public, private, distros,19:30
alexandrelevinesslypushenko: I hope you don't confuse private/public cloud with our private(hidden)/public(visible to all) clouds in RefStack.19:31
*** nikhil has quit IRC19:31
catherineD|2specifu --> specify19:31
alexandrelevinesslypushenko: I was just saying that it should be reflected in UI.19:31
sslypushenkoalexandrelevine:  sure19:31
catherineD|2let's move on ... we will revisit this after we check with DefCore19:32
*** zynzel has joined #openstack-meeting-alt19:32
*** artem_panchenko_ has joined #openstack-meeting-alt19:32
*** asimov.freenode.net changes topic to "open discussion (Meeting topic: neutron_upgrades)"19:32
andrey-mpwhy we need checkbox public/private ? i thought it will be a switch in a cloud page19:32
sslypushenkoI just don't get why we should care about number of product types. It should be just kind of label19:32
catherineD|2sslypushenko: +119:32
catherineD|2#topic Vendor REST API19:33
*** openstack changes topic to "Vendor REST API (Meeting topic: refstack)"19:33
alexandrelevineandrey-mp: We're talking here about different private/public - private cloud or public cloud, not visibility in RefStack.19:33
catherineD|2#link     Vendor registation REST API spec: https://review.openstack.org/#/c/274837/19:33
sslypushenkoandrey-mp:  yeap, you are right19:33
catherineD|2#link     Vendor registration REST API implementation:  https://review.openstack.org/#/c/272188/19:33
alexandrelevinesslypushenko: It's one of the key properties in one of our key objects. If it's just a label - we'll put it into metadata and leave the type to differ "cloud", "software".19:33
andrey-mpabout spec. 1. why we need deletion of vendor?19:34
catherineD|2andrey-mp: it is just incase we need to ... but this should be a low priority ...19:34
andrey-mpok19:35
catherineD|2now the URL19:35
catherineD|2since this is vendor registration ... it makes sense to be /v1/vendors19:35
catherineD|2do we need /v1/foundations down the road ...?19:36
andrey-mp2. i don't understand 'Only foundation admins can create an official vendor.'. As I understood from scenario document - vendors will be created by users and foundation will approve them19:36
catherineD|2or would /v1/organizations be a better URL19:36
*** kairat_ has quit IRC19:36
*** Sukhdev has joined #openstack-meeting-alt19:37
alexandrelevinecatherineD: By the way, good point. I forgot several "removal" use-cases. Right now I have only one for Cloud removal. I guess I should add for Software and for Vendor, what do you think?19:37
catherineD|2only foundation can create official vendor19:37
catherineD|2alexandrelevine: I think so especialy for product ...19:37
sslypushenkocatherineD|2:  'approve' sounds better here19:38
rockygalexandrelevine, +1.  Definitely vendors can go away.19:38
andrey-mpcatherineD|2: who will be owner in this case?19:38
catherineD|2we can talk about removal being soft or hard delete from the db ... but I think we need removal API but low priority19:38
rockygRemoval of vendor would be owned by foundation19:38
andrey-mprockyg: good point19:39
catherineD|2official vendors creation and removal both own by founation19:39
alexandrelevinecatherineD: I think, "create" and "approve" it's the same - Foundation has the final say in the matter.19:39
rockygremoval of product, vendor or foundation.  Same with cloud19:39
*** smillward has quit IRC19:39
catherineD|2rockyg: I think removal of product should only own by vendor19:39
andrey-mprockyg: i think that product and cloud (maybe only private) can be removed by ordinary user19:40
alexandrelevinecatherineD: Right now, you can see in the site that each User can request his created Vendor to be approved by Foundation. When Foundation admin approves - it'll become official.19:40
*** Sukhdev has quit IRC19:40
rockygIf vendor goes away, and foundation removes, will all the products go away with vendor removal?19:40
*** numans has quit IRC19:40
*** ijw has quit IRC19:40
andrey-mprockyg: yes. all products should removed with dependent vendor19:41
alexandrelevineandrey-mp: Definitely, private user clouds, software and non-approved vendors can be deleted by the User.19:41
*** Akis__ has joined #openstack-meeting-alt19:41
*** smillward has joined #openstack-meeting-alt19:41
andrey-mpalexandelevine: i mean the same point19:41
rockygThen ok.  Foundation doesn't need to be able to remove sw or cloud19:41
sslypushenkorockyg:  +119:41
catherineD|2we talk about this ealier about the complication of register a vendor .. need confirmation of website,email etc19:41
rockygIs there a way to transfer sw or cloud?  like company or product line gets sold?  Low priority19:42
sslypushenkoFoundation should have only approval role and that is all19:42
*** ScottMillward has joined #openstack-meeting-alt19:42
catherineD|2DefCore decides that official_vendor will be from a list that openstack alreaidy has19:42
andrey-mprockyg: it can be implemented via user management and vendor editing19:42
alexandrelevinecatherineD: Yes, and all of it will be entered by User during registration, but not by email - right in our RefStack site. Then Foundation admin checks everything and if all right approves.19:42
*** piet has joined #openstack-meeting-alt19:43
catherineD|2alexandrelevine: approving a vendor is not just register on RefStack ... there is legal procdedure that foundation need to do ...19:43
alexandrelevinecatherineD: This'll be in the beginning. And in any case there should be a user-friendly mechanism for entering this data, no?19:43
*** gongysh has joined #openstack-meeting-alt19:44
alexandrelevinecatherineD: Of course. Clicking "approve" button is just the last step. What's wrong with that?19:44
catherineD|2alexandrelevine: in the future maybe ... if RefStack taking a bigger task of on boarding vendor :-)19:44
alexandrelevinecatherineD: Does Foundation have new Vendors coming all the time?19:44
*** Akis_ has quit IRC19:45
*** mrmartin has joined #openstack-meeting-alt19:45
*** kfarr has quit IRC19:45
catherineD|2alexandrelevine: IMO, any implementation of approval process would not be just clicking a button .. it would involve a process and workflow .19:45
*** matrohon has joined #openstack-meeting-alt19:45
catherineD|2that is why at this phase only foundation memebers can create official vendors ..19:45
alexandrelevinecatherineD: Of course. Ok. Let's say, I'm a representative of EMC and I want EMC to register as a Vendor. What do I do?19:45
*** smillward has quit IRC19:45
alexandrelevinecatherineD: Of course. The will do this. I'm just suggesting convenient infrastructure for this.19:46
catherineD|2alexandrelevine: EMC will need to go thru what ever process OpenStack require a vendor to go thru19:46
*** Leom has quit IRC19:47
alexandrelevinecatherineD: Perfect. I suggest this process to be connected with the RefStack. I go to the RefStack panel. Enter all the information and click "apply". The information is delivered to Foundation and it handles it exactly the way it does now.19:47
catherineD|2alexandrelevine: I support we think ahead ... I oppose to allow user to create official vendor at this phase19:47
alexandrelevinecatherineD: Who said User can CREATE official vendor?19:47
rockygcatherineD|2,  right.  So, there might be more automation added in front of "approve" button when the foundation defines what the need.  But right now, "approve" only happens after the manual process they go through.19:47
alexandrelevinecatherineD: There is no such possibility.19:47
*** ninag has quit IRC19:48
alexandrelevinerockyg: Exactly.19:48
pvaneckI think one of my main worries with foundation-only vendor creation is the foundation member having trouble adding the first user for the vendor's group.19:48
catherineD|2alexandrelevine: how do you send infor to Foundation?19:48
pvaneckFoundation has to procure and email to add, and that user has to have logged in to refstack once in order to have a record in refstack. This could lead to slow-down in the process.19:48
alexandrelevinecatherineD: You can see it in the existing prototype.19:48
alexandrelevinecatherineD: You can create Vendor, fill in all the fields and click "Register". That's it. Foundation admin goes to his page in the same RefStack Panel and see the new Pending Vendor.19:49
catherineD|2alexandrelevine: I can't see what it is? you send an emai;?19:49
*** egallen has quit IRC19:49
*** egallen has joined #openstack-meeting-alt19:49
catherineD|2alexandrelevine: how do foundation member know how to go to this page?19:49
alexandrelevinecatherineD: Have you signed in?19:50
catherineD|2we do not have all of this notification infra implemeneted to suport this19:50
catherineD|2yea19:50
alexandrelevinecatherineD: Check "my vendors" at the bottom.19:50
alexandrelevinecatherineD: You'll see "pending" vendors.19:50
catherineD|2yes19:50
alexandrelevineAnd the button "approve registration"19:51
alexandrelevineThere should be an action "decline registration", of course, as well.19:51
alexandrelevineThis section "Pending vendors" will be available to Foundation Admin only.19:51
andrey-mpalexandrelevine: what should be in decline case?19:51
catherineD|2yes   my concern is how do you notify the person to take action ... and how do you control if that person does not take action?19:51
alexandrelevineandrey-mp: Information to user in "My Vendors" and status "declined"19:52
catherineD|2I am talking about an entire notification workflow ..19:52
alexandrelevinecatherineD: That's a different story. We can trigger it by manual email or by automatic email or by periodic checking - in any case it's no worse than anything without it.19:53
rockygcatherineD|2, good point.  An email to a list would be good on vendor completing their end of the process.  But right now, the foundation can easily lose stuff.  And does;-)19:53
alexandrelevinecatherineD: How does the entire notification workflow work now? Personal email?19:53
*** jkf has joined #openstack-meeting-alt19:54
catherineD|2rockyg: exactly ... that is why in this phase .. foundation has the sole responsibility to create/remove vendor19:54
catherineD|2until we have all this infrastructure in place ...19:54
alexandrelevinecatherineD: It still does. Come on, what's the difference?19:54
rockygso, right now, personal email or email alias.  But it's all a manual process.  So, no reminders if the email gets buried.19:54
alexandrelevinecatherineD: Ok. How do you suggest they deliver this info into our DB now.19:54
rockygSo, anything we automate will be better than what they currently have19:55
alexandrelevinerockyg: Exactly.19:55
catherineD|2alexandrelevine: at this point  official_vendor can only be created by foundation ...19:55
rockygMaybe we should have a "ping foundation" button for the vendors ?)19:55
alexandrelevinecatherinD: By what means?19:55
*** ihrachys has joined #openstack-meeting-alt19:55
alexandrelevinerockyg: "Register" is such a ping button.19:55
alexandrelevinerockyg: Do you have "ping" button in OpenStack review?19:56
rockygalexandrelevine, by manually adding them to the website.  Probably through content management system.  Forget the name of that thing.19:56
alexandrelevinerockyg: I can tell you how it works. We have to use email and IRC and skype to ping core teams to check our reviews, usually, right?19:56
*** diazjf has joined #openstack-meeting-alt19:56
rockygalexandrelevine, or you can change the commit message.  But lose all the votes19:57
*** ikutukov has joined #openstack-meeting-alt19:57
*** qwebirc40340 has joined #openstack-meeting-alt19:57
catherineD|2foundation members (like Chris) will create vendor from the RefStack UI , in addiiton RefStack will provide tools to import a vendor list in Json file ..pvaneck: is working on the import tools19:57
rockygJust because the devs don't make it convenient, doesn't mean we can't for the vendors and foundation19:57
alexandrelevinecatherineD: What RefStack UI should look like to create a vendor?19:57
*** dave-mccowan has quit IRC19:57
sslypushenkocatherineD|2:  It looks overcomplication19:58
catherineD|2all the input field as needed ...19:58
alexandrelevinecatherineD: Right now, it's exactly the Vendor creation. Just it's done by a proper person.19:58
rockyg"Push the button, Max!"  Reference to movie Around the world in 80 Days19:58
catherineD|2sslypushenko: what is over complication?19:58
*** pdesai has joined #openstack-meeting-alt19:58
*** ikutukov has quit IRC19:58
*** silos has joined #openstack-meeting-alt19:58
sslypushenkoexporting vendors data19:58
*** balajiiyer has quit IRC19:58
catherineD|2importing data19:59
catherineD|2?19:59
sslypushenkoIt looks like we need more time for discussion19:59
sslypushenkoexport/import workflow is overcomplication19:59
alexandrelevinecatherineD: Ok, I don't see any advantage of manual work with lists, import and such in comparison with nice input page in the panel where user fills in all the required info and Foundation admin only has to process it and approve.19:59
*** mp1 has joined #openstack-meeting-alt19:59
catherineD|2#link please check this link https://etherpad.openstack.org/p/mitaka-refstack-ation-items19:59
alexandrelevinesslypushenko: +119:59
* redrobot pokes head in20:00
*** jhfeng has joined #openstack-meeting-alt20:00
catherineD|2it was decided by DefCore on 20151029 that vendor will be import20:00
catherineD|2sorry20:00
catherineD|2qew need to end meeting20:00
*** egallen has quit IRC20:00
*** maxabidi has joined #openstack-meeting-alt20:00
catherineD|2#endmeeting20:00
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"20:00
openstackMeeting ended Mon Feb  1 20:00:42 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-02-01-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-02-01-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-02-01-19.01.log.html20:00
redrobot#startmeeting barbican20:00
openstackMeeting started Mon Feb  1 20:00:53 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
*** kfarr has joined #openstack-meeting-alt20:01
*** sslypushenko has left #openstack-meeting-alt20:01
redrobot#topic Roll Call20:01
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:01
*** ninag has joined #openstack-meeting-alt20:01
kfarro/20:01
jmckindo/20:01
woodster_o/20:01
silos\o/20:01
pdesaio/20:01
jhfengo/20:01
diazjfo/20:01
mp1o /20:01
edtubillo/20:01
*** alexandrelevine has left #openstack-meeting-alt20:02
redrobot#topic Action Items20:02
*** openstack changes topic to "Action Items (Meeting topic: barbican)"20:02
redrobotI've totally been slacking on these.  I did manage to complete 1/420:02
maxabidi0/20:02
maxabidio/20:02
*** amitgandhinz has quit IRC20:03
redrobotI sent pdesai some details regarding the doc team ask of publishing our API guide on docs.openstack.org/api-guide20:03
*** egallen has joined #openstack-meeting-alt20:03
*** harshs has quit IRC20:03
redrobotbut I'll have to punt on the other thee action items20:03
*** salv-orlando has joined #openstack-meeting-alt20:03
redrobot#action edrobot to check on status of reported security bug20:03
redrobot#undo20:03
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x9377c10>20:03
redrobot#action redrobot to check on status of reported security bug20:04
*** amitgandhinz has joined #openstack-meeting-alt20:04
redrobot#action redrobot to ping ccneill about the nova+cinder security bug20:04
redrobot#action redrobot to touch base with Designate folks20:04
redrobotclear20:04
* redrobot needs some coffee20:04
*** rellerreller has joined #openstack-meeting-alt20:04
rellerrellero/20:04
redrobotok, moving on20:04
redrobot#topic Liaison Updates20:04
*** andrey-mp has left #openstack-meeting-alt20:04
*** openstack changes topic to "Liaison Updates (Meeting topic: barbican)"20:04
*** weshay has quit IRC20:05
*** ninag has quit IRC20:05
redrobotI don't have anything to report today...  any of our other liaisons have anything to update on?20:05
*** electrocucaracha has joined #openstack-meeting-alt20:05
pdesaiyup i received your email redrobot, we need two patches for it, before we get started with those patches, it will be great to have this merged: https://review.openstack.org/#/c/236123/11 (userguide on orders)20:05
*** kfarr has quit IRC20:05
*** alee has joined #openstack-meeting-alt20:05
*** mrmartin has quit IRC20:05
aleeo/20:05
redrobotpdesai agreed20:06
redrobothi alee !20:06
redrobotalee any updates from Magnum?20:06
aleeno updates20:06
redrobotalrighty20:07
redrobotmoving on to today's agenda20:07
elmikoo/20:07
aleesorry - I've been focused on getting ready for conferenrce this week20:07
redrobotalee  no worries20:07
redrobot#topics Castellan Object Patches20:07
redrobot#topic Castellan Object Patches20:07
*** openstack changes topic to "Castellan Object Patches (Meeting topic: barbican)"20:07
*** salv-orlando has quit IRC20:07
redrobotdiazjf o/20:07
diazjfSo rellerreller and kfarr have provided excellent feedback. I was concerned on wether we should limit the parameters or include all possible keystone parameters for auth20:08
*** arunkant has joined #openstack-meeting-alt20:08
diazjfSee comments in https://review.openstack.org/#/c/270602/20:08
arunkanto/20:08
diazjfhttps://review.openstack.org/#/c/270602/2/castellan/common/credentials/keystone_password.py20:09
diazjfI agree with rellerreller and will update the patch tonight20:09
*** kfarr has joined #openstack-meeting-alt20:10
redrobotdiazjf awesome20:10
rellerreller:)20:10
redrobot#topic Google Hangouts20:10
*** openstack changes topic to "Google Hangouts (Meeting topic: barbican)"20:10
redrobotdiazjf another one of yours20:10
diazjfyup :)20:10
diazjfok so I wanted to setup 2 google hangout sessions this week20:10
diazjf1 to go over BYOK20:11
jkfo/20:11
diazjf2 to help alee with puppet20:11
diazjfJust wanted to see if there was any interest in going over these topics this week20:11
rellerreller+1 for BYOK20:11
aleediazjf, I'd love to set up a session but I'll bve travelling/ in conference for most of the week.20:12
kfarrdiazjf +1 BYOK20:12
diazjfrellerreller, kfarr, how do you feel about Tuesday or Wednesday?20:12
diazjfalee, we'll talk then when you get back20:12
rellerrellerTuesday is better for me20:12
kfarreither works for me, afternoons are better20:13
rellerreller3:00 PM ET Tuesday?20:13
aleediazjf, if you like , we can talk a bit after this meeting.20:13
diazjfrellerreller, perfect20:13
diazjfalee, sure we can talk a little about it20:13
rellerrellerkfarr ?20:13
aleediazjf, ok - lets do that20:14
kfarrrellerreller, diazjf +1 for 320:14
*** sbalukoff has joined #openstack-meeting-alt20:14
diazjfawesome, so I have nothing else20:15
*** egallen has quit IRC20:15
redrobotdiazjf awesome, thanks20:15
redrobotok, moving on20:15
redrobot#topic Blueprints20:15
*** openstack changes topic to "Blueprints (Meeting topic: barbican)"20:15
*** grimlock86 has joined #openstack-meeting-alt20:16
redrobotwe still have a lot of blueprints in review20:16
*** dave-mccowan has joined #openstack-meeting-alt20:16
redrobotand there's only 4 weeks of development time left20:16
redrobotbefore the feature freeze release20:16
*** panatl has joined #openstack-meeting-alt20:16
silosI updated the ones on launchpad in barbican that had the 'mitaka' release target20:16
redrobotsilos awesome!  you da man!20:17
silosredrobot: thx!20:17
redrobot#link https://blueprints.launchpad.net/barbican20:17
*** ikutukov has joined #openstack-meeting-alt20:17
*** weshay has joined #openstack-meeting-alt20:18
*** mhickey has joined #openstack-meeting-alt20:18
redrobotAlso please take a look at the open specs for review20:18
redrobot#link https://review.openstack.org/#/q/project:openstack/barbican-specs+status:open20:18
*** harshs has joined #openstack-meeting-alt20:19
*** harshs has quit IRC20:19
redrobotthat's all we had on the agenda for today20:19
*** tonytan_brb has joined #openstack-meeting-alt20:19
redrobot#topi Open Discussion20:19
*** kebray has quit IRC20:19
redrobotare there any other topics we should talk about while we're here?20:19
woodster_Please review this CR, as it adds missing contraint/defaults when setting up database via alembic: https://review.openstack.org/#/c/274276/20:19
*** tonytan4ever has quit IRC20:19
rellerrellerAny proposed talks for Austin?20:20
jkfI'd like to get some more eyes on the pkcs11 padding bug fix I submitted, so it can get merged... https://review.openstack.org/#/c/27057220:20
redrobotrellerreller good question20:20
redrobot#link https://etherpad.openstack.org/p/barbican-austin-summit-talks20:20
hockeynuto/ better late than never!20:20
redrobotrellerreller ^^ we have an etherpad to track those20:20
redrobottoday is the last day to propose talks, so if you have something in mind, today would be the day to put an abstract in!20:21
panatlo/20:21
arunkantredrobot: can core reviewer look into audit patch https://review.openstack.org/#/c/217523/ ..has been pending for a while.20:21
hockeynutrellerreller noooooo!20:22
* hockeynut is looking for the attendance etherpad20:22
rellerrellerhockeynut ?20:22
*** harshs has joined #openstack-meeting-alt20:23
*** baoli_ has quit IRC20:23
arunkant_wooster: Can you please look into this again (sqlaclhemy connection leak) : https://review.openstack.org/#/c/263358/20:23
arunkants/_wooste/_woodster20:24
jhfengredrobot: we submitted one. I'll add it into the etherpad20:24
*** egallen has joined #openstack-meeting-alt20:25
*** tonytan_brb has quit IRC20:26
*** neelashah1 has joined #openstack-meeting-alt20:26
*** tonytan4ever has joined #openstack-meeting-alt20:26
woodster_arunkant:  will do20:26
redrobotany other topics we should talk about?20:27
arunkantthanks woodster_20:27
redrobotif not we can be done with the meeting early today.20:27
arunkantredrobot: I did update the https://review.openstack.org/#/c/263972/20:28
redrobotarunkant awesome20:28
redrobotwoodster_ rellerreller can you guys please re-review arunkant 's BP20:28
*** neelashah has quit IRC20:28
arunkantredrobot: looks like most of rellerreller questions/concerns were answered in previous patch discussion.20:29
redrobotI'm concerned that it probably won't land for mitaka since it's such a big change.20:29
rellerrellerI would not say that all of my concerns are gone.20:29
arunkantredrobot: It depends on how soon this is approved.20:29
rellerrellerOne feature that is common to PKCS11 and KMIP is key wrapping. I think that needs to be worked out before agreeing to this.20:29
arunkantrellerreller: Please mention the details of issue in patch. As per earlier comments, transport key should not be a concern.20:30
rellerrellerI think this should be discussed in Austin.20:31
arunkantrellerreller: summit is over 2 months away..will be good to have some progress before that.20:32
*** markmcclain has quit IRC20:32
redrobotrellerreller +1 ...  I think it should be good to iterate on the Blueprint before then though.20:32
rellerrellerredrobot +120:32
*** rockyg has left #openstack-meeting-alt20:32
*** markmcclain has joined #openstack-meeting-alt20:33
redrobotok y'all20:33
redrobotseems like we're out of topics for today20:33
redrobotso we all get 25 min of our day back. :)20:34
elmiko\o/20:34
redrobotdon't forget to review!20:34
redrobot#endmeeting20:34
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"20:34
openstackMeeting ended Mon Feb  1 20:34:12 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-02-01-20.00.html20:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-02-01-20.00.txt20:34
*** mp1 has left #openstack-meeting-alt20:34
*** maxabidi has quit IRC20:34
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-02-01-20.00.log.html20:34
elmikothanks redrobot20:34
*** silos has left #openstack-meeting-alt20:34
*** DuaneDeC7 has quit IRC20:34
*** arunkant has left #openstack-meeting-alt20:34
*** harshs has quit IRC20:36
*** qwebirc40340 has quit IRC20:38
*** DuaneDeC7 has joined #openstack-meeting-alt20:38
*** jhfeng has left #openstack-meeting-alt20:38
*** gongysh has quit IRC20:38
*** _nadya_ has quit IRC20:40
*** ashleighfarnham has quit IRC20:40
*** harshs has joined #openstack-meeting-alt20:41
*** Leo_ has joined #openstack-meeting-alt20:41
*** dane has quit IRC20:43
*** Leom has joined #openstack-meeting-alt20:43
*** kebray has joined #openstack-meeting-alt20:44
*** DuaneDeC7 has quit IRC20:44
*** DuaneDeC7 has joined #openstack-meeting-alt20:44
*** baoli has joined #openstack-meeting-alt20:45
*** baoli has quit IRC20:45
*** baoli has joined #openstack-meeting-alt20:46
*** Leo_ has quit IRC20:46
*** iyamahat has quit IRC20:47
*** zeih has joined #openstack-meeting-alt20:48
*** ninag has joined #openstack-meeting-alt20:48
*** sc68cal has joined #openstack-meeting-alt20:50
*** dane has joined #openstack-meeting-alt20:51
*** cbouch has joined #openstack-meeting-alt20:51
*** salv-orlando has joined #openstack-meeting-alt20:53
*** thomasem is now known as thomasem-away20:53
*** Sukhdev has joined #openstack-meeting-alt20:54
*** balajiiyer has joined #openstack-meeting-alt20:55
*** diazjf1 has joined #openstack-meeting-alt20:55
*** hichihara has joined #openstack-meeting-alt20:55
*** neiljerram has quit IRC20:55
*** diazjf has quit IRC20:57
*** ashleighfarnham has joined #openstack-meeting-alt20:57
*** edtubill has quit IRC20:57
*** kzaitsev_mb has joined #openstack-meeting-alt20:58
*** barrett1 has joined #openstack-meeting-alt20:59
*** leong has joined #openstack-meeting-alt20:59
barrett1#startmeeting Product Working Group21:00
openstackMeeting started Mon Feb  1 21:00:35 2016 UTC and is due to finish in 60 minutes.  The chair is barrett1. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: Product Working Group)"21:00
openstackThe meeting name has been set to 'product_working_group'21:00
*** pchadwick has joined #openstack-meeting-alt21:00
shamailhi all21:00
leonghi21:00
barrett1Hi Folks - Let's start with role call21:00
sgordon`o/21:01
barrett1Hi Shamail21:01
pchadwicko/21:01
barrett1Hi Leong21:01
barrett1Hi Pete21:01
shamailPresent21:01
barrett1Hi Steve21:01
kencjohnstono/21:01
pchadwickHi all21:01
kencjohnstonwelcome back barrett1 !21:01
*** MeganR has joined #openstack-meeting-alt21:01
shamail++21:01
*** egafford has joined #openstack-meeting-alt21:01
barrett1Thanks Kenny - Good to type with everyone again ;-)21:01
kencjohnston:)21:01
*** leong_ has joined #openstack-meeting-alt21:02
kencjohnstonIt's a miracle shamail survived21:02
barrett1The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/product-team21:02
*** dims has joined #openstack-meeting-alt21:02
shamailhaha21:02
barrett1kencjohnston: LOL21:02
leong_LOL21:02
barrett1more suprising is that you missed me at all!21:02
thingeeo/21:02
barrett1Hi MIke21:03
barrett1Ok Let's get going21:03
barrett1#topic Review actions items from last meeting21:03
*** openstack changes topic to "Review actions items from last meeting (Meeting topic: Product Working Group)"21:03
*** dims_ has quit IRC21:03
barrett1#link http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-25-21.00.html21:03
*** egafford has left #openstack-meeting-alt21:03
*** rellerreller has quit IRC21:04
shamailI can start with mine21:04
barrett1Thanks Shamail21:04
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:04
Arkady_Kanevskyhello21:04
shamailI sent an email out to the mailing list to ask for more volunteers as CPL (mainly Keystone) but no replies21:04
shamailhi Arkady_Kanevsky21:04
*** egallen has left #openstack-meeting-alt21:04
kencjohnstonbarrett1 I can report we did merge the pending "Upgrades Gaps Analysis" CR21:04
*** zeih has quit IRC21:04
Arkady_Kanevskysaw that.21:05
*** nateziemann has joined #openstack-meeting-alt21:05
shamailI also sent out the reminder for the CFP submission deadline (which was extended today to tomorrow)21:05
*** leong has quit IRC21:05
*** nateziemann has quit IRC21:05
barrett1kencjohnston:: we'll get to yours in a min21:05
*** jkf has left #openstack-meeting-alt21:05
shamailI still have to update the wiki go incorporate the CSPL role in the workflow21:05
*** nateziemann has joined #openstack-meeting-alt21:05
shamailill do that this week21:05
shamailthats all from me :]21:05
*** leong_ is now known as leong21:05
MarkBaker0/21:06
leongi haven't update the FAQ yet21:06
leongi can't seem to find the email from Kenny21:06
kencjohnstonleong I'll forward it to you now21:06
leongkencjohnston: do you still have that email>?21:06
leongok. thanks!21:06
barrett1Shamail: What follow-on actions should we take since there was no response to your email?21:06
*** egafford has joined #openstack-meeting-alt21:06
leongi have included the meeting-time to midcycle meetup agenda21:07
*** rockyg has joined #openstack-meeting-alt21:07
shamailLet's take it up at the mid-cycle since there is a bigger topic there21:07
*** baoli has quit IRC21:07
barrett1Shamail: OK21:07
rockygo/21:07
shamailThe next major item we need the CPL for is the roadmap refresh so holding off until mid-cycle won't slow anything down21:07
*** fzdarsky is now known as fzdarsky|afk21:07
*** baoli has joined #openstack-meeting-alt21:07
*** fnaval has joined #openstack-meeting-alt21:08
*** baoli has quit IRC21:08
barrett1Leong: When will you complete the FAQ update by?21:08
*** rocky_g has joined #openstack-meeting-alt21:08
leongtoday.. once i got the email :-)21:08
*** baoli has joined #openstack-meeting-alt21:09
barrett1#action Leong Complete update of FAQ adding in FAQ by 2/2/1621:09
leongand just got the email :-)21:09
Arkady_KanevskyOK. I will update QA one after mid cycle21:09
*** jmckind has quit IRC21:09
*** esker has quit IRC21:09
*** markmcclain has quit IRC21:09
barrett1kencjohnston: Update on your action item?21:09
*** markmcclain has joined #openstack-meeting-alt21:09
kencjohnstonbarrett1 As mentioned CR was merged on Thursday21:09
* shamail cheers21:10
kencjohnstonbarrett1 For the other item, opening the user story for review and  sending around the gerrit link to Openstack-Dev, I need some advice21:10
kencjohnstonis there a best practice for creating a CR for review that doesn't have any changes?21:10
*** davideagnello has joined #openstack-meeting-alt21:10
barrett1kencjohnston: Great! (Sorry, still spinning back up on IRC flow)21:10
kencjohnstonI would imagine thingee sgordon` or rockyg woudl know.21:10
sgordon`what did i break21:11
shamaillol21:11
kencjohnstonsgordon` ha21:11
rocky_gI would think you could just change the commit message to something like gettingg dev input to.....21:11
thingeewhat is a cr?21:11
sgordon`so kencjohnston when you propose it21:11
*** hichihara has quit IRC21:11
kencjohnstonthingee change request21:11
sgordon`i think you need to do it against a new folder21:11
sgordon`proposed instead of draft21:11
rocky_gchange request21:11
sgordon`thus it is in fact a new change21:11
shamailthingee: patch in gerrit21:11
thingeeyou want to submit a change request that doesn't have changes?21:11
rocky_gotherwise known as how to start a new review on existing files that aren't changing?21:12
kencjohnstonthingee correect, so we have something open to accept comments on21:12
pchadwickWhy can't we just comment on the base?21:12
thingeeOk hang on21:12
thingeeI think we talked about this in the past.21:13
rocky_gyup21:13
kencjohnstonpchadwick I don't know how to do that, say more.21:13
thingeeSo I think last time we discussed, we said people merge stuff right away, because of readable reasons21:13
shamail#link https://review.openstack.org/#/c/255633/21:13
thingeeI said, what's so hard to read the format of these documents21:13
*** Sukhdev has quit IRC21:13
sgordon`pchadwick, it21:13
shamailthingee, added the link to the review in question for your ref.21:13
sgordon`pchadwick, it's already merged21:13
thingeeand people agreed that it wasn't hard to read21:13
sgordon`pchadwick, so there is no review to comment on21:13
pchadwickAh - ok21:13
Arkady_Kanevskywhat is the point to comment on what is merged already?21:14
sgordon`Arkady_Kanevsky, dev review time21:14
kencjohnstonArkady_Kanevsky We wanted to ask a broader group for their feedback on the user story21:14
thingeeSo here's the thing, if people prefer to have something rendered in order to do reviews, we can have a job set to render documents21:14
thingeebut I think merging things right away is not a good idea21:14
sgordon`+121:14
shamailThis user story went through an internal review (only PWG members have looked at it) and we would now like to send it out to openstack-dev for greater community feedback21:14
Arkady_Kanevsky+221:14
thingeeyou should merge things when it's approved, and keep it iterating and commenting until you can merge it21:14
*** merooney has quit IRC21:14
thingeethe reason why gerrit doesn't allow what you're asking for is because it wasn't meant to be used this way21:15
Arkady_KanevskyDo we want wider audience to comment on whole user story?21:15
kencjohnstonthingee agreed. Honestly I think I'll just make some nit changes to the doc and submit them for review and leave it open.21:15
shamailall, maybe we should only accept things into "proposed" that have gone through PWG review and reserve "tracked" for community review... thoughts?21:15
sgordon`we actually already have a job that renders the stuff afaict21:15
sgordon`e.g. http://docs-draft.openstack.org/33/255633/7/gate/gate-openstack-user-stories-docs/8b21a31//doc/build/html/21:15
kencjohnstonany objections to that?21:15
thingeeSo I recommend we revert the merge of the file and then post again.21:15
leongshamail +121:15
shamailthingee: +121:15
thingeesgordon`: excellent21:15
sgordon`folks may not necessarily realize that you can click through to that from the review though21:16
Arkady_Kanevskydo not like revert.21:16
barrett1shamail: +121:16
thingeeArkady_Kanevsky: well you can't comment then21:16
shamailDoes my suggestion sound okay (for workflow amendment?)... it doesn't work in this case but we can prevent this scenario in the future21:16
thingeethat's just not gerrit reviews work21:16
Arkady_KanevskyIt is better to resubmit the full proposal for other folks to comment on it.21:16
sgordon`what about if they do a move?21:16
leongsgordon, looks like that job need to change to cater for the recently changes in folder structure21:16
*** grimlock86 has quit IRC21:17
*** edtubill has joined #openstack-meeting-alt21:17
Arkady_KanevskyIntiial merge shows that our group accepted it21:17
sgordon`e.g. currently it's draft/mything.rst and they propose moving it to proposed/mything.rst21:17
thingeeArkady_Kanevsky: if they accepted it, why do you need comments21:17
sgordon`(just riffing off the original flow)21:17
thingeeyou can't have it both ways21:17
shamailbarrett1, can you assign the action item to me?21:17
shamaildraft: review for syntax and language, proposed: internal PWG review, tracked: community review before merge21:17
*** jmckind has joined #openstack-meeting-alt21:18
sgordon`as a reminder this was the draft workflow: https://wiki.openstack.org/wiki/ProductTeam/User_Stories21:18
kencjohnstonshamail I'm happy to repost I just didn't know if there was a best practice21:18
Arkady_KanevskyLike the idea that we submit a pulll request to Copy or move user story from draft to accepted folder21:18
sgordon`i think folks are talking past each other21:18
barrett1#action Shamail draft: review for syntax and language, proposed: internal PWG review, tracked: community review before merge21:18
kencjohnstonsgordon` +!21:18
kencjohnston+1 :)21:18
*** rcernin has joined #openstack-meeting-alt21:18
shamailsgordon`: +121:18
thingeeArkady_Kanevsky: but then people can't comment on the draft21:18
barrett1The action is assigned, but we need to decide what to do with the current situation21:18
sgordon`so what we have atm from that diagram is a heap of stuff in the first column21:18
thingeeArkady_Kanevsky: it just doesn't work that way21:18
shamailbarrett1: +121:18
sgordon`which has been merged in draft/21:18
shamailI agree with thingee, maybe unmerge for this particular case21:19
barrett1kencjohnston: What direction do you want to go?21:19
kencjohnstonI'm happy to unmerge, rebuild the changes that happened during review and resubmit21:19
kencjohnstonI'm also happy to submit a nit change on the doc21:19
barrett1Does anyone have heartburn with that approach?21:19
shamailooo21:19
Arkady_Kanevskywe can add the state.21:19
shamailI prefer the nit change :)21:19
shamailwould serve the same purpose of opening up reviews again.21:19
barrett1Are we good with the Nit Change?21:20
Arkady_KanevskyThen we submit pull rquest toi change state to "VOTED" and let people to comment on full proposal.21:20
rocky_gNo, I like Arkady's, plan.  We can add a comment to the userstory so that it is changed.  Then the reviews will happen again.21:20
shamailagreed sgordon`21:20
sgordon`i am still thinking just moving it to proposed/21:20
sgordon`will make the whole thing come up as a new review21:20
rocky_gWe can add "Approved by PWG {date}21:20
barrett1rocky_g: Isn't that the Nit approach?21:20
Arkady_KanevskyWee have 2 levers. One is state. and one is folder.21:20
Arkady_KanevskyChange for each is new pull request21:21
rocky_gEither way works for me.  But having the record in the doc I think is a good thing21:21
barrett1OK so we have 2 proposals on the table: Change the State to Proposed (from Tracked) or make a Nit Change to cause new review cycle21:21
thingeeWhat is the point of this idea though? Gerrit reviews are for approving. Why create yet another thing for approving?21:22
shamailit should be passed proposed now (since we have all reviewed it) and it is getting resource assignments/gap21:22
*** ikutukov has quit IRC21:22
thingeeor rather indicating something is approved21:22
shamailbarrett1: I vote for nit change21:22
rocky_gDifferent group is approving the second time round21:22
barrett1thingee: it's to gather comments21:22
shamailthingee: the first approval was from the PWG... we want to now open it up for community review now that we agree with it21:22
thingeeBut your process is the reason why you're creating this other thing21:22
thingeelet me explain again21:22
Arkady_Kanevskydifferent audience. And because of that different merge criteria.21:22
thingeeThe initial review is the time to gather comments. Don't merge the thing until comments are satisified. The things that aren't ready are the open reviews.21:23
thingeeI just can't understand why we're making things more complicated21:23
pchadwickBut this is more like just adding another gate21:23
thingeewhy?21:23
thingeewhat do you gain?21:23
Arkady_Kanevskysee https://wiki.openstack.org/wiki/File:Userstoryflow.png21:23
pchadwickwe have reviewed, now we get wider input21:23
*** baoli has quit IRC21:24
thingeecc people you want wider input from. that's the point of gerrit reviews21:24
rocky_gSo, the first merge is PWG is ready to expose the story for comments/approval.  It's a multistage comment/approval process.21:24
Arkady_Kanevsky<pchadwick> - right21:24
sgordon`i am +1 to what thingee is saying here because we have some recent items that i think would get early negative feedback from the community and it's better to realize that sooner than later21:24
pchadwickLast time we said we wanted the developers to look at it.21:24
thingeewe do it on cross-project specs all the time21:24
sgordon`so that you can work that feedback in21:24
thingeepchadwick: great, why can't they comment on the initial review before merging?21:24
sgordon`as it stands it's "approved" but that doesn't really mean a lot in the grand scheme of things21:24
pchadwickOk, so then PWG shouldn't merge until we get the reviews.21:25
thingeeright21:25
kencjohnstonAn alternative would be to send an email to the dev list and say "CRs welcome"?21:25
Arkady_KanevskyThe first stage is to get enough content for developers to review it. If we are missing impact on some project, say nova, then nova dev folks will just ignore it.21:25
barrett1Folks - I think we've got 2 discussions going in parallel. How to handle the current situation and how to update our work flow for future use21:25
shamailthingee and sgordon`: Are you suggesting that the first review (product-wg review) should happen at the draft state and then it should be open thereafter?21:25
barrett1Can we solve these one at a time?21:25
thingeeI guess who are the developers that you want to talk to?21:25
shamailbarrett1: +121:25
kencjohnstonbarrett1 +1, one at a time.21:26
shamailLet's park the "workflow for future use" until the mid-cycle and focus on the current rolling upgrades story for now...21:26
barrett1Shamail: +121:26
leongshamail +!21:26
pchadwick+121:26
Arkady_Kanevsky+121:26
rocky_g+121:26
barrett1#action Carol Add work flow changes to mid-cycle agenda21:27
kencjohnstonshamail +121:27
thingeebarrett1: if you remember, this came up because you can't figure out how to get comments on something you already merged. This is going to keep happening until you resolve the workflow problem21:27
* shamail had to put out a small kitchen fire while having this conversation... good times.21:27
*** markmcclain has quit IRC21:27
barrett1thingee: the midcycle is in 2 weeks, think we'll be OK til then21:27
Arkady_Kanevskypointer to rolling upgrade user story?21:27
thingeeso don't merge anything until then21:27
pchadwickhttps://review.openstack.org/#/c/254389/21:28
* rocky_g would have like to roast some marshmallows befor shamail put out his fire21:28
barrett1thingee: It's already been merged and we want to get developer feedback - this is the situation we're trying to figure out21:28
*** julim has quit IRC21:28
thingeeok so you can't. I just told you that.21:28
kencjohnstonHow about I'll just send my note with a reference to the User Story and ask for changes.21:28
thingeeyou have to unmerge it and post it for review again21:28
Arkady_Kanevskyit has 2 +2 already. Do you still want input for it?21:28
shamailLet's make a small change so it re-opens it...21:29
kencjohnstonDoes that work for everyone?21:29
thingeekencjohnston: that's going to be annoyign to have a bunch of reviews for one thing to get feedback21:29
thingeeit's also just not the normal workflow in the openstack project21:29
barrett1Shamail +1;21:29
barrett1kencjohnston: +121:29
kencjohnstonthingee ok so the next alternative in my mind is the nit change.21:29
shamailthingee: so the best way would be to remove it and then re-submit?21:29
thingeeshamail: that also is a problem. Some of the review will be collapsed unless people expand the parts that are not similar to the previous revision21:30
Arkady_Kanevskydo yuou want the feedback for just that change or for the whole proposal? If full proposal - please, resubmit21:30
thingeeshamail: people assume the review is the stuff highlighted21:30
shamailthingee: makes sense.21:30
Arkady_Kanevskycore folks - you can vote +1 and wait for more review before you votre +221:30
rocky_gThingee, we're not a "project" persee, so our process may be different.21:30
shamailCleanest way seems to be to submit a patch to remove the story, then kencjohnston resubmit it.21:30
rocky_gWe are adapting a dev tool to work for our purposes.21:30
kencjohnstonshamail ok sounds good. I can do that.21:30
*** amrith is now known as _amrith_21:31
shamailsorry for the re-work kencjohnston21:31
barrett1Thingee: Are you OK with that approach?21:31
kencjohnstonnot really rework...21:31
shamailI'll keep an eye out and approve as soon as you submit (the removal)21:31
thingeerocky_g: ok, well if you're going to interact with the openstack community, they're not going to pick up on this process unless you explain it to them. and good luck with developers following all the instructions21:31
thingeeor humans in general :)21:31
rocky_gAnother thing we could do is add links to reviews that address this issue.  There are projects already working on it.21:31
Arkady_Kanevskyyou can revert...21:31
*** ikutukov has joined #openstack-meeting-alt21:31
thingeebarrett1: yes21:32
barrett1#action kencjohnston  submit a patch to remove the story, then resubmit it.21:32
Arkady_Kanevskythen resubmit21:32
shamailawesome.21:32
barrett1Folks - Can we close this one?21:32
kencjohnstonbarrett1 +121:32
thingeeand who are the developers that you want to target?21:32
shamailbarrett1, +121:32
rocky_gAlso, by adding the review links, we can get devs to comment on adding/removing others and it starts to build toward the gap analysis21:32
pchadwickbarrett1 +121:32
thingeebarrett1: ^21:33
barrett1thingee: do we need to be explicit?21:33
*** jungleboyj has quit IRC21:33
thingeewell I think it's not entirely useful to say the openstack developers. Trust me, I've been a ptl for a project for a couple of releases and leading the cross-project initiatives.21:33
Arkady_Kanevskywe can add PTL for each project impacted for review.21:34
*** DuaneDeC7 has quit IRC21:34
thingeesaying everyone is just throwing ideas at noise. Having focused people is more useful21:34
Arkady_KanevskyOr we can add Perez for it.21:34
barrett1kencjohnston: Do you know how to target the review to the PTLs for the key Projects we're targeing?21:34
kencjohnstonbarrett1 Yes, I will do CPLs and PTLs21:34
thingeeand that's why I ask this. I think PTLs are really unreliable unless they're onboard with helping21:35
kencjohnstonbarrett1 plus some other ugprade folks I know in various projects.21:35
thingeebecause you're one of many working groups wanting their attention21:35
*** markmcclain has joined #openstack-meeting-alt21:35
shamailkencjohnston: +1, should TC be copied too?21:35
kencjohnstonshamail I'm not sure, I'm open to adding them as an FYI21:35
barrett1#action kencjohnston Target the User Story review to required PTLs and Devs working on Upgrades21:36
barrett1Let's move on21:36
egaffordkencjohnston: +1 to add both CPLs and PTLs; increases chance that it'll receive attention from each project without diluting the call to action too much.21:36
shamailkencjohnston, fyi is good21:36
rocky_gDon't include TCs  They've got enough on their plates and many are PTLs anyway.21:36
thingeeshamail, kencjohnston it's pretty easy. In gerrit you click the add button and start typing in their name. It'll auto-complete21:36
shamailthingee: +121:36
kencjohnstonthingee thanks!21:36
barrett1Next actions are about reviewing User stories - did folks complete those?21:36
*** esker has joined #openstack-meeting-alt21:37
*** mhickey_ has joined #openstack-meeting-alt21:37
*** esker has quit IRC21:37
*** catherineD|2 has left #openstack-meeting-alt21:37
barrett1#link https://review.openstack.org/25322821:37
*** banix has quit IRC21:37
*** esker has joined #openstack-meeting-alt21:37
barrett1#link https://review.openstack.org/#/c/26987421:37
barrett1I will review this week; others ?21:38
shamailbarrett1: same here, sorry for the delay everyone.21:38
pchadwick+121:38
*** grimlock86 has joined #openstack-meeting-alt21:38
barrett1OK - will carry this action over21:38
barrett1# Action all Please review https://review.openstack.org/25322821:38
barrett1 #Action all Please review https://review.openstack.org/25322821:39
*** mhickey has quit IRC21:39
barrett1 #Action all Please review https://review.openstack.org/#/c/26987421:39
barrett1Next one is Shamail'sbout proposals21:39
*** grimlock861 has joined #openstack-meeting-alt21:40
barrett1#topic OpenStack Austin Talk Proposals21:40
*** openstack changes topic to "OpenStack Austin Talk Proposals (Meeting topic: Product Working Group)"21:40
barrett1#link https://etherpad.openstack.org/p/austin_summit_product_wg21:40
barrett1Piet: Are you here?21:40
*** MarkAtwood has quit IRC21:41
Arkady_Kanevskyreview https://review.openstack.org/#/c/269874 - its already merged. are oyu going to reopenit for comments?21:41
pietRunning an interview w an operator21:41
barrett1Piet: OK, was wondering where you are on the UX BoF on Personas21:41
barrett1Rocky_g: What's that status on yours?21:41
pietBoF?21:42
*** jprovazn has quit IRC21:42
barrett1BoF = Bird of Feather21:42
barrett1pchadwick: What's the status on yours?21:42
Arkady_KanevskyBOF sounds good. But it need to be done jointly with operator and user groups.21:42
pietWe didn't submit as BoF21:42
pietGotta go21:43
rocky_gI'm gonna put it together today.  I'm thinking we could do both the newbie session and a BOF.21:43
pchadwickI have the abstract, but no feedback on ether pad21:43
pchadwick(for the Epic discussion)21:43
*** grimlock86 has quit IRC21:43
barrett1rocky_g: Sound good21:43
barrett1pchadwick: can you post the link?21:43
pchadwickOn the enterprise panel we only have one committed participant21:43
barrett1pchadwick: who is it?21:43
Arkady_KanevskyBOF on big tent and multiple releases - droping it. No time to prepare submission21:43
barrett1Arkady_Kanevsky: OK21:44
pchadwickhttps://etherpad.openstack.org/p/austin_summit_product_wg (last one on the list)21:44
*** rcernin has quit IRC21:44
barrett1pchadwick: any word back from Doug Hellman?21:44
pchadwickNot yet21:44
barrett1dhellmann: Are you around?21:45
shamailpchadwick, I like the abstract but do you want to call out that epics == themes?21:45
*** matrohon has quit IRC21:45
pchadwickshamail +121:45
thingeeArkady_Kanevsky: for what it's worth, Thierry and Doug covered that subject quite well https://www.openstack.org/summit/tokyo-2015/videos/presentation/herding-cats-into-boxes-how-openstack-release-management-changes-with-the-big-tent ... curious what you see we would get from a bof?21:45
shamailWe have been referring to them as "themes" in our roadmap presentation and mitaka PTL interviews21:45
barrett1shamail: +121:45
pietSorry to jump in, but could really use a room at the Ops Summit for interviews/usability21:46
leongshamail +121:46
barrett1Team - pls review and provide add'l feedback to pchadwick21:46
barrett1Piet: Talk to Tom Fifield21:46
Arkady_Kanevsky<thingee> - agree. expect update once we start multiple release options per Mitake or Newton release.21:46
barrett1I have submitted the Community Roadmap proposal - thanks for the feedback. Nate, Hugh and I are the speakers21:47
shamailpiet, email Tom Fifeld or Matt Jarvis21:47
*** Sukhdev has joined #openstack-meeting-alt21:47
rocky_gpiet, the ops summit hasn't started compiling its sessions yet21:47
barrett1What about Confronting Complexity?21:47
kencjohnstonbarrett1 I'm ready to submit it this evening21:47
barrett1I think Piet is referring to the Ops Midcycle in Manchester21:47
barrett1kencjohnston: Excellent!21:48
leongkencjohnston: i assume you also include Kei?21:48
kencjohnstonleong yep!21:48
leong+121:48
barrett1kencjohnston: what about the OpenStack SWOT or Business Strategy proposal?21:48
kencjohnstonMarkBaker you still interested?21:48
kencjohnstonbarrett1 I'm planning on submitting that one as well21:48
kencjohnstonright now it is barrett1 and me, anyone else interested in joining?21:48
barrett1kencjohnston: You are on it! Thanks!21:49
pietNeed both.  Would love to have rooms at both.  In fact, there is a ton of value to the community if we could run studies at both summits.21:49
thingeeArkady_Kanevsky: multiple release options... you like intermediate, indepdent, milestone release types? https://governance.openstack.org/reference/tags/index.html#release-management-tags21:49
kencjohnston#link https://etherpad.openstack.org/p/AUS-Summit-BOF-Business-Strategy-Proposal-Draft21:49
thingeeArkady_Kanevsky: because those happened before mitaka.21:49
rocky_gI think the stabilization theme should be added to themes talk.21:49
barrett1Next one is Rolling Upgrades session. I know the Kolla team has proposed a session around this21:49
rocky_gIf you want, I can cover that one in the session.21:50
MarkBakerkencjohnston, sure21:50
*** banix has joined #openstack-meeting-alt21:50
kencjohnstonMarkBaker Great I'll add you to the submission.21:50
Arkady_KanevskyI am talking releases for Enterprise, NFV, HPC and others not general bi-annual "release" of openstack21:50
*** grimlock861 has quit IRC21:50
Arkady_KanevskyPete Chadwick - I will be happy to co-present with oyu21:50
barrett1Folks - It's hard to follow the discussion when we have multiple conversations going on the channel21:51
barrett1Arkady_Kanevsky: Can you and Pete close on that?21:51
Arkady_Kanevskyworking on it in etherpad21:51
barrett1Thank you21:51
barrett1Next one is the Stabilization efforts - Rockyg21:52
pchadwickArkady_Kanevsy: thanks. I assume you haven't hit your limit yet ;)21:52
MarkBakerkencjohnston, I'd like to see if I can work an economics angle in there too21:52
rocky_gI think that should be added as a new theme to the themes one.21:52
*** angdraug has joined #openstack-meeting-alt21:52
kencjohnstonMarkBaker Great, let's chat offline21:52
barrett1Rocky_g: So this isn't intending to introduce the new project and guidelines around it?21:53
barrett1Rocky_g: I think a BoF on the Stabalization project, at a minimum, would be good21:54
thingeebarrett1: what are the ideas with that exactly?21:55
rocky_gbarrett1, so it's not a project, so much as a cross project effort gaining awareness and importance in the dev community21:55
barrett1rocky_g: That makes BoF sound like a better fit21:56
barrett1Folks - We have 4 mins left. Have people looked at the Ops Midycle agenda?21:56
thingeerocky_g: i'd recommend working with the stabilization folks. Matt Riedemann heads that team21:56
barrett1Are there any topics that we want to propose? Or any volunteers to moderate already proposed sessions?21:56
rocky_gYup.  So, I can put together a BoF proposal on that.21:56
barrett1rocky_g: Thanks!21:57
kencjohnstonbarrett1 I've expressed my willingness to volunteer to Matt and Tom21:57
barrett1Great kencjohnston!21:57
thingeerocky_g: however as we've discussed in the past, it's hard to get support from the community. Linux distributions would rather keep making their money then contribute efforts there21:57
barrett1I replied that I would lead the user story session if they want21:57
shamailbarrett1: 3 min left21:57
rocky_gAnd I'll do the newbie "How you can make OpenStack better but you're not a developer" session21:57
thingeerocky_g: +121:58
thingeethat sounds awesome21:58
*** rossella_s has quit IRC21:58
thingeeand we need more of that21:58
barrett1rocky_g: +121:58
shamailDo we want to move over to #openstack-productwg to continue the conversation after our time is up or defer the remaining agenda items until next week?21:58
barrett1I can go for another 30 mins21:58
shamailsame21:59
leongsame21:59
kencjohnstonshamail sounds like last remaining item was a discussion around meeting times21:59
kencjohnstonI cannot stay on21:59
shamailhttps://wiki.openstack.org/wiki/Meetings/product-team21:59
shamailit got updated21:59
barrett1kencjohnston: agenda for our midcycle also needs discussion21:59
shamailremaining items are: stabilization user story, mid-cycle planning21:59
shamailmid-cycle planning being priority22:00
leonglet's jump to another channel..22:00
shamail#openstack-productwg22:00
barrett1OK22:00
barrett1#endmeeting22:00
*** openstack changes topic to "Discuss L7 feature (and review) timeline re: Mitaka (sbalukoff) (Meeting topic: Octavia)"22:00
openstackMeeting ended Mon Feb  1 22:00:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-02-01-21.00.html22:00
*** egafford has left #openstack-meeting-alt22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-02-01-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-02-01-21.00.log.html22:00
*** nateziemann has quit IRC22:00
*** cbouch has quit IRC22:01
*** MeganR has quit IRC22:01
*** kszukielojc has quit IRC22:01
*** MeganR has joined #openstack-meeting-alt22:02
*** shwetaap has quit IRC22:02
*** pchadwick has left #openstack-meeting-alt22:02
*** sriram has quit IRC22:02
*** ihrachys has quit IRC22:03
*** AndreyPavlov has quit IRC22:05
*** amitgandhinz has quit IRC22:06
*** amitgandhinz has joined #openstack-meeting-alt22:07
*** leong has left #openstack-meeting-alt22:07
*** thomasem-away is now known as thomasem22:09
*** vgridnev has quit IRC22:09
*** thomasem is now known as thomasem-away22:15
*** harshs has quit IRC22:18
*** sc68cal has quit IRC22:18
*** Sukhdev has quit IRC22:18
*** EricGonczer_ has quit IRC22:18
*** Sukhdev has joined #openstack-meeting-alt22:20
*** Sukhdev has quit IRC22:22
*** banix has quit IRC22:24
*** piet has quit IRC22:24
*** harshs has joined #openstack-meeting-alt22:25
*** mhickey_ has quit IRC22:26
*** shwetaap has joined #openstack-meeting-alt22:28
*** Sukhdev has joined #openstack-meeting-alt22:31
*** Sukhdev has quit IRC22:31
*** Sukhdev has joined #openstack-meeting-alt22:31
*** barrett1 has left #openstack-meeting-alt22:32
*** ninag has quit IRC22:33
*** ijw has joined #openstack-meeting-alt22:33
*** ninag has joined #openstack-meeting-alt22:33
*** ninag has quit IRC22:38
*** Sukhdev has quit IRC22:38
*** diazjf1 has quit IRC22:38
*** edtubill has quit IRC22:38
*** edtubill has joined #openstack-meeting-alt22:39
*** edtubill has quit IRC22:39
*** Sukhdev has joined #openstack-meeting-alt22:43
*** amitgandhinz has quit IRC22:43
*** neelashah1 has quit IRC22:44
*** harshs has quit IRC22:44
*** harshs has joined #openstack-meeting-alt22:45
*** esker has quit IRC22:50
*** harshs has quit IRC22:51
*** balajiiyer has quit IRC22:52
*** kzaitsev_mb has quit IRC22:57
*** ikutukov has quit IRC22:57
*** jecarey has quit IRC22:57
*** harshs has joined #openstack-meeting-alt22:58
*** jmckind has quit IRC23:01
*** weshay has quit IRC23:01
*** sgotliv has quit IRC23:03
*** kencjohnston has quit IRC23:07
*** xyang1 has quit IRC23:10
*** zhhuabj has quit IRC23:13
*** piet has joined #openstack-meeting-alt23:14
*** shwetaap has quit IRC23:14
*** armax has quit IRC23:15
*** david-lyle has quit IRC23:15
*** kfarr has quit IRC23:18
*** sigmavirus24 is now known as sigmavirus24_awa23:22
*** spotz is now known as spotz_zzz23:22
*** rockyg has quit IRC23:24
*** Arkady_Kanevsky has quit IRC23:24
*** rocky_g has quit IRC23:25
*** zhhuabj has joined #openstack-meeting-alt23:26
*** armax has joined #openstack-meeting-alt23:29
*** Leom has quit IRC23:33
*** kebray has quit IRC23:34
*** kei_yama has joined #openstack-meeting-alt23:34
*** tpsilva has quit IRC23:36
*** salv-orl_ has joined #openstack-meeting-alt23:37
*** dimtruck is now known as zz_dimtruck23:38
*** dalgaaf has quit IRC23:38
*** kragniz_ is now known as kragniz23:38
*** salv-orlando has quit IRC23:40
*** markvoelker has quit IRC23:41
*** MarkAtwood has joined #openstack-meeting-alt23:42
*** EricGonczer_ has joined #openstack-meeting-alt23:51
*** amotoki has joined #openstack-meeting-alt23:51
*** yamahata has quit IRC23:53
*** vilobhmm11 has quit IRC23:53
*** vilobhmm11 has joined #openstack-meeting-alt23:54
*** vilobhmm11 has quit IRC23:54
*** vilobhmm11 has joined #openstack-meeting-alt23:54
*** Swami has quit IRC23:55
*** tonytan4ever has quit IRC23:55
*** yamahata has joined #openstack-meeting-alt23:56
*** iyamahat has joined #openstack-meeting-alt23:56
*** jrist has quit IRC23:58

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