Tuesday, 2014-04-22

*** mwagner_lap has joined #openstack-meeting00:00
*** dwalleck has quit IRC00:04
*** rakhmerov has quit IRC00:04
*** oomichi has joined #openstack-meeting00:05
*** Alexandra_ has joined #openstack-meeting00:08
*** jjmb has joined #openstack-meeting00:08
*** JRobinson__ has joined #openstack-meeting00:11
*** coreywright_ is now known as coreywright00:11
*** eguz has quit IRC00:11
*** amotoki_ has quit IRC00:12
*** fnaval has joined #openstack-meeting00:13
*** tkay has quit IRC00:13
*** sarob_ has quit IRC00:15
*** sarob has joined #openstack-meeting00:16
*** matsuhashi has joined #openstack-meeting00:19
*** sarob has quit IRC00:21
*** Alexandra_ has quit IRC00:23
*** Alexandra_ has joined #openstack-meeting00:23
*** JRobinson__ has quit IRC00:25
*** SridarK has quit IRC00:25
*** rossk has quit IRC00:25
*** baoli has joined #openstack-meeting00:27
*** dwalleck has joined #openstack-meeting00:27
*** zhikunliu has joined #openstack-meeting00:27
*** Tross1 has quit IRC00:30
*** nati_ueno has quit IRC00:30
*** radsy has joined #openstack-meeting00:31
*** radsy has quit IRC00:31
*** radsy has joined #openstack-meeting00:31
*** esker has quit IRC00:34
*** esker has joined #openstack-meeting00:35
*** vijendar has quit IRC00:36
*** krotscheck has quit IRC00:36
*** dwalleck_ has joined #openstack-meeting00:36
*** JRobinson__ has joined #openstack-meeting00:37
*** zdiN0bot has joined #openstack-meeting00:38
*** krotscheck has joined #openstack-meeting00:39
*** dwalleck has quit IRC00:40
*** nati_ueno has joined #openstack-meeting00:41
*** zdiN0bot1 has joined #openstack-meeting00:42
*** zdiN0bot has quit IRC00:42
*** spzala has quit IRC00:46
*** vjay has quit IRC00:49
*** zns has quit IRC00:53
*** zdiN0bot1 has quit IRC00:53
*** SumitNaiksatam has quit IRC00:53
*** bdpayne has quit IRC00:57
*** nati_uen_ has joined #openstack-meeting00:59
*** rakhmerov has joined #openstack-meeting01:00
*** dwalleck_ has quit IRC01:01
*** Alexandra_ has quit IRC01:02
*** nati_ueno has quit IRC01:03
*** IlyaE has quit IRC01:03
assefola alguem tc01:04
*** rakhmerov has quit IRC01:05
*** baoli has quit IRC01:05
*** coreywright is now known as coreywright_01:06
*** kgriffs is now known as kgriffs|afk01:08
*** manishg has joined #openstack-meeting01:08
*** manishg_ has joined #openstack-meeting01:11
*** Jianyong has joined #openstack-meeting01:11
*** manishg has quit IRC01:12
*** shivharis has quit IRC01:19
*** ramashri has joined #openstack-meeting01:19
*** JRobinson__ has quit IRC01:23
*** SumitNaiksatam has joined #openstack-meeting01:25
*** emaganap has quit IRC01:25
*** emagana has joined #openstack-meeting01:25
*** emagana has quit IRC01:25
*** marun has quit IRC01:26
*** manishg_ is now known as manishg01:26
*** manishg_ has joined #openstack-meeting01:29
*** neelashah has joined #openstack-meeting01:30
*** comay has quit IRC01:30
*** resker has joined #openstack-meeting01:31
*** manishg has quit IRC01:31
*** manishg_ is now known as manishg01:31
*** saschpe has quit IRC01:32
*** radsy has quit IRC01:33
*** esker has quit IRC01:34
*** mattgriffin has joined #openstack-meeting01:35
*** baoli has joined #openstack-meeting01:36
*** nosnos has joined #openstack-meeting01:36
*** Longgeek has joined #openstack-meeting01:37
*** saschpe has joined #openstack-meeting01:37
*** tkay has joined #openstack-meeting01:37
*** Jianyong has quit IRC01:46
*** banix has joined #openstack-meeting01:46
*** ArthurBerezin1 has left #openstack-meeting01:46
*** rwsu has quit IRC01:47
*** baoli has quit IRC01:48
*** natarajk has quit IRC01:50
*** sbalukoff has quit IRC01:55
*** IlyaE has joined #openstack-meeting01:57
*** xianghui has joined #openstack-meeting01:59
*** Mandell has quit IRC01:59
*** banix has quit IRC01:59
*** baojg has joined #openstack-meeting02:00
*** rakhmerov has joined #openstack-meeting02:01
*** rakhmerov has quit IRC02:05
*** gokrokve has quit IRC02:06
*** yingjun has joined #openstack-meeting02:06
*** gokrokve has joined #openstack-meeting02:07
*** fnaval has quit IRC02:08
*** fnaval has joined #openstack-meeting02:09
*** Longgeek has quit IRC02:10
*** gokrokve has quit IRC02:11
*** hemna_ has joined #openstack-meeting02:11
*** fnaval has quit IRC02:13
*** iron1 has quit IRC02:13
*** epico has joined #openstack-meeting02:16
*** novas0x2a|laptop has quit IRC02:20
*** tkay has quit IRC02:21
*** IlyaE has quit IRC02:22
*** gokrokve has joined #openstack-meeting02:22
*** asettle is now known as alex-gym02:24
*** yamamoto_ has joined #openstack-meeting02:27
*** nati_uen_ has quit IRC02:27
*** zhiyan_ is now known as zhiyan02:30
*** Tross has joined #openstack-meeting02:32
*** nati_ueno has joined #openstack-meeting02:33
*** resker has quit IRC02:40
*** Longgeek has joined #openstack-meeting02:41
*** weshay has quit IRC02:43
*** paragan has joined #openstack-meeting02:44
*** paragan has joined #openstack-meeting02:44
*** Longgeek has quit IRC02:45
*** nati_ueno has quit IRC02:45
*** IlyaE has joined #openstack-meeting02:45
*** rkukura has quit IRC02:47
*** coolsvap|afk is now known as coolsvap02:48
*** nati_uen_ has joined #openstack-meeting02:49
*** ramashri has quit IRC02:51
*** eghobo has joined #openstack-meeting02:53
*** nati_uen_ has quit IRC02:55
*** Jianyong has joined #openstack-meeting02:55
*** alex-gym is now known as asettle02:56
*** harlowja is now known as harlowja_away02:58
*** Jianyong has quit IRC02:58
*** yingjun has quit IRC02:59
*** yaguang has joined #openstack-meeting03:01
*** rakhmerov has joined #openstack-meeting03:01
*** rakhmerov has quit IRC03:06
*** jpeeler has quit IRC03:06
*** vjay has joined #openstack-meeting03:11
*** banix has joined #openstack-meeting03:15
*** crandquist has quit IRC03:16
*** crandquist has joined #openstack-meeting03:16
*** harlowja_away is now known as harlowja03:16
*** IlyaE has quit IRC03:17
*** tkay has joined #openstack-meeting03:17
*** tkay has quit IRC03:19
*** sarob has joined #openstack-meeting03:20
*** matsuhashi has quit IRC03:20
*** ramishra has joined #openstack-meeting03:21
*** sankarshan has joined #openstack-meeting03:21
*** ramishra has quit IRC03:23
*** ramishra has joined #openstack-meeting03:24
*** sarob has quit IRC03:25
*** arnaud__ has quit IRC03:28
*** nosnos has quit IRC03:32
*** rakhmerov has joined #openstack-meeting03:34
*** banix has quit IRC03:38
*** Longgeek has joined #openstack-meeting03:42
*** Longgeek has quit IRC03:46
*** mspreitz has joined #openstack-meeting03:46
*** nati_ueno has joined #openstack-meeting03:49
*** Tross has quit IRC03:50
*** ramishra_ has joined #openstack-meeting03:51
*** ramishra has quit IRC03:55
*** ramishra has joined #openstack-meeting03:59
*** TravT has quit IRC04:00
*** chandan_kumar has joined #openstack-meeting04:02
*** ramishra_ has quit IRC04:02
*** nati_ueno has quit IRC04:03
*** pablosan_ has joined #openstack-meeting04:04
*** pablosan has quit IRC04:05
*** slong_ has joined #openstack-meeting04:06
*** slong has quit IRC04:07
*** chandan_kumar has quit IRC04:10
*** bdpayne has joined #openstack-meeting04:12
*** yfried has quit IRC04:13
*** nati_ueno has joined #openstack-meeting04:18
*** IlyaE has joined #openstack-meeting04:21
*** dkehn_ has joined #openstack-meeting04:21
*** dkehnx has quit IRC04:25
*** Tross has joined #openstack-meeting04:28
*** matsuhashi has joined #openstack-meeting04:28
*** nati_ueno has quit IRC04:29
*** akuznetsov has joined #openstack-meeting04:36
*** nosnos has joined #openstack-meeting04:37
*** ildikov has quit IRC04:38
*** Mandell has joined #openstack-meeting04:43
*** deepakcs has joined #openstack-meeting04:44
*** sdake_ has quit IRC04:45
*** nelsnelson has quit IRC04:48
*** baojg has quit IRC04:48
*** baojg has joined #openstack-meeting04:48
*** haomaiw__ has joined #openstack-meeting04:49
*** Longgeek has joined #openstack-meeting04:51
*** haomaiwang has quit IRC04:52
*** morganfainberg is now known as morganfainberg_Z04:55
*** Mandell has quit IRC04:56
*** morganfainberg_Z is now known as morganfainberg04:59
*** sankarshan is now known as sankarshan_away05:01
*** Mandell has joined #openstack-meeting05:01
*** matsuhas_ has joined #openstack-meeting05:02
*** bdpayne has quit IRC05:03
*** matsuhashi has quit IRC05:05
*** neelashah has quit IRC05:06
*** Longgeek has quit IRC05:06
*** yamahata has joined #openstack-meeting05:06
*** Longgeek has joined #openstack-meeting05:07
*** akuznetsov has quit IRC05:08
*** nati_ueno has joined #openstack-meeting05:09
*** baojg_ has joined #openstack-meeting05:10
*** yfried has joined #openstack-meeting05:11
*** yamahata has quit IRC05:12
*** yamahata has joined #openstack-meeting05:12
*** mattgriffin has quit IRC05:12
*** akuznetsov has joined #openstack-meeting05:12
*** baojg has quit IRC05:14
*** vkozhukalov has joined #openstack-meeting05:15
*** cjellick has quit IRC05:17
*** cjellick has joined #openstack-meeting05:17
*** Mandell has quit IRC05:17
*** cjellick has quit IRC05:18
*** SridharG has joined #openstack-meeting05:20
*** comay has joined #openstack-meeting05:21
*** Mandell has joined #openstack-meeting05:21
*** sdake_ has joined #openstack-meeting05:22
*** fawadkhaliq has joined #openstack-meeting05:24
*** akuznetsov has quit IRC05:26
*** ramishra has quit IRC05:26
*** ramishra has joined #openstack-meeting05:27
*** doron_afk has quit IRC05:28
*** akuznetsov has joined #openstack-meeting05:28
*** stevemar has quit IRC05:28
*** Leonr has quit IRC05:28
*** Longgeek has quit IRC05:30
*** ildikov has joined #openstack-meeting05:34
*** akuznetsov has quit IRC05:34
*** akuznetsov has joined #openstack-meeting05:36
*** slong__ has joined #openstack-meeting05:37
*** slong_ has quit IRC05:38
*** topol has quit IRC05:41
*** harlowja is now known as harlowja_away05:41
*** Mandell has quit IRC05:43
*** akuznetsov has quit IRC05:43
*** zns has joined #openstack-meeting05:47
*** zns has quit IRC05:48
*** zns has joined #openstack-meeting05:48
*** akuznetsov has joined #openstack-meeting05:49
*** akuznetsov has quit IRC05:49
*** nati_ueno has quit IRC05:49
*** akuznetsov has joined #openstack-meeting05:51
*** nshaikh has joined #openstack-meeting05:55
*** haomaiw__ has quit IRC05:56
*** haomaiwa_ has joined #openstack-meeting05:56
*** gyee has quit IRC05:56
*** haomaiw__ has joined #openstack-meeting05:57
*** slong__ has quit IRC05:58
*** IlyaE has quit IRC05:58
*** jtomasek has joined #openstack-meeting05:58
*** afazekas_ has joined #openstack-meeting05:59
*** Longgeek has joined #openstack-meeting06:00
*** haomaiwa_ has quit IRC06:01
*** akuznetsov has quit IRC06:01
*** chandan_kumar has joined #openstack-meeting06:02
*** matsuhas_ has quit IRC06:02
*** mkoderer has joined #openstack-meeting06:02
*** Longgeek has quit IRC06:05
*** jdurgin has quit IRC06:05
*** jcoufal has joined #openstack-meeting06:07
*** Mikhail_D_ltp has joined #openstack-meeting06:08
*** matsuhashi has joined #openstack-meeting06:10
*** nati_ueno has joined #openstack-meeting06:12
*** _nadya_ has joined #openstack-meeting06:13
*** zhikunliu has quit IRC06:14
*** vkozhukalov has quit IRC06:17
*** ttrifonov_zZzz is now known as ttrifonov06:17
*** gokrokve has quit IRC06:18
*** cjellick has joined #openstack-meeting06:18
*** yamahata has quit IRC06:19
*** Macaveli has joined #openstack-meeting06:21
*** jdurgin has joined #openstack-meeting06:21
*** doron_afk has joined #openstack-meeting06:24
*** cjellick has quit IRC06:26
*** mspreitz has quit IRC06:27
*** sankarshan_away is now known as sankarshan06:30
*** Longgeek has joined #openstack-meeting06:36
*** max_lobur has joined #openstack-meeting06:40
*** ttrifonov is now known as ttrifonov_zZzz06:43
*** _nadya_ has quit IRC06:45
*** arosen1 has quit IRC06:46
*** Fdot has joined #openstack-meeting06:46
*** Guest67947 has quit IRC06:48
*** amandeep has joined #openstack-meeting06:48
*** amandeep is now known as Guest6785406:48
*** gokrokve has joined #openstack-meeting06:48
*** chandan_kumar has quit IRC06:49
*** Mikhail_D_ltp has quit IRC06:50
*** gokrokve_ has joined #openstack-meeting06:50
*** haomaiw__ has quit IRC06:50
*** haomaiwang has joined #openstack-meeting06:51
*** yfujioka has joined #openstack-meeting06:51
*** gokrokve has quit IRC06:53
*** flaper87|afk is now known as flaper8706:53
*** gokrokve has joined #openstack-meeting06:56
*** hemna_ has quit IRC06:56
*** ArthurBerezin has joined #openstack-meeting06:57
*** gokrokve_ has quit IRC06:57
*** gokrokve has quit IRC07:00
*** Qiming has joined #openstack-meeting07:01
*** jlibosva has joined #openstack-meeting07:04
*** chandan_kumar has joined #openstack-meeting07:07
*** arosen1 has joined #openstack-meeting07:07
*** jgallard has joined #openstack-meeting07:11
*** doron_afk is now known as doron07:11
*** sbalukoff has joined #openstack-meeting07:12
*** eghobo has quit IRC07:15
*** rakhmerov has quit IRC07:17
*** zhikunliu has joined #openstack-meeting07:17
*** doron is now known as doron_afk07:18
*** doron_afk is now known as doron07:20
*** rakhmerov has joined #openstack-meeting07:20
*** nelsnelson has joined #openstack-meeting07:22
*** yamamoto_ has quit IRC07:23
*** ArthurBerezin has left #openstack-meeting07:28
*** Sajeesh has joined #openstack-meeting07:29
*** rakhmerov has quit IRC07:29
*** rakhmero_ has joined #openstack-meeting07:29
*** schwicke has joined #openstack-meeting07:30
*** schwicke has quit IRC07:30
*** shardy_afk is now known as shardy07:30
*** rakhmero_ has quit IRC07:31
*** rakhmerov has joined #openstack-meeting07:32
*** egallen has joined #openstack-meeting07:32
*** ttrifonov_zZzz is now known as ttrifonov07:33
*** jcoufal has quit IRC07:33
*** matrohon has joined #openstack-meeting07:34
*** I159 has joined #openstack-meeting07:40
*** I159_ has joined #openstack-meeting07:40
*** jcoufal has joined #openstack-meeting07:40
*** ygbo has joined #openstack-meeting07:41
*** mrunge has joined #openstack-meeting07:42
*** ndipanov has joined #openstack-meeting07:42
*** vkozhukalov has joined #openstack-meeting07:46
*** haomai___ has joined #openstack-meeting07:50
*** nacim has joined #openstack-meeting07:50
*** Qiming has quit IRC07:50
*** ttrifonov is now known as ttrifonov_zZzz07:53
*** haomaiwang has quit IRC07:53
*** ttrifonov_zZzz is now known as ttrifonov07:54
*** nati_ueno has quit IRC07:54
*** gcb has joined #openstack-meeting07:54
*** nwidell has joined #openstack-meeting07:56
*** ndipanov has quit IRC07:56
*** gokrokve has joined #openstack-meeting07:57
*** andreaf has joined #openstack-meeting07:59
*** gokrokve has quit IRC08:01
*** ildikov_ has joined #openstack-meeting08:03
*** derekh has joined #openstack-meeting08:03
*** jtomasek has quit IRC08:04
*** jtomasek has joined #openstack-meeting08:04
*** arosen1 has quit IRC08:05
*** ildikov has quit IRC08:05
*** idegtiarov has joined #openstack-meeting08:07
*** xianghui has quit IRC08:08
*** yaguang has quit IRC08:08
*** ndipanov has joined #openstack-meeting08:09
*** xianghui has joined #openstack-meeting08:10
*** andreaf has quit IRC08:12
*** rakhmero_ has joined #openstack-meeting08:13
*** rakhmerov has quit IRC08:13
*** andreaf has joined #openstack-meeting08:13
*** mrda is now known as mrda_away08:17
*** safchain has joined #openstack-meeting08:18
*** yfujioka has quit IRC08:25
*** rakhmerov has joined #openstack-meeting08:26
*** rakhmero_ has quit IRC08:29
*** DuncanT-1 has quit IRC08:34
*** haomai___ has quit IRC08:34
*** bauzas has joined #openstack-meeting08:34
*** haomaiwang has joined #openstack-meeting08:35
*** DuncanT- has joined #openstack-meeting08:35
*** zaneb has quit IRC08:36
*** doron is now known as doron_afk08:36
*** zaneb has joined #openstack-meeting08:36
*** Mandell has joined #openstack-meeting08:44
*** haomaiw__ has joined #openstack-meeting08:45
*** q3k has quit IRC08:45
*** haomaiwang has quit IRC08:45
*** Mandell has quit IRC08:49
*** ttrifonov is now known as ttrifonov_zZzz08:50
*** che-arne has joined #openstack-meeting08:52
*** yaguang has joined #openstack-meeting08:57
*** gokrokve has joined #openstack-meeting08:57
*** q3k has joined #openstack-meeting08:57
*** sbalukoff has quit IRC08:59
*** sbalukoff has joined #openstack-meeting08:59
*** ttrifonov_zZzz is now known as ttrifonov09:00
*** ramishra has quit IRC09:01
*** gokrokve has quit IRC09:01
*** xianghui has quit IRC09:02
*** xianghui has joined #openstack-meeting09:04
*** jogo has quit IRC09:07
*** asadoughi has quit IRC09:07
*** jogo has joined #openstack-meeting09:07
*** asadoughi has joined #openstack-meeting09:07
*** belmoreira has joined #openstack-meeting09:08
*** ramishra has joined #openstack-meeting09:10
*** akuznetsov has joined #openstack-meeting09:14
*** chandan_kumar has quit IRC09:15
*** bgorski has joined #openstack-meeting09:26
*** chandan_kumar has joined #openstack-meeting09:29
*** sankarshan is now known as sankarshan_away09:32
*** dshulyak has joined #openstack-meeting09:42
*** MaxV has joined #openstack-meeting09:42
*** deepakcs has quit IRC09:45
*** _nadya_ has joined #openstack-meeting09:46
*** tinoue has quit IRC09:49
*** assef has quit IRC09:49
*** miarmak_ has quit IRC09:49
*** _nadya_ has quit IRC09:50
*** miarmak has joined #openstack-meeting09:54
*** jhenner has joined #openstack-meeting09:54
*** chandan_kumar is now known as chandankumar09:55
*** chandankumar is now known as chandan_kumar09:56
*** gokrokve has joined #openstack-meeting09:58
*** zns has quit IRC09:58
*** zns has joined #openstack-meeting10:01
*** gokrokve has quit IRC10:02
*** MaxV has quit IRC10:05
*** deepakcs has joined #openstack-meeting10:06
*** dkehn__ has joined #openstack-meeting10:07
*** oomichi_ has joined #openstack-meeting10:08
*** garyduan has joined #openstack-meeting10:08
*** nprivalova has left #openstack-meeting10:08
*** sbalukoff1 has joined #openstack-meeting10:08
*** jhenner has quit IRC10:08
*** gduan has quit IRC10:09
*** jhenner has joined #openstack-meeting10:09
*** oomichi has quit IRC10:09
*** sbalukoff has quit IRC10:10
*** dkehn_ has quit IRC10:10
*** reed has joined #openstack-meeting10:11
*** deepakcs has quit IRC10:12
*** deepakcs has joined #openstack-meeting10:12
*** asselin has quit IRC10:16
*** ivar-lazzaro has quit IRC10:23
*** egallen has quit IRC10:25
*** jgallard has quit IRC10:28
*** zns has quit IRC10:29
*** paragan has quit IRC10:30
*** jhenner has quit IRC10:31
*** coolsvap is now known as coolsvap|afk10:40
*** jjmb has quit IRC10:49
*** MaxV has joined #openstack-meeting10:53
*** Michalik- has quit IRC10:57
*** epico has quit IRC10:58
*** gokrokve has joined #openstack-meeting10:59
*** derekh has quit IRC11:01
*** rakhmerov has quit IRC11:01
*** rakhmerov has joined #openstack-meeting11:02
*** alexpilotti has joined #openstack-meeting11:02
*** gokrokve has quit IRC11:04
*** Michalik- has joined #openstack-meeting11:07
*** alexpilotti has quit IRC11:07
*** baojg_ has quit IRC11:10
*** baojg has joined #openstack-meeting11:11
*** che-arne has quit IRC11:12
*** rakhmerov has quit IRC11:15
*** baojg has quit IRC11:16
*** ArthurBerezin has joined #openstack-meeting11:18
*** Longgeek has quit IRC11:26
*** Fdot has quit IRC11:31
*** miqui has quit IRC11:33
*** Longgeek has joined #openstack-meeting11:35
*** rfolco has joined #openstack-meeting11:36
*** egallen has joined #openstack-meeting11:38
*** zhikunliu has quit IRC11:39
*** yfried has quit IRC11:40
*** enikanorov_ has quit IRC11:43
*** ArthurBerezin has left #openstack-meeting11:48
*** jmh_ has joined #openstack-meeting11:49
*** Guest67854 has quit IRC11:50
*** gokrokve has joined #openstack-meeting11:59
*** che-arne has joined #openstack-meeting12:01
*** pdmars has joined #openstack-meeting12:03
*** pdmars has quit IRC12:03
*** xianghui has quit IRC12:04
*** jcoufal has quit IRC12:04
*** pdmars has joined #openstack-meeting12:04
*** jcoufal has joined #openstack-meeting12:04
*** gokrokve has quit IRC12:04
*** afazekas_ has quit IRC12:04
*** yaguang has quit IRC12:06
*** jdob has joined #openstack-meeting12:06
*** jgallard has joined #openstack-meeting12:07
*** jcoufal has quit IRC12:09
*** ArthurBerezin has joined #openstack-meeting12:09
*** jdob has quit IRC12:09
*** jcoufal has joined #openstack-meeting12:09
*** jdob has joined #openstack-meeting12:09
*** rakhmerov has joined #openstack-meeting12:12
*** yamamoto has joined #openstack-meeting12:12
*** erecio has joined #openstack-meeting12:13
*** baoli has joined #openstack-meeting12:14
*** jcoufal has quit IRC12:14
*** jcoufal has joined #openstack-meeting12:14
*** jcoufal has quit IRC12:15
*** adalbas has joined #openstack-meeting12:15
*** jcoufal has joined #openstack-meeting12:15
*** adalbas has quit IRC12:16
*** yfried has joined #openstack-meeting12:18
*** jcoufal has quit IRC12:18
*** jcoufal has joined #openstack-meeting12:19
*** afazekas_ has joined #openstack-meeting12:19
*** ArthurBerezin has quit IRC12:19
*** ArthurBerezin has joined #openstack-meeting12:19
*** jcoufal has quit IRC12:20
*** jcoufal has joined #openstack-meeting12:20
*** ArthurBerezin has quit IRC12:24
*** aysyd has joined #openstack-meeting12:24
*** rakhmerov has quit IRC12:24
*** adalbas has joined #openstack-meeting12:25
*** sankarshan_away is now known as sankarshan12:25
*** nwidell has quit IRC12:26
*** yamamoto has left #openstack-meeting12:33
*** weshay has joined #openstack-meeting12:35
*** vjay has quit IRC12:35
*** neelashah has joined #openstack-meeting12:36
*** adalbas has quit IRC12:37
*** rbowen has quit IRC12:38
*** ArthurBerezin has joined #openstack-meeting12:38
*** ArthurBerezin has left #openstack-meeting12:38
*** enikanorov has joined #openstack-meeting12:39
*** vjay has joined #openstack-meeting12:39
*** derekh has joined #openstack-meeting12:41
*** xuhanp has joined #openstack-meeting12:41
*** esperanza has joined #openstack-meeting12:42
*** prad has joined #openstack-meeting12:42
*** matsuhashi has quit IRC12:43
*** jjmb has joined #openstack-meeting12:43
*** matsuhashi has joined #openstack-meeting12:43
*** nshaikh has quit IRC12:44
*** jjmb1 has joined #openstack-meeting12:44
*** jhenner has joined #openstack-meeting12:45
*** jpeeler has joined #openstack-meeting12:46
*** jpeeler has quit IRC12:46
*** jpeeler has joined #openstack-meeting12:46
*** egallen has quit IRC12:47
*** jjmb has quit IRC12:47
*** matsuhashi has quit IRC12:48
*** blamar has quit IRC12:48
*** nosnos has quit IRC12:48
*** dburmistrov_ has joined #openstack-meeting12:49
*** blamar has joined #openstack-meeting12:49
*** nosnos has joined #openstack-meeting12:51
*** deepakcs has quit IRC12:51
*** nosnos has quit IRC12:52
*** bauzas has quit IRC12:52
*** oomichi_ has quit IRC12:52
*** boh_ricky has joined #openstack-meeting12:52
*** beagles has joined #openstack-meeting12:52
*** bauzas has joined #openstack-meeting12:53
*** egallen has joined #openstack-meeting12:54
*** bknudson1 has quit IRC12:55
*** ameade has joined #openstack-meeting12:56
*** miarmak has quit IRC12:56
*** miarmak has joined #openstack-meeting12:56
*** dkehn__ is now known as dkehnx12:57
*** jecarey has quit IRC12:57
*** ramishra has quit IRC12:58
*** phil_h has quit IRC12:58
*** dprince has joined #openstack-meeting12:59
*** overlayer has joined #openstack-meeting12:59
*** imsurit has joined #openstack-meeting13:00
*** rakhmerov has joined #openstack-meeting13:00
*** gokrokve has joined #openstack-meeting13:00
*** afazekas_ has quit IRC13:01
*** ameade has quit IRC13:01
*** terriyu has joined #openstack-meeting13:02
*** jjmb1 has quit IRC13:03
*** gokrokve has quit IRC13:04
*** jhenner1 has joined #openstack-meeting13:05
*** jhenner has quit IRC13:06
*** jjmb has joined #openstack-meeting13:07
*** banix has joined #openstack-meeting13:08
*** oomichi has joined #openstack-meeting13:09
*** bauzas has quit IRC13:10
*** absubram has joined #openstack-meeting13:10
*** gcb has quit IRC13:11
*** jjmb has quit IRC13:12
*** doron_afk is now known as doron13:13
*** max_lobur has quit IRC13:14
*** max_lobur has joined #openstack-meeting13:15
*** paragan has joined #openstack-meeting13:15
*** paragan has quit IRC13:15
*** paragan has joined #openstack-meeting13:15
*** jjmb has joined #openstack-meeting13:15
*** pablosan_ is now known as pablosan13:15
*** oomichi has quit IRC13:15
*** vijendar has joined #openstack-meeting13:17
*** jjmb1 has joined #openstack-meeting13:17
*** jjmb has quit IRC13:19
*** bknudson has joined #openstack-meeting13:21
*** jjmb1 has quit IRC13:22
*** jjmb has joined #openstack-meeting13:25
*** prad has quit IRC13:27
*** eharney has joined #openstack-meeting13:28
*** Leonr has joined #openstack-meeting13:28
*** ramishra has joined #openstack-meeting13:30
*** thangp has joined #openstack-meeting13:30
*** AndChat|27729 has joined #openstack-meeting13:31
*** jgrimm has joined #openstack-meeting13:32
*** ygbo has quit IRC13:32
*** MaxV has quit IRC13:33
*** jay-lau-513 has joined #openstack-meeting13:33
*** boh_ricky has quit IRC13:33
*** MaxV has joined #openstack-meeting13:38
*** MaxV has quit IRC13:38
*** AndChat|27729 has quit IRC13:39
*** nacim_ has joined #openstack-meeting13:40
*** nacim has quit IRC13:40
*** yamamoto has joined #openstack-meeting13:40
*** yamamoto has quit IRC13:41
*** ilyashakhat has joined #openstack-meeting13:41
*** julim has joined #openstack-meeting13:42
*** paragan has quit IRC13:43
*** afazekas_ has joined #openstack-meeting13:43
*** doron is now known as doron_afk13:43
*** adalbas has joined #openstack-meeting13:43
*** doron_afk is now known as doron13:43
*** esperanza has quit IRC13:44
*** terriyu has quit IRC13:45
*** ygbo has joined #openstack-meeting13:46
*** doron is now known as doron_afk13:50
*** doron_afk is now known as doron13:50
*** ndipanov has quit IRC13:53
*** ndipanov has joined #openstack-meeting13:55
*** mrunge has quit IRC13:55
sc68calHello all, ready for some neutron ipv6?13:55
xuhanphello. ready :-)13:57
*** devvesa has joined #openstack-meeting13:58
*** esperanza has joined #openstack-meeting13:59
sc68cal#startmeeting neutron_ipv613:59
openstackMeeting started Tue Apr 22 13:59:24 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"13:59
openstackThe meeting name has been set to 'neutron_ipv6'13:59
*** rakhmerov has quit IRC13:59
sc68cal#link https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_April_21st Agenda for today13:59
*** kun_huang has joined #openstack-meeting13:59
sc68cal#topic blueprints13:59
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"13:59
baolihi14:00
sc68cal#announcement Neutron-Specs is up and active, all blueprints for Juno release must follow the new git based workflow14:00
*** BrianB__ has joined #openstack-meeting14:00
absubramhi14:00
sc68cal#link https://wiki.openstack.org/wiki/Blueprints#Neutron Information about the new blueprint process14:01
*** gokrokve has joined #openstack-meeting14:01
*** ameade has joined #openstack-meeting14:01
baoliI need to start working on the specs soon.14:01
*** stevemar has joined #openstack-meeting14:02
sc68calyes - I saw a couple blueprints you added to the agenda exist in launchpad14:02
*** sushils_ has joined #openstack-meeting14:02
*** pcm_ has joined #openstack-meeting14:03
baoliI haven't had time to put more details in them.14:03
*** gcb has joined #openstack-meeting14:03
*** prad has joined #openstack-meeting14:03
*** hrzbrg has joined #openstack-meeting14:04
sc68calOK. We should also take the blueprints for the dnsmasq work and put them in14:05
*** doron is now known as doron_afk14:05
sc68calEither as one big blueprint or possibly as multiple blueprints - I'm thinking maybe multiple blueprints (since they already are multiple BPs)14:05
*** ameade has quit IRC14:06
*** gokrokve has quit IRC14:06
sc68caland hopefully that will help break up the big patch that shixiong has14:06
sc68calinto more managable chunks14:06
xuhanpsc68cal, I will work on the security group related BP soon.14:06
*** Macaveli has quit IRC14:07
sc68calrefresh my memory about that one? I thought you got everything merged? or do you mean the work for triggering security group refreshing?14:07
xuhanpthere are some egress rule, spoofing stuff as well14:07
sc68calOK - cool!14:08
xuhanpand the discussion you have with baoli about the LLA and router interface14:08
xuhanpI think we still need to figure out them14:08
*** hartsocks has quit IRC14:08
*** rwsu has joined #openstack-meeting14:09
*** mattgriffin has joined #openstack-meeting14:10
sc68calOK - do we have anything else to discuss, related to BPs?14:10
sc68cal#topic code reviews14:11
*** openstack changes topic to "code reviews (Meeting topic: neutron_ipv6)"14:11
sc68calbaoli: think you had some stuff on the agenda14:11
baolisc68cal, regarding the radvd BP, I put some of my thoughts in the whiteboard14:11
*** dkranz has joined #openstack-meeting14:12
*** ameade has joined #openstack-meeting14:12
*** markmcclain has joined #openstack-meeting14:12
sc68calok - the problem with the whiteboard is it's sometimes hard to follow - we may have to forklift your concerns into the new bp14:12
baoliwhich new bp?14:13
sc68calthe one we'll have to create for the radvd stuff14:13
*** coreywright_ is now known as coreywright14:14
*** ayoung has quit IRC14:14
sc68calotherwise looks like you have the SNAT rules for ipv4 only in hand, just a couple nits to address.14:15
baoliSo you want to create a new BP for that, not using the existing one?14:15
*** zns has joined #openstack-meeting14:15
sc68calCan't use any existing blueprints in launchpad - all work for Juno must have a bp in neutron-specs14:15
baolisc68cal, I thought that we have to have a bp in launchpad anyway?14:16
*** markmcclain1 has joined #openstack-meeting14:16
*** hartbox has joined #openstack-meeting14:16
*** markmcclain has quit IRC14:16
*** hartbox has joined #openstack-meeting14:16
*** hartbox has left #openstack-meeting14:17
*** thedodd has joined #openstack-meeting14:17
*** chandan_kumar has quit IRC14:17
sc68calbaoli: you are correct - just checked the wiki, yes you must have it in launchpad, then something in neutron-specs. Sorry for the mistake14:17
*** hartbox has joined #openstack-meeting14:17
*** spzala has joined #openstack-meeting14:17
*** bauzas has joined #openstack-meeting14:17
*** changbl has quit IRC14:18
baolisc68cal, no problem. So in the specs, we'll refer to the bp14:18
sc68calYeah, although I think the BPs in launchpad will be pretty light on detail, and the specs will be heavy on detail14:18
baolisc68cal, I agree14:19
*** ttrifonov is now known as ttrifonov_zZzz14:20
sc68calbaoli: I moved some of your agenda items from bugs to code review, since they're links to gerrit. Does anyone want to discuss them?14:20
baolisc68cal, thanks14:20
sc68calI think the only thing I have to say about the devstack one is possibly break it into pieces, which I put in my review comments. Otherwise looks good for both the devstack and SNAT patch14:21
baolisc68cal, I'll give it a try for the next submission14:21
sc68calany other code reviews? otherwise we'll go to bugs, then to open discussion14:22
*** jjmb has quit IRC14:23
jay-lau-513dansmith ping14:23
sc68cal#topic bugs14:23
*** openstack changes topic to "bugs (Meeting topic: neutron_ipv6)"14:23
sc68calNothing was on the agenda for this - so we can continue right to open discussion if nobody has anything14:24
*** morganfainberg is now known as morganfainberg_Z14:24
*** _nadya_ has joined #openstack-meeting14:25
sc68cal#topic open discussion14:25
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"14:25
sc68calSo I put together an etherpad for the design summit session - to put together at least a couple topics to discuss - feel free to edit - https://etherpad.openstack.org/p/neutron-ipv6-atlanta-summit14:26
sc68calCurrently they are oversubscribed on summit sessions to available slots, by like 2.5:114:26
*** mtanino has joined #openstack-meeting14:26
fifieldtjust want to say thanks to you all for the huge effort during icehouse with ipv6 - was awesome to see14:27
sc68cal:)14:27
baolisc68cal, thanks for opening the etherpad. I'll add some stuff soon14:27
*** overlayer has quit IRC14:27
*** fnaval has joined #openstack-meeting14:28
sc68calPretty light day today, so if there isn't anything else I can give everyone back half an hour14:29
*** mwagner_lap has quit IRC14:29
*** jcoufal has quit IRC14:29
sc68calfifieldt: thanks for the praise - I agree - everyone did a fantastic job this cycle, especially since we have no cores on the subteam and it was all community driven14:30
xuhanpagreed. Great team to work with! :-)14:30
*** david-lyle has joined #openstack-meeting14:31
sc68calAlrighty then, if there are no objections, we'll meet next week!14:31
sc68cal#endmeeting14:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:32
openstackMeeting ended Tue Apr 22 14:32:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-04-22-13.59.html14:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-04-22-13.59.txt14:32
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-04-22-13.59.log.html14:32
*** nealph has joined #openstack-meeting14:33
*** zhangleiqiang has joined #openstack-meeting14:33
*** hrzbrg has quit IRC14:35
*** gokrokve has joined #openstack-meeting14:40
*** marun has joined #openstack-meeting14:41
*** scotty95747 has joined #openstack-meeting14:41
*** vjay has quit IRC14:42
*** sushils_ has quit IRC14:44
*** pcm_ has left #openstack-meeting14:44
*** absubram has quit IRC14:44
*** kevinconway has joined #openstack-meeting14:45
*** kgriffs|afk is now known as kgriffs14:45
*** Longgeek has quit IRC14:46
*** jergerber has joined #openstack-meeting14:49
*** xuhanp has quit IRC14:49
*** doron_afk is now known as doron14:49
*** ameade has quit IRC14:49
*** jmontemayor has quit IRC14:49
*** PaulMurray has joined #openstack-meeting14:50
*** dburmistrov_ has quit IRC14:53
*** esperanza has quit IRC14:53
*** loquacities has quit IRC14:54
*** ameade has joined #openstack-meeting14:55
*** vkmc has joined #openstack-meeting14:55
*** vkmc has quit IRC14:55
*** vkmc has joined #openstack-meeting14:55
*** esperanza has joined #openstack-meeting14:57
*** jecarey has joined #openstack-meeting14:57
*** che-arne has quit IRC14:57
*** loquacities has joined #openstack-meeting14:57
*** tianst has joined #openstack-meeting14:58
*** devvesa has left #openstack-meeting14:58
*** vjay has joined #openstack-meeting14:58
bauzas#startmeeting gantt15:00
openstackMeeting started Tue Apr 22 15:00:17 2014 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
bauzashi all15:00
*** mspreitz has joined #openstack-meeting15:00
*** YorikSar has joined #openstack-meeting15:00
PaulMurrayhi15:00
tiansthi15:00
jay-lau-513hi15:00
mspreitzo/15:00
bauzasnice to see people there :)15:01
bauzaswaiting one more min and then we start15:01
PaulMurrayfinally worked out the time zone15:01
YorikSarbauzas: Hi :)15:01
bauzasYorikSar: hi ! j15:01
*** IlyaE has joined #openstack-meeting15:02
*** vjay2 has joined #openstack-meeting15:02
*** devlaps has joined #openstack-meeting15:02
bauzas#topic Open action items15:02
*** openstack changes topic to " Open action items (Meeting topic: gantt)"15:02
*** marun has quit IRC15:02
*** derekh has quit IRC15:02
bauzas#link http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-15-15.00.html15:02
bauzasquite simple, there were 3 actions from one single person last week :)15:03
bauzasluckily, I know him15:03
*** hrzbrg has joined #openstack-meeting15:03
bauzasso, all, you can look at https://wiki.openstack.org/wiki/Gantt15:04
*** che-arne has joined #openstack-meeting15:04
*** alexpilotti has joined #openstack-meeting15:04
bauzas#link https://wiki.openstack.org/wiki/Gantt#Developer_Summit_Sessions15:04
bauzashere is the etherpad link for proposals15:04
bauzasI went thru all the open subjects15:04
bauzasmaybe I missed some15:04
bauzasso feel free to add/amend the etherpad if so15:05
*** vjay has quit IRC15:05
*** vkozhukalov has left #openstack-meeting15:05
bauzasthe best would be that mikal and johnthetubaguy would take note of this page15:06
jay-lau-513Not sure if http://summit.openstack.org/cfp/details/262 can be put to gantt?15:06
bauzasjay-lau-513: good question15:06
jay-lau-513 http://summit.openstack.org/cfp/details/262 is for dynamic scheduling15:06
*** baoli has quit IRC15:06
*** vjay2 has quit IRC15:06
bauzasjay-lau-513: I think that some gantt people would love joining the discussion15:06
bauzasjay-lau-513: even if it's not purely related to gantt15:07
jay-lau-513Great, the dynamic scheduler can work for nova, cinder even neutron etc15:07
bauzasjay-lau-513: IMHO, this service should be linked someway to gantt15:07
*** manishg has quit IRC15:07
*** reed has quit IRC15:07
mspreitz262 is related to 40015:07
jay-lau-513but we can first start from nova for this15:07
mspreitzI see Gantt as preparing for both15:07
bauzasmspreitz: +115:08
bauzasthe problem is see here is the chicken-and-egg one15:08
bauzasas gantt is currently not yet delivered, it can't be leveraged for this purpose15:08
*** vjay has joined #openstack-meeting15:08
bauzasbut possibly it should help15:09
mspreitzI do not see a circle of dependency15:09
mspreitz262 and 400 depend on Gantt, not the other way around15:09
*** nacim_ has quit IRC15:10
bauzaswell, let's discuss about this topic later in the meeting15:10
jay-lau-513mspreitz yes,  262 is for dynamic schdulig and seems 400 is still for  holistic static placement15:10
bauzasI also had an action for linking Gantt wiki with Nova one15:11
bauzasthat's done :15:11
bauzas#link https://wiki.openstack.org/wiki/Nova#Active_Sub-teams:15:11
*** hrzbrg has left #openstack-meeting15:12
bauzasthe last action I had, about creating a 2nd blueprint for the sched forklif15:12
*** ygbo has quit IRC15:12
*** jcoufal has joined #openstack-meeting15:12
bauzas#link https://blueprints.launchpad.net/nova/+spec/isolate-scheduler-db15:12
bauzasthe nova-specs patch has to be sent15:12
bauzaslet's move quickly to the next topic15:13
bauzasso, we'll have time for discussions :)15:13
*** hemna_ has joined #openstack-meeting15:13
bauzas#topic Status on forklift efforts15:13
*** openstack changes topic to "Status on forklift efforts (Meeting topic: gantt)"15:13
*** hemna_ has quit IRC15:14
bauzas#link https://review.openstack.org/#/c/82133/15:14
bauzasif people have time for reviewing it, that would be great15:14
*** afazekas_ has quit IRC15:15
bauzasI made a dependency on https://review.openstack.org/#/c/86988/415:15
bauzasany comments yet ?15:15
bauzasI take it for a no :)15:16
*** markmcclain1 has quit IRC15:16
bauzasas said, I also began working on another blueprint15:16
bauzashttps://blueprints.launchpad.net/nova/+spec/isolate-scheduler-db15:16
bauzasthe idea is to have the scheduler only accessing compute_nodes db table15:17
YorikSarbauzas: I guess that should be related to no-db-scheduler15:17
*** doron is now known as doron_afk15:17
bauzasYorikSar: that's a separate blueprint15:17
bauzasIMHO15:17
*** hemna_ has joined #openstack-meeting15:18
bauzasYorikSar: at the moment, scheduler is not only accessing compute_nodes, but also aggregates, services etc.15:18
YorikSarbauzas: Sure. I see.15:18
bauzasYorikSar: so there is need to modify the calls15:18
bauzasYorikSar: for baby-stepping, I was planning to only refactor the changes and isolate all the calls into the next scheduler client lib15:19
bauzasYorikSar: but that needs to be debated15:19
bauzasboth in terms what and how :)15:19
*** cjellick has joined #openstack-meeting15:20
bauzasYorikSar: correct me if I'm wrong, but no-db sched is planning to rewrite accesses to compute_nodes table ?15:20
bauzasYorikSar: only15:20
YorikSarbauzas: Yes. It isolates only nodes/services/hoststates.15:21
bauzasYorikSar: I saw your patches15:21
*** adalbas has quit IRC15:21
bauzasYorikSar: I would love discussing it in the next second topic15:21
bauzasYorikSar: because we need to see when you plan to deliver it15:22
YorikSarbauzas: Looking forward to it :)15:22
*** dougw has joined #openstack-meeting15:22
bauzasok, any other comments about the forklift ?15:23
bauzasfyi, as the sched-lib blueprint is close to be accepted, I'll publish a first patch for implementing it, next week15:23
bauzasok, next topic15:24
bauzas#topic Juno summit design sessions15:24
*** openstack changes topic to "Juno summit design sessions (Meeting topic: gantt)"15:24
bauzasagain, the etherpad15:24
*** ndipanov has quit IRC15:24
bauzas#link https://etherpad.openstack.org/p/Gantt-summit-sessions15:24
*** ygbo has joined #openstack-meeting15:25
bauzasso, jay-lau-513, do you prefer I remove mention to 262 ?15:25
*** jmontemayor has joined #openstack-meeting15:25
*** hemna_ has quit IRC15:25
*** doron_afk is now known as doron15:25
jay-lau-513bauzas, you mean remove 262 from gantt session?15:25
bauzasjay-lau-513: from the etherpad, at least :)15:26
bauzaswe still have to discuss with mikal to see how many sessions we will have15:26
bauzasand if there is need to group some proposals15:26
jay-lau-513bauzas, ok, but does gantt will handle dynamic schduling in the future?15:27
*** Hao has joined #openstack-meeting15:27
bauzasmaybe russellb is knowing how many sessions we will have for scheduler ?15:27
bauzasjay-lau-513: maybe that could be discussed during http://summit.openstack.org/cfp/details/14015:27
bauzasjay-lau-513: I mean, Gantt scope should be considered therer15:28
bauzasthere15:28
jay-lau-513bauzas: OK, no problem15:28
*** ipbabble has quit IRC15:28
bauzasjay-lau-513: so, do we keep track of your proposal as gantt related subject ?15:28
jay-lau-513I think that we can merge it to 14015:29
jay-lau-513bauzas: make sense?15:29
*** egallen has quit IRC15:29
bauzasjay-lau-513: when do you plan to implement 262?15:29
mspreitzMy estimation is that scheduling will get few slots, 142, 2562, 400 will get merged into 14015:30
jay-lau-513bauzas: You mean implement code or just spec :-)15:30
*** hartsocks has joined #openstack-meeting15:30
*** hartsocks is now known as Guest6739515:30
bauzasjay-lau-513: I mean implementation15:30
mspreitzs/2562/262/15:30
jay-lau-513mspreitz: Agree15:30
*** cjellick has quit IRC15:30
jay-lau-513bauzas: In Juno if approved, but not sure in which sprint.15:31
bauzasjay-lau-513: that sounds a big baby here :)15:31
jay-lau-513bauzas: I also discussed with someone, many of them prefer a new project for this :)15:31
*** cjellick has joined #openstack-meeting15:31
bauzasjay-lau-513: who's someone ? :D15:31
jay-lau-513bauzas: let me check my email15:31
bauzasjay-lau-513: ok, I see15:31
*** doddstack has joined #openstack-meeting15:31
bauzasjay-lau-513: no worries15:32
bauzasjay-lau-513: I remember the discussion in the ML15:32
bauzasjay-lau-513: but as mspreitz said, it could possibly need Gantt15:32
bauzasfor implementation15:32
*** egallen has joined #openstack-meeting15:33
bauzasjay-lau-513: ok, let's amend the etherpad for merging 140 and 262, and let's discuss it in the etherpad15:33
jay-lau-513bauzas: Exactly, gantt is th ebase15:33
jay-lau-513the base15:33
jay-lau-513bauzas: OJK15:33
jay-lau-513ok15:33
jay-lau-513bauzas: http://markmail.org/message/5zotly4qktaf34ei15:34
*** adalbas has joined #openstack-meeting15:34
bauzas#action bauzas to merge http://summit.openstack.org/cfp/details/262 into http://summit.openstack.org/cfp/details/140 in the etherpad15:34
*** Sajeesh_ has joined #openstack-meeting15:34
*** thedodd has quit IRC15:34
* bauzas loves to see his name 15:34
bauzasok, any other sessions to mention?15:35
*** asselin has joined #openstack-meeting15:35
mspreitzI have been thinking about 9915:35
mspreitzthat email just cited mixes 99 and 26215:35
mspreitzI was willing to accept 99 as a separete, small scope thing15:35
mspreitzbut that email links to bigger ideas15:35
bauzassounds lik15:35
mspreitzI agree that 99 can be seen as part of bigger things15:36
bauzasmspreitz: sounds like 99 is the first step for 26215:36
mspreitzExactly, let's do 99 as a baby step first15:36
*** pberis has joined #openstack-meeting15:36
bauzaswill also amend the etherpad if so15:36
jay-lau-513bauzas mspreitz yes, 99 is the first step for many projects ;)15:36
*** whenry has joined #openstack-meeting15:36
*** emagana has joined #openstack-meeting15:36
*** Sajeesh has quit IRC15:37
*** Sajeesh_ has quit IRC15:37
bauzaswell, the no-db sched effort would love discussing about 99, I bet :)15:37
*** ndipanov has joined #openstack-meeting15:37
bauzasmaybe I'm wrong, YorikSar ?15:38
bauzas:)15:38
bauzashttp://summit.openstack.org/cfp/details/9915:38
*** nacim_ has joined #openstack-meeting15:38
YorikSarbauzas: I won't come to summit but someone will definitelly come to discuss further directions in that.15:38
jay-lau-513the nova spec for 99 is here https://review.openstack.org/#/c/88983/15:38
*** emagana has quit IRC15:39
*** mwagner_lap has joined #openstack-meeting15:39
*** emagana has joined #openstack-meeting15:39
bauzasYorikSar: well, the idea of persisting hints would impact no-db sched efforts I suppose15:39
bauzasso, indeed, that would be worth discussing it at summit time15:39
bauzasjay-lau-513: I added myself to the reviewers for the spec15:40
YorikSarbauzas: I'm not sure about that. no-db part is about host states, not about resources themselves.15:40
jay-lau-513bauzas: yes, I think 99 does deserve a small session though it is straigforward, but it has some interation with other blueprints15:40
jay-lau-513bauzas: great :)15:40
bauzasjay-lau-513: will try to take time to review it15:40
bauzasanyway, that's a good transition for...15:41
jaypipesso many Jays... my IRC is just lighting up. :)15:41
bauzas#topic no-db scheduler15:41
*** openstack changes topic to "no-db scheduler (Meeting topic: gantt)"15:41
bauzasYorikSar: you're up15:41
bauzas:)15:41
jay-lau-513jaypipes sorry for the confuse :-)15:41
bauzasYorikSar: glad to see you took the blueprint15:41
YorikSarI've picked up Alexey's work in Nova.15:41
YorikSarCurrently it looks like technical part works.15:42
bauzasYorikSar: could you please summarize a bit on what you're doing?15:42
YorikSar(at least Jenkins is not complaining)15:42
bauzasYorikSar: I saw some patches15:42
mspreitzjay-lau-513: should that change be linked to bp?15:42
bauzasYorikSar: do you need reviewing help ?15:43
jay-lau-513mspreitz which change?15:43
YorikSarhttps://review.openstack.org/#/q/topic:bp/no-db-scheduler,n,z - this patch series15:43
*** _TheDodd_ has joined #openstack-meeting15:43
YorikSarI'd appreciate anyone besides bots to take a look at it.15:43
bauzas#link https://review.openstack.org/#/q/topic:bp/no-db-scheduler,n,z15:43
bauzas(for minutes)15:43
YorikSarI still have 2 -2's because I need to write blueprint to nova-specs and get it approved (again)15:44
jay-lau-513YorikSar I will add myself as reviewer15:44
YorikSarbauzas: thanks. I forget about those all the time15:44
bauzasYorikSar: ok, let us know when you're done with the spec, so we can review it15:44
bauzasYorikSar: that's already in my review list15:44
YorikSarI asked our Rally team to stress-test that code to see if there're more errors to be fixed.15:45
bauzasYorikSar: cool15:45
YorikSarjay-lau-513, bauzas: Thanks, I'm looking forward to your -1's (with comments) :)15:45
*** hemna_ has joined #openstack-meeting15:45
bauzasYorikSar: you know how I love reviewing your code ;)15:45
*** pberis has quit IRC15:45
*** doddstack has quit IRC15:46
YorikSarbauzas: It's Alexey's code with couple of bugs fixed by me15:46
*** pberis has joined #openstack-meeting15:46
*** jpeeler has quit IRC15:46
YorikSarbauzas: So you'll have to try to love reviewing his code too ;)15:46
bauzasYorikSar: ;)15:46
YorikSarI guess we can add an action item for me to publish spec.15:47
bauzas#action YorikSar to publish nova-spec for no-db scheduling blueprint15:47
bauzasthere it is15:47
YorikSarbauzas: cool15:48
bauzasthanks for your support :)15:48
*** jpeeler has joined #openstack-meeting15:48
bauzasYorikSar: is that basically ready for reviewing or do you plan further bugfixing ?15:48
bauzasYorikSar: as you mentioned, Jenkins is happy but still :)15:49
YorikSarbauzas: It's ready. Except for Memcached part that laks both unittests and real-world testing.15:49
YorikSarI'll mark that one as WIP15:49
bauzasYorikSar: cool thanks15:50
*** zhiyan is now known as zhiyan_15:50
YorikSarOh, I can't :(15:50
bauzasYorikSar: ok, no worries, just put a comment then15:50
YorikSarI'll -1 it :)15:50
bauzassure thanks15:50
bauzascan we move to open discussion ?15:50
YorikSarsure15:50
bauzas#topic opens15:50
*** openstack changes topic to "opens (Meeting topic: gantt)"15:50
bauzasthere, 10 mins to go15:51
bauzasany subject to raise?15:51
bauzasany miss I made ?15:51
bauzasany complain to do ?15:51
*** eghobo has joined #openstack-meeting15:51
*** reed has joined #openstack-meeting15:51
YorikSarHow often are we going to have these meetings?15:52
*** amotoki has quit IRC15:52
jay-lau-513Does the meeing time always UTC 15:00 every Tuesday?15:52
bauzasevery Tuesday15:52
*** asselin_ has joined #openstack-meeting15:52
bauzasjay-lau-513: indeed15:52
jay-lau-513bauzas: ok15:53
*** derekh has joined #openstack-meeting15:53
bauzashttps://wiki.openstack.org/wiki/Meetings/Scheduler15:53
YorikSarGreat. It's hard to remember when to expect every-other-week meetings. Good to have a weekly one :)15:53
*** jpeeler has quit IRC15:54
bauzaswell, I think we'll only have one left before summit15:54
*** jpeeler has joined #openstack-meeting15:54
bauzasmaybe on May 6th, but that's close to summit dates15:54
bauzasok, any other things to discuss ?15:55
*** venkatesh has joined #openstack-meeting15:55
bauzasPaulMurray: I had no time for reviewing yet (Monday was off in France), but I'll do it for your patches on extended RT15:55
bauzasPaulMurray: I saw some new patchsets15:56
*** rakhmerov has joined #openstack-meeting15:56
*** IlyaE has quit IRC15:56
bauzasPaulMurray: s/extended/extensible/15:57
*** Leonr has quit IRC15:57
*** amotoki has joined #openstack-meeting15:57
bauzasok, thanks all for your presence15:57
*** mrunge has joined #openstack-meeting15:58
bauzaslet's discuss next week15:58
bauzasthanks15:58
bauzas#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Tue Apr 22 15:58:18 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-22-15.00.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-22-15.00.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-22-15.00.log.html15:58
*** jay-lau-513 has quit IRC15:59
*** bauzas_ has joined #openstack-meeting16:00
*** rakhmerov has quit IRC16:00
*** YorikSar has left #openstack-meeting16:01
*** bauzas__ has joined #openstack-meeting16:01
*** IlyaE has joined #openstack-meeting16:01
*** jhenner1 has quit IRC16:02
*** jhenner has joined #openstack-meeting16:02
*** bauzas has quit IRC16:02
*** elo1 has joined #openstack-meeting16:02
*** jlibosva has quit IRC16:03
*** ameade has quit IRC16:03
*** bauzas_ has quit IRC16:05
*** vjay2 has joined #openstack-meeting16:06
*** vjay has quit IRC16:06
*** gcb has quit IRC16:07
*** elo1 has quit IRC16:10
*** ivasev has joined #openstack-meeting16:11
*** chandan_kumar has joined #openstack-meeting16:11
*** zdiN0bot has joined #openstack-meeting16:13
*** venkatesh has quit IRC16:13
*** venkatesh has joined #openstack-meeting16:14
*** mspreitz has quit IRC16:14
*** vjay2 has quit IRC16:15
*** markmcclain has joined #openstack-meeting16:15
*** venkatesh has quit IRC16:15
*** julim has quit IRC16:15
*** mrunge has quit IRC16:15
*** manishg has joined #openstack-meeting16:15
*** megan_w is now known as megan_w|afk16:16
*** vjay has joined #openstack-meeting16:19
*** tianst has quit IRC16:19
*** changbl has joined #openstack-meeting16:19
*** julim has joined #openstack-meeting16:20
*** zhangleiqiang has quit IRC16:20
*** chandan_kumar has quit IRC16:20
*** mattf has joined #openstack-meeting16:21
*** marcoemorais has joined #openstack-meeting16:21
*** mattf has left #openstack-meeting16:22
*** cjellick has quit IRC16:22
*** cjellick has joined #openstack-meeting16:23
*** egallen has quit IRC16:23
*** rakhmerov has joined #openstack-meeting16:23
*** ttrifonov_zZzz is now known as ttrifonov16:24
*** egallen has joined #openstack-meeting16:25
*** bauzas has joined #openstack-meeting16:25
*** PaulMurray has left #openstack-meeting16:26
*** elo1 has joined #openstack-meeting16:26
*** jgrimm has quit IRC16:26
*** hartbox has quit IRC16:27
*** tkay has joined #openstack-meeting16:27
*** Guest67395 is now known as hartsocks16:28
*** I159 has quit IRC16:28
*** I159_ has quit IRC16:28
*** nacim_ has quit IRC16:28
*** Leonr has joined #openstack-meeting16:30
*** bauzas__ has quit IRC16:30
*** megan_w|afk is now known as megan_w16:31
*** vhoward has left #openstack-meeting16:31
*** dburmistrov_ has joined #openstack-meeting16:31
*** emagana has quit IRC16:31
*** bauzas1 has joined #openstack-meeting16:31
*** rossk has joined #openstack-meeting16:32
*** ygbo has quit IRC16:33
*** jjmb has joined #openstack-meeting16:33
*** emagana has joined #openstack-meeting16:33
*** Leonr has quit IRC16:34
*** Leonr has joined #openstack-meeting16:34
*** jamespag` is now known as jamespage16:35
*** Leo_ has joined #openstack-meeting16:36
*** Leonr has quit IRC16:36
*** baoli has joined #openstack-meeting16:36
*** shakamunyi has joined #openstack-meeting16:40
*** ndipanov is now known as ndipanov_gone16:41
*** alexpilotti has quit IRC16:43
*** zdiN0bot has quit IRC16:44
*** alexpilotti has joined #openstack-meeting16:45
*** meteorfox has joined #openstack-meeting16:47
*** _nadya_ has quit IRC16:48
*** dkranz has quit IRC16:48
*** belmoreira has quit IRC16:50
*** doron is now known as doron_afk16:50
*** derekh has quit IRC16:51
*** ramishra has quit IRC16:52
*** ramishra has joined #openstack-meeting16:53
*** megan_w is now known as megan_w|afk16:53
*** ramishra has quit IRC16:53
*** ramishra has joined #openstack-meeting16:53
*** egallen has quit IRC16:54
*** jcoufal has quit IRC16:55
*** doron_afk has quit IRC16:55
*** atiwari has joined #openstack-meeting16:56
*** bauzas1 has quit IRC16:57
*** esperanza has quit IRC16:57
*** zdiN0bot has joined #openstack-meeting16:58
*** CristianF has joined #openstack-meeting17:00
*** safchain has quit IRC17:01
boris-42#startmeeting rally17:01
openstackMeeting started Tue Apr 22 17:01:54 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
*** jlibosva has joined #openstack-meeting17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: rally)"17:02
openstackThe meeting name has been set to 'rally'17:02
*** amotoki has quit IRC17:02
boris-42marcoemorais meteorfox msdubov ping17:02
msdubovboris-42, hi17:02
*** bauzas has quit IRC17:02
meteorfoxboris-42: hi17:02
boris-42hughsaunders ping17:02
*** enikanorov_ has joined #openstack-meeting17:02
marcoemoraisboris-42: hi17:02
*** pablosan is now known as zz_pablosan17:03
*** ameade has joined #openstack-meeting17:03
boris-42kun_huang ping17:03
*** mrunge has joined #openstack-meeting17:03
*** rediskin has joined #openstack-meeting17:03
boris-42rediskin hi17:03
rediskinhi17:03
*** dkranz has joined #openstack-meeting17:04
kun_huangboris-42 hi17:04
kun_huanglet's meeting :)17:04
* boris-42 kun_huang is ready to have some meeting17:04
boris-42^_^17:04
boris-42so let's start17:05
kun_huangboris-42 chen is pregnant, so it is a little hard for her being online at this time17:05
*** Leo_ has quit IRC17:05
boris-42kun_huang oO nice =)17:05
*** ameade has quit IRC17:05
boris-42kun_huang ok it's good that you are here so you'll be able to share info17:06
rediskincongratulations :)17:06
boris-42okay lets start=)17:06
*** megan_w|afk is now known as megan_w17:06
boris-42#topic PERFORMANCE GATES FOREVER!! =)17:06
*** openstack changes topic to "PERFORMANCE GATES FOREVER!! =) (Meeting topic: rally)"17:06
boris-42rediskin could you share with others17:06
*** emagana has quit IRC17:06
*** igormarnat_ has joined #openstack-meeting17:06
boris-42rediskin with your graet work =)17:06
*** eghobo has quit IRC17:07
rediskinnow we can easyly add rally-jobs. it is now as easy as python-jobs17:07
*** eghobo has joined #openstack-meeting17:07
rediskinbut17:07
rediskinwe have to make scenarios work out-of-the-box17:08
boris-42rediskin i think it's only related to nova benchmarks17:08
rediskinwithout editing image_id and other stuff17:08
boris-42marcoemorais should finish his patch soon17:08
boris-42marcoemorais ^17:08
marcoemoraisboris-42: ack17:08
marcoemoraisboris-42: saw your comments on review17:08
boris-42marcoemorais we will discuss it after this topic17:08
boris-42=)17:08
boris-42So for others that are not related to gates17:09
boris-42there is new gate in rally17:09
*** vjay has quit IRC17:09
boris-42it's called check-rally-dsvm-rally17:09
boris-42it will run 1 task with bunch of benchmarks17:10
rediskinthis job just run tests_ci/scenarios/rally.yaml17:10
boris-42and upload html with results17:10
rediskinso we need to add to this yaml as many scenarios as possible %)17:10
*** alexpilotti_ has joined #openstack-meeting17:10
meteorfoxboris-42: where in the tree is the code for this gate? ;)17:10
boris-42yep so we will put in rally.yaml all benchmarks17:10
rediskinhttps://review.openstack.org/#/c/86945/17:10
boris-42meteorfox it's not in tree yet17:10
rediskincurrently gates seems broken17:11
*** idegtiarov has quit IRC17:11
meteorfoxok17:11
*** vjay has joined #openstack-meeting17:11
boris-42meteorfox here is successful run  http://logs.openstack.org/45/86945/15/check/check-rally-dsvm-rally/780bb2e/logs/devstack-gate-post-test-hook.txt.gz17:11
boris-42meteorfox on bottom you can see table with result17:12
meteorfoxboris-42: thanks17:12
boris-42but it's now a bit complicated17:12
boris-42in future after this patch https://review.openstack.org/#/c/89562/17:12
boris-42we will get html plots=)17:12
meteorfoxawesome17:12
boris-42does anybody has any question?)17:12
marcoemoraisagree this is pretty nice17:13
kun_huanglove it17:13
msdubovboris-42, so the output is equivalent as if we run it with the -vd option?17:13
*** alexpilotti has quit IRC17:13
*** alexpilotti_ is now known as alexpilotti17:13
*** zns has quit IRC17:14
boris-42msdubov link was log*17:14
rediskinmsdubov: https://review.openstack.org/#/c/86945/17/tests_ci/rally-gate.sh17:14
boris-42msdubov that allows to troubleshot17:14
*** ayoung_ has joined #openstack-meeting17:14
boris-42msdubov but it will be as well plots17:14
*** marun has joined #openstack-meeting17:14
*** zdiN0bot has quit IRC17:14
msdubovboris-42, rediskin Yep I see17:14
*** nati_ueno has joined #openstack-meeting17:14
*** zdiN0bot has joined #openstack-meeting17:14
boris-42if morder or clarkb merge our patch https://review.openstack.org/#/c/89562/ =)17:15
boris-42so okay let's just move to next topic17:15
rediskinwhy merge out? merge in =)17:15
boris-42our*17:15
boris-42not out lol17:15
rediskin%)17:15
boris-42><17:15
boris-42#topic pre processing of args17:15
*** openstack changes topic to "pre processing of args (Meeting topic: rally)"17:15
*** david-lyle is now known as david-lyle_afk17:16
meteorfoxboris-42: will they gate have the concept of thresholds, say, like tolerating that the certain metric is +/- 10%, and have absolute limits?17:16
boris-42meteorfox I think in half year we will be able to make something like that17:16
*** vjay has quit IRC17:16
boris-42meteorfox or year17:16
boris-42=)17:16
meteorfoxboris-42: cool17:16
boris-42meteorfox it's hard cause node pool has absolutely different nodes17:16
boris-42and normalization in benchmarking is quite complex stuff17:16
boris-42marcoemorais ping17:17
boris-42marcoemorais your turn17:17
*** emagana has joined #openstack-meeting17:17
*** vjay has joined #openstack-meeting17:17
marcoemoraisboris-42: so open question is to add types17:17
marcoemoraisboris-42: types will be more generic way to apply transformation17:17
boris-42#link https://review.openstack.org/#/c/86116/17:17
boris-42marcoemorais so I think that Types will be simpler to organize code17:18
marcoemoraisboris-42: idea of types is to create a class which has a transform method17:18
boris-42and it will be simpler to understand17:18
*** harlowja_away is now known as harlowja17:18
*** _nadya_ has joined #openstack-meeting17:18
marcoemoraisboris-42: for now the only 2 Types are Image and Flavor17:19
meteorfoxmarcoemorais: sorry, I still no too familiar with the code base, what kind of Types are we talking about? benchmark types, results types?17:19
*** dkehn has quit IRC17:19
marcoemoraismeteorfox: Types are objects inside of our scenario config17:19
boris-42meteorfox we are speaking about input arguments17:20
meteorfoxgotcha17:20
rediskinkinda OpenStack objects types, like Image, Snapshot, Volume, Network?17:20
*** dkehn has joined #openstack-meeting17:20
boris-42meteorfox https://github.com/stackforge/rally/blob/master/doc/samples/tasks/nova/boot-and-delete.json#L5-L617:20
*** ramashri has joined #openstack-meeting17:20
marcoemoraismeteorfox: given a Type — you can do a transform on that type to normalize it to be consistent with what the scenario expects17:20
boris-42so we would like to be able to specify not only image_id17:20
meteorfoxok, now I understand, thanks17:21
boris-42we would like to specify image: {"id": some_id} or image: {"name": some_name}17:21
*** zns has joined #openstack-meeting17:21
boris-42image: {"reg": some_reg}17:21
*** dkranz has quit IRC17:21
boris-42and now marcoemorais made patch that allows us to do any transformations17:21
boris-42cause we are not able to use image name inside benchmark17:21
boris-42meteorfox cause it will be huge overhead inside benchmark (e.g. if you would like jus to show() image) overhead will be almost x217:22
*** nibalizer has joined #openstack-meeting17:22
boris-42so there are 2 ways to resolve issue17:22
boris-42more abstract17:22
boris-42e.g. transformations17:22
boris-42that can transfer input kwargs in any way17:22
boris-42or "types"17:22
boris-42that can transfer only one argument to something17:23
boris-42meteorfox rediskin ^17:23
boris-42As at this moment we have only Image and Flavor types and I don't think that we will have such multi arg transformations17:23
boris-42it  is better to keep things simpler17:23
boris-42and use just types17:23
*** Mikhail_D_ltp has joined #openstack-meeting17:24
meteorfoxok17:24
marcoemoraisboris-42 meteorfox where in the source tree should I put types under rally/tree/master/rally/benchmark/types?17:24
boris-42meteorfox yep17:24
msdubovboris-42, So having types as you suggested won't make it obligatory to specify them in the docstring as well, if I understand that correctly17:24
boris-42marcoemorais yep17:24
*** Mikhail_D_ltp has quit IRC17:24
boris-42msdubov probably we can reuse them17:25
boris-42msdubov for it as well17:25
*** ayoung_ is now known as ayoung17:25
*** morganfainberg_Z is now known as morganfainberg17:26
boris-42so marcoemorais  ok?17:27
marcoemoraisboris-42 meteorfox: yes, one more small issue — for regex, we will use "first match" or fail on ambiguity?17:27
*** crandquist has quit IRC17:28
boris-42marcoemorais validation stuff should fail17:28
boris-42marcoemorais and say multiply images possible17:28
marcoemoraisboris-42 ok17:28
boris-42,marcoemorais as well for name17:28
boris-42so next topic?17:28
boris-42#topic tempest & rally integration17:29
*** openstack changes topic to "tempest & rally integration (Meeting topic: rally)"17:29
*** rakhmerov has quit IRC17:29
boris-42sdague probably will be interesting for you^17:29
boris-42So actually I will just make some update17:29
boris-42So there are 2 parts:17:30
boris-421) verification part17:30
boris-422) benhmarking part17:30
boris-42In verification part17:30
*** crandquist has joined #openstack-meeting17:31
boris-42We have: 1) tempest conf generation 2) support of work with multiply clouds 3) parsing results to json and storing in rally db17:31
boris-424) and base operations to work with results, e..g show/detailed/results commands17:31
*** gyee has joined #openstack-meeting17:31
boris-42About benchmarking part17:31
*** jgrimm has joined #openstack-meeting17:32
boris-42The base patch that adds possibility to run any tempest test as benchmark was merged17:32
boris-42http://pavlovic.me/rally/tempest.html <- here is the sample of output17:32
boris-42so actually there will be couple of improvements17:32
boris-42A) we will mesure not only total duration (setUp, runTest, tearDown) but as well just of runTest in atomic actions17:33
boris-42B) we will support running different tests simultaneously (this will be super usefully for testing races in tempest tests)17:33
*** dkranz has joined #openstack-meeting17:34
boris-42Actually here is the patch17:34
boris-42https://review.openstack.org/#/c/86836/17:34
boris-42marcoemorais meteorfox msdubov hughsaunders kun_huang rediskin any questions ^ ?17:34
*** scotty95747 has quit IRC17:35
msdubovmsdubov, nope17:35
msdubovboris-42, nope17:35
marcoemoraisboris-42: high level question, what is distinction btwn use of tempest for benchmarking and use of rally scenarios for benchmarking?17:35
meteorfoxboris-42: +1 marcoemorais question17:36
*** ildikov_ has quit IRC17:36
boris-42marcoemorais rally benchmarks are more benchmarks lol=)17:36
*** dkehn has quit IRC17:36
boris-42e.g. we don't have mess of setUp/tearDown and running benchmark17:36
boris-42and we have powerful mechanism of context classes17:37
*** coreywright is now known as coreywright_17:37
*** epim has joined #openstack-meeting17:37
boris-42+ we are able to collect much more results17:37
*** dkehn has joined #openstack-meeting17:37
boris-42using atomic actions and in future I'll add collecting of all python clients calls (equivalent to http calls)17:37
boris-42that is unfortunately impossible with tempest unit tests17:37
marcoemoraisboris-42: I mean here, until rally, we did look at tempest (functional test) output as mini-benchmark, but it isn't as powerful as what we are doing with rally17:37
boris-42marcoemorais meteorfox ^17:38
*** gyee has quit IRC17:39
boris-42marcoemorais you disagree with this?)17:39
meteorfoxboris-42: so why is tempest integration needed, I think that's my question. :)17:39
boris-42meteorfox the answer is simple17:39
kun_huangboris-42 I think marcoemorais don't know this intrgration17:39
boris-42meteorfox 1) tempest has a bunch of validation tests (every day more)17:40
boris-42so running it to validate cloud is I think most proper way17:40
boris-422) why we need benchmarks from tempest tests?17:40
*** IlyaE has quit IRC17:40
boris-42there are couple of things17:41
boris-421) helping improving tempest (removing race conditions)17:41
boris-422) simple way to repeat race conditions from gates17:41
*** amotoki has joined #openstack-meeting17:41
*** amotoki has quit IRC17:41
boris-423) if you have something already implemented in tempest (some complex scenario) that you would like to run in rally you don't need to port it17:41
boris-42meteorfox ^17:41
boris-42meteorfox so as it was not hard to integrate tempest in Rally => why not?)17:42
*** jgallard has quit IRC17:42
boris-42meteorfox I mean benchmarking part* (verification part was quite tricky)17:43
meteorfoxboris-42: ok, I see. I'm concerned with new users, won't they be confused and prefer to write the benchmarks in tempest, where instead they should use Rally scenarios?17:43
kun_huangbtw reproduce race conditions is to use 'rally task start <path-to-tempest-scen>' ?17:44
*** zns has quit IRC17:44
meteorfoxboris-42: I see the value of "perf testing" tempest scenario, and testing for race conditions, but not so much as for a meaningful workload on the whole system.17:45
*** SumitNaiksatam has quit IRC17:45
meteorfoxboris-42: but I might not be understanding all of it.17:45
boris-42meteorfox if user would like to use tempest to benchmark cloud we should let him17:45
boris-42meteorfox it's his wiliness imho17:46
boris-42meteorfox our goal is to make it simple as possible17:46
*** bobt has joined #openstack-meeting17:46
meteorfoxboris-42: cool, ok.17:46
boris-42meteorfox why we should decide for others?)17:46
boris-42meteorfox my goal is to make it simple and it is all17:47
meteorfoxboris-42: true, I agree. :)17:47
boris-42meteorfox if it will be simple -> it will be popular -> many developers will start benchmark -> we will fix openstack17:47
*** baoli has quit IRC17:47
boris-42-> I will resolve my current task -> my boss happy -> me happy=)17:48
meteorfoxboris-42: lol17:48
*** lbragstad has joined #openstack-meeting17:48
*** emaganap has joined #openstack-meeting17:48
boris-42Okay let's move to next topic17:48
boris-42#topic new output table17:48
*** openstack changes topic to "new output table (Meeting topic: rally)"17:48
boris-42msdubov could you share with your ideas17:48
boris-42about new output17:49
*** baoli has joined #openstack-meeting17:49
msdubovboris-42 Yep17:49
msdubovSo basically the idea is to make the CLI output less messy17:49
*** sdake is now known as sdake-afk17:49
msdubovA reasonable first step seemingly would be to merge the 2 output tables17:49
msdubovNamely the result table and the atomic action table17:49
msdubovHere are 2 possible ways to do that: http://paste.openstack.org/show/76661/17:50
msdubovAny ideas on what looks better?17:50
meteorfoxmsdubov: still loading for me :/17:50
*** emagana has quit IRC17:50
msdubovNote that here I removed the "success/total" column17:51
kun_huangmsdubov opening it17:51
*** _nadya_ has quit IRC17:51
msdubovAnd moved it to the parens17:51
msdubovin "count"17:51
msdubovHopefully it is still clear enough, what "(0.7)" means there17:51
meteorfoxdid it open for anyone?17:51
*** chandan_kumar has joined #openstack-meeting17:51
kun_huangmeteorfox html title is loaded, but content not17:52
msdubovmeteorfox,  Seems that it hangs :(17:52
boris-42msdubov you gave us some strange link17:52
msdubovAn alternative link: http://pastebin.com/ps3bDrM917:52
marcoemoraismeteorfox: open for me, either table seems fine, but maybe the first is a little more typical (eg total at bottom rather than top)17:52
msdubovmarcoemorais, Yes, but the last row is also the most important one...17:53
msdubovThat's why I proposed the second table17:53
boris-42+117:53
boris-42I lie first one17:53
meteorfoxmsdubov: I agree with marcoemorais17:53
marcoemoraismsdubov: the % success (7/10) is still a problem for me, but I don't have an idea how to improve that17:53
kun_huang+1 for first one17:53
*** Mandell has joined #openstack-meeting17:53
boris-42yep17:53
boris-42so everybody decided to use first one17:54
kun_huangbut which is better, 0.7 and 70%17:54
msdubovOk, thanks. Any ideas on what to do with success % ?17:54
boris-42kebray 70%17:54
marcoemoraismsdubov: unless you have a row that is titled num failed or something that just has 3 in 'count' column and 'NA' in all other colums17:54
boris-42msdubov 70%17:54
boris-42msdubov btw do we need count at all?17:54
meteorfoxmsdubov: for the order of the columns, though, wouldn't avg, min, max, 90%ile, 95%ile be a better order?17:54
boris-42meteorfox yep agree min/agv/max is better then max/avg/min17:55
msdubovmsdubov Not sure, the order also requires discussion17:55
msdubovboris-42, Ok!17:55
boris-42about count it should be last column17:55
msdubovboris-42, But meteorfox actually suggested avg/min/max17:55
boris-42I think at least17:55
*** gyee has joined #openstack-meeting17:56
marcoemoraismsdubov: btw: enhancement would be to allow user to specify a % (some users will have a specific SLA to meet eg 98.5% of all requests <= y response time and will want rally to report that17:56
boris-42I think min/avg/max is probably better cause it raises from left tto right17:56
msdubovboris-42, Agree17:56
meteorfoxmsdubov: I think in order in order is better, what boris-42 suggested. min/avg/max17:56
marcoemoraisboris-42: agree with count as last colum17:56
msdubovmarcoemorais, Yep, I think we'll add custom percetiles soon17:57
meteorfoxmsdubov: what about %error?17:57
*** Gordonz has joined #openstack-meeting17:57
boris-42yep % instead of 0.7 will be better imho17:57
*** olaph has joined #openstack-meeting17:57
msdubovmeteorfox, boris-42, Perhaps than we can make a separate column for success %?17:57
*** zns has joined #openstack-meeting17:57
msdubovIt will have data only for the "total" row17:57
boris-42yep17:57
boris-42so to columns17:57
boris-42count | success17:57
boris-42?17:57
msdubovboris-42, How do you imagine that?17:58
boris-422 columns*17:58
boris-42two*17:58
*** Gordonz has quit IRC17:58
msdubovboris-42, Yep17:58
kun_huangboris-42 success (70%) should be the first column or last?17:58
*** topol has joined #openstack-meeting17:58
*** SumitNaiksatam has joined #openstack-meeting17:58
msdubovAnd success % only for the last row ("total")?17:58
boris-42msdubov it can be done for all columns17:58
*** Gordonz has joined #openstack-meeting17:58
boris-42=)17:58
boris-42msdubov okay we can discuss this in rally caht17:59
boris-42cause time is up17:59
msdubovboris-42, Yep17:59
boris-42#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Apr 22 17:59:22 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-04-22-17.01.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-04-22-17.01.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-04-22-17.01.log.html17:59
*** _nadya_ has joined #openstack-meeting17:59
*** egallen has joined #openstack-meeting17:59
*** dstanek has joined #openstack-meeting18:00
*** bgorski has quit IRC18:00
stevemaro/18:00
*** nkinder_ has joined #openstack-meeting18:00
*** rakhmerov has joined #openstack-meeting18:00
stevemardolphm, ayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder18:00
gyee\o18:00
dstaneko/18:00
*** zns has quit IRC18:00
lbragstaddolphm: hey18:00
bknudsondolphm: hi18:00
dolphmstevemar: thanks :)18:00
stevemargreetings keystoners18:00
bknudsonstevemar: hi18:00
morganfainbergOh lookie18:00
morganfainbergit's that time18:00
topolo/18:00
stevemardolphm, np, got your back18:00
lbragstadstevemar: you tricked me :)18:01
stevemarlbragstad, moi? impossible?18:01
atiwario/18:01
ayoung(゜.゜)18:01
*** assef has joined #openstack-meeting18:01
*** zz_pablosan is now known as pablosan18:01
ayoung(゜o゜)18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Apr 22 18:01:53 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
nkinder_hi all18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
*** Michalik- has quit IRC18:02
*** IlyaE has joined #openstack-meeting18:02
dolphmalright, i was waiting on sched.org... but that looks like it's going to take more than a couple minutes...18:02
dolphmanyway:18:02
dolphm#topic Icehouse released!18:02
*** openstack changes topic to "Icehouse released! (Meeting topic: keystone)"18:02
morganfainbergw00t!18:02
ayoung\(◎o◎)/18:02
*** meteorfox is now known as meteorfox|lunch18:02
*** coreywright_ is now known as coreywright18:02
*** mdenny has quit IRC18:02
stevemarwoot woot18:03
dolphm#link http://lists.openstack.org/pipermail/openstack-announce/2014-April/000225.html18:03
*** mdenny has joined #openstack-meeting18:03
topolGreat job! Congrats!!!18:03
*** mrunge has quit IRC18:03
topolLot of great stuff in icehouse18:03
*** jamielennox has joined #openstack-meeting18:03
*** yfried has quit IRC18:03
nkinder_woohoo!18:03
dolphm"Thanks to the hundreds of people who contributed to this development cycle and helped in making this release great!" <-- i can't echo that enough!18:03
*** vjay has quit IRC18:04
ayoungHere's a special thank you to our own Atlas.  Three cheers for the PTL.  Well done, dolphm18:04
lbragstad++18:04
gyeegood stuff!18:04
topol+++++18:04
stevemar+++18:04
dolphmit's been surprisingly quiet on the bug front, so i'm hesitantly excited about that too :P18:04
topolGreat job dolphm!!!18:04
morganfainberg+++++18:04
dolphmayoung: danke18:04
atiwari+++18:05
*** zns has joined #openstack-meeting18:05
*** sdake-afk is now known as sdake18:05
dstanek++18:05
jamielennox++18:05
dolphmmore fun stuff...18:05
dolphm#topic Design summit schedule18:05
*** openstack changes topic to "Design summit schedule (Meeting topic: keystone)"18:05
dolphm#link http://junodesignsummit.sched.org/18:06
dolphmi *just* pushed a tentative schedule to sched.org a few minutes ago, so the keystone track should appear there at some point ^18:06
*** ameade has joined #openstack-meeting18:06
*** nelsnelson has quit IRC18:06
*** sjcazzol_ has joined #openstack-meeting18:06
dolphmin the mean time, it looks something like this:18:07
dolphm#link http://i.imgur.com/Mglw49y.png18:07
*** nelsnelson has joined #openstack-meeting18:07
bknudson8 sessions?18:07
dolphmthis is very much a first draft: timeslots WILL be shuffled, etc18:07
dolphmbknudson: yes18:07
dolphmbknudson: one fewer than previous summits due to the cross-project tack18:08
dolphmtrack*18:08
*** vjay has joined #openstack-meeting18:08
topoldolphm, looks good18:08
nkinder_more reason to schedule a mid-cycle hackfest18:08
dolphmnkinder_: ++18:08
topolin San Antonio. Bring the pace pciante salsa18:08
nkinder_..get a rope18:08
topol++18:09
dolphmwe should also be a bit more organized for topics outside of formal design sessions18:09
gyeejust look for dolphm at the developer's lounge18:09
morganfainbergmid-cycle fun again!18:09
nkinder_yeah, there are some topics that would be nice to discuss that aren't in the sessions18:09
dolphmgyee: you should be able to look for a keystone flag or something :)18:09
dolphmgyee: not sure how it's all going to work yet18:09
gyeegrease him with beer, money, or whatever18:09
morganfainberggyee, whiskey18:09
topolthose breakfast burritos were good.  I hope the lamb food truck is there this time18:09
bknudsonif we're going to discuss service catalog we should consider what we're going to do with templated catalog18:09
morganfainbergbknudson, ++++18:10
bknudsonsince it seems to be getting left behind18:10
*** acoles is now known as acoles_away18:10
gyeemorganfainberg ++18:10
ayoungLeav it behind18:10
morganfainbergbknudson, i'm kindof for making it disappear.18:10
*** shohel02 has joined #openstack-meeting18:10
topolhow do we know there arent folks relying on it?18:10
ayoungit can easily be supported by SQL, or a KVS impl, so why keep a readonly, hard coded version?18:10
morganfainbergbknudson, its suboptimal on many fronts.18:10
gyeebknudson, catalog is a big elephant we need to tackle18:10
dstanekmorganfainberg, bknudson: does anyone use it?18:10
*** ameade has quit IRC18:10
morganfainbergdstanek, unfortunately we do18:10
* ayoung is visualizing gyee tackling an elephant. It is quite entertaining.18:11
*** dburmistrov_ has quit IRC18:11
morganfainbergdstanek, but it caused us major issues so we will move off it as soon as possible18:11
ayoungdstanek, we deprecate, and see if anyone shouts18:11
dolphmtopol: lack of bug reports, for starters. we're aware of issues that our users don't seem to care about18:11
bknudsonyou can't get a v3 token using the templated catalog now18:11
gyeeayoung, I mean elephant in the room, american thing, you don't want me to translate into other language18:11
dolphmi'd be happy to fix it if there are users18:12
ayoungWE NEED V2 /V3 INTEROP OR WE WILL NEVER GET PEOPLE TO V318:12
*** Hao has quit IRC18:12
*** vjay has quit IRC18:12
morganfainbergthis sounds like a ML topic to me18:12
dolphmayoung: i suspect that will be a significant topic for the client session18:12
ayoung++18:12
morganfainbergprobably x-posted to operators18:12
*** Hao has joined #openstack-meeting18:12
ayoungdolphm, wasn't there a miniscule patch that did the "chop v.20" off the endpoints?18:12
dolphmayoung: that landed18:13
dolphmayoung: i think it's in 0.7.018:13
jamielennoxayoung: it got merged - it doesn't really cover everything though18:13
ayoungAh...I was looking for it.  Good.18:13
morganfainbergpreferably I'd like that mail to be out there before we hit the summit so we have some information18:13
morganfainbergif needed i can write that email up.18:13
*** ttrifonov is now known as ttrifonov_zZzz18:13
ayoungjamielennox, I realize, but its a start18:13
*** mfisch has joined #openstack-meeting18:13
*** vjay has joined #openstack-meeting18:13
ayoungjamielennox, what critical is missing?18:13
dolphmmorganfainberg: i'd like to tackle that v2 deprecation bp in the next coupld weeks18:14
*** rakhmerov has quit IRC18:14
ayoungI mean, aside from support for other services....anything specific to Keystone>18:14
ayoung?18:14
jamielennoxhttps://review.openstack.org/#/c/81146/18:14
morganfainbergdolphm, yeah good plan18:14
topoldolphm in any of the federated sessions can we discuss audit support for federated environments?18:14
morganfainbergtopol, i thiink the answer is "we should emit audit for it"18:14
dolphmtopol: i think it's a given that we'll need to emit the appropriate audit notifications -- what is there to discuss?18:15
morganfainbergtopol, and anyone who complains about it is probably wrong18:15
jamielennoxah, it's been a while - i can't find the dependant one18:15
topolOK, so handle the details via blueprints. Thats cool18:15
stevemardolphm, there are a bunch of sessions marked as unreviewed, should those be considered rejected?18:15
*** eguz has joined #openstack-meeting18:15
morganfainbergtopol, yep, it would be silly not to do audit18:15
dolphmstevemar: likely, yes - unless i meant to merge something and didn't. i updated the statuses of as few as possible in a flurry right before this meeting18:15
ayoungjamielennox, starrring that one...18:15
stevemardolphm, cool18:16
jamielennoxayoung: there are a couple in my client list to do with discovery, version-less auth etc18:16
jamielennoxthe one i can't find is version-less endpoints in the catalog18:16
jamielennoxit should dep on that one18:16
nkinder_As an aside, has using gerrit for blueprints been previously discussed at all? (nova started doing this recently)18:16
*** Hao has quit IRC18:16
lbragstadI think that led into a discussion about storyboard18:17
sjcazzol_I was creating an specification to add quotas for users/projects by domain in the blueprint tenants-users-quotas18:17
*** ttrifonov_zZzz is now known as ttrifonov18:17
*** gothicmindfood has joined #openstack-meeting18:17
sjcazzol_what do you think about this blueprint?18:18
gyeejamielennox, is the discovery mechanism a standard or something we came up with18:18
jamielennoxgyee: it's something that is close to standard (which is possibly worse)18:19
*** eghobo has quit IRC18:19
*** tongli has joined #openstack-meeting18:19
*** ttrifonov is now known as ttrifonov_zZzz18:19
*** kgriffs is now known as kgriffs|afk18:19
jamielennoxgyee: we forked it from nova - and made changes, other projects either did the same or came up with there own18:19
gyeejamielennox, I think TC should take on this one18:19
sjcazzol_this blueprint is in the path to get parity on quota management with AWS18:19
dolphmnkinder_: yes18:19
gyeeas it has wider impact18:19
jamielennoxgyee: i did a spec a while ago https://wiki.openstack.org/wiki/VersionDiscovery18:20
*** eddie has joined #openstack-meeting18:20
dolphmgyee: ++18:20
*** jtomasek has quit IRC18:20
jamielennoxgyee: publicised as much as i could and was well received - but who knows if people look at it18:20
*** eddie is now known as Guest5541018:20
*** Guest55410 has quit IRC18:20
jamielennoxgyee: the problem is no one will change because they all need backwards compat18:20
*** dburmistrov_ has joined #openstack-meeting18:21
*** akuznetsov has quit IRC18:21
dolphmjamielennox: the only opposition i recall is that there's an IETF draft of something similar?18:21
jamielennoxor at the very least we need to support older versions pre-changed because we can't afford  to wait for them all to standardize18:21
morganfainbergdolphm, really an IETF draft?18:21
jamielennoxdolphm: not an IETF thing - there's a json-home spec which one of the new projects is using18:21
dolphmmorganfainberg: well there's a few, but one actually has some traction IIRC18:21
morganfainbergah.18:21
dstanekdolphm: url?18:22
dolphm#link http://tools.ietf.org/html/draft-nottingham-json-home-0218:22
dolphmnot sure if that's the latest18:22
jamielennoxAFAIK no-one is actually converting anything though18:22
dolphmjamielennox: thanks, i couldn't remember the name18:22
*** ramishra has quit IRC18:22
dolphm#link https://github.com/otto-de/jsonhome18:22
morganfainbergthis is something the TC should weigh in on and specify a direction to take since it needs to be consistent across projects18:22
dolphmdraft 3!18:23
dolphm#link http://tools.ietf.org/html/draft-nottingham-json-home-0318:23
*** ramishra has joined #openstack-meeting18:23
jamielennoxmorganfainberg: i don't disagree - but we can't wait for that18:23
*** jprovazn has joined #openstack-meeting18:23
morganfainbergjamielennox, we may not be able to wait, but we can at least get that up for consideration with the new TC convening soon18:23
gyeejamielennox, wait for a consistent approach, or go alone and risk retrofit later? :)18:23
ayoung++18:23
morganfainbergjamielennox, if we have a clear direction, we can figure out where we're headed and how to best get there18:24
ayounggyee, or make keystoneclient own the service catalog and just solve it for everyone18:24
jamielennoxgyee: this is client side, we are always going to have to support older versions18:24
*** baoli has quit IRC18:24
gyeeretrofitting protocol is much difficult18:24
morganfainbergayoung, ++18:24
jamielennoxayoung: that is the plan18:24
*** vjay has quit IRC18:24
morganfainbergayoung, we should absolutely own the SC in either case18:24
ayoungand policy18:24
jamielennoxif anything this means that at least all discovery should come from one place so it should be easier to convert people later18:25
dolphmayoung lost me -- this doesn't have much to do with the catalog...18:25
morganfainbergayoung, that is a slightly different topic...but don't disagree.18:25
*** vjay has joined #openstack-meeting18:25
morganfainbergayoung, lets table the policy bit from this convo, it's not directly relevant18:25
*** ramishra_ has joined #openstack-meeting18:26
*** krtaylor has quit IRC18:26
ayoungsure18:26
*** eddie_ has joined #openstack-meeting18:26
jamielennoxfor comparison dtroyer has a similar discovery mechanism in OSC and (i think it's new again) in -SDK18:26
*** hemna__ has joined #openstack-meeting18:26
jamielennoxanything that expects to work across projects is going to have a really bastardized/hacky discovery mechanism18:26
*** ramishra has quit IRC18:27
morganfainbergjamielennox, ok so i come back to we need the TC to set the direciton then work to get from here to there -- however hacky it is.18:27
morganfainbergjamielennox, but making another standard.....18:27
gyeemorganfainberg, amen, brother18:27
morganfainbergjamielennox, wait isn't there an XKCD about standards.18:27
jamielennoxmorganfainberg: right - but that's a future direction. we don't get to wait for interop until the TC makes all projects convert to a standard18:27
*** eharney has quit IRC18:28
gyeejamielennox, then what is TC for?18:28
*** jtomasek has joined #openstack-meeting18:28
nkinder_can't we do both?  Start consulting with the TC, but let them know we need to forge ahead?18:28
gyeeceremonial?18:28
morganfainbergnkinder_, ++18:28
nkinder_we might get at least some early guidance18:28
jamielennoxi honestly couldn't care less what the format is, we need to get people moving to v3 and that doesn't happen until we can do discovery18:28
ayounglets provide them with a solution18:28
morganfainbergnkinder_, i think we can get an answer on where we are doing and work towards it without interop18:28
nkinder_yes, we might serve as the model for the standard if we start working with the TC from the outset18:29
jamielennoxthe wiki i linked earlier was the most common elements of nova/keystone/glance etc the older projects18:29
jamielennoxthe projects that were going to find it most difficult to change18:29
ayoungI think what jamielennox was driving towards works for the majority of the services. The ones it doesn't work for are one-offs anyway18:29
ayoungand will require specific fixes that are not generalizable18:29
morganfainbergnkinder_, we should get the TC involved before we get too deep into the impl so we don't end up with yet-another-standard18:29
*** doron_afk has joined #openstack-meeting18:29
*** chandan_kumar has quit IRC18:29
dolphmi suspect nottingham's proposal was at least in part a result of his time spent working in/around openstack18:29
jamielennoxmorganfainberg: this is not creating a standard - it's reacting to existing standards18:30
ayoungjamielennox, please make sure the relevant reviews have keystone-core +nkinder set as reviewers18:30
jamielennoxdolphm: i didn't think he had anything to do with openstack18:30
morganfainbergjamielennox, and if we go create an implementation to solve that... without clear direction that this is the way going forward, we have created another "standard" that the new system needs to support18:30
jamielennoxdolphm: the way i read it it was related to the json-api stuff, but it's been a while18:31
dolphmjamielennox: http://www.mnot.net/personal/resume.html18:31
morganfainbergjamielennox, i'm not saying don't do the work, i'm saying concurrently involve the TC so we know where we need to eventually land and we don't write ourselves into a corner reacting to the current situation18:31
topolwould it be worth an email on the mailing list to see if anyone still uses the templated catalog?18:31
*** manishg has quit IRC18:31
topoljust to do a little cya for us if we pull it?18:31
morganfainbergtopol, yes. x-posted to operators list as well18:31
topolmorganfainberg will you handle that?18:31
morganfainbergtopol, yeah was planning on it once the meeting was done since no one responded to my earlier question18:32
topolcool18:32
dstanekjson-home appears to be a document format - what does that have to do with discovery?18:32
ayoungSo...we should make a concerted push on all client issues in the lull between now and the summit18:32
dolphmmorganfainberg: awesome18:32
morganfainbergtopol, just going to ask for metrics on use not indicate we're trying to remove it.18:32
ayoungaside from discovery....thkns for the help thus far on comporessed tokens18:32
morganfainbergtopol, don't want to induce panic18:32
jamielennoxmorganfainberg: sure, that's what i tried to do with that wiki page - but client still claims compatability with like essex clouds so we are going to have to react to the current18:32
*** _nadya_ has quit IRC18:33
ayounghttps://review.openstack.org/#/q/status:open+project:openstack/python-keystoneclient,n,z    quite a few there still18:33
*** manishg has joined #openstack-meeting18:33
dstanekit's more about navigating hypermedia to navigate the API - similar to what html provides18:33
*** gokrokve has quit IRC18:33
morganfainbergjamielennox, and thats fine. lets get this on the agenda for the TC first thing and start the work now.18:33
morganfainbergjamielennox, we can put some compat stuff in as needed for the old deployments18:33
ayounghttps://review.openstack.org/#/c/81166/  revocation API needs to be in the client before it is usable.18:34
dolphmayoung: ++18:34
*** atiwari has quit IRC18:34
morganfainbergayoung, +++++18:34
*** MIDENN_ has joined #openstack-meeting18:35
*** mdenny has quit IRC18:35
nkinder_one other topic that would be nice to discuss at the design summit is keystone scalability/performance18:35
*** gyee has quit IRC18:35
topolmorganfainberg, nice. good to not induce panic.18:35
*** crc32 has joined #openstack-meeting18:35
ayoungjamielennox's client patches  https://review.openstack.org/#/q/status:open+project:openstack/python-keystoneclient+owner:jamielennox,n,z18:35
stevemarnkinder_, it doesn't do either well atm :(18:35
dolphmnkinder_: absolutely, and i'm sure we will18:35
morganfainbergnkinder_, that is plan for the POD/Dev Lounge18:35
nkinder_I was talking with someone last week who has a large delpoyment, and keystone is the performance bottleneck18:35
ayounghttps://review.openstack.org/#/c/74599/  that was the heart of the discussion, right?18:36
jamielennoxayoung: on the up side that list is the shortest it's been in a while18:36
nkinder_Ok, great.  I know the ephemeral token work is a part of it, but it would be good to outline a plan for other areas too18:36
stevemarnkinder_, <sarcasm tell them to flush tokens />18:36
morganfainbergnkinder_, yep, and expanding caching, working on improving SQL performance etc18:36
morganfainbergnkinder_, lots of things to do18:36
nkinder_stevemar: that was my first response, followed by reducing the token validity period :)18:36
bknudsona rally person was in openstack-keystone the other day discussing how they can post their results for perf tests18:37
*** CristianF has quit IRC18:37
ayoungnkinder_, do they have any profiling data?18:37
*** arnaud has joined #openstack-meeting18:37
nkinder_ayoung: we can get some I'm sure18:37
ayoungand are they on anything modern, or is this an essex setup?18:37
*** eddie_ has quit IRC18:37
nkinder_once thing mentioned was scaling across cores (not just for keystone)18:37
ayoung(RHOS 4 I assume)18:37
nkinder_ayoung: havana18:37
morganfainbergbknudson, yeah i want to sync up w/ the rally guys and get that info going in (probably on the checks)18:37
ayoungnkinder_, so, is the bottleneck calling Keystone from Horizon (list users etc) or token request and verification?  Are they using UUID tokens?18:38
ayoungOr PKI18:38
ayoungRHOS4 == Havana for the rest of the team18:38
morganfainbergayoung, ah yes.18:39
ayoung5 will be Icehouse and so on18:39
nkinder_ayoung: spinning up hundreds/thousands of new instances at once18:39
ayounginteresting....18:39
sjcazzol_I would discuss a bp to add quotas for the # of projects/users created by domain18:39
nkinder_ayoung: this was >1000 pyhsical systems18:39
dolphm#topic open discussion18:39
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:39
morganfainbergnkinder_, that is not exclusively a keystone issue but it's def related.18:39
ayoungscripted?  Are they reusing tokens or getting a new one for each op?18:40
morganfainbergnkinder_, we have had similar complaints (smaller hypervisor counts)18:40
bknudsonI was wondering if we could discuss https://bugs.launchpad.net/python-keystoneclient/+bug/128730118:40
uvirtbotLaunchpad bug 1287301 in python-keystoneclient "Keystone client token cache doesn't respect revoked tokens" [Medium,In progress]18:40
nkinder_morganfainberg: sure, other areas are problems too (nova scaling across cpus, etc.)18:40
morganfainbergnkinder_, yep18:40
*** rakhmerov has joined #openstack-meeting18:40
jamielennoxbknudson: looking18:40
morganfainbergnkinder_, they were scripted against the API directly but similar issues, adding neutron in causes more pain (due to token issuance insanity)18:41
ayounggyee is gone...he's the one that held up https://bugs.launchpad.net/python-keystoneclient/+bug/128730118:41
bknudsonso the proposed fix was, I think, to check both the token cache AND the revocation list18:41
ayoungI still don't understand his concern18:41
ayoungI think he's wrong18:41
bknudsonwhereas before it was checking only the token cache18:41
*** gothicmindfood has left #openstack-meeting18:41
morganfainbergbknudson, that was my understanding18:41
jamielennoxbknudson: i was under the impression that became a non-issue18:41
*** ramishra_ has quit IRC18:41
*** kun_huang has quit IRC18:41
bknudsonwhich doesn't seem like a terrible thing to do18:41
*** MIDENN_ has quit IRC18:41
*** rakhmerov has quit IRC18:42
*** hemna__ has quit IRC18:42
sjcazzol_I would discuss a bp to add quotas for the # of projects/users created by domain in https://blueprints.launchpad.net/keystone/+spec/tenants-users-quotas18:42
*** rakhmerov has joined #openstack-meeting18:42
bknudsonwell, the revocation cache and the token cache were changed to have the same timeout18:42
*** ramishra has joined #openstack-meeting18:42
*** aysyd has quit IRC18:42
*** rbowen has joined #openstack-meeting18:42
bknudsonso maybe it is a non-issue?18:42
jamielennoxsjcazzol_: i think this or something similar has been raised before18:43
morganfainbergbknudson, i think it is worth revisiting.18:43
ayoungbknudson, yeah, his concern seems ill-=placed.  I PMed him and his response still puzzles me18:43
dolphmsjcazzol_: it's open discussion, feel free18:43
morganfainbergsjcazzol_, i know there is demand from my company's customers for something like that (when we move to domains)18:43
*** vjay has quit IRC18:44
ayoung"If you really want to do it right, get rid of revocation_cache_time and come18:44
ayoungup with a lightweight daemon process to listen on the revocation events and update the cache accordingly. Similar to how Certmonger monitoring the certificate status and perform automatic renewal."18:44
morganfainbergsjcazzol_, so please :) lets discuss it!18:44
jamielennoxsjcazzol_: and from memory there are two problems 1 there is no standard quotaing method in keystone or openstack 2. why? users are cheap18:44
*** ThiagoCMC has joined #openstack-meeting18:44
ayoungsjcazzol_, how are you going to distribute global quotas, and how are you going to enforce?18:44
bknudsonayoung: I can see the desire to have some kind of notification... maybe revocation events makes it a non-issue18:44
*** sweston has joined #openstack-meeting18:44
morganfainbergjamielennox, it's project quotas18:45
ayoungbknudson, regardless...he's wrong18:45
morganfainbergjamielennox, not users.18:45
jamielennoxmorganfainberg: users per project18:45
*** vkmc has quit IRC18:45
*** kun_huang has joined #openstack-meeting18:45
morganfainbergjamielennox, oh wait did i misread it?18:45
*** novas0x2a|laptop has joined #openstack-meeting18:45
morganfainbergjamielennox, ah18:45
jamielennoxusers per domain, users per project18:45
*** sjcazzol has joined #openstack-meeting18:45
morganfainbergsjcazzol_, i'm in support of working on a quota of projects per domain18:45
morganfainbergsjcazzol, but i don't see a value to users per domain?18:45
ayoungbknudson, cache is to keep from doing a validation again, but a revocation event timeout (or revocation list) still needs to be checked.  It doesn't render the cache useless.18:46
jamielennoxmorganfainberg: is it just a billing thing?18:46
*** gyee has joined #openstack-meeting18:46
*** sjcazzol_ has quit IRC18:46
morganfainbergjamielennox, less billing more they allow anyone to create projects on demand18:46
nkinder_I suppose you could prevent someone from adding 1M users that way18:46
morganfainbergjamielennox, they would like to limit it because a project can consume a network18:46
*** kun_huang has quit IRC18:46
morganfainbergjamielennox, etc.18:46
*** rakhmerov has quit IRC18:46
morganfainbergjamielennox, so you can give them a domain and they get X projects to play with18:46
*** ildikov has joined #openstack-meeting18:46
*** ramishra has quit IRC18:47
gyeeayoung, you have a question for me, sorry I have a shitty connection here18:47
morganfainbergjamielennox, dev, stage, prod, prod2, etc but not 1000 projects18:47
ayounggyee, yeah18:47
morganfainbergjamielennox, you can make a policy saying "no don't do that" or you can enforce "you get X projects"18:47
*** sjcazzol_ has joined #openstack-meeting18:47
ayounggyee, can you please unblock  https://bugs.launchpad.net/python-keystoneclient/+bug/128730118:47
uvirtbotLaunchpad bug 1287301 in python-keystoneclient "Keystone client token cache doesn't respect revoked tokens" [Medium,In progress]18:47
bknudsongyee: https://review.openstack.org/#/c/78241/18:47
ayoungI think you are wrong in that it does not invalidate the value of the cache18:47
jamielennoxmorganfainberg: fair enough, it'd be nice if this stuff was a bit more generic across openstack18:48
morganfainbergjamielennox, yeah18:48
*** eglynn-call has joined #openstack-meeting18:48
*** eglynn-call is now known as eglynn18:48
ayoungcache in this case will prevent a popen openssl cms call18:48
jamielennoxmorganfainberg: i wouldn't prefer not to have a whole quotaing system within keystone18:48
gyeethat one doesn't *fix* the problem completely18:48
bknudsonsince https://review.openstack.org/#/c/78241/ is abandoned, may not be able to re-do18:48
*** vjay has joined #openstack-meeting18:48
ayoungand you still want to check that the token is not revoked separate from cached timeout18:48
morganfainbergjamielennox, ++ consistent quota system would be nice. but i don't think we have anything like that yet*18:48
dolphmjamielennox: is that a +1 for a standalone quota service? :D18:48
ayoungwe can resubmit in a different reviewid if needs be18:48
jamielennoxdolphm: i think i +1ed that a while ago18:49
dolphmmorganfainberg: there is actually an abandoned standalone quota service18:49
sjcazzol_morganfainberg, what about to have quotas for user but per project instead of domain?18:49
dolphmjamielennox: probably so18:49
morganfainbergbknudson we can have infra restore a review18:49
gyeeayoung, best we can do is reverse the order between revocation cache and token cache18:49
ayoung?18:49
dolphmgyee: reverse the check?18:49
dolphmorder of checks*18:49
gyeedolphm, yes18:49
ayounggyee, that makes no sense18:49
morganfainbergsjcazzol_, i don't see a value to limiting the number of users in that regard, what is the value / usecase?18:49
morganfainbergsjcazzol_, users are cheap.18:49
*** sjcazzol has quit IRC18:49
gyeeright now token_cache_time have priority over revocation_cache_time18:49
ayoungwe pull the token out of memcached first, check against the revocation list second18:50
gyeethat patch, if implemented correct, will reverse the order18:50
bknudsoncurrently we're not checking revocation list if it's in the cache18:50
gyeeand that's it, but its still not real time18:50
morganfainberggyee, if we hit the cache, no popen call18:50
*** emaganap has quit IRC18:50
morganfainberggyee, avoiding popen would be good?18:50
morganfainberggyee, doesn't mean we shouldn't also check revocation list18:50
*** zns has quit IRC18:51
gyeemorganfainberg, yes, it's only helpful if token_cache_time is much greater than revocation_cache_time18:51
morganfainberggyee, oh i see, no popen is needed if we check TRL first18:51
gyeeright now they are both default at 300 seconds18:51
bknudsonboth those cache times are configurable.18:51
gyeelemme unblock, but that's just an half-ass solution18:51
sjcazzol_morganfainberg, I think it should be to avoid performance issues18:52
morganfainbergsjcazzol_, i would argue that limitation is premature optimisation18:52
gyeeif you want real time check, implement a lightweight process to listen on revocation events and update the cache18:52
*** armax has joined #openstack-meeting18:52
gyeesimilar to certmonger18:52
*** chandan_kumar has joined #openstack-meeting18:53
sjcazzol_morganfainberg, yes18:53
morganfainberggyee, sure. better solution, but we should make things incrementally better if we can as well.18:53
*** zns has joined #openstack-meeting18:53
jamielennoxgyee: also a standalone service on every machine with auth_token is a big ask18:53
*** _nadya_ has joined #openstack-meeting18:53
gyeejamielennox, no18:54
ayounggyee, you mean thread, right?18:54
*** aysyd has joined #openstack-meeting18:54
gyeememcached is usually running in a ring18:54
morganfainbergayoung, thread/process same thing right?18:54
gyeeyou just need one process18:54
dolphmjamielennox: on every machine?18:54
morganfainbergayoung, when you involve external (memcache) kvs for the cache18:54
*** ameade has joined #openstack-meeting18:54
morganfainbergayoung, this isn't in-mem18:54
sjcazzol_morganfainberg, also it could be used to charge extra money in case a domain is requesting more users/projects18:54
ayoungits like token_flush.18:55
jamielennoxdolphm: i guess it depends on where memcache is18:55
jamielennoxbut i'm guessing for auth_token it's largely just on the same machine18:55
gyeeayoung, can't unblock, patch is abandon18:55
ayoungrevoation list fetch could easily be done external to the flow, but it would not make a difference.18:55
*** zns_ has joined #openstack-meeting18:55
gyeeauthor needs to restore it first I guess18:55
nkinder_I'd like to briefly discuss the keystone security info wiki pages while we still have a few minutes (or we can take it to #openstack-keystone afterwards)18:55
ayounggyee, NP.  so long as you agree in principal to the direction, we can create a new review if necessary18:55
nkinder_I've added a new security info page for keystone in Juno now that Icehouse has been released18:56
gyeeayoung, I don't agree with the current impl, but its some improvement nevertheless18:56
*** overlayer has joined #openstack-meeting18:56
morganfainbergsjcazzol_, sure, lets work on figuring out quota stuff and we can implement as many/few quota implements then (argue about the individual ones)18:56
*** IlyaE has quit IRC18:56
dolphmjamielennox: ah, i thought you were referring to another web service18:56
*** hub_cap has joined #openstack-meeting18:56
morganfainbergnkinder_, awesome!18:56
nkinder_I added a new section at the bottom to cover security items that have changed since the previous release18:56
bknudson I asked on -infra if https://review.openstack.org/#/c/78241/ could be restored.18:56
dolphmgyee: leave a comment that you'll unblock when the author restores?18:57
nkinder_https://wiki.openstack.org/wiki/Security/Juno/Keystone#Notable_changes_since_Icehouse18:57
gyeedolphm, sure18:57
nkinder_We have a few things in progress that I called out there (and the LDAP hashing patch that landed)18:57
morganfainbergi hear we might have a new gerrit soon™, and i think cores will be able to restore patches for their project from abandoned18:57
bknudsongyee: https://review.openstack.org/#/c/78241/ is restored now18:57
ayounggyee, I think you are caluclating wrong18:57
dolphmthis showed up at some point:18:57
dolphm#link http://junodesignsummit.sched.org/overview/type/keystone18:58
dolphmdesign summit schedule ^18:58
dolphm(TENTATIVE)18:58
*** zns_ has quit IRC18:58
ayoungcache time of 300 starts when token is validated.  Revocation cache time is every 300 regardless.  They do not necessarily align18:58
dolphmalso, time's up18:58
bknudsonlooks like I don't have to show up until wed18:58
*** zns has quit IRC18:58
morganfainbergbknudson, hehe18:58
*** nati_ueno has quit IRC18:58
*** vhoward has joined #openstack-meeting18:58
dolphmbknudson: cross-project tracks tuesday18:58
morganfainbergbknudsonm there are cross project things on tuesday18:58
dolphm#endmeeting18:58
dstaneki think the cache time configuration doesn't matter - even if the values are the same18:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:58
openstackMeeting ended Tue Apr 22 18:58:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-04-22-18.01.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-04-22-18.01.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-04-22-18.01.log.html18:59
nkinder_thanks everyone!18:59
*** sjcazzol_ has quit IRC18:59
*** egallen has quit IRC18:59
*** jamielennox has left #openstack-meeting18:59
*** dprince has quit IRC19:00
*** emagana has joined #openstack-meeting19:00
clarkbo/19:00
anteayao/19:00
*** zns has joined #openstack-meeting19:00
zaroo/19:00
pleia2o/19:00
jeblairwho else is around for the infra meeting? :)19:00
*** jeblair sets mode: -o jeblair19:00
anteayamordred is on the agenda19:01
jeblairi put him there19:01
anteayak19:01
_nadya_o/19:01
*** rockyg has joined #openstack-meeting19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Apr 22 19:01:42 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. 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: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
*** jmontemayor has quit IRC19:01
jeblairagenda:19:01
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
jeblairlast meeting:19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-15-19.01.html19:02
jeblair#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
jeblairmordred to test zaro's gerrit upgrade instructions (with timing info)19:02
jeblairmordred: ?19:02
*** ameade has quit IRC19:02
*** david-lyle_afk is now known as david-lyle19:03
jeblair<sigh>19:03
*** roaet has joined #openstack-meeting19:03
clarkbzaro: do you know if he did that yet?19:03
*** derekh has joined #openstack-meeting19:03
*** roaet has quit IRC19:03
nibalizerim here19:03
zaroi do not know19:03
*** phschwartz has joined #openstack-meeting19:03
SergeyLukjanovo/19:03
*** schwicht has joined #openstack-meeting19:03
swestono/19:03
anteayado we have a back up plan?19:03
*** radez_g0n3 is now known as radez19:03
*** nati_ueno has joined #openstack-meeting19:04
jeblairanteaya: we trust that zaro has tested his instructions :)19:04
anteayago zaro19:04
jeblairit would have been nice to get a second set of eyes on the process, but zaro's been working on this for a while so i assume he knows what he's doing.  :)19:04
jeblairthe backup plan is that if something goes minorly wrong, we wing it.19:05
*** nkinder_ has left #openstack-meeting19:05
* clarkb has randomly poked at it with zaro and it seems to be well handled19:05
jeblairthe backup backup plan is we roll back19:05
*** bobt has quit IRC19:05
anteayagood enough19:05
swestonI can test them!19:05
*** roaet has joined #openstack-meeting19:05
*** jcoufal has joined #openstack-meeting19:05
*** roaet has quit IRC19:05
jeblairwhich, should be fairly easy to do since i think we will be building the replacement on another host19:05
swestonI don't know about the timing though, someone may have to work with me on that.19:05
*** roaet has joined #openstack-meeting19:05
jeblair#topic  Gerrit 2.8 upgrade (zaro)19:05
*** openstack changes topic to "Gerrit 2.8 upgrade (zaro) (Meeting topic: infra)"19:05
jeblairwe might as well move into that ^ :)19:06
anteayathat was my understanding, this is on a new host19:06
*** roaet has quit IRC19:06
*** igormarnat_ has quit IRC19:06
jeblair#link https://etherpad.openstack.org/p/remaining-gerrit-upgrade-changes19:06
*** roaet has joined #openstack-meeting19:06
jeblairsweston: i think ^ has all the info19:07
zaroi've verified that puppet is able to deploy review-dev and verified that review-dev is working as expected.19:07
anteayasweston: I would offer to help but I still can't get current gerrit up with puppet19:07
jeblairzaro: awesome -- that's very reassuring19:07
*** krtaylor has joined #openstack-meeting19:07
zarojeblair: i've rebased my changes on top of your changes for nodepool.  need that reviewed.19:07
*** GheAway is now known as GheRivero19:07
jeblairzaro: which?19:07
zaroanteaya: i wasn't able to either.  clarkb did it for me.19:08
*** shohel02 has quit IRC19:08
jeblairzaro: did mordred not update the 2.8 branch for you?19:08
zarojeblair: https://review.openstack.org/#/c/8802619:08
jeblair(i'm noticing those items are still on the list and not struck out)19:08
*** roaet has left #openstack-meeting19:08
zarojeblair: i don't think it's been updated. but let me check again.19:08
*** denis_makogon has joined #openstack-meeting19:09
swestonanteaya: I was able to do it, fortunately :-)  I am always available in IRC for questions.19:09
*** imsurit has quit IRC19:09
anteayasweston: awesome, hopefully you can follow through zaro's instructions then19:10
swestonyup, I will refresh my environment and then start testing this afternoon19:11
anteayasweston: let me work with you on that, maybe you can teach me19:11
swestonanteaya: that sounds lovely.  Anyone else is welcome to join, the more, the merrier!19:11
*** gyee has quit IRC19:11
*** rbowen has quit IRC19:11
zarojeblair: looks like openstack stable-2.8 has been synced with gerrit upstream stable-2.819:11
zarojeblair: don't know which method was used to do it though.19:12
jeblairzaro: doesn't matter, so what next?  do we need an openstack/2.8.4 branch?19:12
swestonanteaya: that will work well, as I have an action item to create some documentation for the upgrade process as well.19:13
anteayasweston: great19:13
zarowe need to update openstack/2.8 branch with commits from stable-2.8 branch19:13
anteayayay docs19:13
sweston+1 yay docs!19:13
*** tris has joined #openstack-meeting19:13
*** hashar has joined #openstack-meeting19:13
jeblairlet's focus on the branch topic for a sec19:13
anteayasorry19:14
zaromordred didn't do that.  so anybody want to take care of that?19:14
*** bruff has joined #openstack-meeting19:14
* sweston gets excited too easily19:14
clarkbI can create the branch if you give me a sha119:14
jeblairi'm not sure we're all following the same process here19:14
*** nati_ueno has quit IRC19:14
* clarkb holds off for jeblair to explain19:14
jeblairzaro: what is the difference between the openstack/2.8 and openstack/2.8.3 branches?19:15
zaroi'm referring to line #7 on etherpad19:15
jeblairwhat is that branch for?19:15
zaroohh, gerrit is now at ver 2.8.4 release.  but more changes were added to the stable-2.8 branch.19:15
clarkbjeblair: its so that we didn't have to put upstream commits atop our commits19:15
*** zdiN0bot has quit IRC19:16
clarkbjeblair: so that our fork sits nicely atop upstream instead of being mixed in19:16
jeblairclarkb: okay, so there's an upstream/stable-2.8 branch19:16
jeblairthat should have whatever is, well, upstream.19:16
jeblairusually what we do is build our version on top of releases19:16
jeblairso we'd branch openstack/2.8.4 from the 2.8.4 tag, then propose our modifications on top of it19:17
*** chandan_kumar has quit IRC19:17
zarook, that wfm19:17
*** eglynn has quit IRC19:18
jeblairi think zaro is asking that we somehow do a force push to the openstack/2.8 branch, which seems to already have some commits in it19:18
clarkbI interpreted that as making the 2.8.4 branch19:18
zaroi think in this case we should just git rid of openstack/2.8 ?19:19
*** IlyaE has joined #openstack-meeting19:19
*** dprince has joined #openstack-meeting19:19
zaromake openstack/2.8.4 instead?19:19
jeblairzaro: do we need anything in upstream/2.8 that is past 2.8.4?19:19
*** mfisch has left #openstack-meeting19:20
zaroi assume you mean upstream stable-2.8 ?19:20
jeblairyeah sorry19:20
jeblairhttp://git.openstack.org/cgit/openstack-infra/gerrit/log/?h=upstream%2Fstable-2.819:20
zarothere seems to be a major fix with secondary indexing.19:21
*** eglynn has joined #openstack-meeting19:21
*** gokrokve has joined #openstack-meeting19:21
jeblairokay, how about we branch openstack/2.8.4 from upstream/stable-2.8 so we get all of that19:22
zarodeadlocks in subIndex or something.19:22
jeblairzaro, clarkb: ^ make sense?19:22
clarkbyup19:22
zarowfm19:23
jeblairzaro: then you can propose the local changes on top of that19:23
*** rbowen has joined #openstack-meeting19:23
jeblair#action clarkb make openstack/2.8.4 gerrit branch19:23
zarook.19:23
jeblairokay, let's get excited about docs now! :)19:23
*** nati_ueno has joined #openstack-meeting19:23
jeblairsweston: you volunteered to write up some docs for developers about the changes; any progress?19:23
*** rbowen has quit IRC19:24
swestonjeblair: yes, but I need to dot some i's and cross some t's first.19:25
jeblairi think what we need is something highlighting the major differences.  for example:19:25
jeblair'important changes' view is going away -- how to make an equivalent custom dashboard19:25
jeblairworkinprogress button is going away, how to use the workflow label instead19:25
jeblairnote that the approval label is changing to workflow (but the value +1=approved is the same, and the approval process in general is the same)19:26
jeblairi'd like to send something out with a reminder announcement asap (ideally, today), even if it's brief19:26
jeblairbecause i don't want to tell 2000 developers after the fact that, btw, we changed your workflow.19:26
*** Mandell has quit IRC19:26
zarothere are also some changes to permission, like stream events are no longer available to all registered users.19:27
swestonjeblair: okay, let me spend some time on it then .. I do have some other code I am trying to get merged into Neutron, so that is taking up quite a bit of my time as well.19:27
*** akuznetsov has joined #openstack-meeting19:27
clarkbzaro: we can preserve the old behavior though and hopeflly people won't notice the difference19:27
hashar( for important changes maybe consider a per user version of http://status.openstack.org/reviews/ )19:27
anteayasweston: do you have your notes on an etherpad?19:27
anteayasweston: then we can refine what you have created thus far?19:28
jeblairclarkb: zaro: yeah, we should set permissions correctly so that does not change19:28
swestonanteaya: no, but I can put them out there tomorrow, if that is okay for everyone?19:28
anteayasweston: jeblair said he would like to send something out today19:28
anteayacan I help you get them on an etherpad today?19:29
jeblairit's < 1 week out and we basically haven't told developers anything about this, so i'm going to write up a followup reminder announcement and let people know about the changes19:29
swestonanteaya: yup!19:29
*** jlibosva has quit IRC19:29
anteayasweston: great thanks19:29
jeblairwe can continue to work on getting sweston's documentation in shape and point to it when ready19:29
swestonanteaya: absolutely19:30
swestonjeblair: sounds good19:30
*** vjay has quit IRC19:30
jeblairclarkb: did you ever send out something about changing the ssh keys for heartbleed?19:30
anteayaare we all caught up on heartbleed?19:30
clarkbI did not...19:30
*** akuznetsov has quit IRC19:31
clarkbjeblair: you had mentioned that it wasn't worth sending a note at the time19:31
clarkba general note at least19:31
jeblairokay.  we will do that during the gerrit upgrade as well and we'll do it then19:31
clarkbmaybe I misinterpreted what that meant about ssh keys19:31
clarkbok sounds good19:31
mordredo/19:31
anteayahey19:31
jeblairclarkb: i don't think i ever would suggest that we should change the ssh keys without telling anyone.19:31
anteayalook who it is19:31
mordredsorry I'm late. no, I did not get to the upgrade19:31
clarkbjeblair: you didn't. Just that I shouldn't send the note last monday19:31
clarkbwhere I interpreted the note to be generic thing + keys19:32
jeblairclarkb: i feel certain something was misinterpreted.19:32
clarkbya probably was19:32
jeblairbut anyway, we will change the ssh keys on monday and my reminder announcement today will include that19:32
clarkbgreat thanks19:32
*** shakamunyi has quit IRC19:33
jeblairclarkb, zaro: let's try to get our patches on 2.8.4++ running on review-dev today19:33
clarkbyup going to cut branch after meeting then go grab lunch19:33
jeblaircool19:33
jeblairanything else on the gerrit upgrade?19:34
*** jrodom has joined #openstack-meeting19:34
*** _nadya_ has quit IRC19:34
jeblair#topic  manage-projects status (mordred)19:34
*** openstack changes topic to "manage-projects status (mordred) (Meeting topic: infra)"19:34
jeblairmordred: what's the news?19:35
mordredmanage-projects works again19:35
mordredand is live19:35
*** _nadya_ has joined #openstack-meeting19:35
mordredso landing new projects changes should work19:35
anteayayou said you were going to switch it off to test something last night19:35
anteayayou turned it back on then19:35
mordredyes - I was testing a few quick and dirty ways to decrease the run-time, but they didn't help19:35
mordredso I gave up on them19:35
anteayak19:35
anteayano data from your tests?19:36
*** shakamunyi has joined #openstack-meeting19:36
mordredit takes 10 minutes ish to run manage-projects as is,19:36
mordredwhcih means it can complete before the next puppet run19:36
*** mrodden has quit IRC19:36
mordredif we remove the github chatter, it can be about twice as fast - but we'd be losing features19:37
mordredso I think the next step is just continuing to refactor some of the different thigns (like upstream tracking) into disconnected processes19:37
mordredbut that's not urgent19:37
mordredmanage-projects is NOT running on cron19:38
mordredonly on projects.yaml change19:38
mordredso we're only getting upstream tracking when we add projects19:38
mordredthis is the main motivation behind splitting out upstream tracking19:38
*** IlyaE has quit IRC19:38
* anteaya makes a note to look at the sections of code that handle upstream tracking19:39
*** eglynn_ has joined #openstack-meeting19:39
mordredthat's all Iv'e got - questions?19:39
*** Mandell has joined #openstack-meeting19:39
anteayathanks for fixing it19:39
*** eglynn has quit IRC19:40
clarkbmordred: no questions19:40
jeblair#topic Open Discussion19:40
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:40
jeblairnibalizer: any progress on the lp->storyboard script?19:41
jeblairi think it would be nice to move zuul bugs over19:41
clarkbI will be AFK next week. And plan to get red hat tripleo CI cloud added to nodepool this afternoon19:41
anteayaenjoy hawaii19:41
*** ramashri has quit IRC19:42
jeblairanteaya: there are only 4 open jeepyb bugs19:42
jeblairanteaya: https://bugs.launchpad.net/openstack-ci?field.searchtext=jeepyb&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=19:42
jeblairanteaya: i was thinking we should file a story on 'separate upstream tracking' for jeepyb19:42
SergeyLukjanovclarkb, have a good vacation!19:42
jeblairmaybe we should just move those 4 bugs over19:42
_nadya_hi folks! I'd like to ask about status of fedora20 on gating. In Ceilometer we would like to move py27 jobs from ubuntu12 to fedora20. Because fedora20 has new mongo. As far as I understand #link https://review.openstack.org/#/c/86842/ needs to be merged to create testing job. Are there any concerns about this change?19:43
jeblairclarkb: yes, enjoy!19:43
anteayaI have no objections19:43
*** rakhmerov has joined #openstack-meeting19:43
anteayait would be good to test them on storyboard, I agree19:43
clarkb_nadya_: yes, we cannot gate on F20 as is19:43
pleia2oh yes, I'm leaving on Friday and have a few days off and then LOPSA-East next week, then the following Monday and Tuesday I have the Open Source Business Conference19:43
clarkb_nadya_: you can definitely test on F20 when we get it in, but it won't replace the ubuntu tests19:43
anteayapleia2: safe travels to you too19:43
pleia2anteaya: thanks :)19:43
SergeyLukjanovoh, I have a small notice too - I'll be in CA starting from May 3 (and traveling day before)19:44
_nadya_clarkb: where can I find the reasons :)?19:44
mordredSergeyLukjanov: beer!19:44
anteayaSergeyLukjanov: awesome19:44
clarkb_nadya_: because we don't have redundant providers for F20 images19:44
anteayaI will be at home next week, on my computer and hopefully not bailing my basement19:44
clarkbif someone teach nodepool to use DIB we can change that19:44
*** emagana has quit IRC19:45
_nadya_clarkb: maybe ubuntu14 will be available soon? And it will be easier then enabling fedora20. What's the plan about it?19:45
jeblairi don't think we can run ceilometer jobs on f20 until it's available everywhere19:46
nibalizerjeblair: no, still unable to reproduce a running storyboard19:46
nibalizermordred: and i beat on it again last night and couldn't figure it out19:46
nibalizer:( maybe someone more familiar with storyboard should take this over19:46
clarkb_nadya_: we currently have the same issue with trusty that we have with F2019:46
* mordred is going to try to connect with nibalizer later today and figure out why it's not working for him19:46
clarkb_nadya_: not all of our cloud providers have images yet, so we need a way to provide our own images or wait for the providers19:46
anteayanibalizer: I have faith in you19:46
*** alexpilotti has quit IRC19:46
nibalizeranteaya: woooooo19:47
anteaya:D19:47
nibalizermordred: lets tag team it!19:47
SergeyLukjanovI think that I saw f20 images in rackspace cloud19:47
jeblairmordred: are you still working on nodepool dib?19:47
clarkbSergeyLukjanov: yup rax has f20 and trusty19:47
pleia2SergeyLukjanov: yeah, rackspace has them but not hp19:47
*** rakhmerov has quit IRC19:47
*** emagana has joined #openstack-meeting19:48
*** jrodom has quit IRC19:48
mordredjeblair: yes. that, I believe, is my current top priority, other than helping nibalizer and testing gerrit upgrade (sorry, lost that one last week, my bad)19:48
SergeyLukjanovoh, got it19:48
eglynn_is it the voting status of the job that requires redundant image providers?19:48
_nadya_clarkb:  sounds sad... and no estimates? Or somebody works on it?19:48
jeblairmordred: sweston has volunteered to test gerrit upgrade19:48
mordredjeblair: woot19:48
eglynn_(re. f20 and/or trusty gating_19:48
eglynn_)19:48
mordredthen I will double down on dib nodepool19:48
clarkb_nadya_: no estimate for when our providers will have images up19:49
clarkb_nadya_: mordred may have an estimate on DIB for nodepool19:49
clarkbor anyone else can give one and do the work19:49
eglynn_clarkb: would a non-voting job be equally objectionable?19:49
mordredit's not TOO far off - the main parts for the first stab are mostly in place19:49
jeblaireglynn_: we can't run jobs in either check or gate queues (regardless of voting status) if the node it runs on isn't HA19:49
eglynn_clarkb: (if the image was only available on a single provider)19:49
mordredI need to test and slightly rework the elements19:49
jeblaireglynn_: because that would block changes equally if there were a problem with that provider19:50
mordredand then hand off to jeblair for help with making sure the image upload step works right19:50
eglynn_jeblair: a-ha, I see, because even non-voting jobs have to complete?19:50
jeblaireglynn_: yep19:50
eglynn_k, thanks for the clarification19:50
eglynn_... so would it be possible to push HP to upload said image?19:51
jeblairnp.  we definitely want these running asap19:51
*** alexpilotti has joined #openstack-meeting19:51
*** mrodden has joined #openstack-meeting19:51
*** emagana has quit IRC19:52
*** igormarnat_ has joined #openstack-meeting19:52
pleia2eglynn_: I'm sure they're working as quickly as possible for at least trusty, it usually just takes a few weeks19:52
jeblairi don't know.  i'd honestly rather we put our efforts into dib for nodepool; then we can potentially use the same image across providers19:53
clarkb++19:53
mordred++19:53
pleia2yeah, that would be great19:53
jeblairwhich will mean much less work and much more consistency in tests19:53
clarkband avoid a lot of problems with image building that we currently have19:53
mordredit's not far off - I think I can get it done this week19:53
eglynn_pleia2: cool enough, it would be great to see f20 there also19:53
mordredit just needs finishing and testing19:53
*** joesavak has joined #openstack-meeting19:53
mordredI'll try to get it asap to a point where other people can also test19:53
clarkbalso I think we have somewhat agreed that we would just drop tests run on F20 when it goes out of support19:54
jeblairmordred: great, thanks19:54
clarkbthat isn't concrete but is the current train of thought19:54
clarkbso you don't really want to replace tests that don't have other coverage when using F2019:54
eglynn_we've had long-running issues with the ceilometer gate being hobbled because of the lack of a mongo package newer than the ancient 2.0.4 available on precise19:54
SergeyLukjanovdib and nodepool, sounds awesome19:54
*** bcrochet has joined #openstack-meeting19:54
jeblairclarkb: yeah; that's why everything at least needs to run on lts19:54
pleia2clarkb: yeah19:54
sdaguehas anyone considered dib as part of projects we gate on? Because there is a use case for building heat capable images as well19:54
jeblaireglynn_: fortunately, juno can test on trusty19:54
*** mwagner_lap has quit IRC19:55
_nadya_eglynn_: maybe we should think about ubuntu14 mostly, not f20?19:55
*** markmcclain has quit IRC19:55
pleia2for reference, the in-progress-ish dib in nodepool patch from mordred: https://review.openstack.org/#/c/88479/19:55
eglynn__nadya_: if trusty nodes are available soon, then yes ... main goal is for mongo to be testable19:55
jeblairsdague: afaik it's doable, people have mentioned doing that, no one has done it.19:55
pleia2(I thought I remembered this from my reviews :))19:55
*** SlickNik has joined #openstack-meeting19:56
SergeyLukjanovfyi climate new name (blazar) has been approved by foundation, so, folks want to rename someday too19:56
eglynn_... but would be great to have more OS distro choices in the gate to avoid such issues in the future19:56
sdagueI feel like there was resistance to dib getting commit gated before, if that's changed, it would make some things easier19:56
jeblaireglynn_: so we don't decide the distro support policy for the project19:56
jeblaireglynn_: the tc does that -- we try to support that19:57
*** Leonr has joined #openstack-meeting19:57
mordredsdague: I think we weren't gating gating it before due to consumption in the gate being primarily via pip releases19:57
eglynn_jeblair: a-ha, I see, thanks for the clarification19:57
sdaguemordred: yeh, well pip doesn't work with it, heat's been stalled on that for 5 months19:57
mordredhowever, I think we very well may want to revisit that :)19:58
mordredsdague: ++19:58
*** markmc has joined #openstack-meeting19:58
jeblairthe current policy is to support latest ubuntu and fedora, and don't break rhel and ubuntu lts; that leaves us with a baseline of only rhel and lts being supported for the life of our releases, so the bulk of our testing is there19:58
mordredyah. but with the door open to adding backport repos, such as the UCA repos19:58
mordred(which is how we pull in stuff from latest ubuntu)19:58
jeblaireglynn_: we can do additional testing on fedora and ubuntu latest, but basic functionality really ought to be done in the context of one of the long-term distros19:58
*** otherwiseguy has joined #openstack-meeting19:59
clarkbmordred: well we don't do that19:59
clarkbmordred: we have attempted it but it never worked19:59
mordredclarkb: right. I said door open to19:59
jeblairmordred: yeah, everytime we try to do that it fails19:59
mordredfrom a policy perspective19:59
jeblairmordred: indeed19:59
*** zehicle_at_dell has joined #openstack-meeting20:00
*** jlibosva has joined #openstack-meeting20:00
jeblairoh look at the time20:00
jeblairthanks everyone!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Apr 22 20:00:29 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-22-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-22-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-22-19.01.log.html20:00
*** jcoufal has quit IRC20:01
ttxAnyone here for the TC meeting ?20:01
sdague\o/20:01
markmchey20:01
zehicle_at_dello/20:02
mesteryo/20:02
dhellmanno/20:02
ttxrussellb, annegentle, mikal, mordred, jgriffith, vishy, markmcclain, jeblair, lifeless, dhellmann : around ?20:02
mikalHi20:02
mordredo/20:02
SlickNiko/20:02
annegentleholla20:02
ttxthat makes quorum20:02
russellbo/20:02
dhellmannttx: markmcclain is on his way (irc issues)20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Apr 22 20:02:39 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
jeblairo/20:02
ttxSo... This time it's *really* the last TC meeting for the Icehouse membership :)20:02
hub_caplies ;)20:02
ttxOur agenda for today:20:03
mordredttx: you say that every week20:03
*** derekh has quit IRC20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
*** markmcclain has joined #openstack-meeting20:03
mikalHeh20:03
markmcclaino/20:03
ttxthis time I MEAN IT20:03
ttx#topic Integrated projects and new requirements: Review Neutron plan to cover gap20:03
*** openstack changes topic to "Integrated projects and new requirements: Review Neutron plan to cover gap (Meeting topic: tc)"20:03
ttxSo... One month ago we went through the gap analysis for Neutron20:03
ttx(compared to current integration requirements)20:04
ttxThis was documented at:20:04
ttx#link https://etherpad.openstack.org/p/neutron-nova-parity20:04
ttxNow we need to have a clear plan to address those gaps during the Juno cycle20:04
*** eddie_ has joined #openstack-meeting20:04
ttxSince it's been a few cycles that we are talking about closing the gap, we need a detailed plan with actionable deadlines that the TC can check20:04
*** jlibosva has quit IRC20:04
*** _nadya_ has quit IRC20:05
ttxmestery: hi!20:05
mesteryttx: hi!20:05
devanandaso o/20:05
mesterymarkmcclain and I both going to talk about this.20:05
mestery#link https://etherpad.openstack.org/p/neutron-nova-parity-gap-analysis-coverage-plan20:05
ttxI know markmcclain had been working with neutron-core on getting a plan together20:05
* ttx reads20:05
mesteryttx: yes20:05
*** bcrochet has left #openstack-meeting20:05
mesterymarkmcclain and I spent some time coming up with this plan for Juno.20:05
*** asselin has quit IRC20:06
sdaguemestery: I feel like the db migration issue is a big enough deal that it probably warrants it's own called out it20:06
sdagueitem20:06
*** TravT has joined #openstack-meeting20:07
mesterysdague: I agree, I will rework this to include that as it's own issue here. Thanks for bringing that up!20:07
dhellmannare you talking about a different issue than the one on line 12?20:07
russellbwith tempest, it's not just missing test cases, right?20:07
*** IlyaE has joined #openstack-meeting20:07
sdagueand in reality #3 is going to come after a lot of the rest is done, because we don't want to make the defaults for people in devstack regress20:08
mesterydhellmann: The one on line 12 is a symptom of the actual issue.20:08
sdaguedhellmann: no, it's the same issue, but it's a big architectural issue20:08
ttxmestery: do you think you could set a milestone target for each of those ? juno-1, juno-2, juno-3 ? They will be roughly the 3 thirds of the cycle20:08
mesteryrussellb: The initial gap was around missing tests, but expanded coverage there and in functional testing is also important.20:08
lifelesso20:08
markmc"Neutron Replacement for Multi-Host Functionality - OVS will be minimum requirement"20:08
lifelesso/ - doing breakfast for the family but msotly here20:09
russellbnot just missing tests, but not running all of the existing tests20:09
dhellmannsdague, mestery : ok, I think you're agreeing and that I understand20:09
mesteryttx: Yes, that makes sense.20:09
markmcnova-network parity will require Open vSwitch? that's a bit of a head-scratcher20:09
russellbmarkmc: true, not exactly parity20:09
ttx(juno-1 mid-June, juno-2 second half of July, juno-3 start of September)20:09
*** igormarnat_ has quit IRC20:09
mesteryThe DVR solution being developed to close the multi-host gap is targeted at OVS right now.20:10
mesteryDVR=Distributed Virtual Router (FYI)20:10
sdagueon the tempest front, I haven't looked recently, but the gaps are really pretty small20:10
russellbsdague: cool.20:10
ttxthat would give a general indication of how late in the cycle each of those are expected, and give us sync points to see if anything is going over20:10
mesterysdague: That's thanks to the great work of mlavalle and team!20:10
russellbttx: yes, that'd be nice20:10
sdaguerussellb: yeh, a lot of work done in icehouse to close that20:10
russellband i really can't emphasize how important i think actually closing all of these gaps is ...20:10
russellbor else we really need to re-evaluate neutron's status in openstack20:10
markmcclainsdague: right we should be able to enable the full job voting right about.. salv-orlando was working on that20:11
sdaguemestery: so there is no way to do something as simple as the existing bridge model in n-net? ovs does seem like a big requirement jump.20:11
mesteryrussellb: Absolutely. It's neutron's top priority in Juno.20:11
markmcclainso for gaps 1,2,4,5 anticipate Juno-120:11
russellbi think enabling the full job, and it running successfully / stable, should be listed explicitly20:11
ttxadding milestones to the plan20:11
markmcclainfor 3,6,7 anticipate J-220:11
markmcclainrussellb: ok will update plan20:12
markmcclainI think we forgot to share that I'll be point of contact leading the parity effort for Juno20:12
mesterysdague: The ML2 plugin does support LB, but the work to do DVR is all based on OVS at the moment.20:12
mesteryYes, thanks markmcclain for volunteering for that!20:13
ttxI think (2) needs to be completed by j-2 if we want it to be useful for release work20:13
sdaguemestery: right, but if we are talking about a migration path from existing n-net, it feels like that should support the existing model. Otherwise it's not much of a migration path.20:13
markmcclainttx: agreed20:13
markmcclainI hedged a bit because the migration issue right now20:13
russellbso the OVS requirement ... this may be more of a nova question, but I guess that doesn't cover everything you can do with nova-network today20:14
russellbI'd like to see that explicitly discussed with the nova team20:14
markmcclainrussellb: it should20:14
markmcclainOVS just makes it easier to do a few things on the control plane20:14
mesteryrussellb: OK, I agree, a wider discussion is good there.20:14
ttxmestery: I added milestones to the etherpad, you should check them. No idea for (4)20:14
sdagueis there a design summit session that it fits into?20:14
jeblairis neutron in icehouse at a sufficient point that it can be used as a base for a grenade upgrade test to juno?20:14
mikalI can see adding OVS to existing deploys making upgrades a lot more complicated20:14
russellbas in, is nova willing to deprecate/remove nova-network, even if neutron *requires* OVS, when nova-network did not (to get the same features)20:14
mesteryttx: Someone beat me to it :)20:15
*** nibalizer has left #openstack-meeting20:15
mikalIf there's no appropriate summit session we can make one, right?20:15
ttxmestery: ok, sounds all optimistic but then juno-3 is pretty light so we can cover any missed target20:15
mesterymikal: We have a DVR session, it woudl be good to discuss it there20:15
*** zhhuabj has quit IRC20:15
mikalmestery: what days do neutron run on? Nova is a three day thing, so if its up against a nova thing that's hard20:16
mesteryttx: Yes, exactly!20:16
markmcclainthis is problem we've encountered multiple times already20:16
jeblairor will closing the grenade gap involve work on stable/icehouse and juno-master?20:16
mesterymikal: Neutron is Wed, part of thur, part of Friday20:16
markmcclainthe requirements keep changing a bit20:16
sdaguejeblair: grenade neutron jobs don't work today, due to the issue around neutron migrations20:16
*** andreaf_ has joined #openstack-meeting20:16
mikalmestery: yeah, we directly clash20:16
*** zhhuabj has joined #openstack-meeting20:16
mikalmestery: unless we shut down the nova stream for a session to walk over there20:16
russellbdo a session in the nova track, while neutron is off20:16
mikalmestery: which I think this is important enough to do20:16
russellbneutron isn't the whole time20:16
mesterymikal: Lets work together to find an appropriate slot.20:17
ttxmikal: or find an orthogonal topic to discuss in Nova while this is running20:17
mesteryrussellb: +1 to that!20:17
russellbor what ttx said20:17
mikalYeah, we could for example have a sesison Thursday arvo20:17
ttxmikal: you need to work on your cloning strategy20:17
mikalI will start a mail thread20:17
mesterymikal: Thanks!20:17
mikalttx: and my napping strategy20:17
*** emagana has joined #openstack-meeting20:17
russellbmikal: enjoy :-p20:17
markmcclainso the OVS thing is new… this was on the original etherpad from a month ago20:18
mikalrussellb: :P20:18
markmcclainwhy is it now a problem?20:18
russellbit's not the TC's call IMO20:18
russellbi just want to make sure the nova crowd is OK with it20:18
mikalI worry about deploys who can't do OVS for some reason20:19
markmcmarkmcclain, only just noticed now, I guess20:19
russellbTC requirement is that nova is OK with deprecating/removing nova-network20:19
*** andreaf_ has quit IRC20:19
ttxyes, the TC cares about the existence of a plan to cover the gap and the deadliens in it... not really the details of the plan20:19
sdaguemarkmcclain: some times these things come in layers, and things dont' get noticed when other thigns are in the way20:19
ttxwhich are more internal nova-neutron stuff20:19
markmcmarkmcclain, could wind up just being a question of explaining the need for the new req in simple terms20:19
*** andreaf_ has joined #openstack-meeting20:19
*** sballe_ has joined #openstack-meeting20:19
sdaguewe also need to play for a migration grenade job20:19
sdagueicehouse n-net -> juno neutron20:19
russellbyeah, could be fine ... but better have it written out very explicitly on list now, than debate it late juno, when the stakes are higher20:20
mesterysdague: Yes, agreed, I think that will be critical as well.20:20
*** andreaf has quit IRC20:20
dhellmannrussellb: ++20:20
sdagueand that's going to demonstrate some of the challenges in the hop that not one has noticed yet20:20
jeblairsdague: in addition to or instead of icehouse neutron -> juno neutron?20:20
sdaguejeblair: yes20:20
sdaguein addition20:20
markmcclainsdague: yeah agree a grenade update might make sense20:20
russellbsdague: ooh, that's a cool idea20:20
ttxsdague: should we add db migration as its own gap (like Gap 0) so that the plan is complete and can be blessed by the TC today ?20:21
sdagueI think for whenever we are deciding that "now is when we expect people to move" we should demonstrate that we can do it20:21
mordredsdague: ++20:21
russellbi like that20:21
sdaguettx: yes, I think we should call that out20:21
ttxsdague: care to word it out and add it as Gap 0 ?20:21
ttxmestery: check that you agree with sdague's gap 020:22
*** emagana has quit IRC20:22
* mestery waits for sdague to finish typing20:22
jeblairi've added a note on gap2 about the 2 grenade tests20:22
russellbjeblair: ++20:23
*** sballe has quit IRC20:23
markmcclainjeblair: so which grenade tests nova-net to neutron should be validated?20:23
ttxmarkmcclain: is j-2 still reasonable given the two goals on grenade test ?20:23
sdaguemestery: ok, I'll let you propose solution20:23
russellbalso, which nova-net modes for grenade?20:23
markmcclainttx: yes depending on what matrix of testing is desired20:23
russellbjust one?  all of them?20:24
russellbmarkmcclain: yes, that :)20:24
mesterysdague: Thanks! Really, we need to discuss this one a bit more as a neutron team with input from the broader community I think.20:24
sdaguerussellb: we have to pick on20:24
mesterysdague: We've discussed a bit on ML and on the bug so far, FYI.20:24
sdaguepick one, we don't test *every* mode20:24
sdaguemestery: yep, just want that called out as needed to be solved20:24
mesterysdague: agreed20:24
mesterysdague: I'll mark myself as owner for now on this one.20:25
annegentlerussellb: is a mode like flat/flatdhcp?20:25
*** TravT has quit IRC20:25
markmcclainannegentle: yes20:25
markmcthis gap 0 is in https://etherpad.openstack.org/p/neutron-nova-parity ?20:25
annegentlek thanks20:25
ttxGot a design summit session about that grenade testing ?20:25
mesterymarkmc: It fell out of #2 there.20:25
sdaguemarkmc: not that I know of, it was only recently uncovered20:25
sdaguettx: there is a grenade general session in qa track20:25
mesteryttx: We have a general testing session right now, not a grenade specific one at the moment. But good point.20:25
sdaguehttp://summit.openstack.org/cfp/details/38120:26
ttxsdague: maybe we should make sure it doesn't happen during Neutron slots20:26
mesteryttx: +120:26
ttxsdague: topic for next meeting20:26
*** mdenny has joined #openstack-meeting20:26
sdaguettx: sure20:26
*** _nadya_ has joined #openstack-meeting20:27
ttxOK, I think this looks good20:27
ttxMore comments ?20:28
*** pablosan is now known as zz_pablosan20:28
ttxi propose that the next TC reviews progress on that at every milestone20:28
markmcclainttx: +120:28
russellb+120:28
mikalSounds good to me20:28
jeblair++20:28
ttxmaking sure we are still on track20:28
mordred++20:28
dhellmann+120:29
ttxmestery, markmcclain: nice work on the plan20:29
ttxSlickNik, hub_cap: around ?20:29
SlickNikhere20:29
mesterythanks ttx!20:29
ttx#topic Integrated projects and new requirements: Review Trove plan to cover gap20:29
*** openstack changes topic to "Integrated projects and new requirements: Review Trove plan to cover gap (Meeting topic: tc)"20:29
SlickNik#link https://etherpad.openstack.org/p/TroveIntegratedGapPlan20:29
*** vhoward has left #openstack-meeting20:29
ttxAt the meeting last week we went through Trove's gaps there ^20:29
ttx#link https://etherpad.openstack.org/p/TroveIntegrationRequirements20:29
* ttx reads again20:30
*** zz_pablosan is now known as pablosan20:30
*** ramashri has joined #openstack-meeting20:30
*** tongli has quit IRC20:30
SlickNikwhoops, sorry ttx posted the plan before you posted the gaps.20:30
*** julim has quit IRC20:30
ttxI'm so predictable20:30
mordredSlickNik: so, it just came to my attention that trove only supports nova-network - given the previous discussion, is this something that needs to be called out for this cycle and tracked?20:30
SlickNikmordred: We're already working on this and it's a top priority for Juno.20:31
ttxmordred: ha?20:31
mordredSlickNik: yes - I've just heard that as well - thought I'd bring it up here because I'm guessing none of us thought to ask if you supported neutron20:32
mordredI know I didn't20:32
lifelessttx: its due to the neutron namespaced network feature20:32
SlickNikmordred: It's complicated. There is limited support, but no tests around it.20:32
* ttx wonders why Trove cares, but hides his ignorance behind silence20:32
russellbmordred: good point, sounds like something that should be tracked specifically20:32
* lifeless knew20:32
ttxlifeless: ah.20:32
*** assef has quit IRC20:32
SlickNikmordred: And I'm of the view that if it's not tested, we can't claim to support it.20:32
sdaguettx: because trove manages provisioning as well20:32
mordredSlickNik: I agree with that view20:32
mordred:)20:32
sdagueSlickNik: that seems big enough to call out as a separate item20:32
russellbyep20:33
SlickNikmordred: So we're adding tests, and have found a couple of issues as part of it already.20:33
ttxyes, we missed it during the gap analysis, obviously20:33
SlickNik++ to calling it out officially in the gap and plan.20:33
ttxmordred: care to add it as Concern #5 ?20:33
mordredttx: sure20:33
*** eddie_ has quit IRC20:33
*** bruff has left #openstack-meeting20:34
SlickNikI can fill in the actions20:34
SlickNikbut basically - 1. we're adding tests for provisioning with neutron ports / networks20:35
russellbtests in tempest?20:35
ttxSlickNik: could you fill target milestones in the document ? i.e. the rough dates you expect that work to bne completed (juno-1, juno-2, juno-3 ?)20:36
SlickNikrussellb: Tests in our functional test system (rdjenkins) for now since the tempest effort is going on in parallel.20:36
ttx(juno-1 mid-June, juno-2 second half of July, juno-3 start of September)20:36
mordredif we have trove enabled in all of the d-g jobs, then shouldn't we pick up coverage of the different modes since e have nova-network config and neutron-config - as long as there are tests which exercise things/20:36
*** Mandell has quit IRC20:37
*** _nadya_ has quit IRC20:37
SlickNikrussellb: So there is some amount of work to ensure that tempest is also testing this.20:37
russellbSlickNik: OK.  I think for the gap to be considered filled, it should be in openstack-infra20:37
SlickNikrussellb: Yes, there is that overlap between #5 and #320:37
russellbyeah, noted20:37
SlickNikmordred: I think that's true. However the trove tempest coverage is pretty poor right now and we're working on getting that up.20:38
sdaguemordred: yes, but the trove tests are very minimal20:38
SlickNikttx: Will add the milestones20:38
mordredyup. I think 3 + 5 == happy bunnies20:39
ttxSlickNik: if you add them now we could bless the plan20:39
SlickNikAh, okay20:39
mordredannegentle: on point #2 - is that what we're doing with API docs now across the board?20:40
SlickNikttx, added20:40
ttxSlickNik: OK, looks optimistic, but I'll take those :)20:40
annegentlemordred: so long story, last summit we had a session where we said we wanted to move all <project>-api repos into a <project>/doc/api area20:40
annegentlemordred: that move never happened20:41
mordredannegentle: k. but it's desired by docs?20:41
*** phschwartz has left #openstack-meeting20:41
ttxPlan looks good to me -- other comments ?20:42
sdaguenope, lgtm20:42
annegentlemordred: ttx: wait I'm trying to understand where point #2 is spelled out?20:42
*** Mandell has joined #openstack-meeting20:42
* ttx wonders if we should move those plans somewhere less volatile, like a wiki page20:43
*** dougw has left #openstack-meeting20:43
dhellmannttx: it would be nice to have edit history20:43
mordredannegentle: concern #2: "    - Currently in the process of moving them over to the trove repository for better locality so it makes it easier to update"20:43
ttxdhellmann: right20:43
mikalttx: something more discoverable would be good20:43
russellbttx: could at least snapshot the etherpad20:43
dhellmannttx: also, these colors make my eyes cross :-)20:43
russellbso you get a record of its state when we discussed it20:44
*** rakhmerov has joined #openstack-meeting20:44
ttxmestery, SlickNik: do you mind if I copy those etherpads and make them wiki pages ? (tomorrow) ?20:44
annegentlemordred: ah. Yes the thinking is that the API specs are a place for devs to discuss changes to the API20:44
russellbwe could have this proposed to governance ...20:44
russellbmaybe that's too much20:44
*** IlyaE has quit IRC20:44
ttxrussellb: yeah, I think that would be a bit too much20:44
mesteryttx: That is fine by me, thanks!20:44
SlickNikttx: be my guest.20:44
russellbk20:44
annegentlemordred: ideally we'd get all projects to do API docs the same way, we had agreement last summit but the work didn't happen20:44
ttx#action ttx to move gap coverage plans somewhere discoverable on the wiki20:44
*** denis_makogon has quit IRC20:45
*** emagana has joined #openstack-meeting20:45
*** kgriffs|afk is now known as kgriffs20:46
ttxannegentle: does this have to be resolved for the plan to be blessed ?20:46
ttxor can it be discussed offline / at design summit ?20:46
*** dburmistrov_ has quit IRC20:46
annegentlettx: nope I'm fine with the plan20:46
SlickNikannegentle: So for #2, grapex is driving the effort and I'll work with him and you to make sure what we're thinking is good with the docs team.20:46
*** thangp has quit IRC20:46
*** zdiN0bot has joined #openstack-meeting20:47
ttxOK, so we'll do the same as for Neutron, review progress on the plan at every milestone20:47
annegentlegogo grapex20:47
*** hashar has quit IRC20:47
ttx#topic Incubation/integration requirements changes20:47
*** openstack changes topic to "Incubation/integration requirements changes (Meeting topic: tc)"20:47
ttx* Add upgrade expectations (https://review.openstack.org/87234)20:48
SlickNikSounds good. Thanks all!20:48
ttxThis looks good to me, will approve once it reaches the threshold20:48
russellbSlickNik: thanks, and good luck :)20:48
ttxSlickNik: thx!20:48
*** rakhmerov has quit IRC20:48
ttx* Add Ceilometer requirements (https://review.openstack.org/85978)20:48
ttxThere are a few objections to this one, in particular jog0 raises an interesting point...20:48
ttx... that such a requirement looks premature until Ceilometer is more extensively tested at the gate20:49
*** _TheDodd_ has quit IRC20:49
ttxDo you think that's a valid objection, or that it's an orthogonal concern ?20:49
markmcI think that's orthogonal20:49
russellb+120:49
markmcit's integrated now, we should require projects integrate with it20:49
markmcwhere it makes sense, of course20:49
sdagueI think we could generalize this whole section of "should use heat, should use horizon, should use ceilometer"20:49
dhellmannyeah, it's an integrated project -- we want more testing, but that shouldn't block other projects20:49
ttxOK. The wording still needs to be fixed anyway20:50
ttxso it's not really ready20:50
jeblairmarkmc, sdague, dhellmann: +120:50
dhellmannsdague: we did think about that, but there may be specific points of integration20:50
sdagueto something about "we expect projects to use integrated projects for the functions they provide"20:50
*** jmh_ has quit IRC20:50
ttxjust wanted to make sure we still wanted it on the drawing board$20:50
dhellmannsomeone also mentioned that having a checklist would help, rather than having to make that list each time we review a project20:51
*** TravT has joined #openstack-meeting20:51
russellbsdague: it goes the other way, too.  we expect the project to work with other projects to consume this one, where it makes sense.20:51
russellbor something like that20:51
sdaguerussellb: yep, sure20:51
russellbi think listing each project is still OK for now20:51
sdagueI just think we'd do ourselves a favor by making it more general, and not having every project push in a line for their projects20:51
russellbthe first case you mentioned is covered by "don't duplicate stuff"20:51
*** olaph has left #openstack-meeting20:52
devanandafwiw, i agree that general is better here, and require it to be identified when the project enters incubation20:52
ttxagree there is room for generalization. We'll see which change gets in first20:52
*** SridharG has quit IRC20:52
ttx#topic Minor governance changes20:52
*** openstack changes topic to "Minor governance changes (Meeting topic: tc)"20:52
ttx* Begin conversion to rst (https://review.openstack.org/87579)20:52
ttxThis one is moving the ball forward on doc publication, it's more a technical change than a policy change so I'll approve it after the meeting, unless someone objects (and posts a -1)20:53
*** megan_w is now known as megan_w|afk20:53
annegentlettx: do you need seven or eight +1s?20:53
ttxannegentle: no, i'll just abuse my power20:53
jgriffithI just gave the 8'th anyway :)20:53
ttxjgriffith: hah!20:53
annegentlettx: ha ha20:53
ttx* Add project mission statement for Ceilometer (https://review.openstack.org/87526)20:54
ttxThis one is still being disputed, so it might need a few more iterations20:54
ttx* Adds integrated and incubated release names to programs.yaml (https://review.openstack.org/81859)20:54
lifelessI've thrown a -1 up there20:54
*** jecarey has quit IRC20:54
lifelessfor the upgrade one20:54
ttxThere is good progress here... I think we settled on the format, so now it's just about getting the content right.20:54
ttxannegentle: you left out one of my suggestions... was it on purpose ?20:54
*** TravT has quit IRC20:55
annegentlettx: looking20:55
ttxI just -1ed your latest20:55
*** TravT has joined #openstack-meeting20:55
*** Mandell has quit IRC20:55
annegentlettx: ah I see, yeah just missed it. Though one Q I did have, does this doc record when the TC meeting occurred? (I thought that was one of the early inputs)20:56
*** radez is now known as radez_g0n320:56
ttxannegentle: for future entries it will record when the change was made...20:56
ttxbut that clearly doesn't work for old entries20:56
ttxannegentle: we can always add more keys to that dictionary over time20:57
annegentlettx: ok right.20:57
ttxlike incubated-in-tc-meeting: 2014-04-1020:57
ttxif we really want to track additional data20:58
ttx#topic Open discussion20:58
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:58
ttx* Joint BoD/TC meeting agenda20:58
ttxI worked with Alan on defining the content for the joint TC/BoD meeting in Atlanta.20:58
ttxMost of the items we proposed for discussion are present in the agenda draft I've seen20:58
ttxI think Alan shall post it really soon now, i'll make sure it's sent to openstack-tc as well20:58
ttx* TC elections: voting under way20:59
*** erecio has quit IRC20:59
ttxWe have elections under way, please encourage everyone to vote -- we actually need good participation scores if we want to lecture others on election systems :)20:59
ttxAnything else, anyone ?20:59
anteaya26% voter turnout so far20:59
annegentlevote vote vote!20:59
anteayatalk up voting20:59
*** nati_ueno has quit IRC20:59
markmcwow, is that all?20:59
anteayaso far21:00
russellbouch21:00
ttxWe had 31% last time21:00
anteayaI think easter weekend cut into it21:00
sdagueanteaya: when do polls close?21:00
sdaguewe do have > 1000 ATCs21:00
*** coreywright has quit IRC21:00
anteayaFriday when I wake up21:00
anteaya1510 atcs21:00
jeblairttx: i got the impression the board wasn't very interested in talking about the CLA21:00
anteayaafter 1300utc21:00
ttxjeblair: I asked that it is added to the agenda though.21:00
jeblairwhich is disappointing because i think we are interested, and we're seeing new issues come up21:00
*** epim has quit IRC21:00
*** coreywright has joined #openstack-meeting21:00
*** dfg has joined #openstack-meeting21:00
jeblairttx: okay good21:00
*** nati_ueno has joined #openstack-meeting21:00
*** jlibosva has joined #openstack-meeting21:00
ttxit's in the current agenda draft, fwiw21:00
ttxOK, time is up21:01
jeblairit's just reared its head again on the -legal list, based on two recent events21:01
ttxThanks everyone, been a privilege working with you all for this last cycle21:01
mordredI loved the "why can't they just sign the CLA, IBM has" response21:01
jeblairttx: seconded!21:01
annegentlettx: thanks for running efficient meetings :)21:01
mikalLovely typing near you all21:02
ttx#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Tue Apr 22 21:02:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-22-20.02.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-22-20.02.txt21:02
ttx(and ending them on time)21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-22-20.02.log.html21:02
*** manishg has quit IRC21:02
annegentlemikal: LOL21:02
russellbmordred: but ask them how long it takes to get added to their corporate CLA if you work there21:02
jgriffithso long TC21:02
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, kmestery, SlickNik, mtreinish, annegentle, jeblair, dtroyer, jraim, kgriffs, devananda, SergeyLukjanov, lifeless: around ?21:02
notmynamehere21:02
zanebmordred: yeah, that was completely a tone-deaf response21:02
dhellmanno/21:02
SergeyLukjanovo/21:02
kgriffsp/21:02
eglynn_o/21:02
dolphmo/21:02
devanandao/21:02
zanebo/21:02
lifelesso/21:02
mesteryo/21:03
jgriffith\o/21:03
jeblairo/21:03
mtreinisho/21:03
david-lyleo/21:03
*** ameade has joined #openstack-meeting21:03
ttx#startmeeting project21:03
mikalHi, but I am taking a quick bio break, back in a sec21:03
openstackMeeting started Tue Apr 22 21:03:16 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: project)"21:03
openstackThe meeting name has been set to 'project'21:03
*** markwash has joined #openstack-meeting21:03
ttxWe'll abuse this meeting today to discuss Juno Design Summit scheduling:21:03
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:03
ttx#topic Design Summit scheduling21:03
*** openstack changes topic to "Design Summit scheduling (Meeting topic: project)"21:03
ttxFirst, do you have questions on the review/scheduling interface ?21:03
ttxThe first step is to review sessions and set their status to Preapproved or Refused21:04
*** jdob has quit IRC21:04
ttxOnce that's done, you can use the scheduling screen to drag and drop sessions to available time slots21:04
ttxOne thing to keep in mind is that you can pre-approve more sessions than you have available slots, and then merge multiple sessions into the same schedule slot.21:04
*** BrianB__ has quit IRC21:04
zanebttx: no questions, but is there a wiki page about it? if not I might create one21:04
ttxzaneb: it has Help screens!21:05
zanebwould have been good to know some of that stuff earlier :)21:05
dolphmi'm not sure if it's a new feature or not, but i found it surprising this cycle that you could drag multiple proposals into the *same* timeslot to merge them21:05
*** jlibosva has quit IRC21:05
eglynn_one question, what's the typical over-subscription ratio?21:05
dolphmttx: i only picked up on it from your email21:05
ttxzaneb: feel free to document your experience :)21:05
eglynn_(i.e. proposals to available slots on track)21:05
*** jecarey has joined #openstack-meeting21:05
mesteryttx: The merging of proposals is quite awesome!21:05
*** manishg has joined #openstack-meeting21:05
devanandafwiw, ironic is subsribed 18:421:05
ttxeglynn_: here is the secret URL: http://summit.openstack.org/cfp/topicstatus21:05
*** vkmc has joined #openstack-meeting21:05
*** vkmc has joined #openstack-meeting21:05
annegentledevananda: dang21:06
*** adalbas has quit IRC21:06
ttxironic wins21:06
mikal.21:06
zanebttx, eglynn_: oooh. but rejected sessions are not shown on that21:06
eglynn_ttx: nice :)21:06
ttxfollowed closely by Sahara and Swift21:06
dolphmzaneb: i believe rejected sessions vanish21:06
zanebdolphm: correct21:06
ttxzaneb: yes, only works for so long21:06
*** ameade has quit IRC21:07
ttxit's more of a "reminder of the problem" type graph21:07
zanebeglynn_: heat was 2:1 oversubscribed fwiw21:07
ttxremainder?21:07
*** _nadya_ has joined #openstack-meeting21:07
*** glange has joined #openstack-meeting21:07
ttxDo you have sessions you would like to push to another topic ?21:07
*** glange has left #openstack-meeting21:07
ttxRemember you will all have a project pod where you can discuss overflow sessions21:08
devanandai've proposed a few sessions to other tracks (eg, for ceilometer and nova integration)21:08
ttxThis will be available all 4 days of the summit21:08
mikalttx: what's the deadline for scheduling?21:08
zaneb\o/21:08
dolphmmikal: aim for end of week?21:08
devanandagiven taht ironic would like to graduate, and that integration is now a pre-requirement, it'd be great to have those discussions some time :)21:08
ttxit's just a round table with a flipchart, but it will be a designated spot (with your program name on it) and there will be a map to help locate it21:09
mikalI was going to discuss it my meeting at the end of the weke, but have just realized I'll be on a plane during that meeting21:09
ttxmikal: goal is to have a basic proposal up at end of week21:09
ttxbut then we can tweak it until the last minute21:09
mikalttx: ok21:09
lifelessttx: I plan to put tripleos things in on monday21:09
ttxmikal: if we have "most" in by the end of week we'll be fine21:09
devanandattx: what tools will be available in the overflow pods? whiteboard? projector? also, how many ppl can effectively congregate there?21:09
lifelessttx: we're waiting on core team reviews of the proposals21:10
lifelessttx: is that ok ?21:10
ttxlifeless: that's good. Just won't be around to assist in case stuff falls apart21:10
*** jprovazn has quit IRC21:10
* ttx takes the off week off21:10
lifelessttx: long as we have our 6 slots we're fine :>21:10
eglynn_so what's the PTL "tribal knowledge" on the sense or o'wise of merging unrelated sessions?21:10
eglynn_(... just to shoehorn things into the available slots)21:10
mesteryI have an etherpad with the neutron schedule, working on pushing those into the tool now.21:10
lifelesseglynn_: its doable but not with contentious sessions21:10
lifelesseglynn_: try to have things that will attract the same audience21:11
eglynn_lifeless: fair point21:11
ttxeglynn_: well, previously we didn't have project pods, so the dynamic is slightly different this time21:11
lifelesseglynn_: otherwise you get lots of folk moving in and out21:11
dhellmanneglynn_: markmcclain did that with neutron a few times, you might want to ask him how well it went21:11
*** rockyg has quit IRC21:11
SlickNikttx: For trove, we're planning on going through the proposals tomorrow. I should have the schedule set by Friday.21:11
lifelesseglynn_: e.g. we're likel merging *ALL* our CI issues into one session21:11
eglynn_dhellmann: thanks will do21:11
ttxeglynn_: I would make sure you use your "scheduled" slots to reach out to people and identify the interested people21:11
dhellmanneglynn_: he says "you need to be a strict time keeper"21:11
lifelesseglynn_: which should let sdague drop in...21:11
eglynn_cool21:11
ttxeglynn_: then the project pod can be used to work, hackathon style21:11
devanandaeglynn_: merging 2 uncontested sessions with a fairly even split isn't bad. beyond that, i haven't see nit work well21:11
devanandaeglynn_: unless the topics are very similar to begin with21:12
ttxDoes anyone expect to have unused slots they could give to someone else ?21:12
dolphmttx: some session proposals would be better for project pods than design sessions - is there anything published about project pods that i can direct people to?21:12
*** Mandell has joined #openstack-meeting21:12
* eglynn_ rapidly cools on the idea ...21:12
*** jtomasek has quit IRC21:12
* devananda is also wondering what the pods will provide21:12
*** tjones has joined #openstack-meeting21:12
ttxeglynn_: last time, Glance and Horizon had extra slots they gave out.21:12
ttxdolphm: let me check21:13
zanebeglynn_: I'm planning to do a lot of merging, but only of related topics21:13
ttxhttps://wiki.openstack.org/wiki/Summit has a paragraph about pods21:13
SergeyLukjanovsahara schedule will be hopefully ready by the end of week, no unused slots already21:13
ttxdolphm: ^21:13
eglynn_ttx: all looking over-subscribed this time if I read those graphs right21:13
dolphmttx: thanks!21:13
ttxeglynn_: yes21:13
eglynn_(so alms for the poor looking unlikely)21:14
ttxeglynn_: less lots overall kinda does taht to you21:14
devanandattx: "round table" -- so not a reasonable place for the whole team to gather, then21:14
ttxdevananda: You can steal extra chairs and invade others space !21:14
kgriffsdevananda: that was my question too - do we have some sense of the actual number of seats / physical space?21:14
* ttx has no idea if this pod thing will work21:15
ttxkgriffs: let me look at the map I was given21:15
dolphmttx: not if you're stealing chairs!21:15
*** IlyaE has joined #openstack-meeting21:16
lifelessttx: 'spare slots' ahahahahahahahahahahahahahahahahaha21:16
notmynamettx: the concept of pods makes the 4:1 oversubscription somewhat more bearable. :-)21:16
ttxkgriffs: so.. the map says the roundtablaes are 66", whatever THAT means21:16
ttxThey drew 10 chairs around them21:17
dolphm9-10 people21:17
SlickNikSeats 9-1021:17
*** kevinconway has quit IRC21:17
markwash1.67 m21:17
kgriffsthat should work OK. If things get crazy we can steal more chairs. :p21:17
ttxyou can definitely invest the walls that are near to your table21:17
notmynamebut they are dark and don't support projectors well?21:17
ttxnotmyname: well, you saw the photo. haven't seen them in real21:18
*** ArthurBerezin has joined #openstack-meeting21:18
* ttx finds a link21:18
notmynamettx: ah, ok21:18
ttxhttp://www.gwcc.com/event_planners/Interactive_Planning_Guide.aspx > Click on Level 2 in building B21:19
*** fnaval has quit IRC21:19
*** ni291187 has joined #openstack-meeting21:19
*** tjones has left #openstack-meeting21:19
ttxpods will be in rooms B201 B202 B203 B20421:19
*** adalbas has joined #openstack-meeting21:19
ttxif you want to look what the rooms look like21:19
*** fnaval has joined #openstack-meeting21:19
ttxthere is a "photos" button21:20
*** ni291187 has left #openstack-meeting21:20
ttxafter you select a specific room21:20
*** gyee has joined #openstack-meeting21:20
eglynn_they look substantial enough21:20
ttxnow you know as much as I do.21:20
ttxI can forward questions if you have any21:20
ttxDo you have scheduling constraints or conflicts you would like to tell us about ?21:20
ttxlike a session where Nova folks need to have Neutron guys around21:21
mikalNo yet!21:21
* dolphm it doesn't bother me at all that they misspelled "ceiling" AND "height" in this tool in the same label21:21
ttxdolphm: not exactly reassuring21:21
mikalttx: there was a mail thread during the TC meeting about that. It looks like we can do it Thursday arvo21:21
dolphmttx: it's probably fine for banqets21:21
mtreinishmestery: you had a qa/neutron session on the neutron track right?21:21
ttxmikal: yep, that would fall in the space where no neutron is running21:22
markmcclaindolphm: you should know that GA education is dead last in the US21:22
*** yfried has joined #openstack-meeting21:22
markwashmarkmcclain: I think they prefer "first in opportunities to improve"21:22
mesterymtreinish: Yes: http://summit.openstack.org/cfp/details/366 and http://summit.openstack.org/cfp/details/40121:22
ttxmtreinish, jeblair, dhellmann : ideally we would publish our schedules soon, so that the others can plan around it21:22
jeblairttx: ack21:23
dhellmannttx: working on it21:23
mesteryttx: What happens if we accidentally press "push to sched" early? :)21:23
notmynameI've got one talk that should probably be moved to the cross-project session21:23
mtreinishmestery: oh they're multiplying, I only knew about the first one21:23
ttxi.e. a neutron QA session in the neutron track could try to avoid times where a QA session is running21:23
jeblairnotmyname: what is that?21:23
dhellmannnotmyname: I'm pretty sure the cross-project session is full21:23
mesterymtreinish: We're combining those ones for now, as they overlap a bit.21:23
sdaguemestery: you can redo it later21:23
mesterysdague: Thanks.21:23
mtreinishttx: should have it Thurs. I want to discuss it during the meeting this week before I schedule anything21:23
notmynamehttp://summit.openstack.org/cfp/details/192  <-- glance + swift + keystone21:24
ttxmestery: it will just push the current state of the schedule21:24
mesterysdauge: Not that I accidentally hit "push to sched" or anything. :)21:24
sdagueso pushing early isn't and issue21:24
mesterythanks ttx21:24
ttxnotmyname: checking how stuff aligns21:24
*** fnaval has quit IRC21:24
dhellmannnotmyname: we tried to keep the cross-project sessions to those affecting all (or at least most) projects, not just >121:24
ttxRemember slot layout lives at https://docs.google.com/spreadsheet/ccc?key=0AmUn0hzC1InKdGNXcWlWX0FIekQxbUtvRVlnVF9IV3c&usp=drive_web#gid=521:24
jeblairnotmyname: probably worth seeing if you can do that with a joint swift/glance/cinder session21:25
ttxnotmyname: as long as you avoid the first two slots of the swift track, you should have all of them21:25
sdagueyeh, I think a session like that we'd have kicked back to project tracks. Like the various neutron+nova things we kicked back out.21:25
ttxif you want cinder as well, that limits choices21:25
notmynamewell as one of 22 proposed for 8 slots, I'm not sure if it will get chosen anyway in the swift track21:25
jgriffithttx: notmyname we could possibly pu tit in Cinder21:25
ttxOh, an offer to take one slot!21:25
notmynamejgriffith: how generous of you :-)21:26
jgriffithnotmyname: I'd of course like to tweak the session a bit :)21:26
*** ivasev has quit IRC21:26
ttxjgriffith: Friday after 2:10pm you would have swift/glance and keystone folks available21:26
notmynamejgriffith: ya, makes sense21:27
jeblaireven more generous! ;)21:27
jgriffithttx: notmyname we can take it, I have been wanting to propose a glance/cinder21:27
notmynamejgriffith: cool, thanks!21:27
jgriffithttx: notmyname I think this counts and could be abstracted a bit21:27
ttxjeblair: anything you'd like to try to sneak in release management ? Or can I run with my canned 4 ?21:27
notmynamejgriffith: FWIW, Donagh is in Ireland, so keep aware of that when getting in touch with him21:28
jeblairttx: nope, thanks21:28
ttxjeblair: I have a release branch vs. QA vs. infra session filed in release management already21:29
ttxwhere we can also disucss requirements21:29
notmynamettx: are you the only one who can rehome a talk or can we do it?21:29
ttxnotmyname: no you can do it21:29
ttxon the review screen, click in the topic column (where it says Swift)21:29
devanandattx: i'd like to ask that http://summit.openstack.org/cfp/details/198 be scheduled tuesday morning (not overlapping ironic)21:29
*** dkranz has quit IRC21:29
ttxrussellb: ^21:30
devanandattx: of the cross project sessions taht i dont want to miss, it's probably the most important for ironic21:30
notmynamettx: ah, cool21:30
jeblairttx: yeah, i saw that.  ++.  i don't see anything overlapping that...21:30
notmynamejgriffith: moved. thanks21:30
jeblairmtreinish, ttx: do you have any thoughts on this session: http://summit.openstack.org/cfp/details/28521:30
jgriffithnotmyname: np21:30
ttxjeblair: I'm not 100% convinced we need a session for that21:31
mtreinishjeblair: yeah I'm not sure either, but I know we want to do it21:31
mtreinishit seems like it's more working through issues as they come up21:31
ttxdevananda: it's already scheduled at http://junodesignsummit.sched.org/ -- does it conflict ?21:31
* ttx checks21:32
dhellmanntuesday 5:30 pm21:32
ttxoh, it does21:32
devanandayep21:32
*** ni291187 has joined #openstack-meeting21:32
jeblairttx, mtreinish: that's kind of what i'm thinking.  let me know if you see a session we might be able to combine it with; otherwise, maybe hallway track or pod for that one.21:33
*** ni291187 has quit IRC21:33
sdaguettx: is it worth shuffling the incubated slots instead?21:33
ttxsdague: maybe21:33
devanandai will be delegating folks from ironic for the afternoon cross project sessions that we need to sync with, but where I dont need to be present21:33
sdaguelike switch marconi and ironic21:33
ttxdevananda: how about you swap with Marconi slots ?21:33
ttxkgriffs: would that work for you ?21:34
devanandathe morning cross proejct slots are not especially pertitnent to ironic21:34
kgriffsyep, I'm flexible21:34
devanandaconsistency across APIs would be nice to attend, but i dont think we'll have much input there21:34
ttxdevananda: looks like we have a winner21:34
devanandakgriffs: thanks!21:35
ttxdevananda: i'll have to edit the slots on the scheduling site21:35
devanandayep. i wont schedule anything yet21:35
*** dprince has quit IRC21:35
ttx#action ttx to move slots around between Marconi and Ironic21:35
ttxwill do that tomorrow morning. At this hour I would fumble it21:36
mikalSo, perhaps I'm slow. I can see a commenting interface on summit.o.o. Where do I set things to approved / rejected etc?21:36
ttxmikal: you should have a "Review Nova topic" button on the main screen21:36
*** pdmars has quit IRC21:36
*** weshay has quit IRC21:36
notmynamemikal: you have to click on the "unreviewed" word on the far right21:36
mikalttx: yep, clicked that21:36
*** vijendar has quit IRC21:36
notmynamemikal: not the topic name21:37
mikalnotmyname: ahhh, ok!21:37
dhellmanntook me a while to find that too21:37
*** pdmars has joined #openstack-meeting21:37
notmynamemikal: I've been doing this for years and ttx just tought me about the rehoming today!21:37
ttxmikal: also the "Help" screen (link at bottom) is supposed to contain useful help21:37
*** pdmars has quit IRC21:37
mikalOh, you can't do that in the proposal view screen?21:37
mikalJust that summary list?21:37
ttxmikal: yes, you have to be on the review screen21:37
mikalOk21:37
mikalI can live with that21:37
*** pdmars has joined #openstack-meeting21:37
ttxfirst person who tells me the site sucks gets a link to the openstack-infra repo which contains the code for it :)21:38
devanandaheh21:38
mikalThe site is wonderful!21:38
devanandattx: it's awesome :)21:38
*** fnaval has joined #openstack-meeting21:38
ttxmikal: I KNOW! It has this little Launchpad feeling!21:38
*** pdmars_ has joined #openstack-meeting21:38
ttx#topic Open discussion21:39
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:39
ttxmight as well switch to that21:39
*** IlyaE has quit IRC21:39
*** overlayer has quit IRC21:40
ttxjeblair: looks like you have a duplicate on the SSO stuff21:40
*** max_lobur has quit IRC21:40
jeblairttx: yes, i'm combining those 221:40
ttxjeblair: by the way, we are sharing the same pod!21:40
* mtreinish has to drop21:41
notmynameI have questions about the Dev/Ops session(s) that were proposed21:41
mikalIf we combine two proposals, do we end up with a proposal with two presenters?21:41
notmynamewere those proposed to every project?21:41
mikali.e. is that more politically acceptable than accepting one and rejecting the other?21:41
jeblairdhellmann: any chance you have space for this in oslo? http://summit.openstack.org/cfp/details/6921:41
dolphmmikal: basically, yes21:41
ttxnotmyname: I think that was Tom's plan yes21:41
mikalAnd then I can edit the proposal text to make it make sense?21:41
notmynameah, yes. I see them now21:41
ttxmikal: so.. let me explain21:41
dhellmannjeblair: only if you promise all of you guys come and help us decide what to do -- I need your input on that one21:41
dolphmmikal: you end up with sessions like this http://junodesignsummit.sched.org/event/20465cd62e9054d4043dda156da5070e21:41
zanebnotmyname: I believe only projects who requested it, but that was quite a lot21:42
dolphmmikal: and all you can do is add some prefix text, which i didn't do there21:42
dolphm(yet)21:42
*** pdmars has quit IRC21:42
mikalHmmmm, ok21:42
ttxmikal: if you add more than one session on a time slot, it becomes a combined session with the two descriptions concatenated. You can edit the title of the session and add a small paragraph on top so that the thing doesn't look too ugly21:42
jeblairdhellmann: definitely, probably want qa folks there too21:42
mikalAnd the way you merge is in the scheduling UI?21:42
annegentlewe have ten interns working this (northern hemisphere) summer on OpenStack through the Google Summer of Code and GNOME Outreach Program for Women programs21:42
dolphmmikal: i suppose you could also stomp on the proposed session descriptions to eliminate redundancy, etc21:43
dhellmannjeblair: true21:43
annegentleten!21:43
dhellmannjeblair: ok, send it over, and I'll try to make room21:43
notmynameannegentle: nice!21:43
dolphmmikal: but do that individually before getting to the scheduling screen21:43
ttxmikal: but it's also valid to tweak one so that it includes the other and then reject session 221:43
dhellmannjeblair: oops, I can change that one, nevermind21:43
zanebannegentle: that's awesome :)21:43
ttxmikal: if you are comfortable with the proposers21:43
dhellmannjeblair: hmm, no, I can't change the track21:43
mikalOk, I will muddle around and do my best, making a lot of enemies in the process and leading to my ultimate downfall. Its a greek trajedy of summit organization really.21:43
ttxmikal: I can help you.21:44
jeblairdhellmann: it's probably going to be tricky scheduling it; there's a lot of infra/oslo/qa/docs/release overlap.  i definitely want it to happen and attend though.21:44
ttxmikal: don't hesitate to ping me when you want to work on it21:44
*** rakhmerov has joined #openstack-meeting21:44
notmynamemikal: beware the ides of may21:45
dhellmannjeblair: yeah21:45
ttxmikal: and yes, you merge by dragging more than one session to the same time slot.21:45
*** pdmars_ has quit IRC21:45
mikalttx: thanks, I'm starting to fight with it now, but slowly21:45
mikalnotmyname: so true21:45
jeblairttx: how do we move to another topic?21:45
devanandattx: does the UI support merging >2 proposals?21:46
dolphmdevananda: yes21:46
notmynamejeblair: I know this one! click on the topic on the far left21:46
devanandadolphm: thanks21:46
jeblairttx, notmyname: got it thx21:46
dolphmdevananda: the session i linked above is 4 proposals merged into one session21:46
ttxnotmyname: looks like I should make that a bit more discoverable.21:46
ttxdevananda: yes21:46
jeblairdhellmann: http://summit.openstack.org/cfp/details/69 moved to oslo.  mtreinish: fyi on a session infra and qa folks should try to attend21:47
ttxdhellmann: maybe you should wait until the Docs/RelMgt/Infra/QA room is scheduled to do the Oslo scheduling21:47
dhellmannjeblair: ack21:47
notmynamettx: IMO having one "edit" screen accessed by any link on that session would be nice21:47
dhellmannttx: yeah, good point21:47
ttxdhellmann: that should make choices easier21:48
*** ArthurBerezin has left #openstack-meeting21:48
ttxnotmyname: yes. I'll admit not having worked AT ALL on that app this cycle.21:48
*** rakhmerov has quit IRC21:49
dhellmannseems much more important to spend time on story board21:49
notmynamettx: also, when I was doing open compute project stuff, they were really wanting to use the same system for scheduling sessions at their conference. it's a popular thing!21:49
lifelessttx: I'd really like to let more folk in the project twiddle the layout21:50
*** mattgriffin has quit IRC21:50
lifelessttx: ptl-only takes ptl from an arbitrator to a only-one-that-does situation21:50
ttxlifeless: it's just a convenience gateway, you don't have to make all the calls21:50
zaneblifeless: +1. tbh, I'd love to see the selection/scheduling done in Gerrit21:50
*** _nadya_ has quit IRC21:51
lifelessttx: copying stuff out of it to an etherpad is painful and time consuming21:51
*** topol has quit IRC21:51
ttxI just need to have one go-to name to complain to if it's not done21:51
lifelessttx: thats fine - have a the PTL as ultimately responsible21:51
dolphmlifeless: do the twiddling in google docs or something, and then enter the final outcome into summit.openstack.org ?21:51
lifelessdolphm: sure - we're using etherpad. Its the copy-paste-sync thats painful21:51
ttxlifeless: but yeah, I guess the tool could allow for more collaboration in scheduling21:52
lifelessbecause you have an app that doesn't delegate21:52
lifelessand we tell people to use that app21:52
ttxlifeless: or we could have some export/import that would let you iterate off-tool with more people21:52
lifelessbut many? most? projects don't scheule in it21:52
lifelessttx: import-export to something gerrit managed would be sweet21:52
*** JoeZhou has joined #openstack-meeting21:52
dolphmttx: maybe an export session titles and details links to csv feature?21:52
jgriffithgerrit for EVERYTHING21:53
jgriffith:)21:53
jeblairttx: first cut of infra is pushed to sched21:53
*** lbragstad has quit IRC21:53
dolphm(but it takes awhile for sched.org to reflect)21:53
ttxyes, somehow sched takes time to show up stuff21:53
ttxdolphm: funny how it fails to detect a new topic21:54
ttxit takes anywhere from 5 to 60minutes for the new sessions to be recognized as a new topic21:55
ttxjeblair: pushed the tentative RelMgt schedule21:56
jeblairanteaya: ^21:57
ttxOK, we are running out of time21:57
ttxDon't hesitate to ping me this week if you have questions21:58
ttxI'm away next week, so better ask questions this week21:58
*** JoeZhou has quit IRC21:58
*** crandquist has quit IRC21:58
ttxLast words ?21:58
anteayathanks21:58
ttxOh. Vote!21:58
mikalttx: thanks for the hand holding21:58
anteaya:D21:58
*** sballe_ has quit IRC21:59
ttx#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:59
openstackMeeting ended Tue Apr 22 21:59:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-04-22-21.03.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-04-22-21.03.txt21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-04-22-21.03.log.html21:59
*** ameade has joined #openstack-meeting22:01
*** jlibosva has joined #openstack-meeting22:01
*** marcoemorais has quit IRC22:02
*** JoeZhou_ has joined #openstack-meeting22:03
*** ameade has quit IRC22:03
*** nati_ueno has quit IRC22:04
*** jlibosva has quit IRC22:05
anteayathanks reminding people to vote is working22:06
*** mwagner_lap has joined #openstack-meeting22:07
*** dfg has left #openstack-meeting22:08
*** marcoemorais has joined #openstack-meeting22:09
*** JoeZhou_ has quit IRC22:09
*** markmcclain has quit IRC22:10
*** derekh has joined #openstack-meeting22:13
*** IlyaE has joined #openstack-meeting22:13
*** mattgriffin has joined #openstack-meeting22:14
*** dstanek is now known as dstanek_zzz22:17
*** _nadya_ has joined #openstack-meeting22:17
*** joesavak has quit IRC22:18
*** epim has joined #openstack-meeting22:20
*** epim has quit IRC22:20
*** banix has quit IRC22:20
*** markmc has quit IRC22:23
*** Mandell has quit IRC22:24
*** prad has quit IRC22:24
*** nati_ueno has joined #openstack-meeting22:24
*** bknudson has quit IRC22:25
*** Gordonz has quit IRC22:27
*** andreaf_ has quit IRC22:29
*** Mandell has joined #openstack-meeting22:31
*** otherwiseguy has quit IRC22:33
*** IlyaE has quit IRC22:38
*** nati_ueno has quit IRC22:43
*** rakhmerov has joined #openstack-meeting22:45
*** IlyaE has joined #openstack-meeting22:46
*** stevemar has quit IRC22:47
*** topol has joined #openstack-meeting22:48
*** rakhmerov has quit IRC22:49
*** epim has joined #openstack-meeting22:50
*** elo1 has quit IRC22:52
*** zdiN0bot has quit IRC22:52
*** neelashah has quit IRC22:53
*** banix has joined #openstack-meeting22:54
*** gokrokve has quit IRC22:56
*** reed has quit IRC22:56
*** banix has quit IRC22:58
*** fnaval has quit IRC23:00
*** eglynn_ has quit IRC23:02
*** jlibosva has joined #openstack-meeting23:02
*** nati_ueno has joined #openstack-meeting23:02
*** ameade has joined #openstack-meeting23:04
*** mattgriffin has quit IRC23:05
*** jlibosva has quit IRC23:07
*** ameade has quit IRC23:09
*** atiwari has joined #openstack-meeting23:10
*** david-lyle has quit IRC23:10
*** zdiN0bot has joined #openstack-meeting23:14
*** jergerber has quit IRC23:15
*** changbl has quit IRC23:18
*** ramashri has quit IRC23:19
*** gokrokve has joined #openstack-meeting23:20
*** elo has quit IRC23:20
*** elo has joined #openstack-meeting23:21
*** kgriffs is now known as kgriffs|afk23:21
*** elo has joined #openstack-meeting23:22
*** fnaval has joined #openstack-meeting23:22
*** mrodden has quit IRC23:26
*** atiwari has quit IRC23:26
*** doron_afk has quit IRC23:33
*** emagana has quit IRC23:33
*** flaper87 is now known as flaper87|afk23:35
*** eguz has quit IRC23:36
*** gokrokve_ has joined #openstack-meeting23:36
*** yfujioka has joined #openstack-meeting23:36
*** eghobo has joined #openstack-meeting23:36
*** jgrimm has quit IRC23:36
*** elo1 has joined #openstack-meeting23:38
*** gokrokve has quit IRC23:39
*** rediskin has left #openstack-meeting23:40
*** krtaylor has quit IRC23:43
*** meteorfox|lunch has quit IRC23:44
*** rakhmerov has joined #openstack-meeting23:46
*** topol has quit IRC23:47
*** fnaval has quit IRC23:48
*** fnaval has joined #openstack-meeting23:49
*** rakhmerov has quit IRC23:51
*** bknudson has joined #openstack-meeting23:52
*** mrodden has joined #openstack-meeting23:53
*** fnaval has quit IRC23:53
*** mrodden1 has joined #openstack-meeting23:55
*** beagles has quit IRC23:55
*** elo1 has quit IRC23:57
*** mrodden has quit IRC23:58

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