Thursday, 2013-08-08

*** vipul is now known as vipul-away00:01
*** danwent has quit IRC00:02
*** hemna is now known as hemnafk00:05
*** sarob has quit IRC00:12
*** sarob has joined #openstack-meeting00:12
*** krtaylor has joined #openstack-meeting00:14
*** sarob has quit IRC00:15
*** adjohn has joined #openstack-meeting00:15
*** adjohn has quit IRC00:17
*** adjohn has joined #openstack-meeting00:17
*** adjohn_ has joined #openstack-meeting00:18
*** woodspa has joined #openstack-meeting00:18
*** adjohn has quit IRC00:22
*** woodspa has quit IRC00:22
*** adjohn_ has quit IRC00:23
*** woodspa has joined #openstack-meeting00:23
*** diogogmt has quit IRC00:23
*** adjohn has joined #openstack-meeting00:25
*** adjohn has quit IRC00:25
*** lexinator has quit IRC00:25
*** sarob has joined #openstack-meeting00:26
*** danwent has joined #openstack-meeting00:28
*** nijaba has quit IRC00:28
*** adjohn has joined #openstack-meeting00:29
*** nijaba has joined #openstack-meeting00:29
*** lbragstad_ has joined #openstack-meeting00:31
*** wolfdreamer has quit IRC00:31
*** nachi has joined #openstack-meeting00:32
*** nachi_ has joined #openstack-meeting00:32
*** adjohn has quit IRC00:32
*** sarob_ has joined #openstack-meeting00:33
*** nachi_ has quit IRC00:34
*** lexinator has joined #openstack-meeting00:35
*** adjohn has joined #openstack-meeting00:36
*** sarob has quit IRC00:37
*** adjohn has quit IRC00:37
*** TravT has quit IRC00:37
*** sarob_ has quit IRC00:37
*** epim has quit IRC00:38
*** tanisdl has quit IRC00:41
*** bdpayne has quit IRC00:42
*** vipul-away is now known as vipul00:43
*** rwsu is now known as rwsu-away00:44
*** FallenPegasus has quit IRC00:45
*** MarkAtwood has joined #openstack-meeting00:45
*** adjohn has joined #openstack-meeting00:46
*** markwash has quit IRC00:57
*** adjohn has quit IRC01:02
*** adjohn has joined #openstack-meeting01:11
*** brucer_ has joined #openstack-meeting01:15
*** stevemar has joined #openstack-meeting01:17
*** adjohn has quit IRC01:17
*** brucer has quit IRC01:17
*** jecarey has joined #openstack-meeting01:18
*** stevemar has quit IRC01:20
*** stevemar has joined #openstack-meeting01:21
*** adjohn has joined #openstack-meeting01:25
*** woodspa_ has joined #openstack-meeting01:26
*** woodspa_ has quit IRC01:27
*** nijaba has quit IRC01:29
*** nijaba has joined #openstack-meeting01:30
*** terriyu has quit IRC01:30
*** adjohn has quit IRC01:30
*** woodspa has quit IRC01:30
*** adjohn has joined #openstack-meeting01:30
*** tedross has joined #openstack-meeting01:30
*** MarkAtwood has quit IRC01:31
*** danwent has quit IRC01:32
*** nati_ueno has quit IRC01:34
*** epim has joined #openstack-meeting01:34
*** dscannell has quit IRC01:35
*** gongysh has joined #openstack-meeting01:37
*** adjohn has quit IRC01:41
*** lexinator1 has joined #openstack-meeting01:43
*** lexinator has quit IRC01:43
*** adjohn has joined #openstack-meeting01:46
*** lexinator1 has quit IRC01:50
*** adjohn has quit IRC01:50
*** dscannell has joined #openstack-meeting01:51
*** SumitNaiksatam has quit IRC01:53
*** armax has quit IRC01:56
*** noslzzp has quit IRC01:56
*** adjohn has joined #openstack-meeting01:56
*** epim has quit IRC02:01
*** yaguang has joined #openstack-meeting02:05
*** fnaval_ has joined #openstack-meeting02:10
*** adjohn has quit IRC02:12
*** fnaval_ has quit IRC02:12
*** fnaval_ has joined #openstack-meeting02:13
*** zul has quit IRC02:14
*** MarkAtwood has joined #openstack-meeting02:14
*** medberry_ has quit IRC02:18
*** SumitNaiksatam has joined #openstack-meeting02:18
*** sarob has joined #openstack-meeting02:21
*** emagana has quit IRC02:21
*** markvan has joined #openstack-meeting02:24
*** MarkAtwood has quit IRC02:25
*** MarkAtwood has joined #openstack-meeting02:25
*** epim has joined #openstack-meeting02:26
*** neelashah has joined #openstack-meeting02:27
*** markvan has quit IRC02:28
*** markvan has joined #openstack-meeting02:28
*** nijaba has quit IRC02:29
*** nijaba has joined #openstack-meeting02:30
*** nijaba has quit IRC02:30
*** nijaba has joined #openstack-meeting02:30
*** jecarey has quit IRC02:33
*** sarob has quit IRC02:35
*** sarob has joined #openstack-meeting02:36
*** tedross has quit IRC02:38
*** markvan has quit IRC02:39
*** sarob has quit IRC02:40
*** MarkAtwood has quit IRC02:45
*** galstrom_zzz is now known as galstrom02:45
*** MarkAtwood has joined #openstack-meeting02:46
*** zul has joined #openstack-meeting02:47
*** zehicle_at_dell has joined #openstack-meeting02:50
*** martine has joined #openstack-meeting02:50
*** martine is now known as Guest6403202:50
*** eharney has quit IRC02:51
*** Guest64032 is now known as martine_02:51
*** epim has quit IRC02:53
*** galstrom is now known as galstrom_zzz02:55
*** lexinator has joined #openstack-meeting03:01
*** galstrom_zzz is now known as galstrom03:02
*** SergeyLukjanov has joined #openstack-meeting03:03
*** zehicle_at_dell has quit IRC03:05
*** adjohn has joined #openstack-meeting03:07
*** mdomsch has joined #openstack-meeting03:07
*** mdomsch has quit IRC03:08
*** mdomsch has joined #openstack-meeting03:11
*** troytoman is now known as troytoman-away03:11
*** yaguang has quit IRC03:14
*** ayoung is now known as ayoung-zZzZzZz03:21
*** HenryG has quit IRC03:22
*** mdomsch has quit IRC03:25
*** MarkAtwood has quit IRC03:26
*** yaguang has joined #openstack-meeting03:26
*** mdomsch has joined #openstack-meeting03:26
*** turul_ has joined #openstack-meeting03:27
*** turul_ is now known as afazekas03:28
*** zehicle_at_dell has joined #openstack-meeting03:28
*** nijaba has quit IRC03:29
*** martine_ has quit IRC03:29
*** nijaba has joined #openstack-meeting03:30
*** novas0x2a|laptop has quit IRC03:31
*** sandywalsh has quit IRC03:32
*** zul has quit IRC03:33
*** galstrom is now known as galstrom_zzz03:38
*** neelashah has quit IRC03:38
*** adjohn_ has joined #openstack-meeting03:39
*** adjohn has quit IRC03:42
*** sarob has joined #openstack-meeting03:46
*** mdomsch has quit IRC03:48
*** mdomsch has joined #openstack-meeting03:49
*** sarob has quit IRC03:51
*** galstrom_zzz is now known as galstrom03:51
*** mdomsch has quit IRC03:52
*** cody-somerville has quit IRC03:55
*** danwent has joined #openstack-meeting03:58
*** galstrom is now known as galstrom_zzz03:58
*** sandywalsh has joined #openstack-meeting04:06
*** zehicle_at_dell has quit IRC04:11
*** IlyaE has quit IRC04:12
*** jrodom has joined #openstack-meeting04:15
*** galstrom_zzz is now known as galstrom04:26
*** zehicle_at_dell has joined #openstack-meeting04:29
*** nijaba has quit IRC04:30
*** nijaba has joined #openstack-meeting04:30
*** afazekas has quit IRC04:31
*** galstrom is now known as galstrom_zzz04:31
*** SergeyLukjanov has quit IRC04:33
*** shanks has joined #openstack-meeting04:35
*** boris-42 has joined #openstack-meeting04:43
*** dcramer_ has joined #openstack-meeting04:50
*** dscannell has quit IRC04:51
*** afazekas has joined #openstack-meeting04:52
*** dcramer_ has quit IRC04:56
*** glikson has quit IRC05:03
*** zehicle_at_dell has quit IRC05:13
*** glikson has joined #openstack-meeting05:15
*** epim has joined #openstack-meeting05:22
*** lukego has joined #openstack-meeting05:23
*** jrodom has quit IRC05:24
*** glikson has quit IRC05:25
*** markpeek has quit IRC05:25
*** nijaba has quit IRC05:30
*** nijaba has joined #openstack-meeting05:31
*** nijaba has quit IRC05:31
*** nijaba has joined #openstack-meeting05:31
*** dcaroest has joined #openstack-meeting05:37
*** epim has quit IRC05:37
*** garyk has joined #openstack-meeting05:37
*** jlucci1 has quit IRC05:38
*** garyk has quit IRC05:38
*** gkotton has joined #openstack-meeting05:38
*** gkotton is now known as garyk05:38
*** obondarev_ has joined #openstack-meeting05:48
*** ytwu has joined #openstack-meeting05:52
*** IlyaE has joined #openstack-meeting05:53
*** nachi has quit IRC05:53
*** mikal has quit IRC05:54
*** mikal has joined #openstack-meeting05:55
*** ytwu1 has joined #openstack-meeting05:56
*** ytwu has quit IRC05:56
*** jlucci has joined #openstack-meeting05:57
*** lukego has quit IRC05:57
*** jlucci has quit IRC06:01
*** ytwu has joined #openstack-meeting06:02
*** glikson has joined #openstack-meeting06:03
*** ytwu2 has joined #openstack-meeting06:05
*** ytwu1 has quit IRC06:05
*** ytwu has quit IRC06:07
*** ytwu has joined #openstack-meeting06:10
*** ytwu2 has quit IRC06:12
*** lukego has joined #openstack-meeting06:12
*** thomasbiege1 has joined #openstack-meeting06:15
*** lukego has quit IRC06:16
*** ytwu1 has joined #openstack-meeting06:16
*** ytwu has quit IRC06:17
*** markmcclain has quit IRC06:19
*** ytwu has joined #openstack-meeting06:20
*** ytwu1 has quit IRC06:20
*** ytwu1 has joined #openstack-meeting06:24
*** ytwu has quit IRC06:24
*** ytwu has joined #openstack-meeting06:29
*** nijaba has quit IRC06:30
*** jhenner has joined #openstack-meeting06:30
*** ytwu1 has quit IRC06:31
*** nijaba has joined #openstack-meeting06:31
*** ytwu1 has joined #openstack-meeting06:31
*** tkammer has joined #openstack-meeting06:33
*** ytwu has quit IRC06:33
*** ytwu has joined #openstack-meeting06:33
*** jhenner has quit IRC06:33
*** mrunge has joined #openstack-meeting06:34
*** ytwu1 has quit IRC06:36
*** ytwu1 has joined #openstack-meeting06:36
*** epim has joined #openstack-meeting06:37
*** ytwu has quit IRC06:37
*** ytwu has joined #openstack-meeting06:40
*** ytwu1 has quit IRC06:41
*** ytwu1 has joined #openstack-meeting06:44
*** ytwu has quit IRC06:44
*** ytwu has joined #openstack-meeting06:47
*** ytwu1 has quit IRC06:48
*** ytwu has quit IRC06:52
*** ytwu has joined #openstack-meeting06:52
*** ytwu1 has joined #openstack-meeting06:55
*** debo_os has joined #openstack-meeting06:56
*** ytwu has quit IRC06:57
*** jhenner has joined #openstack-meeting06:57
*** ytwu has joined #openstack-meeting07:00
*** pnavarro has joined #openstack-meeting07:00
*** ytwu1 has quit IRC07:02
*** ytwu1 has joined #openstack-meeting07:03
*** jhenner has quit IRC07:03
*** ytwu has quit IRC07:04
*** thomasbiege1 has quit IRC07:05
*** markvoelker has quit IRC07:08
*** markvoelker has joined #openstack-meeting07:10
*** ytwu has joined #openstack-meeting07:11
*** ytwu1 has quit IRC07:13
*** IlyaE has quit IRC07:16
*** ytwu1 has joined #openstack-meeting07:17
*** mestery_ has joined #openstack-meeting07:17
*** debo_os_ has joined #openstack-meeting07:17
*** debo_os has quit IRC07:17
*** debo_os_ is now known as debo_os07:17
*** epim has quit IRC07:18
*** ytwu has quit IRC07:19
*** lexinator has quit IRC07:19
*** mestery has quit IRC07:19
*** IlyaE has joined #openstack-meeting07:20
*** dcaroest has quit IRC07:21
*** SergeyLukjanov has joined #openstack-meeting07:21
*** IlyaE has quit IRC07:22
*** [1]glikson has joined #openstack-meeting07:23
*** glikson has quit IRC07:25
*** [1]glikson is now known as glikson07:25
*** nachi has joined #openstack-meeting07:25
*** IlyaE has joined #openstack-meeting07:25
*** nachi_ has joined #openstack-meeting07:25
*** stevemar has quit IRC07:25
*** nachi_ has quit IRC07:26
*** ytwu1 has quit IRC07:28
*** ytwu has joined #openstack-meeting07:29
*** IlyaE has quit IRC07:29
*** nijaba has quit IRC07:31
*** nijaba has joined #openstack-meeting07:32
*** debo_os has quit IRC07:32
*** ytwu1 has joined #openstack-meeting07:36
*** dcaroest has joined #openstack-meeting07:36
*** nachi has quit IRC07:37
*** ytwu has quit IRC07:37
*** ytwu has joined #openstack-meeting07:38
*** ytwu2 has joined #openstack-meeting07:40
*** ytwu1 has quit IRC07:40
*** ytwu has quit IRC07:43
*** ytwu has joined #openstack-meeting07:43
*** debo_os has joined #openstack-meeting07:44
*** emagana has joined #openstack-meeting07:44
*** ytwu2 has quit IRC07:45
*** ytwu1 has joined #openstack-meeting07:47
*** ytwu has quit IRC07:47
*** jaimegil has joined #openstack-meeting07:50
*** ytwu has joined #openstack-meeting07:50
*** ytwu1 has quit IRC07:51
*** ytwu1 has joined #openstack-meeting07:53
*** mrunge has quit IRC07:54
*** thomasbiege1 has joined #openstack-meeting07:54
*** ytwu has quit IRC07:55
*** adjohn_ has quit IRC07:56
*** mrunge has joined #openstack-meeting07:58
*** ytwu1 has quit IRC07:59
*** ytwu has joined #openstack-meeting08:00
*** sushils has joined #openstack-meeting08:03
*** ytwu1 has joined #openstack-meeting08:03
*** yaguang has quit IRC08:03
*** ytwu has quit IRC08:04
*** ytwu has joined #openstack-meeting08:07
*** ytwu1 has quit IRC08:07
*** derekh has joined #openstack-meeting08:07
*** thomasbiege1 has quit IRC08:12
*** ytwu1 has joined #openstack-meeting08:13
*** ytwu has quit IRC08:14
*** ytwu has joined #openstack-meeting08:19
*** ytwu1 has quit IRC08:20
*** boris-42 has quit IRC08:23
*** lukego has joined #openstack-meeting08:25
*** debo_os has quit IRC08:28
*** yaguang has joined #openstack-meeting08:28
*** debo_os has joined #openstack-meeting08:29
*** nijaba has quit IRC08:31
*** psedlak has joined #openstack-meeting08:31
*** nijaba has joined #openstack-meeting08:32
*** ytwu has quit IRC08:33
*** ytwu has joined #openstack-meeting08:33
*** ytwu1 has joined #openstack-meeting08:35
*** jcoufal has joined #openstack-meeting08:35
*** ytwu2 has joined #openstack-meeting08:37
*** ytwu has quit IRC08:38
*** glikson has quit IRC08:39
*** [1]glikson has joined #openstack-meeting08:39
*** ytwu1 has quit IRC08:40
*** dcaro_ has joined #openstack-meeting08:40
*** ytwu has joined #openstack-meeting08:42
*** dcaroest has quit IRC08:43
*** ytwu2 has quit IRC08:44
*** ruhe has joined #openstack-meeting08:45
*** ytwu1 has joined #openstack-meeting08:45
*** xBsd has joined #openstack-meeting08:46
*** ytwu has quit IRC08:47
*** ytwu has joined #openstack-meeting08:50
*** ytwu1 has quit IRC08:52
*** ytwu1 has joined #openstack-meeting08:53
*** ytwu has quit IRC08:55
*** ytwu has joined #openstack-meeting08:56
*** ytwu1 has quit IRC08:58
*** ytwu1 has joined #openstack-meeting09:01
*** dkehn has quit IRC09:01
*** ytwu has quit IRC09:03
*** ytwu has joined #openstack-meeting09:04
*** ytwu1 has quit IRC09:06
*** adjohn has joined #openstack-meeting09:06
*** thomasbiege1 has joined #openstack-meeting09:07
*** ytwu1 has joined #openstack-meeting09:07
*** ytwu has quit IRC09:08
*** debo_os has quit IRC09:09
*** ytwu has joined #openstack-meeting09:09
*** adjohn has quit IRC09:11
*** oNeToWn has joined #openstack-meeting09:11
*** ytwu1 has quit IRC09:11
*** yaguang has quit IRC09:13
*** isviridov has joined #openstack-meeting09:14
*** yaguang has joined #openstack-meeting09:14
*** lukego has quit IRC09:16
*** ytwu1 has joined #openstack-meeting09:17
*** ytwu has quit IRC09:19
*** lukego has joined #openstack-meeting09:20
*** ytwu has joined #openstack-meeting09:21
*** ytwu1 has quit IRC09:22
*** yaguang has quit IRC09:22
*** ytwu1 has joined #openstack-meeting09:23
*** yaguang has joined #openstack-meeting09:23
*** ytwu has quit IRC09:25
*** Yada has joined #openstack-meeting09:26
*** ytwu has joined #openstack-meeting09:27
*** ytwu1 has quit IRC09:27
*** ytwu1 has joined #openstack-meeting09:31
*** nijaba has quit IRC09:31
*** ytwu has quit IRC09:32
*** nijaba has joined #openstack-meeting09:32
*** nijaba has quit IRC09:32
*** nijaba has joined #openstack-meeting09:32
*** hyakuhei has quit IRC09:36
*** hyakuhei has joined #openstack-meeting09:36
*** ytwu has joined #openstack-meeting09:36
*** ytwu1 has quit IRC09:37
*** yaguang_ has joined #openstack-meeting09:38
*** yaguang has quit IRC09:38
*** dkehn has joined #openstack-meeting09:40
*** boris-42 has joined #openstack-meeting09:40
*** brucer_ has quit IRC09:43
*** ytwu1 has joined #openstack-meeting09:44
*** ytwu has quit IRC09:45
*** xBsd has quit IRC09:50
*** ruhe has quit IRC09:50
*** ytwu has joined #openstack-meeting09:51
*** ytwu1 has quit IRC09:52
*** xBsd has joined #openstack-meeting09:53
*** Mikhail has joined #openstack-meeting09:56
*** mdurnosvistov has quit IRC09:56
*** Mikhail is now known as Guest6586109:56
*** ytwu1 has joined #openstack-meeting09:59
*** ytwu has quit IRC10:01
*** ytwu has joined #openstack-meeting10:05
*** fvollero|gone is now known as fvollero10:05
*** isviridov has quit IRC10:07
*** ytwu1 has quit IRC10:07
*** ytwu1 has joined #openstack-meeting10:09
*** ytwu has quit IRC10:10
*** isviridov has joined #openstack-meeting10:12
*** ytwu has joined #openstack-meeting10:13
*** emagana_ has joined #openstack-meeting10:14
*** ytwu1 has quit IRC10:16
*** mikal has quit IRC10:17
*** ytwu1 has joined #openstack-meeting10:18
*** emagana has quit IRC10:18
*** mikal has joined #openstack-meeting10:19
*** ytwu has quit IRC10:20
*** ytwu has joined #openstack-meeting10:23
*** ytwu1 has quit IRC10:24
*** ytwu1 has joined #openstack-meeting10:25
*** ytwu has quit IRC10:28
*** nijaba has quit IRC10:28
*** ytwu has joined #openstack-meeting10:28
*** ytwu1 has quit IRC10:30
*** obondarev_ has quit IRC10:32
*** ytwu1 has joined #openstack-meeting10:32
*** nijaba has joined #openstack-meeting10:32
*** nijaba has quit IRC10:32
*** nijaba has joined #openstack-meeting10:32
*** ytwu has quit IRC10:33
*** ytwu has joined #openstack-meeting10:37
*** thomasbiege1 has quit IRC10:38
*** ytwu1 has quit IRC10:39
*** gongysh has quit IRC10:40
*** ytwu1 has joined #openstack-meeting10:43
*** ytwu has quit IRC10:45
*** ytwu has joined #openstack-meeting10:46
*** ytwu1 has quit IRC10:47
*** zul has joined #openstack-meeting10:50
*** adjohn has joined #openstack-meeting10:51
*** adjohn has quit IRC10:51
*** ytwu1 has joined #openstack-meeting10:52
*** ytwu has quit IRC10:53
*** lpabon has joined #openstack-meeting10:54
*** lpabon has quit IRC10:54
*** [1]glikson has quit IRC10:54
*** glikson has joined #openstack-meeting10:55
*** ytwu has joined #openstack-meeting10:55
*** ytwu1 has quit IRC10:56
*** ytwu1 has joined #openstack-meeting10:58
*** ruhe has joined #openstack-meeting10:58
*** yaguang_ has quit IRC10:59
*** ytwu has quit IRC11:00
*** lexinator has joined #openstack-meeting11:02
*** martine_ has joined #openstack-meeting11:02
*** ytwu has joined #openstack-meeting11:05
*** lexinator has quit IRC11:07
*** ytwu1 has quit IRC11:07
*** ruhe has quit IRC11:08
*** ytwu1 has joined #openstack-meeting11:09
*** nijaba has quit IRC11:09
*** zehicle_at_dell has joined #openstack-meeting11:10
*** ytwu has quit IRC11:10
*** ruhe has joined #openstack-meeting11:10
*** ytwu has joined #openstack-meeting11:14
*** ytwu1 has quit IRC11:15
*** nijaba has joined #openstack-meeting11:16
*** nijaba has joined #openstack-meeting11:16
*** ytwu1 has joined #openstack-meeting11:18
*** lukego has quit IRC11:19
*** dkehn has quit IRC11:20
*** ytwu has quit IRC11:21
*** [1]glikson has joined #openstack-meeting11:22
*** glikson has quit IRC11:24
*** dkehn has joined #openstack-meeting11:24
*** woodspa has joined #openstack-meeting11:25
*** ndipanov has quit IRC11:26
*** [1]glikson has quit IRC11:26
*** tedross has joined #openstack-meeting11:27
*** mikal has quit IRC11:28
*** ndipanov has joined #openstack-meeting11:28
*** glikson has joined #openstack-meeting11:29
*** pcm_ has joined #openstack-meeting11:29
*** zehicle_at_dell has quit IRC11:30
*** mikal has joined #openstack-meeting11:30
*** pcm__ has joined #openstack-meeting11:34
*** HenryG has joined #openstack-meeting11:35
*** emagana_ has quit IRC11:36
*** rscottcoyle has quit IRC11:37
*** pcm_ has quit IRC11:37
*** thomasbiege1 has joined #openstack-meeting11:41
*** ruhe has quit IRC11:45
*** ruhe has joined #openstack-meeting11:51
*** oNeToWn has quit IRC11:51
*** obondarev_ has joined #openstack-meeting11:56
*** rscottcoyle has joined #openstack-meeting12:00
*** noslzzp has joined #openstack-meeting12:01
*** rscottcoyle has joined #openstack-meeting12:01
*** rscottcoyle has joined #openstack-meeting12:03
*** lexinator has joined #openstack-meeting12:03
*** ytwu has joined #openstack-meeting12:04
*** dvarga has joined #openstack-meeting12:04
*** rscottcoyle has quit IRC12:04
*** rscottcoyle has joined #openstack-meeting12:05
*** ruhe has quit IRC12:06
*** ytwu1 has quit IRC12:06
*** ytwu1 has joined #openstack-meeting12:07
*** lexinator has quit IRC12:08
*** ytwu has quit IRC12:08
*** vkmc has joined #openstack-meeting12:08
*** vkmc has joined #openstack-meeting12:08
*** gongysh has joined #openstack-meeting12:09
*** oNeToWn has joined #openstack-meeting12:13
*** lukego has joined #openstack-meeting12:15
*** chuckieb has joined #openstack-meeting12:16
*** noslzzp has quit IRC12:16
*** ayoung-zZzZzZz is now known as ayoung12:16
*** dprince has joined #openstack-meeting12:21
*** dvarga is now known as dvarga|away12:21
*** ytwu1 has quit IRC12:21
*** ytwu has joined #openstack-meeting12:22
*** sandywalsh has quit IRC12:22
*** mikal has quit IRC12:22
*** mikal has joined #openstack-meeting12:24
*** mrunge has quit IRC12:24
*** dvarga|away is now known as dvarga12:26
*** ytwu1 has joined #openstack-meeting12:27
*** ytwu has quit IRC12:29
*** galstrom_zzz is now known as galstrom12:31
*** ytwu has joined #openstack-meeting12:32
*** SergeyLukjanov has quit IRC12:34
*** ytwu1 has quit IRC12:34
*** sandywalsh has joined #openstack-meeting12:35
*** emagana has joined #openstack-meeting12:37
*** huats has quit IRC12:37
*** ytwu1 has joined #openstack-meeting12:38
*** huats has joined #openstack-meeting12:38
*** huats has quit IRC12:38
*** huats has joined #openstack-meeting12:38
*** ytwu has quit IRC12:39
*** ytwu has joined #openstack-meeting12:40
*** ruhe has joined #openstack-meeting12:42
*** radez_g0n3 is now known as radez12:42
*** ytwu1 has quit IRC12:43
*** SergeyLukjanov has joined #openstack-meeting12:43
*** zbitter has joined #openstack-meeting12:43
*** ytwu1 has joined #openstack-meeting12:44
*** emagana has quit IRC12:45
*** ytwu has quit IRC12:45
*** zaneb has quit IRC12:47
*** ytwu has joined #openstack-meeting12:47
*** galstrom is now known as galstrom_zzz12:48
*** zbitter is now known as zaneb12:48
*** ytwu1 has quit IRC12:48
*** ruhe has quit IRC12:49
*** cwolferh_ has joined #openstack-meeting12:49
*** lbragstad_ has quit IRC12:50
*** jaimegil has quit IRC12:50
*** cwolferh has quit IRC12:52
*** ytwu1 has joined #openstack-meeting12:57
*** ytwu has quit IRC12:58
*** anteaya has joined #openstack-meeting12:58
*** ruhe has joined #openstack-meeting12:59
*** thang_ has joined #openstack-meeting12:59
*** ruhe has quit IRC13:00
*** anniec has joined #openstack-meeting13:10
*** litong has joined #openstack-meeting13:13
*** haomaiwang has quit IRC13:15
*** topol has joined #openstack-meeting13:17
*** adalbas has joined #openstack-meeting13:17
*** haomaiwa_ has joined #openstack-meeting13:18
*** fnaval_ has quit IRC13:19
*** oNeToWn has quit IRC13:20
*** haomaiwa_ has quit IRC13:20
*** haomaiwa_ has joined #openstack-meeting13:20
*** lbragstad has joined #openstack-meeting13:21
*** dscannell has joined #openstack-meeting13:23
*** topol has quit IRC13:23
*** topol has joined #openstack-meeting13:23
*** haomaiwa_ has quit IRC13:23
*** haomaiwang has joined #openstack-meeting13:23
*** ytwu has joined #openstack-meeting13:24
*** ytwu1 has quit IRC13:26
*** leif has joined #openstack-meeting13:26
*** haomaiwang has quit IRC13:26
*** leif is now known as Guest846413:26
*** haomaiwang has joined #openstack-meeting13:27
*** ytwu1 has joined #openstack-meeting13:27
*** ytwu has quit IRC13:28
*** topol has quit IRC13:28
*** krtaylor has quit IRC13:29
*** neelashah has joined #openstack-meeting13:29
*** jecarey has joined #openstack-meeting13:30
*** changbl has quit IRC13:30
*** Guest8464 has quit IRC13:32
*** leif_ has joined #openstack-meeting13:34
*** ytwu has joined #openstack-meeting13:37
*** ytwu1 has quit IRC13:39
*** ytwu1 has joined #openstack-meeting13:40
*** cody-somerville has joined #openstack-meeting13:41
*** markpeek has joined #openstack-meeting13:41
*** vijendar has joined #openstack-meeting13:42
*** ytwu has quit IRC13:42
*** ruhe has joined #openstack-meeting13:45
*** ruhe has quit IRC13:45
*** markpeek has quit IRC13:46
*** markpeek has joined #openstack-meeting13:47
*** afazekas has quit IRC13:47
*** fnaval_ has joined #openstack-meeting13:48
*** lukego has quit IRC13:49
*** ruhe has joined #openstack-meeting13:50
*** pentameter has joined #openstack-meeting13:56
*** kevinconway has quit IRC13:57
*** vbellur has joined #openstack-meeting13:57
*** markvan has joined #openstack-meeting13:58
*** lukego has joined #openstack-meeting13:58
*** medberry_ has joined #openstack-meeting13:59
*** medberry_ is now known as med_13:59
*** med_ has joined #openstack-meeting13:59
*** dkranz has quit IRC14:00
*** dscannell has quit IRC14:06
*** armax has joined #openstack-meeting14:06
*** mrodden has joined #openstack-meeting14:06
*** topol has joined #openstack-meeting14:08
*** stevemar has joined #openstack-meeting14:09
*** ruhe has quit IRC14:09
*** leif_ has quit IRC14:09
*** lukego has quit IRC14:11
*** terriyu has joined #openstack-meeting14:13
*** afazekas has joined #openstack-meeting14:14
*** krtaylor has joined #openstack-meeting14:15
*** markmcclain has joined #openstack-meeting14:15
*** markmcclain has quit IRC14:15
*** tedross has left #openstack-meeting14:20
*** iben has joined #openstack-meeting14:21
*** burt has joined #openstack-meeting14:24
*** changbl has joined #openstack-meeting14:26
*** MarkAtwood has joined #openstack-meeting14:28
*** adalbas has quit IRC14:28
*** ytwu has joined #openstack-meeting14:29
*** lukego has joined #openstack-meeting14:29
*** diogogmt has joined #openstack-meeting14:30
*** ytwu1 has quit IRC14:30
*** jang1 has quit IRC14:31
*** tanisdl has joined #openstack-meeting14:32
*** lpabon has joined #openstack-meeting14:33
*** xBsd has joined #openstack-meeting14:33
*** danwent has quit IRC14:33
*** jang1 has joined #openstack-meeting14:34
*** otherwiseguy has joined #openstack-meeting14:36
*** eharney has joined #openstack-meeting14:37
*** eharney has joined #openstack-meeting14:37
*** danwent has joined #openstack-meeting14:38
*** markmcclain has joined #openstack-meeting14:40
*** dcramer_ has joined #openstack-meeting14:41
*** danwent has quit IRC14:44
*** adalbas has joined #openstack-meeting14:44
*** ytwu1 has joined #openstack-meeting14:46
*** ytwu has quit IRC14:47
*** tkammer has quit IRC14:47
*** jlucci has joined #openstack-meeting14:48
*** lexinator has joined #openstack-meeting14:49
*** spzala has joined #openstack-meeting14:50
*** jlucci has quit IRC14:51
*** jlucci has joined #openstack-meeting14:52
*** herndon has joined #openstack-meeting14:53
*** ytwu1 has quit IRC14:55
*** ytwu has joined #openstack-meeting14:55
*** thomasm has joined #openstack-meeting14:55
*** dowillia has joined #openstack-meeting14:56
*** yaguang has joined #openstack-meeting14:57
*** ivasev has joined #openstack-meeting14:57
*** llu-laptop has joined #openstack-meeting14:57
*** eglynn has joined #openstack-meeting14:58
*** nealph has joined #openstack-meeting14:59
jd__#startmeeting ceilometer15:00
openstackMeeting started Thu Aug  8 15:00:24 2013 UTC and is due to finish in 60 minutes.  The chair is jd__. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ceilometer)"15:00
*** suo has joined #openstack-meeting15:00
openstackThe meeting name has been set to 'ceilometer'15:00
*** gordc has joined #openstack-meeting15:00
*** danspraggins has joined #openstack-meeting15:01
jd__hello everyone15:01
jd__I realize I have forgotten to send the agenda to the list15:02
jd__sorry about that15:02
*** dscannell has joined #openstack-meeting15:02
*** IlyaE has joined #openstack-meeting15:02
jd__#topic Review Havana-3 milestone15:03
*** openstack changes topic to "Review Havana-3 milestone (Meeting topic: ceilometer)"15:03
jd__so we are really getting late15:03
eglynnAlarm history API patches coming soon15:03
jd__to the point that ttx will remove blueprints next Tuesday if we don't start merging things15:03
eglynn(making good progress on this)15:03
jd__you know that guy is scary and not kidding, so we should hurry up15:04
eglynnyep, understood15:04
gordcjd__, removing 'not started'  blueprints?15:04
sandywalsh was moved to the stacktach-integration-pt2 BP, which is targeted for icehouse15:04
*** dowillia has left #openstack-meeting15:04
jd__gordc: yeah, and likely only high/medium things since we don't care about low ones15:05
*** topol_ has joined #openstack-meeting15:05
jd__sandywalsh: ack15:05
sandywalshI think I have all our other stuff moved15:05
nealphjd__: we have one that's been superseded, I think....perhaps others do too. Should everyone be cleaning house?15:05
jd__nealph: which one?15:05
*** nsaje has joined #openstack-meeting15:05
jd__always a good idea to clean anyway15:05
sandywalshherndon, is going to do a double somersault from the high dive to get in H3 :)15:06
terriyuwhat happens if I don't get my blueprint done?  (worried)15:06
nealphAPI extensions...I need to look at it a little closer before taking it off. perhaps it's just postpone to Icehouse (it's low anyways)15:06
gordcjd__, i think there's some overlap on this bp:
*** topol has quit IRC15:06
gordcmaybe you want to sync up on that.15:06
* terriyu 's blueprint:
*** topol_ is now known as topol15:06
jd__terriyu: well, that shouldn't happen because we need it so I'll step in I think on this one15:07
jd__nealph: ack15:07
jd__gordc: yes, there's overlap with what you're doing we shall discuss this at some point15:08
*** sushils has quit IRC15:08
gordcjd__, cool cool15:08
jd__gordc: I have a plan, didn't have time to expose yet15:08
llu-laptopjd__, Toni said he didn't have much time to merge, and asked me to do it.15:08
*** boris-42 has quit IRC15:08
jd__llu-laptop: what will you do?15:09
llu-laptopjd__: I'll try to start merge it next week.15:09
sandywalshmy big concern is oslo-common reviews taking a really long time15:09
llu-laptopjd__: got stuck by other things in 2 weeks. :-(15:09
*** danwent has joined #openstack-meeting15:09
*** DandyPandy has left #openstack-meeting15:09
jd__sandywalsh: feel free to add me as reviewer on that, I do it once in a while but I can hurry on some15:09
*** lukego has quit IRC15:09
*** mrodden has quit IRC15:10
jd__llu-laptop: ack15:10
sandywalshjd__, will do15:10
nsajeo/ (didn't notice meeting was on a different channel)15:10
jd__anything else on that topic?15:10
*** dkranz has joined #openstack-meeting15:11
jd__#topic Release python-ceilometerclient?15:11
*** openstack changes topic to "Release python-ceilometerclient? (Meeting topic: ceilometer)"15:11
*** rnirmal has joined #openstack-meeting15:11
*** sushils has joined #openstack-meeting15:11
jd__we need to release it after lands to please mordred15:11
mordredyes! please!15:11
mordredit will make bunny rabbits smile15:12
eglynnalso just proposed
*** mestery_ is now known as mestery15:12
jd__mordred: btw did you notice my comment about the huge amount of Change-Id in that?15:12
eglynn(add support for new alarm repeat_actions attribute)15:12
jd__eglynn: ah so cool15:12
mordredjd__: I will fix - (there was a bug in my script)15:12
*** lukego has joined #openstack-meeting15:12
jd__mordred: ack15:12
*** lexinator has quit IRC15:12
eglynnbut other than that, defo should release soon to pick up fix to the auth_token logic15:12
jd__I seem to remember only me or eglynn can release15:13
mordredjd__: fixed and uploaded15:13
eglynnjd__: yep, I think that's correct15:13
gordceglynn, that auth_token fix is already merged?15:13
jd__so I think I'll take the action for this time?15:13
eglynngordc: yep
uvirtbotLaunchpad bug 1207441 in python-ceilometerclient "keystoneclient.auth_token property is prematurely evaluated, misses refresh on token expiry" [High,Fix committed]15:14
jd__#action jd__ Release python-ceilometerclient15:14
*** epende_ has joined #openstack-meeting15:14
eglynngordc: sorry, wrong link ...
gordceglynn, cool cool. just checking to see if i needed to review15:14
eglynngordc: cool15:14
jd__#topic Event API Blueprint Modification15:15
*** openstack changes topic to "Event API Blueprint Modification (Meeting topic: ceilometer)"15:15
*** krtaylor has quit IRC15:15
*** kebray has joined #openstack-meeting15:16
herndonIn a code review yesterday, jd_ suggested a modification to the event api. As this was reviewed by a number of people, I wanted to get some feedback. I think sandywalsh and dhellman were involved substantially?15:16
jd__dhellmann_ is away today15:17
dragondmme as well15:17
herndonbasically, should the traits api be moved under /event_types?15:17
*** writerDi_ has joined #openstack-meeting15:17
herndonthis call was confusing: /v2/events/(event_type)/traits/ - should we change it to /v2/event_types/(event_type)traits15:18
*** dhellmann_ has quit IRC15:18
jd__if 'traits' is about listing the traits for an event type, yes15:18
sandywalshyeah, I think that's a good suggestion15:18
jd__unless I misunderstood the /traits meaning :)15:18
sandywalshevent_types is generic and /events is specific (like a class vs an instance)15:19
*** mrodden has joined #openstack-meeting15:19
jd__yeah that makes sense to me15:19
*** dhellmann has joined #openstack-meeting15:19
herndonallright. I think /v2/events/(event_type)/traits/(trait)/ makes sense still. agree?15:19
jd__you could have /v2/events/(event_id)/traits/ too15:19
*** kebray has quit IRC15:19
jd__herndon: no15:20
jd__you can't have an event_type a key in /events/15:20
jd__you can't have an event_type as key in /events/15:20
*** SergeyLukjanov has quit IRC15:20
sandywalshI tend to lean towards /event_types/<event_name>/traits I think15:20
jd__herndon: don't mix keys under a path15:20
herndonok :)15:21
herndonI will update the BP and submitted a new patch with this change.15:21
sandywalshjd__, so how would you suggest "give me all events of this type"?15:21
sandywalshoh, I see your point15:21
jd__sandywalsh: /v2/events?filter=15:21
sandywalshyes, absolutely15:21
jd__the meter API is crap in this regard btw, I hope we'll fix this in v3 :(15:22
jd__(and in a lot of other things anyway)15:22
herndonIf we added /v2/events/(event_type), it could return all events of a type without having to use query filters.15:22
herndonthen traits may make more sense as /v2/events/(event_type)/traits and /v2/events/(event_type)/traits/(trait_name)15:23
*** hartsocks has joined #openstack-meeting15:23
thomasmherndon: Why do we not want to use query filters?15:23
*** hartsocks has left #openstack-meeting15:23
jd__herndon: but if I have an event id of 'foobar' and a message type of 'foobar' you /events/foobar is going to fail; don't mix keys!15:23
herndonok. so ignore my suggestion :p15:24
sandywalshyeah, sorry herndon I should have picked up on that before. I think jd__'s suggestion makes sense. The filter approach is cleaner.15:24
jd__and earlier discussion with sandywalsh seems to indicate having message_id as primary key is really good idea :)15:24
jd__so everything's going to connect15:25
herndonokey dokey, I'm satisfied.15:25
apmeltonis there a reason we can't use path params?15:25
*** SergeyLukjanov has joined #openstack-meeting15:25
jd__apmelton: doesn't make sense because things aren't hiearchical15:25
sandywalshthe path param should be related to the parent resource15:25
*** sacharya has joined #openstack-meeting15:25
*** debo_os has joined #openstack-meeting15:25
sandywalshso /events/<message_id>15:26
sandywalshbut other things should be filter params15:26
jd__#topic Open discussion15:27
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:27
sandywalshlovely day15:28
gordcsandywalsh, agreed :)15:28
terriyuit's finally not sweltering15:28
*** lukego has quit IRC15:28
nsaje40 degrees C here :(15:28
llu-laptopme too :(15:29
* gordc wonders how long weather talk can continue for.lol15:29
jd__I just wish they didn't spread manure in the field near the garden15:29
dragondmhigh is 104F here.15:29
eglynngordc: indefinitely if necessary ;)15:29
thomasmSo, I was digging into the resource metadata bug.15:29
jd__we still have this place for 31 minutes, enjoy15:29
gordceglynn, we got 30mins.15:29
thomasmWhy do we use the Meter table instead of the Resource table when querying for resources?15:30
jd__thomasm: in which driver?15:30
jd__well actually my question doesn't really matters15:30
*** lukego has joined #openstack-meeting15:31
jd__the resource table is pretty useless15:31
*** vijendar has quit IRC15:31
jd__when you want to know which resources where sampled during a certain time15:31
jd__you HAVE to check the meter table15:31
thomasmWell I was looking in SQLAlchemy, but the resource table is just a rollup of the current resource state.15:31
thomasmYEah, that's what I figured15:31
thomasmanyway, the reason we're getting old metadata is because of the group_by15:31
jd__it's a bad rollup15:31
thomasmin get_resources15:31
jd__I'm pretty sure these tables should go away… I'm going in that direction in the MongoDB driver15:32
epende_So any objection to adding resource_metadata to Meter?15:32
thomasmIT's already there15:32
thomasmEach meter has resource metadata associated15:32
jd__thomasm: feel free to rewrite without using the resource table yeah15:32
*** vbellur has left #openstack-meeting15:32
jd__thomasm: I just have a patch that went in for that in MongoDB using aggregate()15:32
*** ruhe has joined #openstack-meeting15:32
jd__s/in MongoDB/in our MongoDB driver/15:33
jd__same applies to user and projects, which are not even connected to the v2 api I *think*15:33
epende_thomasm:  Is the doc not up to date on Meter, because I don't see it there15:33
*** stackKid has quit IRC15:33
jd__epende_: we're talking about storage, not what the API exposes15:33
epende_Ok to add an implementation to allow metadata to be exposed and used for filtering?15:34
epende_on Meter15:34
epende_along with an update to the API15:35
*** topol has quit IRC15:35
*** esker has joined #openstack-meeting15:35
thomasmjd__: I'm not as familiar with Mongo. What're you aggregating there? The group_by is used to return a list of resources, but when you want the latest on a single resource, you have to just query on that and get the last one - that's where the Resource table would come in handy, but yes we lose the timestamp functionality - which isn't really useful unless we're trying to get resource latest state within a specific time peri15:35
thomasmod; seems odd.15:35
jd__we already have that, I don't think we're talking about the same thing epende_15:36
*** yaguang has quit IRC15:36
*** topol has joined #openstack-meeting15:36
jd__thomas: well aggregate in MongoDB is what you would call group by I guess in SQL :)15:36
gordcepende_, metadata is exposed through Sample15:36
thomasmjd__: ah, okay. The current SQLAlchemy driver uses the meter table, but that group_by screws it up when it's looking for the latest resource state.15:37
jd__thomasm: I consider the general case as having a timestamp range, and that just is useless in the end15:37
jd__s/that/the resource table/15:37
epende_gordc: Yes, but that requires getting sample(s) in order to select meters based on metadata15:37
epende_possibly many samples15:37
epende_It would be nice to have a way to get certain Meters without getting all the Samples15:38
thomasmjd__: Fair. The API spec shows that it returns last updated timestamp (I think) with the resource_id query.15:38
*** esker has quit IRC15:38
thomasmjd__ I'll patch it up and see what we get :)15:38
jd__thomasm: that's just went in a few hours ago15:38
epende_Getting a sample requires the client to know what the meter id is15:38
epende_Which means the client must have foreknowledge of the meter id list15:38
epende_Which prevents an ignorant client from traversing the API15:39
*** tanisdl has quit IRC15:39
thomasmjd__: What went in a few hours ago?15:39
*** tanisdl has joined #openstack-meeting15:39
gordcepende_, i believe it's because metadata isn't necessarily the same everytime a meter is captured... the same reason meter dpesm15:39
jd__thomasm: the change that returns first and last timestamp of a resource15:39
thomasmjd__: Ohhhhh15:39
thomasmjd__: I'll have to pull15:39
gordcs/meter dpesm/meter doesn't have a volume/15:39
jd__thomasm: sure thing! :-)15:40
*** pnavarro has quit IRC15:40
epende_gordc, does it have to be the same each time?15:40
*** pnavarro has joined #openstack-meeting15:40
gordcepende_, the way i see it, Meters are just a roundup/overview of Samples.15:41
epende_A similar discussion was had here:
uvirtbotLaunchpad bug 1194593 in ceilometer "Meter object in reporting API does not allow resource_metadata attribute" [Wishlist,Triaged]15:41
*** markmcclain has quit IRC15:41
*** topol has quit IRC15:41
gordcepende_, whoa, a lot of discussion there. i'll need to read up on that. ignore my comments :)15:42
epende_NP, should have thrown that out there first :)15:42
epende_Thanks for the feedback15:42
*** openstack changes topic to "OpenStack Meetings ||"15:43
openstackMeeting ended Thu Aug  8 15:43:52 2013 UTC.  Information about MeetBot at . (v 0.1.4)15:43
jd__thanks guys15:43
openstackMinutes (text):
*** jmontemayor has joined #openstack-meeting15:44
*** epende_ has quit IRC15:44
thomasmTake it easy everyone!15:44
*** llu-laptop has quit IRC15:44
dragondmthat ended unexpectedly15:44
thomasmHaha, yeah15:45
*** krtaylor has joined #openstack-meeting15:45
*** topol has joined #openstack-meeting15:46
*** hemna has joined #openstack-meeting15:48
*** yaguang has joined #openstack-meeting15:49
*** gongysh has quit IRC15:50
*** garyk has quit IRC15:50
*** nealph has quit IRC15:51
*** jmontemayor has quit IRC15:52
*** nachi has joined #openstack-meeting15:53
*** nachi_ has joined #openstack-meeting15:53
*** anniec has quit IRC15:54
*** martine_ has quit IRC15:57
*** hemanth has quit IRC15:57
*** derekh has quit IRC15:57
*** eglynn has quit IRC15:57
*** hemanth has joined #openstack-meeting15:57
*** lexinator has joined #openstack-meeting15:58
*** galstrom_zzz is now known as galstrom15:59
*** anteaya has quit IRC16:01
*** markwash has joined #openstack-meeting16:02
*** vijendar has joined #openstack-meeting16:02
*** kebray has joined #openstack-meeting16:03
*** lukego has quit IRC16:04
*** stevemar has quit IRC16:04
*** ozstacker has joined #openstack-meeting16:06
*** thomasbiege2 has joined #openstack-meeting16:07
*** jtomasek has quit IRC16:07
*** nijaba has quit IRC16:07
*** thomasbiege1 has quit IRC16:07
*** emagana has joined #openstack-meeting16:07
*** esker has joined #openstack-meeting16:08
*** BobBall_AFK has left #openstack-meeting16:08
*** ruhe has quit IRC16:09
*** esker has quit IRC16:09
*** gordc has quit IRC16:09
*** resker has joined #openstack-meeting16:10
*** SergeyLukjanov has quit IRC16:11
*** lpabon has quit IRC16:12
*** ytwu1 has joined #openstack-meeting16:13
*** ytwu has quit IRC16:13
*** lexinator has quit IRC16:14
*** litong has quit IRC16:14
*** lexinator has joined #openstack-meeting16:14
*** SumitNaiksatam has quit IRC16:16
*** reed has joined #openstack-meeting16:21
*** jcoufal has quit IRC16:22
*** garyk has joined #openstack-meeting16:24
*** epim_ has joined #openstack-meeting16:25
*** glikson has quit IRC16:28
*** xBsd has quit IRC16:28
*** yaguang has quit IRC16:31
*** yaguang has joined #openstack-meeting16:31
*** ytwu has joined #openstack-meeting16:31
*** lexinator has quit IRC16:32
*** lexinator has joined #openstack-meeting16:33
*** ytwu1 has quit IRC16:33
*** lpabon has joined #openstack-meeting16:37
*** yaguang has quit IRC16:38
*** bdpayne has joined #openstack-meeting16:40
*** markmcclain has joined #openstack-meeting16:42
*** whenry has joined #openstack-meeting16:42
*** giulivo has joined #openstack-meeting16:42
*** SumitNaiksatam has joined #openstack-meeting16:43
*** stevemar has joined #openstack-meeting16:44
*** anteaya has joined #openstack-meeting16:48
*** emagana has quit IRC16:48
*** ruhe has joined #openstack-meeting16:51
*** ryanpetrello has joined #openstack-meeting16:51
*** otherwiseguy has quit IRC16:53
*** ytwu1 has joined #openstack-meeting16:54
*** mrodden has quit IRC16:55
*** ytwu has quit IRC16:55
*** Bageshree has joined #openstack-meeting16:55
*** mrodden has joined #openstack-meeting16:56
*** isviridov has quit IRC16:56
*** tanisdl_ has joined #openstack-meeting16:56
*** iben has quit IRC16:57
*** jgriffith has quit IRC16:57
*** ytwu has joined #openstack-meeting16:57
*** eglynn has joined #openstack-meeting16:58
*** ytwu1 has quit IRC16:58
*** SumitNaiksatam has quit IRC16:58
*** jgriffith has joined #openstack-meeting16:58
*** tanisdl has quit IRC16:59
*** tanisdl_ is now known as tanisdl16:59
*** danspraggins has quit IRC17:00
sdague#startmeeting qa17:00
openstackMeeting started Thu Aug  8 17:00:52 2013 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: qa)"17:00
openstackThe meeting name has been set to 'qa'17:00
sdagueok, who's around for the QA meeting?17:01
mtreinishI am here17:01
*** lexinator has quit IRC17:01
sdagueok, agenda for today17:01
sdaguefirst up...17:01
sdague#topic Volunteers to run meeting while sdague out (sdague)17:02
*** openstack changes topic to "Volunteers to run meeting while sdague out (sdague) (Meeting topic: qa)"17:02
dkranzsdague: When?17:02
sdagueok, I'm going to miss the next 3 meetings due to vacation17:02
sdagueso basically for the rest of august17:02
dkranzsdague: I'm out next week.17:02
mtreinishsdague: I can take care of that I guess17:02
sdaguedo we have volunteers for the various weeks?17:02
sdaguemtreinish: ok, you volunteer for running the next 3 weeks?17:02
dkranzsdague: I can do week after next17:03
sdagueor you and dkranz want to take turns?17:03
mtreinishsdague: whatever17:03
dkranzmtreinish: Can you do next week?17:03
mtreinishdkranz: yeah I'll be here17:03
dkranzmtreinish: I know I can do the third week.17:03
dkranzmtreinish: Not sure about the second.17:04
mtreinishdkranz: I can just handle all 3 weeks its not a problem for me17:04
*** lexinator has joined #openstack-meeting17:04
sdague#info mtreinish to run the QA meeting for the rest of August17:04
sdagueok, I think that's easiest, one person to drive through the whole time17:04
mkodererI think so too ;)17:04
sdague#topic Blueprints (sdague)17:04
*** openstack changes topic to "Blueprints (sdague) (Meeting topic: qa)"17:05
sdagueok, lets hit the big ones first, then ask for other updates17:05
*** SumitNaiksatam has joined #openstack-meeting17:05
sdague#topic testr progress (mtreinish)17:05
*** openstack changes topic to "testr progress (mtreinish) (Meeting topic: qa)"17:05
sdaguemtreinish: you first17:05
mtreinishok, so I'm still moving along with fixing races17:05
mtreinishlast friday a nova change got merged to completely destroyed az and aggregates17:06
mtreinish(when running in parallel)17:06
mtreinishI've got a fix to nova for that and added extra locking to get around it17:06
mtreinishother than that the only blocking race is the security group one in scenarios17:06
sdaguecool, hows the state of the nova patch?17:06
sdagueit will be very interesting to see what's hiding behind these races17:07
mtreinishsdague: it's got a -1 from cyeoh about v3 tests but I don't think there is any need for them17:07
afazekasmtreinish: which scenario ?17:07
*** obondarev_ has quit IRC17:07
*** rlp has joined #openstack-meeting17:07
sdaguemtreinish: you have the review?17:07
mtreinishafazekas: all of them there is an inherent race between the scenario tests and security groups17:07
afazekasIs the security group deletions happens after the server reported as deleted ?17:07
mtreinishthey all try to add the same rules the same default sec group17:07
mtreinishtenant isolation will fix it17:08
mtreinishI've just got to work through it17:08
dkranzmtreinish: Are we running each test in parallel, or each class?17:08
afazekasDo we have reason not to use a new security group in the scenario test ?17:08
sdaguedkranz: this is class level parallel17:08
mtreinishit's each class (which for scenario is each test)17:08
dkranzmtreinish: OK, good.17:08
mtreinishafazekas: that's essentially what I'm doing by adding tenant isolation to the scenario tests17:09
mtreinisheach tenant has it's own default sec group17:09
*** gkotton has joined #openstack-meeting17:09
sdaguecool, good stuff.17:09
mtreinishit's a good thing to add to the scenario tests to prevent this kind of contention on any tenant level resources17:09
mtreinishalso back to overall testr status I've got a patch up to move to serial testr17:10
mtreinishthis will help people get used to the new ui before we make the switch to parallel17:10
sdaguemtreinish: great! link for that review?17:11
afazekasI would prefer an isolation per worker process solution in the future17:11
mtreinishbut I need to respin it adalbas found a small issue with it17:11
*** rwsu-away is now known as rwsu17:12
*** garyk has quit IRC17:12
sdaguemtreinish: yep see that, cool17:12
*** gkotton is now known as garyk17:12
sdaguethat will be nice17:12
afazekasmtreinish: Looks like saving the  logs is not solved yet17:12
*** joelcoffman has joined #openstack-meeting17:12
mtreinishafazekas: it is, I'm going to add the debug flag to devstack17:12
afazekasmtreinish: ok17:13
sdagueok, anything else on the testr front?17:13
mtreinishsdague: I don't think so17:13
sdague#topic stress tests (mkoderer)17:14
*** openstack changes topic to "stress tests (mkoderer) (Meeting topic: qa)"17:14
sdaguemkoderer: how goes stress tests?17:14
mkodererit uses the common logger now ;)17:14
sdaguenice :)17:14
mkodererwe had general discussions about the purpose in some reviews17:14
mkodererI think we should discuss about them17:15
mkodererso about
afazekas this should be approved for the logger :)17:15
*** IlyaE has quit IRC17:15
mkodererafazekas: thanks ;)17:15
mkodererso about  ... IMHO every test could be a stress test17:16
mkodererI would like to be able to run several api test a stress test17:16
mkodererand scenario test as well17:16
mkodererI already started a discussion on that in the mailing list17:17
sdaguemkoderer: ok, that sounds interesting17:17
mkoderergiulivo: are you there?17:17
sdaguewhat are the concerns on it?17:17
giulivomkoderer, I'm all, +1 on all you said from me17:17
mkodererso I mean we could complely remove all test in tempest/stress17:18
dkranzgiulivo: It's got your -1 at present17:18
mkodererand use the existing ones17:18
sdaguemkoderer: oh, and just use the existing tests. And stress would just be a framework?17:18
mkodererso we would stop duplicate code17:18
sdagueI like that idea17:19
giulivoI think the only issue was about a particular submission where we were trying to find out how to organize the tests proposed17:19
mkoderersdague: that would be my finial idea17:19
giulivodkranz, I know but that is only because of minor suggestions with the code not the actual feature17:19
*** nati_ueno has joined #openstack-meeting17:19
mkodererand maybe we could add a decorator to specify which test can be used as "stresstest"17:19
mkodererI think not all test are useful for stress test17:20
sdaguegiulivo: ok, so it's just a details thing? I think we can work it through in the normal review process then.17:20
mkodererand maybe some of them don't work17:20
*** emagana has joined #openstack-meeting17:20
*** alexb_ has joined #openstack-meeting17:20
sdaguemkoderer: right, it also seems like you'd want to know if some tests allocate a lot of resources, so could only be run a few N way, and not 100x at a time17:20
mkodereryes if we all agree that this is the way to go.. let's use the reviews to finalise it17:21
giulivosdague, definitely we can, the discussion was about the scope of the tests, the link to the review was more an example of the potential problems facing now17:21
afazekasmkoderer: in the existing stress framework we can make tests more parametric
sdagueI think that's good. I imagine that we'll probably have plenty of work to do post havana for this, but I think having a summit session on it would be very cool17:21
sdagueand I like the idea of using the existing tests in another way, so we aren't duplicating our work17:21
dkranzI'm fine with this but we should still allow there being a stress case that does not go in api or scenario.17:22
dkranzSo if current stress tests in the stress dir are redundant we can remove them17:22
sdaguedkranz: well is there a stress case that you don't think would fit into either one?17:22
mkodererdkranz: yes ok thats right17:22
afazekasmkoderer: for example we can add random wait times for certain tasks17:22
dkranzsdague: Not off the top of my head.17:22
sdagueit seems like we backed up a little because we want to make sure things get run in the normal gate to make sure they work, so if they are scenario tests, we can do that17:23
sdaguethen in stress we can run those scenarios N-way over and over again17:23
dkranzsdague: I just don't like saying that if you add a stress test it must fit into the other infrastructure.17:23
sdaguedkranz: I sort of do, otherwise we have to figure out how to not bit rot them in a different way :)17:23
dkranzsdague: Well, I guess we can cross that bridge when we come to it.17:24
sdaguebut regardless, we can decide that later17:24
mkodererok great17:24
*** writerDi_ has quit IRC17:24
sdaguethis, however, I think is a very fruitful direction, which I like17:24
mkodererso we have something to do ;)17:24
sdaguenice job mkoderer17:24
dkranzsdague: agreed17:24
mkoderersdague: thanks17:24
sdaguecool, ok other blueprints we should talk about?17:25
sdaguethose two have been the top recurring ones17:25
*** resker has quit IRC17:25
dkranzsdague: quantum, but don't know what there is to say.17:25
sdague#topic quantum in gate17:25
*** openstack changes topic to "quantum in gate (Meeting topic: qa)"17:25
dkranzsdague: It is really odd that no one is fixing this.17:25
*** HenryG has quit IRC17:25
sdaguewell, it's worth an update17:25
giulivoso the way I'm reading it it means we would not accept submissions like this
sdagueso smoke tests are back on17:25
* giulivo was typing too slow, sorry17:26
dkranzgiulivo: I think that's right.17:26
sdaguegiulivo: right, not for now, as we want to go down mkoderer's path17:26
*** spzala_ has joined #openstack-meeting17:26
sdague#topic neutron in gate17:26
*** openstack changes topic to "neutron in gate (Meeting topic: qa)"17:26
sdagueI have to get used to using the new name17:26
sdagueso neutron smoke gate is back on17:26
sdaguethough there are still some races17:26
sdagueI haven't looked at full runs recently17:27
sdagueanyone working on neutron full gate runs around?17:27
afazekasIMHO there are some not yet implemented not too core feature on  the full neutron gate17:27
sdagueI know I've put my foot down on the devstack side that neutron isn't going to be default there until it makes the whole gate17:28
*** gkotton has joined #openstack-meeting17:28
*** dcaro_ has quit IRC17:28
dkranzsdague: But is any one actually working on it?17:28
sdagueafazekas: if we end up with a handful of tests that aren't applicable, I'm ok in skipping those17:28
afazekasWe should skip them until implemented, and try to get the full neutron gate  job as a job what can say success17:28
*** ruhe has quit IRC17:28
sdaguebut I'd like to see someone working on it17:28
sdagueit's the same approach on the cells side, if we can narrow it down to a few skips based on high priority nova bugs, we can do that.17:29
sdaguebut we'll leave the project teams to owning getting us there17:29
*** garyk has quit IRC17:30
sdagueok, anything other blueprints?17:30
*** gkotton is now known as garyk17:30
dkranzsdague: Just heat, but that is its own agenda topic.17:30
*** spzala has quit IRC17:30
sdague#topic high priority reviews17:30
*** openstack changes topic to "high priority reviews (Meeting topic: qa)"17:30
sdagueok, who's got reviews that need extra attention?17:30
afazekassdague: I will reread the etherpad related to the neutron blueprint17:30
sdagueafazekas: great, thanks17:31
afazekas looks like here I got the opposite comment then I get the beginning17:31
dkranzsdague: Not sure any are special, just a lot not yet approved.17:31
*** spzala_ has quit IRC17:32
dkranzsdague: I will get to some today.17:32
sdaguedkranz: yeh, that happens. But I think we're keeping up not too bad17:32
sdagueyes, I will as well17:32
afazekas is still belongs to the leaking stuff17:32
sdagueafazekas: great, that one I wanted to come back to again today17:33
sdaguethat's an important one to get right and get in17:33
sdagueI'll review again today17:33
sdagueother reviews?17:33
dkranzafazekas: I made a comment that one of sdague's comments was not addressed.17:33
*** gkotton has joined #openstack-meeting17:33
dkranzsdague: BTW, are we saying that tearDownClass must never throw and always call super?17:34
afazekasdkranz: he noted a sub function17:34
sdaguedkranz: yes, I think that's what we need17:34
sdagueotherwise we won't get to the end of the inheritance chain17:35
dkranzsdague: Sure, but I think we are way short of that currently.17:35
sdaguedkranz: agreed17:35
mkodererI never found a try block insinde of a tearDown17:35
sdaguethis is going to go in phases17:35
dkranzsdague: And there is the question of whether that applies to "expected" exceptions or if all need blanket try17:35
*** gkotton_ has joined #openstack-meeting17:35
sdaguedkranz: yes, we're going to need to tackle these one by one17:36
sdagueI guess the question is should we fix tearDown's with a blanket decorator?17:36
*** mrodden1 has joined #openstack-meeting17:36
sdaguewe could probably do that pretty generically17:36
dkranzsdague: Yes, if we are going to be hard core about this requirement17:36
*** garyk has quit IRC17:36
*** mrodden has quit IRC17:36
*** gkotton_ is now known as garyk17:36
sdagueand it would be easier to catch people's mistakes17:36
dkranzsdague: +117:37
dkranzAnd easier to not make them in the first place17:37
sdaguewe could probably get away with 2, one for teardown, one for teardownclass17:37
dkranzSound's reasonable.17:38
sdagueafazekas: you want to tackle that as part of this?17:38
dkranzsdague: There is also setup17:38
*** dprince has quit IRC17:38
*** gkotton has quit IRC17:38
afazekassdague: at can added after that17:38
sdagueafazekas: ok17:38
dkranzwhich should call super and call teardown if failing17:38
sdaguedkranz: I'm less concerned with setup right now17:39
dkranzThat's another thing we do only sporadically17:39
dkranzsdague: OK17:39
*** SergeyLukjanov has joined #openstack-meeting17:39
sdagueteardown is the big racey bit right now17:39
dkranzdecorator makes things more tractable.17:39
sdagueok, other reviews to talk about?17:40
sdague#topic Status of slow heat tests (dkranz)17:40
*** openstack changes topic to "Status of slow heat tests (dkranz) (Meeting topic: qa)"17:40
sdagueok, it's your show dkranz17:40
dkranzSo I've been working with sbaker on this17:40
*** gkotton has joined #openstack-meeting17:40
dkranzI pushed a new heat-slow tox job today17:41
dkranzI just need a new yaml job and a change to devstack-gate to set a new env variable used by the slow tests.17:41
dkranzThe only question I had was if we should run the new job serial or parallel?17:41
sdagueI'm assuming the heat job will need to go on all the projects, as it drives them all17:41
dkranzI submitted it as serial17:41
*** sarob has joined #openstack-meeting17:42
dkranzsdague: Yes, but I was going to start it as non-voting on tempest17:42
sdaguedkranz: does it run in parallel?17:42
*** glikson has joined #openstack-meeting17:42
sdaguedkranz: at first I would at least add it non-voting on heat and tempest17:42
dkranzsdague: Not with my pending patch (please review :)17:42
*** rongze has quit IRC17:42
sdaguedkranz: ok :)17:42
dkranzsdague: Did you see my last two comments ? :)17:42
mtreinishdkranz: how many test classes are there with the slow tag?17:43
*** rongze has joined #openstack-meeting17:43
dkranzmtreinish: There are just two tests now.17:43
dkranzmtreinish: Steve is waiting on some image build stuff for the rest.17:43
mtreinishok then probably not much benefit to running in parallel...17:43
sdaguedkranz: right, I'd like to also run it non-voting on heat, so as they make changes it will trigger there17:43
*** garyk has quit IRC17:43
mtreinishbut it'd be nice to try it17:43
*** gkotton is now known as garyk17:43
dkranzsdague: Sure17:43
sdaguebut other than that, seems cool17:43
dkranzsdague: That's it.17:44
sdague#topic Open Discussion17:44
*** openstack changes topic to "Open Discussion (Meeting topic: qa)"17:44
sdagueany other topics?17:44
mkodererany news regarding the core reviewers topic? ;)17:44
dkranzsdague: Did you ever put out the call for reviewers?17:44
sdaguedkranz: I didn't, my bad. I'll do that today17:44
dkranzsdague: np17:45
dkranzsdague: Also contributors :)17:45
sdagueI think we'll look at core reviewer nominations at H3, that gives us the rest of the month17:45
*** thomasbiege has joined #openstack-meeting17:45
sdagueand will give us potentially additional people during the rc phase to help review tests17:45
*** thomasbiege2 has quit IRC17:45
sdagueas tempest work kind of peaks post H317:46
dkranzsdague: Sound's good.17:46
sdagueI'm still running after these global requirements issues in the gate17:46
mkoderersry.. what is H3?17:46
sdaguewhich we have mostly nailed in devstack/tempest17:46
dkranzmkoderer: havana 317:46
mtreinishmkoderer: havanna-3 milestone17:47
sdagueHavana-3 milestone17:47
sdaguewhich is first week of Sept17:47
mkodererahh sorry ;)17:47
mtreinishlooks like I still can't spell :)17:47
sdagueno worries :)17:47
sdaguemtreinish: that's not new :)17:47
sdaguewe have a new way we can break the gate though, with clients releasing and breaking other people's unit tests17:48
sdaguewhich... was fun yesterdya17:48
sdaguemordred and I are trying to come up with solutions17:48
*** ayoung is now known as ayoung-afk17:48
*** thomasm has left #openstack-meeting17:48
sdagueok, anything else from folks?17:48
mordredtrying trying17:48
anteayanot sure if it is my turn, I just want to let you know that I would like to attend a -qa bootcamp17:48
dkranzsdague: There is a blueprint for better testing of python clients17:49
anteayaso for me to attend one, there needs to be one17:49
dkranzsdague: But no progress yet.17:49
anteayaso I'd like there to be a -qa bootcamp, please17:49
afazekasdevstack still not OK on fedora :(17:49
sdagueanteaya: yeh, I suspect that probably won't happen before Icehouse summit17:49
sdaguebut something we can figure out if makes sense after17:49
anteayasdague: yeah, I agree17:49
anteayaafter works for me17:50
sdagueit's a lot to organize though17:50
anteayathank you17:50
anteayait is17:50
anteayalet me know if I can do anything to help17:50
sdagueafazekas: yeh, did you look at dtroyer's patch?17:50
sdagueI think that got russellb fixed yesterday17:50
anteayaif you want to have it in Canada, icehouse in February, just let me know17:50
sdaguethere is still the requirements issue17:50
sdagueafazekas: will try to get that sorted today17:50
sdagueI know that's biting fedora folks a lot17:51
dkranzsdague: Bit me :)17:51
giulivodkranz, that blueprint about the python clients, how about after we have some more scenario tests we try to use the scenario tests with different versions of the client libraries?17:51
afazekassdague: I will try that17:51
afazekassdague: thx17:51
dkranzgiulivo: Yes, that was the idea.17:51
sdagueafazekas / dkranz: from the red hat side, any volunteers to figure out how to get f19 in the gate so we don't break ourselves like this in the future?17:51
russellbyeah i got it working ... i had to change one thing, but i think it's either a fedora issue or rackspace fedora mirror issue17:51
dkranzsdague: We're working on that.17:52
sdaguedkranz: cool17:52
dkranzsdague: Is there any doc about exactly what needs to be done?17:52
russellbcommented out the python-libguestfs requirement, because it was pulling in qemu, which was pulling in qemu-system-*, and some weren't available17:52
russellband they're not all needed, so i just didn't install libguestfs for now17:52
*** IlyaE has joined #openstack-meeting17:52
russellbother than that one line, devstack works for me right now on f19 fwiw17:52
dkranzsdague: It's been waiting on fedora/devstack  working.17:52
sdaguerussellb: ok, cool. any chance in laying a patch on top of dtroyer's fixes?17:53
dkranzrussellb: Great.17:53
russellbnot sure it's a devstack fix for what i saw, so no patches coming17:53
sdagueno worries17:53
*** annegentle is now known as annegentle_vacay17:53
sdaguedkranz: on what's needed, run at mordred :)17:54
dkranzsdague: OK17:54
sdagueand the rest of -infra, they can tell you. I think the lack of public glance api was still an issue17:54
*** eglynn has quit IRC17:54
dkranzmordred: We wil do the work to get a fedora/devstack gating job.17:54
mordredah - great.17:54
sdaguemordred: on how we test fedora in the gate with devstack, so we don't break those guys all the time17:54
dkranzmordred: But not sure exactly what needs to be done.17:54
mordreddkranz: cool. find us in infra and let's chat about it17:55
sdaguebut we can take that offline from here17:55
dkranzmordred: Will do.17:55
sdagueI've got a hard stop at the top of the hour17:55
afazekassdague: IMHO there will be a volunteer soon, just it is summer and vacations ..17:55
sdagueafazekas: totally understood17:55
dkranzsdague: It is high priority17:55
sdagueI just look forward to the day where we've got fedora in the gate, I think it will be good for the project17:55
sdagueok, anything else from folks?17:56
afazekasI mean it would be good for the project :)17:56
sdagueok, lets call it17:56
* afazekas end17:56
sdaguethanks everyone for coming, see you on other irc channels17:56
*** openstack changes topic to "OpenStack Meetings ||"17:56
openstackMeeting ended Thu Aug  8 17:56:52 2013 UTC.  Information about MeetBot at . (v 0.1.4)17:56
openstackMinutes (text):
*** giulivo has left #openstack-meeting17:56
*** nachi has quit IRC17:57
*** mrodden has joined #openstack-meeting17:57
*** mdomsch has joined #openstack-meeting17:59
*** ytwu1 has joined #openstack-meeting17:59
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu Aug  8 18:00:18 2013 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at
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
bdpaynehi security group18:00
bdpaynewho's here today?18:00
*** rellerreller has joined #openstack-meeting18:00
*** mrodden1 has quit IRC18:01
*** ytwu has quit IRC18:02
bdpayneso I have a bit to discuss today18:03
bdpaynehopefully others join in :-)18:03
rlpAfternoon Everyone18:03
bdpaynelet's start by syncing on action items from previous meetings18:03
bdpayne#topic Action Items18:03
*** openstack changes topic to "Action Items (Meeting topic: OpenStack Security Group)"18:03
bdpaynejoelcoffman I believe that you were talking about doing a conference session on key management and volume encryption18:03
bdpaynedid that come together?18:03
*** kevinconway has joined #openstack-meeting18:04
*** krtaylor has quit IRC18:04
joelcoffmanyes, Jarret Raim submitted the user session (Barbican + volume encryption)18:04
bdpayneah cool18:04
bdpayneso let's keep an eye for that during the voting phase :-)18:04
bdpayneoh… and of course my talk too on securing compute nodes :-)18:05
bdpaynea few other actions items18:05
bdpaynethomasbiege is working on how to integrate automated security testing18:05
bdpayneI believe he's out today18:05
*** jlucci has quit IRC18:05
*** MarkAtwood has quit IRC18:06
bdpaynebut I can add that Xiao Xin Liu from IBM has expressed interest in helping with that effort18:06
bdpayneso that's great18:06
bdpaynenicolae__ was going to work on the wiki pages18:06
bdpayneI'll talk a little more about that later18:06
bdpayneany other action items to report on?18:07
bdpayne#topic OSSG Slide Deck18:07
*** openstack changes topic to "OSSG Slide Deck (Meeting topic: OpenStack Security Group)"18:07
joelcoffmannone from me18:07
eloHi. Eric here.18:07
*** eglynn has joined #openstack-meeting18:07
bdpayneok, so there has been some discussion on the mailing list about putting together some slides18:07
*** ndipanov is now known as ndipanov_gone18:07
bdpaynehi eric18:08
bdpayneseems like a worthwhile effort18:08
bdpaynedid you guys track that discussion?18:08
joelcoffmanpartially, but not in great detail18:09
bdpayneI was just checking it again18:09
elosame here…18:09
bdpaynediscussion has died down a bit, but this seems like a worthwhile activity18:09
bdpayne#action bdpayne will rev that discussion up again and see if someone can take ownership of making that happen18:09
bdpayne#topic OSSG Logo18:10
*** openstack changes topic to "OSSG Logo (Meeting topic: OpenStack Security Group)"18:10
bdpayneI think it would be handy to have an OSSG logo18:10
bdpaynewe have approval from the OS people to use the basic OS logo and do something security oriented with it… but before we actually use it we need to circle back and get specific approval on the use case and final logo design18:11
bdpaynetldr; I'm looking for someone that could help with the graphics work18:11
bdpayneanyone handy there?  or perhaps have someone at your company that could help?18:11
bdpaynethis should be easy… just not my domain18:11
bdpayneok, I think it was quiet on this last week too18:12
bdpayneI'll see if I can pull some strings at my end18:12
bdpayne#action bdpayne to strong arm someone to working on OSSG logo18:12
bdpayne#topic Wiki Page for OSSG Newbies18:12
*** openstack changes topic to "Wiki Page for OSSG Newbies (Meeting topic: OpenStack Security Group)"18:12
*** Bageshree has quit IRC18:13
*** ayoung-afk has quit IRC18:13
bdpayneWe've talks at various levels in the past about helping people get integrated into OSSG18:13
bdpayneI'm finally ready to make this happen18:13
bdpayneI'll be putting together a wiki page this week to help with all of this18:13
bdpayneI would love help18:13
bdpayneperhaps someone to bounce ideas off of, help fill in content, etc18:13
bdpayneany volunteers?18:13
joelcoffmanI'm happy to review and provide feedback when possible, but I don't have a lot of spare cycles right now18:14
rlpSame here18:14
bdpayneok, thanks guys18:14
bdpayneI'll take the lead and use you for ideas / review18:14
*** alexb_ has quit IRC18:14
eloSame here… my cycles are a little tight for the next few week due to VMworld18:15
*** stevemar has quit IRC18:15
bdpayne#action bdpayne to put together newbie wiki page with review / help from joelcoffman rlp elo18:15
*** malini1 has joined #openstack-meeting18:15
malini1hello! sorry late18:15
bdpayneVMworld?  what's that? ;-)18:15
*** stevemar has joined #openstack-meeting18:15
bdpaynehi malini118:15
bdpayne#topic OSSN work18:16
*** openstack changes topic to "OSSN work (Meeting topic: OpenStack Security Group)"18:16
bdpayneRob created several new OSSNs this week18:16
bdpaynethey still need some eyes / editing18:16
bdpayneif you follow that link18:16
bdpayneclick on bugs18:16
bdpayneand then loop at the in progress bugs18:16
bdpaynethe please provide some comments / feedback on the wording there18:17
bdpayneis everyone seeing the emails about these when they are created?18:17
bdpayne#action everyone to help review new OSSNs18:18
bdpayne#topic Other Discussion Items18:18
*** openstack changes topic to "Other Discussion Items (Meeting topic: OpenStack Security Group)"18:18
bdpaynewhat else would people like to discuss today?18:19
bdpayneI feel like I've been talking a lot … surely there's other stuff18:19
elowill review ossn stuff as well18:19
elonothing from me18:19
joelcoffmanwe could *really* use some reviews on our volume encryption patches18:19
joelcoffmanbig ones are and
bdpaynejoelcoffman you need cinder people specifically, or security people or ?18:20
jgriffithhe needs cinder people18:20
*** alexb_ has joined #openstack-meeting18:20
jgriffithbut extra eyes from sec folks would help me out18:20
joelcoffmanyes, Cinder most specifically but we'd appreciate any feedback18:20
malini1joelcoffman -- did Zhitang (winnston) ever review anything for us?18:20
*** otherwiseguy has joined #openstack-meeting18:20
bdpayneok, I'll see if I can work some connections at this end18:21
joelcoffmannot yet, I think he said he'd review it this week18:21
malini1we have bound reviewing slow at intel too on nova patches, everyone busy with their feature18:21
*** mikal has quit IRC18:22
joelcoffmanagreed, reviewers can't seem to keep up with all the proposed features18:22
bdpayneanother worthwhile thing to do is to work through the book making edits where needed18:22
bdpayneeven if you just do a page at a time, or a chapter, etc18:22
bdpayneif you do that and put up a PR for edits, just drop me a line and I can help see it through18:22
*** mikal has joined #openstack-meeting18:23
malini1:) Ah, I am doing that, markingup my book with little edits, learning as i go along18:23
malini1PR ?18:23
bdpayneedits can be made via PR
bdpayneusing the normal "git review" system18:23
bdpaynebook edits are a great task for new people to help get involved in OSSG18:24
*** esker has joined #openstack-meeting18:24
bdpayneI'll be syncing with people at my end about the Vol encryption reviews joelcoffman18:25
bdpayneI'll keep you posted18:25
*** virajh has joined #openstack-meeting18:25
bdpayneand that's all I have for today18:25
bdpaynethanks everyone18:25
*** openstack changes topic to "OpenStack Meetings ||"18:26
openstackMeeting ended Thu Aug  8 18:26:00 2013 UTC.  Information about MeetBot at . (v 0.1.4)18:26
openstackMinutes (text):
*** [1]glikson has joined #openstack-meeting18:26
*** glikson has quit IRC18:26
*** [1]glikson is now known as glikson18:26
*** joelcoffman has quit IRC18:26
*** sushils has quit IRC18:27
*** rlp has quit IRC18:28
*** MarkAtwood has joined #openstack-meeting18:28
*** zul has quit IRC18:28
*** sarob has quit IRC18:29
*** sarob has joined #openstack-meeting18:29
*** rellerreller has quit IRC18:34
*** ytwu has joined #openstack-meeting18:34
*** nachi has joined #openstack-meeting18:34
*** sarob has quit IRC18:34
*** dcaro_ has joined #openstack-meeting18:34
*** esker has quit IRC18:35
*** ytwu1 has quit IRC18:35
*** jhenner has joined #openstack-meeting18:36
*** danwent has quit IRC18:38
*** esker has joined #openstack-meeting18:41
*** ytwu1 has joined #openstack-meeting18:43
*** hartsocks has joined #openstack-meeting18:43
*** markwash has quit IRC18:44
*** ytwu has quit IRC18:45
*** ytwu has joined #openstack-meeting18:45
*** alexb_ has quit IRC18:46
*** ytwu1 has quit IRC18:48
*** psedlak has quit IRC18:48
*** ytwu1 has joined #openstack-meeting18:49
*** novas0x2a|laptop has joined #openstack-meeting18:49
*** garyk has quit IRC18:49
*** ytwu has quit IRC18:49
*** esker has quit IRC18:52
*** garyk has joined #openstack-meeting18:53
*** malini1 has left #openstack-meeting18:54
*** bdpayne has quit IRC18:54
*** epim_ has quit IRC18:55
*** rongze has quit IRC18:56
*** tanisdl has quit IRC18:56
*** tanisdl has joined #openstack-meeting18:56
*** wolfdreamer has joined #openstack-meeting18:57
*** rongze has joined #openstack-meeting18:57
*** jcoufal has joined #openstack-meeting18:58
*** mdomsch has quit IRC18:58
*** ruhe_ has joined #openstack-meeting19:02
*** jlucci has joined #openstack-meeting19:03
*** mdomsch has joined #openstack-meeting19:03
*** lcheng has joined #openstack-meeting19:03
*** mdomsch has quit IRC19:04
*** alexb_ has joined #openstack-meeting19:05
*** sarob has joined #openstack-meeting19:06
*** sarob has quit IRC19:07
*** sarob has joined #openstack-meeting19:08
*** martine_ has joined #openstack-meeting19:09
*** thomasbiege has quit IRC19:10
*** ytwu has joined #openstack-meeting19:11
*** ytwu1 has quit IRC19:11
*** sarob has quit IRC19:12
*** alexb_ has quit IRC19:13
*** numero8 has joined #openstack-meeting19:13
*** esker has joined #openstack-meeting19:14
*** jmontemayor has joined #openstack-meeting19:14
*** ruhe_ has quit IRC19:14
*** radez is now known as radez_g0n319:15
*** alexb_ has joined #openstack-meeting19:17
*** jcoufal has quit IRC19:18
*** radez_g0n3 is now known as radez19:18
*** ruhe has joined #openstack-meeting19:22
*** bdpayne has joined #openstack-meeting19:22
*** ytwu1 has joined #openstack-meeting19:26
*** ytwu has quit IRC19:27
*** MarkAtwood has quit IRC19:27
*** adalbas has quit IRC19:29
*** writerDiane has joined #openstack-meeting19:30
*** writerDiane has quit IRC19:30
*** writerDiane has joined #openstack-meeting19:31
*** mrodden1 has joined #openstack-meeting19:35
*** mrodden has quit IRC19:36
*** sarob has joined #openstack-meeting19:36
*** MarkAtwood has joined #openstack-meeting19:37
*** sarob has quit IRC19:39
*** sarob has joined #openstack-meeting19:39
*** sarob has quit IRC19:43
*** adalbas has joined #openstack-meeting19:44
*** ytwu has joined #openstack-meeting19:44
*** MarkAtwood has quit IRC19:45
*** ytwu1 has quit IRC19:45
*** vipul is now known as vipul-away19:46
*** gyee has joined #openstack-meeting19:47
*** changbl has quit IRC19:48
*** changbl has joined #openstack-meeting19:50
*** annegentle_vacay has quit IRC19:53
*** bdpayne has quit IRC19:53
*** ytwu1 has joined #openstack-meeting19:55
*** bdpayne has joined #openstack-meeting19:55
*** pcm__ has quit IRC19:55
*** herndon has left #openstack-meeting19:56
*** ytwu has quit IRC19:56
*** dcaro_ has quit IRC19:56
*** markwash has joined #openstack-meeting19:57
*** kchenweijie has joined #openstack-meeting19:57
*** doron_afk has joined #openstack-meeting19:58
*** sandywalsh has quit IRC19:59
*** esker has quit IRC20:00
harlowja#startmeeting state-management20:00
openstackMeeting started Thu Aug  8 20:00:13 2013 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: state-management)"20:00
openstackThe meeting name has been set to 'state_management'20:00
*** adrian_otto has joined #openstack-meeting20:00
harlowjainteresting, is the 'due to finish new'20:00
harlowjamaybe i just never paid attention20:00
*** melnikov has joined #openstack-meeting20:00
harlowja"Meeting started Thu Aug  8 20:00:13 2013 UTC and is due to finish in 60 minutes."20:01
harlowjahi hi20:01
harlowjai don't remember if due to finish was there before, ha20:01
jlucciYeah - it says "due to finish in 60 minutes"20:01
harlowjawhat happens at 6120:01
jlucciThe program divides by 020:01
melnikovhi there20:01
harlowjamelnikov thx for joining, know its late20:02
melnikovnot that late in fact20:02
melnikova midnight20:02
*** vipul-away is now known as vipul20:02
* harlowja thats late20:02
*** dvarga has quit IRC20:02
harlowjaalright, anyway, getting started20:03
harlowja#topic announcements20:03
*** openstack changes topic to "announcements (Meeting topic: state-management)"20:03
harlowjaya for cinder20:03
jlucciAwesome awesome job20:04
harlowjajust wanted to throw that out there ;)20:04
harlowjaon this day in aug8, a giant leap for mankind, or a small step or something20:05
kebray+1 on awesome job on the Cinder merge!20:06
adrian_ottowell done20:06
harlowjaya, thx hemna and john g. and others20:06
*** diogogmt has quit IRC20:06
harlowjayup, step uno of a path to many more steps20:06
harlowjaalright onwards and upwards20:07
harlowja#topic status20:07
*** openstack changes topic to "status (Meeting topic: state-management)"20:07
harlowjai'll go first i guess20:07
harlowjaresynced oslo code, fixed up cinder, hit oslo exception bug, continuing reading and trying out blocks, trying to see what others think about next steps20:08
harlowjawhich i think is a good topic for a little later (next steps)20:08
harlowjaand putting more priority on me doing reviews20:08
harlowjaso that kchenweijie DB work is merged20:09
harlowjawhat has everyone else been doing20:09
*** vkmc has quit IRC20:10
*** jkyle has quit IRC20:10
*** emagana has quit IRC20:10
kebrayDon't forget videos.20:10
harlowjaoh ya!20:10
jlucciMostly sorting through trove code though20:10
*** sandywalsh has joined #openstack-meeting20:10
jlucciOh, and I made a video. haha20:10
harlowjacrap can't go back to the announcement section20:11
jlucciSo that seemed to get some pretty good reception (brought down my dropbox :P)20:11
harlowjawe have our local actor20:11
harlowja---> jlucci20:11
*** emagana has joined #openstack-meeting20:11
jlucciSo that was pretty cool - trying to generate some more interest in the project and what not20:11
jlucciBut next steps for me are working on integrating taskflow into trove for create instance20:12
*** radez is now known as radez_g0n320:12
jlucci45 views *whatwhat*20:12
harlowjahmmm, need to get that placed on somehow20:12
harlowjathat will shoot that number up20:12
jlucciAnyway - that's it for me!20:12
harlowja:) thx jlucci20:13
harlowjahollywood awaits20:13
*** noslzzp has joined #openstack-meeting20:13
harlowja#action josh make some video to20:13
harlowjakchenweijie what have been up to, fighting with git i think is part of it :)20:14
jlucciMake a cinder-taskflow video20:14
harlowjaah, jlucci  good idea20:14
kchenweijieyup, fighting with git was definitely part of it20:14
kchenweijieso i got the (hopefully) final git review up for backend API and generic types20:14
kchenweijieand made it into two (slightly) smaller separate reviews20:14
kchenweijiealso been working on rpc calls for distributed taskflow20:15
harlowjacool, is that pretty involved?20:15
kchenweijiefully functional except for the fact that the celery worker at this moment still cannot figure out the ip of the calling machine20:15
kchenweijieworking on that though20:15
harlowjasounds neat20:15
kchenweijiei switch between the two projects when i get tired or frustrated with one20:15
harlowjai wonder how similar the oslo.messaging stuff is to what u are using20:15
kchenweijiewill be merged in with the distributed taskflow so that code can be added after a worker is already running20:16
jlucciOnly thing that's a little tricky is that we don't want to modify celery code20:16
kchenweijiehmm. will take a look at that link20:16
harlowja^ just might be something to read over kchenweijie20:16
uvirtbotharlowja: Error: "just" is not a valid command.20:16
jlucciBut the worker is the server listener20:16
harlowjathx uvirtbot (no idea what u are talking about)20:16
jlucciHave to get a little hacky20:16
jluccicelery worker*20:16
*** mrodden has joined #openstack-meeting20:17
kchenweijieyup, so im reading into celerys source code, which is actually really hard to follow at places...20:17
harlowjaya, i looked at it a little once, i came to some of the same conclusion20:17
harlowja:) that it kchenweijie ?20:18
kchenweijiethats it for me20:19
*** alexpilotti has joined #openstack-meeting20:19
kchenweijiealso, internship ends next tuesday, but we already discussed that i htink20:19
kchenweijieso slowly wrapping things up as well20:19
harlowjaya, sad face20:19
harlowjayour work has been much appreciated :)20:19
harlowjaand i hope it was useful for u to :)20:20
kchenweijiethank you. hope it winds up being useful and mostly problem free20:20
kchenweijieit was. learned a lot about python, databases, message queues, and above all git20:20
jlucciYes, thanks so much for all your help kchenweijie!20:20
harlowjagood ole git, ha20:20
*** mrodden1 has quit IRC20:20
harlowjamelnikov yt20:21
harlowjai think u've just been exploring the concepts and seeing what u think is good/bad/needs work (much appreciated) ya, maybe get soem coding in soon also20:21
harlowjafresh insight is something i think taskflow needs to encourage to be the best it can be :)20:22
melnikovyes, pretty much that20:22
*** vipul is now known as vipul-away20:22
*** dkranz has quit IRC20:23
harlowjaanastasia isn't around i think, but i've been messing around with here block stuff, so getting more comfortable there20:23
harlowjabut i think still some back and forth on that20:23
harlowjashe i think might be able to help continue on kchenweijie work20:23
changblHi guys, sorry I am late20:23
harlowjanp changbl20:23
jlucciYeah - can you post the link to that wiki that melnikov made?20:23
harlowjayup yup20:23
adrian_ottoyou missed the big news though20:23
changbllet me read the logs20:24
hemnabig news? :P20:24
harlowjamedium big20:24
adrian_ottoI think it's important to recognize integration of taskflow with consider as a major milestone20:24
harlowjasmall step for man, big leap for mankind20:24
changblgreat job, harlowja !20:24
*** topol has quit IRC20:25
harlowjathx changbl20:25
adrian_ottoso if we were all together I wold lead the room in a round of applause20:25
harlowjavirtual clap20:25
harlowjavirtual high-five20:25
* harlowja high-fived my laptop20:25
* adrian_otto claps20:25
* melnikov claps too20:25
adrian_ottoso special thanks to everyone, especially harlowja for this contribution20:26
harlowjahemna jlucci had a neat idea, in the spirt of videos, could make one showing what cinder is now like, the log files would be the most interesting, and describing the changes, what do u think20:26
hemnathat'd be cool to see20:26
adrian_ottoit's a win for cinder, and a win for taskflow.20:26
harlowjaadrian_otto np, just doing my duty :)20:27
harlowja#action item josh think of possible video situation20:27
harlowjachangbl just doing status also btw, have u been able to mess around at all?20:28
harlowjaalso link for some of melnikov writeups20:28
harlowjaand one that kchenweijie  made20:28
changblI am reading through your new examples, and trying to play with it20:28
harlowjawith some insights (the melnikov one) and the persistance work ( kchenweijie )20:28
changblalso reading blocks and its code20:28
harlowjasounds great20:29
harlowjaany insights u have, or questions, or anything else we are all here to help20:29
harlowja*almost anything else*20:29
harlowjaso lets maybe jump it some of melnikov ideas, before he falls asleep20:30
jlucciharlowja, melnikov - could one of ya'll still post the link to the wiki that melnikov made real quick?20:30
harlowjai think i just did?20:30
jlucciI'm done talking now. :P20:30
harlowjahaha, np20:30
*** doron_afk has quit IRC20:31
harlowja#topic melnikov-ideas20:31
*** openstack changes topic to "melnikov-ideas (Meeting topic: state-management)"20:31
harlowjai know everyone hasn't had time to read it20:31
harlowjawhich is fine20:31
harlowjamelnikov could u maybe provide a summary quickly?20:31
harlowjathx :)20:32
melnikovcurrent flows do three things: describe flow structure, actually run the tasks and hold some runtime state for that20:33
melnikovi'd like to see them separated20:33
harlowjaso seperation would be at which pieces?20:33
harlowjaflow structure + tasks20:33
harlowjathen runtime elsewhere?20:33
melnikovtasks, you put into struture via *patterns* (like linear flow or parallel or graph), than give it to *engine* to execute20:35
harlowjai think that makes sense20:36
harlowjahow much interaction/introspection do u think an engine will have to do to basically 'unravel' the pattern to run it20:36
harlowja*the above being complex when subflows and such are used20:37
melnikovthat will depend on engine implementation imo20:38
melnikovwe can have several, some might explore structure like builder from blocks code, some will just extract deps from structure and use that, maybe other ways20:38
harlowjado u want to maybe prototype that idea, i think it likely is the best direction forward, and now (at the early stages) is the best time for it i think20:39
harlowjawe aren't yet at a stage where its hard to make that change20:39
*** sarob has joined #openstack-meeting20:39
harlowjaand melnikov any idea how the logbook (or tasklog, or whatever u want to call it) will be used there20:39
*** ytwu has joined #openstack-meeting20:40
harlowjawill the machine use the tasklog (as like a persistant memory)20:40
harlowja*sorry engine, not machine20:40
harlowjajlucci does the above seem pretty useful, i think its where we all want to go in the end20:41
*** ruhe has quit IRC20:41
*** ytwu1 has quit IRC20:41
harlowjai just wonder about the engine/flow boundary (and how much introspection the engine will need to do to understand the pattern)20:42
harlowjaand then will machines themselves be saved/restored (so that we can resume/rollback)20:42
jlucciIt all sounds good, but I just worry that it might get too complicated20:42
*** vipul-away is now known as vipul20:43
harlowjaagreed, i think a prototype that shows it might help there to see it20:43
jlucciLike, I agree that there are distinct parts in the project (flow structure, runtime state/persistance, what runs the tasks/patterns)20:43
*** glikson has quit IRC20:43
melnikovjlucci, i hope it would get simpler20:43
jlucciI'm not sure that adding additional engines would simplify it though...20:44
melnikovthere are already engines hidden inside linear flow and graph flow20:44
jlucciI think the patterns tell us enough of the "how" to run a flow, that we only need one engine to run them20:44
jlucciRight, as of now, our patters are patterns/engines, right?20:45
jlucciThey define a flow structure, and how to run that structure20:45
jlucciAnd they run said structure20:45
melnikovpatterns/engines/storage, all three20:45
* harlowja wonders if we can get away with 1 engine, idk20:45
*** glikson has joined #openstack-meeting20:45
*** funzo has quit IRC20:45
*** danwent has joined #openstack-meeting20:45
jlucciYeah - it might be too difficult to have one engine20:46
jlucciNow that I think through how different the flows currently are20:46
adrian_ottowhy would it be difficult? please elaborate further.20:46
jlucciIf we had one engine it would probably become all confusing/intricate/spaghetti20:46
harlowjadepends i think on the engine/pattern barrier right?20:47
harlowja*and how that is done*20:47
jlucciWell, each flow, as of now, has a very specific way that flows need to be run20:47
melnikovi don't think one engine is the way20:47
*** woodspa has quit IRC20:47
jlucciFor instance, linear flows can only be running one task at a time20:47
jlucciWhere something like parallel flow needs to run multiple tasks at a time20:47
jlucciCreating an engine that supports the needs of every flow, I think, would get too complicated20:48
adrian_ottook, I'm persuaded by that.20:48
jlucciI'm all for keeping stuff simple, but the more I think about it, I think melnikov does has the right idea20:48
harlowjawould a possible prototype help there, that might help explore it more deeply20:48
*** dani4571 has joined #openstack-meeting20:49
harlowjathat would make it pretty evident20:49
harlowjamelnikov do u think that u can attempt that?20:49
harlowjathen we can maybe discuss it next meeting and see what we all think20:50
*** glikson has quit IRC20:50
harlowja*or the meeting after20:50
melnikovyes i think prototype will clarify the matters20:50
*** yjiang5 has joined #openstack-meeting20:50
jlucciYeah, I'd like to see the organization of things. I'm pretty sure I understand the need for all the parts20:50
jlucciJust want to see the big picture I guess20:50
* harlowja same here20:51
melnikovalso don't know if i'll be able to do something by the next meeting20:51
harlowjathats fine20:51
harlowjalots to do in the meantime :)20:51
harlowjaso no worries20:51
jlucciDefinitely. haha20:51
harlowjaand i think if engines go into taskflow, they should be mostly transparent to users of the library20:51
*** noslzzp has quit IRC20:51
harlowjajust might be 1 or 2 new lines of code20:52
harlowja*for the users*20:52
jlucciThe less the user has to know about the system, the better20:52
melnikov2 to 5 lines in config file maybe20:52
harlowjaya, or that :20:52
*** ayoung_ has joined #openstack-meeting20:52
harlowja2-5, 1-2, 3-420:52
*** noslzzp has joined #openstack-meeting20:52
harlowjasounds pretty good20:53
harlowjaanything else melnikov u want to mention?20:53
jlucci<5 and we'll call it a day20:53
jlucci __________20:54
jlucci< Success! >20:54
jlucci ----------20:54
jlucci        \   ^__^20:54
jlucci         \  (oo)\_______20:54
jlucci            (__)\       )\/\20:54
jlucci                ||----w |20:54
jlucci                ||     ||20:54
jlucciAnvil built btw20:54
*** SergeyLukjanov has quit IRC20:54
jlucciThus the cow. :P20:54
*** SergeyLukjanov has joined #openstack-meeting20:54
harlowja#topic talk-about-whatever20:54
*** openstack changes topic to "talk-about-whatever (Meeting topic: state-management)"20:54
melnikovi thik we're done with my stuff for now20:54
harlowjasweet, thx melnikov20:54
harlowjahappy cow be happy20:55
jlucciYeah - thank you. I think your ideas are going to be really beneficial to taskflow. (:20:55
* harlowja sorta wants to see what happens at minute 6120:55
harlowjadef, more good inputs the better20:55
harlowja*and even bad inputs20:56
harlowjaall inputs considered20:56
*** jmontemayor has quit IRC20:56
*** markwash has quit IRC20:56
harlowjaalright, maybe i have to wait for next time to see minute 6120:56
harlowjaunless anyone wants to talk more about taskflow20:56
jlucci*sad panda*20:56
harlowja(or whatever)20:56
harlowjahow's whatever going for u jlucci20:57
harlowjahow's the horse20:57
jlucciWaiting for anvil to finish installing20:57
jlucciI will cry if it doesn't20:57
harlowjait should20:57
*** MarkAtwood has joined #openstack-meeting20:57
jlucciI don't know man20:57
*** cyeoh has joined #openstack-meeting20:57
jluccidevstack should've worked20:58
jlucciUnexpected error while running command.20:58
jlucciTo the logs!20:58
harlowjarun again with -vv20:58
harlowjaanyway, end meeting, join us in our local home @ #openstack-state-management for more20:58
*** openstack changes topic to "OpenStack Meetings ||"20:58
openstackMeeting ended Thu Aug  8 20:58:55 2013 UTC.  Information about MeetBot at . (v 0.1.4)20:58
*** suo has quit IRC20:58
openstackMinutes (text):
*** kchenweijie has left #openstack-meeting20:59
*** joel-coffman has joined #openstack-meeting21:00
*** mriedem has joined #openstack-meeting21:00
russellb#startmeeting nova21:00
openstackMeeting started Thu Aug  8 21:00:48 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova)"21:00
russellbhello, everyone!21:00
openstackThe meeting name has been set to 'nova'21:00
*** melnikov has left #openstack-meeting21:00
* joel-coffman waves hello21:01
russellb#topic havana-3 status21:01
*** openstack changes topic to "havana-3 status (Meeting topic: nova)"21:01
*** sarob has quit IRC21:01
russellbwe are just under 2 weeks from the first havana-3 deadline, when feature patches must be submitted for review to be considered for havana21:01
dansmithcripes, two weeks?21:02
*** sarob has joined #openstack-meeting21:02
russellb98 blueprints21:02
russellbless than 10 implemented21:02
*** melwitt has joined #openstack-meeting21:02
russellbso obviously some serious work to do to even get a big chunk of this merged21:02
russellbwe're going to hit a review bottleneck i'm sure21:02
russellbso it's really important that we try to prioritize which features we're reviewing21:03
*** IlyaE has quit IRC21:03
russellbnot just on age at this point, but also what we think is most important to get into havana21:03
russellbso those are my general comments21:03
russellbwe can now talk about whichever blueprints people here are interested in discussing the status of21:03
russellbi think vishy would like to talk about live-snapshots21:04
vishyso i'm getting quite a bit of push-back from libvirt folk21:04
vishyon two points21:04
vishya) I'm using the libvirt api for snapshots in a way that wasn't intended21:04
vishyand b) we shouldn't be loading memory state into a new vm because it might break21:05
vishyI wanted to discuss these here21:05
dansmithI don't understand b21:05
lifelessthats interesting21:05
vishydansmith: see the comment from eric blake21:05
dansmithvishy: yes, that comment makes no sense to me21:05
jog0a) concerns me21:05
lifelesssee I had this idea the other day that we could snapshot memory state into a new sort of glance image21:05
*** kebray has quit IRC21:05
dansmithlet me reread21:05
vishycloning memory state into a "new" vm means there is data in memory that is invalid21:05
lifelessand deploy that at an arbitrary later date21:05
vishyspecifically the mac address and other hardware specific things21:06
vishyI think this is an acceptable tradeoff for live booting vms21:06
lifelessoh it's exactly what vishy is doing - cool21:06
vishybut it will lead to hard to diagnose problems21:06
russellblifeless: :-)21:06
*** pnavarro has quit IRC21:06
*** esker has joined #openstack-meeting21:06
*** sarob has quit IRC21:07
lifelessvishy: where is eric's comments ?21:07
*** topol has joined #openstack-meeting21:07
*** benl has joined #openstack-meeting21:07
russellblifeless: on patch set 1121:07
vishynot inline21:07
dansmithyeah, eric's comments don't make sense to me (still)21:07
vishywell one comment is inline and one is global21:07
vishyI would like to treat live-cloning as experimental for sure21:07
*** galstrom is now known as galstrom_zzz21:07
vishybut if we can ignore b) what do we do about a) ?21:08
vishydo i have to rewrite it to use the qemu monitor directly and just deal with the libvirt tainted flag?21:08
*** kebray has joined #openstack-meeting21:08
vishyfyi one of my main reasons for pushing this is I want it as an option in the api21:08
lifelesshow is this so different to live migration ?21:08
vishylifeless: it is a clone21:09
dansmithvishy: in a former life, I used life migration in xen to do this21:09
vishy… so that other companies can come in and make better versions21:09
vishyfor example, grid centric has a pretty sexy version of this already21:09
russellbvishy: why can't they contribute it?  :-)21:09
vishyrussellb: because it is proprietary code21:10
russellbi don't have much to add.  I generally defer to the libvirt folks on point a) and generally think we should avoid doing something that freaks them out if we can't convince them it's ok21:10
lifelessvishy: so then eric's comments translate as 'live migration can't possibly work, but does because it doesn't change the MAC address'21:10
jog0vishy: why is this worth pusing for Havana?21:10
vishyso basically i want to get the framework in so others can write a better version21:10
lifeless(as teh MAC is the only in-instance visible thing).21:10
lifelessI have a suggestion that might mitigate his concerns21:11
vishyjog0 only because i've been trying to get it in for two months :)21:11
lifelesshot-unplug the vnic.21:11
lifelesssave state.21:11
lifelessand on boot21:11
jog0vishy: fair enough21:11
russellbvishy: to be honest, i'm not terribly interested in a framework for other implementations that aren't coming upstream21:11
lifelessboot without a mac21:11
*** dcaro_ has joined #openstack-meeting21:11
lifelessthen hot-plug it in.21:11
vishylifeless: that could work, unplug the nic before save21:11
lifelesstada, as long as vcpu has teh same flags and arch etc, there should be no in-instance twiddling to do at all.21:11
dansmithlifeless: I don't thnk that is his concern, right?21:11
lifelessI will put this in a review comment.21:11
dansmithhe does a replug after creating it21:11
dansmithI think eric is concerned about something else, but it doesn't make sense to me21:12
yjiang5lifeless: you have to make sure there is no window between hot-remove and save, otherwise application may failed21:12
vishyit doesn't really address point a)21:12
lifelessdansmith: his concern is about having to update in-RAM values.21:12
vishyyjiang5: ah yes good point, I did think of this before21:12
*** numero8 has quit IRC21:12
dansmithlifeless: you think that's what he means by "address" ?21:12
lifelessdansmith: I think he means memory address.21:12
lifelessdansmith: in the guest RAM space21:12
vishyyjiang5: however i am hot unplug/replug on clone anyway so it should be roughly the same21:13
dansmithlifeless: right, what does that have to do with anything?21:13
*** krtaylor has joined #openstack-meeting21:13
vishylifeless: meaning the mac address of the old vm could be in a bunch of places in memory21:13
vishywhich will break things21:13
lifelessdansmith: ^21:13
dansmiththat's solved by the replug21:13
vishyaye dansmith ^21:13
lifelessdansmith: right21:13
lifelessdansmith: but you have to unplug it first to avoid potential crazy21:14
dansmithhis words led me to think he's concerned about something else21:14
jog0is it worth discussing the details here or just the high level issues vishy listed (a and b)?21:14
russellblet me see if i can get him to join us ...21:14
lifelessdansmith: if you unplug *after* the snapshot, you're changing the hardware MAC of a virtIO device without warning21:14
vishymaybe if it doesn't actually change the mac address in the xml and just does uuid/name then the libvirt folk will be better with it21:14
lifelessdansmith: it's easy to image that leading to subtle corruption bugs21:14
dansmithlifeless: well, I dunno, you can unplug a network device in linux without notice, it's not like a block device21:15
vishythat would also potentially allow for multiple nics to be attached as well21:15
vishydansmith: right but that is trusting the os to be smart about these things21:15
vishyi suspect windows is not nearly as forgiving21:15
dansmithum, who cares? :)21:15
yjiang5vishy: in live snapshot, will the VM pause a while to get the last round RAM state?21:15
n0anoare we sure that the MAC address is the only data in RAM to worry about, what about things like file system UUIDs21:16
vishyit pauses while snapshotting yes21:16
*** suo has joined #openstack-meeting21:16
vishythere are probably other things but this is all related to the idea of live clones in general21:16
mroddenwhat about hardware passthrough devices and such...21:16
lifelessdansmith: right, I agree you can hot unplug21:16
dansmithmrodden: out of scope for something like this, I'd say21:16
lifelessdansmith: but we're not hot unplugging, we're just rewriting details in the virtio device, *then* hot replugging.21:17
dansmithmrodden: hardware passthrough pins a lot of things21:17
vishythere will need to be a smart guest agent to handle some of the edge cases21:17
mroddenit straight up wouldn't work21:17
*** hartsocks has quit IRC21:17
vishythats why i want to get it in for people to experiment with21:17
mroddenbut i guess if its not a concern21:17
*** hartsocks has joined #openstack-meeting21:17
lifelessdansmith: I'm saying we need to switch the order to address his concern about changing things out under the guest without the normal hw notifications21:17
dansmithlifeless: but we all agree we should be hot unplugging before snapshot, right?21:17
lifelessdansmith: I think we do; modulo yjiang5's point about apps21:18
*** litong has joined #openstack-meeting21:18
lifelessdansmith: which I think is a higher layer problem - the IP will change as well21:18
dansmithright, that has to be understood21:18
dansmiththe thing is,21:18
dansmithhis comments are so emphatic,21:18
mroddenunless qemu does something weird with the memory mapping in the state file, i can't think of why it wouldn't work21:18
dansmithI assumed that changing the order was not going to assuage his fears, so I assumed he was worried about something else21:18
*** martine_ has quit IRC21:18
vishyok so I will rewrite the hotplugging before and minimize the xml changes, add some notes that i would prefer to do it through a libvirt api but the xml rewrite is the only thing supported currently21:19
dansmithvishy: personally,21:19
vishyand see what daniel et. al. think about that21:19
dansmithI'd like to see you do a lot more bounds checking and stuff on the xml payload,21:19
yjiang5vishy:  I think n0ano is correct that we may have a lot of guest-specific status, considering the guest has connection to a server, then that connectoin may be cloned also and confused the server.21:19
dansmithbecause changing offsets in a new version of that format would cause you to really badly break the image21:19
vishyyes clearly the production version of this needs a guest agent21:19
dansmithand I think you can do some easy sanity stuff21:19
vishygridcentric has offered to create an opensource guest agent to do this stuff21:20
vishysince they already have one21:20
russellbshould we be waiting on something we consider production ready?21:20
*** cody-somerville has quit IRC21:20
*** itzikb has joined #openstack-meeting21:21
vishyrussellb: I don't think we are going to get there unless there is an experimental version for people to start trying21:21
*** dcaro_ has quit IRC21:21
*** cody-somerville has joined #openstack-meeting21:21
russellbvishy: so sounds like you have a plan for an update to make?21:22
vishyyep i will make the update and see how it goes21:23
russellbnext blueprint for discussion?21:23
russellbdansmith: alrighty, have at it21:24
dansmithI think compute-api-objects is still in striking distance21:24
dansmithit's going to be a lot of work to get it done in two weeks, especially since comstud refuses to step up, but I think it's doable regardless21:24
dansmith(kidding about comstud of course)21:24
jog0dansmith: why does this need to hit the havana deadline?21:25
*** sarob has joined #openstack-meeting21:25
comstudit sucks having 1/2 of it done21:25
russellband that has an effect on the pain of maintaining havana21:25
jog0comstud: true, but there is an impact on ther blueprints21:25
comstudby done i mean merged already21:26
jog0russellb: good point, as in backports would be much harder if half done?21:26
comstudwe already have a lot of transitional code that is not ideal21:26
russellbi think so, we'd be left maintaining a fairly inconsistent interface21:26
jog0russellb: you convinced me21:26
russellbk :)21:26
yjiang5comstud:  do this really changed the interface a lot ?21:26
russellb(and setting deadlines for ourselves is good to help ensure we keep up the pace)  ;-)21:27
comstudyjiang5: I'm not sure what interface you're specifically referring to21:27
yjiang5comstud: the interface russellb is talking about :-)21:28
*** dansmith has quit IRC21:28
russellbcompute api?21:28
comstudit's generally way different how you work with objects or sqlalchemy models/dicts21:28
comstudsome compute api methods expect objects now21:28
comstudothers cannot take objects21:28
*** writerDiane has quit IRC21:28
comstudit'd be nice to get that all consistent :)21:29
yjiang5comstud: got it and agree.21:29
*** dansmith has joined #openstack-meeting21:29
*** writerDiane has joined #openstack-meeting21:29
dansmithum, sorry21:29
russellbdani4571: didn't miss *too* much, just clarifying what's different in compute api with objects21:30
comstuddansmith: it's cool, we assigned 10 more things to you21:30
russellbanything else you want to cover?21:30
dansmithcomstud: bring it on!21:30
russellbok, next blueprint?21:30
comstudalaski ?21:30
n0anogaryk wanted me to bring up instance groups21:30
russellbn0ano: ok21:31
*** vipul is now known as vipul-away21:31
russellbn0ano: what's up with that one21:31
n0anohe's looking for reviewers21:31
alaskicomstud: ack.  I'll go next21:31
russellbn0ano: did it get converted to objects?21:31
n0anothe patch was ready and then he had to change it to use objects and now it's ready again21:31
russellblooks like it did21:31
n0anoyes, I believe he did21:32
russellbanything else?21:32
yjiang5although PCI pasthrough is low now, I still want to lobby more cores to review our patch. It's really helpful for virtualization, and some customer want it.21:32
jog0shameless plug for:
russellbheh, just review lobbying?21:33
russellbalaski: you're up21:33
jog0russellb: yeah and feedback of course21:33
alaskiso the tl;dr is that rather than casting to scheduler to compute, and then back to scheduler on a failure.  we cast to conductor which gets a list of hosts from scheduler and calls to compute21:34
yjiang5jog0: I think the question is to me :) yes, just review lobby and feedback of course.21:34
alaskiexcept that calling to compute doesn't work so well becuase building an instance can take some time21:34
*** dansmith has quit IRC21:34
*** dansmith_ has joined #openstack-meeting21:34
alaskiso now I'm looking at conductor casting to compute and compute casting back to conductor to report success/failure21:35
russellbalaski: that would at least match how it works now21:35
russellbalaski: seems like anything else is going to be a lot more work (and more risk)21:35
alaskiright.  But leaves the scheduler in a better place21:35
*** dansmith_ is now known as dansmith21:35
russellbseems ok to me21:35
russellband perhaps worth looking at again next cycle to consider having conductor do more active monitoring of the progress21:36
russellbbut what you said sounds good to me for now21:36
alaskiagreed.  I'm open to ideas on ways to not have ccompute need to cast/call back to conductor21:37
russellbok, good on that one?21:38
alaskiyep, thanks21:38
russellbany other blueprints to discuss?21:38
itzikbrussellb: Can I ask for a review ?21:38
russellbitzikb: sure why not21:38
joel-coffmanI'll second that request21:38
russellbi assume anything marked as "needs code review", someone would like a review on it21:39
russellbcomstud: direct mysql?  still want it on the list?21:39
*** neelashah has quit IRC21:39
jog0comstud: :(21:39
comstudjog0: "Why does it need to be in Havana?" ;)21:40
russellbcomstud: ha21:40
jog0comstud: performance21:40
*** annegentle has joined #openstack-meeting21:40
comstudI know and I tend to agree21:40
comstudunless a miracle happens, I don't see it making it21:40
comstudbeacuse of trying to get these other things done21:40
russellbreality is a pain sometimes21:41
jog0comstud: yeah ... it sure is21:41
comstudI need to put my current code back up on github at least21:41
jog0russellb: what about all the BPs that aren't started?21:41
comstudor well, update it21:41
russellbjog0: all hyper-v yes?  they say they're delivering all of them ...21:42
* russellb shrugs21:42
jog0shouldn'tthey at least mark them as started21:42
russellbjog0: you'd think so21:42
russellbmaybe i'll defer them next week21:43
russellbnote that we're basically aiming to merge *everything* in high/medium21:43
russellbbut beyond that it's no real commitment21:43
russellbalright, let's check with subteams real quick, and then open discussion21:43
russellb#topic sub-team reports21:44
*** openstack changes topic to "sub-team reports (Meeting topic: nova)"21:44
russellbanyone around to provide a subteam report?21:44
*** thang_ has quit IRC21:44
russellbhartsocks: hey21:44
russellbso hartsocks does a nice job sending out regular subteam status emails :-)21:44
hartsocksSo I'm building a list of the most important blueprints to our subteam.21:45
hartsocksI'll mail the list with that tonight after I collect the stats.21:45
*** litong has quit IRC21:45
russellbanything else?21:45
hartsocksI've got a few reviews I'm shilling for...21:45
hartsocksI'll save that for the list.21:46
russellbany other subteams?21:46
russellbalrighty then21:46
russellb#topic open discussion21:46
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:46
russellbany final topics?21:47
jog0if no one else has anything, got a question about the future of conductor21:47
russellbjog0: sure, we can chat about that21:47
*** dcramer_ has quit IRC21:47
russellbi don't know that there's a wiki page i can point to ...21:47
*** beagles is now known as beagles_biab21:48
jog0so the question is, I have been ignoring the conductor planning until now, and my question is why make conductor long term tasks etc21:48
russellbthe related blueprints for havana are unified-migrations (and its child blueprints for cold and live migrations)21:48
russellband query-schedulre21:48
jog0I noticed scheduling doess a conductor hop21:48
*** numero8 has joined #openstack-meeting21:48
russellbyeah, so, there's multiple angles to this21:48
* russellb tries to think of where to start21:48
*** numero8 has quit IRC21:49
jog0so migrations makes a lot of sense to me, query-scheduling just makes things nicer but21:49
russellbwith migrations, one issue is that it's not great for security to have compute nodes telling each other what to do21:49
alaskijog0: I think it makes the most sense when you consider something like migrate.  it needs to communicate with the source and destination21:49
*** nachi has quit IRC21:49
russellbanother thing that applies to migrations and the instance build, is just status tracking of long running tasks21:49
jog0alaski: yes things like migrations make sens to me.21:49
jog0russellb: this sounds like a change that needs well documented reasoning21:49
russellbwe want to be able to eventually have graceful handling of these tasks, even if a service has to restart, for example21:50
jog0can you expand on what status tracking for long running tasks actually means21:50
russellband having it anchored in one spot makes it much more achievable to do that21:50
*** ryanpetrello has quit IRC21:50
jog0russellb: one spot in code doesn't have to be one service though21:50
russellbso you think hopping through the scheduler is better?21:50
russellbi won't argue that what we've done / are doing is the best possible way, most things aren't :-)21:51
russellbbut is it an iterative improvement?21:51
jog0not any worse.21:51
russellbi think it is, but if it isn't, we need to reconsider21:51
jog0russellb: without knowing what the goal clearly is its hard to say21:51
russellbso is your concern specifically with the scheduler related build_instance bit you were looking at?21:51
jog0I am fairly sure this won't make things worse in anyway my question is more of is this a good use of our time.  (I am playing devils advocate here)21:52
*** topol has quit IRC21:52
jog0russellb: my concern is we are going down a road without a clear idea of what we are trying to do21:52
alaskiwell, we're taking a very short step right now21:52
jog0unfiy task logic makes sense to me, but there are other ways to do that  Ithink21:53
alaskiand where we go after that is open for discussion21:53
jog0alaski: right, but doesn't it make sense to have the discussion before?21:53
russellbmaking the scheduler interface much simpler21:53
yjiang5jog0: agree.21:53
comstudwe discussed this at the summit21:53
*** nachi has joined #openstack-meeting21:53
comstudunless I just dreamed it21:53
jog0note: I am not saying i don't like this, just saying  I want to see a detailed answer why I am completely wrong21:53
russellbyep, and should probably have another chat about next steps21:53
alaskiyeah, there was discussion21:53
*** nachi_ has joined #openstack-meeting21:53
russellbjog0: well ... i think the burden is on you to say what's bad21:54
russellbnot that you're owed an explanation of why it's good21:54
jog0comstud: IMHO at this point in OpenStacks life a discussion at the summit without a doc summing it up isn't enough21:54
*** markmcclain has quit IRC21:54
russellbjust a general opinion on things21:54
comstudjog0: I'm sure there's an etherpad with notes... and then there's the BP.21:54
jog0russellb: because not everyone wants to run conductors21:54
russellbjog0: ok, well why not?21:54
comstudconductor is not necessary here21:54
russellbwe've had many ML threads on this too21:54
comstudit just runs it local if you don't want it21:55
russellbputs all this in nova-api instead basically if you run in that mode21:55
alaskiyes, local mode works fine.  it spawns a greenthread in that case21:55
comstud'local' tends to mean in nova-api for these things.21:55
jog0russellb: right, but the next question is will this actaully make task logic easier to understand?21:55
russellbi think it will/does, yes21:55
alaskiyes, it does21:55
russellbfollowing the process is going to be *much* easier this way21:56
jog0russellb: because ...? (once again devils advocate here)21:56
alaskibecause it's centralized to conductor.  and because it's not mixed in with filtering and weighting concerns in the scheduler21:57
russellbjog0: can you come back with some specific objections?  perhaps it'd be easier to address those?21:58
jog0and why not something like taskflow? and how do we handle when a conductor goes down21:58
jog0russellb: I don't have any objects really21:58
russellbtaskflow is somewhat related here21:58
jog0my objection is the lack of a clear document saying why tis is good21:58
russellbthe issue with that is that we didn't have a place to really utilize it21:58
alaskithis is moving towards being able to look at taskflow21:58
russellbwhat alaski said21:58
dansmithwe're out of time21:59
russellbthis were steps 1-10 and step 20 was (maybe) taskflow21:59
russellbin general21:59
russellbok, time!21:59
russellbthanks everyone!21:59
*** joel-coffman has quit IRC21:59
*** openstack changes topic to "OpenStack Meetings ||"21:59
openstackMeeting ended Thu Aug  8 21:59:29 2013 UTC.  Information about MeetBot at . (v 0.1.4)21:59
openstackMinutes (text):
*** SergeyLukjanov has quit IRC21:59
*** mriedem has left #openstack-meeting22:00
*** vipul-away is now known as vipul22:01
*** itzikb has quit IRC22:02
*** ivasev has quit IRC22:02
*** dani4571 has quit IRC22:03
*** nachi_ has quit IRC22:04
*** nachi has quit IRC22:04
*** melwitt has left #openstack-meeting22:05
*** writerDiane has quit IRC22:06
*** IlyaE has joined #openstack-meeting22:06
*** burt has quit IRC22:07
*** jecarey has quit IRC22:07
*** ravikumar_hp has joined #openstack-meeting22:08
*** ravikumar_hp has quit IRC22:09
*** ravikumar_hp has joined #openstack-meeting22:09
*** jlucci has quit IRC22:12
*** markvan has quit IRC22:13
*** lbragstad has quit IRC22:14
*** noslzzp has quit IRC22:15
*** markmcclain has joined #openstack-meeting22:16
*** jmontemayor has joined #openstack-meeting22:16
*** changbl has quit IRC22:18
*** jmontemayor has quit IRC22:20
*** cdub_ has quit IRC22:22
*** dscannell has quit IRC22:23
*** ytwu1 has joined #openstack-meeting22:24
*** otherwiseguy has quit IRC22:25
*** lpabon has quit IRC22:26
*** ytwu has quit IRC22:26
*** ryanpetrello has joined #openstack-meeting22:26
*** hartsocks has left #openstack-meeting22:27
*** sacharya has quit IRC22:27
*** adrian_otto has left #openstack-meeting22:28
*** ytwu has joined #openstack-meeting22:32
*** ayoung_ has quit IRC22:32
*** vijendar has quit IRC22:33
*** ytwu1 has quit IRC22:34
*** ytwu1 has joined #openstack-meeting22:35
*** ytwu has quit IRC22:36
*** sushils has joined #openstack-meeting22:36
*** ytwu has joined #openstack-meeting22:37
*** ytwu1 has quit IRC22:40
*** afazekas has quit IRC22:41
*** adalbas has quit IRC22:43
*** afazekas has joined #openstack-meeting22:44
*** ytwu1 has joined #openstack-meeting22:44
*** ytwu has quit IRC22:44
*** sarob has quit IRC22:45
*** sarob has joined #openstack-meeting22:46
*** sarob has quit IRC22:49
*** ytwu has joined #openstack-meeting22:51
*** ayoung_ has joined #openstack-meeting22:51
*** kebray has quit IRC22:52
*** kebray has joined #openstack-meeting22:53
*** ytwu1 has quit IRC22:54
*** branen__ has quit IRC22:55
*** vipul is now known as vipul-away22:55
*** vipul-away is now known as vipul22:55
*** suo2 has joined #openstack-meeting22:58
*** suo has quit IRC22:58
*** leif has joined #openstack-meeting22:59
*** leif is now known as Guest5654722:59
*** branen has joined #openstack-meeting23:03
*** debo_os has quit IRC23:03
*** Yada has quit IRC23:05
*** brucer_ has joined #openstack-meeting23:05
*** sarob has joined #openstack-meeting23:07
*** pentameter has quit IRC23:08
*** Yada has joined #openstack-meeting23:10
*** suo2 has quit IRC23:10
*** ayoung_ has quit IRC23:11
*** ayoung_ has joined #openstack-meeting23:11
*** ytwu has quit IRC23:12
*** gpocentek has quit IRC23:12
*** ytwu has joined #openstack-meeting23:13
*** rnirmal has quit IRC23:13
*** markpeek has quit IRC23:13
*** armax has quit IRC23:15
*** gpocentek has joined #openstack-meeting23:20
*** ayoung_ has quit IRC23:22
*** galstrom_zzz is now known as galstrom23:22
*** debo_os has joined #openstack-meeting23:23
*** huats has quit IRC23:24
*** hartsocks has joined #openstack-meeting23:25
*** hartsocks1 has joined #openstack-meeting23:26
*** hartsocks1 has quit IRC23:27
*** ayoung_ has joined #openstack-meeting23:27
*** hartsocks1 has joined #openstack-meeting23:28
*** hartsocks1 has quit IRC23:28
*** ytwu1 has joined #openstack-meeting23:28
*** hartsocks1 has joined #openstack-meeting23:28
*** hartsocks1 has quit IRC23:28
*** huats has joined #openstack-meeting23:29
*** huats has quit IRC23:29
*** huats has joined #openstack-meeting23:29
*** sdake_ has quit IRC23:29
*** ytwu has quit IRC23:29
*** hartsocks has quit IRC23:30
*** sacharya has joined #openstack-meeting23:30
*** hartsocks has joined #openstack-meeting23:31
*** venkatesh has joined #openstack-meeting23:32
*** vipul is now known as vipul-away23:33
*** ytwu has joined #openstack-meeting23:35
*** ytwu1 has quit IRC23:36
*** changbl has joined #openstack-meeting23:36
*** kebray has quit IRC23:36
*** sacharya has quit IRC23:37
*** galstrom is now known as galstrom_zzz23:38
*** markwash has joined #openstack-meeting23:38
*** ytwu1 has joined #openstack-meeting23:39
*** ytwu has quit IRC23:39
*** fifieldt has joined #openstack-meeting23:40
*** Guest56547 has quit IRC23:42
*** ayoung_ has quit IRC23:42
*** ayoung_ has joined #openstack-meeting23:42
*** galstrom_zzz is now known as galstrom23:43
*** ytwu1 has quit IRC23:43
*** ytwu has joined #openstack-meeting23:43
*** vipul-away is now known as vipul23:44
*** branen_ has joined #openstack-meeting23:45
*** herndon has joined #openstack-meeting23:49
*** jpeeler has quit IRC23:52
*** zul has joined #openstack-meeting23:53
*** ytwu1 has joined #openstack-meeting23:54
*** jhenner has quit IRC23:54
*** ytwu has quit IRC23:55
*** gongysh has joined #openstack-meeting23:56
*** ytwu has joined #openstack-meeting23:57
*** IlyaE has quit IRC23:57
*** ayoung_ has quit IRC23:58
*** ytwu1 has quit IRC23:58

Generated by 2.14.0 by Marius Gedminas - find it at!