Thursday, 2014-04-24

*** Qiming has joined #openstack-meeting00:01
*** zdiN0bot has quit IRC00:01
*** gokrokve has quit IRC00:03
*** nati_ueno has quit IRC00:05
*** epim has quit IRC00:06
*** ThiagoCMC has quit IRC00:08
*** vuil has quit IRC00:08
*** epim has joined #openstack-meeting00:10
*** epim has quit IRC00:12
*** marcoemorais has quit IRC00:13
*** rakhmerov has joined #openstack-meeting00:13
*** manishg has joined #openstack-meeting00:14
*** Qiming has quit IRC00:14
*** marcoemorais has joined #openstack-meeting00:15
*** ssurana has joined #openstack-meeting00:16
*** rakhmerov has quit IRC00:17
*** tsekiyam_ has joined #openstack-meeting00:18
*** epim has joined #openstack-meeting00:18
*** jungleboyj has quit IRC00:18
*** eguz has joined #openstack-meeting00:19
*** s3wong has joined #openstack-meeting00:20
*** sweston has quit IRC00:21
*** tsekiyama has quit IRC00:21
*** tsekiyam_ has quit IRC00:22
*** eghobo has quit IRC00:23
*** zhikunliu has joined #openstack-meeting00:25
*** mattgriffin has quit IRC00:25
*** ameade has joined #openstack-meeting00:26
*** fnaval has quit IRC00:27
*** fnaval has joined #openstack-meeting00:28
*** epim has quit IRC00:29
*** joesavak has joined #openstack-meeting00:30
*** fungi has quit IRC00:30
*** gokrokve has joined #openstack-meeting00:30
*** ameade has quit IRC00:31
*** vjay has joined #openstack-meeting00:31
*** cjellick has quit IRC00:31
*** fnaval has quit IRC00:32
*** cjellick has joined #openstack-meeting00:32
*** zdiN0bot has joined #openstack-meeting00:33
*** jsavak has joined #openstack-meeting00:34
*** amcrn has joined #openstack-meeting00:34
*** gokrokve has quit IRC00:34
*** nati_ueno has joined #openstack-meeting00:36
*** fungi has joined #openstack-meeting00:36
*** cjellick has quit IRC00:37
*** zhiyan_ is now known as zhiyan00:37
*** zdiN0bot has quit IRC00:38
*** epico has joined #openstack-meeting00:38
*** beagles has quit IRC00:38
*** joesavak has quit IRC00:38
*** nati_ueno has quit IRC00:40
*** mwagner_lap has joined #openstack-meeting00:42
*** zdiN0bot has joined #openstack-meeting00:44
*** zdiN0bot1 has joined #openstack-meeting00:49
*** yfujioka has joined #openstack-meeting00:49
*** zdiN0bot has quit IRC00:49
*** zdiN0bot1 has quit IRC00:53
*** fnaval has joined #openstack-meeting00:53
*** ssurana has quit IRC00:53
*** jsavak has quit IRC00:54
*** jlibosva has joined #openstack-meeting00:55
*** rockyg has quit IRC00:56
*** mtanino has quit IRC00:58
*** huats_ has joined #openstack-meeting00:58
*** huats_ has quit IRC00:58
*** huats_ has joined #openstack-meeting00:58
*** zhiyan has quit IRC00:58
*** kiall has quit IRC00:58
*** huats has quit IRC00:58
*** jwang_ has quit IRC00:58
*** asselin2 has joined #openstack-meeting00:59
*** gokrokve has joined #openstack-meeting00:59
*** jlibosva has quit IRC01:00
*** zhiyan has joined #openstack-meeting01:00
*** fungi has quit IRC01:00
*** harlowja has joined #openstack-meeting01:00
*** fungi has joined #openstack-meeting01:01
*** kiall has joined #openstack-meeting01:02
*** marcoemorais has quit IRC01:02
*** annegentle has quit IRC01:02
*** dstanek_zzz has quit IRC01:02
*** marcoemorais has joined #openstack-meeting01:03
*** IlyaE has joined #openstack-meeting01:03
*** gokrokve has quit IRC01:04
*** Mandell has quit IRC01:08
*** nati_ueno has joined #openstack-meeting01:10
*** s3wong has quit IRC01:11
*** jecarey has joined #openstack-meeting01:11
*** Darren_ has joined #openstack-meeting01:12
*** yaguang has joined #openstack-meeting01:13
*** rakhmerov has joined #openstack-meeting01:13
*** IlyaE has quit IRC01:15
*** TravT has quit IRC01:15
*** rakhmerov has quit IRC01:18
*** yamahata_ has joined #openstack-meeting01:20
*** zdiN0bot has joined #openstack-meeting01:20
*** yamahata has joined #openstack-meeting01:20
*** Darren_ has left #openstack-meeting01:21
*** zdiN0bot1 has joined #openstack-meeting01:22
*** Qiming has joined #openstack-meeting01:22
*** changbl has joined #openstack-meeting01:22
*** lintan_ has quit IRC01:23
*** lintan_ has joined #openstack-meeting01:23
*** zdiN0bot has quit IRC01:25
*** marcoemorais has quit IRC01:25
*** oomichi has joined #openstack-meeting01:26
*** zdiN0bot1 has quit IRC01:27
*** nati_ueno has quit IRC01:28
*** sweston has joined #openstack-meeting01:32
*** assef has joined #openstack-meeting01:32
*** eguz has quit IRC01:33
*** saschpe has quit IRC01:35
*** manishg has quit IRC01:36
*** manishg has joined #openstack-meeting01:36
*** nosnos has joined #openstack-meeting01:36
*** changbl has quit IRC01:36
*** saschpe has joined #openstack-meeting01:37
*** mengxd has joined #openstack-meeting01:44
*** changbl has joined #openstack-meeting01:49
*** ArthurBerezin has joined #openstack-meeting01:52
*** jlibosva has joined #openstack-meeting01:56
*** jlibosva1 has joined #openstack-meeting01:58
*** benonsoftware has quit IRC01:59
*** gokrokve has joined #openstack-meeting01:59
*** jlibosva has quit IRC02:00
*** gokrokve has quit IRC02:00
*** xianghui has joined #openstack-meeting02:01
*** gokrokve has joined #openstack-meeting02:01
*** weshay has quit IRC02:02
*** jlibosva1 has quit IRC02:02
*** jrist has quit IRC02:02
*** elo1 has joined #openstack-meeting02:04
*** ArthurBerezin has quit IRC02:04
*** IlyaE has joined #openstack-meeting02:04
*** gokrokve has quit IRC02:05
*** benonsoftware has joined #openstack-meeting02:05
*** coolsvap has quit IRC02:05
*** neelashah has joined #openstack-meeting02:06
*** IlyaE has quit IRC02:06
*** ArthurBerezin has joined #openstack-meeting02:06
*** coreywright has quit IRC02:06
*** banix has joined #openstack-meeting02:07
*** assef has quit IRC02:07
*** sweston has quit IRC02:08
*** yaguang has quit IRC02:09
*** jrist has joined #openstack-meeting02:10
*** coolsvap has joined #openstack-meeting02:10
*** sweston has joined #openstack-meeting02:13
*** haomaiw__ has quit IRC02:13
*** assef has joined #openstack-meeting02:13
*** haomaiwang has joined #openstack-meeting02:13
*** rakhmerov has joined #openstack-meeting02:14
*** coreywright has joined #openstack-meeting02:19
*** rakhmerov has quit IRC02:19
*** sweston has quit IRC02:20
*** imsurit has joined #openstack-meeting02:21
*** otherwiseguy has joined #openstack-meeting02:24
*** zehicle_at_dell has joined #openstack-meeting02:24
*** changbl has quit IRC02:26
*** nati_ueno has joined #openstack-meeting02:26
*** banix has quit IRC02:31
*** banix has joined #openstack-meeting02:33
*** devlaps has quit IRC02:35
*** mattgriffin has joined #openstack-meeting02:39
*** assef has quit IRC02:40
*** jrodom has joined #openstack-meeting02:40
*** vjay has quit IRC02:41
*** amcrn has quit IRC02:41
*** amotoki has quit IRC02:43
*** NobodyCam has quit IRC02:46
*** morganfainberg is now known as morganfainberg_Z02:47
*** vkmc has quit IRC02:48
*** xuhanp has joined #openstack-meeting02:48
*** alexpilotti has quit IRC02:49
*** matiu has joined #openstack-meeting02:55
*** matiu has joined #openstack-meeting02:55
*** coreywright has quit IRC02:55
*** enykeev has joined #openstack-meeting02:55
*** paragan has joined #openstack-meeting02:56
*** paragan has joined #openstack-meeting02:56
*** yamahata has quit IRC02:57
*** matiu_ has joined #openstack-meeting02:57
*** jlibosva has joined #openstack-meeting02:59
*** gokrokve has joined #openstack-meeting02:59
*** fnaval has quit IRC03:02
*** dkranz has joined #openstack-meeting03:02
*** fnaval has joined #openstack-meeting03:03
*** jlibosva has quit IRC03:04
*** rfolco has quit IRC03:07
*** fnaval has quit IRC03:07
*** sandywalsh has quit IRC03:08
*** harlowja is now known as harlowja_away03:09
*** dkranz has quit IRC03:09
*** arnaud has quit IRC03:10
*** sandywalsh has joined #openstack-meeting03:10
*** lbragstad has joined #openstack-meeting03:11
*** IlyaE has joined #openstack-meeting03:12
*** asselin2 has quit IRC03:16
*** zhikunliu has quit IRC03:16
*** yaguang has joined #openstack-meeting03:17
*** elo1 has quit IRC03:18
*** mattgriffin has quit IRC03:18
*** prad has quit IRC03:19
*** manishg has quit IRC03:20
*** manishg_ has joined #openstack-meeting03:20
*** IlyaE has quit IRC03:22
*** sankarshan_away is now known as sankarshan03:24
*** jrodom has quit IRC03:24
*** banix has quit IRC03:25
*** Jianyong has joined #openstack-meeting03:30
*** changbl has joined #openstack-meeting03:30
*** HenryG has quit IRC03:36
*** zhikunliu has joined #openstack-meeting03:41
*** ramishra has joined #openstack-meeting03:46
*** sweston has joined #openstack-meeting03:47
*** rakhmerov has joined #openstack-meeting03:50
*** nati_ueno has quit IRC03:55
*** haomai___ has joined #openstack-meeting03:55
*** Mandell has joined #openstack-meeting03:56
*** haomaiwang has quit IRC03:59
*** jlibosva has joined #openstack-meeting03:59
*** otherwiseguy has quit IRC04:00
*** eghobo has joined #openstack-meeting04:01
*** sweston has quit IRC04:01
*** yfried has quit IRC04:01
*** ujuc has joined #openstack-meeting04:02
*** matiu has quit IRC04:03
*** sweston has joined #openstack-meeting04:03
*** vjay has joined #openstack-meeting04:03
*** slong has quit IRC04:04
*** slong has joined #openstack-meeting04:04
*** jlibosva has quit IRC04:05
*** coolsvap has quit IRC04:05
*** amcrn has joined #openstack-meeting04:06
*** coolsvap has joined #openstack-meeting04:07
*** gokrokve has quit IRC04:08
*** Longgeek has joined #openstack-meeting04:10
*** novas0x2a|laptop has quit IRC04:12
*** yamahata has joined #openstack-meeting04:17
*** harlowja_away is now known as harlowja04:18
*** marcoemorais has joined #openstack-meeting04:20
*** comay has quit IRC04:23
*** yfried has joined #openstack-meeting04:24
*** haomai___ has quit IRC04:24
*** haomaiwang has joined #openstack-meeting04:25
*** stevemar has joined #openstack-meeting04:27
*** yfried has quit IRC04:29
*** comay has joined #openstack-meeting04:31
*** neelashah has quit IRC04:32
*** David___ has joined #openstack-meeting04:33
*** David___ has quit IRC04:34
*** buptdavid has joined #openstack-meeting04:34
*** buptdavid has quit IRC04:34
*** jjmb has joined #openstack-meeting04:38
*** arnaud__ has joined #openstack-meeting04:40
*** slong has quit IRC04:42
*** slong has joined #openstack-meeting04:42
*** yamahata has quit IRC04:48
*** yamahata has joined #openstack-meeting04:49
*** nati_ueno has joined #openstack-meeting04:52
*** haomaiw__ has joined #openstack-meeting04:54
*** afazekas is now known as _afazekas_away04:56
*** haomaiwang has quit IRC04:57
*** chandan_kumar has joined #openstack-meeting05:00
*** jlibosva has joined #openstack-meeting05:00
*** sankarshan is now known as sankarshan_away05:01
*** jlibosva has quit IRC05:05
*** nelsnelson has quit IRC05:06
*** gokrokve has joined #openstack-meeting05:07
*** rwsu has quit IRC05:07
*** nati_ueno has quit IRC05:07
*** nosnos has quit IRC05:08
*** yfried has joined #openstack-meeting05:10
*** gokrokve has quit IRC05:11
*** IlyaE has joined #openstack-meeting05:11
*** lbragstad has quit IRC05:16
*** marcoemorais has quit IRC05:16
*** Jianyong has quit IRC05:17
*** ItSANg___ has joined #openstack-meeting05:20
*** ItSANgo has quit IRC05:22
*** rwsu has joined #openstack-meeting05:23
*** Jianyong has joined #openstack-meeting05:24
*** wwallnrr__ has quit IRC05:27
*** Jianyong has quit IRC05:31
*** nati_ueno has joined #openstack-meeting05:33
*** amotoki has joined #openstack-meeting05:33
*** Jianyong has joined #openstack-meeting05:34
*** nosnos has joined #openstack-meeting05:35
*** saurabhs has left #openstack-meeting05:35
*** jlibosva has joined #openstack-meeting05:35
*** jlibosva has quit IRC05:35
*** eghobo has quit IRC05:39
*** eghobo has joined #openstack-meeting05:39
*** ssurana has joined #openstack-meeting05:39
*** eguz has joined #openstack-meeting05:46
*** yogeshmehra has joined #openstack-meeting05:47
*** Qiming has quit IRC05:48
*** Qiming has joined #openstack-meeting05:49
*** yamamoto_ has joined #openstack-meeting05:50
*** eghobo has quit IRC05:50
*** arnaud__ has quit IRC05:52
*** hrzbrg has joined #openstack-meeting05:52
*** egallen has quit IRC05:54
*** nati_ueno has quit IRC05:58
*** garyk has joined #openstack-meeting06:00
*** jcoufal has joined #openstack-meeting06:02
*** mrunge has joined #openstack-meeting06:04
*** nati_ueno has joined #openstack-meeting06:05
*** Longgeek has quit IRC06:05
*** gyee has quit IRC06:05
*** Longgeek has joined #openstack-meeting06:06
*** Longgeek has quit IRC06:06
*** Longgeek has joined #openstack-meeting06:07
*** gokrokve has joined #openstack-meeting06:07
*** haomaiw__ has quit IRC06:10
*** haomaiwa_ has joined #openstack-meeting06:10
*** yogeshmehra has quit IRC06:11
*** gokrokve has quit IRC06:12
*** Longgeek_ has joined #openstack-meeting06:12
*** IlyaE has quit IRC06:13
*** ildikov has quit IRC06:15
*** vjay has quit IRC06:16
*** Longgeek has quit IRC06:16
*** jlibosva has joined #openstack-meeting06:18
*** nshaikh has joined #openstack-meeting06:19
*** IlyaE has joined #openstack-meeting06:23
*** zehicle_at_dell has quit IRC06:23
*** hrzbrg has quit IRC06:26
*** Macaveli has joined #openstack-meeting06:27
*** harlowja is now known as harlowja_away06:30
*** afazekas has joined #openstack-meeting06:32
*** belmoreira has joined #openstack-meeting06:32
*** ssurana has quit IRC06:36
*** comay has quit IRC06:37
*** IlyaE has quit IRC06:37
*** flaper87|afk is now known as flaper8706:38
*** yogeshmehra has joined #openstack-meeting06:41
*** Mandell has quit IRC06:43
*** sankarshan_away is now known as sankarshan06:43
*** Mandell has joined #openstack-meeting06:43
*** mengxd has quit IRC06:44
*** ramishra has quit IRC06:45
*** ramishra has joined #openstack-meeting06:46
*** zdiN0bot1 has joined #openstack-meeting06:46
*** Fdot has joined #openstack-meeting06:48
*** ndipanov has joined #openstack-meeting06:48
*** zdiN0bot1 has quit IRC06:51
*** _nadya_ has joined #openstack-meeting06:52
*** slong has quit IRC06:53
*** doron_afk has joined #openstack-meeting06:53
*** hrzbrg has joined #openstack-meeting06:53
*** garyk has quit IRC06:53
*** stevemar has quit IRC06:54
*** hrzbrg has left #openstack-meeting06:55
*** sweston is now known as sweston|away06:57
*** sweston|away is now known as sweston06:57
*** nwidell has joined #openstack-meeting06:57
*** deepakcs has joined #openstack-meeting07:02
*** sandywalsh has quit IRC07:03
*** sandywalsh has joined #openstack-meeting07:04
*** amcrn has quit IRC07:04
*** ttrifonov_zZzz is now known as ttrifonov07:05
*** egallen has joined #openstack-meeting07:06
*** gokrokve has joined #openstack-meeting07:08
*** marekd|afk is now known as marekd07:08
*** lsmola has joined #openstack-meeting07:09
*** imsurit has quit IRC07:09
*** egallen has quit IRC07:10
*** marcoemorais has joined #openstack-meeting07:12
*** gokrokve has quit IRC07:12
*** mengxd has joined #openstack-meeting07:13
*** eguz has quit IRC07:13
*** ArthurBerezin has quit IRC07:15
*** _nadya_ has quit IRC07:18
*** epico has quit IRC07:20
*** bauzas has joined #openstack-meeting07:21
*** _nadya_ has joined #openstack-meeting07:21
*** reed has joined #openstack-meeting07:24
*** imsurit has joined #openstack-meeting07:24
*** ramishra has quit IRC07:24
*** nelsnelson has joined #openstack-meeting07:26
*** acoles_away is now known as acoles07:26
*** epico has joined #openstack-meeting07:27
*** d0ugal has quit IRC07:27
*** mrda is now known as mrda_away07:29
*** d0ugal has joined #openstack-meeting07:29
*** d0ugal has quit IRC07:29
*** d0ugal has joined #openstack-meeting07:29
*** rediskin has joined #openstack-meeting07:33
*** mrunge has quit IRC07:35
*** nwidell has quit IRC07:39
*** nwidell has joined #openstack-meeting07:40
*** ArthurBerezin has joined #openstack-meeting07:44
*** nwidell has quit IRC07:44
*** hashar has joined #openstack-meeting07:47
*** andreaf has joined #openstack-meeting07:50
*** ArthurBerezin has left #openstack-meeting07:51
*** akuznetsov has quit IRC07:51
*** akuznetsov has joined #openstack-meeting07:52
*** mrunge has joined #openstack-meeting07:52
*** gongysh has joined #openstack-meeting07:53
*** ipbabble has quit IRC07:55
*** whenry has quit IRC07:55
*** ildikov has joined #openstack-meeting07:56
*** vjay has joined #openstack-meeting08:02
*** ipbabble has joined #openstack-meeting08:03
*** whenry has joined #openstack-meeting08:03
*** sandywalsh_ has joined #openstack-meeting08:04
*** matrohon has joined #openstack-meeting08:06
*** nwidell has joined #openstack-meeting08:06
*** andreaf has quit IRC08:06
*** sandywalsh has quit IRC08:06
*** gokrokve has joined #openstack-meeting08:09
*** garyk has joined #openstack-meeting08:11
*** manishg_ has quit IRC08:13
*** mrmartin_ has joined #openstack-meeting08:13
*** gokrokve has quit IRC08:13
*** ildikov_ has joined #openstack-meeting08:16
*** BobBallAway has left #openstack-meeting08:17
*** nosnos has quit IRC08:18
*** derekh has joined #openstack-meeting08:18
*** yogeshmehra has quit IRC08:19
*** ildikov has quit IRC08:20
*** phil has joined #openstack-meeting08:20
*** julienvey has joined #openstack-meeting08:22
*** darraghb has joined #openstack-meeting08:24
*** evgenyf has joined #openstack-meeting08:24
*** ygbo has joined #openstack-meeting08:24
*** Mandell has quit IRC08:27
*** _nadya_ has quit IRC08:30
*** vjay has quit IRC08:34
*** vjay has joined #openstack-meeting08:38
*** andreaf has joined #openstack-meeting08:40
*** jtomasek has joined #openstack-meeting08:45
*** nati_ueno has quit IRC08:46
*** reed has quit IRC08:47
*** reed has joined #openstack-meeting08:47
*** safchain has joined #openstack-meeting08:48
*** ipbabble has quit IRC08:48
*** whenry has quit IRC08:48
*** Jianyong has quit IRC08:48
*** Jianyong has joined #openstack-meeting08:49
*** idegtiarov has joined #openstack-meeting08:49
*** dkehn has quit IRC08:49
*** 6JTAAFPHV has joined #openstack-meeting08:49
*** 5EXAA26CG has joined #openstack-meeting08:49
*** rediskin has left #openstack-meeting08:54
*** ipbabble has joined #openstack-meeting08:55
*** whenry has joined #openstack-meeting08:55
*** dkehn has joined #openstack-meeting08:56
*** [1]evgenyf has joined #openstack-meeting08:56
*** huats_ is now known as huats08:57
*** nwidell has quit IRC08:57
*** evgenyf has quit IRC08:58
*** [1]evgenyf is now known as evgenyf08:58
*** evgenyf has quit IRC09:00
*** evgenyf has joined #openstack-meeting09:00
*** zhikunliu has quit IRC09:01
*** Longgeek_ has quit IRC09:01
*** haomai___ has joined #openstack-meeting09:02
*** garyk has quit IRC09:03
*** yfujioka has quit IRC09:05
*** haomaiwa_ has quit IRC09:06
*** marcoemorais has quit IRC09:06
*** garyk has joined #openstack-meeting09:07
*** sankarshan is now known as sankarshan_away09:08
*** _nadya_ has joined #openstack-meeting09:08
*** ominakov has joined #openstack-meeting09:09
*** _nadya_ has quit IRC09:09
*** overlayer has joined #openstack-meeting09:09
*** Longgeek has joined #openstack-meeting09:09
*** gokrokve has joined #openstack-meeting09:10
*** yamamoto_ has quit IRC09:12
*** asselin2 has joined #openstack-meeting09:12
*** gokrokve has quit IRC09:14
*** sweston has quit IRC09:16
*** asselin2 has quit IRC09:16
*** hashar has quit IRC09:19
*** oomichi has quit IRC09:20
*** sushils_ has joined #openstack-meeting09:22
*** miarmak has quit IRC09:23
*** evgenyf has quit IRC09:23
*** nwidell has joined #openstack-meeting09:23
*** miarmak has joined #openstack-meeting09:27
*** overlayer has quit IRC09:28
*** zhiyan is now known as zhiyan_09:32
*** nwidell has quit IRC09:33
*** marcoemorais has joined #openstack-meeting09:33
*** nwidell has joined #openstack-meeting09:34
*** marcoemorais1 has joined #openstack-meeting09:35
*** evgenyf has joined #openstack-meeting09:36
*** marcoemorais has quit IRC09:38
*** marcoemorais1 has quit IRC09:39
*** paragan has quit IRC09:41
*** nwidell has quit IRC09:51
*** hashar has joined #openstack-meeting09:52
*** mengxd has quit IRC09:58
*** zhiyan_ is now known as zhiyan09:58
*** epico has quit IRC10:00
*** doron_afk is now known as doron10:03
*** dims has quit IRC10:08
*** zhiyan is now known as zhiyan_10:08
*** ujuc has quit IRC10:10
*** hashar has quit IRC10:10
*** gokrokve has joined #openstack-meeting10:11
*** Longgeek has quit IRC10:12
*** jprovazn has joined #openstack-meeting10:12
*** gokrokve has quit IRC10:15
*** nosnos has joined #openstack-meeting10:15
*** dims has joined #openstack-meeting10:19
*** Longgeek has joined #openstack-meeting10:20
*** Jianyong has quit IRC10:24
*** xuhanp has quit IRC10:24
*** Qiming has quit IRC10:26
*** evgenyf has quit IRC10:27
*** _qb has quit IRC10:28
*** nwidell has joined #openstack-meeting10:29
*** evgenyf has joined #openstack-meeting10:32
*** marcoemorais has joined #openstack-meeting10:36
*** marcoemorais has quit IRC10:40
*** jcoufal has quit IRC10:41
*** dstanek_zzz has joined #openstack-meeting10:44
*** dstanek_zzz is now known as dstanek10:44
*** ujuc has joined #openstack-meeting10:47
*** darraghb has quit IRC10:48
*** darraghb has joined #openstack-meeting10:48
*** mattgriffin has joined #openstack-meeting10:59
*** doron is now known as doron_afk11:00
*** paragan has joined #openstack-meeting11:05
*** paragan has quit IRC11:05
*** paragan has joined #openstack-meeting11:05
*** gongysh has quit IRC11:11
*** gokrokve has joined #openstack-meeting11:11
*** gokrokve has quit IRC11:16
*** rbowen has joined #openstack-meeting11:26
*** ramishra has joined #openstack-meeting11:34
*** beagles has joined #openstack-meeting11:35
*** jgallard has joined #openstack-meeting11:36
*** marcoemorais has joined #openstack-meeting11:37
*** SridharG has joined #openstack-meeting11:39
*** marcoemorais has quit IRC11:41
*** adalbas has joined #openstack-meeting11:42
*** chandan_kumar has quit IRC11:45
*** Qiming has joined #openstack-meeting11:48
*** Longgeek_ has joined #openstack-meeting11:52
*** Longgeek has quit IRC11:53
*** HenryG has joined #openstack-meeting11:55
*** Longgeek_ has quit IRC11:57
*** ildikov has joined #openstack-meeting11:59
*** mattgriffin has quit IRC12:01
*** rfolco has joined #openstack-meeting12:02
*** pdmars has joined #openstack-meeting12:02
*** ildikov_ has quit IRC12:02
*** Longgeek has joined #openstack-meeting12:04
*** Longgeek_ has joined #openstack-meeting12:04
*** hashar has joined #openstack-meeting12:07
*** doron_afk is now known as doron12:07
*** Longgeek has quit IRC12:08
*** salv-orlando has joined #openstack-meeting12:09
*** erecio has joined #openstack-meeting12:09
*** gokrokve has joined #openstack-meeting12:12
*** nwidell has quit IRC12:13
*** erecio has quit IRC12:13
*** jdob has joined #openstack-meeting12:16
*** mengxd has joined #openstack-meeting12:16
*** sankarshan_away is now known as sankarshan12:16
*** gokrokve has quit IRC12:17
*** rakhmerov has quit IRC12:19
*** rakhmerov has joined #openstack-meeting12:20
*** yogeshmehra has joined #openstack-meeting12:20
*** prad has joined #openstack-meeting12:22
*** rakhmerov has quit IRC12:24
*** erecio has joined #openstack-meeting12:24
*** rakhmerov has joined #openstack-meeting12:24
*** yogeshmehra has quit IRC12:25
*** mengxd has quit IRC12:26
*** mengxd has joined #openstack-meeting12:27
*** erecio has quit IRC12:27
*** prad has quit IRC12:31
*** xuhanp has joined #openstack-meeting12:36
*** marcoemorais has joined #openstack-meeting12:37
*** topol has joined #openstack-meeting12:39
*** mengxd has quit IRC12:40
*** erecio has joined #openstack-meeting12:40
*** nosnos has quit IRC12:42
*** marcoemorais has quit IRC12:42
*** rakhmerov has quit IRC12:43
*** ildikov has quit IRC12:50
*** ildikov has joined #openstack-meeting12:51
*** weshay has joined #openstack-meeting12:52
*** xianghui has quit IRC12:52
*** spzala has joined #openstack-meeting12:54
*** kun_huang has joined #openstack-meeting12:56
*** acoles is now known as acoles_away12:56
*** ildikov has quit IRC12:56
*** ayoung has quit IRC12:59
*** acoles_away is now known as acoles12:59
*** deepakcs has quit IRC12:59
*** neelashah has joined #openstack-meeting13:01
*** alexpilotti has joined #openstack-meeting13:01
*** zehicle_at_dell has joined #openstack-meeting13:02
*** ameade has joined #openstack-meeting13:02
*** jungleboyj has joined #openstack-meeting13:04
*** overlayer has joined #openstack-meeting13:04
*** ameade has quit IRC13:06
*** ildikov has joined #openstack-meeting13:06
*** Jianyong has joined #openstack-meeting13:07
*** yfried has quit IRC13:09
*** gokrokve has joined #openstack-meeting13:13
*** coolsvap is now known as coolsvap|afk13:13
*** coolsvap|afk is now known as coolsvap13:13
*** bknudson has quit IRC13:14
*** dprince has joined #openstack-meeting13:15
*** overlayer has quit IRC13:17
*** overlayer has joined #openstack-meeting13:17
*** jecarey has quit IRC13:17
*** gokrokve has quit IRC13:17
*** dhuber has joined #openstack-meeting13:18
*** markmcclain has joined #openstack-meeting13:19
*** julim has joined #openstack-meeting13:20
*** markmcclain has quit IRC13:20
*** deepakcs has joined #openstack-meeting13:21
*** ramishra_ has joined #openstack-meeting13:21
*** belmoreira has quit IRC13:21
*** ramishra has quit IRC13:22
*** vivek-ebay has joined #openstack-meeting13:24
*** yaguang has quit IRC13:25
*** belmoreira has joined #openstack-meeting13:27
*** banix has joined #openstack-meeting13:28
*** rakhmerov has joined #openstack-meeting13:28
*** banix has quit IRC13:28
*** vivek-eb_ has joined #openstack-meeting13:28
*** vijendar has joined #openstack-meeting13:28
*** changbl has quit IRC13:31
*** dkranz has joined #openstack-meeting13:32
*** deepakcs has quit IRC13:32
*** vivek-ebay has quit IRC13:32
*** jecarey has joined #openstack-meeting13:35
*** samuelbercovici has joined #openstack-meeting13:35
*** zehicle_at_dell has quit IRC13:36
*** jungleboyj has quit IRC13:37
*** fnaval has joined #openstack-meeting13:38
*** marcoemorais has joined #openstack-meeting13:38
*** marun has joined #openstack-meeting13:39
*** lbragstad has joined #openstack-meeting13:39
*** lbragstad has left #openstack-meeting13:40
*** yogeshmehra has joined #openstack-meeting13:41
*** overlayer has quit IRC13:41
*** VinceThePrince has joined #openstack-meeting13:41
*** bknudson has joined #openstack-meeting13:41
*** rakhmerov has quit IRC13:41
*** VinceThePrince has quit IRC13:41
*** berlin has joined #openstack-meeting13:42
*** zhangleiqiang has joined #openstack-meeting13:42
*** Macaveli has quit IRC13:42
*** marcoemorais has quit IRC13:42
*** eddie_ has joined #openstack-meeting13:43
*** _nadya_ has joined #openstack-meeting13:45
*** fabio has joined #openstack-meeting13:45
*** _nadya_ has quit IRC13:45
*** _nadya_ has joined #openstack-meeting13:45
*** jaypipes has joined #openstack-meeting13:46
*** akuznetsov has quit IRC13:46
*** mattgriffin has joined #openstack-meeting13:46
*** zns has joined #openstack-meeting13:48
*** zns has quit IRC13:48
*** zns has joined #openstack-meeting13:48
*** ayoung has joined #openstack-meeting13:49
*** coreywright has joined #openstack-meeting13:50
*** zns has quit IRC13:51
*** vivek-eb_ is now known as vivek-ebay13:52
*** balajiiyer has joined #openstack-meeting13:52
*** zns has joined #openstack-meeting13:54
*** manishg has joined #openstack-meeting13:54
*** jay-lau-513 has joined #openstack-meeting13:55
*** markwash has joined #openstack-meeting13:55
*** armax has joined #openstack-meeting13:55
*** balajiiyer has left #openstack-meeting13:55
*** zhiyan_ is now known as zhiyan13:55
*** coolsvap is now known as coolsvap|afk13:57
*** joesavak has joined #openstack-meeting13:57
*** manishg_ has joined #openstack-meeting13:58
enikanorov_neutron lbaas meeting in 3 minutes13:58
*** sbalukoff1 is now known as sbalukoff13:58
*** che-arne has joined #openstack-meeting13:58
*** samuelbercovici has quit IRC13:58
*** manishg has quit IRC13:59
*** samuelbercovici has joined #openstack-meeting13:59
*** german_ has joined #openstack-meeting13:59
*** hvprash has joined #openstack-meeting13:59
*** blogan has joined #openstack-meeting13:59
*** jorgem has joined #openstack-meeting14:00
*** bbaby has joined #openstack-meeting14:00
*** pcm_ has joined #openstack-meeting14:01
enikanorov_hi14:01
mesteryo/14:01
sbalukoffHowdy, eh!14:01
jorgemhello14:01
obondarev0/14:01
*** radez_g0n3 is now known as radez14:01
sballemorning14:01
enikanorov_#startmeeting neutron lbaas14:01
openstackMeeting started Thu Apr 24 14:01:38 2014 UTC and is due to finish in 60 minutes.  The chair is enikanorov_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron lbaas)"14:01
openstackThe meeting name has been set to 'neutron_lbaas'14:01
rm_workhey :)14:01
*** gokrokve has joined #openstack-meeting14:01
*** mrunge has quit IRC14:02
*** manishg has joined #openstack-meeting14:02
sballejust a heads up that I will not be here next week since I am goign on vacation.14:02
bloganhello14:02
*** thangp has joined #openstack-meeting14:02
german_hi14:02
enikanorov_the agenda for today is to discuss the steps we need to take in order to make a progress14:02
mesterysballe: Enjoy the time off!14:02
*** manishg_ has quit IRC14:02
enikanorov_sballe: good to know14:02
rm_worksballe: have a good one :P14:02
berlinhi14:02
sballethanks Going to Paris :-)14:02
enikanorov_so far we had several competing API/object model proposals14:02
*** zns has quit IRC14:03
jorgemenikanorov: Can we also figure out how we are going to organize at the summit sometime in the near future? Perhaps overML?14:03
mesteryJust FYI: It's looking like LBaaS will end up with 2 40 minute sessions.14:03
mesteryI'd hope we can organize as a team what we want to accomplish in those sessions.14:03
jorgemawesome14:03
enikanorov_jorgem: right, let's discuss the summit at the end of the meeting14:03
enikanorov_mestery: cool!14:04
enikanorov_so, let's get back on API discussion as I'd like to end it with some action items14:04
enikanorov_currently we have two competing approaches, one is existing 'granular' API14:04
enikanorov_another is 'single-call' API14:05
vivek-ebaywhy can't they both co-exist ?14:05
sbalukoffWell, technically the one I proposed is both.14:05
enikanorov_on 'granular API' which is an evolution of existing API I'v filed a blueprint to neutron-specs14:05
*** tongli has joined #openstack-meeting14:05
enikanorov_vivek-ebay: hold on :)14:05
jorgemenikanorov: "the single call" also allows granularity14:05
enikanorov_#link https://review.openstack.org/#/c/89903/14:05
rm_worki think both are both14:05
*** akuznetsov has joined #openstack-meeting14:05
*** manishg_ has joined #openstack-meeting14:05
sbalukoffrm_work: True.14:06
mesterySo for the single call API, it just makes use of the more granular APIs underneath? Is that the case?14:06
enikanorov_yes, so the API/obj model proposal in the link above is the API that we'll be focusing on14:06
*** martines_ has quit IRC14:06
enikanorov_the question would be how to better converge with single-call approach14:06
*** manishg has quit IRC14:06
rm_workmestery: yes and no? there is some thought that it should actually speak directly with the driver to do a single call, but I am not 100% sure we need to go that deep14:07
*** TrevorV has joined #openstack-meeting14:07
jorgemmestery: Our proposal allows for multiple API calls if wanted. However, provisioning can occur with a single call as well.14:07
enikanorov_btw, by saying 'we' i mean samuelbercovici, me, sbalukoff14:07
jorgemmestery: The choice is left up to the user14:07
mesteryThanks for the clarification folks!14:07
*** zns has joined #openstack-meeting14:07
jorgemenikanorov: And by "our"/"we" I mean the Rackspace LBaaS team. Good to point out14:07
enikanorov_so for the rest of the subteam, who would like to see single-call approach i suggest to come up with the blueprint14:08
*** avishayb has joined #openstack-meeting14:08
*** rakhmerov has joined #openstack-meeting14:08
enikanorov_that actually explains the approach based on the object model proposed in ^^^14:08
enikanorov_refering to the wiki with obj model description, we decided to go with 'vip-centric' approach, where the root object is VIP14:09
jorgemTo give an update, blogan sent out an email with some docs. What we are now doing is showing how the API proposal actually works with the use cases lined out in https://docs.google.com/document/d/1Ewl95yxAMq2fO0Z6Dz6fL-w2FScERQXQR1-mXuSINis/edit#14:09
enikanorov_and it plays loadbalancer role14:09
jorgemusing both a single call and multiple calls14:09
*** manishg has joined #openstack-meeting14:09
bloganenikanorov: are you saying you've already decided on going with the vip centric approach?14:09
mesteryjorgem: That's on my list of reading material today in fact. :)14:10
sbalukoffThis is news to me.14:10
sballeHP's current implementation of LBaaS uses the Atlas API so "we" like Rackspace's proposal and have decided to back that up instead of doing yet another proposal14:10
german_+114:10
*** manishg_ has quit IRC14:10
*** belmoreira has quit IRC14:10
enikanorov_blogan: that was a consensus solution with those who originally would like to see granular api14:10
rm_workerr wait, was there a vote already that I missed? :/14:10
enikanorov_sballe: that's fine, we need to come up with a plan on hw we can converge14:11
bloganenikanorov: so what was the point of us doing a proposal?14:11
TrevorVsbalukoff: what is news to you?  What jorgem was doing or what enikanorov_ said about vip-centric?14:11
sballeI missed it too14:11
*** aburaschi has joined #openstack-meeting14:11
jorgemA work-in-progress of how the use cases fit with our API is located here14:11
jorgem#link https://drive.google.com/folderview?id=0B_x8_4x6DRLad1NZMjgyVFhqakU&usp=sharing14:11
enikanorov_there's no vote, we need to account for everyone's need14:11
jorgemAgain, this is a WIP. I'm planning on making some diagrams for people that are visual learners14:11
sbalukoffTrevorV It feels like a decision has been made. I thought we were still in the "let's talk about pros and cons" stage.14:11
sballeenikanorov, I understand. I guess if we had to vote I know what proposal I would vote for. That's all I am saying14:11
enikanorov_one of the important needs is backward compatibility and support for existing customers14:12
rm_worksbalukoff: i also thought hat14:12
rm_work*that14:12
*** rakhmerov has quit IRC14:12
* rm_work though sometimes also thinks about hats14:12
bloganenikanorov: i thought we already decided that backwards compatibility is not needed anymore and starting an API from scratch was what we were going to do going forward14:12
enikanorov_sballe: yes, but i'm against choosing the only one. we can have both14:12
sballeblogan, +114:12
TrevorVenikanorov_:  you're saying there is no reason to entertain object models that aren't vip-centric?14:12
enikanorov_one option has been there since the beginning14:12
sballeenikanorov, Ok but let's amke sure we don't only the vip centric one.14:13
*** manishg_ has joined #openstack-meeting14:13
jorgemenikanorov: Mark McClain had suggested a new approach to the API. Perhaps allowing to run both side by side for a while is a meet in the middle compromise?14:13
mesteryjorgem: There's some overhead there, but that is one way to deprecate the older API.14:14
*** prad has joined #openstack-meeting14:14
enikanorov_sballe: on the object model side - it's pretty much fixed. on API side - there are options. so I actually would like to see how single-call approach fits in along with the proposed API/obj model14:14
sballejorgem, I like thta idea14:14
mesteryjorgem: We would have to support the old API for at least one more cycle.14:14
*** manishg has quit IRC14:14
rm_workyeah, jorgem +114:14
enikanorov_jorgem: side by side is what i'm suggesting as well. but we can't have two different object models14:14
*** thedodd has joined #openstack-meeting14:15
enikanorov_granular API is to stay.14:15
sbalukoffThat's true. But maybe it makes sense to have a different object model if there's a good reason for it.14:15
jorgemenikanorov: K, I'm just trying to figure out how to get everyone's needs in.14:15
*** ssurana has joined #openstack-meeting14:15
sbalukoffjorgem: Have y'all created an object model diagram that works with your proposed API?14:16
bloganif a new API is going to be made, trying to jam it into the shape of the current object model is the wrong way to go14:16
jorgemsbalukoff: We are working on it. There is a WIP in the link I sent14:16
sballesbalukoff, I agree and I thougth we were revising the object model as well14:16
enikanorov_jorgem: I think the task would be just to come up with a 'single-call' API for the resources that are proposed in the blueprint i've filed14:16
german_snd my underdtsnding was the API would drive the object model14:16
sballegerman_, +114:16
enikanorov_it is not very different from the API that you have14:16
blogangerman_: that is usually the case14:16
jorgemenikanorov: Could you link the bp?14:17
*** manishg has joined #openstack-meeting14:17
enikanorov_ https://review.openstack.org/#/c/89903/14:17
jorgemenikanorov: thanks14:17
enikanorov_folks, we're not doing it from scratch14:17
*** manishg_ has quit IRC14:18
enikanorov_obj model evolves, we're fixing the problems with it and with the API. it's fine to have a single call addition14:18
enikanorov_but it's not fine to rewrite everything14:18
mesteryDo folks have serious concerns with the object model as proposed? I need to look at enikanorov_'s BP yet myself. Just curious.14:18
bloganthe current object model was derived from the current API. the current API is not liked by many, why would we try to do a new API and jam that into the shape of the current object model?14:19
TrevorVblogan: +114:19
german_+114:19
sbalukoffHeh! To be honest, I'm trying to see where in the bp the object model diagram or other description is.  (I've not seen this bp before today.)14:19
samuelbercovicithe proposed model is in essence splitting the v1.0 VIP to VIP-->listeners14:19
TrevorVenikanorov_: who decided the lack of a new Object Model?14:19
TrevorVenikanorov_: why is there no replacing it?14:19
rm_workI had some concerns, but I need to see if enikanorov_ is proposing any fixes for the specific things I had problems with, or if the objectmodel is essentially unchanged14:19
enikanorov_sbalukoff: i can't put pictures in the text format. it refers obj model discussion14:20
*** martines_ has joined #openstack-meeting14:20
mesteryenikanorov_: asciiflow.com or such. :)14:20
samuelbercovicisbalukoff: we are working in prallel to have an graphivsl object model14:20
enikanorov_sbalukoff: and yes, it was put out there just yesterday14:20
samuelbercoviciwe will add it to the wiki14:20
bloganmestery: i have concerns if we're keeping the same object model and we have to work around it14:20
enikanorov_blogan: we're not14:20
sbalukoffblogan: +114:20
mesteryblogan: Understood.14:21
enikanorov_we're not keepng existing object model14:21
*** manishg_ has joined #openstack-meeting14:21
bloganenikanorov: but you've already decided on an object model14:21
ptoohill?14:21
enikanorov_obejct model is extended to account for every case we have planned14:21
sbalukoffIt seems to me an API overhaul and object model overhaul go hand-in-hand. The question is: Are the use cases satisfied?14:21
samuelbercovicisbalukoff: yes14:21
*** manishg has quit IRC14:21
ptoohilllook the link jorgem provided14:21
jorgemsbalukoff: Correct which is what I'm trying to show with the documents we are preparing14:22
TrevorVsbalukoff: in the object model we've been working on the use-cases are a priority to satisfy.14:22
* mestery admits he needs to read the use case documents and enikanorov_'s BP to see how the gaps were closed.14:22
*** jungleboyj has joined #openstack-meeting14:22
rm_workno use arguing about it right now, we need some time to go and actually review enikanorov_'s proposed object model in depth and verify that it works for us… but we shouldn't consider this "closed"14:22
sballerm_work, Agreed14:22
mesteryrm_work: +114:22
*** phil has quit IRC14:22
sbalukoffSweet! Well... I've certainly not had time yet to add the use cases I was able to think of this last week in creating the API proposal that I made.14:22
enikanorov_the proposed object model was there for months: https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance/Discussion14:22
*** fnaval has quit IRC14:22
enikanorov_that's a VIP-centric approach14:22
sbalukoffSorry, I didn't know that would become a priority.14:22
bloganyeah all I am saying is that decided in the object model shouldn't be changed drastically without everyone agreeing causes concern14:23
jorgemenikanorov: Can you do a similar exercise that we are doing and actually document workflows on how your proposal fits with the use cases we have identified thus far?14:23
rm_workenikanorov_: that proposed object model was one of many, including the one we were going to propose, we weren't aware that it wasn't up for debate14:23
*** fnaval has joined #openstack-meeting14:23
sbalukoffrm_work: +114:23
german_let's pick an API first and then revisitit the object model14:23
enikanorov_rm_work: we've discussed these proposals for several meetings in line14:23
bloganand now that everyone has been caught off guard on this and thought it was up for debate, why is not now up for debate?14:24
enikanorov_and vip-centric approach was one of two primary14:24
*** belmoreira has joined #openstack-meeting14:24
jorgemIf everyone documents their proposals in a similar fashion I think we can then start to talk about the merits of them in a more structured fashion.14:24
rm_workenikanorov_: yes, and the discussion has been centered around picking a good API design, and then building an obj model from it14:24
enikanorov_along with 'loadbalancer' which is quite similar14:24
sbalukoffjorgem: +114:24
*** atiwari has joined #openstack-meeting14:24
sballerm_work, +114:24
german_jorgem, rm_work +114:25
*** manishg has joined #openstack-meeting14:25
mesteryThe new process for Neutron BPs is to submit things into the gerrit neutron-specs repository.14:25
mesteryNothing is set in stone until it's approved, so we can all comment on the object model in gerrit.14:25
mesteryIt may be best to drive initial comments there in fact.14:25
rm_workactually, could I ask why you have the authority to *make* this decision? I don't mean to be rude, but as a newcomer to this sort of system, I thought there was a PTL (now mestery) and… ??14:25
samuelbercovicimestery +114:25
rm_workmestery: +114:25
bloganmestery: thanks for the information, I did not know this14:25
mesteryIf people feel it's off base for their concerns, then perhaps we need to have a broader discussion.14:25
ptoohill+1 rm_work i had the same question14:26
*** manishg_ has quit IRC14:26
mestery#link https://wiki.openstack.org/wiki/Blueprints#Neutron14:26
enikanorov_good question on authority14:26
mesteryrm_work: It's ideal to drive consensus on gerrit, ML, and IRC. Hopefully we can do this going forward.14:26
enikanorov_i'm accouting for opinions of the folks who already actually committed fopr the project14:26
rm_workenikanorov_: and tallying a vote in your head?14:27
mesteryI love the passion from all the LBaaS participants! You folks have generated so many documents I'm buried catching up. :)14:27
enikanorov_and also we try to account for everyone else's needs14:27
TrevorVenikanorov_: are you talking about the original API or this new API we've been discussing creating?14:27
*** fnaval has quit IRC14:27
samuelbercovicienikanorov_: +114:27
*** funzo has quit IRC14:27
*** markmcclain has joined #openstack-meeting14:28
enikanorov_rm_work: my personal opinion that 'democracy' isn't working well in a group of 20 people and several competing proposals14:28
mesteryI also want to point out I am very happy that all the operators/providers are active in this sub-team. This is a good thing!14:28
*** funzo has joined #openstack-meeting14:28
enikanorov_the API change was discussed long before 1.5 months ago14:28
rm_workenikanorov_: well, we haven't ever had a "vote" so I wouldn't discount it yet <_<14:28
enikanorov_so there are both implementations and decisions made by many14:28
sbalukoffenikanorov_: Discussed but not decided upon14:28
*** funzo is now known as Guest1881814:28
*** hrzbrg has joined #openstack-meeting14:28
*** manishg_ has joined #openstack-meeting14:29
enikanorov_sbalukoff: because there was not an agreement, until recently14:29
mesteryFolks: Gerrit is where we can vote now. You all have +1/-1 authority there. :)14:29
bloganmestery: we're excited about being a part of this and hope that we can improve the current product14:29
*** kgriffs|afk is now known as kgriffs14:29
german_same here14:29
mesteryI appreciate enikanorov_ pushing out a spec review in the new process. I think we should vote there, and iterate and improve things in gerrit.14:29
*** manishg has quit IRC14:29
mesteryThoughts?14:29
german_let's work through the other documents first14:29
enikanorov_yeah, basically the new process has been made specifically for that14:30
sbalukoffenikanorov_: True, but should they be excluded because they just got involved recently? I know we have to move forward, but I also don't like excluding late-comers with valuable things to add.14:30
sballemestery, just like blogan we are existing about making this a better service as well14:30
mesterygerman_: You mean use cases?14:30
ptoohill+1 sbalukoff14:30
enikanorov_sbalukoff: i'm not trying to exclude nobody!14:30
sbalukoffFor example, jorgem's idea to create a google spreadsheet listing actual usage of load balancing services and features was brilliant.14:30
rm_workthat's a good point. we can have a vote on gerrit, if we would like.14:30
*** mwagner_lap has quit IRC14:30
enikanorov_that's the last thing i'd do14:30
sbalukoffI think we got a lot of valuable new information from that.14:30
bloganmestery: a lot of us operators are new and may not have votes, but we're very committed to this project and if we do not like the BP then because we have a lack of votes we don't have much power14:30
enikanorov_once again, we have two quite different competing approches14:31
*** nelsnelson has quit IRC14:31
enikanorov_i'd like to see them developing side by side14:31
enikanorov_not deciding between them14:31
sballeblogan, +1 same with us14:31
samuelbercovicienikanorov_, +114:31
enikanorov_the new approach has it's constraints - we can't rewrite everything from scratch, that needs to be understood14:31
bloganenikanorov: why not?14:31
*** nelsnelson has joined #openstack-meeting14:31
german_+114:31
sballeenikanorov, Why not? If we don;t like it14:32
TrevorVenikanorov_: exactly, what stops us from rewriting lbaas 2.0?14:32
sballeblogan, you beat me to it ;-)14:32
enikanorov_well.. saying with your words14:32
enikanorov_because we don't like to rewrite it14:32
sbalukoffenikanorov_: If we don't meet people's needs without rewriting everything from scratch, then they're going to do that themselves anyway.14:32
jorgemAt the end of the day, if we get all requirements in everyone should be happy right?14:32
*** adalbas has quit IRC14:32
mesteryjorgem: +100014:32
sbalukoffWhich is fine, if they're willing to put forth the work.14:32
samuelbercoviciblogan: there is alraedy a large amount of work in there which is not just the API14:32
*** manishg has joined #openstack-meeting14:32
rm_workenikanorov_: correction, *you* don't like to rewrite it :P14:32
enikanorov_jorgem: yep14:32
*** ttrifonov is now known as ttrifonov_zZzz14:32
rm_workwe're happy to :)14:32
sbalukoffjorgem: Yep!14:33
sballeenikanorov, yeah but we cannot duck-tape stuff. that will never give us the rigth product14:33
bloganjorgem: yes i agree but its concerning that decisions are being made because they were made prior to all this new interest in the product14:33
german_and if the current code doersn't meet requirements it has to chnage14:33
enikanorov_i'd not call evolution a duct-taping14:33
*** manishg_ has quit IRC14:33
sballeenikanorov, yeah but if the foundation isn't right the evolution won;t be14:34
german_+114:34
sbalukoffsballe: +114:34
rm_worksballe: +114:34
jorgemsballe: You have a good point. A lot of new requirements have come in which is why we are trying to start from scratch. enikanorov, the project as it is currently does not even address a lot of the operator requirements14:34
enikanorov_may be it make sense to talk after we see some committed patches from you so you taste yourself what it takes to actually contribute :)14:34
bloganevolving from something that had a lot of problems is not the right approach14:34
mesteryI think we're all in agreement we want to make things better in LBaaS.14:34
enikanorov_before suggesting to rewrite everything :)14:34
jorgemenikanorov: which I guess is why we have been proposing things from scratch14:34
enikanorov_sballe: we're fixing foundation14:34
enikanorov_sballe: that's the purpose of the BP14:35
*** jtomasek has quit IRC14:35
mesteryHow about if we all post comments on enikanorov_'s BP in gerrit.14:35
jorgemblogan: Didn't you just code up an example?14:35
mesteryIt's even possible for people to pull it down and push a new rev with changes as well, enikanorov_, would you be ok with that?14:35
enikanorov_'lots of problems' is just saying14:35
TrevorVmestery: Everyone is speaking in a sense to produce a positive outcome here, however enikanorov has just now stated people without commits have no opinion or value here.14:36
sballeenikanorov, I totally agree with you that I haven't contributed "patches" so far. I do plan to become very active and do so. I just want to contribute to the right foundation and not duck tape the old one.14:36
enikanorov_mestery: as long as it goes along the main idea14:36
sbalukoffenikanorov_: I'm concerned that a dictatorial approach to this problem is going to kill people's enthusiasm for improving LBaaS. If concerns aren't addressed, people will go back to what they've been doing until a couple months ago: Working on their disparate projects in a vacuum.14:36
*** manishg_ has joined #openstack-meeting14:36
mesteryI think enikanorov_ didn't mean it quite as it came out, and certainly we value everyone's opinion here, patch or no patch. There are many ways to measure contributions, patches being one.14:36
*** jungleboyj has quit IRC14:36
sballesbalukoff, +214:36
blogansbalukoff: perhaps that is what the intention is14:37
*** Guest18818 is now known as funzo14:37
enikanorov_sbalukoff: yes, that's a good point. but i'm not a dicator for sure. i just want to make a progress at least with one approach. and i want to help people make progress with another approach14:37
*** manishg has quit IRC14:37
aburaschi+1 to reuse the good parts of the current API14:37
*** TravT has joined #openstack-meeting14:37
samuelbercoviciI have written most of the use cases and about 90% could be solved with existing API + SSL +L7 which are in very advanced state. the modification comes to address the rest.14:38
jorgemaburaschi: I am down for reusing if it makes sense.14:38
*** tsekiyama has joined #openstack-meeting14:38
ptoohillhave we identified what the good parts are versus the bad?14:38
sbalukoffblogan: I hope not. Despite our disagreements, I think we can all do better working together still.14:38
enikanorov_ptoohill: yes14:38
sballejorgem, +214:38
aburaschisure :)14:38
enikanorov_ptoohill: the bad pats are those which prevent us to allow advanced use cases14:38
sbalukoffjorgem: +1.14:38
*** mtanino has joined #openstack-meeting14:38
german_jorgem +114:38
sbalukoffOk, so I keep hearing this come back to use cases. Maybe we should spend some time *really* fleshing out the use cases and move forward from there?14:39
samuelbercoviciI have also reviewed the proposed single call api and belive that it can be implemented with the proposal14:39
sbalukoffIf we do that, how do we go about determining which use cases we'll support and which we won't?14:39
*** marcoemorais has joined #openstack-meeting14:39
*** tsekiyam_ has joined #openstack-meeting14:39
german_vote in gerrit?14:39
jorgemsbalukoff: +1. And actually showing workflows on how each proposal satisfies those use cases14:39
enikanorov_sbalukoff: i think the single-call approach can fit well with the proposed API/obj model14:39
mesterygerman_: +1!14:39
aburaschi+1!14:40
enikanorov_sbalukoff: and that's why i said about the agreement14:40
mesteryIf someone files a use cases document in neutron-specs, that may be a really good start!14:40
sballeI would like to suggest we look at what is Neutron Foundation e.g. Plumbing and what should be in the Advanced services. We want the integation to be clean so that Neutron can change its implementation which affecting LBaaS which is a consumer of Neutron internals. Does tha make sense?14:40
samuelbercoviciboth the granular api and the single call should use the same object model whcih addresses the use cases14:40
*** manishg has joined #openstack-meeting14:40
sballes/whihc/without14:40
enikanorov_samuelbercovici: that's for sure14:40
german_+114:40
sbalukoffsamuelbercovici: +114:40
jorgemWe have one here that someone started ==> https://docs.google.com/document/d/1Ewl95yxAMq2fO0Z6Dz6fL-w2FScERQXQR1-mXuSINis/edit#14:41
vivek-ebay+114:41
*** manishg_ has quit IRC14:41
aburaschisballe: +114:41
rm_worksballe, samuelbercovici +114:41
mesteryNot to derail, but we only have 19 minutes left. It would be good to have some actionable items come out of this meeting. It may take us 10-15 minutes to get those. :)14:41
mesteryI'd like to see everyone comment on enikanorov_'s proposal in neutorn-specs.14:42
mesteryI'd also like to see use cases added to that or a separate spec with use cases filed.14:42
german_let's agree on use cases first14:42
*** kevinconway has joined #openstack-meeting14:42
mesteryIt makes it easier to comment in one place.14:42
enikanorov_#action enikanorov to extend BP with more detailed object model description14:42
samuelbercoviciso the proposal is based on 1. existing use cses 2. the ones we tried to do for icehouse want to complete forn juno 3. new uses cases that were the reason the discussion have started14:42
*** tsekiyama has quit IRC14:42
german_it feels like we need to agree on use cases first14:42
mesteryI'm finding it hard to figure out which documents to read and comment on :)14:42
*** vkmc has joined #openstack-meeting14:42
*** vkmc has quit IRC14:42
*** vkmc has joined #openstack-meeting14:42
enikanorov_german_: what to agree on, actually? if there's a use case, we need to support in, unless its totally don't fit into anything14:43
mesterygerman_: Absolutely! Someone can take a first crack and we can suggest more in gerrit.14:43
aburaschiI agree with mestery14:43
sbalukoffgerman_: +114:43
mesterygerman_: But the gerrit review can be a starting point.14:43
enikanorov_mestery: me too14:43
vivek-ebaymestery: +114:43
*** marcoemorais has quit IRC14:43
blogani will comment once I look it over, if it does satisfy our needs then I'll +1 it, however it seems like if a lot of the new people's opinions wont be heard because they more than likely dont have votes14:43
mesteryI am more than happy to help someone out who wants to drive that.14:43
enikanorov_blogan: it's not about choice, it's about accounting for everyone's concerns14:44
rm_workif you HAVE a gerrit account, you have a vote in gerrit, right? there's no requirements above that14:44
jorgemenikanorov: No necessarily, the product will have natural constraints and satisfying the .00001% use case may not make sense. We need to identify major and minor use cases in order to make a good decision.14:44
*** manishg_ has joined #openstack-meeting14:44
enikanorov_blogan: that what we had in mind proposing the BP14:44
*** adalbas has joined #openstack-meeting14:44
*** safchain has quit IRC14:44
enikanorov_jorgem: that's also true14:45
mesteryrm_work: It's tied to your launchpad account, so you need one of those.14:45
enikanorov_jorgem: but you know there are cases that affect API.obj model14:45
*** manishg has quit IRC14:45
jorgemenikanorov: Also, operator use cases have been largely ignored14:45
enikanorov_jorgem: others just affect a set of constants may be14:45
rm_workmestery: ah, well right. just saying, you don't need to have contributed a patch to neutron to vote14:45
mesteryrm_work: Correct! Anyone with a LP account can +1/-1.14:45
samuelbercovicirm_work: correct14:45
jorgemenikanorov: Correct, I think we are in agreement14:45
enikanorov_jorgem: operator API is another big story, but probably less complex and requiring less discussions14:45
bloganenikanorov: i agree everyone's concerns should be accounted for, but I'm still worried that just because there has been a surge in interest lately in this product and a lot of us are new, our opinions will not be accounted for14:45
*** garyk has quit IRC14:45
sballerm_work, You can vote +1 but you cannot approve +2. Only core members can +214:46
rm_workblogan: we just need to do an actual vote. so far we've just been in discussion mode, but it looks like the time for that has ended14:46
enikanorov_blogan: we're trying to account for them14:46
jorgemenikanorov: Hmm, operating at a large scale like we do here at Rackspace comes with all sorts of new issues though.14:46
rm_worksballe: right, but we won't be "unheard" :)14:46
mesteryblogan: We'll make sure we let everyone have a say for sure!14:46
sballerm_work, Agreed :)14:46
jorgemenikanorov: I'd like to share those and address them. In the end it will really help everyone out I believe.14:46
mesteryjorgem: +114:47
*** doron is now known as doron_afk14:47
enikanorov_jorgem: on the operator side there are a bit of unresolved issues project-wise14:47
bloganthose are going to be the most difficult to solve14:47
samuelbercovicijorgem: please do it on https://docs.google.com/document/d/1Ewl95yxAMq2fO0Z6Dz6fL-w2FScERQXQR1-mXuSINis/edit?usp=sharing so at least for use cases we will have one place to look14:47
*** fnaval has joined #openstack-meeting14:47
enikanorov_but we can sort them out in parallel to tenant API14:47
samuelbercovicithe document is world wide edited14:47
jorgemenikanorov: But for now I agree on focusing on the user requirements makes sense. I don't want to broaden the discussion right now.14:47
enikanorov_yeah14:48
aburaschiIs it ok to use jorgem proposed link to unify documents and use cases?14:48
*** manishg has joined #openstack-meeting14:48
samuelbercoviciaburaschi: please do it on https://docs.google.com/document/d/1Ewl95yxAMq2fO0Z6Dz6fL-w2FScERQXQR1-mXuSINis/edit?usp=sharing so at least for use cases we will have one place to look14:48
mesteryI would really like us to move to gerrit for all of these things as fast as we can.14:48
blogani thought the uses cases will be pushed to neutron-specs14:48
jorgemaburaschi: By all means please!14:48
enikanorov_so, going back to use cases: I'd suggest we will discuss only those, which affect object model and API14:48
mesteryI'm fine with consolidating in gdoc for now, but moving to gerrit should be a priority quickly after that.14:48
sballejorgem, We have the same large operator agreements as you do and I agree taht we cannot dolve them al lin once. The focus on the APi makes a lot of sense to me as a first priority14:48
*** manishg_ has quit IRC14:48
bloganmestery: that should be an action itemt hat comes out of this meeting14:49
*** hashar has quit IRC14:49
*** IlyaE has joined #openstack-meeting14:49
aburaschisamuelbercovici, jorgem: ok, thanks! great.14:49
enikanorov_if it's TCP vs HTTP propotoc - that would not make much sense to discuss it, because implementaion will be mostly unaffected by decision14:49
sbalukoffWill the +1'ing we do on use cases be for individual use cases?  Will that work with gerrit?14:49
bloganmestery: that will make it a lot better14:49
sbalukoff(We're potentially look at dozens of different use cases.)14:49
mestery#action The team to consolidate use cases here: https://docs.google.com/document/d/1Ewl95yxAMq2fO0Z6Dz6fL-w2FScERQXQR1-mXuSINis/edit?usp=sharing14:49
*** 5EXAA26CG is now known as I15914:49
mestery#action The team to move the use cases to the neutron-specs repository before next week's LBaaS meeting.14:49
TrevorVenikanorov_: When reviewing the use-cases, many of them are not just differences in protocol...14:50
sballeTrevorV, +114:50
sbalukoffIt's also possible that some use cases will be mutually exclusive.14:50
enikanorov_TrevorV: yes, there are different types of cases. L7 switching for example introduces whle bunch of requirements for API and obj model14:50
enikanorov_*whole14:50
rm_worksbalukoff: I hope we don't run into that :(14:50
enikanorov_and that's the kind of cases it makes sense to discuss14:51
sbalukoffI can think of one off the top of my head. :)14:51
samuelbercovicisbalukoff: shhot :-)14:51
samuelbercovicishoot14:51
sballesbalukoff, let's hear it ;)14:51
rm_workI have not seen anything like that yet, fortunately… what is the one you are thinking of? I guess you can explain externally14:51
rm_workmight be better handled after this14:51
*** llu-laptop has joined #openstack-meeting14:52
*** belmoreira1 has joined #openstack-meeting14:52
*** llu-laptop has left #openstack-meeting14:52
*** dhuber has quit IRC14:52
sbalukoff"User needs to ensure that the password encrypting SSL key is not stored anywhere on disk and therefore needs to be prompted for a passphrase whenever the key is used."   "Operator needs to be able to automate service stops and starts"14:52
*** manishg has quit IRC14:53
*** zdiN0bot has joined #openstack-meeting14:53
enikanorov_ok, that's the use cases that out of our current scope, I'd say14:53
german_who decides scope?14:53
enikanorov_questions are important, but not now.14:53
enikanorov_german_: our topic14:53
*** ramishra_ has quit IRC14:53
enikanorov_which is tenant API and object model14:53
jorgemsbalukoff: Correct. Prompting for passphrase is not conducive to an API I would think.14:54
*** mrmartin_ has quit IRC14:54
sballesbalukoff, This sounds to me like it would involve integration with Barbican so to me it is an advanced features of the lB. it should still be in scope for LBaaS IMHO14:54
samuelbercovicisbalukoff: lets take it off line as although I understand this, I did not encountered it yet14:54
sbalukoffjorgem: Yeah, see that part of the SSL stuff in the wiki has been disturbing to me this whole time. ;014:54
enikanorov_sballe: it is in scope, but just let's do one thing at a time14:54
samuelbercovicisballe: correct14:54
sballeenikanorov, I agree14:55
*** belmoreira has quit IRC14:55
german_sballe +114:55
aburaschienikanorok_: +114:55
enikanorov_ok, we have few minutes left, lets talk about summit design tracks14:55
* mestery notes we're 5 minutes from this meeting being over.14:55
sballeenikanorov, I am just saying that we will have basic use cases and and advanced use cases and we can agree to tackle them at different times14:55
sbalukoffIn any case, this is just one possible case of conflict. And yes, we need a way to discuss how compromises are made in this case. If this can be done with gerrit, let's do it. I guess we'll see how well discussions work there.14:55
samuelbercovicisbalukoff: this was done to support directly provisioning the certificates without any store such as barbican14:55
aburaschienikanorov_14:55
mesteryAny other actionable items we want for the team or individuals this week?14:55
aburaschi+114:55
*** zhangleiqiang has quit IRC14:56
enikanorov_samuelbercovici and me have several topics to cover on those tracks14:56
jorgemShow workflows on how use cases fit in proposals14:56
rm_worksbalukoff: i assume you would comment on the specific use-case you had a problem with, -1 the whole thing, and a patchset would be proposed14:56
bloganim unclear as to what the API proposing teams are supposed to do? get their API proposals working with the current object model?14:56
enikanorov_if you feel something needs to be added, please send out to ML14:56
enikanorov_and we'll think on how to merge your proposals14:57
sballeblogan, I thouht the object-model was up for discussion too.14:57
mesteryI would strongly encourage feedback on gerrit as well.14:57
rm_worksballe: it is if we vote in gerrit that it is :)14:57
sbalukoffblogan: Action items so far include stuff around consolidating use cases and getting them into gerrit.14:57
mesteryConsolidating feedback there is actually quite nice and allows for fast iteration in addition.14:57
blogansballe: it is in gerrit, but thats why its unclear, the decision on that is the lynchpin for anything going forward14:58
*** llu-laptop has joined #openstack-meeting14:58
*** zdiN0bot has quit IRC14:58
*** eglynn has joined #openstack-meeting14:58
mesteryThe object model in gerrit is fair game for comments by any takers. :)14:58
enikanorov_mestery: got it14:58
sbalukoffWe're almost out of time. Shall we do summit-related discussion on mailing list?14:58
enikanorov_we'll amend the bp14:58
*** nacim has joined #openstack-meeting14:58
enikanorov_sbalukoff: i suggest so14:58
sballeblogan, agreed that is why I wanted to make sure we were still discussing hte object model. Making the APi work with the old object model doesn't make sense if it will change too14:58
german_+114:59
bloganmestery: i like having all of this in gerrit, i think it will streamline workflows14:59
*** idegtiarov has quit IRC14:59
mesteryblogan: +114:59
sballeblogan, +114:59
rm_workand actual voting will be transparent14:59
* mestery nods in agreement.14:59
*** gordc has joined #openstack-meeting14:59
sbalukoffHeh! I've got just to figure out gerrit, then. XD14:59
rm_workwhelp, good meeting everyone :)15:00
*** markwash has quit IRC15:00
enikanorov_sballe: old object model is refined as well per BP, do don't  worry!15:00
*** pcm_ has left #openstack-meeting15:00
*** yogeshmehra has quit IRC15:00
*** german_ has left #openstack-meeting15:00
mesteryThanks folks!15:00
aburaschiThank you all. Bye!15:00
enikanorov_ok, thanks every one for the meeting15:00
*** hvprash has left #openstack-meeting15:00
enikanorov_you made my fingers burn15:00
enikanorov_:)15:00
aburaschi:)15:00
enikanorov_#endmeeting15:00
sbalukoffThanks!15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Apr 24 15:00:46 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-04-24-14.01.html15:00
bloganin a good way?15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-04-24-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-04-24-14.01.log.html15:00
eglynn#startmeeting ceilometer15:01
openstackMeeting started Thu Apr 24 15:01:00 2014 UTC and is due to finish in 60 minutes.  The chair is eglynn. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: ceilometer)"15:01
openstackThe meeting name has been set to 'ceilometer'15:01
gordco/15:01
DinaBelovao/15:01
ildikovo/15:01
llu-laptopo/15:01
fabioHello!15:01
ityaptino/15:01
*** bbaby has left #openstack-meeting15:01
nealpho/15:01
*** baoli has quit IRC15:01
*** jorgem has left #openstack-meeting15:01
nsajeo/15:01
silehto/15:01
jd__o/15:02
eglynnwelcome all! ... the new timeslot seems to suit more peeps at a 1st glance15:02
ildikoveglynn: +1 :)15:02
_nadya_o/15:02
eglynn#topic summit scheduling15:02
*** openstack changes topic to "summit scheduling (Meeting topic: ceilometer)"15:02
*** sweston has joined #openstack-meeting15:02
dhellmanno/15:02
eglynnso the ceilometer track is gonna have 10 slots this time round15:02
eglynn(one less than either HK or Portland)15:03
*** dims has quit IRC15:03
*** berlin has quit IRC15:03
eglynnall day Wed plus morning slots on the Thurs15:03
prado/15:03
eglynn(clashing with Heat sessions unfortunately, but c'est la vie ...)15:03
nealphI count 18 proposals at this point...15:03
*** vivek-ebay has quit IRC15:03
*** nwidell has joined #openstack-meeting15:03
eglynnnealph: yeap, we're over-subscribed to the tune of circa 2:115:04
*** chandan_kumar has joined #openstack-meeting15:04
* nealph smells a consolidation coming15:04
eglynn... which is *good* as it shows interest in the project15:04
eglynnnealph: :)15:04
dhellmannnealph: those decisions are why the PTLs get paid the big bucks ;-)15:04
*** jay-lau-513 has quit IRC15:04
nealphriiiiight. :)15:04
ildikovwe had several shared slots in HK too, as I remember15:04
ildikovdhellmann: LOL :)15:04
eglynndhellmann: I only accept payment in the form of the finest craft beer ;)15:05
*** dims has joined #openstack-meeting15:05
eglynnyeah so the downside is the high contention for the available slots15:05
*** pablosan has joined #openstack-meeting15:05
eglynnthe ceilo core team has been working on a "collaborative scheduling" exercise15:05
eglynnI'll translate the output of that into something vaguely coherent on sched.org by EoW15:06
eglynnideally all these discussion would be done on gerrit in the open15:06
eglynnmaybe we'll get to that for Paris ...15:06
eglynnalso new for this summit ... there'll be a dedicated space for overflow sessions from each project track15:07
dhellmanneglynn: the source for the current proposal system is in git somewhere, so we could possibly add features15:07
*** ameade has joined #openstack-meeting15:07
eglynndhellmann: cool, let's think about far enough in advance of the K* summit15:07
* dhellmann nods15:07
eglynnsee https://wiki.openstack.org/wiki/Summit under "Program pods" for a short blurb on the pod idea15:08
*** nshaikh has quit IRC15:08
eglynn... inevitably the contention will result in us punting some of the session proposals to the pod15:08
*** ramishra has joined #openstack-meeting15:08
eglynn... we've also identified a bunch of candidate sessions for merging15:09
nealpheglynn:looking at the pod description...seems like some conversations would fit there well and others not so much15:10
nealphi.e. collaboration within ceilometer team yes, cross-team no15:10
eglynnnealph: yeap, that is true15:10
*** rakhmerov has joined #openstack-meeting15:10
nealphokay...guessing the core team has that in mind. :)15:10
eglynnnealph: cross-team also more likely to suffer from scheduling conflicts15:10
*** doron_afk is now known as doron15:11
eglynnnealph: ... yeah IIRC none of the punts are obviously cross-team proposals, so I think we're good on that point15:12
* nealph sighs15:12
*** ameade has quit IRC15:12
ildikoveglynn: I think so too15:12
eglynnnealph: sigh == "scheduling is hard" ?15:12
*** Leonr has joined #openstack-meeting15:13
nealphcool...appreciate the work core team is doing. excited to see the schedule. sighing because we always seem to conflict with heat. :)_15:13
*** blogan has quit IRC15:13
nealph(and was hoping to talk about tripleo) :)15:13
eglynnnealph: yeah I wasn't filled with joy about that either conflict either15:13
eglynnnealph: ... in previous summits heat and ceilo were kept apart because we had some pressing cross-project issues to discuss15:14
*** dane_leblanc has joined #openstack-meeting15:14
eglynn(i.e. autoscaling/alarming)15:14
*** rakhmerov has quit IRC15:14
*** zns has quit IRC15:15
*** coolsvap|afk is now known as coolsvap15:15
nealphperhaps I'm remembering wrong then...regardless, will be good sessions I'm sure.15:15
eglynnnealph: ... but yeah we've conflicted before also, I guess only so many ways to slice and dice the 4 days15:15
*** mspreitz has joined #openstack-meeting15:16
*** david-lyle has joined #openstack-meeting15:16
*** chandan_kumar has quit IRC15:16
eglynnBTW any cores who haven't fully filled in their prefs on the proposals (and want to get their say in), pls do so by EoD today15:16
eglynnmove on folks?15:17
*** mrodden has joined #openstack-meeting15:17
DinaBelova+115:17
eglynn#topic update on f20-based gating15:17
*** openstack changes topic to "update on f20-based gating (Meeting topic: ceilometer)"15:17
eglynnwe discussed this last week15:17
eglynnBTW https://review.openstack.org/86842 hasn't landed yet15:17
*** aburaschi1 has joined #openstack-meeting15:17
eglynnI suspect because the reviewer pulling the trigger on the +1 becomes unoffiical "nursemaid" for the new job15:18
ildikoveglynn:  at least it seems close to15:18
DinaBelovaso many +'s :)15:18
_nadya_HP doesn't have image as i understood15:19
DinaBelovaonly rackspace15:19
DinaBelovapossibly that's the reason15:19
_nadya_yep15:19
*** aburaschi has quit IRC15:19
eglynn_nadya_:  yeah, there was push-back from the infra guys on that redundancy issue15:19
*** imsurit has quit IRC15:19
*** bobmel has joined #openstack-meeting15:19
eglynn_nadya_: at the infra meeting, when you brought it up ... pushback away from f20, towards trusty, right?15:20
*** Mandell has joined #openstack-meeting15:20
*** ramishra has quit IRC15:20
_nadya_I guess the only thing we may do is to wait15:20
*** garyk has joined #openstack-meeting15:20
DinaBelovapossibly after summit we'll have ubuntu14/f20 - both will be cool for mongo15:20
* eglynn not entirely understanding the infra team's logic TBH15:21
*** afazekas has quit IRC15:21
eglynnnot on the image redundancy across HP & RAX clouds15:21
eglynn... more on the point that the TC decides distro policy for project, infra just implement it15:21
eglynnTC policy is ...15:21
_nadya_eglynn: jobs may run on hp-cloud or rackspace. it's not determined as I understand (maybe wrong)15:21
eglynn#link http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-01-08-20.02.html15:22
DinaBelova_nadya_, yes, that's true15:22
eglynn_nadya_: jobs need to be runnable on *both* clouds, or?15:22
DinaBelovathat's not determined15:22
*** vivek-ebay has joined #openstack-meeting15:22
_nadya_eglynn: yep15:22
DinaBelovaeglynn - if there is no image on HP -> jobs going to it will fail15:23
DinaBelovaand ok for rackspace15:23
eglynnDinaBelova: yep, agreed15:23
eglynnbut on the TC policy point, pasting here for reference ...15:23
eglynn"OpenStack will target its development efforts to latest Ubuntu/Fedora, but will not introduce any changes that would make it impossible to run on the latest Ubuntu LTS or latest RHEL."15:23
*** banix has joined #openstack-meeting15:24
*** garyk1 has joined #openstack-meeting15:24
eglynninfra interpretation is ...15:24
eglynn"basic functionality really ought to be done in the context of one of the long-term distros"15:24
*** garyk has quit IRC15:24
eglynnsounds like a tension between target-to-latest and gate-on-long-term-distros15:25
*** fnaval has quit IRC15:25
eglynndhellmann: ... were you around on the TC when that distro policy ^^^ was agreed?15:25
*** vivek-eb_ has joined #openstack-meeting15:26
*** fnaval has joined #openstack-meeting15:26
*** samuelbercovici has quit IRC15:26
eglynn... k, I'll take that discussion on the distro policy off-line15:27
eglynn... moving on15:27
dhellmanneglynn: no, I think that predates me15:27
DinaBelova:)15:27
dhellmannwe might have inherited that from the ppb15:27
eglynndhellmann: cool, I'll see if I can clarify with the infra folks at their next meeting15:28
dhellmanneglynn: good idea15:28
* eglynn doesn't want to be caught in the mongo-less gate situation again, so having alternative gate distros with latest version is goodness IMO15:29
eglynn#topic launchpad housekeeping15:29
*** openstack changes topic to "launchpad housekeeping (Meeting topic: ceilometer)"15:29
eglynnDinaBelova has identified a bunch of bugs & BPs in LP that need attention15:29
*** vivek-ebay has quit IRC15:29
eglynn(in terms of status relfecting reality)15:29
DinaBelova#link https://etherpad.openstack.org/p/ceilometer-launchpad-cleaning15:29
DinaBelovawell, yes15:29
ildikovmaybe we could have some periodic rounds on LP15:30
DinaBelovawhile surfing the launchpad it turned out that there are some things that should be fixed I guess15:30
eglynnyeah if anyone wants to pitch in and help with the bureaucracy ... we could divide and conquer15:30
*** cjellick has joined #openstack-meeting15:30
DinaBelovaildikov, well, there are triage-days in some of hte OS projects15:30
eglynnmaybe use DinaBelova's etherpad as a mutex?15:30
ildikovDinaBelova: sounds good15:30
*** fnaval has quit IRC15:30
ildikovDinaBelova: I thought somethings similar15:31
*** vivek-eb_ has quit IRC15:31
eglynni.e. if you're gonna attack a section, mark it on the etherpad so that you effort isn't duplicated?15:31
DinaBelovawell, so they are running 1-2 days a month if there is no much load15:31
DinaBelovatriage-days I mean15:31
*** dshulyak has quit IRC15:31
eglynnyeah, I'd be on for regular triage days in general15:32
ildikoveglynn, DinaBelova: or having a round robin schedule for cores and whoever wants to join for checking LP periodically15:32
ildikoveglynn: it was an issue earlier too15:32
ildikoveglynn: and I think it will be a continuous issue TBH15:32
DinaBelovaildikov, eglynn - it's up for you))15:32
DinaBelovathe solution I mean15:32
DinaBelova:)15:32
DinaBelovaand other core team members, sure)15:33
ildikovso I'm definitely on for triage-days or anything similar15:33
ildikovDinaBelova: thanks for the etherpad BTW15:33
eglynnmy preference is to avoid too much heavy-weigth scheduling of the core team's time15:33
DinaBelovaeglynn, please mark this as info - decision about triage days15:33
DinaBelovaildikov, np15:33
ildikovDinaBelova: in long term it will be not effective, but it will be good for now for a heads up for sure15:33
*** dshulyak has joined #openstack-meeting15:33
DinaBelovaildikov, I guess yes15:34
eglynn... as everyone has chaotic demands on their schedules, hard to make round-robin scheduling stick15:34
ildikoveglynn: sure, that's true also15:34
* jd__ used to triage NEW once a week at least :(15:34
DinaBelovafor now mess is huge :(15:34
*** Longgeek_ has quit IRC15:34
ildikoveglynn: it is a painful process anyway I think, no one likes administration...15:34
DinaBelovajd__, well, I guess it'll be great - as now there is a traffic jam really))15:35
eglynnjd__: right, I'll follow your lead and go with a once-a-week trawl15:35
gordcDinaBelova: i'll take a quick look through the list. thanks for building it.15:35
DinaBelovagordc, np15:35
*** imsurit has joined #openstack-meeting15:35
eglynn... and if anyone wants to also pitch in on a best-effort basis, that would be welcome also15:35
DinaBelovagordc, the main problem here is that there is also huge list of completely new bigs/bps15:36
DinaBelovaand I did not mention them here15:36
*** changbl has joined #openstack-meeting15:36
jd__you can't really clean BP i think because you can't even delete it, they just rot15:36
jd__s/it/them/15:36
DinaBelovawell, at least we may set priority for the almost merged things15:37
llu-laptopdoes launchpad has any advanced feature to help this kind of work?15:37
DinaBelovaas there are lots of them here too15:37
*** avishayb has quit IRC15:37
DinaBelovallu-laptop, don't think so15:37
llu-laptop:(15:37
*** mwagner_lap has joined #openstack-meeting15:37
eglynnwhat's the thought on moving to gerrit for blueprint review?15:38
eglynn... as was recently discussed for nova on the ML?15:38
*** yfried has joined #openstack-meeting15:38
ildikoveglynn: like nova-specs?15:38
dhellmann+115:38
eglynn... not a solution for existing BP cruft, but might prevent the accretion in the future15:39
*** belmoreira1 has left #openstack-meeting15:39
ildikoveglynn: +1 from me too15:39
*** 6JTAAFPHV has quit IRC15:39
*** I159 has quit IRC15:39
dhellmanniiuc, those nova specs all have a blueprint, too, and the reviews are only used to track changes to the implementation plan but not the status of the blueprint's implementation or schedule15:39
eglynn#action eglynn look into the mechanics of reviewing new BPs in gerrit15:39
llu-laptop+1, this15:40
DinaBelovaildikov, eglynn but please notice that that will also make load on the core reviewers even much15:40
ildikovon LP the outdate ones can be set to an invalid state or something like this15:40
DinaBelova... as it's now15:40
ildikovDinaBelova: sure, but at least the BPs will be finally reviewed15:40
DinaBelovaildikov, sure15:40
dhellmannDinaBelova: yes, true, but the tradeoff is that code reviews should be easier, because we would have agreed to the design in advance15:40
DinaBelovaand not appearing on the LP without the need15:40
DinaBelovadhellmann +115:41
eglynnDinaBelova: ... true enough, but we'd have to look at that extra upfront workload as an investment for the future15:41
ildikovdhellmann: +115:41
eglynnk, we're up against the shot-clock here so better move on15:41
*** mrmartin has joined #openstack-meeting15:41
llu-laptopb.t.w. does the approval of ceilometer-spec patch will be reflected on launchpad blueprint?15:41
eglynnllu-laptop: my understanding was that "approved" status would be gated on the gerrit review of the BP15:42
*** hemna_ has joined #openstack-meeting15:42
eglynnllu-laptop: ... as opposed to just being set on an ad-hoc basis15:42
*** evgenyf has quit IRC15:42
llu-laptopeglynn: got that, please move on15:43
eglynn#topic Tempest integration15:43
*** openstack changes topic to "Tempest integration (Meeting topic: ceilometer)"15:43
eglynn_nadya_: anything new to report?15:43
*** ssurana has quit IRC15:43
*** fnaval has joined #openstack-meeting15:43
DinaBelovabtw these patches are the following15:44
_nadya_no valuable updates. Postgres doesn't work quick enough too :(15:44
*** vivek-ebay has joined #openstack-meeting15:44
DinaBelova#link https://review.openstack.org/#/q/status:open+project:openstack/tempest+owner:vrovachev,n,z15:44
_nadya_DinaBelova: some became abandoned today or yesterday15:44
eglynnDinaBelova: so those patches are still effectively blocked from landing by the sqla performance issues?15:44
DinaBelovaalready restored)15:44
DinaBelovaeglynn, yes15:45
DinaBelovawe're blocked by the f20/ubuntu1415:45
DinaBelovawith mongo15:45
DinaBelovathat is working 30x times faster15:45
_nadya_we may move on to 'performance tests' :)15:45
eglynnk, so no change then until we sort out the sqla issues and/or gate the longer-running tests on mongo15:45
DinaBelova_nadya_, yes)15:45
_nadya_eglynn: yep15:46
DinaBelovaeglynn, yes, it looks so15:46
eglynnfair enough, so that dovetails nicely to the next topic15:46
eglynn#topic Performance testing15:46
*** openstack changes topic to "Performance testing (Meeting topic: ceilometer)"15:46
eglynnityaptin: the floor is yours, sir!15:46
ityaptinhow you known we started perfomance testing15:47
*** rakhmerov has joined #openstack-meeting15:47
*** mspreitz has quit IRC15:47
DinaBelova#link https://docs.google.com/document/d/1ARpKiYW2WN94JloG0prNcLjMeom-ySVhe8fvjXG_uRU/edit?usp=sharing15:47
ityaptinwe tests mysql, mongo, hbase - it's standalone backends and habse cluster on VMs15:47
eglynnityaptin: it was on the meeting agenda and discussed on the IRC channel yesterday15:48
*** comay has joined #openstack-meeting15:48
*** bobmel has quit IRC15:48
*** ivasev has joined #openstack-meeting15:48
*** vivek-ebay has quit IRC15:48
ityaptinAnd I guess all core reviers to take look on this document15:48
*** marekd is now known as marekd|away15:48
*** ominakov has quit IRC15:49
DinaBelovaas currently we got feedback from you, eglynn, I guess and that's it15:49
DinaBelovaI mean from core team15:49
ityaptintests results of mysql shows what it's work more than 30 times slower than hbase or mongo15:49
DinaBelovadhellmann, ildikov, jd__, gordc ^^15:49
ildikovityaptin: I think it will be very useful after having the revised SQL models, etc15:49
eglynnDinaBelova, ityaptin: so I was also wondering if the test harness used to generate the load was up on github or somewhere similar?15:50
dhellmanndoes that include any tuning of mysql itself? or changes to our indexes?15:50
ityaptinildikov, yes)15:50
ildikovso we can compare how much the situation is better15:50
*** garyk1 has quit IRC15:50
_nadya_to evaluate "new model" we need results for the old one. to compare15:50
eglynnityaptin: ... having the loadgen logic in the public domain would be really useful for anyone following up on your results15:51
ityaptineglynn, not yet) but I can, if you want)15:51
_nadya_dhellmann: no, no tuning15:51
*** Alexei_987 has joined #openstack-meeting15:51
eglynnildikov: excellent, that would be great!15:51
DinaBelovaityaptin, I guess it'll be anyway better to share it15:51
*** blogan has joined #openstack-meeting15:51
eglynnityaptin: ^^^15:51
*** megan_w|afk is now known as megan_w15:51
eglynndarned tab completion of irc nicks!15:51
DinaBelovaokay, and one more time - core team - please take a look on the results15:51
DinaBelovaand please propose your own cases/ideas15:52
ildikoveglynn: np ;)15:52
*** beagles is now known as beagles_brb15:52
DinaBelovaas ityaptin is going to continue this work15:52
dhellmann_nadya_: it would be useful to have some profiling info about what part of the sql driver is so slow, to see if tuning helps15:52
*** julien-llp has joined #openstack-meeting15:52
_nadya_so the main plea is "please tell us what results do you want to see"15:52
*** samuelbercovici has joined #openstack-meeting15:52
dhellmannmongo was really slow at one point, until we improved the indexes there15:52
*** mspreitz has joined #openstack-meeting15:53
*** samuelbercovici has quit IRC15:53
ityaptindhellmann, I'll try to find bottleneck in mysql15:53
*** markmcclain has quit IRC15:53
_nadya_dhellmann: ok, will take that into account15:53
gordcDinaBelova: this is with a single worker?... i get the feeling sql will never work unless with multiple workers (it was consistently 10x slower for me)15:53
DinaBelovagordc, yes single one for now15:53
*** zdiN0bot has joined #openstack-meeting15:53
llu-laptopgordc: there is a 3-collector setup15:54
DinaBelovagordc, ityaptin is planning to try other variant too15:54
ildikovdhellmann: did you mean there SQLAlchemy as driver?15:54
ityaptindhellman, if we have some results, it will be shown15:54
eglynnDinaBelova, ityaptin, _nadya_: any ideas on the cause of the saw-tooth pattern observed in time-per-message for hbase as the load is scaled up in the 3-collector case?15:54
*** MarkAtwood has joined #openstack-meeting15:54
ityaptinwe had 2 ideas:15:55
dhellmannI wonder if there's a more efficient way to implement _create_or_update() in that sql driver15:55
eglynn... i.e. the semi-regular spikes in the time-per-message15:55
ityaptin1) It's connection pool size in hbase and mongo. It is not true.15:55
gordcthe api response time are concerning. especially for only 100k samples... i was testing with 1million and it was comparable/better than that on sql.15:55
*** rakhmerov has quit IRC15:56
ildikov_create_or_update was changed not so long ago or it was just planned to be changed?15:56
ityaptinwe test different poolsizes in hbase and all results have same pattern15:56
*** bobmel has joined #openstack-meeting15:56
gordcdhellmann: i'd hope to drop the _create_or_update logic... the update option is a bottleneck.15:56
_nadya_eglynn: ityaptin speaking about 1-collector case15:56
ityaptin2) greenpool size15:56
dhellmanngordc: yeah15:56
*** zns has joined #openstack-meeting15:57
ityaptingrenn pool size is not tested yet.15:57
_nadya_eglynn: there is a peak there with 400 m/s. Regarding 3-collectors case I don't know the answer yet15:57
*** mspreitz_ has joined #openstack-meeting15:57
gordcfyi, this is the etherpad i created for ceilometer reschema session: https://etherpad.openstack.org/p/ceilometer-schema15:57
*** mspreitz has quit IRC15:57
eglynn_nadya_: k15:57
*** mspreitz_ is now known as mspreitz15:57
*** zdiN0bot has quit IRC15:58
_nadya_eglynn: actually we don't tune hbase yet. only schema optimization15:58
*** jlibosva has quit IRC15:58
*** otherwiseguy has joined #openstack-meeting15:58
DinaBelovaok, any questions here? as that's close to the end of the meeting15:58
eglynngordc: yeah re. API responsiveness, the "was 141.458 a typo or in seconds?" comment is revealing15:58
*** vivek-ebay has joined #openstack-meeting15:59
*** bobmel has quit IRC15:59
eglynn... that sounds unusable as an API15:59
ityaptin:(15:59
*** mspreitz has quit IRC15:59
DinaBelovaeglynn, yeah...15:59
gordceglynn: agreed..especially for such a small set.15:59
eglynn... would cause an LB or haproxy to drop the connection long before the API call completes :(15:59
eglynnright, we a lot of work to do on performance16:00
*** lsmola has quit IRC16:00
eglynnbut we're outta time now16:00
DinaBelovaeglynn, +116:00
eglynnlets continue the discussion in ATL16:00
eglynnthanks folks! ... let's close now16:00
DinaBelovabye16:01
eglynn#endmeeting ceilometer16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Thu Apr 24 16:01:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-04-24-15.01.html16:01
fabiobye16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-04-24-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-04-24-15.01.log.html16:01
*** fabio has quit IRC16:01
ildikovthanks all, bye16:01
*** mlavalle has joined #openstack-meeting16:01
*** llu-laptop has quit IRC16:01
*** Alexei_987 has left #openstack-meeting16:01
*** ygbo has quit IRC16:01
*** dims has quit IRC16:03
*** overlayer has joined #openstack-meeting16:03
*** vjay has quit IRC16:03
*** jlibosva has joined #openstack-meeting16:04
*** sweston has quit IRC16:05
*** ramishra has joined #openstack-meeting16:05
*** gordc has left #openstack-meeting16:06
*** julien-llp has left #openstack-meeting16:06
*** dims has joined #openstack-meeting16:06
*** matiu_ has quit IRC16:06
*** matiu_ has joined #openstack-meeting16:07
*** devlaps has joined #openstack-meeting16:08
*** manishg has joined #openstack-meeting16:08
*** krtaylor has quit IRC16:08
*** baoli has joined #openstack-meeting16:09
*** xuhanp has quit IRC16:10
*** manishg has left #openstack-meeting16:10
*** eghobo has joined #openstack-meeting16:11
*** nwidell has quit IRC16:11
*** bauzas has quit IRC16:12
*** Qiming has quit IRC16:12
*** hashar has joined #openstack-meeting16:12
*** matiu_ has quit IRC16:12
*** aburaschi1 has quit IRC16:13
*** bdpayne has joined #openstack-meeting16:13
*** jaypipes has quit IRC16:13
*** ndipanov has quit IRC16:14
*** Mandell has quit IRC16:14
*** _afazekas_away is now known as afazekas16:14
*** marcoemorais has joined #openstack-meeting16:17
*** dims has quit IRC16:17
*** TrevorV has left #openstack-meeting16:17
*** dims has joined #openstack-meeting16:17
*** zns has quit IRC16:18
*** aburaschi has joined #openstack-meeting16:18
*** ramishra has quit IRC16:19
*** nacim has quit IRC16:21
*** ramishra has joined #openstack-meeting16:22
*** rakhmerov has joined #openstack-meeting16:22
*** Zhou_Yu has joined #openstack-meeting16:23
*** eguz has joined #openstack-meeting16:23
*** rakhmerov has quit IRC16:24
*** rakhmerov has joined #openstack-meeting16:24
*** aburaschi has quit IRC16:24
*** chandan_kumar has joined #openstack-meeting16:25
*** jgallard has quit IRC16:25
*** gyee has joined #openstack-meeting16:26
*** eghobo has quit IRC16:27
*** sbalukoff has quit IRC16:27
*** rakhmerov has quit IRC16:28
*** vuil has joined #openstack-meeting16:28
*** rakhmerov has joined #openstack-meeting16:28
*** vuil has quit IRC16:31
*** zns has joined #openstack-meeting16:32
*** gokrokve_ has joined #openstack-meeting16:32
*** rakhmerov has quit IRC16:33
*** zehicle_at_dell has joined #openstack-meeting16:33
*** ramishra has quit IRC16:33
*** gokrokve has quit IRC16:36
*** vjay has joined #openstack-meeting16:41
*** troy_psx has quit IRC16:41
*** jlibosva has quit IRC16:43
*** tris has quit IRC16:43
*** aburaschi has joined #openstack-meeting16:44
*** zns has quit IRC16:45
*** zns has joined #openstack-meeting16:46
*** marun_ has joined #openstack-meeting16:46
*** ameade has joined #openstack-meeting16:46
*** marun has quit IRC16:47
*** marun_ is now known as marun16:47
*** crc32 has joined #openstack-meeting16:47
*** tris has joined #openstack-meeting16:48
*** hashar has quit IRC16:50
*** garyk has joined #openstack-meeting16:50
*** harlowja_away is now known as harlowja16:51
*** _nadya_ has quit IRC16:52
*** garyk has quit IRC16:53
*** aburaschi has quit IRC16:54
*** tosky has joined #openstack-meeting16:54
*** zdiN0bot has joined #openstack-meeting16:54
*** overlayer has quit IRC16:55
*** Mikhail_D_ltp has joined #openstack-meeting16:55
*** shardy is now known as shardy_afk16:57
*** jpeeler has quit IRC16:58
*** Zhou_Yu has quit IRC16:58
*** jpeeler has joined #openstack-meeting16:59
*** jpeeler has quit IRC16:59
*** jpeeler has joined #openstack-meeting16:59
*** zdiN0bot has quit IRC16:59
*** jasonhullinger has joined #openstack-meeting16:59
*** crc32 has quit IRC16:59
*** malini1 has joined #openstack-meeting17:00
mtreinish#startmeeting qa17:00
openstackMeeting started Thu Apr 24 17:00:58 2014 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** rockyg has joined #openstack-meeting17:01
*** openstack changes topic to " (Meeting topic: qa)"17:01
openstackThe meeting name has been set to 'qa'17:01
*** zns has quit IRC17:01
mtreinishhi who do we have here today?17:01
marunhi17:01
mlavallehi17:01
*** rossk has joined #openstack-meeting17:01
mtreinish#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_April_24_2014_.281700_UTC.2917:01
*** sweston has joined #openstack-meeting17:01
andreafhi17:01
mtreinish^^^ Today's agenda17:01
dkranz hi17:01
sdagueo/17:02
*** julien-llp has joined #openstack-meeting17:02
mtreinishmkoderer, afazekas: you guys around?17:02
afazekashi17:03
mtreinishwell let's get started17:03
*** s3wong has joined #openstack-meeting17:03
mtreinish#topic Oslo Liaison (mtreinish)17:03
*** openstack changes topic to "Oslo Liaison (mtreinish) (Meeting topic: qa)"17:03
mtreinishso I brought this up during last week's meeting17:03
*** zhiyan is now known as zhiyan_17:03
mtreinishbut I thought that'd I ask during the alternate time too17:04
*** otherwiseguy has quit IRC17:04
mtreinish#link https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons17:04
*** darraghb has quit IRC17:04
mtreinishthe oslo team is looking for a person to be a focal point on keeping up with oslo changes in the projects17:04
*** Michalik- has quit IRC17:04
*** thedodd has quit IRC17:04
mtreinishI think it would be good to have someone do that for tempest17:04
mtreinishdoes anyone want to volunteer?17:04
mtreinishok well I'll bug people in person at summit about it then :)17:05
mtreinishlet's move onto the next topic17:05
*** ipbabble has quit IRC17:05
*** whenry has quit IRC17:05
mtreinish#topic Summit sessions (mtreinish)17:05
*** openstack changes topic to "Summit sessions (mtreinish) (Meeting topic: qa)"17:05
mtreinish#link https://etherpad.openstack.org/p/Juno-QA-design-summit-topics17:05
*** thedodd has joined #openstack-meeting17:06
*** sweston has quit IRC17:06
mtreinishso we currently have only one extra session proposal17:06
mtreinishso we need to figure out which one we can drop17:06
*** SumitNaiksatam has quit IRC17:06
mtreinishI also rejected boris-42's rally w/ tempest proposal because it wasn't in the qa program. But, thinking about it might be a good idea to have that session17:07
dkranzmtreinish: Are "How to improve the UX of our testing tools:" and "Tempest GUI / Should we have a tempest GUI (in Horizon)?" similar?17:07
dkranzmtreinish: I think we should have the rally session17:07
marunux -> user experience17:07
marunnot necessarily ui17:07
mtreinishdkranz: I can combine them, but UX one was strictly about test tooling17:08
mtreinishlike the testr headaches17:08
dkranzmtreinish: ok17:08
sdaguehonestly, I'd rather give ux a whole block17:08
sdagueI think it would be good to talk through, and hopefully get some voluteers17:08
*** coolsvap is now known as coolsvap|afk17:08
sdagueespecially as I think testr will be on github around then17:08
mtreinishthe gui one is about making a tempest server which stores results and actually runs tempest with a client and a horizon plugin17:08
dkranzarguably rally should be part of the qa program17:08
mtreinishmasayuki had a cool little diagram17:08
dkranzmtreinish: ok17:08
*** gokrokve_ has quit IRC17:08
*** torandu has joined #openstack-meeting17:08
sdagueyeh, having a rally session would be interesting to talk that through and figure out the challenges in having it more part of the fold17:09
marunI'm wondering if the UX issue shouldn't be cross-project17:09
sdaguemarun: possibly, though that ship has sailed17:09
marunall projects suffer the same issues - the test tooling being suited more to running tests in ci than developing with them17:09
sdaguethe cross project sessions were set over a week ago17:09
marunah, fair enough17:09
mtreinishmarun: yeah it's too late for the cross project17:09
marunin that case, I hope I get to participate17:09
mtreinishand I'm fine with giving it a qa slot17:10
*** otherwiseguy has joined #openstack-meeting17:10
andreafdo we have anything about tempest outside of devstack / tempest for multinode which is functional to  --> tempest in toci?17:10
marunand +1 for scheduling it17:10
mtreinishmarun: well I can move it around a bit so it won't overlap17:10
mtreinishfor you hopefully17:10
marunmtreinish: awesome17:10
dkranzmtreinish: Maybe Marc's two could be combined?17:11
mtreinishandreaf: the closest one on that topic would be the gui one17:11
mtreinishdkranz: yeah I was thinking that17:11
*** ssurana has joined #openstack-meeting17:11
mtreinishthey are related17:11
mtreinishandreaf: masayuki's idea is about making tempest easy for operators17:11
dkranzmtreinish: One is kind of a sub-case of the other.17:11
mtreinishdkranz: yeah that's a better description because fuzz testing will use the negative framework17:11
sdaguemtreinish: so if we combine marc's 217:11
mtreinishthen it's drop 117:12
sdagueand we drop service debug, and bring in rally, does that make us good?17:12
mtreinishand I'll give up my service debug api one17:12
*** malini has joined #openstack-meeting17:12
dkranz+117:12
mtreinishyeah we should be all set then17:12
sdaguecool17:12
*** morganfainberg_Z is now known as morganfainberg17:12
mtreinishok, then the session list has been finalized, unless anyone has something else to add on it17:13
dkranzsdague: BTW, with regard to your branchless tempest item, has that idea been broadly accepted at this point?17:13
*** eglynn has quit IRC17:13
mtreinishI'll schedule things after the meeting17:13
sdaguedkranz: well, it's in effect17:13
dkranzsdague: :)17:13
sdagueI mostly got head nodding17:13
dkranzsdague: cool17:13
maruni would nod, but i don't actually understand the implications well enough17:13
sdaguewe'll find out the first time when someone tries to land juno specific test17:13
maruni'm looking forward to hearing more at summit17:14
*** paragan has quit IRC17:14
sdaguemarun: the qa-spec hopefully covers most of the major bits https://github.com/openstack/qa-specs/blob/master/specs/branchless-tempest.rst17:14
sdaguebut we'll definitely talk at summit17:14
*** Mikhail_D_ltp has quit IRC17:15
*** derekh has quit IRC17:15
mtreinishok, let's move onto the next topic17:15
marunsdague: cool17:15
mtreinish#topic Specs Review17:15
*** openstack changes topic to "Specs Review (Meeting topic: qa)"17:15
mtreinishok so we don't have any people who put there specs on the agenda for this week17:16
mtreinishwe've got a handful of open specs for review17:16
mtreinish#link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z17:16
mtreinishso if people could take a look when they get a chance that would be cool17:16
andreafmtreinish: I fixed syntax issues in my qa-specs, but I still have to address the comments17:17
mtreinishdoes anyone have a spec review that they would like to discuss?17:17
dkranzmtreinish: I have a question about my non-admin spec.17:17
mtreinishandreaf: ok17:17
mtreinishdkranz: ok, go ahead17:17
dkranzmtreinish: There was a comment from andreaf that we should have a network admin config option.17:17
*** ildikov has quit IRC17:18
dkranzmtreinish: And you and I had discussed removing the one for compute because it was not used.17:18
mtreinisha network admin config option? what does it specify?17:18
dkranzmtreinish: At some point hopefully tempest could have its own domain as an option for admin tests (some)17:18
sdaguedkranz: so there are 2 classes of admin that we need to worry about right?17:18
sdaguethere is *all* admin17:18
dkranzsdague: At least 217:18
sdagueand keystone admin17:18
dkranzsdague: Yes, and this is complicated because services don't really deal with this17:19
sdagueand in keystone v3 we could be admin of a domain17:19
andreafdkranz, mtreinish, sdague: for identity service there is an overall admin and a domain admin (with v3)17:19
*** chandan_kumar has quit IRC17:19
*** chandan_kumar has joined #openstack-meeting17:19
dkranzsdague: For example, should 'nova list --all-tenants' return *all* or all in the domain?17:19
sdagueandreaf: right17:19
andreafbut it is possible to define admin for services as well17:19
*** Mikhail_D_ltp has joined #openstack-meeting17:19
dkranzSo this will get complicated and need to be hashed out.17:19
dkranzBut I don't want this to get in the way of the capability to run non-admin now.17:20
sdaguedkranz: so I feel like we need @test.admin('....')17:20
sdaguethat specifies the kind17:20
sdagueof admin needed17:20
andreafsdague: the list of roles would be useful17:20
*** SumitNaiksatam has joined #openstack-meeting17:20
sdaguethe point of the qa-spec is to actually hash it out in advance so the implementation can be pretty straight forward :)17:20
afazekasThe '....' should be admin capabilities ?17:21
sdagueafazekas: yeh17:21
sdaguelike what it needs17:21
*** zns has joined #openstack-meeting17:21
mtreinishsdague: but how do we specify the valid things in the config file17:21
sdaguehonestly, I haven't thought that part all the way thorugh17:21
*** jamespage_ has joined #openstack-meeting17:21
dkranzsdague: ok, I will think a little more about this.17:21
*** jamespage_ has quit IRC17:21
sdaguethat's a good question, these should be clarified in the spec17:21
andreafroles and policies are heavily customizable and if we want tempest to be portable to real clouds we need something like list of roles a tests depends one17:22
dkranzsdague: The trouble  is that it is perfectly clear for what we have now.17:22
sdaguedkranz: not really, there are lots of different admin creds in our config17:22
dkranzsdague: It just doesn't work17:22
*** beagles_brb is now known as beagles17:22
*** whenry has joined #openstack-meeting17:22
dkranzsdague: So where should we draw the line?17:23
mtreinishandreaf: yeah but we need to have a way to tell tempest what it has so we can check the list of roles against it17:23
dkranzsdague: Wait until everything supports keystone v3 to do anything?17:23
sdaguedkranz: we can cut at keystone admin and service admin today17:23
sdaguehonestly, I feel like we can dump all the service admins into a single bucket17:23
sdagueto begin with17:24
dkranzsdague: ok, I'm good with that.17:24
afazekasandreaf: there are to many capabilities defined in the services, and possible capabilities (in the policy.jsons)  are frequently changing17:24
dkranzsdague: It is a very small change from what I had17:24
sdaguedkranz: but we should have sample syntax on the decorator17:24
sdaguein the spec17:24
andreafsdague, dkranz: we could introduce service admin roles in devstack17:25
sdaguewe could17:25
sdaguehonestly, lets make this spec clear enough for someone to implement17:25
sdaguebecause right now, it's still missing some details, as seen by this conversation17:25
andreafsdague: ok - that's perhaps a dofferent spec - to have something more complex that a single admin to rule them all17:26
*** vjay has quit IRC17:26
sdaguewe also have to address tenant isolation in non admin environment17:26
sdagueI feel like that's still missing, and maybe it's not actually dkranz's spec, but it needs to happen soon17:27
sdaguebecause we need to stop running serial, as it keeps hiding bugs17:27
sdagueeven in non admin environments17:27
*** mattgriffin has quit IRC17:27
mtreinishsdague: we depend on domains for that right?17:27
mtreinishwhich means we have to land the v3 auth stuff first17:27
sdaguewe don't need to17:27
*** sbalukoff has joined #openstack-meeting17:27
*** thedodd has quit IRC17:28
sdaguewe can do it with preallocted users17:28
*** vjay has joined #openstack-meeting17:28
sdaguewhich, honestly, a service provider would probably find much more palatable17:28
mtreinishso we set the concurrency = the number of predefined tenants17:28
*** rakhmerov has joined #openstack-meeting17:28
mtreinishthat's an interesting sync problem between putting something in the conf file and using it in the .testr.conf17:29
mtreinishunless we leave it up to the user to do it correctly17:29
mtreinishsdague: but yeah I feel like that's a different spec17:30
dkranzsdague: These are all good ideas. I mentioned some of this in the spec but did not think we were going to address the whole ball of wax right now.17:30
afazekasMaybe some should ask for good practices for v3  roles and admin users and policies... on the ML17:30
sdagueafazekas: good thought17:30
sdagueafazekas: you want to send that out?17:30
*** aburaschi has joined #openstack-meeting17:30
afazekassdague: I would recommend a better writer :)17:31
*** gyee has quit IRC17:31
andreafafazekas: I can try if you want, not that my english is fantastic though :D17:31
*** mattgriffin has joined #openstack-meeting17:31
*** akuznetsov has quit IRC17:32
afazekasandreaf: thx17:32
mtreinish#action andreaf to write a ML post asking about good v3 keystone practices17:32
*** mrodden has quit IRC17:32
dkranzmtreinish: I thought about the multiple users but am not sure how the testr processes get mapped.17:32
*** akuznetsov has joined #openstack-meeting17:32
*** Gordonz has joined #openstack-meeting17:32
mtreinishdkranz: I actually made a mistake above, the concurrency is set in the cli for testr17:33
mtreinishby default it equals # cpus17:33
dkranzmtreinish: Yes but we have to map to user/tenant names somehow17:33
*** rakhmerov has quit IRC17:33
*** sankarshan is now known as sankarshan_away17:33
sdagueso I guess this actually opens up a meta question17:33
dkranzmtreinish: which means each tempest process has to have a different config17:33
sdaguewe clearly have a longer list of things that we want in tempest17:33
mtreinishdkranz: not necessarily17:34
sdaguethat none of the most active people are working through yet17:34
sdaguethis as a good example17:34
sdaguewhat would be a good mechanism for listing / signalling these wants17:34
dkranzsdague: I suggest allowing "specs" that are not fully formed and do not yet have an implementer17:35
andreafsdague: perhaps the qa-specs are17:35
*** eguz has quit IRC17:35
andreafdkranz: +117:35
mtreinishsdague: I'm not sure we could keep an etherpad, because it's kinda nebulous17:35
sdaguemtreinish: yeh, etherpad seems not good17:35
dkranzsdague: But we need to use a collaboration tool, not gerrit to flesh them out. Google docs for example.17:36
sdaguewhat about a single page list in qa-specs ?17:36
sdaguebasically paragraph level description17:36
dkranzsdague: pointing to google docs?17:36
*** eghobo has joined #openstack-meeting17:36
sdagueno, not pointing to google docs :)17:36
*** mrodden has joined #openstack-meeting17:36
sdaguein qa-spec17:36
mtreinishsdague: so a spec with a list of TODO things17:36
dkranzsdague: ok, but how do we collaboratively evolve them? gerrit sucks for this.17:37
sdaguelike a TODO.rst (better name tbd)17:37
sdaguedkranz: I actually like gerrit for this17:37
*** tosky has quit IRC17:37
*** thedodd has joined #openstack-meeting17:37
sdaguewhat are the concerns you have with gerrit on this?17:37
mtreinishdkranz: when someone is ready to implement it we break it off into it's own spec17:37
dkranzsdague: It does not support multiple writers17:37
*** zehicle_at_dell has quit IRC17:37
sdaguedkranz: you can just grab the review and push your own rev17:37
dkranzsdague: I know. But we are moving to the kind of process that zillions of people use, and there are tools designed for that.17:38
dkranzsdague: Not code review systems17:38
dkranzsdague: I don;'t think we should argue about this now.17:38
sdaguedkranz: do you think that zillions of people with simultaneous cursors makes it more clear?17:38
sdague:)17:39
sdaguethat's fine17:39
*** ScottCarlsonPP has joined #openstack-meeting17:39
mtreinishsdague: why don't you take it to the ML?17:39
sdagueok, so tabling that17:39
sdaguesure17:39
dkranzsdague: not simultaneous, though I have done that :)17:39
mtreinishbecause I'm sure other people have ideas on this17:39
sdagueyep17:39
sdagueaction me up17:39
mtreinish#action sdague to send a ML post about how to maintain a list of TODO items17:40
dkranzsdague: sorry, I meant zillions of users across all things done, not zillions on a single document17:40
*** blogan has left #openstack-meeting17:40
*** epim has joined #openstack-meeting17:40
mtreinishok, is there anything else on specs review?17:40
*** gokrokve has joined #openstack-meeting17:40
*** mrodden1 has joined #openstack-meeting17:41
mtreinishok then moving on17:41
mtreinish#topic Blueprints17:41
*** openstack changes topic to "Blueprints (Meeting topic: qa)"17:41
*** mrodden has quit IRC17:41
mtreinishjulien-llp: you had a bp on the agenda that you wanted to talk about17:41
julien-llpyes, hi everyone17:41
mtreinishjulien-llp: ok, go ahead17:42
julien-llpatthe moment this blueprint is waiting in the code review system and I thought that it could be a good idea to discuss a bit about it's relevancy17:42
mtreinish#link https://blueprints.launchpad.net/tempest/+spec/stress-test-ssh-floating-ip17:42
julien-llporiginally this blueprint was meant to implement a stress test for checking the capability of a stack to launch (have ahve fully availabl for a user) a large number of servers17:43
*** jtomasek has joined #openstack-meeting17:43
*** _nadya_ has joined #openstack-meeting17:43
mtreinishjulien-llp: you need to open a spec on qa-specs for the bp. We moved to a new process for bps17:43
julien-llpfor the time being (and with my comprehension of tempest growing), I believed that this test can be used not only for in house stress tests but also a a non-regression test scenario17:43
mtreinishjulien-llp: https://github.com/openstack/qa-specs/blob/master/README.rst17:43
julien-llpoh, ok, I'm not accustomed to this process by now :)17:44
*** crc32 has joined #openstack-meeting17:44
mtreinishjulien-llp: we just started it for juno17:44
julien-llpallright, I will add it to this document so17:44
mtreinishjulien-llp: so you want to take your stress test and make it a normal scenario test17:44
mtreinish?17:44
julien-llpI implemented it that way, yes17:45
*** marekd|away is now known as marekd17:45
*** paulmo has joined #openstack-meeting17:45
*** rellerreller_ has joined #openstack-meeting17:45
*** krtaylor has joined #openstack-meeting17:45
mtreinishoh I looked at the code review I understand now17:45
*** rellerreller_ has left #openstack-meeting17:45
mtreinishyou can just make that an api test17:45
julien-llpI believe this is relevant to test some small batches of instances since it's a fairly common use case, and once upun a time there was somes issues in Openstack about this17:45
mtreinishand use the decorator to use it in the stress suite17:45
mtreinishping me after the meeting and we can discuss it on -qa17:46
julien-llpallright17:46
mtreinishok does anyone else have any bp to discuss?17:46
andreafyes17:46
sdaguebranchless tempest is going well17:46
mtreinishandreaf: ok, go ahead17:46
sdaguewe're enforcing correctly on icehouse, and seem to have all the major holes covered17:46
andreafmulti-auth17:47
mtreinishsdague: cool17:47
mtreinishsdague: have we had any backports merged with the new process?17:47
*** jprovazn has quit IRC17:47
sdaguenot yet, realistically the code queues are slow right now17:47
andreafI rebased the pending changes and addressed comments, and also I fixed the unit tests forhttps://review.openstack.org/#/c/82911/ so  there are about 8 patchset available now17:47
*** zns has quit IRC17:48
mtreinishandreaf: ok cool, I'll try to take a look at them today17:48
andreafso next step I started working on is provide support for v3 in scenario tests, but I hit an issue17:48
mtreinishv3 support in the clients right? :)17:48
andreafthe problem is I can create most client with token and url17:49
andreafbut what if the token expires?17:49
andreafwe would need a way to globally handle 401 from clients, similar issue as with handling of rate limiting17:49
andreafthe only solution I can think of is to get that implemented in the clients - so to get v3 in the clients17:50
afazekasandreaf: the token's lifetime is 24h by default, A test case does not runs for more than 10 minute17:50
andreafunless someone has any good idea on this17:50
sdagueafazekas: the token lifetime is now 1h17:50
sdagueby default17:50
sdaguewhich is why we started tripping it17:50
mtreinishafazekas: also we can't assume the default lifetime either17:50
andreafsdague, afazekas: yes I did not want to make that assumption17:51
dkranzsdague: Why can't devstack just set it to a larger number by default?17:51
*** marekd is now known as marekd|away17:51
sdaguedkranz: that doesn't solve real clouds17:51
dkranzsdague: At least in the gate.17:51
sdaguewe should address this17:51
sdagueandreaf: is it possible to handle this as a decorator around the clients17:51
sdagueif that exception comes up, redo the auth, then redo the call?17:52
andreafwell monkey patching the client17:52
*** IlyaE has quit IRC17:52
dkranzYes, that was previously proposed for rate-limiting17:52
*** nati_ueno has joined #openstack-meeting17:52
afazekasCan you use a still valid token to get new one ?   Can we have our manager to request new token if it would expire in 5 minute ? Do we really want to support the case when the tokens lifetime is smaller then 10 minute ?17:53
andreafthe client would redo the auth call now, but if I only give them token and service url they can't17:53
sdagueandreaf: oh, this is because of official clients?17:53
marunmaybe the auth code should be common across libraries and reusable by tempest?17:53
mtreinishandreaf: can you generate a token using v3 with keystone client?17:53
andreafthey would need to go to the auth provider and ask for a new token17:53
*** elo has left #openstack-meeting17:53
andreafmtreinish: yes that's what I'm doing17:53
marunor is there some benefit from tempest having its own implementation?17:53
*** elo has joined #openstack-meeting17:54
mtreinishandreaf: so why not catch the exception regen the token with keystone client and pass that to a new client17:54
sdaguemarun: mostly for the same reason we have our own implementation of everything, otherwise people tend to code around server bugs17:54
mtreinishor a new instance of the client17:54
andreafyes17:54
marunsdague: uh17:54
marunsdague: if you're testing keystone, fine17:54
dkranzSounds like we need a proxy for the official clients17:54
marunsdague: but i don't see why any other service would have to use custom coding17:54
sdaguemarun: which is one of the things we have to do anyway17:55
marunsdague: *sigh*17:55
andreafit would be good if the client could be given a call back to an auth provider17:55
marunsdague: I hope I live to see mechanically-generated clients.17:55
andreafhttps://review.openstack.org/9016617:55
marunsdague: this constant make-work nonsense offends my delicate sensibilities17:55
sdagueheh17:55
mkodererhi folks, sry for being late :(17:56
andreafI just published the code I'm working on - if anyone has good ideas on how to handle this please let me know - else we shall wait for clients to support v3 or an external auth provider17:56
*** zns has joined #openstack-meeting17:57
mtreinishandreaf: ok I'll take a look at that, I think we can discuss this in review or on -qa17:57
sdagueandreaf: cool, is this something that will come up in a summit session?17:57
*** sushils_ has quit IRC17:57
sdague2 minutes17:58
andreafsdague: it could be relevant for the matrix one17:58
*** acoles is now known as acoles_away17:58
*** doron is now known as doron_afk17:58
*** Gordonz has quit IRC17:58
andreafsdague: I'll check if it can fit somewhere17:58
*** coreywright is now known as coreywright_17:58
mtreinishok, well with <2 min let's get a list of reviews from people and close17:58
mtreinish#topic critical reviews17:58
*** openstack changes topic to "critical reviews (Meeting topic: qa)"17:59
*** thedodd has quit IRC17:59
mtreinishso does anyone have any reviews that they'd like to get eyes on?17:59
mlavallehttps://review.openstack.org/#/c/60008/17:59
*** natedmac has joined #openstack-meeting17:59
*** hgedikli has joined #openstack-meeting17:59
*** doron_afk has quit IRC17:59
mtreinishok, well that's time18:00
*** shohel02 has joined #openstack-meeting18:00
mtreinishthanks everyone18:00
afazekashttps://review.openstack.org/#/c/90100/ some of SSH connection issue happens because the instance fails to initialize the timer (kernel boot) http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIk1QLUJJT1MgYnVnXCIgQU5EIHRhZ3M6XCJjb25zb2xlXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTgzNTk2NTYwODEsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiI18:00
afazekasn0=18:00
mtreinish#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Apr 24 18:00:22 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-04-24-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-04-24-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-04-24-17.00.log.html18:00
*** dane_leblanc has quit IRC18:00
*** arnaud has joined #openstack-meeting18:00
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu Apr 24 18:00:39 2014 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:00
openstackThe meeting name has been set to 'openstack_security_group'18:00
bdpaynegreetings everyone18:00
ScottCarlsonPPHello18:00
bknudsonbdpayne: hi18:00
bdpayne#topic Rollcall18:01
*** openstack changes topic to "Rollcall (Meeting topic: OpenStack Security Group)"18:01
*** nkinder has joined #openstack-meeting18:01
shohel02hi18:01
nkinderhi all18:01
bknudsonhi18:01
paulmoPaul Montgomery18:01
torandupart18:01
malini1hello!18:01
*** torandu has left #openstack-meeting18:01
*** vivek-ebay has quit IRC18:01
*** thedodd has joined #openstack-meeting18:01
ScottCarlsonPPScott @ PayPal18:01
* hyakuhei here :D18:01
hyakuheiHey malini1 !18:01
*** vivek-ebay has joined #openstack-meeting18:01
*** sweston has joined #openstack-meeting18:01
bdpaynehi everyone, thanks for joining today18:01
jasonhullingerand here18:01
bdpayne#topic Agenda18:01
*** openstack changes topic to "Agenda (Meeting topic: OpenStack Security Group)"18:01
*** chair6 has joined #openstack-meeting18:02
bdpayneAnything that people would like to add to the agenda today?18:02
hgediklihere18:02
chair6howdy18:02
natedmacher18:02
*** ujuc has quit IRC18:02
natedmachere*18:02
*** andreaf has quit IRC18:02
hyakuheiBusy one today. I don't have much to update - other than I'm working on an update to the guide18:02
*** viraptor has joined #openstack-meeting18:02
bdpayneI can provide a brief status update on the book18:02
hyakuheiHas anything happened in the threat analysis this week?18:02
shohel02yes,18:03
bdpayneok, so we can talk about the threat analysis work too18:03
*** bill_az has joined #openstack-meeting18:03
*** jcoufal has joined #openstack-meeting18:03
shohel02we had a new template, not much outside18:03
bdpayneand we should do a review of open OSSNs18:03
*** CristianF has joined #openstack-meeting18:03
bdpayneanything else?18:03
CristianFHi Everybody18:03
bdpayneok, let's dive in18:04
bdpayne#topic Book updates18:04
*** openstack changes topic to "Book updates (Meeting topic: OpenStack Security Group)"18:04
bdpayneSo I've started coordinating the book update efforts18:04
hyakuheiCool! Man it hurts to edit this xml.18:04
bdpayneRight now I'm taking a little time to assess what needs to happen18:04
*** julien-llp has left #openstack-meeting18:04
bdpayneIf anyone has specific asks, please let me know18:04
bknudsonit shouldn't be painful to write docs18:04
bdpayneeither here, or just by email18:05
bknudsonis it the tool?18:05
bdpayneThe xml isn't bad... he just likes to complain ;-)18:05
hyakuheiSo there's probably a good tool to use but editing the files directly...18:05
hyakuheiHurts my (small) brain.18:05
bdpayneit is all in docbook18:05
nkinder...speaking of XML, I do want to talk about OSSN format18:05
ScottCarlsonPP@bdpayne we'd like to start to provide enterprise guidance around PCI and compliance, should we consider that part of the book or separate white paperish thing.18:05
bdpaynesure, we can talk OSSN in a few18:05
*** sweston has quit IRC18:05
bdpayneScottCarlsonPP that would be a nice addition to the compliance section of the book18:06
malini1bdpayne: need to make references to the glossay in the book text18:06
bdpayneperhaps you can send me an email to coordinate moving ahead on that contribution?18:06
*** nati_ueno has quit IRC18:06
bdpayne#action references the references in the book18:07
ScottCarlsonPPbdpayne will do18:07
hyakuheiScottCarlsonPP: There's plenty that can be added to the existing compliance section too, especially around PCI18:07
bdpayne#action ScottCarlsonPP to contact bdpayne about compliance updates in the book (PCI and enterprise compliance)18:07
bdpayne#action bdpayne to review state of glossary and references in the book18:07
*** mlavalle has left #openstack-meeting18:08
malini1what is everyone's feeling around: http://summit.openstack.org/cfp/details/8, "signing messages" to improve security of the rpc18:08
*** ssurana1 has joined #openstack-meeting18:08
*** MarkAtwood has quit IRC18:08
bdpaynehyakuhei did you mention you have a book update that you're working on?18:08
bdpaynemalini1 let's discuss that at the end18:08
bdpayneI'd like to keep us focused on the current agenda item atm18:08
malini1:-) yes18:09
hyakuheiyeah just this https://bugs.launchpad.net/openstack-manuals/+bug/131120418:09
uvirtbotLaunchpad bug 1311204 in openstack-manuals "Security Guide should discuss KSM impact" [High,Triaged]18:09
*** dane_leblanc has joined #openstack-meeting18:09
*** amcrn has joined #openstack-meeting18:09
bdpayneah fantastic18:09
bdpaynelet me know when you are ready for reviews there18:09
hyakuheiWill do, it'll need a few iterations of review, the writing is pretty crappy18:10
bdpayne#action hyakuhei is working on https://bugs.launchpad.net/openstack-manuals/+bug/131120418:10
bdpaynenp18:10
bdpayneany other book discussion today?18:10
*** ssurana has quit IRC18:10
nkindermy OSSN format stuff fits in with the book18:10
bdpayne#topic Moving to OSSN18:10
*** openstack changes topic to "Moving to OSSN (Meeting topic: OpenStack Security Group)"18:10
*** marcusvrn has quit IRC18:10
bdpayneok, let's cover some OSSN stuff18:10
nkinderI've been playing around with the best way to get the OSSNs to be published in an appendix of the book18:11
nkinderThis is going to require docbook XML, and that may just be the right format to write and commit them in18:11
bdpayneperhaps18:11
*** _nadya_ has quit IRC18:11
bdpaynecertainly the easiest18:12
nkinderThere is a docbook "article" type, and I've manually converted one note to try it out18:12
nkindernot the easiest for sure18:12
bdpayneotherwise, we could translate from a slightly less structured format into docbook18:12
nkinder...but, we need to have ways to translate18:12
bdpayneif we play it right, the docbook could then be converted into all of the formats that we need / want18:12
nkinderwe can use RST and translate to XML possibly too18:12
shohel02nkinder: OSSN currently in markdown format , it should be easy to covert docbook?18:12
bknudsonnkinder: can you post the docbook example somewhere?18:12
bknudsone.g., gerrit18:12
*** che-arne has quit IRC18:13
bdpaynehttp://johnmacfarlane.net/pandoc/18:13
bdpayne^^ converts from docbook to markdown and back again18:13
nkinderbknudson: I haven't yet, but I can.  I was still hashing through details with anne18:13
*** nati_ueno has joined #openstack-meeting18:13
nkinderbdpayne: ok, I'll take a look at that.  I would prefer to edit in markdown or RST or something other than XML18:13
*** Mandell has joined #openstack-meeting18:13
bdpayneso I would say either switch to docbook or explore tools to automate the conversion from markdown... if the later then we should validate that conversion using gerrit18:13
nkinderthe gate jobs can then ensure that convert properly, and publishing can convert and publish18:14
bdpaynenkinder, yes I agree and I think that sticking with markdown is a good idea18:14
*** nati_ueno has quit IRC18:14
bdpayneexactly18:14
bdpayne#action nkinder to explore conversion from markdown to docbook using the gate jobs18:14
nkinderI'll continue to hash out the right docbook end result with anne, then will figure out how we can translate18:14
*** zns has quit IRC18:14
shohel02thats would be great18:14
bdpayneso getting it in docbook is step118:14
bdpayneany thoughts on how to go from there to actually having it in the book appendix?18:15
nkinderIf we auto publish to the book, do we even need to publish on the wiki?18:15
shohel02i am currently coverting doc and xls to markdown format18:15
nkinderbdpayne: well, that's part of what I'm discussing with Anne.  There are ways to do an include, but we need to hash out the details.18:15
bdpayneI think that putting it on the wiki is handy18:15
bdpaynebut we should balance that against the amount of manual work18:16
nkinderbut the docs are on the wiki too18:16
bdpayneideally, I'd like an approved OSSN to auto publish to all the right places18:16
malini1+1 to also have on wiki instead of having to download full book18:16
nkinderWe would have to see what sort of auto wiki publishing is available.  Next steps after the book.18:16
bdpayneright but I'm not sure if people will look into the back of the book to find an OSSN18:16
nkinderWe still need to e-mail them out regardless18:16
bdpayne#action nkinder to continue to explore right path for integration of OSSNs into book appendix18:17
bknudsonhopefully there's a docbook rendering to text18:17
bdpaynewe render to html and to pdf by default18:17
bdpaynebut docbook can render to lots of different formats18:17
nkinderbknudson: or markdown to text if we write in markdown18:17
nkinderok, I have lots to explore here :)18:17
bdpayneindeed18:18
bdpaynethanks for taking this on nkinder18:18
nkindersure18:18
bdpayneare there any open OSSNs at this point?18:18
hyakuhei+1 - very useful18:18
nkinderThere are 218:18
nkinderone is owned by hyakuhei, the other has someone who was interested and then disappeared18:18
bdpaynehttps://bugs.launchpad.net/ossn18:18
bdpayneso which one needs an owner?18:19
nkinderSo one is up for grabs if anyone is interested - https://bugs.launchpad.net/ossn/+bug/126067918:19
uvirtbotLaunchpad bug 1260679 in cinder "Multiple drivers set insecure file permissions" [High,In progress]18:19
nkinderIt's a pretty easy one I think18:19
*** jcoufal has quit IRC18:19
nkinderany takers?18:19
malini1if easy, i shall take!18:20
bdpayneis everyone familiar with what is involved here?18:20
bdpayneok, thanks malini118:20
*** aburaschi has quit IRC18:20
nkindermalini: thanks!18:20
bdpaynefwiw, writing an OSSN is pretty easy and we have gentle reviewers ;-)18:20
bdpayneit's a great way to get involved18:20
hyakuheiWe could possibly do with a mini version of the 'GerritWorkflow' page18:20
*** malini has left #openstack-meeting18:20
malini1:-)18:20
nkindermalini1: I can help through the process if needed.  Just let me know.18:20
bdpayne#action malini1 to work on https://bugs.launchpad.net/ossn/+bug/126067918:21
uvirtbotLaunchpad bug 1260679 in cinder "Multiple drivers set insecure file permissions" [High,In progress]18:21
malini1thanks nkinder!18:21
bdpayneok anything else for OSSNs?18:21
bdpayne#topic Threat analysis update18:21
*** openstack changes topic to "Threat analysis update (Meeting topic: OpenStack Security Group)"18:21
bdpayneshohel02 could you provide an update for us?18:22
shohel02Yes, i have started to covert doc and XLS format to markdown format18:22
*** darraghb has joined #openstack-meeting18:22
*** nati_ueno has joined #openstack-meeting18:22
shohel02we think its an issue for reviewing and tracking18:22
bdpayneexcellent18:22
bdpayneyou may find that tool I linked earlier to be useful too18:22
shohel02https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Project_ThreatAnalysis_ComponentName_Number.md18:22
shohel02here is some sample18:23
shohel02https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/keystone/Formatted_Output/Keystone_ThreatAnalysis_TokenProvider_2.9.md18:23
shohel02https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/keystone/Formatted_Output/Keystone_ThreatAnalysis_HighLevel.md18:23
bdpayneexcellent18:24
shohel02Another thing is david,HP and our threat analysis involved people are planning to go through the threat process again18:24
shohel02that would be good reivew18:24
bdpaynesounds good18:24
bdpayneany other next steps?18:24
*** epim has quit IRC18:24
bdpayneor areas where you need help from the group?18:24
nkinderbknudson: has anyone on the keystone core side been reviewing the threat analysis?18:25
shohel02One of the step is after markdown complete help is required from keystone developers18:25
*** darraghb has quit IRC18:25
nkindershohel02: just for review, or anything else in particular?18:25
bknudsonnkinder: I believe I mentioned the auth_token threat analysis at the keystone meeting once18:25
shohel02here we need help18:25
shohel02thanks..18:26
bdpayneyeah, it would be great to get someone(s) from keystone core to be involved18:26
bdpayneto make sure that the ideas are represented accurately18:26
shohel02yes18:26
bdpayneand to perhaps just open a communication channel18:26
nkinderok, so a review at first, but I expect that some proposed improvements can come out of the analysis as well18:26
shohel02i think OSSG people can also review the threats and docs18:27
bknudsonI'm hoping things will settle down here soon so I can get more involved in security work18:27
*** rellerreller has joined #openstack-meeting18:27
*** rellerreller has left #openstack-meeting18:27
bdpayneyeah, and also to help keep the proposed improvements as things that are doable18:27
*** otherwiseguy has quit IRC18:27
*** epim has joined #openstack-meeting18:27
morganfainbergbknudson, I'm in the same boat.18:27
nkinderI think everyone is :)18:27
bdpayneheh18:27
bdpayneok, thanks for the update shohel0218:27
nkinderI can help review too since I've been developing more on keystone too18:27
bdpayneanything else on threat analysis?18:27
* morganfainberg is in-fact here, just quiet.18:27
shohel02thats great18:27
shohel02thats all18:28
bdpayne#topic Open Discussion18:28
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack Security Group)"18:28
bdpaynemalini1 asked about http://summit.openstack.org/cfp/details/818:28
bdpayneperhaps we start there18:28
nkinderI'm pretty familiar with that effort18:28
bdpayneI know that this and related issues have come around at each summit for the past several18:28
nkindermalini1: Was there something in particular you wanted to know?18:28
malini1Earlier there was a kerberos like effort from Simo but this is lighter weight18:29
*** balajiiyer has joined #openstack-meeting18:29
*** blamar_ has joined #openstack-meeting18:29
malini1and in conjunction with us keeping certs in barbican, thius is lighter weight18:29
*** blamar_ is now known as blamar18:29
*** imsurit has quit IRC18:29
bdpayneat a high level, this sounds good but it is all in the details for stuff like this18:29
bdpayneI'd like to attend this session and learn more18:29
*** rakhmerov has joined #openstack-meeting18:29
hyakuheiKinda feels like PGP re-invented with x50918:29
*** mspreitz has joined #openstack-meeting18:30
hyakuheicentral registry etc.18:30
nkinderhere's some background...18:30
nkinderThe Kite project is the first step, which uses symmetric crypto18:30
*** darraghb has joined #openstack-meeting18:30
nkinderlots of low-level detail is here - https://wiki.openstack.org/wiki/MessageSecurity18:30
*** derekh has joined #openstack-meeting18:31
bknudsonis kite planned for juno?18:31
nkinderbknudson: it's going into barbican, but my guess is that it will be at a POC level for Juno18:31
bknudsongoing to be part of identity or barbican?18:31
nkinderit will require changes on the oslo.messaging side to use it18:31
nkinderit has some caveats for group messaging though, which is where PKI might help out18:31
nkinderI covered this pretty well in the API doc for Kite/KDS18:32
*** balajiiyer has quit IRC18:32
*** balajiiyer has joined #openstack-meeting18:32
* bdpayne notes the time, but doesn't believe the meeting room is in use for another 30 min...18:32
nkinderI have some slides and diagrams on how it works that might be of interest to folks too18:32
bdpaynenkinder I'd certainly be interested18:33
bdpayne:-)18:33
malini1+1 for slides18:33
nkinderok, let me dig up the API doc18:33
bdpayneperhaps you can send something out to the ML18:33
nkinderwill do18:33
*** manishg has joined #openstack-meeting18:33
hyakuheiYes please.18:33
shohel02me too18:33
nkinderwarning that it's a lot of slides as it was made for an in-person preso18:33
bknudsonlooked like the conference would have rooms for each project -- is there one for security?18:33
*** balajiiyer has left #openstack-meeting18:33
nkinderso the diagrams are useful, but the words are sparse18:33
bdpaynesecurity won't have a room18:34
*** rakhmerov has quit IRC18:34
nkinderwho here is going to be at the summit?18:34
bdpaynebut we do have a session in the cross project room18:34
bknudsonhang out in identity room18:34
nkinderMaybe I can present it to OSSG folks outside of a session18:34
bdpayneI tend to hang out with Keystone and, these days, Barbican18:34
bdpayneo/ I will be at the summit18:34
hyakuheinkinder: yeah something like that might work18:34
eloI have a topic that I would like to bring up18:34
*** ramishra has joined #openstack-meeting18:34
* ScottCarlsonPP is at summit. doing a presentation PayPal and "is your cloud compliant"18:34
*** darraghb has quit IRC18:34
shohel02will be in the summit18:35
bdpayneelo go for it18:35
malini1malini at summit too18:35
*** markwash has joined #openstack-meeting18:35
eloare we aware of the open policy framework being worked on called Congress18:35
*** igor__ has joined #openstack-meeting18:35
eloI'll be at he Summitt18:35
bdpayne#action bdpayne to schedule an OSSG meetup at the summit18:35
bdpayneI am not aware of Congress18:35
*** megan_w is now known as megan_w|afk18:36
bdpaynehttps://wiki.openstack.org/wiki/Congress18:36
eloit's still in the early stage and some of the developers are trying to get people more involved to get it to incubation status18:36
*** Gordonz has joined #openstack-meeting18:37
eloit is provide policy as a service across different cloud services18:37
elohttps://wiki.openstack.org/wiki/Congress18:37
bdpaynewho is driving this effor?18:37
malini1elo -- would that mean policy move out of keystone?18:37
bdpaynes/effor/effort/18:37
eloPeter Ballard18:37
*** zns has joined #openstack-meeting18:37
*** thedodd has quit IRC18:37
nkinderpolicy is sort of out of keystone AFAIK18:38
nkinderkeystone defines roles and policy for keystone, but everyone else has their own policy.json, right>18:38
shohel02policy in OSLO18:38
bknudsonthe policy code was moved to oslo18:38
eloand a few other developers at VMware.. and a few other developers at other companies18:38
malini1soemthing coming up in barbican is control access at the level of each key on the basis of domain/project/user18:38
bknudsonevery project has their own policy.json18:38
eloit seems that policy is in each project and there isn't a common broker… we should look into this a little more18:39
elohttps://wiki.openstack.org/wiki/Congress18:39
*** vjay has quit IRC18:39
*** ramishra has quit IRC18:39
nkinderelo: it's an interesting effort, but it's going to take buy-in from all of the projects18:39
*** _nadya_ has joined #openstack-meeting18:39
bdpayneso is this for the control plane or for the guests?18:39
bdpayneoh, and getting this stuff right is... hard18:39
nkindervery18:39
*** vjay has joined #openstack-meeting18:40
nkinderalso, does every service have to go to congress to check policy every time?18:40
*** thedodd has joined #openstack-meeting18:40
nkinderif so, it becomes a bottleneck.  So in comes caching, etc.18:40
ScottCarlsonPPno, services have to send lobbyists to congress on their behalf.18:40
eloLOL18:40
malini1:-D18:41
bdpayneha18:41
eloits very open and flexible, so it really is how things are configured to leverage it…18:41
bdpayneso, interesting project with lots of open questions18:41
bdpaynecould be interesting to chat to the people working with this at the summit18:41
elocorrect… i just want to make sure people are aware of it on this list.18:41
*** dane_leblanc has quit IRC18:41
bdpayneyeah, thanks18:41
elothere will be an unconference on it  I know18:42
bdpayneahh, handy18:42
nkinderOne more thing on the secure messaging topic.  The API doc I mentioned is here - https://github.com/stackforge/kite/blob/master/doc/source/api/v1.rst18:42
ScottCarlsonPPthis sounds like something that needs to have terms defined very succinctly.  there's a lot of definitions of this stuff out there.  scares me a bit that implementation directives won't match between plugins18:42
nkinderThe beginning covers the use-case and how things work pretty well, so it's good reading if you want to know more about it.18:42
nkinder...of course I'm biased since I wrote a good chunk of it :)18:42
*** megan_w|afk is now known as megan_w18:43
bdpaynecool, I'll check it out18:44
CristianF@nkinder there are several models in Congress: proactive, reactive, interactive, so once policies are set congress may act proactively, react to request from other modules, or work on behalf of additional admin decisions18:44
bdpayneany other business ?18:44
bknudsonis secure messaging more than using SSL for qpid/kombu/whatever?18:44
nkinderbknudson: yes, absolutely18:45
nkinderbknudson: SSL is for encryptin gthe communication with the broker18:45
nkinderthe broker can then read (and modify) the message contents18:45
nkindersecure messaging means the sender encrypts/signs for the recipient(s)18:45
*** overlayer has joined #openstack-meeting18:45
*** overlayer has quit IRC18:45
nkinderthe broker does not need to be trusted, and it can't tamper with the message contents18:46
*** doddstack has joined #openstack-meeting18:46
nkinderbknudson: I'll send out my slides.  I have nice diagrams that show the difference between broker SSL/TLS and what Kite does18:46
bdpaynelet's taking the PKI for messaging discussion to the mailing list18:46
*** _nadya_ has quit IRC18:46
hyakuheiwhich of course means you need to know the current keys for the destination18:46
*** jasonhullinger has quit IRC18:46
bdpayneI think that it will be of broad interest18:46
bdpayneand we should probably wrap things up here18:46
nkinderhyakuhei: short lived tickets... That's where Kite comes in18:46
nkinderok, enough here. :)18:47
bknudsonnkinder: slides would be great. thanks18:47
bdpaynethanks everyone18:47
nkinderthanks all!18:47
bdpayne#endmeeting18:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:47
openstackMeeting ended Thu Apr 24 18:47:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-04-24-18.00.html18:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-04-24-18.00.txt18:47
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-04-24-18.00.log.html18:47
*** paulmo has left #openstack-meeting18:47
*** shohel02 has quit IRC18:47
*** natedmac has left #openstack-meeting18:47
hyakuheinkinder: Where can I read more about Kite?18:47
*** viraptor has quit IRC18:48
*** overlayer has joined #openstack-meeting18:48
*** hashar has joined #openstack-meeting18:49
*** thedodd has quit IRC18:49
*** nati_ueno has quit IRC18:49
*** vivek-ebay has quit IRC18:50
*** sballe has quit IRC18:50
*** ScottCarlsonPP has quit IRC18:51
*** chandan_kumar has quit IRC18:52
*** ominakov has joined #openstack-meeting18:53
*** dane_leblanc has joined #openstack-meeting18:53
*** zns has quit IRC18:54
*** manishg has quit IRC18:55
*** zns has joined #openstack-meeting18:55
*** zehicle_at_dell has joined #openstack-meeting18:55
*** ramishra has joined #openstack-meeting18:55
*** zdiN0bot has joined #openstack-meeting18:56
*** iv_m has joined #openstack-meeting18:57
*** coreywright_ is now known as coreywright18:58
*** jaypipes has joined #openstack-meeting18:58
*** chair6 has left #openstack-meeting18:59
*** ildikov has joined #openstack-meeting18:59
*** ramishra has quit IRC19:00
*** sballe has joined #openstack-meeting19:00
*** IlyaE has joined #openstack-meeting19:00
*** zdiN0bot has quit IRC19:00
*** kun_huang has quit IRC19:02
*** ujuc has joined #openstack-meeting19:02
*** epim has quit IRC19:03
*** dane_leblanc has quit IRC19:05
*** jamie29 has joined #openstack-meeting19:05
*** rockyg has quit IRC19:05
*** novas0x2a|laptop has joined #openstack-meeting19:05
*** markmcclain has joined #openstack-meeting19:07
*** ujuc has quit IRC19:07
*** Shaan7 has quit IRC19:07
*** vivek-ebay has joined #openstack-meeting19:07
*** dhuber has joined #openstack-meeting19:07
*** nsaje has quit IRC19:08
*** simonmcc_ has quit IRC19:08
*** simonmcc_ has joined #openstack-meeting19:08
*** Adri2000 has quit IRC19:10
*** acoles_away has quit IRC19:10
*** ujuc has joined #openstack-meeting19:10
*** rockyg has joined #openstack-meeting19:10
*** gduan has quit IRC19:10
*** garyduan has joined #openstack-meeting19:10
*** nsaje has joined #openstack-meeting19:10
*** Adri2000 has joined #openstack-meeting19:10
*** cyoyo has quit IRC19:11
*** dims has quit IRC19:11
*** acoles_away has joined #openstack-meeting19:12
*** blamar has quit IRC19:12
*** acoles_away is now known as acoles19:12
*** cyeoh has joined #openstack-meeting19:12
*** dane_leblanc has joined #openstack-meeting19:14
*** ujuc has quit IRC19:15
*** chandan_kumar has joined #openstack-meeting19:15
*** dhuber2 has joined #openstack-meeting19:16
*** prad has quit IRC19:16
*** prad has joined #openstack-meeting19:17
*** MarkAtwood has joined #openstack-meeting19:17
*** _nadya_ has joined #openstack-meeting19:17
*** tongli has quit IRC19:17
*** marcoemorais has quit IRC19:17
*** Shaan7 has joined #openstack-meeting19:18
*** Shaan7 has quit IRC19:18
*** Shaan7 has joined #openstack-meeting19:18
*** dhuber has quit IRC19:18
*** chandan_kumar has quit IRC19:23
*** david-lyle_ has joined #openstack-meeting19:26
*** saschpe has quit IRC19:29
*** sseverson has quit IRC19:29
*** mdenny has quit IRC19:29
*** mdenny has joined #openstack-meeting19:30
*** KurtMartin has joined #openstack-meeting19:30
*** rakhmerov has joined #openstack-meeting19:30
*** nati_ueno has joined #openstack-meeting19:30
*** malini1 has quit IRC19:31
*** kmartin has quit IRC19:33
*** dims has joined #openstack-meeting19:33
*** rakhmerov has quit IRC19:34
*** ivasev has quit IRC19:35
*** mspreitz has quit IRC19:35
*** Mikhail_D_ltp has left #openstack-meeting19:35
*** marcoemorais has joined #openstack-meeting19:36
*** banix has quit IRC19:37
*** arnaud has quit IRC19:38
*** saschpe has joined #openstack-meeting19:38
*** banix has joined #openstack-meeting19:39
*** sdague has quit IRC19:41
*** ttrifonov_zZzz is now known as ttrifonov19:41
*** sdague has joined #openstack-meeting19:42
*** otherwiseguy has joined #openstack-meeting19:42
*** rand738 has quit IRC19:43
*** coolsvap|afk has quit IRC19:44
*** rand738 has joined #openstack-meeting19:45
*** jamie29 has quit IRC19:45
*** IlyaE has quit IRC19:46
*** dhuber2 has quit IRC19:46
*** pablosan is now known as zz_pablosan19:47
*** hashar has quit IRC19:47
*** malini has joined #openstack-meeting19:49
*** MarkAtwood has quit IRC19:49
*** sseverson has joined #openstack-meeting19:49
*** IlyaE has joined #openstack-meeting19:50
*** dprince has quit IRC19:51
*** marekd|away is now known as marekd19:52
*** s3wong has quit IRC19:53
*** _nadya_ has quit IRC19:54
*** tioue has joined #openstack-meeting19:55
*** ramishra has joined #openstack-meeting19:56
*** david-lyle_ has quit IRC19:56
*** julim has quit IRC19:58
*** ramishra has quit IRC20:01
*** zz_pablosan is now known as pablosan20:02
*** vjay has quit IRC20:03
*** zehicle_at_dell has quit IRC20:05
*** Jianyong has quit IRC20:05
*** harlowja is now known as harlowja_away20:06
*** marcoemorais has quit IRC20:06
*** iv_m has quit IRC20:07
*** epim has joined #openstack-meeting20:09
*** stevemar has joined #openstack-meeting20:09
*** marcoemorais has joined #openstack-meeting20:09
*** Jianyong has joined #openstack-meeting20:10
*** ujuc has joined #openstack-meeting20:11
*** HenryG has quit IRC20:11
*** mattgriffin has quit IRC20:14
*** mattgriffin has joined #openstack-meeting20:14
*** mrmartin has quit IRC20:15
*** sweston has joined #openstack-meeting20:15
*** ujuc has quit IRC20:15
*** tioue has quit IRC20:16
*** epim has quit IRC20:16
*** nelsnelson has quit IRC20:17
*** topol has quit IRC20:18
*** nelsnelson has joined #openstack-meeting20:18
*** _sweston_ has joined #openstack-meeting20:20
*** sweston has quit IRC20:20
*** rockyg has quit IRC20:22
*** SumitNaiksatam has quit IRC20:24
*** scott-millward has joined #openstack-meeting20:26
*** bknudson has quit IRC20:28
*** CristianF has quit IRC20:28
*** epim has joined #openstack-meeting20:31
*** rakhmerov has joined #openstack-meeting20:31
*** ArthurBerezin has joined #openstack-meeting20:32
*** jecarey has quit IRC20:32
*** ttrifonov is now known as ttrifonov_zZzz20:34
*** ttrifonov_zZzz is now known as ttrifonov20:34
*** weshay has quit IRC20:34
*** ameade has quit IRC20:35
*** rakhmerov has quit IRC20:35
*** changbl has quit IRC20:36
*** bknudson has joined #openstack-meeting20:37
*** derekh has quit IRC20:39
*** marun has quit IRC20:40
*** radez is now known as radez_g0n320:40
*** ArthurBerezin has left #openstack-meeting20:41
*** changbl has joined #openstack-meeting20:41
*** jecarey has joined #openstack-meeting20:42
*** banix has quit IRC20:45
*** banix has joined #openstack-meeting20:46
*** zehicle_at_dell has joined #openstack-meeting20:47
*** changbl has quit IRC20:50
*** che-arne has joined #openstack-meeting20:50
*** jaypipes has quit IRC20:52
*** jdob has quit IRC20:52
*** ominakov has quit IRC20:52
*** prad has quit IRC20:53
*** Michalik- has joined #openstack-meeting20:54
*** changbl has joined #openstack-meeting20:54
*** SumitNaiksatam has joined #openstack-meeting20:54
*** erecio has quit IRC20:55
*** _nadya_ has joined #openstack-meeting20:55
*** s3wong has joined #openstack-meeting20:56
*** ramishra has joined #openstack-meeting20:57
*** zdiN0bot has joined #openstack-meeting20:57
*** mwagner_lap has quit IRC20:59
*** harlowja_away is now known as harlowja21:01
*** pdmars has quit IRC21:02
*** ramishra has quit IRC21:02
*** zdiN0bot has quit IRC21:02
*** rfolco has quit IRC21:05
*** marcoemorais has quit IRC21:05
*** dane_leblanc has quit IRC21:07
*** manishg has joined #openstack-meeting21:09
*** marcoemorais has joined #openstack-meeting21:09
*** ujuc has joined #openstack-meeting21:11
*** rbowen has quit IRC21:12
*** IlyaE has quit IRC21:16
*** ujuc has quit IRC21:17
*** hashar has joined #openstack-meeting21:18
*** manishg has left #openstack-meeting21:22
*** jjmb has quit IRC21:22
*** markmcclain has quit IRC21:23
*** yamahata has quit IRC21:24
*** malini has quit IRC21:24
*** epim has quit IRC21:26
*** jjmb has joined #openstack-meeting21:26
*** balajiiyer1 has joined #openstack-meeting21:26
*** nelsnelson has quit IRC21:26
*** nelsnelson has joined #openstack-meeting21:27
*** _sweston_ is now known as sweston21:28
*** megan_w is now known as megan_w|afk21:30
*** epim has joined #openstack-meeting21:30
*** balajiiyer1 has quit IRC21:30
*** rakhmerov has joined #openstack-meeting21:32
*** zns has quit IRC21:33
*** nati_ueno has quit IRC21:33
*** thangp has quit IRC21:35
*** ameade has joined #openstack-meeting21:35
*** rakhmerov has quit IRC21:36
*** ujuc has joined #openstack-meeting21:37
*** ujuc_ has joined #openstack-meeting21:39
*** vijendar has quit IRC21:39
*** ameade has quit IRC21:40
*** hashar has quit IRC21:40
*** ujuc has quit IRC21:42
*** malini has joined #openstack-meeting21:42
*** markmcclain has joined #openstack-meeting21:42
*** ttrifonov is now known as ttrifonov_zZzz21:42
*** bknudson has quit IRC21:42
*** ujuc_ has quit IRC21:44
*** changbl has quit IRC21:44
*** zns has joined #openstack-meeting21:45
*** hrzbrg has quit IRC21:47
*** mspreitz has joined #openstack-meeting21:48
*** ominakov has joined #openstack-meeting21:48
*** kevinconway has quit IRC21:50
*** _nadya_ has quit IRC21:51
*** ttrifonov_zZzz is now known as ttrifonov21:52
*** derekh has joined #openstack-meeting21:52
*** kin has joined #openstack-meeting21:52
*** SridharG has quit IRC21:53
*** kin has quit IRC21:53
*** IlyaE has joined #openstack-meeting21:53
*** asselin_ has quit IRC21:54
*** sseverson has quit IRC21:54
*** mdenny has quit IRC21:54
*** adalbas has quit IRC21:54
*** asselin_ has joined #openstack-meeting21:55
*** sseverson has joined #openstack-meeting21:55
*** kin has joined #openstack-meeting21:55
*** mdenny has joined #openstack-meeting21:55
*** nikhil___ has quit IRC21:56
*** dims has quit IRC21:56
*** kin is now known as nikhil___21:56
*** david-lyle has quit IRC21:57
*** ramishra has joined #openstack-meeting21:58
*** KurtMartin has quit IRC22:00
*** otherwiseguy has quit IRC22:00
*** KurtMartin has joined #openstack-meeting22:00
*** ssurana1 has left #openstack-meeting22:01
*** jgrimm has quit IRC22:02
*** ramishra has quit IRC22:02
*** marcoemorais has quit IRC22:06
*** armax has quit IRC22:07
*** amcrn has quit IRC22:08
*** marcoemorais has joined #openstack-meeting22:08
*** dims has joined #openstack-meeting22:08
*** yamahata has joined #openstack-meeting22:09
*** marcoemorais has quit IRC22:12
*** adalbas has joined #openstack-meeting22:12
*** Leonr has quit IRC22:13
*** vuil has joined #openstack-meeting22:14
*** marcoemorais has joined #openstack-meeting22:14
*** joesavak has quit IRC22:14
*** baoli has quit IRC22:15
*** dstanek is now known as dstanek_zzz22:16
*** _nadya_ has joined #openstack-meeting22:17
*** Michalik- has quit IRC22:19
*** dstanek_zzz is now known as dstanek22:19
*** sushils has joined #openstack-meeting22:21
*** kgriffs is now known as kgriffs|afk22:23
*** dkranz has quit IRC22:24
*** zns has quit IRC22:24
*** Gordonz has quit IRC22:26
*** fnaval has quit IRC22:27
*** fnaval has joined #openstack-meeting22:28
*** zns has joined #openstack-meeting22:28
*** epim has quit IRC22:30
*** ayoung has quit IRC22:30
*** Michalik- has joined #openstack-meeting22:30
*** beyounn has quit IRC22:31
*** jhenner has quit IRC22:32
*** fnaval has quit IRC22:32
*** rakhmerov has joined #openstack-meeting22:32
*** vuil has quit IRC22:33
*** schwicht has quit IRC22:33
*** doddstack has quit IRC22:34
*** beyounn has joined #openstack-meeting22:35
*** mspreitz has quit IRC22:35
*** ameade has joined #openstack-meeting22:35
*** beyounn has quit IRC22:36
*** ttrifonov is now known as ttrifonov_zZzz22:37
*** epim has joined #openstack-meeting22:38
*** ujuc has joined #openstack-meeting22:39
*** ameade has quit IRC22:40
*** neelashah has quit IRC22:41
*** enikanorov_ has quit IRC22:42
*** malini has left #openstack-meeting22:43
*** zns has quit IRC22:43
*** rakhmerov has quit IRC22:43
*** bknudson has joined #openstack-meeting22:44
*** ujuc has quit IRC22:44
*** derekh has quit IRC22:45
*** nkinder has quit IRC22:47
*** armax has joined #openstack-meeting22:47
*** IlyaE has quit IRC22:47
*** fnaval has joined #openstack-meeting22:47
*** banix has quit IRC22:50
*** mdenny has quit IRC22:56
*** mattgriffin has quit IRC22:56
*** amcrn has joined #openstack-meeting22:57
*** epim has quit IRC22:58
*** ramishra has joined #openstack-meeting22:58
*** zdiN0bot has joined #openstack-meeting22:59
*** Michalik- has quit IRC22:59
*** dkehn_ has joined #openstack-meeting23:00
*** vivek-ebay has quit IRC23:00
*** vivek-eb_ has joined #openstack-meeting23:00
*** pfallenop has quit IRC23:01
*** pfallenop has joined #openstack-meeting23:01
*** clarkb has quit IRC23:01
*** tr3buchet has quit IRC23:01
*** clarkb has joined #openstack-meeting23:01
*** tr3buchet has joined #openstack-meeting23:02
*** ctracey has quit IRC23:02
*** adalbas has quit IRC23:02
*** hugokuo has quit IRC23:02
*** sushils has quit IRC23:02
*** elo has quit IRC23:02
*** dkehn has quit IRC23:03
*** hugokuo has joined #openstack-meeting23:03
*** dkehn has joined #openstack-meeting23:03
*** ramishra has quit IRC23:03
*** nkinder has joined #openstack-meeting23:03
*** ctracey has joined #openstack-meeting23:03
*** elo has joined #openstack-meeting23:03
*** zdiN0bot has quit IRC23:03
*** armax has quit IRC23:03
*** anderstj has quit IRC23:03
*** dkehnx has quit IRC23:04
*** lifeless has quit IRC23:04
*** anderstj has joined #openstack-meeting23:04
*** armax has joined #openstack-meeting23:04
*** epim has joined #openstack-meeting23:05
*** lifeless has joined #openstack-meeting23:05
*** IlyaE has joined #openstack-meeting23:05
*** markmcclain has quit IRC23:07
*** flaper87 is now known as flaper87|afk23:08
*** atiwari has quit IRC23:09
*** epim has quit IRC23:11
*** vuil has joined #openstack-meeting23:12
*** fnaval has quit IRC23:12
*** fnaval has joined #openstack-meeting23:13
*** overlayer has quit IRC23:13
*** ayoung has joined #openstack-meeting23:13
*** Jianyong has quit IRC23:13
*** vkmc has quit IRC23:14
*** beyounn has joined #openstack-meeting23:15
*** fnaval has quit IRC23:17
*** adalbas has joined #openstack-meeting23:18
*** beyounn has quit IRC23:18
*** eguz has joined #openstack-meeting23:19
*** eguz has quit IRC23:19
*** manishg has joined #openstack-meeting23:19
*** beyounn has joined #openstack-meeting23:20
*** mattgriffin has joined #openstack-meeting23:22
*** vjay has joined #openstack-meeting23:22
*** eghobo has quit IRC23:23
*** MarkAtwood has joined #openstack-meeting23:26
*** gokrokve has quit IRC23:26
*** vuil has quit IRC23:26
*** mwagner_lap has joined #openstack-meeting23:31
*** ominakov has quit IRC23:32
*** reed has quit IRC23:32
*** IlyaE has quit IRC23:34
*** manishg has quit IRC23:35
*** rockyg has joined #openstack-meeting23:36
*** rockyg has quit IRC23:36
*** oomichi has joined #openstack-meeting23:38
*** s3wong has quit IRC23:39
*** bdpayne has quit IRC23:39
*** MarkAtwood has quit IRC23:39
*** mspreitz has joined #openstack-meeting23:40
*** ujuc has joined #openstack-meeting23:40
*** rakhmerov has joined #openstack-meeting23:41
*** gokrokve has joined #openstack-meeting23:46
*** imsurit has joined #openstack-meeting23:48
*** manishg has joined #openstack-meeting23:49
*** manishg_ has joined #openstack-meeting23:51
*** masayukig has joined #openstack-meeting23:52
*** manishg has quit IRC23:53
*** manishg_ is now known as manishg23:53
*** rakhmerov has quit IRC23:54
*** eghobo has joined #openstack-meeting23:55
*** tinoue has joined #openstack-meeting23:56
*** Qiming has joined #openstack-meeting23:56
*** yamahata has quit IRC23:57
*** ramishra has joined #openstack-meeting23:59
*** GMann has joined #openstack-meeting23:59

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