Wednesday, 2013-10-23

*** rudrarugge has quit IRC00:00
*** oubiwann_ has joined #openstack-meeting00:04
*** yaguang has quit IRC00:05
*** ryanpetrello has joined #openstack-meeting00:07
*** radsy has quit IRC00:07
*** hemna has quit IRC00:11
*** ryanpetrello has quit IRC00:13
*** SumitNaiksatam has quit IRC00:15
*** markpeek has joined #openstack-meeting00:15
*** cody-somerville has quit IRC00:18
*** sacharya has joined #openstack-meeting00:21
*** SumitNaiksatam has joined #openstack-meeting00:24
*** oubiwann_ has quit IRC00:27
*** zul has quit IRC00:29
*** doron is now known as doron_afk00:30
*** rakhmerov has joined #openstack-meeting00:33
*** SumitNaiksatam has quit IRC00:34
*** jamespage_ has joined #openstack-meeting00:35
*** pauli1 has quit IRC00:35
*** vuil has quit IRC00:35
*** Guest34448 has quit IRC00:36
*** rwsu is now known as rwsu-away00:37
*** rakhmerov has quit IRC00:37
*** yogeshmehra has quit IRC00:39
*** dstanek has quit IRC00:39
*** sacharya1 has joined #openstack-meeting00:40
*** sacharya has quit IRC00:40
*** mestery has quit IRC00:41
*** SumitNaiksatam has joined #openstack-meeting00:41
*** sarob has quit IRC00:41
*** reed has quit IRC00:41
*** dstanek has joined #openstack-meeting00:42
*** nosnos has joined #openstack-meeting00:43
*** jamespage_ has quit IRC00:43
*** asalkeld_lunch is now known as asalkeld00:48
*** SumitNaiksatam has quit IRC00:50
*** Guest34448 has joined #openstack-meeting00:52
*** Devioslang has joined #openstack-meeting00:53
*** lblanchard has quit IRC00:57
*** vipul is now known as vipul-away01:00
*** markpeek has left #openstack-meeting01:03
*** Mandell has quit IRC01:03
*** markpeek has joined #openstack-meeting01:03
*** DennyZhang has joined #openstack-meeting01:04
*** Mandell has joined #openstack-meeting01:04
*** MadOwl has quit IRC01:04
*** nermina has joined #openstack-meeting01:05
*** Mandell has quit IRC01:08
*** vipul-away is now known as vipul01:09
*** nermina has quit IRC01:12
*** haomaiwang has joined #openstack-meeting01:13
*** oubiwann_ has joined #openstack-meeting01:14
*** oubiwann_ has quit IRC01:15
*** haomaiwang has quit IRC01:17
*** oubiwann is now known as oubiwann-lambda01:19
*** markmcclain has quit IRC01:22
*** dims has quit IRC01:23
*** nermina has joined #openstack-meeting01:25
*** twoputt has quit IRC01:27
*** twoputt_ has quit IRC01:27
*** openstack has joined #openstack-meeting01:34
*** ChanServ sets mode: +o openstack01:34
*** rakhmerov has quit IRC01:37
*** rakhmerov1 has joined #openstack-meeting01:37
*** markwash has quit IRC01:38
*** esker has joined #openstack-meeting01:38
*** anteaya has quit IRC01:39
*** asalkeld has quit IRC01:40
*** asalkeld has joined #openstack-meeting01:46
*** sjing has joined #openstack-meeting01:47
*** DennyZhang has quit IRC01:47
*** dcramer_ has quit IRC01:49
*** rongze has joined #openstack-meeting01:50
*** SergeyLukjanov has quit IRC01:58
*** danwent has quit IRC01:58
*** thomasm has joined #openstack-meeting01:59
*** SumitNaiksatam has joined #openstack-meeting01:59
*** lpabon has joined #openstack-meeting02:01
*** ArxCruz has joined #openstack-meeting02:09
*** markwash has joined #openstack-meeting02:10
*** IlyaE has quit IRC02:15
*** jlucci has joined #openstack-meeting02:16
*** sjing has quit IRC02:20
*** sjing has joined #openstack-meeting02:23
*** jlucci has quit IRC02:24
*** vipul has quit IRC02:25
*** rongze has quit IRC02:25
*** rongze has joined #openstack-meeting02:25
*** rongze has quit IRC02:25
*** vipul has joined #openstack-meeting02:26
*** rongze has joined #openstack-meeting02:26
*** kersten has quit IRC02:27
*** gyee has quit IRC02:27
*** imsurit has joined #openstack-meeting02:35
*** imsurit is now known as Guest6412702:35
*** haomaiwang has joined #openstack-meeting02:36
*** Guest64127 has quit IRC02:37
*** topol has joined #openstack-meeting02:38
*** zehicle_at_dell has joined #openstack-meeting02:46
*** IlyaE has joined #openstack-meeting02:46
*** cody-somerville has joined #openstack-meeting02:56
*** rongze has quit IRC02:58
*** rongze has joined #openstack-meeting02:59
*** afazekas has joined #openstack-meeting03:01
*** shakayumi has joined #openstack-meeting03:02
*** rongze has quit IRC03:04
*** rongze has joined #openstack-meeting03:05
*** asalkeld has quit IRC03:14
*** IlyaE has quit IRC03:16
*** lpabon has quit IRC03:17
*** sjing has quit IRC03:19
*** suo has joined #openstack-meeting03:20
*** sjing has joined #openstack-meeting03:20
*** vkmc has quit IRC03:24
*** otherwiseguy has quit IRC03:29
*** dscannell has joined #openstack-meeting03:31
*** Mandell has joined #openstack-meeting03:42
*** IlyaE has joined #openstack-meeting03:46
*** shakayumi has quit IRC03:46
*** ryanpetrello has joined #openstack-meeting03:46
*** jecarey has joined #openstack-meeting03:46
*** DennyZhang has joined #openstack-meeting03:48
*** fnaval_ has joined #openstack-meeting03:51
*** ArxCruz has quit IRC03:52
*** dcramer_ has joined #openstack-meeting03:55
*** neelashah has joined #openstack-meeting03:55
*** leif has quit IRC03:57
*** vishy has quit IRC04:00
*** IlyaE has quit IRC04:02
*** Loquacity has quit IRC04:02
*** esker has quit IRC04:05
*** cody-somerville has quit IRC04:08
*** toanster_ has quit IRC04:10
*** alaski has quit IRC04:11
*** rosmaita has quit IRC04:12
*** metral has quit IRC04:12
*** ameade_ has quit IRC04:12
*** venkat_ has quit IRC04:12
*** esheffield has quit IRC04:12
*** nikhil has quit IRC04:12
*** iccha_ has quit IRC04:12
*** clarkb has quit IRC04:13
*** esheffield has joined #openstack-meeting04:16
*** nikhil has joined #openstack-meeting04:16
*** venkat_ has joined #openstack-meeting04:17
*** IlyaE has joined #openstack-meeting04:17
*** leif has joined #openstack-meeting04:18
*** IlyaE has quit IRC04:20
*** iccha has joined #openstack-meeting04:20
*** ameade has joined #openstack-meeting04:20
*** rosmaita has joined #openstack-meeting04:20
*** alaski has joined #openstack-meeting04:20
*** toanster has joined #openstack-meeting04:20
*** clarkb has joined #openstack-meeting04:23
*** amotoki has joined #openstack-meeting04:26
*** dscannell has quit IRC04:27
*** zehicle_at_dell has quit IRC04:27
*** cody-somerville has joined #openstack-meeting04:29
*** garyk has quit IRC04:32
*** neelashah has quit IRC04:33
*** IlyaE has joined #openstack-meeting04:33
*** IlyaE has quit IRC04:34
*** vishy has joined #openstack-meeting04:36
*** esker has joined #openstack-meeting04:37
*** cody-somerville has quit IRC04:38
*** metral has joined #openstack-meeting04:38
*** haomaiwang has quit IRC04:43
*** twoputt_ has joined #openstack-meeting04:44
*** twoputt has joined #openstack-meeting04:44
*** thomasbiege has joined #openstack-meeting04:44
*** rongze has quit IRC04:45
*** rongze has joined #openstack-meeting04:46
*** rongze has quit IRC04:50
*** davidhadas has joined #openstack-meeting04:56
*** yogeshme_ has joined #openstack-meeting04:59
*** sacharya1 has quit IRC05:00
*** asalkeld has joined #openstack-meeting05:06
*** thomasbiege has quit IRC05:07
*** markpeek has quit IRC05:08
*** thomasbiege has joined #openstack-meeting05:09
*** esker has quit IRC05:11
*** esker has joined #openstack-meeting05:11
*** akuznetsov has joined #openstack-meeting05:13
*** cody-somerville has joined #openstack-meeting05:14
*** yogeshme_ has quit IRC05:15
*** esker has quit IRC05:16
*** rongze has joined #openstack-meeting05:16
*** akuznetsov has quit IRC05:17
*** DennyZhang has quit IRC05:17
*** akuznetsov has joined #openstack-meeting05:20
*** esker has joined #openstack-meeting05:21
*** vuil has joined #openstack-meeting05:22
*** esker has quit IRC05:24
*** rongze has quit IRC05:24
*** esker has joined #openstack-meeting05:25
*** esker has quit IRC05:29
*** novas0x2a|laptop has quit IRC05:32
*** yanglyy has joined #openstack-meeting05:34
*** dstanek has quit IRC05:34
*** moe811 has quit IRC05:35
*** moe66 has quit IRC05:35
*** nadya has joined #openstack-meeting05:37
*** twoputt_ has quit IRC05:39
*** twoputt has quit IRC05:39
*** moe66 has joined #openstack-meeting05:39
*** moe811 has joined #openstack-meeting05:39
*** thomasbiege has quit IRC05:43
*** esker has joined #openstack-meeting05:46
*** esker has quit IRC05:47
*** esker has joined #openstack-meeting05:48
*** nadya has quit IRC05:50
*** garyk has joined #openstack-meeting05:52
*** comay has quit IRC05:52
*** esker has quit IRC05:52
*** cody-somerville has quit IRC05:53
*** jecarey has quit IRC05:53
*** nermina has quit IRC05:56
*** comay has joined #openstack-meeting05:58
*** thomasbiege has joined #openstack-meeting05:59
*** akuznetsov has quit IRC06:02
*** thomasbiege2 has joined #openstack-meeting06:04
*** thomasbiege has quit IRC06:06
*** SergeyLukjanov has joined #openstack-meeting06:06
*** thomasbiege2 has quit IRC06:10
*** jlibosva has joined #openstack-meeting06:11
*** nadya has joined #openstack-meeting06:15
*** llu has quit IRC06:15
*** llu has joined #openstack-meeting06:16
*** akuznetsov has joined #openstack-meeting06:17
*** esker has joined #openstack-meeting06:19
*** nadya has quit IRC06:19
*** IlyaE has joined #openstack-meeting06:22
*** topol has quit IRC06:26
*** rongze has joined #openstack-meeting06:27
*** davidhadas has quit IRC06:27
*** vuil has quit IRC06:29
*** nadya has joined #openstack-meeting06:30
*** thomasbiege has joined #openstack-meeting06:41
*** nadya has quit IRC06:42
*** cody-somerville has joined #openstack-meeting06:43
*** doron_afk has quit IRC06:45
*** mrunge has joined #openstack-meeting06:47
*** akuznetsov has quit IRC06:47
*** thomasbiege2 has joined #openstack-meeting06:47
*** akuznetsov has joined #openstack-meeting06:48
*** yogeshme_ has joined #openstack-meeting06:48
*** Fdot has joined #openstack-meeting06:49
*** thomasbiege has quit IRC06:50
*** IlyaE has quit IRC06:51
*** akuznetsov has quit IRC06:52
*** esker has quit IRC06:53
*** resker has joined #openstack-meeting06:56
*** comay has quit IRC07:00
*** thomasbiege has joined #openstack-meeting07:02
*** thomasbiege3 has joined #openstack-meeting07:02
*** thomasbiege has quit IRC07:04
*** thomasbiege2 has quit IRC07:06
*** MarkAtwood has joined #openstack-meeting07:09
*** marekd|away is now known as marekd07:12
*** sdake has quit IRC07:13
*** lsmola has joined #openstack-meeting07:13
*** jcoufal has joined #openstack-meeting07:13
*** davidhadas has joined #openstack-meeting07:14
*** marun has quit IRC07:20
*** marun has joined #openstack-meeting07:20
*** eglynn has quit IRC07:22
saschpedavid-lyle: hi, sorry for missing the recent discussing about lesscpy, I'll reply to jtomasek's mail. I've been on FTO lately.07:24
*** MarkAtwood has quit IRC07:24
*** doron_afk has joined #openstack-meeting07:27
*** shardy_afk is now known as shardy07:28
*** doron_afk is now known as doron07:30
*** davidhadas has quit IRC07:32
*** doron is now known as doron_afk07:38
*** aloga has quit IRC07:45
*** aloga has joined #openstack-meeting07:45
*** doron_afk has quit IRC07:49
*** akuznetsov has joined #openstack-meeting07:51
*** cdub_ has joined #openstack-meeting07:52
*** thomasbiege3 has quit IRC07:56
*** thomasbiege has joined #openstack-meeting07:58
*** fbo_away is now known as fbo07:59
*** SergeyLukjanov has quit IRC08:02
*** johnthetubaguy has joined #openstack-meeting08:09
*** cdub_ has quit IRC08:10
*** derekh has joined #openstack-meeting08:11
*** kiall has quit IRC08:12
*** davidhadas has joined #openstack-meeting08:12
*** yassine has joined #openstack-meeting08:13
*** Shaan7 has quit IRC08:17
*** eglynn has joined #openstack-meeting08:19
*** kiall has joined #openstack-meeting08:22
*** johnthetubaguy1 has joined #openstack-meeting08:30
*** johnthetubaguy has quit IRC08:30
*** yogeshme_ has quit IRC08:31
*** rongze_ has joined #openstack-meeting08:32
*** rongze has quit IRC08:34
*** jtomasek has joined #openstack-meeting08:34
*** suo has quit IRC08:35
*** suo has joined #openstack-meeting08:35
*** Mandell has quit IRC08:37
*** sushils has joined #openstack-meeting08:41
*** thomasbiege has quit IRC08:42
*** sjing has quit IRC08:46
*** johnthetubaguy1 has quit IRC08:50
*** asalkeld has quit IRC08:53
*** asalkeld has joined #openstack-meeting08:53
*** bogdando has quit IRC09:01
*** bogdando has joined #openstack-meeting09:06
*** Fdot_ has joined #openstack-meeting09:06
*** Fdot has quit IRC09:10
*** eharney has joined #openstack-meeting09:11
*** Fdot_ has quit IRC09:12
*** nosnos has quit IRC09:12
*** Loquacities has quit IRC09:12
*** cdub_ has joined #openstack-meeting09:12
*** nosnos has joined #openstack-meeting09:13
*** Fdot has joined #openstack-meeting09:13
*** matsuhashi has quit IRC09:13
*** matsuhashi has joined #openstack-meeting09:14
*** nosnos has quit IRC09:17
*** matsuhashi has quit IRC09:19
*** Loquacities has joined #openstack-meeting09:20
*** jtomasek has quit IRC09:22
*** jtomasek has joined #openstack-meeting09:25
*** yogeshmehra has joined #openstack-meeting09:36
*** cdub_ has quit IRC09:39
*** thomasbiege1 has joined #openstack-meeting09:41
*** marun has quit IRC09:41
*** marun has joined #openstack-meeting09:44
*** ogelbukh has quit IRC09:50
*** alexpilotti has quit IRC09:51
*** ogelbukh has joined #openstack-meeting10:00
*** davidhadas_ has joined #openstack-meeting10:01
*** Devioslang has quit IRC10:03
*** davidhadas has quit IRC10:04
*** Fdot has quit IRC10:10
*** eharney has quit IRC10:10
*** ruhe has joined #openstack-meeting10:11
*** sjing has joined #openstack-meeting10:13
*** ItSANgo_ has joined #openstack-meeting10:17
*** ruhe has quit IRC10:27
*** pcm_ has joined #openstack-meeting10:27
*** alexpilotti has joined #openstack-meeting10:30
*** dims has joined #openstack-meeting10:34
*** pcm_ has quit IRC10:45
*** pcm_ has joined #openstack-meeting10:45
*** zhhuabj_home has joined #openstack-meeting10:51
*** suo has quit IRC10:55
*** AJaeger has joined #openstack-meeting10:55
*** AJaeger has left #openstack-meeting10:56
*** rongze_ has quit IRC10:56
*** yanglyy has quit IRC10:57
*** ruhe has joined #openstack-meeting11:06
*** davidhadas has joined #openstack-meeting11:12
*** davidhadas_ has quit IRC11:15
*** weshay has joined #openstack-meeting11:15
*** rakhmerov1 has quit IRC11:16
*** rakhmerov has joined #openstack-meeting11:16
*** rongze has joined #openstack-meeting11:20
*** suo has joined #openstack-meeting11:24
*** jhenner has joined #openstack-meeting11:24
*** amotoki has quit IRC11:39
*** thomasbiege2 has joined #openstack-meeting11:40
*** thomasbiege1 has quit IRC11:43
*** ArxCruz has joined #openstack-meeting11:44
*** egallen has joined #openstack-meeting11:48
*** dcramer_ has quit IRC11:53
*** bgorski has joined #openstack-meeting11:53
*** adalbas has joined #openstack-meeting11:57
*** pdmars has joined #openstack-meeting12:03
*** dkranz has quit IRC12:03
*** galstrom_zzz is now known as galstrom12:06
*** galstrom is now known as galstrom_zzz12:07
*** sjing has quit IRC12:10
*** slong has joined #openstack-meeting12:13
*** rdxc has joined #openstack-meeting12:13
*** mestery has joined #openstack-meeting12:20
*** anteaya has joined #openstack-meeting12:20
*** ruhe has quit IRC12:25
*** sjing has joined #openstack-meeting12:27
*** thomasbiege2 has quit IRC12:27
*** thomasbiege1 has joined #openstack-meeting12:28
*** resker has quit IRC12:29
*** deviosLang has joined #openstack-meeting12:30
*** zhhuabj_home has quit IRC12:34
*** dstanek has joined #openstack-meeting12:35
*** vkmc has joined #openstack-meeting12:37
*** sjing has quit IRC12:37
*** julim has joined #openstack-meeting12:38
*** akuznetsov has quit IRC12:39
*** bpokorny has joined #openstack-meeting12:42
*** akuznetsov has joined #openstack-meeting12:43
*** egallen has quit IRC12:45
*** deviosLang has quit IRC12:45
*** akuznetsov has quit IRC12:46
*** harlowja_ has quit IRC12:46
*** ruhe has joined #openstack-meeting12:47
*** ruhe has quit IRC12:47
*** akuznetsov has joined #openstack-meeting12:49
*** Fdot has joined #openstack-meeting12:52
*** dkranz has joined #openstack-meeting12:52
*** chandankumar has quit IRC12:54
*** garyk1 has joined #openstack-meeting12:54
*** slong has quit IRC12:55
*** weshay has quit IRC12:55
*** garyk has quit IRC12:56
*** dprince has joined #openstack-meeting12:57
*** deviosLang has joined #openstack-meeting12:59
*** ruhe has joined #openstack-meeting13:00
*** suo has quit IRC13:03
*** ruhe has quit IRC13:04
*** lblanchard has joined #openstack-meeting13:06
*** Fdot_ has joined #openstack-meeting13:06
*** thomasm has joined #openstack-meeting13:08
*** thomasm is now known as Guest2953113:08
*** Fdot__ has joined #openstack-meeting13:09
*** Fdot has quit IRC13:10
*** Fdot_ has quit IRC13:11
*** Fdot__ has quit IRC13:13
*** dcramer_ has joined #openstack-meeting13:17
*** radez_g0n3 is now known as radez13:20
*** oubiwann has joined #openstack-meeting13:21
*** radez is now known as radez_g0n313:22
*** thomasbiege2 has joined #openstack-meeting13:22
*** neelashah has joined #openstack-meeting13:22
*** radez_g0n3 is now known as radez13:24
*** joesavak has joined #openstack-meeting13:25
*** thomasbiege1 has quit IRC13:26
*** dkehn_ has joined #openstack-meeting13:27
*** kevinconway has quit IRC13:29
*** otherwiseguy has joined #openstack-meeting13:29
*** fnaval_ has quit IRC13:30
*** fnaval_ has joined #openstack-meeting13:31
*** nermina has joined #openstack-meeting13:32
*** dcramer_ has quit IRC13:33
*** fnaval_ has quit IRC13:35
*** kevinconway has joined #openstack-meeting13:37
*** weshay has joined #openstack-meeting13:38
*** dscannell has joined #openstack-meeting13:39
*** jsavak has joined #openstack-meeting13:40
*** joesavak has quit IRC13:40
*** dkehn_ is now known as dkehn_w13:41
*** sacharya has joined #openstack-meeting13:41
*** dkehn_w is now known as w_dkehn13:41
*** burt has joined #openstack-meeting13:43
*** vijendar has joined #openstack-meeting13:45
*** johnthetubaguy has joined #openstack-meeting13:46
*** markpeek has joined #openstack-meeting13:46
*** lbragstad has joined #openstack-meeting13:46
*** eharney has joined #openstack-meeting13:47
*** sacharya has quit IRC13:48
*** akuznetsov has quit IRC13:50
*** mrunge has quit IRC13:52
*** egallen has joined #openstack-meeting13:53
*** akuznetsov has joined #openstack-meeting13:53
*** dandrushko has joined #openstack-meeting13:56
*** Linz has joined #openstack-meeting13:56
*** IlyaE has joined #openstack-meeting13:58
*** markvan has joined #openstack-meeting13:58
*** rakhmerov has quit IRC13:58
*** stevemar has joined #openstack-meeting14:00
*** Sukhdev has joined #openstack-meeting14:00
*** fnaval_ has joined #openstack-meeting14:01
*** asomya has joined #openstack-meeting14:01
*** jecarey has joined #openstack-meeting14:01
*** asomya has quit IRC14:03
*** davidhadas_ has joined #openstack-meeting14:04
*** Sukhdev has quit IRC14:04
*** yogeshmehra has quit IRC14:04
*** johnthetubaguy has quit IRC14:05
*** dkranz has quit IRC14:06
*** davidhadas has quit IRC14:06
*** amotoki has joined #openstack-meeting14:06
*** haomaiwang has joined #openstack-meeting14:06
*** esker has joined #openstack-meeting14:10
*** jlucci has joined #openstack-meeting14:14
*** rwsu-away is now known as rwsu14:14
*** dkranz has joined #openstack-meeting14:20
*** markvan_ has joined #openstack-meeting14:21
*** markvan has quit IRC14:24
*** markvan_ is now known as markvan14:24
*** jamespage_ has joined #openstack-meeting14:28
*** sacharya has joined #openstack-meeting14:28
*** beagles_ has joined #openstack-meeting14:30
*** jamespage_ has quit IRC14:30
*** jamespage__ has joined #openstack-meeting14:30
*** beagles_ has quit IRC14:31
*** mrunge has joined #openstack-meeting14:32
*** beagles_ has joined #openstack-meeting14:32
*** cdub_ has joined #openstack-meeting14:32
*** beagles_ is now known as b3nt_pin14:33
*** jmontemayor has joined #openstack-meeting14:33
*** cloudchimp has joined #openstack-meeting14:34
david-lylesaschpe: no worries and thank you14:35
saschpedavid-lyle: sure14:36
david-lylesaschpe: seems like you've been able to get several pull requests merged. Are you the only active contributor, and do you have any idea how far we are from a working solution?14:37
*** cloudchimp has left #openstack-meeting14:38
saschpedavid-lyle: being able to compile bootstrap needs at least two fixes, the "clip" property and variables in @media. I already started to work on the former and it shouldn't be too hard. I'll try to get sth done tomorrow14:39
*** vijendar has quit IRC14:41
*** rongze has quit IRC14:41
*** vijendar has joined #openstack-meeting14:41
*** rakhmerov has joined #openstack-meeting14:42
*** whenry has joined #openstack-meeting14:43
david-lylesaschpe: that's great!  jtomasek implied you might need help, is that true?14:43
david-lylesounds like things are already progressing nicely14:44
saschpedavid-lyle: well, help is always appreciated. actually I'm pretty busy already :-)14:44
*** whenry has quit IRC14:45
*** whenry has joined #openstack-meeting14:46
*** jamespage_ has joined #openstack-meeting14:46
*** jamespage__ has quit IRC14:46
jtomaseksaschpe: thanks again for looking into it14:46
*** dkranz has quit IRC14:48
*** suo has joined #openstack-meeting14:48
*** garyk1 has quit IRC14:49
*** akuznetsov has quit IRC14:52
*** tanisdl has joined #openstack-meeting14:52
*** gkleiman has joined #openstack-meeting14:53
*** gkleiman_ has joined #openstack-meeting14:53
*** jrodom has joined #openstack-meeting14:53
*** jrodom has quit IRC14:53
*** jrodom has joined #openstack-meeting14:53
*** edgarstp has joined #openstack-meeting14:54
*** rongze has joined #openstack-meeting14:55
*** sarob has joined #openstack-meeting14:55
*** jcoufal has quit IRC14:56
*** marun has quit IRC14:56
*** galstrom_zzz is now known as galstrom14:58
*** marun has joined #openstack-meeting15:00
*** jodom has joined #openstack-meeting15:01
*** cody-somerville has quit IRC15:01
*** dkranz has joined #openstack-meeting15:01
*** BobBall has joined #openstack-meeting15:01
*** johnthetubaguy has joined #openstack-meeting15:01
BobBallAfternoon John!15:02
*** thedodd has quit IRC15:02
BobBallWasn't expecting you to make it today!15:02
*** jodom has quit IRC15:02
johnthetubaguyhello15:02
*** jodom has joined #openstack-meeting15:02
johnthetubaguyhave you started up yet?15:02
*** shakayumi has joined #openstack-meeting15:02
johnthetubaguyI will if not15:02
BobBallnope15:03
*** jodom has quit IRC15:03
johnthetubaguy#startmeeting XenAPI15:03
openstackMeeting started Wed Oct 23 15:03:55 2013 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: XenAPI)"15:03
openstackThe meeting name has been set to 'xenapi'15:03
*** jodom has joined #openstack-meeting15:04
johnthetubaguyso has anyone got anything today? shall we go through things as normal?15:04
BobBallMate's just popping in15:04
*** jrodom has quit IRC15:04
*** matel has joined #openstack-meeting15:04
BobBallActually I've got one thing I saw on the ML that's worth raising15:04
matelhi15:04
BobBallQuite an interesting one15:04
johnthetubaguycool15:04
johnthetubaguyI got to my hotel15:05
BobBallit's this gerrit script15:05
johnthetubaguyon the free 30mins wifi15:05
BobBallsubject gerrit tools15:05
johnthetubaguyOK15:05
BobBalloh - let's make sure the meeting is < 30 minutes then!15:05
johnthetubaguy#topic Open Discussion15:05
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"15:05
BobBallJust a very cool patch from Daniel P. Berrange about getting information on which changesets have been uploaded to gerrit15:05
BobBallI've been waiting for him to come on IRC so I could just check if he knew about getting gerrit to watch the changes for you15:06
BobBallbecause i've got that working for Xen and the way I read his email was that he might not have it for the libvirt stuff he's interested in15:06
BobBallIncidentally, the watch I've got on Xen pointed out a tool that's just been changed to help delete orphan VMs that I didn't know existed!15:07
BobBallhttps://review.openstack.org/#/c/53362/ That was this one :)15:07
johnthetubaguyOK cool15:07
*** galstrom is now known as galstrom_zzz15:07
BobBallso it's worth watching for gerrit_view for when daniel's changes are merged15:08
*** nermina has quit IRC15:08
BobBallhellova lot easier to find changes15:08
johnthetubaguyhmm, yeah, I not really played with any of that stuff recently15:08
*** thedodd has joined #openstack-meeting15:08
BobBallwell it's brand new isn't it?15:08
BobBallah well - doesn't matter15:09
*** galstrom_zzz is now known as galstrom15:09
BobBallSo - the other thing to talk about is xenserver-core15:09
johnthetubaguyOK15:09
BobBallMate's been working on automatically setting up a Ubuntu environment for it15:09
BobBallHow's that going Mate?15:09
johnthetubaguyinteresting, Ubuntu? what bits Ubuntu?15:10
matelIt's okay, atm the package build is broken, but i am doing infrastructural stuff, so not there yet.15:10
matelraring15:10
*** jhenner has quit IRC15:10
*** jsavak has quit IRC15:10
matelxenserver-core on raring15:10
matelreally cool stuff, amazing.15:10
BobBallI think the next build should pass - we brought back a bug when fixing iscsi stuff on xenserver-core15:10
*** joesavak has joined #openstack-meeting15:10
BobBallSpeaking of which...15:10
mateljohn: it's the new xcp-xapi15:11
BobBallSome fun things have been found when trying to use xenserver-core with openstack15:11
johnthetubaguymatel: cool, thanks15:11
BobBallsuch as XenServer's use of patched open-iscsi15:11
BobBallwe were using a custom patch to allow us to use per-connection CHAP details15:11
BobBallwhich openstack uses15:11
johnthetubaguyhmm, fun15:12
BobBallbut we were doing it way before upstream supported it15:12
BobBallso that's why we made our own in-house patch (bad XenServer!)15:12
*** deviosLang has quit IRC15:12
BobBallAnyway - it's highlighting all of the things that we're having to fix anyway in the upstreaming / open sourcing efforts15:12
johnthetubaguyah yes, good to fix that15:12
BobBallthat one had already been fixed as it happens - but there is another one with the custom changes to LVM which we're having to work around too15:13
*** amotoki has quit IRC15:13
BobBallThe current status is we have xenserver-core hosts which run VMs started through openstack (although exercises.sh currently fails as we have the wrong version of the SM code which is still relying on our custom patches for open-iscsi)15:13
BobBallwatch this space for the fix to that15:13
*** nermina has joined #openstack-meeting15:13
johnthetubaguycool, so everything but volumes?15:14
johnthetubaguyin the exercises?15:14
BobBallyes15:14
BobBallwell15:14
BobBallvolumes and euca which both fail on volumes15:14
matelI think we are really close.15:14
BobBallI can smell victory15:14
johnthetubaguyits a nice smell15:15
BobBallSo we're expecting to have a demo of xenserver-core doing live migrations for the summit15:15
*** whenry has quit IRC15:15
johnthetubaguyI guess, summit wise, its worth saying the session is looking well prepared now15:15
johnthetubaguylive-migrate is always a cool demo15:15
*** Kharec has quit IRC15:15
BobBallLive-migration with a xen-based hypervisor running on  your own distro is even cooler.15:16
johnthetubaguytrue15:16
*** sarob has quit IRC15:16
BobBallYeah15:16
*** rnirmal has joined #openstack-meeting15:16
BobBallin some ways you living so close is a shame15:17
johnthetubaguyso any more for any more?15:17
*** cdub_ has quit IRC15:17
BobBallbecause it means we had a real meeting to walk through the summit and it wasn't on IRC!15:17
johnthetubaguylol15:17
BobBallBut anyone who wants to see the output can check out the etherpad15:17
*** sarob has joined #openstack-meeting15:17
johnthetubaguyyou got the link handy?15:17
BobBall#link https://etherpad.openstack.org/IcehouseXenAPIRoadmap15:17
BobBallI do indeed15:17
johnthetubaguythanks15:17
*** mrunge has quit IRC15:17
*** Kharec has joined #openstack-meeting15:18
*** jcoufal has joined #openstack-meeting15:18
BobBallI don't have more15:18
BobBallas we said - much of it was discussed offline15:18
johnthetubaguyme neither15:18
johnthetubaguyare we all good for next week?15:18
matelsuresure15:18
*** sarob has quit IRC15:19
BobBallAlthough I'm not15:19
BobBallI'm on hodaliy15:19
BobBallholiday*15:19
BobBallI need one - hence the spelling.15:19
johnthetubaguyah, no worries, enjoy15:19
johnthetubaguyanything more before the summit?15:19
BobBallnah15:20
BobBallthink we're good15:20
johnthetubaguysweet15:20
johnthetubaguyhave a good day all15:20
*** danwent has joined #openstack-meeting15:20
BobBallyou too15:20
johnthetubaguysee you next week or in HK15:20
BobBallenjoy your flight!15:20
johnthetubaguyany you15:20
johnthetubaguylol15:20
johnthetubaguyand you15:20
johnthetubaguy#endmeeting15:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:20
openstackMeeting ended Wed Oct 23 15:20:46 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-10-23-15.03.html15:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-10-23-15.03.txt15:20
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-10-23-15.03.log.html15:20
*** kpepple has quit IRC15:23
*** zul has joined #openstack-meeting15:23
*** kpepple has joined #openstack-meeting15:25
*** akuznetsov has joined #openstack-meeting15:27
*** jamespage__ has joined #openstack-meeting15:28
*** akuznetsov has quit IRC15:28
*** Shaan7 has joined #openstack-meeting15:29
*** beekneemech is now known as bnemec15:30
*** jamespage__ has quit IRC15:30
*** vijendar has quit IRC15:31
*** jamespage_ has quit IRC15:31
*** akuznetsov has joined #openstack-meeting15:33
*** egallen has quit IRC15:34
*** johnthetubaguy has quit IRC15:35
*** egallen has joined #openstack-meeting15:36
*** egallen has quit IRC15:36
*** johnthetubaguy has joined #openstack-meeting15:36
*** rakhmerov has quit IRC15:36
*** rongze has quit IRC15:37
*** yaguang has joined #openstack-meeting15:37
*** egallen has joined #openstack-meeting15:37
*** markmcclain has joined #openstack-meeting15:39
*** kanabuchi has joined #openstack-meeting15:39
*** stevemar has quit IRC15:40
*** hemna has joined #openstack-meeting15:41
*** kanabuchi has quit IRC15:41
*** galstrom is now known as galstrom_zzz15:42
*** mrodden has joined #openstack-meeting15:45
*** mrunge has joined #openstack-meeting15:45
*** thomasbiege2 has quit IRC15:45
*** dcramer_ has joined #openstack-meeting15:46
*** jodom has quit IRC15:47
*** jrodom has joined #openstack-meeting15:47
*** egallen has quit IRC15:47
*** elo has quit IRC15:50
*** changbl has quit IRC15:50
*** ericyoung has joined #openstack-meeting15:50
*** SergeyLukjanov has joined #openstack-meeting15:51
*** SumitNaiksatam has quit IRC15:51
*** nermina has quit IRC15:53
*** egallen has joined #openstack-meeting15:53
*** egallen has quit IRC15:53
*** haomaiwang has quit IRC15:54
*** haomaiwang has joined #openstack-meeting15:54
*** Shaan7 has quit IRC15:54
*** markpeek has quit IRC15:55
*** xyang1 has joined #openstack-meeting15:58
*** thingee has joined #openstack-meeting15:58
*** joel-coffman has joined #openstack-meeting15:58
*** bswartz has joined #openstack-meeting15:58
*** jjacob512 has joined #openstack-meeting15:58
*** Shaan7 has joined #openstack-meeting15:59
*** haomaiwang has quit IRC15:59
*** jbernard has joined #openstack-meeting15:59
*** avishay has joined #openstack-meeting16:00
*** caitlin56 has joined #openstack-meeting16:01
*** hartsocks has joined #openstack-meeting16:01
jgriffith#startmeeting cinder16:01
openstackMeeting started Wed Oct 23 16:01:55 2013 UTC and is due to finish in 60 minutes.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: cinder)"16:01
openstackThe meeting name has been set to 'cinder'16:02
jgriffithHey everyone16:02
thingeeo/16:02
avishayhello16:02
jjacob512hello16:02
xyang1hi16:02
DuncanThey16:02
eharneyhey16:02
*** jrodom has quit IRC16:02
aguzikovao/16:02
jgriffithDuncanT: take it away...16:02
*** jrodom has joined #openstack-meeting16:02
jgriffith#topic nexenta backup driver16:02
*** openstack changes topic to "nexenta backup driver (Meeting topic: cinder)"16:02
DuncanThttps://review.openstack.org/#/c/47005/16:02
jgriffithDuncanT: and I have already discussed BTW :)16:02
med_\o16:02
DuncanTShort version: I think it's a terrible idea, a bad trend, and even if it wasn't then I think it's a bad implementation16:03
*** egallen has joined #openstack-meeting16:03
caitlin56Which patch specifically?16:03
bswartzhi16:03
DuncanTI'm happy to be convinsed otherwise however and I'm not going to get upset if people tell me I'm wrong16:03
avishaydon't be too subtle about how you feel :)16:03
dosaboy:)16:03
DuncanTcaitlin56: https://review.openstack.org/#/c/47005/16:04
*** egallen has quit IRC16:04
*** krtaylor has quit IRC16:04
*** winston-d has joined #openstack-meeting16:04
caitlin56Ok, this one should be short. I agree.16:04
DuncanTNice :-)16:04
jgriffithWell that was easy16:04
caitlin56The objectives are good, but we need to repackage them in a way that deals wsith Duncan's points.16:04
jgriffithcaitlin56: ummm... wait16:05
jgriffithcaitlin56: might be missing the point, not sure16:05
dosaboyand (while we're at it) could you make sure metadata backup is factored in16:05
jgriffithcaitlin56: which *objectives* exactly are good in your opinion?16:05
*** egallen has joined #openstack-meeting16:05
*** bill_az has joined #openstack-meeting16:05
caitlin56Using other servers to make replicas of your content in cost effective ways. Notice that I'm avoiding using the term "backup".16:06
avishaycaitlin56: what is the scenario?  tiering?16:07
*** rushiagr2 has joined #openstack-meeting16:07
rushiagr2hi all!16:07
rushiagr2sry, late16:07
*** rushiagr2 is now known as rushiagr16:07
jgriffithrushiagr: howdy16:07
avishaycaitlin56: i.e., copy the volume over and then delete it, and restore if you want to use again?16:07
*** rongze has joined #openstack-meeting16:07
DuncanTThat's fair. I think we need to get a clear aim around backup and keep it focused...16:07
*** DennyZhang has joined #openstack-meeting16:07
caitlin56Disaster recovery, warm standby, pre-migration.16:08
caitlin56I can replicate content between two like servers more effectively than I can create a vendor neutral "Backup".16:08
guitarzanI think it's sensible to have more than just the swift backup driver16:08
DuncanTBackend migration / cross-backend cloning is a better for this than backup I think16:08
avishayand here i am coding up a prototype of volume mirroring...16:08
DuncanTguitarzan: There#s already ceph and TSM...16:08
caitlin56avishay: or just copy it to other targets in case the first target fails.16:08
guitarzanDuncanT: I'll take that as a point for me :)16:08
*** egallen has quit IRC16:09
guitarzanbut this patch does seem to do a lot more than just that16:09
avishaycaitlin56: HA / DR16:09
caitlin56Volume mirroring is "hot standby", correct? Each write is *immediately* transferred?16:09
avishaycaitlin56: correct16:09
caitlin56This is lower cost, replicate periodically.16:09
avishaycaitlin56: actually, no16:09
caitlin56Not continuously.16:09
avishaycaitlin56: there can be sync, async, snapshots at intervals, etc.16:10
jgriffithOk... so questions16:10
jgriffithcaitlin56: Are you talking backup or replication?16:10
jgriffithcaitlin56: replication is not backup16:10
avishaybackup can be thought of as replication with high RPO :)16:10
caitlin56Replication can be a method of providing extra copies of a volume.16:10
jgriffithavishay: ewww16:10
caitlin56That is also the purpose of a "backup".16:11
jgriffithalright, I'm out16:11
avishaylol16:11
caitlin56Backup can also be vendor neutral, but at a cost that may be too high.16:11
avishayi didn't say i like it, but it's true16:11
avishayand people use it16:11
caitlin56vendor neutral backup is bettr, but it is also more expensive.16:11
jgriffithavishay: understood16:11
*** rpodolyaka has quit IRC16:12
DuncanTThe backup API is aimed at offline, cinder-can-catch-fire-and-your-data-is-safe style backups, and I'd like to try to keep that focus16:12
caitlin56We have NexentaStor customers who use ZFS send incremental replication to "backup" ZVols.16:12
jgriffithcaitlin56: so what's your point?16:12
caitlin56We want to be able to let them do the same thing under Cinder. The first draft didn't do it right.16:12
jgriffithcaitlin56: that's fine, lots of vendors do replication16:12
*** egallen has joined #openstack-meeting16:13
thingeeI keep seeing "hot" and "warm". Lets be clear that backups are cold.16:13
jgriffiththingee: +116:13
winston-dthingee: +116:13
thingeeif you're not doing that, you're not implementing something for the backup service.16:13
*** ygbo has joined #openstack-meeting16:13
jgriffithI really prefer to keep the contexts separate16:13
DuncanTthingee: +116:13
caitlin56thingee: agreed, so calling this a "Backup" was a mistake.16:13
bswartzI think there are more gray areas than people are admitting to16:13
avishayso what i will propose at the summit will allow back-ends (and front-ends) to implement replication however they want16:13
bswartzhot backups do exist -- for different reasons than cold backups do16:14
*** SumitNaiksatam has joined #openstack-meeting16:14
jgriffithbswartz: there are but we have a chance to make some definitions in Cidner and I think we should16:14
DuncanTI think havign a replication interface and API is great, I just don't want it merging into backups16:14
jgriffithDuncanT: +116:14
avishayDuncanT: agreed16:14
DuncanTjgriffith: +1 million16:14
jgriffithThat's my point16:14
jgriffithTBH I'm still a little leary on replication API's / interfaces in some sense16:15
bswartzYes I like the idea of drawing the lines in the sand -- just don't prentend that the reality is black and white16:15
winston-dso it's just a naming problem?16:15
*** dscannell has quit IRC16:15
caitlin56But I agree that we should use different terminology,and keep Ciner "Backups" vendor neutral.16:15
avishayi think the difference could be: if you write a bit and do nothing, and it gets copied eventually, it's replication.  if you have to click the 'backup' button, it's backup.16:15
jgriffithmost vendors are going to have their own replication options that are much better than anythign we're goign to do at a generic level16:15
med_+1 jgriffith16:15
jgriffithavishay: not a bad summary IMO16:15
*** rongze has quit IRC16:15
caitlin56avishay: but what if you have the script push the backup button for you? It's more of a continuum.16:15
*** yassine has quit IRC16:16
*** kartikaditya has joined #openstack-meeting16:16
avishaycaitlin56: i know, that's what i said before, but i agree with jgriffith - we should try to define a difference16:16
caitlin56I think the bigger difference is whether you are in vendor specific format.16:17
DuncanTcaitlin56: Come up with a specific usecase and we can discuss it... vague hypotheticals aren't going to help I don't think16:17
*** dscannell has joined #openstack-meeting16:17
caitlin56Backups should be vendor neutral. Replication can be vendor optimized.16:17
caitlin56DuncantT: I'm working on that presentation for Hong Kong.16:17
avishaymaybe ideally16:17
winston-dDuncanT: I haven't looked at backup code for quite a while, so is it possible to back one volume from back-end A up to back-end B now?16:18
*** IlyaE has quit IRC16:18
jgriffithwinston-d: nope16:18
DuncanT'vendor neutral' isn't a useful term here I don't think16:18
DuncanTwinston-d: Nope, and it isn't meant for that16:18
jgriffithwinston-d: we shelved that for avishay 's migration work16:18
*** w_dkehn has quit IRC16:18
jgriffithor that was my plan anyway16:18
DuncanT(what John said)16:18
caitlin56But that is the intent, correct? Otherwise why object to vendor specific "backup"?16:19
*** afazekas has quit IRC16:19
DuncanTBackup is aimed at cold, logically remote storage, and I'd like to keep that focus16:19
winston-dDuncanT: oh, right, that was a wrong question. i meant to ask if backup service can live standalone (not staying on the same host of vol service).16:19
DuncanTCeph could be thought of as a vendor, TSM certainly is16:19
*** jlibosva has quit IRC16:19
*** caitlin56 has quit IRC16:20
DuncanTwinston-d: I'm not sure that works for all drivers yet, but it is the aim and if you find cases that don't work, please file a bug16:20
dosaboywinston-d: to be clear (as mud?) you can backup  a volume created in any backend to any supported backup location16:20
*** caitlin56 has joined #openstack-meeting16:20
caitlin56Duncant: and since it is less frequent there is no reason for it not be in a vendor neutral format.16:20
*** rushiagr has quit IRC16:20
jgriffithdosaboy: +1, I've tested a few and works good thanks to your patch16:20
DuncanTcaitlin56: It is volume-backend neutral, if that is what you mean16:21
dosaboycool thanks16:21
*** Linz has quit IRC16:21
caitlin56DuncantT: yes.16:21
winston-ddosaboy: will take a look, thx for clarification16:21
DuncanTcaitlin56: Ah, yes, very much so, and that totally needs to stay16:21
avishayceph to ceph has special optimizations i think, but it should work for any backend16:22
caitlin56DuncanT: Fine, but lets add methods short of full live mirroring where customers can replicate content.16:22
DuncanTcaitlin56: Yup, I think the replication interface is the place for that, not the backup one16:22
caitlin56avishay: vendor optimizations on how stuff is creat3ed is fine.16:22
avishayagreed16:22
caitlin56agreed.16:23
jgriffithI'm still a bit of the opinion that replication is an admin function set up for each back-end external of cinder but whatever16:23
avishayall agreed?  we should save some arguments for the summit...will be boring otherwise... :)16:23
jgriffithavishay: ha!16:23
dosaboyisn't there a new "data protection" project being introduced in HK that aims to take care of replication?16:23
jgriffithavishay: haven't you heard, there's new rules for the summit16:23
dosaboythe name alludes me16:23
DuncanTjgriffith: An in-cinder api for setting replication parameters for a volume isn't a bad aim...16:23
jgriffithavishay: no raising of voices, no arguing, peace, harmony and love16:23
avishayjgriffith: sounds good to me16:24
jgriffithdosaboy: there's a backup service proposals16:24
winston-djgriffith: be 'excellent' ?16:24
avishaydosaboy: http://summit.openstack.org/cfp/details/8816:24
jgriffithproposal16:24
caitlin56dosaboy: any project that doesn'tintegrate with cinder volume backends won't beefficient enough to use.16:24
*** rushiagr has joined #openstack-meeting16:24
med_jgriffith, I was thinking boxing gloves and waterguns to cool off the hostilities16:24
DuncanTI'm going to throw a definition of'cinder backup' on the wiki somewhere while there are some good phrases to steal16:24
*** jungleboyj has joined #openstack-meeting16:25
jgriffithOk, anything else on this topic (anything productive that is)?16:26
* jungleboyj is here now. :-)16:26
jgriffithjungleboyj: just in time, we're finished :)16:26
jgriffithLOL16:26
jgriffithalright, DuncanT good for now?16:27
jungleboyjjgriffith: Doh!  What did I miss?  These darn short meetings!  ;-)16:27
*** anniec has joined #openstack-meeting16:27
DuncanTjgriffith: Very much so16:27
jgriffithcaitlin56: anything needed for the meeting?16:27
DuncanTjungleboyj: An impressive lack of argument for a change16:27
winston-dside track, how many of you will be in HK16:27
*** gkleiman has quit IRC16:27
* bswartz raises hand16:27
jgriffitho/16:28
avishayi will16:28
*** gkleiman_ has quit IRC16:28
guitarzano/16:28
DuncanTI will16:28
rushiagrI *most probably* will16:28
xyang1I'll be there16:28
caitlin56jgriffith: no,just gettingready for Hong Kong sessions.16:28
eharneyi will16:28
jungleboyjDuncanT: :-)  Indeed.16:28
winston-dbswartz: you should be right?16:28
bswartzyes NetApp is brining a bunch of folks to HK16:28
* med_ lowers his hand in shane16:28
jgriffith#topic open discssuion16:28
*** openstack changes topic to "open discssuion (Meeting topic: cinder)"16:28
* med_ lowers his hand in shame16:28
jgriffithshane, shame... not sure which is better/worse16:29
jgriffith:)16:29
* dosaboy might be, not sure yet16:29
* jungleboyj will be there in spirit. :-)16:29
kmartinnot me :(16:29
avishayso nobody is brave enough to try volume retype yet?16:29
bswartzdosaboy: it's only 1.5 weeks away!16:29
jgriffithdamn you kmartin16:29
winston-dkmartin: really? too bad16:29
jgriffithavishay: it's on my list :)16:29
jgriffithavishay: I'm hoping this week16:30
avishaycool16:30
* jgriffith is a bit preoccupied with other business this week16:30
winston-davishay: haven't reviewed it, not dare to try. :)16:30
rushiagravishay: I'll give it a try too in the comng week16:30
kmartinsending me to the AWS re:invent conference instead...yippy16:30
xyang1kmartin:  too bad:(16:30
avishayawesome16:30
dosaboybswrtz: i know ;)16:30
avishaykmartin: sucks, next time!16:30
*** suo has quit IRC16:30
kmartinyep, hemna is going to HK16:31
jgriffithalright.. we can jibber jabber in #cinder if there's nothign pressing here?16:31
jungleboyjI have a feeling this Iowa boy would have been lost in HK.16:31
winston-dhemnafk seems to prepared a big shopping list for HK16:31
jgriffithjungleboyj: :)16:31
hemnawell, sure a guy can always have a list :)16:31
avishayjgriffith: any update on the testing suite deal?16:31
xyang1kmartin: that's good16:31
*** jamespage_ has joined #openstack-meeting16:31
jgriffithavishay: :)  not really16:31
*** cdub_ has joined #openstack-meeting16:31
jgriffithavishay: it's on it's way though16:31
jgriffithwill be submitted before the summit I promise :)16:32
*** jamespage_ has quit IRC16:32
avishayjgriffith: HK summit? :)16:32
*** skolathu has joined #openstack-meeting16:32
jgriffithavishay: LOL touchet16:32
rushiagravishay: LOL16:32
med_heh16:32
med_"before the summit"  well played.16:32
winston-dohoh, Advertisement: please take a look at this doc if you are interested in QoS: https://docs.google.com/document/d/1_DEvlzXwOd3bQ4NqXmAS6gIdz0Lja6XJ1MZyNtYSicY/edit?usp=sharing16:33
winston-dand let me know if you have any comment. it's 90% ready. Will do some cleanup16:33
avishaywinston-d: will this go into openstack-manuals?16:33
jgriffithwinston-d: thanks for pointing that out16:33
kmartinwinston-d: +1 and thanks for all the work16:33
jgriffithalright.. .anyone else?16:33
bswartzwinston-d: nice document16:34
*** e-vad has quit IRC16:34
jgriffithlets wrap this up and move to #cinder16:34
avishaysounds good16:34
jgriffith#endmeeting16:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:34
openstackMeeting ended Wed Oct 23 16:34:25 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:34
*** markwash has quit IRC16:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-10-23-16.01.html16:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-10-23-16.01.txt16:34
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-10-23-16.01.log.html16:34
jgriffiththanks everyone!!16:34
*** avishay has left #openstack-meeting16:34
rushiagrthanks all!16:34
*** jungleboyj has left #openstack-meeting16:34
*** thingee has left #openstack-meeting16:35
*** caitlin56 has left #openstack-meeting16:35
*** zul has quit IRC16:35
*** comay has joined #openstack-meeting16:35
*** zul has joined #openstack-meeting16:36
*** kartikaditya has quit IRC16:36
winston-dwc16:37
*** winston-d has left #openstack-meeting16:37
*** jrodom has quit IRC16:37
*** BobBall has left #openstack-meeting16:37
*** egallen has quit IRC16:37
*** rushiagr has left #openstack-meeting16:38
*** Linz has joined #openstack-meeting16:38
*** ygbo has quit IRC16:38
*** nermina has joined #openstack-meeting16:39
*** cody-somerville has joined #openstack-meeting16:40
*** cody-somerville has quit IRC16:40
*** cody-somerville has joined #openstack-meeting16:40
*** blamar has quit IRC16:42
*** blamar has joined #openstack-meeting16:42
*** harlowja has joined #openstack-meeting16:43
*** rakhmerov has joined #openstack-meeting16:44
*** IlyaE has joined #openstack-meeting16:44
*** davidhadas_ has quit IRC16:44
*** Guest29531 is now known as thomasem16:46
*** sarvind has joined #openstack-meeting16:48
*** pauli1 has joined #openstack-meeting16:48
*** pauli1 has quit IRC16:49
*** marekd is now known as marekd|away16:50
*** yfujioka has joined #openstack-meeting16:52
*** jrodom has joined #openstack-meeting16:55
*** jrodom has quit IRC16:55
*** jrodom has joined #openstack-meeting16:55
*** IlyaE has quit IRC16:57
*** tjones has joined #openstack-meeting16:59
hartsocksgo-go-gadget meeting time17:00
tjoneshi17:00
*** twoputt has joined #openstack-meeting17:00
hartsocks#startmeeting VMwareAPI17:00
openstackMeeting started Wed Oct 23 17:00:12 2013 UTC and is due to finish in 60 minutes.  The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: VMwareAPI)"17:00
*** twoputt_ has joined #openstack-meeting17:00
openstackThe meeting name has been set to 'vmwareapi'17:00
hartsockshi all17:00
hartsocksI'm back.17:00
hartsocksDid you miss me?17:00
hartsocksRaise a hand if you did :-)17:00
tjonesI DID!!!17:00
hartsocks*lol*17:00
tjones:-D17:01
*** derekh has quit IRC17:01
hartsocksI'm still reading my old emails but I'm reading from newest to oldest so if there's something you need me to help on, please re-send… it'll get taken care of sooner (and perhaps twice even).17:01
*** jodom has joined #openstack-meeting17:02
*** jodom has quit IRC17:02
hartsocksOne time I actually read all my emails and I didn't know what to do.17:02
*** jodom has joined #openstack-meeting17:02
*** jrodom has quit IRC17:02
*** cody-somerville has quit IRC17:02
hartsocksThen the problem went away.17:02
*** DennyZhang has quit IRC17:02
hartsocksVui said he'd be online later so we might see him.17:03
hartsocksAnybody else around?17:03
sarvindsarvind ; I'm here. first time for the irc meeting17:03
tjoneswelcome sarvind17:04
tjonesi may start calling you that face to face ;-)17:04
hartsocks*lol*17:05
hartsocksWell, let's get rolling then...17:06
hartsocks#topic bugs17:06
*** openstack changes topic to "bugs (Meeting topic: VMwareAPI)"17:06
hartsocks#link http://goo.gl/uD7VDR17:06
hartsockshere's a query on launchpad that combs for open bugs … new , in progress, etc.17:07
*** xyang1 has left #openstack-meeting17:08
*** eglynn has quit IRC17:08
hartsocksWe have a few that's popped up since last week.17:08
hartsocksLooks like 5 or so.17:08
*** smurugesan has joined #openstack-meeting17:08
hartsocksThis one troubles me...17:09
smurugesanThis is sabari here. Hi All.17:09
hartsocks#link https://bugs.launchpad.net/nova/+bug/124135017:09
uvirtbotLaunchpad bug 1241350 in nova "VMware: Detaching a volume from an instance also deletes the volume's backing vmdk" [Undecided,In progress]17:09
hartsockshey sabari!17:09
*** gyee has joined #openstack-meeting17:09
*** danflorea has joined #openstack-meeting17:09
danwenthi folks, garyk says he is having technical issues with his irc client17:10
hartsocksokay.17:10
tjoneslooks like that is out for review17:10
danwent(he let me know via skype, apparently a more reliable channel)17:10
sarvindi'd trouble with the irc client as well switched to the webchat for now17:10
*** skolathu has quit IRC17:10
hartsocksokay.17:11
*** garyk has joined #openstack-meeting17:11
garykhi17:11
hartsocksMy plan for today is just to hit bugs, then blueprints, then HK summit stuff.17:11
*** akuznetsov has quit IRC17:11
hartsocksHey gary.17:11
hartsocksWe were just talking about #link https://bugs.launchpad.net/nova/+bug/124135017:11
uvirtbotLaunchpad bug 1241350 in nova "VMware: Detaching a volume from an instance also deletes the volume's backing vmdk" [Undecided,In progress]17:11
garykthat is a critical issue - hopefully we can get it backported asap17:12
tjonesjay has it out for review17:12
*** rongze has joined #openstack-meeting17:12
garykthere are some minor issues with test cases. but nothing blocking17:12
hartsocksokay good.17:13
hartsocks#link https://bugs.launchpad.net/nova/+bug/124322217:13
uvirtbotLaunchpad bug 1243222 in nova "VMware: Detach leaves volume in inconsistent state" [Undecided,New]17:13
garyki am currently working on that17:14
hartsocksOkay.17:14
garykit is when a snaptshot takes place on the instance17:14
*** lbragstad has quit IRC17:14
hartsocksyou've confirmed it then?17:14
garykconfirmed the bug?17:15
hartsocksyes. So it can be marked "confirmed" not "new" or something else?17:15
*** markwash has joined #openstack-meeting17:15
garyki'll mark it as confirmed17:16
hartsocksgroovy.17:16
danwentgaryk: ok, so that only happens when a snapshot is done?17:16
*** rongze has quit IRC17:16
danwentthe title does not indicate that anywhere, making it sound much larger :)17:17
hartsocksheh. good point.17:17
*** shakayumi has quit IRC17:17
*** lbragstad has joined #openstack-meeting17:17
*** johnthetubaguy has quit IRC17:17
garykthe issues is as follows: when we do a snapshot we ready the disk from the hardware summary. problem is that due to tge fact that there are 2 disks we do not read the right disk17:17
garykthis causes us to snapshot the cinder disk instead of the nova disk.17:17
danwentwe seem to have a problem with that in general, giving bugs very general titles that make things seem very broken17:17
*** vito-ordaz has joined #openstack-meeting17:17
garykdanwent: correct. we need to work on our descriptions17:18
hartsocksI've edited the title to describe step 4 in the repro steps.17:18
danwentok, i'll send a note to the list just to remind people about this17:18
tjonesdanwent: we went to keep you on your toes17:18
hartsocks*lol* what's wrong with: "broken-ness all things happen bad" ?17:18
danwenttjones: or the hospital?  i almost had a heart attack when i saw that17:19
*** yogeshmehra has joined #openstack-meeting17:19
*** jcoufal has quit IRC17:19
hartsocksI see things like that and I usually say, "yeah right"17:19
tjones:-P17:19
tjonesgaryk: did this break in tempest or do we need to add more tests?17:20
danwentor wait, that's a different bug than I thought we were talking about17:20
danwentone sec17:20
*** RajeshMohan has joined #openstack-meeting17:20
garyktjones: i do not think that this is covered in tempest - if it is, it does not really check the validiaty of the disks17:20
hartsocksThis is a good point...17:21
*** vijendar has joined #openstack-meeting17:21
garykdanwent: there are 2 bugs which are very closely related - they may even be the same17:21
danwenthttps://bugs.launchpad.net/nova/+bug/124135017:21
uvirtbotLaunchpad bug 1241350 in nova "VMware: Detaching a volume from an instance also deletes the volume's backing vmdk" [High,In progress]17:21
*** SergeyLukjanov has quit IRC17:21
danwentis the one i saw17:21
hartsocksyeah.17:21
hartsocksThat was top of my list too.17:21
garykthat bug already has a patch upstream. that is a blocker17:22
garykwe have discussed hat a few minutes ago17:22
danwenti'm confused, does this mean any use of volumes is broken?17:22
garykdanwent: something changed as this is a screio that we have done a million times17:23
garyki am not sure if it is in cinder. nothing on our side was chnaged here (we also have this in a lab)17:23
danwentyeah, that is my sense too.17:23
hartsocksslow down guys.17:23
*** Mandell has joined #openstack-meeting17:23
hartsocksThis looks like more bad naming confusion here.17:23
hartsocksIf I'm reading this line right...17:24
*** bswartz has left #openstack-meeting17:24
hartsockshttps://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/vm_util.py#L47117:24
garyki think that subbu and kartik were looking deeepr at the status of the disk and that may have highlighted the problem17:24
hartsocksassuming the bug reporter was linking correctly… this means the17:24
garykhartsocks: that is what the fix addresses17:24
garykthere are two cases17:24
garyk1. a consolidated disk needs to be deleted17:24
hartsocksnova volume-detach17:24
hartsockscalls the delete volume code17:24
garyk2. a detachment does not need to be deleted17:24
danwentone at a time please :)17:25
hartsocksdef delete_virtual_disk_spec(17:25
hartsockswhich is not the right thing to do.17:25
hartsocksSince deleting is not detaching.17:25
hartsocksSo.17:25
hartsocksI'm saying:17:25
hartsocksdelete is not detatch.17:25
garykplease look at https://review.openstack.org/#/c/52645/17:25
hartsocksgreat.17:26
*** shakayumi has joined #openstack-meeting17:26
hartsocksI was scared there for a second.17:26
danwentok, so we can we up a level and talk about impact on customer?17:26
hartsocksSo the impact.17:26
hartsockscan only be on17:26
hartsocksthe nova created vmdk right?17:27
hartsocksthis can't be bleeding into cinder somehow?17:27
garykhartsocks: danwent: no the problem is the cinder volume17:27
garykthe 'detachment' 'deletes' the cinder volume.17:27
garykdue to the fact that it is attached to a empty vm it will not be deleted but may turn into read only17:28
garykso it the case is we have instance X17:28
garykthat uses volume Y17:28
garykand we write to Y17:28
garykthe detach17:28
*** aepifanov has joined #openstack-meeting17:28
garykand attach to instance Z tehn we can read what was written by X but not may be able to write again17:29
garyksorry for the piece meal of comments - eb client is hard and my irc client is broken17:29
danwentwell, the bug says that the actually re-attach fails17:29
danwentnot that it succeeds, but the volume is read-only17:30
hartsocksin my book, that means we haven't really confirmed this bug.17:30
garykhartsocks: subbu and kartik have confimed this and i have tested the patch17:30
danwentgaryk: confirmed what behavior?   what is written in the bug (second attach fails) or what you mentioned (second attach works, but read-only)17:31
hartsocksI have no doubt you've found *a* bug and fixed it.17:31
*** thomasem has quit IRC17:31
garykdanwent: i think that they have confirmed what is written in the bug. i am not 100% sure, but I discussed this with them17:32
danwentok… well, i guess one thing that is different in the bug from what I personally have tested is that I've never tried to immediately re-attach a volume to the same VM, we always booted another VM and attached the volume to that vms17:33
garykdanwent: my understaning, and i may be wrong, or confused, most likely the latter, is that the disk could become read only when we do something like a delete or a snapshot and it is owned by someone else17:33
*** comay has quit IRC17:34
garykdanwent: that is the scenrio that i always tested17:34
*** lblanchard has quit IRC17:34
*** davidhadas has joined #openstack-meeting17:35
danwentok, i don't totally follow on the read-only part, I'm just trying to understand how pervasive the bug is, as the write-up makes it sound like any volume that is detached is deleted and can never be attached to another VM, which means the whole point of volumes is in question.17:35
danwentbut that seems to contract what we've tested.17:36
danwentcontradict17:36
garykdanwent: i'll forllow up with subbu and kartik and get all of the details so that we can paint a better picture17:36
danwentok, thanks, yeah, don't need to take up the whole meeting, but this does seem pretty important17:36
garykhartsocks: you can action item that for me17:36
danfloreaI agree. We need to know if we should say "don't snapshot when you have Cinder volumes attached" or "don't use our Cinder driver"17:36
garykyeah i concur it is very importnat17:36
hartsocks#action garyk follow up on https://bugs.launchpad.net/nova/+bug/1241350 and narrow scope/descriptions17:37
uvirtbotLaunchpad bug 1241350 in nova "VMware: Detaching a volume from an instance also deletes the volume's backing vmdk" [High,In progress]17:37
hartsocksWhich brings me to...17:37
hartsocks#link https://bugs.launchpad.net/nova/+bug/124319317:37
uvirtbotLaunchpad bug 1243193 in nova "VMware: snapshot backs up wrong disk when instance is attached to volume" [Undecided,New]17:37
hartsockswhich seems related.17:38
garykhartsocks: i am currently debugging this17:38
hartsocks(if only by subject matter)17:38
garykthis is related to https://bugs.launchpad.net/nova/+bug/124322217:38
uvirtbotLaunchpad bug 1243222 in nova "VMware: Detach after snapshot leaves volume in inconsistent state" [Undecided,Confirmed]17:38
hartsocksyeah, glad you're on it.17:39
garyki need a stiff drink17:39
hartsocksputting your name on the bug so I don't accidentally try to pick it up.17:39
*** galstrom_zzz is now known as galstrom17:39
*** neelashah has quit IRC17:40
hartsocksWho's ever in HK should buy Gary a round.17:40
tjonesgaryk: at least its late enough for you to do just hat17:40
*** SergeyLukjanov has joined #openstack-meeting17:40
tjonesthat17:40
garyk:)17:40
hartsocksa hat full of vodka.17:40
hartsocks:-)17:40
tjones:-D17:41
hartsocksany other pressing things?17:41
hartsocks(on the topic of bugs that is)17:41
*** reed has joined #openstack-meeting17:41
hartsocksanyone look at #link https://bugs.launchpad.net/nova/+bug/124035517:42
uvirtbotLaunchpad bug 1240355 in nova "Broken pipe error when copying image from glance to vSphere" [Undecided,New]17:42
hartsocksThat seems like someone with a screwy setup more than anything.17:43
hartsocksOkay.17:43
smurugesanI think this is related to the bug Tracy is working on . let me pull it up17:43
garyki have seen that on a number of occasions. have never been able to debug it17:43
*** vijendar has quit IRC17:44
hartsockshmm… so maybe not just a screwy set up (I've never seen this)17:44
smurugesanCould this be because the vmdk descriptor file exists but not the flat-file.17:44
garyki actually think that it happens when the image is copied to the vc - i do not think that devtsack uses ssl between nova and glance17:44
*** vijendar has joined #openstack-meeting17:44
garyki see it once every few days using a vanilla devstack installation with the debian instance17:45
hartsocksReally?!?17:45
*** beyounn has joined #openstack-meeting17:45
tjonesodd i have never sen it17:46
garyki am not sure if a packet is discarded or corrupted. but it is a tcp session so it should be retransmitted17:46
hartsocksThat error looks to me like a transient networking failure.17:46
hartsocksYes. TCP should cover retransmit of the occasional packet loss.17:46
garykmy thinking is that the current connection is terminated and a new session witht he vc is started. the file download is not restarted... but then again i have not been able to reproduce to be able to say for sure17:47
hartsocksHmmm…17:47
hartsocksWhen we transfer to the datastores...17:48
hartsocksare we using the HTTP "rest" like interfaces?17:48
hartsocksI don't recall… I suppose we would have to.17:48
hartsocksI recall that there is a problem with session time-outs between the two forms of connections.17:49
hartsocksThe vanilla HTTP connection used for large file transfer...17:49
hartsocksand the SOAP connection have different sessions.17:49
hartsocksOne can time out and the other can still be active.17:49
hartsocksThis would tend to happen on long running large file transfers.17:49
hartsocksIs that what you've seen Gary?17:50
garyki have just seen the exception. have not delved any deeper than that17:50
*** comay has joined #openstack-meeting17:50
garyki'll try and run tcp dump and see if it reprodues. this may crystalize your theory17:51
danfloreaIt would be good to know if this is isolated to one testbed or if we see it in multiple. If it's the latter, it's less likely that this is just a network/setup issue.17:51
danfloreaPayPal in particular has big image files and is sensitive to failures like this so definitely worth investigating.17:52
garykboth ryand and i have seen this. only thing in common is that we use the same cloud17:52
tjonesgark: you said it was with the debian image?17:52
garyktjones: yes17:53
hartsocksDoes the transfer ever take more than 30 minutes?17:53
tjonesthat's only 1G17:53
*** thomasm has joined #openstack-meeting17:53
*** thomasm is now known as Guest8172117:54
*** Guest81721 is now known as thomasem17:54
garyknope, it is usually a few seconds, maybe a minute at most17:54
*** galstrom is now known as galstrom_zzz17:54
*** neelashah has joined #openstack-meeting17:54
hartsocksOkay. That doesn't support my theory at all.17:54
*** IlyaE has joined #openstack-meeting17:54
hartsocksHmm… who should look at this?17:55
garyki am bigged donw in the disk and datastores17:55
tjonesIf ryan can show me what he does i can take a look17:55
tjonesyeah garyk has enough ;-)17:55
garykbogged not bigged17:55
hartsockstotally.17:55
hartsockswhy not both?17:56
tjonesbugged17:56
garyknah, not bugged.17:56
tjonesat least i can put some debugging in there so we can catch it more easily if i cannot repo17:56
hartsocksokay.17:57
hartsocks#action tjones to follow up on https://bugs.launchpad.net/nova/+bug/124035517:57
uvirtbotLaunchpad bug 1240355 in nova "Broken pipe error when copying image from glance to vSphere" [Undecided,New]17:57
hartsocksWe spent most of the meeting on bugs.17:57
hartsocks#topic open discussion17:57
*** openstack changes topic to "open discussion (Meeting topic: VMwareAPI)"17:57
hartsocksAnything else pressing we need to talk about?17:58
danfloreaJust one request. Please review upstream Nova driver & Cinder driver docs :)17:58
tjones:-D17:58
danfloreaNova driver patch: https://review.openstack.org/#/c/51756/17:58
danfloreaCinder driver doc is already merged. But send me comments if you have any and I can update that one too.17:59
hartsocks#action everyone give some review love to upstream nova driver and cinder docs!17:59
hartsocksSo we're out of time.17:59
tjonesadios17:59
hartsocksThanks for the turn out today.17:59
danfloreabye17:59
hartsocksWe're on #openstack-vmware just hangin' out if anyone needs to chat.18:00
*** danflorea has quit IRC18:00
hartsocks#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Wed Oct 23 18:00:13 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-10-23-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-10-23-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-10-23-17.00.log.html18:00
SumitNaiksatamHi Neutron folks18:00
SumitNaiksatamFWaaS meeting to start18:00
*** SridarK has joined #openstack-meeting18:01
garykhi18:01
*** sarvind has quit IRC18:01
SumitNaiksatamSridarK: hi18:01
SridarKHi18:01
SumitNaiksatamgaryk: hi18:01
SumitNaiksatambeyounn: there?18:01
*** jjacob512 has quit IRC18:02
SumitNaiksatamok lets get started with whoever is around18:02
SumitNaiksatam#startmeeting Networking FWaaS18:02
openstackMeeting started Wed Oct 23 18:02:36 2013 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:02
openstackThe meeting name has been set to 'networking_fwaas'18:02
SumitNaiksatamWelcome to the Firewall as a Service (FWaaS) meeting!18:03
SumitNaiksatamtoday's meeting is also in preparation for the Icehouse summit discussions/sessions18:03
SumitNaiksatam#info etherpad: https://etherpad.openstack.org/p/icehouse-neutron-fwaas18:03
SumitNaiksatam#topic tempest18:03
*** openstack changes topic to "tempest (Meeting topic: Networking FWaaS)"18:03
SumitNaiksatamI have created a place holder blueprint18:04
SumitNaiksatam#link https://blueprints.launchpad.net/tempest/+spec/fwaas-api-tempest18:04
SumitNaiksatamI also had an action item last week to check with Salvatore, but I did not get a chance to catch him and he is on vacation this week18:04
SumitNaiksatamhave pinged him though18:04
SumitNaiksatamif anyone has any input/thoughts on this, happy to spend a few minutes on this topic here18:04
*** ivar-lazzaro has joined #openstack-meeting18:05
*** Kaiwei has joined #openstack-meeting18:05
SumitNaiksatamseems like folks are still joining18:05
*** anand has joined #openstack-meeting18:05
SumitNaiksatamfor folks just joining in, we are discussing tempest tests for FWaaS18:05
SumitNaiksatami have posted a placeholder blueprint18:06
SumitNaiksatamthe idea is to at least test the basic API for the fwaas resources18:06
SumitNaiksatamanyone has more thoughts/input on this?18:06
*** stevemar has joined #openstack-meeting18:07
SumitNaiksatamokay, so will try to prioritize this at least with the ideas we have18:07
*** garyduan has joined #openstack-meeting18:07
SumitNaiksatammoving to the next topic18:07
SumitNaiksatam#topic zones18:07
*** openstack changes topic to "zones (Meeting topic: Networking FWaaS)"18:07
*** SergeyLukjanov has quit IRC18:07
SumitNaiksatameveryone's favorite topic :-)18:07
SridarK:-)18:07
SumitNaiksatamthis was another action item for me18:08
*** whenry has joined #openstack-meeting18:08
garyduanRight18:08
SumitNaiksatamI was supposed to send a email to the mailer with a proposal18:08
SumitNaiksatamwe had discussions with some team members on this, and based on that I sent out the proposal18:08
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-zones-api18:08
SumitNaiksatamcurrently this is pretty simplistic, hoping to get some input18:08
SumitNaiksatamfolks had a chance to think about this?18:08
SridarKI think this captures it at a high level18:09
*** shakayumi has quit IRC18:09
SumitNaiksatamSridarK: okay18:09
SridarKwe can work thru some of the specifics over next week18:09
SumitNaiksatamone thing we realized is that we cant use zones for all scenarios18:09
SumitNaiksatamSridarK: right18:09
SridarKso we have something more tangible b4 summit18:09
*** m__ has joined #openstack-meeting18:09
garyduanSumitNaiksatam: we'd like to help or on other FW objects18:09
*** markpeek has joined #openstack-meeting18:09
SumitNaiksatamfor instance, the zones don't work for bump in the wire scenarios18:09
SridarKyes true that was  a good discussion18:10
SumitNaiksatamgaryduan: sure, that is coming up in the agenda18:10
SumitNaiksatamgaryduan: you mean pitch in for zones as well?18:10
SridarKi think if we cover some of the basic common cases and have it generic so works for all18:10
SumitNaiksatamSridarK: makes sense18:10
*** btorresgil has joined #openstack-meeting18:10
SumitNaiksatammore thoughts on the definition of zones?18:11
garyduanSumitNaiksatam: We can share workload.18:11
SumitNaiksatamgaryduan: definitely, we can decide how to split up18:11
SridarKsounds good to me too18:11
SumitNaiksatamlets first firm up on the proposal18:11
*** pauli1 has joined #openstack-meeting18:11
SridarKhow abt we target that for the next IRC18:12
SridarKto have some more details added to the BP18:12
SumitNaiksatamwe will add source/destination arguments to the rule to be able to specify zones18:12
SumitNaiksatamSridarK: yeah we can do that18:12
*** sarob has joined #openstack-meeting18:12
*** arosen_ has joined #openstack-meeting18:12
SumitNaiksatamSridarK: lets also factor in the summit dynamics18:12
*** sarob has quit IRC18:12
*** rongze has joined #openstack-meeting18:13
*** btorresgil is now known as BrianTorres-Gil18:13
SridarKSumitNaiksatam: agreed18:13
SumitNaiksatamokay seems like everyone is happy with the current state of discussion on zones18:13
SumitNaiksatamwe will keep working on it18:13
SumitNaiksatamnext topic18:13
beyounnwait18:13
*** SergeyLukjanov has joined #openstack-meeting18:13
beyounn:-)18:13
SumitNaiksatambeyounn: sure go ahead18:13
*** jjacob512 has joined #openstack-meeting18:13
beyounnthe vlan support is still up in the air18:13
SumitNaiksatamah ok18:14
beyounnand there is another bp about this18:14
beyounnhttps://docs.google.com/document/d/1WEGmMJ4Vn21trgwa2_mpQ7U_a1BV2rKxlRzHqc49-9Y/edit18:14
SridarKbeyounn: i am also talking to Kyle today evening18:14
SumitNaiksatami was kind of thinking of that as implementation detail18:14
SumitNaiksatambut good to point out18:14
SumitNaiksatamSridarK: thanks18:14
beyounnok18:14
beyounnjust want to put all the info together18:14
beyounnnow, I'm done18:14
SumitNaiksatam#action SridarK and beyounn to continue following up on trunk port blueprint, and any additional blueprints that need to be created18:14
SridarKok sounds good18:15
beyounnok18:15
SumitNaiksatambeyounn: do you want to discuss it here?18:15
SumitNaiksatamnot sure if kyle is around18:15
SumitNaiksatammestery: there?18:15
beyounnok, let's do it offline then18:15
SridarKWe are all in a mtg now18:15
SumitNaiksatamok lets do it offline18:15
SumitNaiksatamSridarK: got it18:15
mesterySumitNaiksatam: Barely. :) In a meeting18:16
SridarKso we can pick it up offline18:16
beyounnright18:16
SumitNaiksatammestery: okay np, we discuss offline18:16
SumitNaiksatamnext topic18:16
SumitNaiksatam#topic Address Objects18:16
*** openstack changes topic to "Address Objects (Meeting topic: Networking FWaaS)"18:16
SumitNaiksatamwe were earlier planning an IP Object resource to model static and dynamic IP objects18:16
SumitNaiksatamthe proposal is to evolve this to generic "address" objects18:16
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-address-objects18:16
SumitNaiksatamwe will first target static IP objects18:17
*** rongze has quit IRC18:17
Kaiweisorry, I just checked the blueprint for the zones and I'm not sure if using ports as zones actually capture the idea of "zones"18:17
SumitNaiksatamKaiwei: can you hold that thought, we just moved past that topic18:17
SumitNaiksatamwe can circle back to zones18:17
Kaiweisure18:17
*** Mandell has quit IRC18:18
SumitNaiksatam#action SumitNaiksatam to followup on Kaiwei regarding zones if we don't get it to it by the end of the meeting18:18
SumitNaiksatamcoming back to address objects18:18
*** dims has quit IRC18:18
*** dims has joined #openstack-meeting18:19
*** ativelkov has quit IRC18:19
SumitNaiksatameveryone fine with IP address object being a subnet or list/range of ip addresses?18:19
SumitNaiksatamthis is the "static" ip address object18:19
beyounnright18:19
*** eglynn has joined #openstack-meeting18:19
Kaiweihow about CIDR?18:19
Kaiweioh, that's a subnet18:20
SumitNaiksatamKaiwei: okay, i was thinking CIDR when i meant subnet18:20
Kaiweimiss that part18:20
SumitNaiksatamKaiwei: yeah :-)18:20
SumitNaiksatamKaiwei: but that is a good point18:20
KaiweiI guess that includes a list of subnets as well18:20
SumitNaiksatamwhen i was thinking subnets i was thinking neutron subnets18:20
SumitNaiksatammaybe there is a case for a super net or something like that18:21
Kaiweiso the subnet is actually a subnet UUID?18:21
SumitNaiksatamKaiwei: that was my initial thought18:21
SumitNaiksatamit helps in validation18:21
SumitNaiksatamUUID or name18:22
KaiweiI'm fine with that...but having CIDR is more flexible18:22
SumitNaiksatamalso easier for the user to specify18:22
SumitNaiksatamKaiwei: i guess we can have both18:22
Kaiweithat will be great18:22
SumitNaiksatameither you can specify the actual CIDR, or the subnet UUID/name18:22
SumitNaiksatamperhaps more usable that way18:22
BrianTorres-GilAgreed, both would be helpful.18:23
SridarKSumitNaiksatam: Since CIDR can cover all cases - should we support both ?18:23
SumitNaiksatam#action SumitNaiksatam to update address object blueprint, add CIDR18:23
*** sushils has quit IRC18:23
SumitNaiksatamSridarK: CIDR would cover18:23
SridarKjust a thought to make it simpler18:23
SumitNaiksatambut providing a reference to neutron resource (subnet) in this case makes a little easier for users18:23
SumitNaiksatamSridarK: we can discuss as follow up18:24
SumitNaiksatamnext topic18:24
SridarKok sounds good - i agree18:24
SumitNaiksatamKaiwei: btw, anything more on address objects?18:24
SumitNaiksatambefore i move on ;-)18:24
*** m__ has quit IRC18:24
*** Mandell has joined #openstack-meeting18:25
*** ericyoung has quit IRC18:25
Kaiweinope, just want to make sure a list of subnets/CIDR is supported as well18:25
SumitNaiksatamokay great18:25
SumitNaiksatam#topic Counters18:25
*** openstack changes topic to "Counters (Meeting topic: Networking FWaaS)"18:25
SumitNaiksatamcouple of blueprints have been proposed18:25
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-counters-api18:25
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/firewall-hitcounts18:25
SumitNaiksatamthe proposal is to pull the counters from the driver, FWaaS DB will not persist any of these18:25
SumitNaiksatamthis will be a separate API from the firewall_rules API (each rule will be identified based on rule_id and firewall_id)18:25
SumitNaiksatamwe still need to define what to report18:27
SumitNaiksatami guess the set of what IP tables reports is a must18:27
SumitNaiksatamaccept, deny18:27
KaiweiI think Salvatore mentioned in last week's meeting that pull the counters directly from driver every time a query is issued can put a lot stress on backend....18:28
SumitNaiksatamKaiwei: I don't think that was what he was suggesting18:28
*** asalkeld is now known as asalkeld_eating18:29
SumitNaiksatami believe what he was suggesting is that we should not continuously update counters in the FWaaS DB18:29
garyduanKaiwei: My understanding is updating database is too costy18:29
SumitNaiksatamgaryduan: right18:29
*** armax has joined #openstack-meeting18:30
SumitNaiksatamKaiwei: also, periodic update of counters will get give stale values, not of much use18:30
BrianTorres-GilPerhaps this is too implementation specific, but what if there are multiple firewalls with the rule.  Is the counter the sum of the counts on each firewall?18:30
Kaiweiok, probably my misunderstanding18:31
SumitNaiksatamBrianTorres-Gil: we want to pull the counters based on rule_id and firewall_is18:31
SumitNaiksatamfirewall_id18:31
SumitNaiksatami would prefer to leave the aggregation to another extension18:31
SumitNaiksatamthoughts?18:32
BrianTorres-Gilok, so counter is per rule and per firewall.18:32
SumitNaiksatamBrianTorres-Gil: that is the current proposal18:32
*** e-vad has joined #openstack-meeting18:32
SumitNaiksatamwe would like to enable the "elemental" API18:32
SumitNaiksatamBrianTorres-Gil: perhaps we can make firewall_id optional18:33
*** chandankumar_ has joined #openstack-meeting18:33
SumitNaiksatamso if firewall_id is not present, then its an aggregation18:33
SumitNaiksatamthat said I am worried about supporting this aggregation in the reference implementation18:34
SridarKand this is completely driven by the vendor implementation18:34
*** lblanchard has joined #openstack-meeting18:34
SumitNaiksatamSridarK: that is true, but if we say firewall_id is optional, the reference implementation will have to support aggregation across firewalls18:34
SridarKSumitNaiksatam: supporting on the reference would be a stretch18:35
*** thomasem has quit IRC18:35
SridarKwe can keep it simple18:35
SumitNaiksatamSridarK: yeah, thats my concern :-)18:35
SumitNaiksatamok lets think a little more how we can handle both scenarios (and not have to support in the reference impl)18:36
SumitNaiksatam#action BrianTorres-Gil SumitNaiksatam SridarK to sync up on aggregate counters18:36
SumitNaiksatamany other thoughts?18:36
Kaiweione question18:36
SumitNaiksatamKaiwei: go ahead18:36
SridarKcould whether it is optional or not be vendor specific ?18:36
Kaiweiwill a rule be shared by multiple firewall policies in icehouse?18:37
SumitNaiksatamKaiwei: not in multiple policies18:37
*** markpeek has quit IRC18:37
SumitNaiksatambut the policy can be shared in multiple firewalls18:37
SumitNaiksatamKaiwei: this is also a part of the commit operation discussion18:37
SumitNaiksatami have it on the agenda if we have time18:37
Kaiweiok, so the aggregation is on one rule applied to multiple firewall?18:38
SumitNaiksatamKaiwei: yeah, that's what BrianTorres-Gil is referring to18:38
Kaiweigot it18:38
SumitNaiksatamSridarK: yeah, to your question, yeah lets think more on this18:39
SumitNaiksatamnext topic18:39
SumitNaiksatam#topic Service Objects18:39
*** openstack changes topic to "Service Objects (Meeting topic: Networking FWaaS)"18:39
SridarKok18:39
SumitNaiksatamproposal is to capture protocol, port, and timeout18:39
SumitNaiksatamthis can be used for source, and destination in a firewall_rule18:39
*** chandankumar_ has quit IRC18:39
beyounnthe port can be a range18:39
Kaiweiwhat timeout is about?18:39
SumitNaiksatambeyounn: ok18:40
*** harlowja has quit IRC18:40
SumitNaiksatambeyounn: over to you :-)18:40
SumitNaiksatamKaiwei's question18:40
beyounnThe service timeout is used to control a session the life time18:40
*** dprince has quit IRC18:40
beyounnyou can define a service witha timeout and bind the service to a policy18:40
*** thomasem has joined #openstack-meeting18:40
beyounnwhen a session hits on the policy, session inherit the timeout value from service def18:41
*** shakayumi has joined #openstack-meeting18:42
SumitNaiksatambeyounn: so you mentioned you wanted to put a blueprint for this?18:42
Kaiweigot it,,,,just wondering how many venders have this kind of support....18:42
beyounnSure18:42
beyounnor, if you want to create it, I can filling detail later18:42
SumitNaiksatamKaiwei: it seems some vendors are supporting this18:42
beyounnKaiwei: juniper and us18:43
SumitNaiksatamKaiwei: but we don't have to make this a required field18:43
SumitNaiksatamit should be optional18:43
Kaiweisure18:43
SumitNaiksatambeyounn: agree?18:43
beyounnIyes18:43
SumitNaiksatamok18:43
SumitNaiksatam#action beyounn to file service objects blueprint18:43
SumitNaiksatamBrianTorres-Gil: you have thoughts on this?18:44
KaiweiAlso, I think we should we have one service per rule, instead of two per rule18:44
SumitNaiksatamKaiwei: can you explain?18:44
Kaiweiyou mentioned we need to have service objects for source and destination18:45
SumitNaiksatamah ok18:45
Kaiweibut the protocol/timeout...etc will be same, only port will be different18:45
SumitNaiksatamKaiwei: ok18:45
*** markpeek has joined #openstack-meeting18:45
*** novas0x2a|laptop has joined #openstack-meeting18:45
Kaiweiso I think one service object which include src port and dst port should be sufficient18:45
beyounnyes18:45
BrianTorres-GilIn the service objects seems a strange place to put a timeout, I would connect a timeout more with a rule.  But this is implemented differently in each vendor so hard to say what works best for everyone.18:46
SumitNaiksatamKaiwei: so you are saying rather than use source/destination for this, we have a new attribute for service18:46
Kaiweiyes18:46
beyounnlet me give a short list18:46
beyounnin a service object, we can have:18:46
*** markpeek has quit IRC18:46
*** elo has joined #openstack-meeting18:46
*** markpeek has joined #openstack-meeting18:47
*** terriyu has quit IRC18:47
beyounnname, proto, port (or port range), timeout18:47
beyounnthe ports are source and dest18:47
SumitNaiksatamproto and port are mandatory?18:47
*** nati_ueno has joined #openstack-meeting18:47
SumitNaiksatami would assume they are18:47
KaiweiI think proto/port are optional....18:48
beyounnkaiwei:yes18:48
SumitNaiksatamKaiwei: if they are optional, then the service object is meaningless18:48
SumitNaiksatamyou can just use the basic firewall rule attributes18:49
KaiweiI mean, you can have a service object with only dst port, or service object with only protocol but no ports18:49
SumitNaiksatami would imagine that the service is characterized by the protocol and source/dest ports18:49
garyduanSumitNaiksatam: an empty service object means match all18:49
*** arosen_ has quit IRC18:49
SumitNaiksatamgaryduan: why would you need that18:49
SumitNaiksatamgaryduan: its match all anyway18:50
SumitNaiksatamKaiwei: i would still argue that at least source or dest port is required since that characterizes the service18:50
*** harlowja has joined #openstack-meeting18:50
garyduanIs current protocol in fw rule optional?18:50
BrianTorres-GilIt makes sense to me to have proto, srcport, dstport.  And srcport is optional.18:50
BrianTorres-GilThen one service object per rule.18:50
SumitNaiksatamgaryduan: protocol is optional in the API18:51
SumitNaiksatamgaryduan: the CLI requires you to use it18:51
SumitNaiksatamBrianTorres-Gil: agree18:51
SumitNaiksatamokay we are running short on time18:51
*** terriyu has joined #openstack-meeting18:51
garyduanSumitNaiksatam: ok18:51
beyounnif you have protocol, then port has to be there18:51
KaiweiSumitNaiksatam: Then how to createa rule says: allow all tcp traffic?18:51
*** markpeek has quit IRC18:51
SumitNaiksatamKaiwei: that is already supported in the rules today18:51
*** markpeek has joined #openstack-meeting18:51
SumitNaiksatamokay let beyounn create the blueprint and we can pick this discussion up again next week18:52
SumitNaiksatam#topic service_type framework and insertion18:52
*** openstack changes topic to "service_type framework and insertion (Meeting topic: Networking FWaaS)"18:52
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/fwaas-service-types-integration18:52
SumitNaiksatamseems like gardyduan has already implemented something18:52
SumitNaiksatamthis part is more mechanical though18:53
SumitNaiksatam#topic revisit firewall to firewall_policy association18:53
*** openstack changes topic to "revisit firewall to firewall_policy association (Meeting topic: Networking FWaaS)"18:53
SumitNaiksatami don't think we have enough time for this discussion18:53
SumitNaiksatamlet's circle back on this next week but i want to bring this up to plant the seed18:53
SumitNaiksatam#topic Zones part deux18:54
*** openstack changes topic to "Zones part deux (Meeting topic: Networking FWaaS)"18:54
SumitNaiksatamKaiwei: go ahead, trying to make sure we get back to your question18:54
*** nadya has joined #openstack-meeting18:54
Kaiweiok18:54
SumitNaiksatamso you think group of neutron ports does not represent a zone?18:55
*** sdake has joined #openstack-meeting18:55
*** sdake has quit IRC18:55
*** sdake has joined #openstack-meeting18:55
Kaiweiif we use ports as zones, what if we have two ports connected to same network (or subnet), each is in different zones?18:55
Kaiweiit looks odd that two ports in same network (or subnet) are in different zones...18:55
SumitNaiksatamKaiwei: yes18:56
SumitNaiksatamKaiwei: however, i doubt it will be used that way18:56
BrianTorres-GilI think it would be unusual to have two FW ports on same network/subnet unless you're doing link aggregation.18:56
Kaiweisome FW doesn't allow two interfaces on same subnet18:57
Kaiweibut I think most can have multiple interfaces on same networks but different subnets18:57
Kaiweialso, what if this is for two ports are for two different FWs?18:58
Kaiweiit it shouldn't be used this way, why not define zones as networks (or subnets)?18:58
SumitNaiksatamKaiwei: the problem is that we don't have an alternative to using neutron ports18:58
*** chandankumar has joined #openstack-meeting18:58
Kaiweiif it shouldn't18:58
*** whenry has quit IRC18:59
SumitNaiksatamdoes subnet work for the other firewall vendors?18:59
beyounnno18:59
SumitNaiksatamlets continue this discussion over emails and in the next meeting18:59
beyounnit does not18:59
SumitNaiksatamwe have to yield to the next meeting19:00
SumitNaiksatamthanks all19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Wed Oct 23 19:00:13 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-10-23-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-10-23-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-10-23-18.02.log.html19:00
BrianTorres-GilA zone can have multiple ports as members of the zone, correct?19:00
*** Kaiwei has quit IRC19:00
beyounnyes19:00
beyounnlater19:00
SumitNaiksatamBrianTorres-Gil: yes19:00
*** marun has quit IRC19:00
BrianTorres-Gilthanks19:01
SumitNaiksatamok lets continue over emails19:01
BrianTorres-Giltill next time19:01
SumitNaiksatambye19:01
ivar-lazzarobye19:01
*** BrianTorres-Gil has left #openstack-meeting19:01
*** luis_fdez has joined #openstack-meeting19:01
*** dcramer_ has quit IRC19:04
*** krtaylor has joined #openstack-meeting19:05
*** sarob has joined #openstack-meeting19:05
*** elo has quit IRC19:06
*** dstanek has quit IRC19:07
*** jlucci has quit IRC19:07
*** anand has quit IRC19:13
*** garyduan has quit IRC19:13
*** rongze has joined #openstack-meeting19:13
*** SridarK has quit IRC19:14
*** reed has quit IRC19:14
*** sushils has joined #openstack-meeting19:16
*** asalkeld_eating is now known as asalkeld19:16
*** elo has joined #openstack-meeting19:17
*** ben_duyujie has joined #openstack-meeting19:17
*** shakayumi has quit IRC19:17
*** rongze has quit IRC19:17
*** dstanek has joined #openstack-meeting19:19
*** elo has quit IRC19:19
*** fbo is now known as fbo_away19:19
*** galstrom_zzz is now known as galstrom19:21
*** smurugesan has left #openstack-meeting19:21
*** adalbas has quit IRC19:24
*** marun has joined #openstack-meeting19:28
*** nati_uen_ has joined #openstack-meeting19:28
*** zul has quit IRC19:28
*** vuil has joined #openstack-meeting19:29
*** yaguang has quit IRC19:30
*** nati_ueno has quit IRC19:32
*** IlyaE has quit IRC19:32
*** nati_uen_ has quit IRC19:32
*** dcramer_ has joined #openstack-meeting19:33
*** cody-somerville has joined #openstack-meeting19:34
*** sarob has quit IRC19:36
*** asalkeld has quit IRC19:37
*** asalkeld has joined #openstack-meeting19:41
*** IlyaE has joined #openstack-meeting19:47
*** whenry has joined #openstack-meeting19:48
*** elo has joined #openstack-meeting19:50
*** matel has quit IRC19:51
*** dkranz has quit IRC19:53
*** jtomasek has quit IRC19:54
*** funzo has joined #openstack-meeting19:55
*** nadya has quit IRC19:58
*** elo has quit IRC19:58
*** lrengan has joined #openstack-meeting19:58
*** jasond` has joined #openstack-meeting19:59
*** tspatzier has joined #openstack-meeting19:59
*** randallburt has joined #openstack-meeting20:00
stevebaker#startmeeting heat20:00
openstackMeeting started Wed Oct 23 20:00:50 2013 UTC and is due to finish in 60 minutes.  The chair is stevebaker. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: heat)"20:00
openstackThe meeting name has been set to 'heat'20:00
*** kanabuchi has joined #openstack-meeting20:01
stevebaker#topic rollcall20:01
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:01
shardyo/20:01
jasond`o/20:01
jpeeleryo20:01
sdake_o/20:01
randallburthello all20:01
tspatzierhi20:01
radixhello20:01
kanabuchihello20:01
*** zaneb has joined #openstack-meeting20:01
asalkeldo/20:01
zanebhello folks20:01
bgorskio/20:01
stevebakerI've just updated https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda20:02
*** gokrokve has joined #openstack-meeting20:02
stevebakernot long till summit!20:02
*** rnirmal_ has joined #openstack-meeting20:02
stevebaker#topic review last week's actions20:03
asalkeldyip20:03
*** openstack changes topic to "review last week's actions (Meeting topic: heat)"20:03
*** rnirmal_ has quit IRC20:03
stevebakershardy to sync Havana release notes etherpad with wiki20:03
shardyThat's done20:03
stevebakersweet20:03
stevebakerstevebaker to review all summit proposals and reduce to 9 sessions20:03
*** rnirmal_ has joined #openstack-meeting20:03
stevebakerdone20:03
shardyI also added a note about HOT being under heavy development, hence possibly being subject to change20:03
stevebakergood20:03
shardyafter some IRC discussions re the evolving HOT spec20:03
*** pcm_ has quit IRC20:03
*** rnirmal has quit IRC20:04
*** rnirmal_ is now known as rnirmal20:04
stevebaker#topic Summit session proposals20:04
*** openstack changes topic to "Summit session proposals (Meeting topic: heat)"20:04
stevebaker#link http://summit.openstack.org/20:04
*** therve has joined #openstack-meeting20:05
stevebakerWe were oversubscribed by 2x, so I had to be brutal20:05
*** m4dcoder has joined #openstack-meeting20:05
*** dcramer_ has quit IRC20:06
zanebstevebaker: is there a way for us plebs to see the _schedule_ (as opposed to the session list)?20:06
*** lrengan_ has joined #openstack-meeting20:06
shardywhich didn't make the cut?20:06
stevebakerso I suggest we just go through each of the 9 sessions quickly now, and feedback would be welcome if any topics are over or under represented.20:06
stevebakershardy: sort by topic and scroll down to heat20:06
*** whenry has quit IRC20:06
zanebeven better, sort by status first, then by topic20:07
*** yogeshmehra has left #openstack-meeting20:07
stevebakerI've also come up with a draft schedule, but I don't yet have visibility on other design summit schedules for clashes so that may change20:07
stevebakerlet me paste the provisional schedule20:07
*** rakhmerov has quit IRC20:07
stevebaker#link http://paste.openstack.org/show/49281/20:08
stevebakerThursday is a big day20:08
*** rpothier_ has joined #openstack-meeting20:08
*** SergeyLukjanov is now known as _SergeyLukjanov20:08
*** _SergeyLukjanov has quit IRC20:09
stevebakerI put the topics that seem to need the most discussion first20:09
stevebakerHeat Software Orchestration20:09
stevebakerHeat workflow: consider taskflow, Mistral or other20:09
stevebakerthen the afternoon sessions are fairly feature based, but ordered arbitrarily20:09
asalkeldlooks good steve20:10
thervestevebaker, It's missing the autoscaling one20:10
*** elo has joined #openstack-meeting20:10
therveErr20:10
thervestevebaker, sorry misreading :/20:10
shardystevebaker: lgtm20:10
radixhehe20:10
therveI counted 8 for some reasons20:11
stevebakerThe 2 friday morning sessions are a bit different to all the others (one is about technical debt, the other is about usability features)20:11
stevebakerso the controversial sessions are first, so we can all be hating on each other for the rest of the day ;)20:11
therveHeh20:11
lrengan_:-)20:11
*** sacharya has quit IRC20:12
stevebakerso one scheduling problem I see so far is 5:20 Thursday clashes with http://openstacksummitnovember2013.sched.org/event/d021c726f6fbe4d1fc7ade0a72a6ae2a20:12
*** vito-ordaz has quit IRC20:12
tspatzieroh, that's mine20:12
*** SergeyLukjanov has joined #openstack-meeting20:12
stevebakerit would be good to go to that, even if we have to jog to all get there20:12
asalkeldthat's late in the day20:13
bgorskiHow it works? The person who proposed the session in responsible for preparing it?20:13
asalkeldbgorski, not much prep20:13
stevebakerso I'll ask if we can swap our 5:20 with another project, we're allowed to horse-trade slots20:13
therveI was about to suggest that20:13
asalkeldit's a discussion20:13
stevebakerbgorski: it depends on the session, generally it will be less structured than that20:14
*** rongze has joined #openstack-meeting20:14
zanebI don't know about this jogging business, but count me in for horse-trading20:14
stevebakerso lets go through each session20:14
randallburtcan we leverage the horses?20:14
stevebakerin time order20:14
stevebaker#link http://summit.openstack.org/cfp/details/8220:14
bgorskiasalkeld, yea I know its are design sessions but some 5 or 10 min introduction would be nice20:14
stevebakerHeat Software Orchestration20:14
asalkeldbgorski, yeah that's about right20:15
* SpamapS imagines randallburt with a very large see-saw being accosted by some angry horse farmers..20:15
asalkeldstevebaker, maybe we can have people with different solutions for that?20:15
stevebakerthis will be a bit of a free-for-all, but hopefully it can be kept on track with a concrete proposal20:15
asalkeldquick 5 min20:15
asalkeldI am trying to make a PoC now20:16
SpamapSbgorski: Right, typically the "leaders" of a session will set the table. What you _don't_ want is a lot of slides and "here is how we're doing it".. even if you want that to happen.. as it hat squelches the discussion. You20:16
asalkeldusing marconi20:16
stevebakerasalkeld: yep20:16
asalkeldSpamapS, +120:16
*** elo has quit IRC20:17
SpamapSlovely typing there.. thank you latency20:17
asalkeldwant some possible solutions, and discuss20:17
stevebaker#link http://summit.openstack.org/cfp/details/12120:17
stevebakerHeat workflow: consider taskflow, Mistral or other20:17
stevebakerzaneb: I wonder if you and harlowja could come up with a plan for running this session?20:17
asalkeldstevebaker, so that is for the engine to use20:17
*** rongze has quit IRC20:18
asalkeld(not to do with the software config)20:18
SpamapSI would like to recommend that the task flow people and mistral people try to have a breakout session some time before this session to allow interested parties to get an idea where the projects are now.20:18
randallburtSpamapS:  +120:18
*** vito-ordaz has joined #openstack-meeting20:18
zanebsure, I can help out but I imagine harlowja knows basically what he wants to discuss20:18
SpamapSAnd/or direct us to where we can ascertain that offline before summit.20:19
asalkeldzaneb, you know what we need tho'20:19
stevebakeryes, this is to consider transforming our declarative orchestration to workflow for execution20:19
zanebbtw, I don't know where the idea of us using Mistral came from20:19
zanebbut... no.20:19
randallburtlol20:19
bgorskiSpamapS, I was not planning to give you presentation about our multi region vision with a lot of slides so do not worry :)20:19
*** sacharya has joined #openstack-meeting20:19
SpamapSzaneb: distributed workflow would mean no need for a single-engine stack lock.20:19
randallburtweeeeeeel maybe not.20:19
stevebakerzaneb: you've got the best knowledge of heat scheduling currently, so you can best represent heat's concerns20:20
zanebI mean, I think we should *probably* use taskflow. But not Mistral.20:20
SpamapSzaneb: but if Mistral isn't quite aimed at distributed celery-like workflow then the point is moot. :)20:20
*** jecarey has quit IRC20:21
stevebaker#link http://summit.openstack.org/cfp/details/7920:21
zanebwe discussed Convection already at the last summit and decided that we would share a library not consume an API20:21
stevebakerAutoscaling Design20:21
asalkeldyip20:21
radixwe have a couple of issues to figure out there20:21
stevebakerA nice easy topic for straight after lunch ;)20:22
zanebstevebaker: getting the easy ones out of the way first? ;)20:22
radixheh heh20:22
radixI have been working on a proposed API spec20:22
asalkeldbring your coffee20:22
radixstevebaker and I talked about splitting up the discussion into API first and resources second20:22
radixI think the load balancer thing is probably the most interesting point to figure out during the discussion20:22
asalkeldI'd suggest people write up as much as possible in advance20:22
asalkeldso we have the maximum context20:22
stevebakerIt seems like this will be a session which is more about presenting a solution, with discussion just about details and problems?20:23
* SpamapS wonders if we can get some of that extra-strength Thai red bull... :)20:23
radixstevebaker: I think a lot of us have come to a baseline agreement about the basic solution, but there's some gnarly things to figure out20:23
radixthe wiki page mentions all the problems we have to solve afaik20:24
radixoh, wait, there was another one therve thought of this morning, we should add that20:24
sdakemonster xtreme ftw20:24
zanebload balancing is definitely a tricky one20:24
stevebakerand I suggested the first half be only about the API, and the second half be about the resources. Our autoscaling talks tend to descend into a gordian knot of api<>resources arguments ;)20:24
asalkeldbrb in 5min20:25
stevebakerbtw, all 9 slots are full, if we can free up one slot that leaves us a spare for the most important topic that arises while we're there20:25
*** elo has joined #openstack-meeting20:26
radixthe main issue about LB is that I'd like to avoid knowledge of it in the autoscale API/service, and instead make it flexible enough to support the general class of relationships like LB20:26
radixhowever that's done, I don't care :)20:26
zanebIMO we should talk about the API as if there were no resources20:26
zanebthen we can add the resources after, like we do for every other OpenStack service20:26
thervestevebaker, retry/convergence and healing could be covered in the same slot, IMHO20:27
radixagreed20:27
SpamapSzaneb: +1 ... make a good micro service, then make resources to support it.20:27
shardyzaneb: agree, I thought the point of the AS API is that folks didn't want to consume AS via heat resources20:27
stevebakertherve: I don't see how they are related, and I think there is enough in healing to discuss on its own20:27
SpamapSRight, so agree on what a good AS micro service will (and will not) expose in an API, and then we can look at what resources are needed to support that.20:28
zanebyeah, it's talking about both at the same time that causes the Gordian knot, with API parts that rely on the resources, which is backwards20:28
stevebaker#link http://summit.openstack.org/cfp/details/20520:28
stevebakerSupport API retry function with Idempotency20:28
radixthe resources should be a pretty obvious mapping to the API anyway20:28
radixok, /me shuts up :)20:28
*** asalkeld has quit IRC20:28
*** asalkeld has joined #openstack-meeting20:28
kanabuchiI noted down details here: https://etherpad.openstack.org/p/kgpc00uuQr20:29
SpamapSthe retry stuff is pretty important, and there seem to be differing approaches suggested, so an entire session may be needed just to articulate the approaches and choose one.20:29
zanebstevebaker: that session could actually be combined with the taskflow one IMO20:29
zanebhttp://summit.openstack.org/cfp/details/205 that is20:29
shardyIMHO we just don't want retry loops in heat20:29
radixand make sure everyone knows that this _isn't_ the same as healing :)20:29
stevebakerso this might not deserve a full session, but there could be some worthy discussion on how the retry policy is specified, and a guide on implementation if it is a non-heat-core dev doing it20:29
shardyIf they should exist, they should be in the *clients20:29
*** yaguang has joined #openstack-meeting20:29
stevebakerradix: exactly20:29
thervestevebaker, It seems to be that retry is a poor-man convergence20:30
shardytherve: they aren't the same thing at all IMO20:30
shardyone is about aligning the template with the real state of resources20:30
*** radez is now known as radez_g0n320:30
SpamapSdetails of how exactly it will work are not always a good summit session goal. Details of _what_ to do are paramount.20:30
stevebakertherve: no, retry happens within create or update on a single resource, convergence is a new action which compares desired state with actual state20:30
shardythe other is about retrying due to service flakiness20:31
SpamapSAs in, we don't want to quibble over syntax, there, but we do wnat to make sure the end goal is agreed upon.20:31
thervestevebaker, Hum, okay. The retry thing sounded like a new action.20:31
*** jecarey has joined #openstack-meeting20:32
*** galstrom is now known as galstrom_zzz20:32
shardyIs the intention for all openstack services to retry everything?20:32
SpamapSshardy: retry loops in Heat is, indeed, a workaround for bugs in the clients. We're more talking about "what to do when Heat is stuck"20:32
*** jjacob512 has quit IRC20:32
shardyI don't see why Heat should be special and retry all the things20:32
zanebstevebaker: the more I look at it the more I think this doesn't deserve a session. It hasn't been discussed on the mailing list even20:32
stevebakerbut maybe the topic is small enough to share with another session, maybe http://summit.openstack.org/cfp/details/121 (workflow) or http://summit.openstack.org/cfp/details/95 (convergence)20:32
radixshardy: special.... man, every openstack user has to retry stuff all the time in practice </rant>20:32
stevebakeror we just drop it20:32
radixbut yeah, that's because there are bugs everywhere20:33
SpamapSLike if you were just plain out of quota space when you did an update that added a resource.. novaclient isn't going to retry that forever... we need a "try again" driven by the user.20:33
shardyradix: hence my suggestion that it should be abstracted into the clients..20:33
*** cdub_ has quit IRC20:33
asalkeldaren't we getting reservations?20:33
*** elo has quit IRC20:33
zanebsession time should be reserved for proposals that have be discussed and need face-to-face interaction to resolve20:33
radixshardy: yeah, I'm not disagreeing20:33
asalkeldshouldn't that solve these issuess20:33
randallburtSpamapS:  agreed, I think its simply allowing some of our actions to be re-entrant without re-creating things that already worked.20:34
stevebakerzaneb: this topic has been floating around for the last cycle20:34
SpamapSrandallburt: well said.20:34
SpamapSIf we can't spare the session time, I'm happy to block out time to do a breakout outside our normal session time, but I definitely want to get some consensus on this and do some of the actual work.20:34
shardyrandallburt: that's not how the session proposal is worded tho20:35
shardy+1 on allowing users to manually retry things, huge -1 on automagiacally while(1)ing stuff in heat code20:35
*** markvan has quit IRC20:35
radixI think if it's a user action, it's more in line with the discussion about convergence20:35
SpamapSshardy: agreed, perhaps we can combine this with convergence.20:35
randallburtshardy:  undertood on the 1st and totally agree on the second20:35
shardySpamapS: +120:35
SpamapSOk so lets combine them.20:36
stevebakerok, lets tack it onto the convergence session, maybe the last 1/3rd20:36
randallburt+1 on combining them20:36
shardyHuh, I think therve just said that didn't he ;)20:36
*** zul has joined #openstack-meeting20:36
randallburtindeed20:36
stevebaker#link http://summit.openstack.org/cfp/details/9520:36
thervemy evil plan succeeded20:36
radix:)20:36
stevebakerHealing and convergence20:37
shardytherve: my point was that what is being proposed is not the same, but I accept that convergence may solve both use-cases20:37
randallburtand retrying20:37
stevebakercan we call this healing? convergence is a mouthful. the action is a 4 letter verb!20:37
therveshardy, Agreed20:37
*** dcramer_ has joined #openstack-meeting20:37
SpamapSor, convergence may make use of the same mechanism that a user-driven retry mechanism uses.20:37
*** topol has joined #openstack-meeting20:37
radixI see two interesting things in this session, 1) discussion of an explicit "retry" / "converge" operation from the user, and 2) automatically watching for divergence and trying to convergence20:38
radixer, trying to converge*20:38
stevebakerradix: heal!20:38
radixok ok20:38
SpamapSradix: if only you could explain these things to us in person...20:38
radixbut it's not like converge is unusual in this space, puppet and chef use that phrase too :P20:38
SpamapSradix: you know, the timezones would allow you to attend both events using a telepresence bot at one of them..20:38
*** rakhmerov has joined #openstack-meeting20:38
radixSpamapS: sorry =( well, honestly I basically just explained everything I have thought on the subject, hehe20:38
*** reed has joined #openstack-meeting20:39
*** tjones has left #openstack-meeting20:39
radixactually, I was wondering if there would be any facility for remote involvement20:39
stevebakerradix: I've heard maybe not20:39
radixI wonder if a G+ hangout would work. but I may be sleeping :)20:39
asalkelddepends on the network20:39
shardybasically we need two things: (1) allow retry from failed states, and (2) allow retry from wedged in-progress states without making a huge mess and breaking everything20:39
asalkeldnot always the best20:39
SpamapShangouts have been used, but in the past the summit network is , while good, not that good.20:39
radixok20:40
stevebaker#link http://summit.openstack.org/cfp/details/5820:40
stevebakerHeat support for multi-region and multi-cloud20:40
bgorskiSo I think we should talk who heat will orchestrate stack with resources in different region20:41
*** salv-orlando has joined #openstack-meeting20:42
stevebakerthe big thinks I want answered in this session is how to represent the credentials for different clouds, and how we represent what resource goes on what cloud/region20:42
stevebakerbig thin*g*s20:42
therveAlso, how auth will work at all20:42
asalkeldand az's/regions/flavors20:42
asalkeld(validating them)20:43
shardyA topic we were discussing is how deferred auth and signals can work for multi-cloud20:43
*** mrunge has quit IRC20:43
bgorskistevebaker,  I really like your context concept to express what resource goes to which cloud/region20:43
SpamapSMy position: figure out just the next step, and do that. This is pretty big, and each step is really tricky... I don't think one cycle will get us to multi-region even.. and multi-cloud is a whole other ball of wax.20:43
shardyie if you can't use trusts, and you don't have admin on all-the-clouds to create stack users20:43
stevebakerbgorski: yep, whether we can apply that context to a single resource, or only to an entire nested stack is a good question20:44
shardySpamapS: +120:44
SpamapS(and I don't consider multi-region done until it is HA so that one region failing != your whole stack being unmanagable)20:44
shardypersonally I think just getting multi region working is a huge undertaking20:44
radixSpamapS: you mean like making heat an actual distributed system?20:44
bgorskiI checked the heat code base and right now each nested stack has his own set of clients20:44
SpamapSradix: aye20:44
bgorskiso right now it is really easy to do that for nested stack20:45
*** gyee has quit IRC20:45
SpamapSright so this sounds like it should be a good healthy session to make sure we understand that next step and the long term vision too20:45
bgorskibut specifying context for each resource will be much harder20:45
*** rwsu has quit IRC20:45
asalkeldwe could put contexts in the environment20:45
asalkeldand associate them to resources there20:46
*** SumitNaiksatam has quit IRC20:46
stevebaker#link http://summit.openstack.org/cfp/details/20020:46
asalkeldthen the resource ask the env for it's context20:46
stevebakerStack abandon and adopt20:46
zanebbgorski: excellent point, and IMO we should implement multi-region only for Stack resources20:46
*** rwsu has joined #openstack-meeting20:46
stevebakerapparently multiple sessions can be scheduled into each slot, so I might resurrect http://summit.openstack.org/cfp/details/98 and add it to this slot20:47
asalkeldthis is scary stuff20:47
*** nati_ueno has joined #openstack-meeting20:47
bgorskizaneb: I think so too20:47
shardyYeah, this loooks like it could get pretty hairy..20:47
SpamapSThat would be an interesting mechanism to make use of for HA multi-region.20:47
randallburtstevebaker:  I think that one would be covered by adopt/abandon20:48
*** nati_ueno has quit IRC20:48
*** nati_uen_ has joined #openstack-meeting20:48
SpamapSregion-master goes down, region-slave promotes itself and reads in a static map of what resources it can own and adopts them.20:48
stevebakerrandallburt: it would, that is why I refused it20:48
asalkeldSpamapS, needs to be heat version independent too20:49
SpamapSI don't think this would be super hairy either btw. I love the concept.20:49
randallburtasalkeld:  I think that's a pretty tall order.20:49
asalkeldSpamapS, if you can guarantee the heat create the resources20:49
SpamapSFor instance, I could see using it to prepare stem-cell type servers to then be mo[4~ved into stacks as needed.20:50
stevebakerthe hairiest bit is how to handle endpoints changing on running servers, but there are many use cases which wouldn't be too hard to achieve20:50
radixIs the idea to have a new API? like "here's the resource properties and resource_id and any resource_data associated with it, go"?20:50
radixor maybe extra parameters with create-stack20:50
randallburtI still think you can do this in the user/base case with environments20:50
asalkeldradix, some kind of state file20:50
randallburtadd the ability to specify a physical resource id for a resource20:50
therveThe interesting part would be to do it without specific resource support20:50
stevebakerradix: I was thinking new actions, abandon and adopt. adopt is like create, but with some extra state information\20:50
SpamapSrandallburt: an interesting approach to bring up before the summit. Can you write that up and comment on the proposal or maybe send to the ML?20:50
randallburtSpamapS:  sure20:51
bgorskiI think adopt and abandon functionality will be great if created stack will be able to generate template which describes it resources and dependencies between them20:51
*** chandankumar has quit IRC20:51
radixtherve: I guess that shouldn't be too hard, since resources only have two well-defined ways to store data20:51
radixin resource_id, and in resource_data20:51
stevebakerrandallburt: OS::Nova::Server already has a name property20:51
stevebakerrandallburt: as do many other native resource types20:51
SpamapSthis _might_ be combinable into convergence as well20:51
bgorskibecause we can use gui as a editor and template debugger but I know it is a long term vision and dream :)20:51
thervebgorski, Hum, what would you pass to Heat? The tenant?20:51
therveradix, That's still 2 too many :)20:52
randallburtstevebaker:  I mean specify a resources native ID in the environment so heat won't create a new one20:52
stevebakerbgorski: resource relationships is already exposed in the API20:52
SpamapSlets not get into HOW... if we want to discuss it, lets move on and keep it scheduled.20:52
stevebakerFriday!20:53
stevebakerhttp://summit.openstack.org/cfp/details/22920:53
shardyOne issue with this (the adopt) is it's essential that we have 100% parity between the resource properties and the underlying API/physical-resource20:53
stevebakerHeat exorcism20:53
stevebakerhangover session20:53
zanebbgorski: so, I don't believe it's possible in general to infer the relationship between resources20:53
shardyso it can never be compatible with multiple versions of things20:53
SpamapSDo we need a session on a list of bugs?20:54
SpamapSThese all look like "yes fix that please"20:54
shardyOr rather we have to have parity with every project at release time20:54
shardyanyway..20:54
stevebakerzaneb has a bunch of technical debt issues to discuss, the fixes for some might be disruptive so discussion may be worthy20:55
asalkeldSpamapS, maybe a user session?20:55
zanebSpamapS: I guess I proposed it because there are a couple of major changes we need to consider20:55
SpamapSzaneb: right I see that we do need a "native heat resource access method"20:55
shardySpamapS: I don't think so, we can prioritize bugs in LP and the weekly meetings20:55
*** luis_fdez has quit IRC20:55
zanebe.g. do we base resources directly on APIs, even when they're broken like Neutron :(20:55
stevebakerand it is a good chance to lay down some "don't to this, and this is why" guidelines20:55
zanebstevebaker: ++20:55
zanebstevebaker: heh, maybe we should schedule this before the autoscaling session ;)20:56
* zaneb ducks20:56
radixa lot of those autoscaling-related ones should go away with the new proposed stuff20:56
stevebakerso if anyone has other implementation cleanup things, let me know and I'll add it to the session20:56
SpamapSzaneb: IMO resources shoudl be tied to the logical problem they solve, not just the API. API adherence is just nice for closing the understanding loop.20:57
*** AndChat|437241 has joined #openstack-meeting20:57
tspatzierSpamapS, +120:57
zanebSpamapS: +220:57
SpamapSBut yeah perhaps we do need to discuss those two things.20:57
*** ben_duyujie has quit IRC20:57
*** nealph has joined #openstack-meeting20:58
asalkelddo we need a user session?20:58
stevebaker#link http://summit.openstack.org/cfp/details/8320:58
stevebakerStack troubleshooting support20:58
radix+1 SpamapS as well :)20:58
asalkeldwhere our users can talk about things that are bugging them?20:58
*** dstanek has left #openstack-meeting20:58
therveSpamapS, This hasn't been what we've done up to now, at least20:59
*** AndChat|437241 has quit IRC20:59
stevebakerthis session is proposing a template debugger (some kind of breakpoint mechanism) and other tools to diagnose why a stack has broken20:59
asalkeldstevebaker, I'll link the user-logging bp too21:00
*** gordc has joined #openstack-meeting21:00
asalkeld#link https://blueprints.launchpad.net/heat/+spec/user-visible-logs21:00
stevebakertspatzier: I'm a little concerned that this is a wishlist, rather than something that has developers ready to work on21:00
*** zul has quit IRC21:00
SpamapStherve: well sometimes we accidentally did it, when the API matched the problem space well ;)21:00
tspatzierstevebaker, partly agree, but we have a team internally how think about implementation.21:00
shardystevebaker: +1, it doesn't look all that achieveable in the near-term to me21:00
*** joel-coffman has quit IRC21:01
stevebakerits totally achievable, but it just needs bodies to do it21:01
SpamapSa line based live debugger wouldn't actually be that hard.21:01
tspatzierI asked them to prepare some more details. A session could help them to get the right direction to get this started.21:01
shardySpamapS: It's the in-instance debugging I think will be ahrd21:01
shardyhard even21:01
bgorskiaren't we out of time?21:02
stevebakertspatzier: as long as they intend to implement something as well - a design wouldn't be that useful21:02
asalkeldyip we are21:02
eglynnladies & gents ... cough ... have ye any homes to go to?21:02
tspatzierin-instance debugging will become a more important issue with the software orchestration thing21:02
eglynn(as Irish barmen shout out at pub closing time ...;)21:02
zanebwow, some really good session proposals didn't make the cut :( tough schedule.21:02
radixwhoah, that went long :) sorry21:02
stevebakereglynn: keep your hair on :)21:02
SpamapSshardy: we implemented that in Juju by ssh'ing in from the client into a screen started specifically to run the hooks (in this case, we'd start screen in the cloud-init)21:02
stevebaker#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Wed Oct 23 21:02:35 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-10-23-20.00.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-10-23-20.00.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-10-23-20.00.log.html21:02
stevebakerlets continue in #heat21:02
*** rdxc has quit IRC21:02
*** galstrom_zzz is now known as galstrom21:02
* SpamapS bows in apology21:02
eglynn#startmeeting ceilometer21:02
openstackMeeting started Wed Oct 23 21:02:56 2013 UTC and is due to finish in 60 minutes.  The chair is eglynn. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
thomasemThat's a sad time.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: ceilometer)"21:02
openstackThe meeting name has been set to 'ceilometer'21:03
eglynnjd__ is on vacation so I'll fight with the ircbot this week ...21:03
*** tspatzier has left #openstack-meeting21:03
*** randallburt has left #openstack-meeting21:03
*** SumitNaiksatam has joined #openstack-meeting21:03
eglynn(here's hoping no-one calls for a vote on anything ... ;))21:03
dhellmanno/21:03
terriyuo/21:03
lsmola hello21:03
asalkeldo/21:03
nealpho/21:03
thomasemYou will win where we previously failed.21:03
thomasemo/21:03
*** bgorski has quit IRC21:03
gordco/21:03
*** therve has left #openstack-meeting21:03
eglynnany more hands to go up?21:03
*** rpothier_ has quit IRC21:03
eglynnright-o, let's dig into the agenda items ...21:04
*** jasond` has left #openstack-meeting21:04
*** kanabuchi has left #openstack-meeting21:04
eglynn#topic Ceilometer errors in tempest runs21:04
*** openstack changes topic to "Ceilometer errors in tempest runs (Meeting topic: ceilometer)"21:04
dhellmann#link https://wiki.openstack.org/wiki/Meetings/MeteringAgenda21:04
eglynnor "when can we stop using sqlalchemy as the default backend in devstack" ;)21:04
eglynndhellmann the floor is your's ...21:04
dhellmannI thought sileht worked out what to do about that already21:04
*** m4dcoder has quit IRC21:04
eglynnyeah we discussed this a while back on IRC with sileht & jd__ IIRC21:04
dhellmannok21:05
nealphcan you summarize?21:05
eglynnwe should be able to switch back to mongodb as the default in devstack21:05
eglynn(as mongodb-server 2.4.x has hit the ubuntu cloud archive)21:05
dhellmannftr, it looks like what we need to do is increase some of the defaults for pool sizes21:05
* eglynn digs for the log ...21:05
* dhellmann looks for the review link21:05
eglynn#link http://eavesdrop.openstack.org/irclogs/%23openstack-metering/%23openstack-metering.2013-10-02.log21:05
dhellmann#link https://review.openstack.org/#/c/53396/21:05
gordcdhellmann: should we be increasing them in ceilometer code?21:06
dhellmanngordc: we want ceilometer's defaults to be useful out of the box21:06
eglynndhellmann: well that may solve one issue with using sqlalchemy, but there are others21:06
eglynndhellmann: for example the lack of support for metaquery21:06
dhellmanneglynn: ok, this was the one I knew about :-)21:06
dhellmannthat should just result in skipped tests, right?21:06
eglynn(needed by horizon and ceilo alarming, possibly other too ...)21:06
gordci'm kind of torn on that personally... because the defaults we set may or maynot work based on how many meters the environment is capturing.21:06
eglynnwell /me thinks we should be defaulting to our most feature complete storage backend21:07
dhellmanngordc: sure. but the tempest environment is very very small, so our standard defaults are clearly not enough21:07
eglynnand the one that distros are likely to recommend for production21:07
*** lblanchard has quit IRC21:07
dhellmanneglynn: sure. we need to figure out how to get the right version of mongodb into devstack then21:07
eglynndhellmann: yep, exactly21:07
gordcdhellmann: i guess... what's setting the defaults currently? the sqlalchemy code from oslo?21:08
thomasemWouldn't that be mongodb-10gen? I'm not sure how ubiquitous that is.21:08
*** asalkeld has quit IRC21:08
eglynndhellmann: so according to sileht, mongodb-server 2.4.0 is now in the ubuntu cloud archive21:08
eglynn(as per IRC link above)21:08
*** asalkeld has joined #openstack-meeting21:08
dhellmanneglynn: ok, does that mean the devstack gates will install it?21:08
eglynnpreviously IIRC the prob was that it was only availble for precise from the 10-gen repo21:08
dhellmanngordc: yes21:08
eglynndhellmann: yep, it did up to now21:08
dhellmanneglynn: yes, that's right21:08
eglynndhellmann: sorry, up to being disabled as the default21:09
dhellmannok, well, I think we should go for both then21:09
thomasemOh, I see. Yeah, like I run on Debian and the .deb for mongodb on Squeeze was <2.2.21:09
*** shakayumi has joined #openstack-meeting21:09
thomasemSo, I have to use mongodb-10gen when I swap to that backend.21:09
dhellmannright, developer environments are OK because we can write instructions for upgrading21:09
thomasemyep21:09
eglynnyep, so I'll follow up with sileht on that again tmrw on how to enable grabbing from the cloud archive21:09
dhellmannbut the automated environment has different rules, so we need to make sure we're allowed to require the package21:10
dhellmanneglynn: sounds good21:10
eglynnthe infra folks didn't want us to require a package from the 10-gen repo IIRC21:10
dhellmanndo we also want to accept a patch to raise the defaults?21:10
dhellmanneglynn: yes, that's right21:10
eglynnbut now we should be to switch back21:10
*** rakhmerov has quit IRC21:10
dhellmanncloud archive may be ok21:10
*** pdmars has quit IRC21:10
eglynnbe ok to switch back, yep exactly21:11
dhellmanneglynn: we should probably do some work to figure out how out of sync the drivers are w.r.t. features21:11
dhellmannbecause I think the mongo driver does not deal with events, right?21:11
eglynndhellmann: yep agreed21:11
dhellmannmaybe I missed that being added, though21:11
thomasemdhellmann, there are reviews up for it21:11
gordcdhellmann: i'm ok with raising defaults.... only thing is the tests i ran, we can/have way more than 10 sessions running at any given time.21:11
thomasemlet me snag them21:11
dhellmannwould be good to go through before the summit21:11
eglynnthere's a patch in the review queue also to add metaquery to sqlalchemy21:11
thomasem#link https://review.openstack.org/#/c/49548/21:12
thomasem#link https://review.openstack.org/#/c/49456/21:12
eglynnhttps://review.openstack.org/#/c/49456/21:12
eglynnsnap! :)21:12
thomasem;)21:12
dhellmanngordc: we can work out the actual values through gerrit discussion; I don't know the right answer there21:12
gordcdhellmann: cool cool.21:12
eglynnso this will bite us again I think unless we become firmer re. feature parity between the drivers21:13
*** atiwari has joined #openstack-meeting21:13
dhellmanneglynn: yeah, I think that should be a goal for icehouse21:13
thomasemeglynn, +121:13
eglynnand where we don't have parity, we need a very clear statement of that21:14
dhellmannwe should do something to specify which parts of the driver API are related, maybe with separate base classes or something to hold the interfaces?21:14
eglynni.e. the implications of chosing a storage backend in terms of what stops working21:14
eglynndhellmann: yep, that would make sense21:14
*** rongze has joined #openstack-meeting21:14
dhellmanneglynn: we could also look at some of the interface description libraries other than abc21:14
thomasemYeah. The tests can be a good source for that. If your driver can't pass this series of tests, it's out of compliance. Sort of like that timestamp ordering one.21:14
dhellmannbut I feel like we have a lot of "this method is implemented, but not all aspects of it work" kinds of differences21:15
thomasemfor resources21:15
dhellmannespecially with variations on queries21:15
dhellmannso we might want to think about whether it makes sense to split those out into separate methods, for clarity21:16
dhellmannI hate even suggesting that, though :-/21:16
*** IlyaE has quit IRC21:16
thomasemdhellmann, I'm not sure I follow.21:16
dhellmannnova has separate methods like "find resource by id" and "find resource by name"21:17
*** SumitNaiksatam has quit IRC21:17
eglynnyeah, its a non-trivial question, how best to capture the functional requirements imposed on the storage driver by various features21:17
dhellmannwe have "find resource" with optional parameters21:17
dhellmannand then in some drivers one of the parameters doesn't work, so we raise NotImplemented21:17
eglynnyep, suddenly pagination or metaquery blows up when you switch drivers21:17
dhellmannthat's a simplistic example, the real example is more like we don't support a particular way of querying against the metadata associated with an event in some cases but not in others21:17
dhellmannright21:18
thomasemI see. Yeah, that's difficult to say which would be deserving of that or not. Some are just simply filters, others may have completely different query structures.21:18
*** SumitNaiksatam has joined #openstack-meeting21:18
dhellmannwe don't want to say we can't add features until all the drivers work, but we should probably say that at least one driver must always have all of the features21:18
dhellmannand pick a single driver to be the main or default or whatever21:18
*** dcramer_ has quit IRC21:18
thomasemIn any case, you could get a bit clever with your tests and see that the method behaves the same across drivers.21:18
eglynndhellmann: +121:18
dhellmannthat used to be mongo, until we had a bunch of people not wanting to use it add features :-)21:19
* dhellmann looks at sandywalsh21:19
*** rongze has quit IRC21:19
thomasemLol, he's on a plane right now, I'd imagine.21:19
eglynn+1 for maintaining mongo as the canonical driver21:19
dhellmannthomasem: we do, in fact, run the same test code against all of the drivers21:19
thomasemdhellmann, I know. What I meant was flesh out in the tests what a compliant driver looks like.21:19
dhellmannI would go along with that, or even with sqlalchemy, but either way we should pick one21:19
thomasemwith what*21:19
dhellmannthomasem: ok, I'm not clear on what you're suggesting we would do different21:20
dhellmanndrivers are allowed to raise NotImplementedError for missing features, and the tests just skip21:20
thomasemdhellmann, Not different, just ore of. :)21:20
*** aepifanov has quit IRC21:20
dhellmannah, ok, yes to more testing :-)21:20
thomasemdhellmann, Take that timestamp ordering test for example.21:20
eglynnhow about we try to grab an unconference slot for this discussion at summit?21:21
nealphthat would provide a reference point...but would we then require those adding new drivers to update mongo with any missing functionality?21:21
eglynn(to involve the RAX folks with skin in the game re. events)21:21
nealph+1 on the session21:21
* eglynn is assuming events is the main incomplete aspect of mongo currently21:21
dhellmanneglynn: not a proper conference session in the ceilometer room? are we out of slots?21:21
gordceglynn: did we figure out how many slots we have at summit?21:21
eglynngordc: 11 last I heard21:22
* thomasem is becoming sadder by the second that he can't join y'all.21:22
dhellmannnealph: yes, the idea would be all new features have to land in mongo if they are added to another storage driver21:22
*** zul has joined #openstack-meeting21:22
dhellmannor, if not mongo, the driver we do agree on21:22
eglynndhellmann: +121:22
dragondmdhellmann: me& sandywalsh will be there @ hk. I'm up for an unconf session.21:22
eglynndragondm: cool21:22
*** weshay has quit IRC21:22
eglynnshould we move on?21:23
dhellmanneglynn: why an unconference session, instead of a regular session?21:23
eglynndhellmann: I'd be up for either21:23
nealph15 proposals so far....some trimming already needed.21:23
dhellmannI'll propose one on this21:23
eglynndhellmann:21:23
eglynndhellmann: cool!21:23
eglynn#topic summit update21:23
gordcnealph: there's a few regarding api so i would think they could be merged.21:24
*** openstack changes topic to "summit update (Meeting topic: ceilometer)"21:24
dragondmeglynn: dhellmann:, I'd be up for either. I'm sure sandy would as well.21:24
eglynnon the subject of HK, the ceilo track for the design sessions will be finalized shortly by jd__21:24
nealphtoo late to propose another?21:24
eglynnwe're over-subscribed, so I suspect there will be some merged sessions21:24
eglynn(some obvious candidates for merging among the proposals)21:24
dhellmann#link http://summit.openstack.org/cfp/details/35521:25
*** anniec has quit IRC21:25
eglynndhellmann: thanks!21:25
eglynnso jd__ will be finalizing the approved sessions and pushing the schedule to sched.org shortly21:25
eglynn(this time round, IIUC the design summit and conference will have completely separate schedules)21:26
eglynnand apparently run in different buildings too ...21:26
*** julim has quit IRC21:26
dhellmannI think it's separate floors of the same building, but a very very large building21:26
dhellmannthere is quite a distance between the two spaces, I think21:26
eglynna-ha, ok21:26
eglynn(apparently some of the other projects had problems before with randomers showing up at design sessions)21:26
dhellmannthat wasn't entirely clear from ttx yesterday, though, so I could have that wrong21:27
*** anniec has joined #openstack-meeting21:27
* eglynn doesn't remember it being an issue with ceilo though21:27
nealphthat should be interesting...I've seen only a couple of cm-specific conference talks though.21:27
dhellmannyeah, the nova room in particular was packed21:27
gordcwhat constitutes a 'randomer'? non-contributer?21:27
dhellmannit's a shame I'm going to have to miss so many of the ceilometer sessions to be in the oslo room21:27
dragondmmakes me wonder if the design summit & conference shouldn't be 2 separate events altogether...21:28
dhellmanngordc: yeah, we had non-atc folks clogging up the doorways21:28
*** jaypipes has quit IRC21:28
eglynngordc: good question, maybe a business-y type in a suit? ... I dunno21:28
dhellmanndragondm: "bringing developers and users together"...21:28
gordcdhellmann: gotcha.21:28
dragondmheh, ok I guess there's a point there :->21:28
gordceglynn: i'll remember to lose the suit ;)21:28
*** vuil has quit IRC21:28
eglynnanyway last I heard our track runs from late Tuesday afternoon, thru' all day Wed, into Thursday morning21:29
eglynn(no doubt y'all are planning your schedules for the week ...)21:29
dhellmanneglynn: yeah, that's what it looks like on the latest layout form I've been given21:29
*** lbragstad has quit IRC21:29
eglynndhellmann: yep, partially clashing with oslo21:29
dhellmannI think we overlap for 5-6 sessions21:30
dragondmOy.21:30
dhellmannyeah, I won't be there for much of wednesday21:30
eglynndhellmann: so if that "Feature parity in storage drivers" session is approved21:30
*** luis_fdez has joined #openstack-meeting21:30
eglynndhellmann: (we'd want it to be shceduled for a non-overlap-with-oslo slot)21:30
dhellmannyeah, jd__ will have to juggle a bit21:30
eglynnyeap21:31
dhellmannas I've done for the sessions he proposed for oslo :-)21:31
dhellmannit looks like he has 6 slots to work with for that, so shouldn't be an issue21:31
eglynncool, intra-PTL horse trading ;)21:31
dhellmann:-)21:32
eglynnjust a quick reminder also that jd__, nijaba_ & myself are doing a conference session on ceilo+heat=alarming at 14.20 on Friday21:32
* dragondm is now imagining jd_- juggling horses...21:32
eglynn#link http://openstacksummitnovember2013.sched.org/event/02a1ea504b3dec538eaedca5e31461ed21:32
thomasemHow amusing!21:32
eglynn... we got the graveyard shift ;)21:33
*** jmontemayor has quit IRC21:33
gordceglynn: was just going to ask for link21:33
*** IlyaE has joined #openstack-meeting21:33
eglynnBTW do we want to pre-arrange a ceilo evening meet-up?21:33
eglynnI guess we could just glom onto the eNovance event on the thursday evening ...21:33
* eglynn is a freeloader ;)21:33
eglynn#link http://openstacksummitnovember2013.sched.org/event/6d7b3e0f9778fa675cd7f0ea56becba321:34
eglynnif memory serves we talked about doing a social event at Portland21:34
eglynnbut everyone had too many other parties to go to ...21:35
dhellmannwe could plan to meet at the enovance party :-)21:35
* gordc is down for a party.21:35
eglynncool, sounds like a plan21:35
dhellmannoops, should have read the backlog :-)21:35
* terriyu wonders what developer parties are like21:36
dragondmDepends on th budget :_>21:36
gordcterriyu: lasers.21:36
thomasemterriyu, unicorns21:36
eglynnyep a lot depends on the budget21:37
*** dscannell has quit IRC21:37
eglynnunicorns are expensive ;)21:37
terriyuare you guys going to pull that trick where you tell me to wear certain clothes and I'm only one who shows up to the party dressed that way?21:37
gordcthomasem: that's all you need unicorn and lasers :)... never been to one myself so looking forward to it.21:37
dragondmJust the horse mask.21:38
dhellmannhaha21:38
thomasemThis is the truth. Because if you can actually get a unicorn, you've probably already had enough to drink.21:38
dhellmannwe usually wear meter reader uniforms, right?21:38
thomasemLOL21:38
eglynnyep, with matching peaked caps, very fetching :)21:38
thomasemI just imagined that. It was amazing. Will y'all do a synchronized dance too?21:38
dhellmannooo, if not this time, definitely in the spring21:39
*** luis_fdez has quit IRC21:39
* dhellmann wants to see jd__ leading us in a line dance on stage21:39
* thomasem does too.21:39
eglynn#action jd__ choreograph a line dance for summit21:40
* dhellmann can't wait to hear jd__'s reaction after reading the meeting log from this week21:40
dhellmannhaha21:40
thomasemI'm sure it'll be grand. :)21:40
terriyusorry to lead everyone off topic, I guess this is what happens when jd__ is not here ;)21:40
dhellmanneglynn, did we have anything else on the agenda?21:40
eglynn#topic any other business21:40
*** openstack changes topic to "any other business (Meeting topic: ceilometer)"21:40
eglynnor open discussion as its known around these parts ...21:41
terriyuI saw something on the agenda about release python-ceilometerclient21:41
terriyuI don't know if that is still relevant21:41
*** lrengan has quit IRC21:41
dhellmannthat's a recurring topic21:41
dhellmannwe should verify that there's no need for an update, though21:41
eglynnah yes21:41
eglynn#topic release python-ceiloclient?21:41
dhellmannI don't think so, is there?21:41
*** openstack changes topic to "release python-ceiloclient? (Meeting topic: ceilometer)"21:41
eglynndon't thinks it's required21:41
dhellmannseconded21:41
eglynnthe patch to update the global requirements to 1.0.6 finally landed21:41
gordceglynn: something went in ... i don't remember what it was21:41
eglynnso that 1.0.6 could be pulled in by heat & ceilo itself21:42
eglynn(the latter for the alarm evaluator)21:42
gordceglynn: nm unit test fix.21:42
eglynngordc: a-ha ok21:42
*** whenry has joined #openstack-meeting21:42
eglynnso no need to re-release then for a test update21:43
gordcagreed21:43
*** marun has quit IRC21:43
eglynn#topic open discussion21:43
*** openstack changes topic to "open discussion (Meeting topic: ceilometer)"21:43
* eglynn has had fun this week kicking the tyres on the new horizon admin metering panel21:43
eglynnprops to lsmola for getting that landed for havana! :)21:43
eglynnfound a few nits but should all be nicely ironed out before 2013.2.121:44
*** dscannell has joined #openstack-meeting21:44
eglynn(i.e. first release off stable/havana)21:44
*** SumitNaiksatam has quit IRC21:44
lsmolaeglynn, cool21:44
thomasemOh, that's awesome. I'll have to go check that out.21:44
eglynnalso related to the UX ...21:44
eglynnone of the women-in-openstack intership ideas for icehouse is sparklines capturing the recent trend for resources21:45
terriyuis the new metering panel also in devstack?21:45
*** lrengan_ has quit IRC21:45
eglynn#link https://wiki.openstack.org/wiki/OutreachProgramForWomen/Ideas#Sparklines_in_Horizon21:45
dhellmanncool21:45
dhellmannterriyu: it should be, if it's in horizon21:45
eglynnterriyu: it's in havana, so defo on master21:45
lsmolaterriyu, yes I install it via devstack21:45
eglynnterriyu: (note though, admin only for now)21:45
eglynnterriyu: (not visible if you log in as a joe-soap user)21:46
terriyucool, thanks for the info guys21:46
terriyueglynn: cool intern project, thanks for pointing it out21:46
eglynnterriyu: yeah, could be quite neat visual candy for new users21:47
eglynn(possible on-ramp to more folks paying attention to ceilo ...)21:47
terriyueglynn: I hope one of the interns picks that project :)21:47
eglynnterriyu: yep, me too!21:48
lsmolait would be cool21:48
eglynnnot much else from me ...21:48
eglynnoh, one other thing21:48
terriyulsmola: since you're a mentor, you can drop by #openstack-opw and say hi to the applicants21:48
eglynnlast 'normal' release off stable/grizzly ... https://launchpad.net/ceilometer/+milestone/2013.1.421:48
eglynnfrom now on, stable/grizzly will prolly be limited to security fixes21:49
gordceglynn: did we resolve the havana wsme issue?21:49
lsmolaterriyu, I am already there, but i did't say hi :-)21:49
eglynnplease continue to tag havana bugs though for stable/havana if appropriate21:49
lsmolaterriyu, more like waiting for some questions :-)21:49
terriyulsmola: ok, I'll try to direct some applicants your way21:50
eglynngordc: we pinned the dependency version to < 5.5b6 IIRC21:50
lsmolaterriyu, ok, cool21:50
gordceglynn: ah cool cool. i'll take a look. i just remembered we had a bunch of havana patches sitting around.21:50
*** shardy is now known as shardy_afk21:51
eglynngordc: (that was on stable/grizzly that the wsme version is limited, on master we're up to latest I think)21:51
gordceglynn: right... i guess i was mostly wondering about this: https://review.openstack.org/#/c/52426/21:52
eglynngordc: here's the exact change https://review.openstack.org/#/c/52348/3/tools/pip-requires21:52
eglynngordc: ouch, didn;t realize that wasn't merged21:53
gordceglynn: yeah... i don't think we ever resolved stable/havana21:53
eglynngordc: OK, thanks for the heads-up, I'll look into that tmrw21:53
gordchttps://review.openstack.org/#/c/52602/ is just sitting there.21:54
gordc(apologies to everyone for bringing this up late... just remembered)21:54
gordceglynn: cool, i'll sync up with you on that tomorrow... see what we've decided.21:54
eglynnnp! I'll try to upick that gordian knot tmrw ...21:54
dhellmanngordc: better late than never!21:55
eglynnright-o, coming up near the end of our timeslot21:55
eglynnanything else anyone wants to raise?21:56
eglynngoing once ...21:56
eglynngoing twice ...21:56
*** chandankumar has joined #openstack-meeting21:56
eglynn#endmeeting ceilometer21:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:56
openstackMeeting ended Wed Oct 23 21:56:49 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-10-23-21.02.html21:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-10-23-21.02.txt21:56
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-10-23-21.02.log.html21:56
eglynnthanks folks!21:56
gordcsee yah later21:57
thomasemThanks. Take it easy!21:57
lsmolathank you, good night :-)21:57
*** gordc has left #openstack-meeting21:57
*** vijendar has quit IRC21:58
*** esker has quit IRC21:58
*** chandankumar has quit IRC21:58
*** thomasem has quit IRC21:58
*** chandankumar has joined #openstack-meeting21:59
*** SumitNaiksatam has joined #openstack-meeting21:59
*** dscannell has quit IRC22:01
*** atiwari has quit IRC22:01
*** SergeyLukjanov is now known as _SergeyLukjanov22:02
*** burt has quit IRC22:02
*** _SergeyLukjanov has quit IRC22:02
*** thedodd has quit IRC22:03
*** thedodd has joined #openstack-meeting22:04
*** SumitNaiksatam has quit IRC22:05
*** egallen has joined #openstack-meeting22:06
*** yfujioka has quit IRC22:07
*** anniec has quit IRC22:08
*** lsmola has quit IRC22:08
*** rakhmerov has joined #openstack-meeting22:08
*** chandankumar has quit IRC22:09
*** neelashah has quit IRC22:11
*** stevemar has quit IRC22:12
*** galstrom is now known as galstrom_zzz22:12
*** rakhmerov has quit IRC22:13
*** Linz has quit IRC22:13
*** rongze has joined #openstack-meeting22:15
*** sacharya has quit IRC22:15
*** whenry has quit IRC22:16
*** Linz has joined #openstack-meeting22:16
*** fbo_away is now known as fbo22:17
*** anniec has joined #openstack-meeting22:19
*** rongze has quit IRC22:20
*** mrodden has quit IRC22:20
*** jlucci has joined #openstack-meeting22:20
*** sushils has quit IRC22:22
*** joesavak has quit IRC22:27
*** stevemar has joined #openstack-meeting22:30
*** fbo is now known as fbo_away22:33
*** eharney has quit IRC22:33
*** elo has joined #openstack-meeting22:34
*** elo has quit IRC22:38
*** oubiwann has quit IRC22:40
*** SergeyLukjanov has joined #openstack-meeting22:41
*** rnirmal has quit IRC22:43
*** openstack has joined #openstack-meeting22:47
*** ChanServ sets mode: +o openstack22:47
*** eglynn has quit IRC22:47
*** stevemar has quit IRC22:52
*** changbl has joined #openstack-meeting22:54
*** herndon_ has joined #openstack-meeting22:57
*** SumitNaiksatam has joined #openstack-meeting22:57
*** markpeek has quit IRC22:59
*** krtaylor has quit IRC22:59
*** twoputt_ has quit IRC23:02
*** twoputt has quit IRC23:02
*** SumitNaiksatam has quit IRC23:08
*** rakhmerov has joined #openstack-meeting23:09
*** doron has joined #openstack-meeting23:10
*** dims has quit IRC23:11
*** changbl has quit IRC23:13
*** rongze has joined #openstack-meeting23:17
*** asalkeld is now known as asalkeld_lunch23:20
*** rongze has quit IRC23:21
*** shakayumi has quit IRC23:22
*** herndon_ has quit IRC23:23
*** dims has joined #openstack-meeting23:25
*** doron is now known as doron_afk23:27
*** sacharya has joined #openstack-meeting23:27
*** jrodom has joined #openstack-meeting23:28
*** jrodom has quit IRC23:28
*** SumitNaiksatam has joined #openstack-meeting23:28
*** julim has joined #openstack-meeting23:29
*** stevemar has joined #openstack-meeting23:31
*** topol has quit IRC23:31
*** doron_afk has quit IRC23:31
*** jodom has quit IRC23:32
*** julim has quit IRC23:33
*** twoputt has joined #openstack-meeting23:39
*** twoputt_ has joined #openstack-meeting23:39
*** changbl has joined #openstack-meeting23:41
*** rakhmerov has quit IRC23:42
*** zhhuabj_home has joined #openstack-meeting23:44
*** cdub_ has joined #openstack-meeting23:45
*** nermina has quit IRC23:46
*** fnaval_ has quit IRC23:49
*** changbl has quit IRC23:53
*** markpeek has joined #openstack-meeting23:53
*** krtaylor has joined #openstack-meeting23:56
*** whenry has joined #openstack-meeting23:57
*** dcramer_ has joined #openstack-meeting23:58

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