Thursday, 2013-11-14

*** dcramer_ has joined #openstack-meeting00:00
*** mrodden has joined #openstack-meeting00:01
*** jroovers has quit IRC00:02
*** herndon_ has quit IRC00:07
*** vuil has quit IRC00:11
*** markpeek has joined #openstack-meeting00:11
*** vuil has joined #openstack-meeting00:12
*** rfolco has quit IRC00:13
*** gatuus has quit IRC00:23
*** nati_ueno has quit IRC00:24
*** nati_ueno has joined #openstack-meeting00:25
*** rfolco has joined #openstack-meeting00:26
*** bill_az has quit IRC00:27
*** rnirmal has quit IRC00:27
*** rakhmerov has joined #openstack-meeting00:29
*** matsuhashi has quit IRC00:29
*** nati_ueno has quit IRC00:30
*** matsuhashi has joined #openstack-meeting00:30
*** diogogmt has joined #openstack-meeting00:32
*** jlucci has quit IRC00:32
*** diogogmt has quit IRC00:33
*** matsuhashi has quit IRC00:34
*** dvarga has joined #openstack-meeting00:35
*** rakhmerov has quit IRC00:36
*** markpeek has quit IRC00:36
*** diogogmt has joined #openstack-meeting00:36
*** sacharya has joined #openstack-meeting00:38
*** coolsvap has quit IRC00:38
*** Linz has quit IRC00:39
*** Linz has joined #openstack-meeting00:40
*** fifieldt has joined #openstack-meeting00:40
*** ywu has quit IRC00:43
*** terriyu has joined #openstack-meeting00:44
*** rfolco has quit IRC00:44
*** smurugesan1 has joined #openstack-meeting00:47
*** ayoung has quit IRC00:48
*** vuil has quit IRC00:48
*** ayoung has joined #openstack-meeting00:49
*** smurugesan has quit IRC00:51
*** smurugesan1 has quit IRC00:52
*** bill_az has joined #openstack-meeting00:54
*** jlucci has joined #openstack-meeting00:54
*** bill_az has quit IRC00:55
*** sdake has quit IRC00:57
*** funzo has quit IRC00:58
*** sdake has joined #openstack-meeting01:00
*** sdake has quit IRC01:00
*** sdake has joined #openstack-meeting01:00
*** danwent has joined #openstack-meeting01:01
*** bpb has quit IRC01:02
*** nati_ueno has joined #openstack-meeting01:02
*** nosnos has joined #openstack-meeting01:05
*** nosnos has quit IRC01:05
*** nosnos has joined #openstack-meeting01:06
*** herndon_ has joined #openstack-meeting01:07
*** matsuhashi has joined #openstack-meeting01:07
*** markpeek has joined #openstack-meeting01:09
*** pablosan has joined #openstack-meeting01:14
*** vito-ordaz has joined #openstack-meeting01:16
*** smurugesan has joined #openstack-meeting01:18
*** mrodden has quit IRC01:20
*** dims has quit IRC01:21
*** markpeek has quit IRC01:30
*** markpeek has joined #openstack-meeting01:31
*** rakhmerov has joined #openstack-meeting01:33
*** markpeek has quit IRC01:36
*** dims has joined #openstack-meeting01:36
*** jasondotstar has joined #openstack-meeting01:37
*** terriyu has quit IRC01:38
*** markwash has quit IRC01:40
*** Jianyong has joined #openstack-meeting01:40
*** cdub_ has quit IRC01:43
*** bdpayne has quit IRC01:46
*** dnavale has quit IRC01:48
*** rongze has joined #openstack-meeting01:50
*** herndon_ has quit IRC01:51
*** nermina has quit IRC01:56
*** jlucci has quit IRC01:59
*** vito-ordaz has quit IRC02:04
*** rakhmerov has quit IRC02:06
*** yaguang has joined #openstack-meeting02:10
*** markwash has joined #openstack-meeting02:11
*** dolphm has joined #openstack-meeting02:13
*** suo has joined #openstack-meeting02:23
*** twoputt_ has quit IRC02:24
*** twoputt has quit IRC02:24
*** sacharya has quit IRC02:27
*** sacharya has joined #openstack-meeting02:32
*** sacharya has quit IRC02:34
*** nati_ueno has quit IRC02:34
*** nati_ueno has joined #openstack-meeting02:35
*** vipul is now known as vipul-away02:35
*** oubiwann has quit IRC02:36
*** krtaylor has joined #openstack-meeting02:37
*** nati_uen_ has joined #openstack-meeting02:37
*** nati_ueno has quit IRC02:38
*** esker has joined #openstack-meeting02:38
*** markwash has quit IRC02:41
*** dcramer_ has quit IRC02:41
*** Jianyong has quit IRC02:41
*** vipul-away is now known as vipul02:43
*** nati_uen_ has quit IRC02:44
*** nati_ueno has joined #openstack-meeting02:44
*** kartikaditya has quit IRC02:44
*** jasondotstar has quit IRC02:45
*** nati_ueno has quit IRC02:48
*** dcramer_ has joined #openstack-meeting02:53
*** neelashah has joined #openstack-meeting02:55
*** jlucci has joined #openstack-meeting02:56
*** kgriffs_afk is now known as kgriffs03:02
*** rakhmerov has joined #openstack-meeting03:03
*** galstrom_zzz is now known as galstrom03:03
*** galstrom is now known as galstrom_zzz03:04
*** rakhmerov has quit IRC03:06
*** rakhmerov has joined #openstack-meeting03:06
*** jasondotstar has joined #openstack-meeting03:08
*** michchap has quit IRC03:19
*** michchap has joined #openstack-meeting03:19
*** enikanorov has quit IRC03:20
*** jasondotstar has quit IRC03:21
*** jasondotstar has joined #openstack-meeting03:21
*** ItSANgo has quit IRC03:21
*** enikanorov has joined #openstack-meeting03:22
*** jasondotstar has quit IRC03:27
*** ItSANgo has joined #openstack-meeting03:35
*** dims has quit IRC03:36
*** dims has joined #openstack-meeting03:37
*** matsuhashi has quit IRC03:39
*** matsuhashi has joined #openstack-meeting03:40
*** smurugesan has quit IRC03:41
*** dolphm has quit IRC03:43
*** dolphm has joined #openstack-meeting03:43
*** nati_ueno has joined #openstack-meeting03:44
*** matsuhashi has quit IRC03:44
*** DennyZhang has joined #openstack-meeting03:45
*** ItSANgo has quit IRC03:45
*** nati_ueno has quit IRC03:48
*** dolphm has quit IRC03:48
*** martines has quit IRC03:49
*** otherwiseguy has joined #openstack-meeting03:50
*** noslzzp has joined #openstack-meeting03:52
*** sandywalsh has quit IRC03:52
*** nati_ueno has joined #openstack-meeting03:53
*** michchap_ has joined #openstack-meeting03:53
*** DennyZhang has quit IRC03:54
*** DennyZhang has joined #openstack-meeting03:54
*** HenryG has quit IRC03:55
*** ItSANgo has joined #openstack-meeting03:55
*** michchap has quit IRC03:55
*** spzala has quit IRC03:58
*** radix has quit IRC03:58
*** nati_ueno has quit IRC03:59
*** nati_ueno has joined #openstack-meeting04:00
*** michchap has joined #openstack-meeting04:02
*** ayoung has quit IRC04:03
*** ayoung has joined #openstack-meeting04:04
*** nati_uen_ has joined #openstack-meeting04:04
*** nati_ueno has quit IRC04:04
*** martines has joined #openstack-meeting04:04
*** nati_uen_ has quit IRC04:04
*** michchap_ has quit IRC04:04
*** nati_ueno has joined #openstack-meeting04:05
*** sandywalsh has joined #openstack-meeting04:06
*** nati_ueno has quit IRC04:09
*** radez_g0n3 is now known as radez04:09
*** vipul has quit IRC04:09
*** nati_ueno has joined #openstack-meeting04:09
*** vipul has joined #openstack-meeting04:10
*** jcru has quit IRC04:11
*** matsuhashi has joined #openstack-meeting04:17
*** macjack has joined #openstack-meeting04:19
*** masayukig has quit IRC04:21
*** novas0x2a|laptop has quit IRC04:22
*** dims has quit IRC04:23
*** devlaps has quit IRC04:24
*** boris-42 has joined #openstack-meeting04:25
*** chandankumar has quit IRC04:25
*** chandankumar has joined #openstack-meeting04:26
*** diogogmt has quit IRC04:29
*** bdpayne has joined #openstack-meeting04:30
*** danwent has quit IRC04:35
*** radez is now known as radez_g0n304:39
*** marun has joined #openstack-meeting04:40
*** IlyaE has joined #openstack-meeting04:41
*** comay has quit IRC04:42
*** davidhadas_ has joined #openstack-meeting04:47
*** nati_ueno has quit IRC04:49
*** davidhadas has quit IRC04:49
*** nati_ueno has joined #openstack-meeting04:49
*** nati_ueno has quit IRC04:53
*** markpeek has joined #openstack-meeting04:56
*** Mandell has quit IRC04:59
*** matsuhashi has quit IRC05:01
*** matsuhashi has joined #openstack-meeting05:02
*** matsuhashi has quit IRC05:02
*** matsuhashi has joined #openstack-meeting05:07
*** rongze_ has joined #openstack-meeting05:11
*** rongze has quit IRC05:11
*** vito-ordaz has joined #openstack-meeting05:13
*** vito-ordaz has quit IRC05:13
*** neelashah has quit IRC05:14
*** vito-ordaz has joined #openstack-meeting05:14
*** vito-ordaz has joined #openstack-meeting05:15
*** vito-ordaz has quit IRC05:16
*** esker has quit IRC05:16
*** vito-ordaz has joined #openstack-meeting05:16
*** esker has joined #openstack-meeting05:16
*** vito-ordaz has quit IRC05:16
*** vito-ordaz has joined #openstack-meeting05:17
*** nati_ueno has joined #openstack-meeting05:18
*** vito-ordaz has quit IRC05:19
*** vito-ordaz has joined #openstack-meeting05:19
*** otherwiseguy has quit IRC05:20
*** vipul is now known as vipul-away05:20
*** bdpayne has quit IRC05:22
*** vito-ordaz has quit IRC05:23
*** vito-ordaz has joined #openstack-meeting05:24
*** nati_ueno has quit IRC05:24
*** sarob has joined #openstack-meeting05:24
*** nati_ueno has joined #openstack-meeting05:24
*** sarob has quit IRC05:26
*** vito-ordaz has quit IRC05:27
*** sarob has joined #openstack-meeting05:27
*** sarob has quit IRC05:27
*** vito-ordaz has joined #openstack-meeting05:28
*** sarob has joined #openstack-meeting05:28
*** nati_ueno has quit IRC05:29
*** vito-ordaz has quit IRC05:32
*** sarob has quit IRC05:32
*** haomaiwang has quit IRC05:33
*** rongze_ has quit IRC05:33
*** DennyZha` has joined #openstack-meeting05:33
*** rongze has joined #openstack-meeting05:34
*** DennyZhang has quit IRC05:36
*** vipul-away is now known as vipul05:37
*** rongze has quit IRC05:38
*** garyk has quit IRC05:43
*** reed has quit IRC05:43
*** zhikunliu has joined #openstack-meeting05:44
*** vipul is now known as vipul-away05:52
*** vipul-away is now known as vipul05:56
*** matsuhashi has quit IRC06:02
*** matsuhashi has joined #openstack-meeting06:02
*** jlucci has quit IRC06:02
*** markpeek has quit IRC06:02
*** afazekas has joined #openstack-meeting06:03
*** matsuhashi has quit IRC06:07
*** matsuhashi has joined #openstack-meeting06:07
*** resker has joined #openstack-meeting06:09
*** fnaval_ has quit IRC06:11
*** matsuhashi has quit IRC06:11
*** esker has quit IRC06:12
*** matsuhashi has joined #openstack-meeting06:12
*** coolsvap has joined #openstack-meeting06:13
*** matsuhashi has quit IRC06:16
*** matsuhashi has joined #openstack-meeting06:17
*** Mandell has joined #openstack-meeting06:23
*** radix has joined #openstack-meeting06:24
*** mrunge has joined #openstack-meeting06:26
*** dcramer_ has quit IRC06:28
*** Mandell has quit IRC06:28
*** zhikunliu has quit IRC06:28
*** IlyaE has quit IRC06:28
*** yaguang has quit IRC06:28
*** beyounn has quit IRC06:28
*** salv-orlando has quit IRC06:28
*** sgran has quit IRC06:28
*** thouveng has quit IRC06:28
*** Nikolay_St has quit IRC06:28
*** termie has quit IRC06:28
*** swifterdarrell has quit IRC06:28
*** esheffield has quit IRC06:28
*** ameade has quit IRC06:28
*** e-vad has quit IRC06:28
*** bdperkin has quit IRC06:28
*** matsuhashi has quit IRC06:30
*** matsuhashi has joined #openstack-meeting06:30
*** matsuhashi has quit IRC06:30
*** matsuhashi has joined #openstack-meeting06:30
*** markwash has joined #openstack-meeting06:34
*** sarob has joined #openstack-meeting06:38
*** dcramer_ has joined #openstack-meeting06:42
*** sarob has quit IRC06:43
*** kgriffs is now known as kgriffs_afk06:44
*** mjbright__ has quit IRC06:53
*** maxdml has quit IRC06:58
*** nati_ueno has joined #openstack-meeting07:00
*** denis_makogon has joined #openstack-meeting07:02
*** nati_ueno has quit IRC07:09
*** garyk has joined #openstack-meeting07:11
*** alexpilotti has joined #openstack-meeting07:12
*** nati_ueno has joined #openstack-meeting07:13
*** jlibosva has joined #openstack-meeting07:14
*** macjack has quit IRC07:15
*** nati_uen_ has joined #openstack-meeting07:17
*** macjack has joined #openstack-meeting07:20
*** nati_ueno has quit IRC07:20
*** doron_afk has joined #openstack-meeting07:22
*** shadower has joined #openstack-meeting07:24
*** alexpilotti has quit IRC07:26
*** davidhadas_ has quit IRC07:29
*** DennyZha` has quit IRC07:29
*** alexpilotti has joined #openstack-meeting07:30
*** ildikov has joined #openstack-meeting07:31
*** akuznetsov has quit IRC07:34
*** akuznetsov has joined #openstack-meeting07:35
*** coolsvap has quit IRC07:40
*** elo has joined #openstack-meeting07:40
*** elo has quit IRC07:41
*** jcoufal has joined #openstack-meeting07:41
*** akuznetsov has quit IRC07:45
*** coolsvap has joined #openstack-meeting07:47
*** coolsvap has quit IRC07:49
*** flaper87|afk is now known as flaper8707:51
*** belmoreira has joined #openstack-meeting07:53
*** belmoreira has quit IRC07:54
*** belmoreira has joined #openstack-meeting07:54
*** noslzzp has quit IRC07:55
*** lbragstad has joined #openstack-meeting07:56
*** Krast has joined #openstack-meeting07:58
*** alexpilotti has quit IRC07:58
*** coolsvap has joined #openstack-meeting08:00
*** ndipanov has joined #openstack-meeting08:01
*** ndipanov has quit IRC08:03
*** mjbright_ has joined #openstack-meeting08:03
*** nati_uen_ has quit IRC08:03
*** ndipanov has joined #openstack-meeting08:04
*** coolsvap has quit IRC08:08
*** nati_ueno has joined #openstack-meeting08:08
*** coolsvap has joined #openstack-meeting08:09
*** nprivalova has joined #openstack-meeting08:09
*** vito-ordaz has joined #openstack-meeting08:09
*** doron_afk is now known as doron08:12
*** cody-somerville has quit IRC08:13
*** doron is now known as doron_afk08:14
*** doron_afk is now known as doron08:14
*** doron is now known as doron_afk08:18
*** rongze has joined #openstack-meeting08:26
*** coolsvap has quit IRC08:28
*** doron_afk is now known as doron08:28
*** saurabh_ has left #openstack-meeting08:28
*** matsuhashi has quit IRC08:30
*** matsuhashi has joined #openstack-meeting08:35
*** orion66 has joined #openstack-meeting08:36
*** garyk1 has joined #openstack-meeting08:37
*** ItSANgo has quit IRC08:39
*** markwash has quit IRC08:40
*** hub_cap_ has joined #openstack-meeting08:40
*** denis_makogon has quit IRC08:40
*** shadower_ has joined #openstack-meeting08:41
*** rossella_s has joined #openstack-meeting08:43
*** lbragstad has quit IRC08:44
*** michchap is now known as 45PAALEL308:44
*** 20WAAKLSA has joined #openstack-meeting08:44
*** michchap has joined #openstack-meeting08:44
*** Mandell has joined #openstack-meeting08:44
*** zhikunliu has joined #openstack-meeting08:44
*** IlyaE has joined #openstack-meeting08:44
*** yaguang has joined #openstack-meeting08:44
*** beyounn has joined #openstack-meeting08:44
*** Nikolay_St has joined #openstack-meeting08:44
*** thouveng has joined #openstack-meeting08:44
*** salv-orlando has joined #openstack-meeting08:44
*** sgran has joined #openstack-meeting08:44
*** termie has joined #openstack-meeting08:44
*** swifterdarrell has joined #openstack-meeting08:44
*** esheffield has joined #openstack-meeting08:44
*** ameade has joined #openstack-meeting08:44
*** e-vad has joined #openstack-meeting08:44
*** bdperkin has joined #openstack-meeting08:44
*** flaper87 has quit IRC08:44
*** flaper87 has joined #openstack-meeting08:44
*** al-maisan_ has joined #openstack-meeting08:44
*** lsmola_ has joined #openstack-meeting08:45
*** jlibosva has quit IRC08:45
*** jlibosva has joined #openstack-meeting08:45
*** doron has quit IRC08:45
*** doron has joined #openstack-meeting08:45
*** shadower has quit IRC08:45
*** shadower has joined #openstack-meeting08:45
*** ildikov has quit IRC08:45
*** ildikov has joined #openstack-meeting08:45
*** jcoufal has quit IRC08:45
*** jcoufal has joined #openstack-meeting08:45
*** mjbright_ has quit IRC08:45
*** mjbright_ has joined #openstack-meeting08:45
*** ndipanov has quit IRC08:45
*** ndipanov has joined #openstack-meeting08:45
*** shadower_ has quit IRC08:45
*** shadower_ has joined #openstack-meeting08:45
*** lsmola_ has quit IRC08:45
*** lsmola_ has joined #openstack-meeting08:45
*** Krast has quit IRC08:45
*** shadower has quit IRC08:45
*** jlibosva has quit IRC08:45
*** garyk has quit IRC08:45
*** radix has quit IRC08:45
*** 45PAALEL3 has quit IRC08:45
*** vahidh has quit IRC08:45
*** matiu has quit IRC08:45
*** moe66 has quit IRC08:45
*** lsmola has quit IRC08:45
*** al-maisan has quit IRC08:45
*** fbo_away has quit IRC08:45
*** jesusaurus has quit IRC08:45
*** hub_cap has quit IRC08:45
*** GheRivero has quit IRC08:45
*** radez_g0n3 has quit IRC08:45
*** matiu has joined #openstack-meeting08:46
*** matiu has quit IRC08:46
*** matiu has joined #openstack-meeting08:46
*** Krast has joined #openstack-meeting08:46
*** radix has joined #openstack-meeting08:46
*** vahidh has joined #openstack-meeting08:46
*** fbo_away has joined #openstack-meeting08:46
*** jesusaurus has joined #openstack-meeting08:46
*** GheRivero has joined #openstack-meeting08:46
*** radez_g0n3 has joined #openstack-meeting08:46
*** nosnos has quit IRC08:46
*** jlibosva has joined #openstack-meeting08:47
*** boris-42 has quit IRC08:47
*** IlyaE has quit IRC08:47
*** boris-42 has joined #openstack-meeting08:49
*** Mandell has quit IRC08:50
*** ItSANgo has joined #openstack-meeting08:51
*** markwash has joined #openstack-meeting08:54
*** akuznetsov has joined #openstack-meeting08:58
*** markwash has quit IRC09:00
*** doron is now known as doron_afk09:03
*** nati_ueno has quit IRC09:06
*** nati_ueno has joined #openstack-meeting09:09
*** davidhadas has joined #openstack-meeting09:10
*** yassine has joined #openstack-meeting09:11
*** vito-ordaz has quit IRC09:15
*** IlyaE has joined #openstack-meeting09:15
*** elo has joined #openstack-meeting09:15
*** vito-ordaz has joined #openstack-meeting09:15
*** jtomasek has joined #openstack-meeting09:16
*** coolsvap has joined #openstack-meeting09:16
*** derekh has joined #openstack-meeting09:19
*** vito-ordaz has quit IRC09:19
*** boris-42 has quit IRC09:21
*** svapneel has joined #openstack-meeting09:27
*** svapneel has quit IRC09:27
*** svapneel has joined #openstack-meeting09:27
*** salv-orlando has quit IRC09:28
*** elo has quit IRC09:28
*** coolsvap has quit IRC09:28
*** svapneel has quit IRC09:31
*** coolsvap has joined #openstack-meeting09:32
*** rongze has quit IRC09:33
*** rongze has joined #openstack-meeting09:33
*** jorisroovers has joined #openstack-meeting09:34
*** nprivalova is now known as nadya_09:37
*** rongze has quit IRC09:38
*** rongze has joined #openstack-meeting09:38
*** rongze has quit IRC09:43
*** rongze has joined #openstack-meeting09:44
*** zhikunliu has quit IRC09:44
*** ygbo has joined #openstack-meeting09:45
*** rongze has quit IRC09:48
*** coolsvap has quit IRC09:51
*** davidhadas has quit IRC09:51
*** coolsvap has joined #openstack-meeting09:52
*** al-maisan_ is now known as al-maisan09:52
*** elo has joined #openstack-meeting09:58
*** sushils has joined #openstack-meeting10:00
*** bgorski has joined #openstack-meeting10:03
*** nati_ueno has quit IRC10:06
*** nati_ueno has joined #openstack-meeting10:07
*** ildikov has quit IRC10:09
*** nati_ueno has quit IRC10:11
*** Krast has quit IRC10:13
*** elo has quit IRC10:15
*** matsuhashi has quit IRC10:20
*** matsuhashi has joined #openstack-meeting10:21
*** SergeyLukjanov has joined #openstack-meeting10:24
*** matsuhashi has quit IRC10:25
*** 20WAAKLSA has quit IRC10:32
*** ildikov has joined #openstack-meeting10:32
*** nosnos has joined #openstack-meeting10:33
*** nosnos has quit IRC10:37
*** elo has joined #openstack-meeting10:41
*** svapneel has joined #openstack-meeting10:43
*** svapneel has quit IRC10:44
*** coolsvap has quit IRC10:44
*** elo has quit IRC10:56
*** metabro has joined #openstack-meeting11:01
*** salv-orlando has joined #openstack-meeting11:01
*** macjack has quit IRC11:02
*** macjack has joined #openstack-meeting11:03
*** ayoung has quit IRC11:04
*** fifieldt has quit IRC11:06
*** ayoung has joined #openstack-meeting11:06
*** jorisroovers has quit IRC11:11
*** doron_afk is now known as doron11:11
*** afrittoli has quit IRC11:15
*** adalbas has joined #openstack-meeting11:18
*** mdenny has quit IRC11:21
*** branen has quit IRC11:23
*** jorisroovers has joined #openstack-meeting11:24
*** jorisroovers has quit IRC11:24
*** boris-42 has joined #openstack-meeting11:24
*** jorisroovers has joined #openstack-meeting11:25
*** ivar-lazzaro has quit IRC11:27
*** ildikov has quit IRC11:29
*** BobBallAway has left #openstack-meeting11:29
*** ildikov has joined #openstack-meeting11:30
*** nadya_ has quit IRC11:36
*** salv-orlando has quit IRC11:39
*** doron is now known as doron_afk11:41
*** nprivalova has joined #openstack-meeting11:44
*** masayukig has joined #openstack-meeting11:45
*** yaguang has quit IRC11:48
*** rfolco has joined #openstack-meeting11:52
*** rfolco has quit IRC11:58
*** michchap has quit IRC12:00
*** rfolco has joined #openstack-meeting12:00
*** michchap has joined #openstack-meeting12:02
*** weshay has joined #openstack-meeting12:05
*** rongze has joined #openstack-meeting12:07
*** haomaiwang has joined #openstack-meeting12:08
*** ayoung has quit IRC12:11
*** ayoung has joined #openstack-meeting12:11
*** danwent has joined #openstack-meeting12:19
*** dims has joined #openstack-meeting12:21
*** ArxCruz has quit IRC12:26
*** ArxCruz has joined #openstack-meeting12:26
*** dkranz has quit IRC12:31
*** ndipanov has quit IRC12:31
*** dkranz has joined #openstack-meeting12:32
*** akrivoka has joined #openstack-meeting12:33
*** doron_afk is now known as doron12:34
*** shanks has quit IRC12:35
*** shanks has joined #openstack-meeting12:36
*** danwent has quit IRC12:36
*** michchap has quit IRC12:37
*** michchap has joined #openstack-meeting12:37
*** jcoufal has quit IRC12:37
*** topol has joined #openstack-meeting12:38
*** jtomasek has quit IRC12:40
*** akrivoka has quit IRC12:40
*** akrivoka has joined #openstack-meeting12:41
*** dkranz has quit IRC12:43
*** akrivoka has quit IRC12:43
*** jtomasek has joined #openstack-meeting12:44
*** shanks has quit IRC12:44
*** jtomasek has quit IRC12:45
*** shanks has joined #openstack-meeting12:45
*** jtomasek has joined #openstack-meeting12:45
*** pcm_ has joined #openstack-meeting12:46
*** akrivoka has joined #openstack-meeting12:46
*** HenryG has joined #openstack-meeting12:49
*** thomasem has joined #openstack-meeting12:51
*** weshay has quit IRC12:54
*** weshay has joined #openstack-meeting12:55
*** shanks has quit IRC12:55
*** shanks has joined #openstack-meeting12:56
*** ryanpetrello has quit IRC12:59
*** ndipanov has joined #openstack-meeting13:02
*** dims has quit IRC13:04
*** ildikov has quit IRC13:04
*** IlyaE has quit IRC13:05
*** dims has joined #openstack-meeting13:06
*** suo has quit IRC13:07
*** dolphm has joined #openstack-meeting13:09
*** kevinconway has quit IRC13:09
*** ildikov has joined #openstack-meeting13:09
*** IlyaE has joined #openstack-meeting13:11
*** jhenner has joined #openstack-meeting13:12
*** dolphm_ has joined #openstack-meeting13:13
*** dolphm has quit IRC13:13
*** alexpilotti has joined #openstack-meeting13:14
*** masayukig has quit IRC13:17
*** DinaBelova has joined #openstack-meeting13:19
*** resker has quit IRC13:20
*** dims has quit IRC13:24
*** vkmc has joined #openstack-meeting13:25
*** SergeyLukjanov is now known as _SergeyLukjanov13:25
*** _SergeyLukjanov has quit IRC13:26
*** dims has joined #openstack-meeting13:28
*** ndipanov has quit IRC13:29
*** eharney has joined #openstack-meeting13:29
*** sandywalsh has quit IRC13:33
*** yaguang has joined #openstack-meeting13:35
*** kevinconway has joined #openstack-meeting13:35
*** fnaval_ has joined #openstack-meeting13:42
*** dkranz has joined #openstack-meeting13:45
*** sandywalsh has joined #openstack-meeting13:46
*** dprince has joined #openstack-meeting13:50
*** dcramer_ has quit IRC13:51
*** iwamoto has joined #openstack-meeting13:51
*** kevinconway has quit IRC13:52
*** doron is now known as doron_afk13:53
*** ayoung has quit IRC13:53
*** jtomasek has quit IRC13:53
*** oda-g has joined #openstack-meeting13:53
*** herndon_ has joined #openstack-meeting13:54
*** kevinconway has joined #openstack-meeting13:57
enikanorovhi13:57
enikanorovneutron lbaas subteam meeting in 2 minutes13:58
iwamotohi13:59
*** DinaBelova has quit IRC13:59
enikanorov#startmeeting neutron-lbaas14:00
openstackMeeting started Thu Nov 14 14:00:30 2013 UTC and is due to finish in 60 minutes.  The chair is enikanorov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
obondarevhi14:00
*** openstack changes topic to " (Meeting topic: neutron-lbaas)"14:00
openstackThe meeting name has been set to 'neutron_lbaas'14:00
enikanorovhi, who;s around?14:00
obondarevo/14:01
iwamotome too14:01
ilyashakhatenikanorov: what's the agenda?14:02
enikanorovok, not too many of us14:02
enikanorovthe agenda for the meeting is14:02
enikanorov1. BPs to be proposed for I-114:02
enikanorov2. QA and 3rd party testing14:02
enikanorov3. Dev resources evaluation14:03
enikanorov4. Additiona lbaasl features to consider in Icehouse14:03
*** Vijay_ has joined #openstack-meeting14:03
enikanorov#topic Blueprints to be proposed for Icehouse-114:03
*** openstack changes topic to "Blueprints to be proposed for Icehouse-1 (Meeting topic: neutron-lbaas)"14:03
*** manish_ has joined #openstack-meeting14:03
*** s3wong has joined #openstack-meeting14:04
enikanorovwe've got big plans for Icehouse in terms of features14:04
enikanoroveven more in terms of blueprints14:04
*** Manur has joined #openstack-meeting14:04
enikanorovand even more in terms of expected patchsets14:04
enikanorovhowever currently we experience problems with neutron gating14:05
*** avishayb has joined #openstack-meeting14:05
enikanorovlots of patches baing stuck14:05
obondarevis there anything already proposed for I1?14:05
*** evgenyf has joined #openstack-meeting14:05
obondarevI mean blueprints14:05
*** ildikov has quit IRC14:06
avishaybhi - i just joined14:06
enikanorovyeah, from my side it would be:14:06
enikanorov#link https://blueprints.launchpad.net/neutron/+spec/lbaas-service-instance14:06
enikanorov#link https://blueprints.launchpad.net/neutron/+spec/lbaas-extensions14:06
obondarevdo you plan this for I1?14:06
obondarevore for I2 maybe?14:07
enikanorovI plan that implementation will be ready in I-114:07
avishaybfrom radware side: SSL + L714:07
enikanorovhowever since we only have 3 weeks left in I-114:07
obondarevyeah14:07
iwamoto#link https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion14:07
enikanorovi doubt that everything will land14:07
enikanorovregarding SSL and L714:07
avishayblots on the plate .. :-)14:08
enikanorovthese are two different features14:08
obondarevavishayb: can you provide links?14:08
enikanorovso their bp are separate14:08
avishayblet me try and do that.. sam created the BP's - i will find it14:08
enikanorovi think those are here: https://etherpad.openstack.org/p/icehouse-neutron-lbaas14:09
*** elo has joined #openstack-meeting14:09
obondarevfrom my side I have registered l7 rules for haproxy14:09
enikanorovso while I'd encourage you to work on SSL or L7, both features have dependency on some others14:09
Vijay_Hi Avishay, Eugene; Vijay from Citrix. We would also be able to contribute to SSL + L714:09
obondarev#link https://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules-haproxy14:09
obondarevit depends on generic L7 rules blueprint14:10
enikanorovok, let me explain the dependencies14:10
Vijay_https://blueprints.launchpad.net/neutron/+spec/lbaas-ssl-termination14:10
avishaybhttps://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules14:10
Vijay_is the SSL termination blue print14:10
enikanorovL7 feature depends on multiple pools per vip, which has to be implemented first14:10
obondarevyeah14:11
Vijay_yeah14:11
enikanorovso in order to go in parallel, we may start with API changes14:11
obondarevit wasn't listed by the way14:11
enikanorovwhich one?14:11
*** elo has quit IRC14:11
obondarevmultiple vips per pool14:11
*** jecarey has joined #openstack-meeting14:11
obondarevI mean the link14:12
enikanorovi will not propose it for I-114:12
obondarevoh, ok14:12
enikanorovit's more complex than service instance14:12
*** DrBacchus has quit IRC14:12
enikanorovand it's design is not yet agreed on14:12
obondarevyeah, but with many dependencies - isn't it better to implement it first of all?14:12
ilyashakhatbut service instance will also require lots of changes from db to client14:13
ilyashakhatisn't it?14:13
Vijay_The basis for all this is the loadbalancer container object implementation, right?14:13
enikanorovmultiple pools/vips depend on 'loadbalancer instance' that's why it goes first14:13
enikanorovVijay_: correct14:13
obondarevoh, got it, right14:13
enikanorovSo, again, we could propose everything for I-114:13
enikanorovbut realistically, it's only 3 weeks left14:14
enikanorovand we have all those gating problems14:14
enikanorovand hundreds of patches on review14:14
enikanorovso it's better for us to work on code without pushing core team too much14:14
*** terriyu has joined #openstack-meeting14:14
ilyashakhatenikanorov: let's start with loadbalancing instance, l7 staff depends on it14:14
enikanorovbut ahving our code ready and covered by tests14:14
enikanorov*having14:14
*** otherwiseguy has joined #openstack-meeting14:14
enikanorovalso, important note:14:15
enikanorov#action everyone proposing BP for the sprint needs to have wiki page with design description14:15
Vijay_ok14:16
enikanorovVijay_: avishayb: please keep in touch with each other and colalborate on ssl feature14:16
enikanorovssl will depend on extension framework, but it's minor dependency, i'd say14:16
enikanorovany questions/announcements on Icehouse-1 plans?14:17
avishaybOK14:17
Vijay_sure we will co-ordinate between ourselves.14:17
Vijay_Citrix's NetScaler , Driver can be sent for review next week.14:18
iwamotol7 could be implemented without service instances ithink14:18
*** markpeek has joined #openstack-meeting14:18
s3wongIs there any particular areas/implementations of these bps that need help on?14:18
enikanorovI'll appreciate if  you also will keep us in the loop :)14:18
iwamotojust to make later changes easier?14:18
*** neelashah has joined #openstack-meeting14:18
enikanorovs3wong: that will be the next topic :)14:18
enikanoroviwamoto: l7 depends on multiple pools per vip which depends on serviec instance14:19
s3wongenikanorov: Cool :-)14:19
*** maxdml has joined #openstack-meeting14:19
enikanorov#topic QA & third-party testing14:19
*** openstack changes topic to "QA & third-party testing (Meeting topic: neutron-lbaas)"14:19
avishaybquestion: whay ssl has dependency on extension framework? I thought this it is not related to extension.14:19
*** lblanchard has joined #openstack-meeting14:19
avishayb*why14:19
*** julim has joined #openstack-meeting14:19
enikanorovavishayb: that's the decision from the design session14:19
enikanorovso, going back to QA14:20
avishaybok.. I wans not aware.14:20
enikanorovobondarev started to work on adding scenario tests to tempest for lbaas14:20
enikanorovobondarev: do you want do update us with your progress?14:20
*** boris-42 has quit IRC14:20
obondarevwell, work in progress:)14:20
obondarevwant to implement basic lbaas workflow14:21
enikanorovgood to know :)14:21
obondarevand validate loadbalancing is happening actually14:21
*** jpeeler has joined #openstack-meeting14:21
*** jpeeler has quit IRC14:21
*** jpeeler has joined #openstack-meeting14:21
obondarevIOW automate this test: https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun#Validation14:21
enikanorovok, cool14:21
enikanorovavishayb: do you guys start working on setting up smoke test system in your environment?14:22
enikanorov#link http://ci.openstack.org/third_party.html14:22
avishaybno - not yet14:22
s3wongobondarev: there is a periodic task pulling stats, right? Should that be exposed to verify LBaaS instance is working and doing something?14:23
enikanorovit's expected at I-2, which is actually just 2 months away14:23
enikanorovobondarev: btw, don't forget that test should not be haproxy-specific14:23
sgransorry I'm a bit late, I'm running between rooms at a conference.  I'd have a few things on my mind if there is time.  I see there is already a pretty full agenda, so please get to me last :)14:23
enikanorovsince we are going to run the same tests for all vendors14:23
obondarevs3wong: not sure14:23
obondarevenikanorov: yeah14:24
enikanorovsgran: i guess we will have time for the open discussion14:24
sgrangreat, thanks14:24
*** johnthetubaguy has joined #openstack-meeting14:24
Vijay_obondarev: will the tests check the data path by sending traffic to the the VIP ?14:25
*** esker has joined #openstack-meeting14:26
enikanorovit should14:26
obondarevVijay_:yes, as it described on the wiki14:26
*** dikov has joined #openstack-meeting14:26
*** dikov has quit IRC14:26
enikanorovok, i suggest we count our heads and see who's doing what14:26
enikanorov#topic dev resources evaluation14:27
*** openstack changes topic to "dev resources evaluation (Meeting topic: neutron-lbaas)"14:27
enikanorovi'll start with myself14:27
*** ildikov has joined #openstack-meeting14:27
enikanorovas i said, i'm going to work on service instance and extension framework14:27
enikanorovobondarev: ?14:27
obondarevI need to wait untill can start working on lbaas-l7-rules, now working on the tests14:28
obondarevcan help with any bp for I114:28
enikanorovok, good to know14:28
enikanorovavishayb: ?14:28
*** bogdando has quit IRC14:28
Vijay_eugene, just for my own clarity; service instance is the loadbalancer container/wrapper instance right?14:28
enikanorovVijay_: correct14:28
avishaybwe are two people working on the SSL and L7 blueprints14:29
s3wongI can help with any bp for l1 as well14:29
enikanorovavishayb: who is the other one?14:29
*** kevinconway has quit IRC14:29
avishaybEvgeny Fedoruk14:30
enikanorovi see, good14:30
Vijay_from my side, i will work with avishayb to cleanup the blueprint on SSL & L7 BluePrints and design doc14:30
enikanorovVijay_: cool14:30
enikanorovs3wong: sgran: you guys?14:30
*** nermina has joined #openstack-meeting14:30
sgranhi14:31
sgranI'm writing a plugin for the neutron LBaaS, to manage stingray loadbalancer14:31
enikanorovs3wong: I'll see if I could share something to help me with14:31
s3wongenikanorov: please let me know where I can lend my hand14:31
enikanorovsgran: i guessed that! :)14:31
sgranhttp://www.riverbed.com/products-solutions/products/application-delivery-stingray/Stingray-Traffic-Manager.html14:32
sgran:)14:32
enikanorovso then one of the tasks will be to keep your code in sync14:32
enikanorovwith the master14:32
sgranI'm watching https://review.openstack.org/#/c/40381/ with interest, so that I know what to sync14:32
enikanorovgood14:32
*** jcoufal has joined #openstack-meeting14:32
*** bogdando has joined #openstack-meeting14:32
*** yassine has quit IRC14:33
sgranmy concern at the moment (I left a note at the bottom of that review) is that the in-memory cache in the agent_manager looks to me like it will make it difficult to have multiple agents for HA14:33
enikanorovsgran: you are also required to setup test environment for your driver, you know14:33
*** yassine has joined #openstack-meeting14:33
enikanorovsgran: yeah, let's discuss it at the end of the meeting14:33
sgranyou mean make a test environment available?14:33
obondarevsgran: yeah, working on that comment..14:33
sgranI have a test environment at work that I'm using to test my code14:33
*** herndon_ has quit IRC14:33
enikanorovsgran: right, implement http://ci.openstack.org/third_party.html14:33
enikanorovshould be fairly simple if you pass your company's security hounds :)14:34
sgranI doubt that that will be possible, but I have contacts at riverbed.  I'll see what they can do for us14:34
sgranI don't actually work for riverbed, so this would mean my company would be paying licensing costs to bring one up to run gate tests on14:35
sgranI don't think they'll like that :)14:35
*** johnthetubaguy1 has joined #openstack-meeting14:36
enikanorovi see14:36
sgranbut yeah, looks straight forward enough14:36
sgranmaybe I can do it with a dev licensed model14:36
sgranI'll ask riverbed, and ask what we can do14:36
*** johnthetubaguy has quit IRC14:37
enikanorovisn't riverbed insterested in adding support for their solution to neutron?14:37
sgranthey are, yeah, but they seem to be moving slowly, which is why I'm ending up writing it :)14:37
enikanorovi see14:37
sgranas I say, I'll talk to them.  They have some people at this conference, so I may be able to get a fast answer14:38
enikanorovok, i think we can move to the next topic14:38
enikanorov#topic Additional features requested by users.14:38
*** openstack changes topic to "Additional features requested by users. (Meeting topic: neutron-lbaas)"14:38
*** markmcclain has quit IRC14:38
enikanorovthose are the features that we missed in the design session and in our vendor discussions14:38
*** SergeyLukjanov has joined #openstack-meeting14:38
enikanorovbut folks raised them at the lbaas presentation14:39
*** kevinconway has joined #openstack-meeting14:39
enikanorovone is to add HA for at least HAProxy provider14:39
*** elo has joined #openstack-meeting14:39
*** yamahata has joined #openstack-meeting14:39
enikanorovthat is one of the most expected feature14:39
obondarevcan you please clarify?14:39
enikanorovhigh availability14:40
obondarevyeah)14:40
sgranhaproxy driver is a SPoF - you lose the host, you lose the LB14:40
*** lbragstad has joined #openstack-meeting14:40
enikanorovusers want haproxy to be highly available, which means that you have more then one balanecer14:40
obondarevcurrently we can run multiple agents14:40
enikanorovif one fails another one picks up the traffic14:40
sgranbut each vip/lb/pool is only on one host14:40
*** zhikunliu has joined #openstack-meeting14:40
sgranthis touches on my concern about the in-memory cache in the agent_manager14:41
obondarevsgran: right14:41
s3wongenikanorov: Is that just having the ability to bind frontend VIP to two haproxy instances? or do people expect things like sticky entries to be in sync between the two haproxy instances?14:41
*** elo has quit IRC14:41
enikanorovsgran: there are secveral approaches to this14:41
enikanorovsince currently HAProxy VIP is on tenant network14:41
enikanorovHA could be done with switching Floating IP from failed haproxy VIP to active one14:41
enikanorovbut that's kinda external monitoring14:41
enikanorovI'd like to see generic HA design for lbaas14:42
sgranyou don't want to use a floating IP, do you?  You'd want another adress on the same port14:42
enikanorovthat could be implemented withing the service14:42
*** doron_afk is now known as doron14:42
*** ivasev has joined #openstack-meeting14:42
enikanorovsgran: i'm not saying that14:42
enikanorovi'm saying that solution for HAProxy will be HAProxy-specific14:42
enikanorovand it looks like a 'foreign' system to neutron (at first glance)14:43
enikanorovanyway14:43
sgranenikanorov: so I think that there are two parts here: whether there are any design decisions that make it hard to have HA LBaaS agents14:43
sgranand then how to make the implementation itself HA14:43
enikanorovif someone is willing to design and implement this feature - you're welcome!14:43
s3wongenikanorov: agree, the LBaaS HA framework should allow driver to specify how they want to sync dynamic states14:43
*** burt has joined #openstack-meeting14:43
obondarevo/14:44
*** kevinconway has quit IRC14:44
enikanorovsgran: i think it's more about HA balancers than agents14:44
obondarevwant to work on this14:44
enikanorovbecause we already may have several lbaas agents14:44
enikanorovand if some agent fail, neutron-server is notified about it14:44
sgrannot really14:44
sgranwe can have multiple agents managing different sets of LB/pool/VIP14:44
sgrannot managing the same set14:44
s3wongenikanorov: what is the monitoring framework to detect LBaaS instance failure?14:45
enikanorovsgran: correct14:45
obondarevcan think of HA for agents in terms of handling one lbaas instance by multiple agents14:45
enikanorovs3wong: there is none14:45
obondarevas a first step at least14:45
* sgran nods obondarev 14:45
sgranthat is exactly what I'm thinking of14:45
enikanorovok, it seems that HA agents is a separate topic14:45
sgranthe implementation I'm working on configures the appliance via a rest api14:45
*** ryanpetrello has joined #openstack-meeting14:45
sgranso in theory, any agent could pick up the update and configure the appliance14:46
sgranit doesn't need a cache of running processes or anything14:46
obondarevsgran: yeah, that what your comment was all about)14:46
*** jpeeler1 has joined #openstack-meeting14:46
enikanorovsgran: right, for such case it's a bit easier14:47
enikanorovbut still, HA is for balancers themselves, agents is different topic14:47
sgranthat's it exactly - I'm trying to make sure that we don't accidentally design the higher level classes in such a way that it makes the implementation classess harder14:47
enikanorovIMO14:47
sgranfair enough, splitting the topic makes sense14:47
*** jpeeler has quit IRC14:48
obondarevagree14:48
enikanorovok, so would be good if someone could pick this up.14:48
*** nprivalova is now known as nadya_14:48
*** dvarga has quit IRC14:48
enikanorovthis is really expected14:48
obondarevI'm ready14:49
s3wongI can help here also14:49
enikanorovok, good14:49
obondarevI'll register a bp for this14:49
sgranI am happy to be part of it.  I've started an etherpad with a braindump14:49
sgrangreat, thanks14:49
enikanorovcool14:49
*** nermina has quit IRC14:49
enikanorovany other items?14:49
enikanorov#topic Open discussion14:50
*** doron is now known as doron_afk14:50
*** openstack changes topic to "Open discussion (Meeting topic: neutron-lbaas)"14:50
*** akrivoka has left #openstack-meeting14:50
*** junxie has joined #openstack-meeting14:50
*** junxie has quit IRC14:50
*** dvarga has joined #openstack-meeting14:51
*** jun has joined #openstack-meeting14:51
iwamotois anyone planning router type loadbalancers (i.e. LVS-like)?14:52
iwamotoI wonder if I'm alone14:52
*** pdmars has joined #openstack-meeting14:52
enikanorovit's up to vendors14:53
Vijay_Are there enhancements planned on the Horizon side for LBaaS? Currently it restricts to configure VIPs only in Pool Networks.14:53
enikanorovi think driver framework and extension framework should allow you to do any wiring you want14:53
enikanorovVijay_: it could be filed as a bug, because it's really should not be so14:53
sgranthere's no such restriction in neutron, so yeah, that's a horizon bug14:54
enikanorovthat was implementation hardcoded to available provider (at grizzly point)14:54
enikanorovnow it should be changed14:54
sgrantime for me to run to another room14:55
*** jpeeler1 is now known as jpeeler14:55
sgranobondarev: if you can leave a note with your thoughts on that change, I'm happy to help14:55
*** jpeeler has quit IRC14:55
*** jpeeler has joined #openstack-meeting14:55
obondarevenikanorov: can add an action iten on it14:55
sgranthanks for your time, everyone14:55
Vijay_can the same driver be loaded as two providers?14:55
*** doron_afk is now known as doron14:56
enikanorov#action file a bug for horizon project to change restriction for the VIP subnet14:56
sgranfor differnt load balancers?  Yes14:56
Vijay_sure14:56
enikanorovVijay_: not at this point14:56
*** ayoung has joined #openstack-meeting14:56
enikanorovVijay_: why are you asking?14:56
Vijay_we have management layer between which sends the calls to the ultimate device.14:57
Vijay_would like to ideally give choices to user14:57
Vijay_to pick providers14:57
enikanorovhow those providers differ one from another?14:57
Vijay_and accordingly configure the VIP/Pools in a device which is according to the provider selection14:57
*** gordc has joined #openstack-meeting14:58
*** bill_az has joined #openstack-meeting14:58
*** eglynn has joined #openstack-meeting14:58
Vijay_currently we are subclassing the plugin driver and created 2 drivers.14:58
*** llu-laptop has joined #openstack-meeting14:58
Vijay_because provider and driver are one to one mapping14:59
enikanorovyeah, so what will be the difference between providers utilizing the same driver?14:59
*** nsaje has joined #openstack-meeting14:59
enikanorovwe have 1 minute left14:59
*** fnaval_ has quit IRC14:59
enikanorovwe can continue on #neutron-lbaas14:59
Vijay_ok15:00
enikanorovlet's go there15:00
enikanorov#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Nov 14 15:00:06 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-11-14-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-11-14-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-11-14-14.00.log.html15:00
jd__#startmeeting ceilometer15:00
openstackMeeting started Thu Nov 14 15:00:30 2013 UTC and is due to finish in 60 minutes.  The chair is jd__. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ceilometer)"15:00
openstackThe meeting name has been set to 'ceilometer'15:00
*** oda-g has left #openstack-meeting15:00
silehto/15:00
apmeltono/15:00
dhellmanno/15:00
lsmola_hello15:00
gordco/15:00
llu-laptopo/15:00
eglynno/15:00
nsajeo/15:00
nadya_o/15:00
zhikunliuo/15:01
jd__hi everybody15:01
sandywalsho/15:01
ildikovo/15:01
thomasemo/15:01
juno/15:01
*** iwamoto has left #openstack-meeting15:01
*** yassine has quit IRC15:01
jd__#topic Pick our official name15:02
*** openstack changes topic to "Pick our official name (Meeting topic: ceilometer)"15:02
jd__#link https://review.openstack.org/#/c/5587715:02
llu-laptopIs it approved?15:02
jd__so there's a little issue around what should be Ceilometer official name15:02
eglynnthe plural form of Measurements seems odd to my ears15:02
dhellmannI agree with eglynn15:02
*** yassine has joined #openstack-meeting15:02
jd__Measurement itself sounds odd to my ears15:02
dhellmannnetworking vs. networks15:03
terriyuo/15:03
eglynnOrchestration versus Orchestrations ;)15:03
jd__I was happy with Metering, but as a non-native speaker…15:03
jd__15:03
*** markvan has joined #openstack-meeting15:03
dhellmannI think the idea was that metering doesn't cover the new monitoring and alarming stuff, right?15:03
*** pdmars has quit IRC15:03
eglynnthe problem with Metering was that it didn't fully reflect the expanded mandate right?15:04
dhellmannalthough I could go with metering myself15:04
eglynnyep15:04
*** jtomasek has joined #openstack-meeting15:04
thomasemWhat about just Monitoring?15:04
jd__Measurement would cover alarming?15:04
eglynnagain doesn't cover the full range of the project15:04
ildikovIs Ceilometer a monitoring tool, or will it be ever?15:04
eglynn(Monitoring that is ...)15:04
*** pdmars has joined #openstack-meeting15:04
dhellmannwe do enough monitoring for alarms15:04
dhellmannand that involves collecting more and different data than metering15:04
*** johnthetubaguy1 has quit IRC15:05
*** johnthetubaguy has joined #openstack-meeting15:05
eglynnyep, so measurement (of resource usage and performance) covers both bases15:05
thomasemMonitoring - we monitor usage, we monitor watermarks for alarming, we will soon have events to monitor arbitrary things defined by the deployers. I don't see how monitoring misses anything?15:05
ildikovUntil we just trying to use aeras for names we will face with the same "not covering all" problem15:05
jd__what about "OpenStack: The Missing Piece"? :)15:05
ildikov:)15:06
*** jasondotstar has joined #openstack-meeting15:06
sileht:)15:06
llu-laptop:-)15:06
*** otherwiseguy has quit IRC15:06
terriyu"Project X" ?15:06
jd__haha15:06
*** bill_az has quit IRC15:06
jd__shall we vote on Measurement then?15:06
*** doron is now known as doron_afk15:06
sandywalshmeasurements doesn't cover events15:06
*** doron_afk is now known as doron15:06
*** bill_az has joined #openstack-meeting15:06
terriyuI dunno, as a native English speaker, measurement doesn't sound that different from metering15:07
sandywalshcollection?15:07
jd__OpenStack Slurp?15:07
nadya_we have processing too15:07
jd__"monitoring" may cover events?15:08
ildikovMaybe an abstract name would be better15:08
jd__ildikov: right, like "Ceilometer" for example? :)15:08
eglynnlike "ceilometer" ;)15:08
eglynnsnap :)15:08
ildikovexactly ;)15:08
juni think the name ceilometer is ok15:08
jd__"OpenStack Ceilometer, codenamed Ceilometer, a project that ceilometer your OpenStack cloud."15:08
*** pdmars has quit IRC15:09
jd__jun: that's not the point, we'll keep the code name15:09
lsmola_+1 to Ceilometer15:09
jd__we just need an official name15:09
*** pdmars has joined #openstack-meeting15:09
lsmola_:-(15:09
dhellmannyeah, we need to pick the name we'll use for trademark purposes15:09
lsmola_then Openstack Slurp :-)15:09
*** bill_az has quit IRC15:10
dhellmannwhat about "metrics"?15:10
*** bill_az has joined #openstack-meeting15:10
eglynnso given that https://review.openstack.org/#/c/55375/ has landed already, the scope for change is fairly narrow, or?15:10
apmeltonwhat about Analytics?15:10
*** rongze has quit IRC15:10
dhellmanneglynn: no, we can "bug fix" the resolution15:10
gordceglynn: was going to ask the same question.15:10
eglynndhellmann: cool15:10
dhellmannapmelton: we *do  not* do analytics15:10
nadya_I like 'monitoring' :) I think if Ceilometer becomes real 'monitoring' tool it will be great15:10
dhellmannthat was specifically restricted from our charter15:11
eglynnwe more enable the doing of analytics by someone else15:11
*** rongze has joined #openstack-meeting15:11
dhellmannright15:11
jd__OpenStack Enabler then?15:11
sandywalshData Collection15:11
* sandywalsh pukes15:11
gordci'm ok with Measurements but i agree with sandywalsh, it doesn't really cover events well.15:11
jd__Auditing?15:11
*** lpabon has joined #openstack-meeting15:11
eglynnDiagnostics?15:11
eglynnTelemetry?15:12
jd__telemetry's nice15:12
dhellmannI sort of like telemetry15:12
ildikovTelemetry sounds good :)15:12
*** thelorax123 has joined #openstack-meeting15:12
eglynncool :)15:12
thomasemA bit esoteric15:12
*** IlyaE has quit IRC15:12
eglynnvery rocket-sciencey15:12
jd__thomasem: like us15:12
*** lpabon has left #openstack-meeting15:12
*** markpeek has quit IRC15:12
nsajetelemetry o/15:12
jd__and it makes me think of teletubbies15:13
eglynnLOL :)15:13
apmelton+1 telemtry15:13
silehtTelemetry sounds good15:13
eglynnwhat's not to like about teletubbies? ;)15:13
sandywalsh+1 Telemetry15:13
terriyuI'm with thomasem , feel like "telemetry" is unnecessarily esoteric15:13
dhellmannas long as we get teletubbies on our new logo, I'm good with it15:13
thomasemNo!15:14
*** vijendar has joined #openstack-meeting15:14
dhellmannesoteric?15:14
thomasemTeletubbies are the most frightening thing on this planet...15:14
jd__#startvote Should Ceilometer pick "OpenStack Telemetry" as it's official project name? Yes, No, Abstain15:14
openstackBegin voting on: Should Ceilometer pick "OpenStack Telemetry" as it's official project name? Valid vote options are Yes, No, Abstain.15:14
openstackVote using '#vote OPTION'. Only your last vote counts.15:14
sandywalshhttp://en.wikipedia.org/wiki/Telemetry15:14
jd__let's vote on this :)15:14
*** joesavak has joined #openstack-meeting15:14
eglynn#vote Yes15:14
lsmola_eglynn, lol15:14
dhellmannpoint of order: should we vote on one name, or vote on the selections?15:14
sandywalshyes15:14
sandywalsh#vote yes15:14
sileht#vote yes15:14
apmelton#vote yes15:14
jd__dhellmann: I think it'll be simpler to vote on a name, otherwise we're going Condorcet :)15:15
dhellmann#vote yes15:15
nsaje#vote yes15:15
thomasem#vote no15:15
yassine#vote yes15:15
ildikov#vote yes15:15
nadya_#vote no15:15
terriyu#vote no15:15
lsmola_#vote yes15:15
*** rongze has quit IRC15:15
*** banix has joined #openstack-meeting15:15
llu-laptop#vote yes15:15
jd__#vote yes15:15
*** nsaje has quit IRC15:15
thomasemFair enough. =]15:15
jun#vote yes15:15
*** nsaje has joined #openstack-meeting15:16
jd__vote ending in a few seconds15:16
jd__tic-tac-tic-tac15:16
*** eharney has quit IRC15:16
jd__#endvote15:16
openstackVoted on "Should Ceilometer pick "OpenStack Telemetry" as it's official project name?" Results are15:16
openstackYes (12): ildikov, apmelton, sileht, sandywalsh, jd__, eglynn, jun, llu-laptop, yassine, dhellmann, lsmola_, nsaje15:16
openstackNo (3): nadya_, thomasem, terriyu15:16
junlooook like we are going to have this Telemetry15:16
junhaha15:16
*** yamahata has quit IRC15:16
*** herndon_ has joined #openstack-meeting15:16
*** ArxCruz has quit IRC15:16
dhellmannis this binding, or is this just polling the room so to speak? do we have anyone else who should be allowed to chime in? nijaba?15:17
sandywalshwell done eglynn15:17
*** whenry has joined #openstack-meeting15:17
jd__dhellmann: I don't think we have any written procedure for that, so…15:17
*** ArxCruz has joined #openstack-meeting15:17
*** Vijay_ has left #openstack-meeting15:17
dhellmannthis feels like a big enough decision that we shouldn't make it just based on who can attend this meeting15:17
jd__dhellmann: shall we ask the TC for a procedure? :)15:18
terriyudhellmann: +115:18
dhellmannit's good to see that there's a certain amount of consensus15:18
eglynndhellmann: well this meeting probably good enough to propose a patch on gerrit15:18
dhellmanneglynn: that sounds like a good next step15:18
*** suo has joined #openstack-meeting15:18
dhellmannand a mailing list thread15:18
eglynn(then nijaba can -2 the patch if he no likee ...)15:18
jd__I think I'd go for a patch and add ceilometer-core as reviewer waiting for everyone to +115:18
*** litong has joined #openstack-meeting15:19
jd__I'm ok doing that if that fits for you dhellmann15:19
*** markmcclain has joined #openstack-meeting15:19
*** llu-laptop|2 has joined #openstack-meeting15:19
eglynnanyone can propose a patch to openstack/governance?15:19
jd__eglynn: I'd hope so :)15:20
eglynn(or just TC/board members)15:20
dhellmannyes15:20
dhellmannanyone15:20
eglynncool15:20
jd__#action jd__ propose a patch to governance for Telemetry and add ceilometer-core as reviewers15:20
*** fnaval_ has joined #openstack-meeting15:20
dhellmannjd__: link to it on https://review.openstack.org/#/c/5587715:20
jd__dhellmann: ack15:20
jd__#topic Release python-ceilometerclient?15:21
*** openstack changes topic to "Release python-ceilometerclient? (Meeting topic: ceilometer)"15:21
*** DrBacchus has joined #openstack-meeting15:21
eglynnno need that I'm aware of15:21
jd__me neither15:21
jd__#topic hardware agent and central agent15:21
*** openstack changes topic to "hardware agent and central agent (Meeting topic: ceilometer)"15:21
jd__llu-laptop go ahaed15:22
lsmola_is llu around?15:22
llu-laptop|2just lost the internet connection. back just in time15:22
*** avishayb has quit IRC15:22
jd__he was15:22
*** llu-laptop has quit IRC15:22
llu-laptop|2i'm here now15:22
lsmola_nice15:22
*** ruhe has joined #openstack-meeting15:22
llu-laptop|2first question, should we get hardware agent merged into central agent first, because I think improving central agent might take some time?15:23
lsmola_so we need to move the whole baremetal agent into the Ironic codebase?15:23
jd__llu-laptop|2: I'd say enhance the central one so it supports hardware, yes15:24
jd__lsmola_: no15:24
*** gatuus has joined #openstack-meeting15:24
lsmola_llu-laptop|2, given the last conversation about the hardware agent, I understood Ironic guys wants to have it in ironic15:24
eglynn#link https://etherpad.openstack.org/p/icehouse-summit-ceilometer-hardware-sensors15:24
jd__the main need for hardware is the ability to provide resources in the pipeline and to make pollster protocol handle taht15:24
*** pablosan has quit IRC15:24
eglynn"ceilometer agent running next to ironic conductor"15:24
lsmola_eglynn, ok, that explains a lot15:25
*** herndon_ has quit IRC15:25
jd__and there's not only Ironic, there's a more general approach too15:25
jd__which is what llu is trying to cover here15:25
*** rbowen has joined #openstack-meeting15:25
*** DrBacchus has quit IRC15:25
eglynn... "running next to" == "separate process, same host"?15:25
llu-laptop|2jd__: ok. things of the 'enhancement' in my mind is 1) 'resources' entry 2) membership and task distribution 3)abstraction layer of pipeline definition loading15:26
*** nsaje has quit IRC15:26
lsmola_eglynn, well what I understood it should run with ironic, be scalable with ironic, etc.15:26
llu-laptop|2do we agree that we need that part 3)?15:26
*** nsaje has joined #openstack-meeting15:26
eglynnwhat usecase would the abstarction layer enable?15:27
eglynn*abstraction15:27
jd__llu-laptop|2: point 2) is not of your concern directly here, it concerns a larger part of Ceilometer so don't worry about it15:27
llu-laptop|2That's Dan Dyer from HP proposed in the design summit. Maybe loading it from DB other than the file?15:27
lsmola_llu-laptop|2, are you considering connectiong to tripleo ?15:28
llu-laptop|2maybe a low priority of part 3?15:28
eglynnOK, nice-to-have, but I don't see a really compelling usecase for that15:28
*** IlyaE has joined #openstack-meeting15:28
eglynnllu-laptop|2: yep, agreed15:28
*** evgenyf has quit IRC15:28
lsmola_llu-laptop|2, if deployed via tripleo, you can obtain baremetals and their IPs from nova, and IMPI credentials from Ironic15:28
*** nsaje has quit IRC15:29
*** jtomasek has quit IRC15:29
*** edmund has quit IRC15:29
lsmola_llu-laptop|2, that is what we want to be configurable, so it automatically polls all resources available15:29
*** rongze has joined #openstack-meeting15:30
jd__lsmola_: that work will help in this regard anyway15:30
jd__llu: anything else or are you clear enough?15:30
llu-laptop|2lsmola_: yes using tripleO+Ironic seems good for ipmi data collection. But what about the situation of not having tripleO?15:30
*** tims has joined #openstack-meeting15:30
lsmola_llu-laptop|2, for for SNMP, you will have to get the IPs from somewhere, defining them by hard will be painfull15:31
jd__not everybody will use Ironic so we'll support that too15:31
lsmola_llu-laptop|2, and you would also define the IPMI credentials by hard15:31
jd__no point in arguing about that15:31
llu-laptop|2I'm not an advocate of SNMP. it's just from the original author, toni15:31
eglynnlsmola_:  "defining baremtals by hand" == "listing IPs in the pipeline.yaml"15:31
eglynn?15:32
lsmola_jd__, well as Tripleo will be official deployment program, and Ironic will become officila in Icehouse too, we should definitely support that, right?15:32
jd__eglynn: and credentials if needed yeah15:32
jd__lsmola_: yes, but not only15:32
eglynnk, that does seem like badness15:32
eglynnway too static to be useful IMO15:32
lsmola_eglynn, yes basically15:32
*** ben_duyujie has joined #openstack-meeting15:33
jd__eglynn: until OpenStack provides an inventory service, that may be a good solution for a lot of corner case15:33
lsmola_jd__, yeah agree, it should be matter of configuration of agent15:33
eglynnso wouldn't we have to restart the agent everytime a new baremetal hosts appears?15:33
lsmola_eglynn, yeah :-D15:34
eglynn(i.e. to force a re-read of the pipeline.yaml)15:34
dhellmanndidn't the ironic guys say they wanted to be the only thing talking ipmi, since there are security risks with spreading those credentials around?15:34
eglynndhellmann: yep, that rings a bell15:34
llu-laptop|2sorry guys, I'm having internet jag here. maybe slow in response15:34
lsmola_dhellmann, exactly15:34
dhellmannso maybe we just need to talk to the ironic service to get the data we want?15:34
dhellmannsorry, I'm catching up on this issue, so I apologize if I'm restating the obvious15:34
*** ygbo has quit IRC15:35
lsmola_dhellmann, well i am not sure about the connection, all I heard is that the Agnet will be part of Ironic (or running next to) so it can access ironic15:35
eglynnso I think the concern was not to limit to ironic only, or?15:35
jd__no, the Ironic guy points is that *if* ironic is used, Ceilometer should ask Ironic, and not talk SNMP/IPMI directly and ask for the credentials Ironic knows15:35
jd__but please, don't mix the "I use Ironic" and "I don't use Ironic" use-cases15:35
lsmola_dhellmann, from what I know, originally Ironic should expose the data via API15:35
dhellmannok, well, talking to ironic seems like a good starting place at least15:36
lsmola_dhellmann, but it's not the case anymore15:36
dhellmannoh, when did that change?15:36
llu-laptop|2lsmola_: what's the case now?15:36
*** Shaan7 has joined #openstack-meeting15:36
lsmola_dhellmann, apparently on the conference :-)15:36
lsmola_well ndipanov told me that they don't want it, they rahter want to run an agent somewhere next to Ironic15:37
lsmola_I am not sure what exact architecture it should be15:37
dhellmannare they expecting us to write that agent, or is it just something different from their current agent that they are going to write?15:37
eglynnlsmola_: run an agent next to the ironic conductor that depends on an API exposed by ironic, right?15:38
jd__eglynn: I think so15:38
lsmola_dhellmann, hmm not sure, I have to ask ndipanov again15:38
jd__but really, this topic is not about Ironic15:38
lsmola_dhellmann, because it seemed to me like the Ironic IPMI API idea died15:39
*** pablosan has joined #openstack-meeting15:39
lsmola_jd__, ok so lets talk about what we want to support15:39
*** wolsen has joined #openstack-meeting15:39
jd__can I say "no"? :)15:40
dhellmannlsmola_: we don't need an IPMI API, we need a monitoring API15:40
lsmola_jd__, for me minimum seems, defining it by hard, + option to allow agent to get the IP's and IPMI credentials from Nova and Ironic15:40
*** nsaje has joined #openstack-meeting15:40
*** kevinconway has joined #openstack-meeting15:40
lsmola_dhellmann, yeah I just named it badly15:40
jd__lsmola_: agreed, but I don't think that was llu's questions initially15:41
dhellmannlsmola_: ok, just making sure we're clear :-)15:41
eglynnif relying on defining by hand, then in the least case we need some way of avoiding the agent restart on pipeline.yaml change15:41
*** jtomasek has joined #openstack-meeting15:41
eglynn(e.g. detecting a change in the file timestamp and re-reading in that case)15:41
jd__eglynn: we have a reload system via SIGHUP15:41
llu-laptop|2do we want the restart or avoid the restart?15:42
lsmola_eglynn, yeah that makes sense15:42
jd__llu-laptop|2: avoid15:42
llu-laptop|2SIGHUP I think is the restart system15:42
eglynnjd__: send a SIGHUP to the process and that forces a re-read?15:42
jd__eglynn: IIRC yes15:42
eglynnjd__: k, I wasn't familiar with that15:42
dhellmanneglynn: what if we put that info in a different file from the pipeline, and just read that file in the pollster(s) (with caching)15:43
lsmola_jd__, also we will want to get list of switches and routers from Neutron later15:43
jd__sure15:43
eglynndhellmann: yep, that would be neater15:43
jd__I'm restating that this is not the subjet of llu intervention here15:43
*** nsaje has quit IRC15:43
llu-laptop|2jd__: I think our current SIGHUP implementation is to automatically restart the service, so new pipeline definition applies15:44
*** nsaje has joined #openstack-meeting15:44
jd__llu-laptop|2: don't have details in mind, that may be :)15:44
*** dcramer_ has joined #openstack-meeting15:44
llu-laptop|2Fengqian did this in Havana cycle. I'll ping him to double check15:44
llu-laptop|2tomorrow15:45
jd__is there any more question than you need an answer llu or can I move on to the next topic?15:45
llu-laptop|2please move on, thanks15:45
jd__#topic integration tests discussion15:45
*** openstack changes topic to "integration tests discussion (Meeting topic: ceilometer)"15:45
jd__nadya_: floor is yours15:45
nadya_yep, thanks15:45
nadya_so the first item is resolved. As I see all crd were restored and is being reviewed now15:46
lsmola_llu-laptop|2, would be great if you could ping ndipanov and devananda15:46
nadya_JFYI I will care about https://review.openstack.org/#/c/5527615:46
lsmola_llu-laptop|2, to make sure if we are thinking about it correctly :-)15:47
*** jmontemayor has joined #openstack-meeting15:47
eglynnmight be useful to do a show of hands as to who is interested in beefing up ceilo coverage in tempest?15:47
eglynnthen maybe do a rough division of functional areas to concentrate on?15:47
nadya_I guess we've covered all tempest crs15:47
eglynn(to avoid possible duplication)15:47
jd__I think yassine is15:47
eglynno/ ... I am also15:48
yassineo/15:48
nadya_me too o/15:48
zhikunliume too15:48
litong@eglynn, certainly, yes.15:48
jd__using the blueprint whiteboard or todo list to state what people are working on could be a good idea15:48
jd__#link https://blueprints.launchpad.net/tempest/+spec/add-basic-ceilometer-tests15:49
eglynnjd__: yep, good call15:49
*** SergeyLukjanov has quit IRC15:49
eglynnwill one blueprint suffice?15:49
eglynnthat one is skewed a bit towards the more basic functionality15:50
jd__I've no opinion, but it's possible to create sub-blueprints with dependencies15:50
eglynnalso doesn't tempest use its own client layer? (not sure that fits with "CLI basic functionalities")15:50
nadya_agreed. So will we determine any period of time within which test plan should be completed?15:50
eglynnnadya_: let's aim for early next week15:51
eglynnsay Monday?15:51
nadya_ok15:51
*** Manur has quit IRC15:52
*** otherwiseguy has joined #openstack-meeting15:52
nadya_should we write in email?? Or let's refuse amount of letters? :)15:52
nadya_*reduce15:52
eglynnnadya_: an etherpad is probably better suited to getting multiple contributions lined up15:53
zhikunliuhttps://etherpad.openstack.org/p/ceilometer-test-plan15:53
eglynn(i.e. better than an email thread)15:53
eglynnzhikunliu: thanks!15:53
*** sgran has left #openstack-meeting15:53
nadya_oh, I saw this doc, yes15:53
*** eharney has joined #openstack-meeting15:54
*** armax has joined #openstack-meeting15:54
*** avishayb has joined #openstack-meeting15:54
nadya_ok. So Monday is the day when we have test-plan for Ceilometer+Tempest15:54
lsmola_have to run, see you all next week, we have angularjs beer meeting :-D15:54
*** rongze has quit IRC15:54
zhikunliu:)15:55
*** evgenyf has joined #openstack-meeting15:55
nadya_and one more question from me about devstack+ceilometer. Who is an expert in this area? We started to look into devstack issues15:55
jun:)15:55
jd__I think sileht knows a lot15:55
jd__though feel free to ask to everybody on #openstack-metering15:55
*** julim has quit IRC15:55
eglynnnadya_: yep re. the test plan ... I'll start by setting out the areas that I intended to concentrate on, and also some general thoughts on the approach15:55
*** jmontemayor_ has joined #openstack-meeting15:56
eglynnthe devstack+ceilometer issue is the sqlalchemy connection pooling thingy, right?15:56
terriyunadya_: I complain a lot about devstack+ceilometer -- i.e. report bugs15:56
silehtnadya_, I have made the lists of the pendings review to have a working devstack in gate in the bp15:56
*** jtomasek has quit IRC15:56
nadya_eglynn, sure. I'm planning to work on test-plan tomorrow too15:57
eglynnnadya_: cool15:57
*** julim has joined #openstack-meeting15:57
nadya_terriyu, sileht, great, will keep in touch15:57
*** jmontemayor has quit IRC15:57
jd__PA: meeting is ending on a few minutes15:57
nadya_I think we can move on to general discussions15:58
jd__#topic Open discussion15:58
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:58
nadya_jd__, when bps from design sessions should be finished?15:59
*** nsaje has quit IRC15:59
jd__nadya_: as soon as possible, especially ones targetting icehouse-115:59
*** kevinconway has quit IRC16:00
eglynnlet's try to get blueprints filed by next week's meeting if poss16:00
eglynn(while the summit is still fresh in the mind ...)16:00
jd__good idea16:00
*** tanisdl has joined #openstack-meeting16:00
*** pdmars has quit IRC16:00
litongI always wonder which db ceilometer wants to use as the first option.16:00
eglynnso icehouse-1 is due when, Dec 4th?16:00
ildikovIs there a schedule available for icehouse?16:00
*** s3wong has quit IRC16:00
dhellmann#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule16:00
dhellmannthat's not final yet16:01
litongdevstack config for ceilometer shifts from mongodb to mysql.16:01
*** nealph has joined #openstack-meeting16:01
ildikovThanks16:01
jd__eglynn: yess16:01
*** pdmars has joined #openstack-meeting16:01
jd__#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule16:01
eglynncool, we get "Off" weeks this time :)16:02
litonganyone know why devstack setup for ceilometer uses mysql now vs using mongodb before?16:02
jd__I'm closing the meeting as we already late, please follow up in #openstack-metering as needed16:02
eglynnlitong: issue with mongodb 2.4 on precise16:02
jd__litong: discussed during the summit btw16:02
jd__#endmeeting16:02
eglynnlitong: (only available in the ubuntu cloud archive)16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
openstackMeeting ended Thu Nov 14 16:02:47 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-11-14-15.00.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-11-14-15.00.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-11-14-15.00.log.html16:02
jd__thanks everybody!16:03
*** manish_ has quit IRC16:03
thomasemcheerio!16:03
eglynnthanks all!16:03
*** Mandell has joined #openstack-meeting16:03
terriyuthanks everyone16:03
*** gordc has left #openstack-meeting16:05
*** herndon has joined #openstack-meeting16:05
*** kevinconway has joined #openstack-meeting16:06
*** pdmars has quit IRC16:06
*** tims has left #openstack-meeting16:08
*** belmoreira has quit IRC16:08
*** rnirmal has joined #openstack-meeting16:08
*** pdmars has joined #openstack-meeting16:08
*** belmoreira has joined #openstack-meeting16:08
*** afazekas has quit IRC16:09
*** llu-laptop|2 has quit IRC16:09
*** pdmars has quit IRC16:09
*** pdmars has joined #openstack-meeting16:10
*** belmoreira1 has joined #openstack-meeting16:10
*** belmoreira has quit IRC16:10
*** belmoreira1 has quit IRC16:11
*** dkranz has quit IRC16:11
*** belmoreira has joined #openstack-meeting16:11
*** shadower_ is now known as shadower16:13
*** avishayb has quit IRC16:14
*** belmoreira has quit IRC16:16
*** rbowen has quit IRC16:18
*** bdpayne has joined #openstack-meeting16:19
*** markmcclain has quit IRC16:19
*** nadya_ has quit IRC16:21
*** jun has quit IRC16:22
*** jlibosva has quit IRC16:25
*** jmontemayor_ has quit IRC16:25
*** rongze has joined #openstack-meeting16:25
*** oubiwann has joined #openstack-meeting16:26
*** dkranz has joined #openstack-meeting16:27
*** stevemar has joined #openstack-meeting16:28
*** dolphm_ is now known as dolphm16:28
*** jmontemayor has joined #openstack-meeting16:28
*** haypo has joined #openstack-meeting16:29
haypo"Python3 Compatibility Team meeting: Bi-Weekly (every other week) meetings on Thursdays at 1600 UTC" does anyone know when is the next meeting and if there are logs of previous meetings?16:29
haypoi'm interested to work on Python3 :)16:30
*** mjbright_ has quit IRC16:30
*** vijendar has quit IRC16:31
*** evgenyf has quit IRC16:32
*** akuznetsov has quit IRC16:34
*** branen has joined #openstack-meeting16:34
*** zhikunliu has quit IRC16:35
*** yaguang has quit IRC16:36
*** zbitter has joined #openstack-meeting16:40
*** mrodden has joined #openstack-meeting16:41
*** dkranz has quit IRC16:42
*** yassine has quit IRC16:43
*** afazekas has joined #openstack-meeting16:43
*** zaneb has quit IRC16:43
*** ruhe has quit IRC16:45
*** vijendar has joined #openstack-meeting16:48
*** kgriffs_afk is now known as kgriffs16:50
*** edmund has joined #openstack-meeting16:52
*** doron is now known as doron_afk16:52
*** vito-ordaz has joined #openstack-meeting16:52
*** zbitter is now known as zaneb16:52
*** suo has quit IRC16:53
*** doron_afk has quit IRC16:54
*** suo has joined #openstack-meeting16:54
*** MarkAtwood has joined #openstack-meeting16:55
*** garyk1 has quit IRC16:55
*** dkranz has joined #openstack-meeting16:55
*** nealph has left #openstack-meeting16:57
*** johnthetubaguy has quit IRC16:58
sdaguewho's arround17:00
mkodererhey there17:00
*** HenryG has quit IRC17:01
sdaguedkranz you about?17:01
dkranzHere17:01
mkodererhe there I spoke to him17:01
mkoderer:)17:01
sdaguecool, let's start the meeting17:01
sdague#startmeeting qa17:02
openstackMeeting started Thu Nov 14 17:02:03 2013 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: qa)"17:02
openstackThe meeting name has been set to 'qa'17:02
sdague#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_November_14_201317:02
*** terriyu has quit IRC17:02
sdaguequick roll call of who's here via: o/17:02
sdague(meetbot actually records that)17:02
dkranzo/17:03
mkoderero/17:03
sdagueafazekas: ?17:03
sdagueI know mtreinish is popping around in .jp this week on vacation17:03
*** Mandell has quit IRC17:03
sdague#topic Possible Meeting Time change to include .jp (sdague)17:03
*** openstack changes topic to "Possible Meeting Time change to include .jp (sdague) (Meeting topic: qa)"17:03
sdagueok, so this is something I know we talked a bit about at the summit17:04
mkoderer+1 for that17:04
*** IlyaE has quit IRC17:04
mkodererI think we should ask giulivo17:04
sdagueagreed17:04
*** rudrarugge has joined #openstack-meeting17:04
sdague just pinged him to jump in channel17:04
*** giulivo has joined #openstack-meeting17:04
sdagueI expect the tz shift might have made people forgetful :)17:05
dkranzmorning in us is the only time that works for us/europe/jp17:05
sdaguehey giulivo17:05
sdaguedkranz: well, the .jp folks said they could do 6am - 9pm their time17:05
*** NikitaKonovalov has joined #openstack-meeting17:05
mkodererso which timeframe are we talking about17:05
mkodererok17:05
sdagueso what I was actually thinking might be best is to do the oscilating meeting17:06
mkodererit's UTC+09:0017:06
sdaguehttps://wiki.openstack.org/wiki/Meetings#Metering_team_meeting17:06
sdagueis how Ceilometer does it17:07
sdagueso I was thinking maybe do those same time blocks that they use, but on the alternate weeks17:07
*** ildikov has quit IRC17:07
*** jasondotstar has quit IRC17:07
*** haypo has left #openstack-meeting17:07
sdaguewhich would make every other week work for .jp17:07
sdagueand not make the .eu people stay up super late all the time, just on some weeks (if they can make it)17:08
sdagueand as long as we take votes to the ML, instead of in IRC, it would be inclusive17:08
dkranzSo for us east that would be 10am and 4pm, plus one hour when DST?17:08
mkodererI am fine with that17:08
*** rudrarug_ has joined #openstack-meeting17:08
sdaguedkranz: yes17:08
sdaguegiulivo: you have an opinion here?17:09
dkranzSo the europe night owls could do both :)17:09
sdagueyes, exactly17:09
*** rudrarugge has quit IRC17:09
sdagueit feels like it would be a more global friendly way of handling it, and let us bring on more folks from around the globa17:09
sdagueglobe17:09
giulivowell I'm a bit worried oscilating meetings17:09
dkranzsdague: Works for me17:10
giulivocould be forgiven17:10
sdaguegiulivo: ok, please share the concerns17:10
dkranzgiulivo: I think oscilating is ok as long as it is easy to remember17:10
sdaguethat's why I brought it up for discussion17:10
*** vkmc has quit IRC17:10
*** suo has quit IRC17:10
dkranzsdague: I presume the ceil thing means "date is odd" or "date is even"17:10
giulivowhat would be an alternative timeframe anyway?17:10
sdaguedoes everyone use google calendar? I could make sure that we have an updated calendar entry17:11
sdaguedkranz: no it's on ISO-week % 217:11
dkranzsdague: urck17:11
mkodererso if we take 6am jp time this will be 11pm euope time right?17:11
sdaguemkoderer: yes17:11
sdagueso the other alternative is to fix to that schedule I think17:11
giulivoauch, that probably won't work for jp anyway17:11
sdaguebecause I really do want to be inclusion of the .jp team17:11
sdaguegiulivo: they said they could do 6am17:12
sdaguebut that's the earliest they could do17:12
giulivoI could manage to do it later actually17:12
sdaguewhich we could do, but that will force the .eu folks to be up all the time.17:12
dkranzUnderstandable :)17:12
mkodererI am for oscilating it17:12
giulivoafazekas, ?17:13
sdaguegiulivo: yeh, I pinged afazekas earlier, did get a response, not sure if he's on right now17:13
sdagueif the concern is forgetting the meeting, is that addressable via a google cal + a reminder?17:14
*** rakhmerov has quit IRC17:14
*** luis__ has joined #openstack-meeting17:14
sdagueok, so because we're a little low on quorum, how about we agree to take to the list, to get other feedback from folks17:14
mkoderergiulivo: what is your concern with oscilating the meetings?17:14
giulivosdague, well it's about organizing things around it to avoid conflict17:14
giulivobut it's three of you voting for oscilating so, np with that17:15
mkoderersdague: yes let's take it to the ML and we vote there17:15
sdaguegiulivo: well, we should at least make sure either of those schedules do actually work for the .jp team :) so I'll take to the list anyway17:15
dkranzsdague: Sounds good.17:15
sdague#action sdague to take schedule change proposals to the list for -qa meeting17:15
sdague#topic Blueprints17:16
*** openstack changes topic to "Blueprints (Meeting topic: qa)"17:16
sdagueok, first off, I haven't started digesting blueprints yet out of our sessions17:16
*** rbowen has joined #openstack-meeting17:16
sdagueI was talking with russellb this morning, and this afternoon I'm going to work on a purge script to drop the old bp so we don't have untargetted crud in our tracker17:17
*** alexpilotti has quit IRC17:17
mkoderersdague: I already added the negative test bp17:17
*** chandankumar has quit IRC17:17
*** ildikov has joined #openstack-meeting17:17
sdaguemkoderer: awesome17:17
*** dolphm has quit IRC17:18
sdagueyeh, any help in creating blueprints out of the etherpads would be awesome17:18
sdagueeven for areas that you aren't the one directly working on17:18
sdaguenext week I'm largely out of commission, so I won't be able to do it until the week after17:18
dkranzsdague: Is this the slot to discuss how we coordinate new scenario tests?17:18
sdaguedkranz: just about17:18
sdagueor... actually mkoderer put the negative testing one in here17:19
sdaguemkoderer: was there something specific on that?17:19
dkranzsdague: Just an update I think17:19
mkoderersdague: yep just a update17:19
sdagueok, mkoderer fire away17:19
*** alexpilotti has joined #openstack-meeting17:19
mkodererdkranz and I started with some design sessions17:20
mkoderer#link https://etherpad.openstack.org/p/bp_negative_tests17:20
mkodererwe agreed to start on a prototype implementation which will be available next week hopefully :)17:21
*** NikitaKonovalov has quit IRC17:21
sdaguenice, that looks really cool17:21
sdaguethat would be awesome17:21
sdagueyou guys rock17:21
*** rakhmerov has joined #openstack-meeting17:21
dkranzsdague: Marc is going to put some prototype code17:21
sdagueI like the declaritive language for it17:21
dkranzsdague: And I am going to make sure the other apis don't have complexity that is missing from this mode.17:21
mkoderersdague: I think we could also produce positive tests with it17:21
dkranzsdague:   ^^ model17:21
*** jasondotstar has joined #openstack-meeting17:22
*** NikitaKonovalov has joined #openstack-meeting17:22
sdagueI think my only suggestion is whether we could declare relative to the REST end point, instead of our internal code17:22
dkranzsdague: We discussed exactly that issue17:22
sdagueeven if that required another mapping layer from rest end point to internal client / library17:22
sdaguebecause it would be easier to onboard folks then17:22
dkranzsdague: I was intially inclined toward rest but there are two issues17:23
sdagueand know relative to the API how we were doing17:23
dkranzsdague: 1. The way it is now covers json and xml17:23
dkranz2. The way it is now avoids the problem that in the http, some arguments are embedded in the url and some in a json dict17:23
*** jasondotstar has quit IRC17:23
*** jasondotstar has joined #openstack-meeting17:24
mkodererbut the drawback is that json schemas are more problematic to link17:24
dkranzShould get some more thought perhaps17:24
sdaguedkranz: sure, it just means there is a lot of tempest specific context in the definition. It would be nice to hide that if possible17:24
*** hub_cap_ is now known as hub_cap17:24
*** gkleiman has joined #openstack-meeting17:24
sdagueanyway, just a thought, I don't want it to derail the great work here17:24
dkranzsdague: I agree if there was a use case outside of tempest. Not sure there really is at the moment.17:24
*** kevinconway has quit IRC17:24
sdaguedkranz: honestly, I'm less concerned with the use case outside of tempest, as it meaning if we refactor tempest internals the defs break17:25
dkranzsdague: Anyway, we are talking a small prototype now17:25
sdagueyep, agreed17:25
mkodererlet's bring the prototype up and we discuss it in more detail17:25
mkodereryep :)17:25
sdagueI think that prototype will make things clearer17:25
*** pdmars has quit IRC17:25
sdaguebut nice start regardless17:25
dkranzok, I think that's it.17:26
*** dwalleck has joined #openstack-meeting17:26
mkodereryes thats it17:26
*** topol has quit IRC17:26
sdagueok, lets do the scenario planning at the end, as it's not on the agenda17:26
sdague#topic Neutron17:26
*** vito-ordaz has quit IRC17:26
*** openstack changes topic to "Neutron (Meeting topic: qa)"17:26
*** rbowen has quit IRC17:26
sdagueEmilienM said he wouldn't be able to make it, but he provided some status in -qa earlier17:27
*** DrBacchus has joined #openstack-meeting17:27
*** vito-ordaz has joined #openstack-meeting17:27
sdaguehe's got some reviews up for negative tests that salvatore thinks the neutron team needs to nail down behavior17:27
sdaguebut it's not quite ready for review yet17:27
sdagueI would just say in general, please prioritize neutron reviews17:28
mkodereryes maybe the guys making those test could directly ping in IRC if they want17:28
sdagueas that team is working really hard now to fix neutron issues, and we'd really like to be part of the solution17:28
sdaguemkoderer: yes, good point17:28
dkranzsdague: +117:28
mkodererso I will directly have a lool17:28
mkoderers/lool/look/17:29
sdague#info please prioritize neutron reviews to help close neutron qa gaps17:29
sdaguealso, there will be a code sprint in Montreal in Jan17:29
*** rudrarug_ is now known as rudrarugge17:29
sdaguethe details are starting to show up on the ML17:29
*** kgriffs is now known as kgriffs_afk17:29
sdaguethe intent being a neutron / qa push to close remaining gaps before icehouse-217:29
*** danwent has joined #openstack-meeting17:29
*** dolphm has joined #openstack-meeting17:29
sdagueso if anyone wants to participate, just keep an eye on it on the ML17:29
anteayamkoderer: I will send them over17:29
sdagueanteaya: thanks17:30
dkranzsdague: I saw that. Hoefully there is a way for those not in Montreal to join, at least for part of it.17:30
mkodereranteaya: great17:30
anteayadkranz: can you attend?17:30
sdaguedkranz: it's going to be a code sprint, so joining will probably just mean staying active on IRC17:30
anteayawould love to have lots of qa there17:30
sdaguedkranz: it's only a 5 hr drive for you, right? :)17:30
dkranzsdague: Right17:30
anteayaso come17:30
anteayaemail me your email address17:30
dkranzsdague: If the roads are clear17:30
sdaguemontreal was chosen for proximity reasons to mtreinish and I17:30
anteayaanteaya at anteaya dot info17:31
sdaguedkranz: that's why I have a subaru17:31
dkranzsdague: :)17:31
anteayadkranz can you take the train?17:31
dkranzanteaya: No17:31
anteaya:(17:31
dkranzTHere is none17:31
sdaguethe train lines around here to montreal are pretty odd and slow17:31
*** vito-ordaz has quit IRC17:31
dkranzanteaya: I'm not sure if I can make it or not.17:32
*** garyk has joined #openstack-meeting17:32
anteayafair enough, please email me anyway17:32
* sdague grew up in vermont, understand the weird trains pretty well17:32
anteayathen we can firm up later17:32
sdagueok, I think we can move on to next topic17:32
sdague#topic How should we sync the teams (neutron/scenario test)? One BP with work items, bugs or ML? (mkoderer)17:32
*** openstack changes topic to "How should we sync the teams (neutron/scenario test)? One BP with work items, bugs or ML? (mkoderer) (Meeting topic: qa)"17:32
sdaguemkoderer: you are up17:32
mkodererso I just added this topic since I saw the discussion about syncing all the teams17:33
mkodererso EmilienM  asked about neutron testing and on the ML was about scenario testing17:33
*** luis__ has quit IRC17:34
*** jlibosva has joined #openstack-meeting17:34
mkodererI have the feeling nobody want to track it in launchpad17:34
sdagueyeh, I think we're going to need to limp through with various ad-hoc things in this cycle until we get enough of storyboard working to run with it17:34
dkranzmkoderer: Is this the same issue I sent to the ml yesterday, about tracking scenario work in general?17:34
sdagueso at this point, I'm completely happy with various groups picking whatever works for them to be productive17:35
mkodererdkranz: yes, there was the very same discussion with neutron testing17:35
sdagueif that's a google doc, cool. etherpad, cool. wiki, cool.17:35
dkranzI didn't see the message from EmilienM17:35
sdagueI think we should have 1 high level blue print for each of these efforts, just so we can keep an overall eye on progress17:36
mkodererdkranz: it was on irc about how we want to sync the effort in neutron17:36
dkranzmkoderer: o17:36
giulivosdague, that means you won't use gerrit and text files for that though, correct?17:36
sdaguebut the details should be wherever the people doing the work want to17:36
sdaguegiulivo: that's an option too17:36
sdaguebut again, I feel like we don't have an efficient standard way to manage the details, so I don't want to impose one on people17:36
dkranzsdague: Right17:37
mkoderersdague: ok so if I have time  I will open up these bp's tomorrow17:37
sdagueI'm completely ok with a blueprint with a description, and a link to however the group is managing the details17:37
dkranzsdague: How about either doing what we talked about yesterday using gerrit, or a blueprint named "Scenario:  ..."17:37
*** bknudson has joined #openstack-meeting17:37
sdaguedkranz: are you talking about 1 blueprint per scenario?17:38
sdaguebecause I think that will be too heavy17:38
dkranzsdague: Yes.17:38
dkranzsdague: That's why I suggested the gerrit thing.17:38
dkranzsdague: I was just agreeing we should not impose it.17:38
mkoderermhh I think it should be one bp with different work items17:38
sdaguedkranz: ok, I think we are on the same page17:38
giulivoI'm with dkranz on the gerrit idea, scenarios usually have good descriptions so that should be the first "patchset": a description of the scenario test17:39
dkranzmkoderer: We are talking about all scenarios. Many are not specific to a project.17:39
sdaguejust to be clear, we really do need a blueprint for each high level thing. Like "Scenario Test Additions in Icehouse"17:39
dkranzsdague: That's fine.17:39
sdaguebut the details really can be elsewhere17:39
sdaguemkoderer: right, the problem is the only way to do work items in blueprints is the whiteboard, which is pretty wonky17:40
mkoderersdague: I know :|17:40
*** jmontemayor has quit IRC17:40
dkranzsdague: I was more concerned with avoiding dup and allowing for comments17:40
giulivodkranz, +117:40
dkranzBut a master blueprint should be fine17:40
dkranzAnd completed scenarios can be added so we have a list17:40
sdaguedkranz: right, so if the top level blueprint takes you to an etherpad or file in gerrit, or however the team wants to manage that, it should funnel everyone there17:40
dkranzsdague: Right17:41
sdagueso a unified entry point to get folks to the right detailed discussion17:41
dkranzYes17:41
mkodererthat's sounds like a plan17:41
sdagueand then agressively go close new blueprints that pop up that look like dups, and drive those folks in through the master blueprint17:41
giulivo1217:42
sdaguepolicing that second bit is going to be important to make sure we don't fragment17:42
dkranz+117:42
mkoderer+117:42
sdaguecool17:42
giulivoactually I don't have credentials in launchpad for that17:42
*** jasondotstar has quit IRC17:42
sdaguegiulivo: ok, lets fix that after the meeting17:42
sdagueeveryone with +2 should have that, but it's not automatic17:43
mkodererok don't know if I have these permissions17:43
sdaguefwiw, the new thinking on storyboard that mordred and I are pushing is make storyboard a rest api first17:43
sdaguewith sample scripts to manipulate it17:43
sdagueand let people build UIs later17:44
sdaguewhich I think would work really well in our workflow17:44
sdagueand ensure we can write lots of scripts to support the workflows we need17:44
sdagueok, next topic17:44
sdague#topic Onboarding documentation - where should we put it? (mkoderer)17:44
*** openstack changes topic to "Onboarding documentation - where should we put it? (mkoderer) (Meeting topic: qa)"17:44
sdaguemkoderer: you up again :)17:45
*** ildikov has quit IRC17:45
mkodererI got these action item from the summit17:45
mkodererany ideas where this document should be stored?17:45
mkodererwiki?17:45
sdaguemkoderer: actually, I'd suggest putting it in tree17:45
giulivoyeah in tree17:45
sdaguedoc/source17:45
dkranzsdague: +117:45
*** rongze has quit IRC17:45
mkoderersdague: ok cool17:45
sdaguepublishes to http://docs.openstack.org/developer/tempest/ on merge17:46
mkoderergreat I will have a look17:46
*** rongze has joined #openstack-meeting17:46
sdagueawesome17:46
mkodererif I find some time I will push it17:46
mkoderer:)17:46
sdaguenice :)17:46
sdague+1 to more docs17:46
mkodererthats all17:46
giulivosorry guys, how is the onboarding different from the README?17:47
sdagueI was actually thinking that maybe we need a REVIEWING.rst as well, which I might bang out a proposed version on the airplane some time next week17:47
sdaguejust to make sure we write down all our assumptions about reviewing, and that we are on the same page17:47
sdaguegiulivo: I think it's more extensive than what's there17:48
sdagueREADME is mostly a quickstart kind of approach17:48
*** comay has joined #openstack-meeting17:48
*** reed has joined #openstack-meeting17:48
sdaguebut with the docs tree we can have more complicated chapter model to target different audiences17:48
sdaguewhich is good17:48
mkodereryes it will have a lot of details that arent needed in readme17:48
sdaguethere is plenty of confusion, and writing things down will help17:48
*** SergeyLukjanov has joined #openstack-meeting17:48
sdaguemkoderer: thanks again for championing this17:48
sdagueok, last topic17:49
mkodererI am quite sure it will cause a lot of discussions17:49
mkodereryep17:49
sdaguemkoderer: yep, and it will be great :)17:49
sdague#topic Critical Reviews (sdague)17:49
EmilienMmkoderer: o/17:49
*** openstack changes topic to "Critical Reviews (sdague) (Meeting topic: qa)"17:49
mkoderershould we quickly talk again about neutron testing?17:50
sdaguemkoderer: we can take that to -qa I think17:50
mkoderersure17:50
*** rongze has quit IRC17:51
sdagueanyone have some reviews they need eyes on that are falling behind?17:51
sdaguein general I'd like to see the Nova v3 reviews make more progress, though it looks Ken'ichi has been all over those over night17:51
sdaguewhich is awesome17:51
mkodererI have a trouble with a review17:51
mkoderer#link https://review.openstack.org/#/c/51122/17:51
mkodererseems that it's a problem due to py2.717:52
sdagueok, is it debug issue?17:52
sdagueok, that's something we should try to sort out17:52
mkodererafazekas told me that I should skip one test for py2.717:52
mkodererI need to have a closer look17:52
sdagueI'd rather not skip 2.717:53
*** joel-coffman has joined #openstack-meeting17:53
sdaguethat seems like the wrong approach17:53
mkoderersdague: I know ;)17:53
sdagueso let's try to get to the bottom of the issue17:53
sdagueafter lunch I'll try to help loook17:53
mordredsdague: what did I do?17:53
*** harlowja has joined #openstack-meeting17:53
mordredah. nm17:53
* mordred read scrollback17:53
sdagueok, any other critical reviews?17:53
sdague#topic Open Discussion17:54
dkranzsdague: There actually aren't any that are old.17:54
*** openstack changes topic to "Open Discussion (Meeting topic: qa)"17:54
giulivoan on-the-fly topic17:54
dkranzsdague: But the queue is still pretty long17:54
dkranzgiulivo: Go ahead17:54
giulivoI noticed the ironic tests addition17:54
*** ravikumar_hp has joined #openstack-meeting17:54
sdaguedkranz: yeh, the queue is long, I was going after it oldest to newest, but I think a lot was lag leading up to summit17:55
sdaguegiulivo: go for it17:55
giulivobut that doesn't seem easy to gate, anyone looking into that?17:55
*** jasondotstar has joined #openstack-meeting17:55
sdaguegiulivo: they have a virtual bare metal setup ... which I thought landed in devstack17:55
sdaguemaybe not yet17:55
sdaguethey will also be doing real baremetal on some tripleo clouds, and report as 3rd party testing17:56
dkranzThe last comment says there are patches after which this can run17:56
*** changbl has quit IRC17:56
*** nkinder_ has joined #openstack-meeting17:56
sdagueso once they get that, we could use the 3rd party testing results to help us know the code runs as well17:56
giulivoneed to learn what that 3rd party directory is :)17:57
*** vito-ordaz has joined #openstack-meeting17:57
sdaguegiulivo: so our 3rdparty directory is for 3rdparty APIs17:57
dkranzsdague: mtreinish pushed the config sample file change which will cause more pain. It is blocked on rebase.17:57
sdaguebut this is going to be like SmokeStack17:57
*** vipul is now known as vipul-away17:57
dkranzsdague: Are you able to push it?17:57
sdaguedkranz: I can rebase it17:57
*** epim has joined #openstack-meeting17:57
* sdague adds to afternoon queue17:58
dkranzsdague: How do you do that?17:58
sdaguegit review -d #####17:58
*** kgriffs_afk is now known as kgriffs17:58
sdaguethen rebase on master17:58
sdaguethen repush17:58
dkranzsdague: Oh, I thought you had a way without "taking" it17:58
dkranzsdague: That's fine17:58
sdagueit only changes the committer, he'll still get author for it17:58
*** rnirmal has quit IRC17:58
*** derekh has quit IRC17:59
dkranzsdague: Got it. We should do that more often.17:59
sdagueyeh, typically I only do that if I know the person is going to be away for a week17:59
sdaguebecause I really want folks to come back around and pay attension to their patches17:59
sdagueand when people don't, I use it as a signal to not prioritize reviewing their code18:00
sdaguebecause they aren't attentive18:00
sdagueok, I think we're at the end of time18:00
sdagueso thanks for coming, see you on -qa18:00
*** mlavalle has joined #openstack-meeting18:00
sdague#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Nov 14 18:00:45 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-11-14-17.02.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-11-14-17.02.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-11-14-17.02.log.html18:00
dkranzsdague: Yes, it would be great if the gerrit ui could encourage review efficiency instead of the opposite.18:00
*** markmcclain has joined #openstack-meeting18:00
*** mylestro has joined #openstack-meeting18:01
*** eglynn has quit IRC18:01
*** giulivo has left #openstack-meeting18:02
dwalleckmlavalle: I think we failed at time zones18:02
mlavalledwalleck: yes we did18:03
*** shohel_ has joined #openstack-meeting18:03
*** andreaf has joined #openstack-meeting18:04
*** akuznetsov has joined #openstack-meeting18:04
*** krtaylor has quit IRC18:04
shohel_Hi, is there anyone from OpenStack Security Group18:04
joel-coffmanme18:05
*** b3nt_pin has joined #openstack-meeting18:05
*** beagles has quit IRC18:05
nkinder_It's the right meeting time for OSSG, isn't it?18:05
*** gyee has joined #openstack-meeting18:05
*** dwalleck has quit IRC18:05
joel-coffmanyes18:05
*** b3nt_pin is now known as beagles18:05
shohel_It should be18:06
bdpayne#startmeeting OpenStack Security Group18:06
openstackMeeting started Thu Nov 14 18:06:57 2013 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:06
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:07
openstackThe meeting name has been set to 'openstack_security_group'18:07
bdpaynehi everyone18:07
joel-coffmanhey18:07
shohel_hi18:07
nkinder_hello18:07
bdpaynesorry about the delay... I hadn't updated my calendar for US daylight savings time18:07
bdpayneheh18:07
bdpayneok, so let's get right into it18:07
*** dims has quit IRC18:07
bdpaynefirst I'd like to do a quick brain dump on the summit18:08
bdpayneand some of the next steps18:08
bdpaynefeel free to chime in with additional details and/or to add things that I miss18:08
bdpayneafter that, I believe shohel_ wanted to talk a bit about threat modeling18:08
bdpayne#topic Summit Wrapup18:09
*** openstack changes topic to "Summit Wrapup (Meeting topic: OpenStack Security Group)"18:09
bdpayneSo, the summit was busy and a lot of fun, as usual18:09
bdpayneFrom an OSSG perspective, I have started to push my agenda for Icehouse: Scaling out OSSG18:09
*** bill_az has quit IRC18:09
*** beagles has quit IRC18:09
bdpaynein particular, I'll be working to get more participation and to spread some of the leadership load18:09
bdpayneand that should free me up to contribute in other ways a bit too18:10
bdpaynemore tactically, here's some of the areas the group discussed working on18:10
bdpayneOSSN18:10
bdpaynethe security notes could be ramped up18:10
bdpayneperhaps up to 1 / week18:10
bdpaynebased on the email thread, I think we have some volunteers to take that on18:11
nkinder_bdpayne: I reached out to Robert to volunteer.18:11
bdpaynegreat18:11
*** matsN has joined #openstack-meeting18:11
bdpaynefor the book, I'd like to find 2-3 people that can serve as editors18:12
bdpaynethese people would drive the improvement of the content18:12
bdpayneand there was some talk of doing a 2nd edition at some point as well18:12
bdpayne(fwiw, I'll be sending out these requests for volunteers to the mailing list as well)18:12
*** jcoufal has quit IRC18:12
bdpaynefor the volume encryption work... I just wanted to give a shout out to joel-coffman and the APL crew for a job well done18:13
bdpaynenice summit talk and a nice path forward to continue working in that space18:13
joel-coffmanthanks18:13
bdpaynejoel-coffman anything you'd like to add and/or are there ways that others can help you out / get involved there?18:13
joel-coffmanwe're continuing to move forward with our ephemeral storage encryption efforts18:13
*** blamar has joined #openstack-meeting18:14
joel-coffmancode reviews are always appreciated18:14
joel-coffman:-)18:14
bdpayneok, sounds good18:14
bdpayneand there's some barbican integration work too?18:14
joel-coffmanfeedback regarding our design, etc. is always helpful too18:15
joel-coffmanyes18:15
joel-coffmankey management is a huge issue for our work18:15
bdpayneyes, indeed18:15
bknudsonusing barbican or keystone for key management?18:15
bdpayneI believe they are moving forward with barbican18:16
joel-coffmanintegrating Barbican with our key manager interface is something that people could help with18:16
bdpaynekeystone isn't really designed for key management18:16
joel-coffmanbknudson: bdpayne: yes18:16
bdpaynejoel-coffman I may be able to help there, we should chat sometime18:16
joel-coffmanokay18:16
*** shardy is now known as shardy_afk18:16
*** rongze has joined #openstack-meeting18:17
bdpaynethreat analysis... there is a new effort here by Ericson that we'll discuss a little more in a bit18:17
bdpaynecve tracking... the group decided that there is a need to have a structured feed for the CVEs18:17
bdpayneturns out that the VMT is thinking along those lines as well18:17
bdpayneso we can collaborate with them on this18:17
bdpayneI think we do need someone from OSSG to help drive that effort18:18
joel-coffmanI think that would be helpful18:18
joel-coffmani.e., a feed for CVEs18:18
bdpaynedev sprints... we plan to do some dev sprints with a security focus for icehouse18:18
*** mlavalle has quit IRC18:18
*** ruhe has joined #openstack-meeting18:19
bdpayneEric Windisch has volunteers to organize those18:19
bdpayneI've noticed that basically all projects could benefit from more security-focused developers18:19
joel-coffmanagreed18:19
bdpayneso, that's a great place to contribute if you can... just getting your hands dirty :-)18:19
*** gatuus has quit IRC18:19
bdpaynefinally... we spoke a bit about the group's visibility18:19
*** armax has quit IRC18:20
nkinder_bdpayne: that's also an area I'm hoping to help with18:20
bdpaynesounds like many of the good things we are doing are not getting out there as much18:20
bdpaynenkinder_ with visibility or dev?18:20
nkinder_security visibility18:20
bdpayneahh, very nice18:20
bdpayneso I think it would be nice to have a community manager to drive this18:20
bdpayneperhaps nkinder_ could fill that role?18:21
nkinder_Many projects don't seem to think about security.  It seems like guidelines are needed, and lots of watching.18:21
*** coolsvap has joined #openstack-meeting18:21
nkinder_That's what I'm hoping to do.18:21
bdpaynebasically, someone to keep the rest of OpenStack abreast of what we are doing18:21
bdpayneemails to dev on a regular basis, perhasps... and perhaps getting a section in the newsletter once a month or so18:21
bdpaynethings like that18:21
bdpaynebut also to help keep OSSG up to speed as well18:22
bdpaynewe have nearly 100 people in the group18:22
*** dims has joined #openstack-meeting18:22
bdpayneand I'd like to keep people engaged and excited about the work happening here18:22
nkinder_makes sense18:22
*** NikitaKonovalov has quit IRC18:22
bdpaynenkinder_ we can talk more about this seprately too, please drop me a line18:22
nkinder_bdpayne: sure18:22
bdpayneso that's what I have from the summit18:23
bdpaynewhat can others add?18:23
bdpayneok, perhaps you guys need some coffee18:23
bdpayne:-)18:24
shohel_he he18:24
*** nsaje has joined #openstack-meeting18:24
bdpayne#topic Threat Analysis18:24
*** openstack changes topic to "Threat Analysis (Meeting topic: OpenStack Security Group)"18:24
bdpayneshohel_ please get us up to speed on your plans18:24
shohel_ok thanks,18:24
shohel_James has already discussed about the plan in the Summit18:24
*** rongze has quit IRC18:25
shohel_just to get started, a wiki has been set up18:25
shohel_so that we can all be in the same page together18:25
shohel_First thing to focus on is the process we want to follow,18:25
bdpaynewiki: https://wiki.openstack.org/wiki/Security/Threat_Analysis18:25
shohel_thanks18:25
shohel_We need to focus on a homogenous process for analysis  of all OpenStack project18:26
shohel_Here i think we can start pretty soon.18:26
bdpaynedo you have something in mind?18:26
bdpayneor is this the first step of your work?18:26
*** blamar has quit IRC18:26
shohel_There is a sketch diagram in the wiki18:26
*** pcm_ has quit IRC18:26
shohel_but need be more defined18:27
*** blamar has joined #openstack-meeting18:27
shohel_I will some more content tomorrow to make the process clear18:27
*** nsaje has quit IRC18:27
shohel_*add*18:27
bdpaynesounds good18:27
shohel_This is something also need to be discussed among OSSG community18:27
bdpayneat the summit, Rob Clark from HP suggested that he may have some thoughts on all of this18:27
bdpayneI'd encourage you to sync with him on the mailing list as well18:28
shohel_yes18:28
shohel_That i think we should do soon18:28
bdpayneshohel_ this sounds interesting and I'm looking forward to tracking the work18:28
bdpayneplease keep engaged with OSSG and let us know how the community can help support you in this effort18:28
shohel_Sriram also said he will architectural diagram activity18:28
*** b3nt_pin has joined #openstack-meeting18:28
*** nsaje has joined #openstack-meeting18:29
bdpayneoh great18:29
bdpayneis that all for now?18:29
bdpayneon threat modeling?18:29
shohel_Another important thing is team member selection and scope selection18:29
*** danwent has quit IRC18:29
shohel_we want to focus on Keystone area and proceed from there18:30
bdpayneok18:30
bdpayneso we're about out of time for today18:30
shohel_Ok18:30
bdpayneplease do keep us posted and let's bring the discussion to the mailing list18:30
shohel_I will inform more my mail18:30
*** nsaje has quit IRC18:30
joel-coffmanthanks18:30
bdpayne#topic Wrapup18:30
*** openstack changes topic to "Wrapup (Meeting topic: OpenStack Security Group)"18:30
bdpaynethanks all, I'll be following up on the mailing list to recruit more volunteers :-)18:30
bdpayneI think that's lots of good efforts coming out of the summit18:30
bdpaynehave a great week18:31
nkinder_thanks18:31
shohel_same to all18:31
*** pcm_ has joined #openstack-meeting18:31
bdpayne#endmeeting18:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:31
openstackMeeting ended Thu Nov 14 18:31:20 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-11-14-18.06.html18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-11-14-18.06.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-11-14-18.06.log.html18:31
*** bknudson has left #openstack-meeting18:31
*** lblanchard has quit IRC18:32
joel-coffman\quit18:32
*** joel-coffman has quit IRC18:32
*** shohel_ has quit IRC18:33
*** sacharya has joined #openstack-meeting18:35
*** changbl has joined #openstack-meeting18:35
*** cody-somerville has joined #openstack-meeting18:37
*** matsN has quit IRC18:39
*** krtaylor has joined #openstack-meeting18:41
*** nkinder_ has left #openstack-meeting18:41
*** docaedo has joined #openstack-meeting18:43
*** coolsvap has quit IRC18:44
*** vipul-away is now known as vipul18:46
*** DrBacchus is now known as rcb_lunch18:49
*** thelorax123 has quit IRC18:51
*** jmontemayor has joined #openstack-meeting18:53
*** pdmars has joined #openstack-meeting18:54
*** pdmars has quit IRC18:54
*** kevinconway has joined #openstack-meeting18:54
*** pdmars has joined #openstack-meeting18:54
*** HenryG has joined #openstack-meeting18:54
*** ildikov has joined #openstack-meeting18:55
*** hemna_ is now known as hemna18:56
*** IlyaE has joined #openstack-meeting18:57
*** markmcclain has quit IRC18:57
*** Mandell has joined #openstack-meeting18:58
*** markmcclain has joined #openstack-meeting18:58
*** jsavak has joined #openstack-meeting19:00
*** changbl has quit IRC19:01
*** joesavak has quit IRC19:01
*** jorisroovers has quit IRC19:01
*** joesavak has joined #openstack-meeting19:02
*** sriramhere has joined #openstack-meeting19:02
sriramherehello there, any OSSG members out here?19:03
*** jsavak has quit IRC19:04
sriramhere<bdpayne> are you there?19:07
*** twoputt has joined #openstack-meeting19:07
*** twoputt_ has joined #openstack-meeting19:07
bdpaynehi, yes... but we should chat outside of this channel.. please send me a PM19:07
bdpayne(OSSG meeting was an hour ago, time change)19:08
*** banix has left #openstack-meeting19:08
sriramhereoh no...PMing you19:09
*** jsergent has joined #openstack-meeting19:09
*** sriramhere has left #openstack-meeting19:09
*** rnirmal has joined #openstack-meeting19:09
*** eglynn has joined #openstack-meeting19:13
*** ben_duyujie has quit IRC19:13
*** kgriffs is now known as kgriffs_afk19:14
*** vito-ordaz has quit IRC19:15
*** vito-ordaz has joined #openstack-meeting19:15
*** Mandell has quit IRC19:19
*** vito-ordaz has quit IRC19:20
*** changbl has joined #openstack-meeting19:20
*** eglynn has quit IRC19:21
*** rongze has joined #openstack-meeting19:21
*** topol has joined #openstack-meeting19:24
*** garyk has quit IRC19:25
*** ruhe has quit IRC19:25
*** rongze has quit IRC19:26
*** jorisroovers has joined #openstack-meeting19:27
*** jroovers has joined #openstack-meeting19:27
*** Mandell has joined #openstack-meeting19:29
*** coolsvap has joined #openstack-meeting19:30
*** jorisroovers has quit IRC19:31
*** kgriffs_afk is now known as kgriffs19:34
*** eglynn has joined #openstack-meeting19:36
*** nermina has joined #openstack-meeting19:39
*** mjbright_ has joined #openstack-meeting19:40
*** rcb_lunch is now known as rbowen19:40
*** coolsvap has quit IRC19:42
*** epim has quit IRC19:44
*** eglynn has quit IRC19:46
*** rossella_s has quit IRC19:49
*** lblanchard has joined #openstack-meeting19:49
*** brianr is now known as rosmaita19:50
*** kgriffs is now known as kgriffs_afk19:52
*** caitlin56 has joined #openstack-meeting19:52
*** sushils has quit IRC19:53
*** vipul is now known as vipul-away19:57
*** markwash has joined #openstack-meeting19:58
*** dolphm has quit IRC19:58
*** dolphm has joined #openstack-meeting19:59
*** SergeyLukjanov is now known as _SergeyLukjanov20:02
*** _SergeyLukjanov is now known as SergeyLukjanov20:03
*** SergeyLukjanov is now known as _SergeyLukjanov20:03
*** dolphm has quit IRC20:03
*** _SergeyLukjanov is now known as SergeyLukjanov20:03
*** gyee has quit IRC20:06
*** caitlin56 has quit IRC20:06
*** epim has joined #openstack-meeting20:07
*** Linz has quit IRC20:08
*** Linz has joined #openstack-meeting20:08
*** eglynn has joined #openstack-meeting20:13
*** bgorski has quit IRC20:15
*** denis_makogon has joined #openstack-meeting20:15
*** julim has quit IRC20:17
*** thelorax123 has joined #openstack-meeting20:18
*** vipul-away is now known as vipul20:18
*** armax has joined #openstack-meeting20:20
*** vito-ordaz has joined #openstack-meeting20:20
*** kgriffs_afk is now known as kgriffs20:21
*** rongze has joined #openstack-meeting20:22
*** marun has quit IRC20:24
*** novas0x2a|laptop has joined #openstack-meeting20:25
*** rongze has quit IRC20:26
*** markmcclain has quit IRC20:27
*** esker has quit IRC20:34
*** otherwiseguy has quit IRC20:34
*** macjack has quit IRC20:40
*** sushils has joined #openstack-meeting20:43
*** nermina has quit IRC20:46
*** hartsocks has joined #openstack-meeting20:47
*** julim has joined #openstack-meeting20:48
*** alexpilotti has quit IRC20:51
*** pdmars has quit IRC20:52
*** pdmars has joined #openstack-meeting20:53
*** kevinconway has quit IRC20:53
*** MikeSpreitzer has joined #openstack-meeting20:56
*** gkleiman has quit IRC20:57
*** rfolco has quit IRC20:57
*** pdmars has quit IRC20:58
*** n0ano has joined #openstack-meeting20:59
*** rohitk has joined #openstack-meeting20:59
*** kmartin has joined #openstack-meeting21:00
*** jaybuff has joined #openstack-meeting21:00
*** mriedem has joined #openstack-meeting21:00
*** jpeeler has quit IRC21:01
*** shanewang1 has joined #openstack-meeting21:01
russellb#startmeeting nova21:01
openstackMeeting started Thu Nov 14 21:01:27 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: nova)"21:01
openstackThe meeting name has been set to 'nova'21:01
russellbhello, everyone!  who's around?21:01
*** melwitt has joined #openstack-meeting21:01
n0anoo/21:01
*** shanewang1 is now known as shane-wang21:01
MikeSpreitzero/21:01
mroddenhi21:01
mriedemhi21:01
alaskihi21:01
dansmitho/21:01
jog0o/21:01
cyeohhi21:01
melwitthi21:01
shane-wanghi21:01
rohitkhi21:01
ryanpetrellohullo21:01
russellbawesome, let's get going then21:01
russellb#topic general announcements21:02
*** openstack changes topic to "general announcements (Meeting topic: nova)"21:02
russellb#link https://wiki.openstack.org/wiki/Meetings/Nova21:02
russellbthat's our meeting page21:02
russellbi'll be keeping an agenda on there each week21:02
russellbif you have something to add, feel free to edit the page, or ping me21:02
dimso/21:02
russellbalso, if you have ideas for things that we should hit every week, let me know21:02
mikalHi21:02
russellbthe other general thing for today is making sure everyone has seen the icehouse schedule21:02
russellb#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule21:02
russellb#note icehouse-1 release is 3 weeks from today21:03
russellbthe release will fly by :)21:03
*** SergeyLukjanov has quit IRC21:03
russellbso, 66 blueprints targeted at icehouse-1, and 0 to the other milestones isn't terribly realistic, but that's another topic :)21:03
dansmithholy crap21:03
russellbdansmith: exactly21:03
*** jpeeler has joined #openstack-meeting21:03
*** jpeeler has quit IRC21:03
*** jpeeler has joined #openstack-meeting21:03
russellbso as you're planning your blueprints, please look closely at the schedule and figure out what's realistic for your work21:04
mriedemi'll go ahead and say instance type flavor dedup is probably I221:04
jog0so we have to merge 33 BPs a  week21:04
mikalrussellb: how firm is that May 15th week for the next summit?21:04
jog0err 2221:04
russellbmikal: contract signed AFAIK21:04
russellbmikal: so very firm21:04
mikalrussellb: cool21:04
mikalrussellb: its nice to be able to plan21:04
russellbso, week of May 12-1621:05
russellbi think they have 5 days booked21:05
russellband we may offset design summit by a day21:05
russellbso something like, conf mon-thurs, design summit tues-fri21:05
russellbor something, not positive yet21:05
mikalCool21:05
russellbbut very likely21:05
mikalDo you have dates for the mid-cycle meetup? It seems like that might be the week of icehouse-2?21:05
russellb"they" being the foundation, that organizes these things21:05
russellbok, so mid-cycle meetup, good question21:06
*** vipul is now known as vipul-away21:06
*** geekinutah has joined #openstack-meeting21:06
russellbi gave some possible dates to the sponsors (bluehost), and last week they told me to just pick and week and they'll make it work21:06
russellbso now it's back on me21:06
russellbor us21:06
mikalPick me!21:06
mikalI can be the decider21:06
russellbheh21:07
russellbok, so based on the poll i did a while back21:07
russellbgood weeks looked like either january 13th21:07
*** b3nt_pin is now known as beagles21:07
russellbor feb 1721:07
* dansmith votes for the latter21:07
mikalJan 13 will clash with the ATC meetup in Australia21:07
russellbfeb 17 is a bit more "mid cycle"21:07
*** skraynev has quit IRC21:08
alaskiI'm in favor of Feb as well21:08
mriedemlocation?21:08
russellbin the US somewhere21:08
mikalAre you thinking an entire week?21:08
russellbdepends on the date we tell them21:08
*** skraynev has joined #openstack-meeting21:08
mikalOr like three days?21:08
russellbmikal: sounds like they're willing to host more like 3 days max21:08
russellb2 or 3 days21:08
* beagles votes for St. John's21:08
russellbprovide us space, and lunches21:08
dansmithI think that's more realistic anyway21:08
dansmithin terms of travel21:08
mikalOh, so somethign like Feb 17 to 19?21:08
MikeSpreitzerAtlanta21:08
russellbgeekinutah: around by chance?21:09
MikeSpreitzersorry,21:09
geekinutahyep21:09
*** sandywalsh has quit IRC21:09
russellbpossible locations sounded like Boston, or Phoenix21:09
* russellb doesn't really care21:09
geekinutahyeah Boston Phoenix or Provo21:09
* mikal wanted Utah21:09
mriedemphoenix, warm21:09
russellbProvo means possible ski trip :)21:09
dansmithI vote provo, phoenix, boston, in that order21:09
geekinutahthis is true :-)21:09
mikalWhere is Provo?21:09
russellbi haven't been snowboarding in years21:09
ryanpetrelloAtlanta in Jan/Feb == coooooooold21:09
russellbmikal: utah21:10
russellbbut any would be good :)21:10
beagleswondering if staying away from the east coast in that time of year would be a good idea ... for that kind of thing anyways21:10
russellbOK, so week of feb 17?21:10
mikalOh yeah, airport closures21:10
beaglessnowstorms messing with travel, etc21:10
MikeSpreitzerAtlanta was typo, sorry21:10
dimsyay to boston :)21:10
*** HenryG has quit IRC21:11
mikalrussellb: my chances of getting you to run it a week earlier are zero, right?21:11
MikeSpreitzerProvo or Pheonix would be my suggestion21:11
russellbmikal: a week earlier hits valentines day, which some people care about21:11
mikalrussellb: I have a probably clash depending on how long the meetup is for21:11
mikalWhat are the dates for Valentine's day?21:11
russellbunless we did a monday-tuesday meetup, perhaps21:11
russellbfeb 1421:11
mikal(Don't tell my wife I asked that)21:11
* russellb doesn't care about it, but some do21:11
shane-wang:D21:11
dripton+1 for avoiding valentine's day21:11
russellbcomstud told me he'd get shot21:11
cyeohmikal: that comment goes on facebook ;-)21:12
russellbfor example :)21:12
dansmithyeah and we need comstud21:12
mikalWell, 10 - 12 Feb would let people get back in time for the 14th21:12
driptonchanging +1 to -1 to avoid getting comstud shot21:12
mikalAnd then I would miss my kids birthday...21:12
russellbmikal: what would make you miss it?21:12
mikals/would/wouldn't/21:12
russellboh, i see21:12
*** pcm_ has quit IRC21:12
russellbanyone *against* feb 10?21:12
mikalI need to be back in AU by 21 Feb, which makes the week of the 17th tight21:12
russellbmikal: 17-18 meetup?21:13
russellbwould get you back ... barely21:13
mikal17 - 19 would get me back on the 21st21:13
russellbdansmith: i know you had some conflicts, feb 10 work for ou?21:13
mikalSo tight but doable21:13
* russellb nods21:13
dansmithrussellb: it would be tight for me, I'm looking21:13
russellbk21:13
dansmithyeah, I could do it21:14
russellbok, well, right now it's either feb 10 or feb 17, leaning toward feb 10, but i'll wait for anything further last minute "please no" comments, and i will re-review the poll results21:14
russellbfrom there i'll confirm it with bluehost, and report back21:14
mikalCool21:14
dansmithmikal: any chance you won't get funding, or will you definitely be there?21:14
russellbi know this needs to get firmed up asap for planning21:14
russellbsorry i'm terrible at this21:14
mikalI personally think three days would be better than two by the way21:14
russellbmikal: OK21:14
mikaldansmith: I need to check... I can do that today though.21:14
*** salv-orlando has joined #openstack-meeting21:14
mikalDo we have a mail thread for this I can let people know on?21:15
russellbmikal: i know 2 is quick for how far you're traveling ...21:15
*** nermina has joined #openstack-meeting21:15
dansmithmikal: okay, if it's unlikely, then maybe we could push for the later, and if not, then the earlier21:15
russellbbut maybe a smaller group can hang out another day, i dunno21:15
russellbi don't want to overextend our welcome21:15
geekinutahI think the mean consensus for length was 3 days also21:15
russellbmikal: no thread right now, please ping me21:15
mikalrussellb: sure21:15
russellbgeekinutah: yeah, but jsmith acted like 3 might be a bit much21:15
jaybuffi expect my employeer to sign the stupid CCLA.  if they do i hope to be more involved and I will attend.  I would love a snowboarding the weekend after with whomever is up for it.21:16
geekinutahwe should check with him on that21:16
geekinutahI think it can be done21:16
*** vijendar has quit IRC21:16
russellbjaybuff: awesome21:16
geekinutahwe just need to move schedules around21:16
russellbgeekinutah: OK21:16
*** vijendar has joined #openstack-meeting21:16
melwittsnowboarding fun21:16
jog0we are 15 min into the meeting and 3 weeks away from I-1 ...21:16
dansmithgeekinutah: do we get a tour of facilities?21:16
geekinutahcertainly21:16
russellbso ... to firm this up, i'm leaning toward feb 10 based on mikals conflict21:16
dansmithsweet21:16
russellband will ask for 3 days, but we'll happily take 221:16
jaybuff+1 provo, feb 10, 3 days21:17
russellbgoing to wait a day for mikal to get back to me21:17
russellband then will push forward21:17
russellbsound good?21:17
mikalThanks guys21:17
* russellb nods21:17
russellbok, onward21:17
russellb#topic bugs21:17
*** openstack changes topic to "bugs (Meeting topic: nova)"21:17
russellbone thing i've mentioned by mail, and in the design summit, is that we need a bug czar21:18
russellbbecause it's one thing that i drop the ball on trying to do everything21:18
*** IlyaE has quit IRC21:18
russellblifeless spoke up at the design summit as willing to start helping with this21:18
russellbfor reference, here is our current triage process:21:18
*** s3wong has joined #openstack-meeting21:18
russellb#link https://wiki.openstack.org/wiki/Nova/BugTriage21:18
russellbhowever, 82 bugs are untagged21:18
russellband 100 tagged bugs are untriaged (181 total untriaged)21:19
russellbso, we aren't doing great at it21:19
*** mylestro has left #openstack-meeting21:19
*** vipul-away is now known as vipul21:19
mriedemone person owning triage gets hard, i've done that before on projects and we had to start rotating it21:19
russellblifeless: around?  thoughts for how we can improve on our bug queue handling?21:19
lifelesshi21:19
lifelessnuts, today is a public holiday21:19
russellbwell i envision a person leading the effort, building a team21:19
lifelessthe bug thing is at the top of my todo list but I vagued on it cause I wasn't going to be here.21:19
*** julim has quit IRC21:19
lifelessI do have a plan!21:19
russellblifeless: ok, all good, shall we revisit next week?21:20
lifelessthree second over view21:20
russellbi like plans21:20
russellbk!21:20
lifelessget some metrics that I think are valuable to game21:20
lifelessask people to join and game them21:20
lifelessdon't mention the mile wide holes that can be driven through this plan in IRC21:20
lifeless*oops*21:20
russellb+121:20
russellba solid start to many things21:21
* russellb points at reviewstats21:21
*** sandywalsh has joined #openstack-meeting21:21
lifelessalso avoid the pathology of bad metrics that Ubuntu has seared in my consciousness21:21
*** ianj1 has joined #openstack-meeting21:21
russellbheh21:21
*** s3wong has quit IRC21:21
*** jlibosva has quit IRC21:22
russellbk, well let's dig into it more next week21:22
russellbenjoy your holiday :)21:22
russellb#topic sub-teams21:22
*** openstack changes topic to "sub-teams (Meeting topic: nova)"21:22
russellbalright, each week we also hit on status of some sub-team efforts within nova (or the compute program in general)21:22
*** rongze has joined #openstack-meeting21:22
russellbone that i'd like to start checking in on regularly this cycle is novaclient21:22
*** gatuus has joined #openstack-meeting21:23
russellbmultiple people have expressed interest in helping, some of which i still need to follow up with21:23
russellbbut melwitt is one, and she has stepped up to help bring some status info to our weekly meeting :-)21:23
russellbmelwitt: i know we're just getting started, but any thoughts for today?21:23
melwittyes, I have gathered a few metrics for the novaclient bugs and reviews21:23
russellbawesome21:23
*** kgriffs is now known as kgriffs_afk21:24
melwittthere are 107 open bugs, i.e. bugs that are not status 'fix released'. 40 bugs in new status, 2 high importance bugs (I don't remember how to link LP bugs here)21:24
melwittthere are 10 patch reviews up, all of which are being actively looked at/updated/reviewed, a couple of them are WIP21:25
russellbOK, so definitely need some help doing triage21:25
russellbyou can just paste bug links21:25
russellbbut sure we have a fancy bot in here for bug numbers ...21:25
russellbso the two High priority bugs, being looked at?21:25
melwittoh ok. https://bugs.launchpad.net/python-novaclient/+bug/103957221:25
russellblet's try ... bug 103957221:26
russellbno bug bot.21:26
driptonlp:103957221:26
driptonnope21:26
russellbthat first one looks fixed now21:26
russellbjoe linked to a patch that has since been merged21:26
melwittthe other is https://bugs.launchpad.net/python-novaclient/+bug/111659321:26
russellbmelwitt: do you have permissions to close bugs?21:26
russellbmelwitt: you just need to join the nova-bugs team on launchpad21:27
russellbin theory21:27
*** rongze has quit IRC21:27
*** sarob has joined #openstack-meeting21:27
melwittrussellb: oh, yes I'm part of nova-bugs team21:27
*** jaybuff has quit IRC21:27
russellbmelwitt: basically, change "Confirmed" to "Fix Committed"21:27
melwittrussellb: ah ok. thanks. I missed that it had been merged, I hadn't clicked on it21:27
russellball good :)21:28
russellbthat's why we're talking through them!21:28
russellbprogress21:28
russellbok, so the other one ... depends on a nova feature, and we have the nova feature as wishlist21:28
russellbso i think i'd change the novaclient bug to wishlist, as well21:28
melwittok. will do that.21:28
*** sarob has quit IRC21:28
russellband like magic, no more High bugs :-p21:29
mikalHeh21:29
russellbthanks for bringing the info!21:29
melwittI never knew it could be so simple! thanks for the help21:29
*** sarob has joined #openstack-meeting21:29
russellbif anyone would like to help with novaclient metrics, or help clean up the novaclient bug queue, please talk to melwitt !  (and you all can talk to me, too)21:29
russellbsounds like the bug queue is the biggest area in need of cleanup21:29
driptonfyi: the magic that closes bugs in launchpad fails if there's a dot after the bug number.  So tag maintainers need to look for bugs to manually mark fixed.21:30
russellbdripton: that seems like an oversight :)21:30
russellbin the magic21:30
rohitkrussellb: Can we form a subteam for third party compatibility efforts? I know atleast 5 folks who're interested21:30
mikaldripton: sounds like a bug needing fixing21:30
driptonrussellb: there's a regex somewhere in the git magic that needs fixing.  I'll look for it.21:30
russellbrohitk: that was next on my list!21:30
russellbdripton: great!21:30
russellbok, next sub-team ...21:31
russellbwe had a session on AWS (EC2) compatibility21:31
mikaldripton: probably openstack-infra/jeepyb ?21:31
*** epim has quit IRC21:31
russellbthe outcome was basically that those interested needed to coordinate efforts in a subteam21:31
*** sarob has quit IRC21:31
russellbrohitk: that was your session, right?21:31
rohitkrusselb: right21:31
*** sarob_ has joined #openstack-meeting21:31
russellbOK, great21:31
*** vipul is now known as vipul-away21:31
russellbso some thoughts on how to get started ... poll the openstack-dev mailing list for those that would like to join21:31
*** vipul-away is now known as vipul21:31
russellbaim to have at least a few people working together regularly21:31
russellband then find a time that is reasonable convenient for everyone to meet once a week21:32
russellband schedule an IRC meeting21:32
*** eglynn has quit IRC21:32
russellband then hopefully one person out of that group can come here and give some status to the rest of the nova community21:32
*** sarob_ has quit IRC21:32
russellbonce you have a group, work to divide and conquer work, baby steps21:32
*** sarob has joined #openstack-meeting21:33
russellbincrease some test coverage, close feature gaps, whatever you guys think is important21:33
russellbfrom a high level anyway :-)21:33
rohitkrussellb: sounds good, will get started on this21:33
russellbok, awesome21:33
russellbplease let me know if you want to discuss further or need any help21:33
russellbi'm happy to see this get going21:33
rohitkrussellb: absolutely, thanks21:33
russellband i can try to attend the first meetings at least to help talk about how the work integrates back into nova21:34
russellbprocesses and such21:34
russellbone other thing that we need a sub-team going on is containers21:34
russellbwe had a big discussion on the future of docker21:34
russellband it sounds like we may go with a separate project completely21:35
russellbstep 1 being come up with a straw man API for what such a project would expose21:35
russellbto help us really decide if it needs to be separate, or continue to be an extension to nova21:35
*** epim has joined #openstack-meeting21:35
russellbsamalba: around by chance?21:35
russellbi'm not sure we identified concretely who was going to run with this idea21:36
russellbbut samalba did the docker driver :)21:36
russellbso i'm hoping he does!21:36
*** jaybuff has joined #openstack-meeting21:36
*** hartsocks has quit IRC21:36
russellbfor reference ...21:36
russellb#link https://etherpad.openstack.org/p/docker-nova-hkg21:36
*** hartsocks has joined #openstack-meeting21:36
russellbbig list of people on there interested21:37
samalbarussellb: I am here21:37
russellbsamalba: just trying to identify next steps on our containers discussion21:37
samalba(reading the backlog)21:37
russellbsamalba: are you (or someone) going to start organizing that?  drawing up an API?21:37
samalbayes, I was planning to start the spec this week-end21:37
russellbperfect!21:37
samalbaand involve the people from the etherpad early21:37
russellbsounds great, let me know how it goes21:38
russellband i'll also try to check in with you21:38
samalbamainly draft the API + requirements for starting the implem21:38
* russellb nods21:38
russellbsounds like a good place to start21:38
samalbaI guess etherpad is the right place to draft21:38
russellbanother key bit is some architecture ... specifically, the interaction with existing openstack services21:38
samalbaexactly, it's included21:38
russellbsuch as, is it built on top of nova exclusively?21:38
russellbok, so you're all over it :)21:38
russellbyeah, etherpad or wiki, whichever21:39
russellbor a git repo21:39
jog0russellb: do we want this to be part of the openstack compute project (not sure if I got terminology right there), as in we would have nova and x21:39
samalbayes, just did not have the chance to start yet... but it's planned for short term :-)21:39
russellbwith just docs21:39
samalbaok21:39
jog0russellb: I guess I am jumping the gun, never mind21:39
russellbjog0: no, it's a good question21:39
russellbmy opionion is that containers are a part of nova right now, so this effort should start as a sub-project of the compute program21:40
*** adalbas has quit IRC21:40
jog0program ooh thats the word I was looking for21:40
russellbif this moves forward far enough that it becomes a new project, we'll re-evaluate21:40
russellbprograms are largely about groups of people21:40
russellbif the people working on it are largely separate from those doing nova, it would probably make sense to have a new program21:40
russellbif there's significant overlap, i would keep it under compute21:40
russellbfrom a technical standpoint, i think we could argue it either way21:40
russellbbut it really comes down to the people21:40
*** eglynn has joined #openstack-meeting21:41
russellbon a related note, every program is supposed to have a mission statement that helps capture the scope21:41
russellbi don't think we have one :)21:41
mikal"To not suck"21:41
*** shane-wan1 has joined #openstack-meeting21:41
russellb"compute" is our mission statement21:41
russellb:-p21:41
russellbmikal: and that21:41
*** gyee has joined #openstack-meeting21:41
mikal"To not suck at compute"21:41
jog0mikal: ++21:41
russellbso anyway, let's start with an effort of the compute program to bootstrap21:41
russellbmake sense?21:41
samalbarussellb: I have to leave IRC for a bit, but I'll keep you in the loop for specing this containers service21:42
*** shane-wang has quit IRC21:42
russellbsamalba: sounds good!21:42
russellbok, other subteams21:42
russellbscheduling, vmware, xenapi, hyper-v21:42
russellbanyone want to provide updates on those?21:42
russellball had a session, or multiple sessions last week21:42
n0anoscheduling - no meeting this week (recovering from the summit)21:42
russellbn0ano: sounds good, i'm still recovering too :)21:42
n0anolots of sessions from the summit, we'll start going over them next week.21:43
russellbsounds good21:43
russellb#topic blueprints21:43
*** openstack changes topic to "blueprints (Meeting topic: nova)"21:43
russellbso we had a thread about blueprint process here21:43
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2013-October/017290.html21:43
russellbI've started integrating our process tweaks into the main blueprints page21:43
russellb#link https://wiki.openstack.org/wiki/Blueprints21:43
*** jasondotstar has quit IRC21:43
mriedemwas just going to ask about that21:43
russellbif there is anything about the blueprint process not clear from that page, it needs love21:44
*** mrunge has quit IRC21:44
russellb(as of the last couple hours)21:44
*** jasondotstar has joined #openstack-meeting21:44
russellbso, we need to start reviewing these things21:44
russellb#link https://blueprints.launchpad.net/nova/+milestone/icehouse-121:44
russellb66 blueprints, all on icehouse-121:44
russellb<glare>21:44
russellbnone on 2 or 321:44
mriedemi can make that 6521:44
russellbcool :)21:45
russellbif you have something that you don't think will be merged by 3 weeks from today, please go ahead and update21:45
mriedeminstance type / flavor rename is just a lot of busy work, so taking a while21:45
russellbi'd like to spend tomorrow starting a big push to catch up on blueprint reviews21:45
russellbso if you're on nova-drivers, or would like to help (anyone can help), please hang around #openstack-nova tomorrow21:45
russellband we'll see how far we get21:45
russellbdepending on how well it goes, we may have another day next week21:45
*** DennyZhang has joined #openstack-meeting21:46
russellbany particular ones you guys want to talk about right now?21:46
*** jaybuff has quit IRC21:46
shane-wan1russellb: can you approve bp https://blueprints.launchpad.net/nova/+spec/pci-api-support?21:46
russellbheh21:46
shane-wan1we are confident for icehourse-121:47
dansmithhaha21:47
russellbwe will be reviewing blueprints tomorrow :)21:47
*** eglynn has quit IRC21:47
*** vipul is now known as vipul-away21:47
russellbthere are probably 50 that need to be looked at21:47
shane-wan1ok21:47
geekinutah+1, I just added one :-)21:47
russellbso you're not alone21:47
*** kgriffs_afk is now known as kgriffs21:47
russellbwe just need to firm up our process, and then talk about it at the summit21:47
russellband this week has been a bit of recovery21:47
shane-wan1is there a review meeting, which everyone  can join?21:48
jog0russellb: I like https://wiki.openstack.org/wiki/Blueprints#Blueprint_Review_Criteria21:48
russellbso i think we're finally to where we can catch up on this21:48
russellbshane-wan1: no specific time, just going to do it tomorrow on IRC21:48
russellb"tomorrow"21:48
dansmithshane-wan1: please read the scroll back from like three minutes ago21:48
russellbjog0: cool thanks21:48
shane-wan1ok, just disconnected, sorry21:48
shane-wan1:D21:48
russellblet's start pasting this wiki link everywhere21:48
russellba majority of people seem to screw up step 121:49
russellb(targeting to a milestone)21:49
russellbtargeting a milestone is a trigger to get review ...21:49
jog0russellb: that may help make it easier to review them tomorrow21:49
russellband then i get emails "why isn't my thing reviewed yet"21:49
russellbbecause you missed step 121:49
russellbjog0: yeah hope so, and we can tweak that criteria as we go21:49
russellbanother thing .... while we have 66 on icehouse, we probably have a couple hundred others21:49
*** jaybuff has joined #openstack-meeting21:49
russellbi'd like to do a mass close of others after another week or so21:49
russellbnext friday was the date i put on the ML a while back21:50
shane-wan1ideally, icehouse-3 will be busy21:50
russellbi'll post a reminder21:50
russellbhttps://blueprints.launchpad.net/nova/21:50
russellb358 total blueprints21:50
russellbneed to identify what's actually active work, so close them all :)21:50
shane-wan1oh, my god21:50
russellband see what gets reopened i guess21:50
russellbclose with a comment linking to process info21:50
shane-wan1blueprints look like bugs21:50
russellbnova is busy :)21:51
mroddenimplement all the thigns21:51
*** vipul-away is now known as vipul21:51
russellbOK, I think that's all for now!21:52
russellb#topic open discussion21:52
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:52
russellba few minutes for any other topics21:52
geekinutahI have a random topic21:52
mikalSo, I'm approved for Utah21:52
russellbmikal: nice work21:52
* beagles notes "fast work"21:52
russellbmikal: we decided it's only for people in the northern hemisphere though, sorry21:52
shane-wan1mikal: for meetup, so quick?21:53
geekinutahI don't know if anyone here uses libvirt hooks to tray and track state changes21:53
geekinutahs/tray/try/21:53
geekinutahwe are starting down that road and I'm wondering if this is something that would belong in nova21:54
mikalrussellb: doh!21:54
russellbthe power state notification hook thing that nova has started using?21:54
geekinutahuhhhhh, probably similar, first I've heard of it though21:54
russellbok, well take a look ...21:54
dansmithgeekinutah: yeah, some work has been done there21:54
russellbwe have a thing now where nova gets notified of VM power state changes21:54
russellbinstead of nova polling in a periodic task21:55
*** dkranz has quit IRC21:55
geekinutahomg21:55
*** topol has quit IRC21:55
russellbuses a libvirt hook21:55
russellb:)21:55
geekinutahso that's awesome, I'll check it out21:55
russellbwas merged into grizzly IIRC21:55
russellblike last minute grizzly21:55
*** dkranz has joined #openstack-meeting21:55
russellbthough i think it may have been broken until recently ...21:55
geekinutahanyone remember the blueprint?21:56
russellbgeekinutah: search "virtevent" in nova/compute/manager.py21:56
russellbgeekinutah: and git blame / log from there21:56
russellbbest i got21:56
russellbactually blueprint is compute-driver-events21:56
russellbhttps://blueprints.launchpad.net/nova/+spec/compute-driver-events21:57
geekinutahthank you much, I will investigate21:57
russellbnp21:57
russellbanything else?21:57
*** dprince has quit IRC21:57
beaglesmmmm21:57
russellbbeagles: neutron parity notes?  :)21:58
beaglesfwiw there will be some activity in the next bit in the bit of neutronv2 code21:58
russellbexcellent21:58
beagles(sorry dog just tipped computer over)21:59
russellbha21:59
russellbwork from home life21:59
shane-wan1:D21:59
shane-wan1admire21:59
russellbalright, everyone, about out of time21:59
beaglesas it is in the nova tree the reviews are going to show up on that side of things,I'm going to be hauling neutron folks over to review21:59
beaglesbut ...21:59
russellbbiggest thing this week, let's get these blueprints in shape21:59
russellbbeagles: OK, if you can help identify which ones need priority that'd be great22:00
beaglesI may ask some questions regarding assumptions where the API might be a ambiguous22:00
russellbreport them in this meeting is a good time22:00
beaglesagreed and will do22:00
russellbor ML threads as needed22:00
russellbtagged with [Nova][Neutron]22:00
russellbhopefully that will get the right attention22:00
* beagles nods22:01
russellbthanks everyone!22:01
russellb#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Thu Nov 14 22:01:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-11-14-21.01.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-11-14-21.01.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-11-14-21.01.log.html22:01
*** beagles has quit IRC22:01
*** MikeSpreitzer has left #openstack-meeting22:01
*** rohitk has quit IRC22:01
*** geekinutah has left #openstack-meeting22:02
*** dolphm has joined #openstack-meeting22:02
*** jasondotstar has quit IRC22:02
*** beagles has joined #openstack-meeting22:03
*** jecarey has quit IRC22:03
*** gatuus has quit IRC22:04
*** epim has quit IRC22:06
*** dolphm has quit IRC22:07
*** jaybuff has quit IRC22:08
*** kgriffs is now known as kgriffs_afk22:09
*** kin is now known as nikhil__22:10
*** venkatesh has quit IRC22:11
*** esheffield_ has quit IRC22:11
*** nikhil has quit IRC22:11
*** shane-wan1 has quit IRC22:15
*** thelorax123 has quit IRC22:16
*** steven-weston has joined #openstack-meeting22:16
*** lblanchard has quit IRC22:17
*** johnthetubaguy has joined #openstack-meeting22:17
*** otherwiseguy has joined #openstack-meeting22:19
*** jecarey has joined #openstack-meeting22:20
*** litong has quit IRC22:21
*** rongze has joined #openstack-meeting22:23
*** lbragstad has quit IRC22:25
*** lbragstad has joined #openstack-meeting22:26
*** rongze has quit IRC22:27
*** loq_mac has joined #openstack-meeting22:28
*** stevemar has quit IRC22:28
*** ayoung has quit IRC22:29
*** jhenner has quit IRC22:31
*** maurosr has quit IRC22:31
*** lbragstad has quit IRC22:31
*** maurosr has joined #openstack-meeting22:32
*** maurosr has quit IRC22:32
*** loq_mac has quit IRC22:33
*** n0ano has quit IRC22:34
*** ianj1 has left #openstack-meeting22:34
*** maurosr has joined #openstack-meeting22:34
*** loq_mac has joined #openstack-meeting22:35
*** flaper87 is now known as flaper87|afk22:35
*** kmartin has quit IRC22:35
*** mriedem has left #openstack-meeting22:37
*** ryanpetrello has quit IRC22:37
*** weshay has quit IRC22:38
*** hartsocks has quit IRC22:39
*** gatuus has joined #openstack-meeting22:39
*** vipul is now known as vipul-away22:39
*** jmontemayor has quit IRC22:41
*** johnthetubaguy1 has joined #openstack-meeting22:41
*** vipul-away is now known as vipul22:41
*** luisg has joined #openstack-meeting22:43
*** markvan has quit IRC22:43
*** johnthetubaguy has quit IRC22:45
*** johnthetubaguy has joined #openstack-meeting22:47
*** steven-weston has quit IRC22:47
*** johnthetubaguy1 has quit IRC22:48
*** oubiwann has quit IRC22:48
*** joesavak has quit IRC22:49
*** bill_az has joined #openstack-meeting22:51
*** vijendar has quit IRC22:51
*** rudrarugge has quit IRC22:51
*** vijendar has joined #openstack-meeting22:52
*** julim has joined #openstack-meeting22:52
*** ttrifonov is now known as ttrifonov_zZzz22:52
*** vuil has joined #openstack-meeting22:52
*** vijendar has quit IRC22:57
*** nermina has quit IRC22:57
*** denis_makogon has quit IRC22:59
*** nati_ueno has joined #openstack-meeting22:59
*** johnthetubaguy has quit IRC23:00
*** dcramer_ has quit IRC23:00
*** dcramer_ has joined #openstack-meeting23:01
*** michchap has quit IRC23:02
*** julim has quit IRC23:03
*** dkranz has quit IRC23:04
*** michchap has joined #openstack-meeting23:04
*** hemna is now known as hemnafk23:07
*** melwitt has left #openstack-meeting23:09
*** Linz has quit IRC23:09
*** burt has quit IRC23:09
*** Linz has joined #openstack-meeting23:10
*** neelashah has quit IRC23:12
*** edmund has quit IRC23:13
*** julim has joined #openstack-meeting23:13
*** kevinconway has joined #openstack-meeting23:15
*** ivasev has quit IRC23:16
*** mrodden has quit IRC23:22
*** sacharya has quit IRC23:23
*** rongze has joined #openstack-meeting23:24
*** jaybuff has joined #openstack-meeting23:25
*** thomasem has quit IRC23:25
*** jaybuff has left #openstack-meeting23:26
*** rongze has quit IRC23:29
*** pablosan has quit IRC23:33
*** loq_mac has quit IRC23:36
*** adalbas has joined #openstack-meeting23:36
*** danwent has joined #openstack-meeting23:39
*** dvarga has quit IRC23:42
*** eharney has quit IRC23:43
*** rakhmerov has quit IRC23:43
*** fnaval_ has quit IRC23:45
*** ArxCruz has quit IRC23:46
*** matsuhashi has joined #openstack-meeting23:47
*** DennyZhang has quit IRC23:52
*** thomasem has joined #openstack-meeting23:53
*** adalbas has quit IRC23:55
*** dcramer_ has quit IRC23:56
*** ayoung has joined #openstack-meeting23:58

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