Wednesday, 2013-05-08

*** mgiles has joined #openstack-meeting00:00
*** morganfainberg has quit IRC00:06
*** mrodden has quit IRC00:06
*** manip has joined #openstack-meeting00:09
*** vipul is now known as vipul|away00:10
*** manip has quit IRC00:11
*** jaypipes has quit IRC00:12
*** ndipanov has quit IRC00:12
*** zhuadl has joined #openstack-meeting00:13
*** topol has quit IRC00:14
*** morganfainberg has joined #openstack-meeting00:14
*** markpeek has joined #openstack-meeting00:18
*** armax_ has joined #openstack-meeting00:19
*** armax_ has left #openstack-meeting00:19
*** hemna_ has joined #openstack-meeting00:19
*** cp16net_ has joined #openstack-meeting00:20
*** zhuadl has quit IRC00:20
*** edleafe has quit IRC00:20
*** cp16net has quit IRC00:20
*** kashyap has quit IRC00:20
*** cp16net_ is now known as cp16net00:20
*** gyee has quit IRC00:21
*** hemnafk has quit IRC00:21
*** Guest36352 has quit IRC00:21
*** edleafe has joined #openstack-meeting00:21
*** Guest36352 has joined #openstack-meeting00:21
*** kashyap has joined #openstack-meeting00:21
*** lloydde has quit IRC00:26
*** alexpilotti has quit IRC00:27
*** MarkAtwood has quit IRC00:31
*** vipul|away is now known as vipul00:32
*** jamespage_ has quit IRC00:39
*** esker has quit IRC00:40
*** shang has joined #openstack-meeting00:40
*** jamespage_ has joined #openstack-meeting00:42
*** dolphm has joined #openstack-meeting00:42
*** shang has quit IRC00:46
*** dolphm has quit IRC00:47
*** vipul is now known as vipul|away00:48
*** martine has joined #openstack-meeting00:50
*** vkmc has quit IRC00:50
*** fnaval has joined #openstack-meeting00:51
*** vipul|away is now known as vipul00:52
*** ayurchen has quit IRC00:53
*** ayurchen1 has joined #openstack-meeting00:53
*** maoy has joined #openstack-meeting00:55
*** salv-orlando has quit IRC00:55
*** lloydde has joined #openstack-meeting00:56
*** zhuadl has joined #openstack-meeting01:00
*** mgiles has quit IRC01:00
*** lloydde has quit IRC01:01
*** danwent has quit IRC01:02
*** reed has quit IRC01:12
*** zb has joined #openstack-meeting01:13
*** zaneb has quit IRC01:16
*** MarkAtwood has joined #openstack-meeting01:18
*** bdpayne has quit IRC01:21
*** arosen has quit IRC01:23
*** ryanpetrello has quit IRC01:28
*** martine has quit IRC01:29
*** terry7 has quit IRC01:37
*** topol has joined #openstack-meeting01:39
*** koolhead17 has joined #openstack-meeting01:57
*** lloydde has joined #openstack-meeting01:57
*** anniec has quit IRC02:00
*** lloydde has quit IRC02:02
*** stevemar has joined #openstack-meeting02:03
*** adjohn has quit IRC02:05
*** jkyle has quit IRC02:07
*** adalbas has quit IRC02:08
*** ayoung is now known as ayoung-gnight02:21
*** stevemar has quit IRC02:27
*** MarkAtwood has left #openstack-meeting02:35
*** woodspa has joined #openstack-meeting02:39
*** novas0x2a|laptop has quit IRC02:39
*** woodspa has quit IRC02:41
*** jbresnah has quit IRC02:43
*** sandywalsh has quit IRC02:43
*** ivasev has joined #openstack-meeting02:47
*** sandywalsh has joined #openstack-meeting02:56
*** mrodden has joined #openstack-meeting02:57
*** lloydde has joined #openstack-meeting02:58
*** SumitNaiksatam has quit IRC03:02
*** lloydde has quit IRC03:02
*** mgiles has joined #openstack-meeting03:06
*** adjohn has joined #openstack-meeting03:15
*** novas0x2a|laptop has joined #openstack-meeting03:16
*** SumitNaiksatam has joined #openstack-meeting03:18
*** adjohn_ has joined #openstack-meeting03:19
*** adjohn has quit IRC03:20
*** mattray has joined #openstack-meeting03:23
*** esker has joined #openstack-meeting03:24
*** esker has quit IRC03:24
*** esker has joined #openstack-meeting03:25
*** martine has joined #openstack-meeting03:41
*** adjohn_ has quit IRC03:44
*** martine has quit IRC03:49
*** amyt has joined #openstack-meeting03:52
*** mattray has quit IRC03:55
*** amyt has quit IRC03:55
*** boris-42 has joined #openstack-meeting03:56
*** amyt has joined #openstack-meeting03:57
*** lloydde has joined #openstack-meeting03:59
*** lloydde has quit IRC04:03
*** zhuadl has quit IRC04:06
*** amyt has quit IRC04:06
*** adjohn has joined #openstack-meeting04:06
*** adjohn has quit IRC04:06
*** amyt has joined #openstack-meeting04:07
*** esker has quit IRC04:07
*** blamar has quit IRC04:08
*** dwcramer has quit IRC04:08
*** stevemar has joined #openstack-meeting04:08
*** garyk has joined #openstack-meeting04:09
*** adjohn has joined #openstack-meeting04:09
*** esker has joined #openstack-meeting04:12
*** amyt has quit IRC04:12
*** amyt has joined #openstack-meeting04:13
*** stevemar has quit IRC04:14
*** SergeyLukjanov has joined #openstack-meeting04:15
*** glikson has joined #openstack-meeting04:16
*** esker has quit IRC04:19
*** stevemar has joined #openstack-meeting04:20
*** amyt has quit IRC04:20
*** amyt has joined #openstack-meeting04:21
*** vipul is now known as vipul|away04:21
*** mgiles has quit IRC04:22
*** vipul|away is now known as vipul04:24
*** amyt has quit IRC04:24
*** boris-42 has quit IRC04:24
*** amyt has joined #openstack-meeting04:25
*** blamar has joined #openstack-meeting04:26
*** danwent has joined #openstack-meeting04:29
*** koolhead17 has quit IRC04:33
*** amyt has quit IRC04:33
*** amyt has joined #openstack-meeting04:34
*** maurosr has quit IRC04:34
*** maurosr has joined #openstack-meeting04:34
*** esker has joined #openstack-meeting04:38
*** garyk has quit IRC04:41
*** amyt has quit IRC04:41
*** amyt has joined #openstack-meeting04:42
*** amyt has quit IRC04:44
*** ivasev has quit IRC04:44
*** boris-42 has joined #openstack-meeting04:44
*** koolhead17 has joined #openstack-meeting04:46
*** vipul is now known as vipul|away04:53
*** maoy has quit IRC04:55
*** esker has quit IRC04:56
*** esker has joined #openstack-meeting04:57
*** FnordDownUnder has joined #openstack-meeting04:58
*** esker has quit IRC05:03
*** stevemar has quit IRC05:05
*** adjohn has quit IRC05:07
*** koolhead17 has quit IRC05:08
*** sacharya has quit IRC05:10
*** boris-42 has quit IRC05:15
*** jamespage_ has quit IRC05:17
*** markpeek has quit IRC05:17
*** PeTeT has quit IRC05:31
*** marun has quit IRC05:32
*** SergeyLukjanov has quit IRC05:49
*** jbresnah has joined #openstack-meeting05:58
*** jbresnah has left #openstack-meeting06:03
*** esker has joined #openstack-meeting06:07
*** lloydde has joined #openstack-meeting06:07
*** mrunge has joined #openstack-meeting06:09
*** MarkAtwood has joined #openstack-meeting06:09
*** lloydde has quit IRC06:10
*** esker has quit IRC06:11
*** garyk has joined #openstack-meeting06:12
*** nati_ueno has joined #openstack-meeting06:14
*** MarkAtwood has quit IRC06:21
*** danwent has quit IRC06:25
*** Mandell has joined #openstack-meeting06:28
*** boris-42 has joined #openstack-meeting06:30
*** afazekas has joined #openstack-meeting06:36
*** FnordDownUnder has quit IRC06:38
*** flaper87 has joined #openstack-meeting06:45
*** luis_fdez has quit IRC06:47
*** boris-42 has quit IRC06:59
*** glikson has quit IRC07:01
*** boris-42 has joined #openstack-meeting07:02
*** ayurchen1 has quit IRC07:06
*** ayurchen has joined #openstack-meeting07:07
*** zb is now known as zaneb07:09
*** topol has quit IRC07:10
*** alexpilotti has joined #openstack-meeting07:13
*** glikson has joined #openstack-meeting07:18
*** eglynn has joined #openstack-meeting07:26
*** Mandell has quit IRC07:33
*** nati_ueno has quit IRC07:43
*** kpavel has quit IRC07:49
*** kpavel has joined #openstack-meeting07:49
*** kpavel_ has joined #openstack-meeting07:51
*** kpavel has quit IRC07:55
*** kpavel_ is now known as kpavel07:55
*** MarkAtwood has joined #openstack-meeting07:55
*** salv-orlando has joined #openstack-meeting07:57
*** jog0 has quit IRC08:01
*** MarkAtwood has quit IRC08:02
*** SergeyLukjanov has joined #openstack-meeting08:27
*** kpavel_ has joined #openstack-meeting08:36
*** kpavel has quit IRC08:38
*** kpavel_ is now known as kpavel08:38
*** SergeyLukjanov has quit IRC08:45
*** johnthetubaguy has joined #openstack-meeting08:45
*** SergeyLukjanov has joined #openstack-meeting08:55
*** obondarev_ has joined #openstack-meeting09:04
*** mkollaro has joined #openstack-meeting09:09
*** ociuhandu_ has joined #openstack-meeting09:09
*** cyeoh_ has joined #openstack-meeting09:10
*** esmute_ has joined #openstack-meeting09:11
*** iccha has joined #openstack-meeting09:12
*** notmyname_ has joined #openstack-meeting09:12
*** llu_linux is now known as llu09:12
*** jcooley_ has joined #openstack-meeting09:13
*** saschpe_ has joined #openstack-meeting09:14
*** uvirtbot has quit IRC09:14
*** saschpe has quit IRC09:14
*** lcheng has quit IRC09:14
*** egallen has joined #openstack-meeting09:14
*** obondarev has quit IRC09:14
*** n0ano has quit IRC09:14
*** jcooley has quit IRC09:14
*** notmyname has quit IRC09:14
*** notmyname_ is now known as notmyname09:14
*** jcooley_ is now known as jcooley09:14
*** uvirtbot has joined #openstack-meeting09:15
*** pleia2 has quit IRC09:15
*** pleia2 has joined #openstack-meeting09:15
*** lcheng has joined #openstack-meeting09:15
*** ociuhandu has quit IRC09:21
*** briancline has quit IRC09:21
*** cyeoh has quit IRC09:21
*** esmute has quit IRC09:21
*** iccha__ has quit IRC09:21
*** ociuhandu_ is now known as ociuhandu09:21
*** esmute_ is now known as esmute09:21
*** egallen has quit IRC09:32
*** alexxu has quit IRC09:33
*** SergeyLukjanov has quit IRC09:41
*** SergeyLukjanov has joined #openstack-meeting09:43
*** esker has joined #openstack-meeting09:59
*** alexpilotti has quit IRC10:06
*** boris-42 has quit IRC10:10
*** pcm___ has joined #openstack-meeting10:14
*** pcm___ has quit IRC10:14
*** pcm__ has joined #openstack-meeting10:15
*** afazekas has quit IRC10:16
*** SergeyLukjanov has quit IRC10:19
*** rnirmal has joined #openstack-meeting10:28
*** afazekas has joined #openstack-meeting10:29
*** SergeyLukjanov has joined #openstack-meeting10:30
*** briancline has joined #openstack-meeting10:30
*** jcoufal has joined #openstack-meeting10:39
*** mgiles has joined #openstack-meeting10:49
*** SergeyLukjanov has quit IRC10:54
*** jcoufal has quit IRC10:59
*** acfleury has joined #openstack-meeting11:02
*** esker has quit IRC11:04
*** esker has joined #openstack-meeting11:05
*** yamahata_ has joined #openstack-meeting11:05
*** ndipanov has joined #openstack-meeting11:13
*** esker has quit IRC11:19
*** esker has joined #openstack-meeting11:20
*** SergeyLukjanov has joined #openstack-meeting11:22
*** dhellmann-away has quit IRC11:23
*** martine has joined #openstack-meeting11:28
*** boris-42 has joined #openstack-meeting11:35
*** maoy has joined #openstack-meeting11:40
*** ladquin_brb is now known as ladquin11:42
*** yamahata_ has quit IRC11:50
*** topol has joined #openstack-meeting11:52
*** SergeyLukjanov has quit IRC11:55
*** matiu has quit IRC12:00
*** dprince has joined #openstack-meeting12:03
*** mrunge has quit IRC12:05
*** matiu has joined #openstack-meeting12:08
*** matiu has quit IRC12:08
*** matiu has joined #openstack-meeting12:08
*** SergeyLukjanov has joined #openstack-meeting12:08
*** eglynn has quit IRC12:18
*** radez_g0n3 is now known as radez12:23
*** yamahata_ has joined #openstack-meeting12:28
*** zhuadl has joined #openstack-meeting12:28
*** ayoung-gnight is now known as ayoung12:29
*** zhuadl has quit IRC12:33
*** martine has quit IRC12:34
*** zhuadl has joined #openstack-meeting12:35
*** jecarey has joined #openstack-meeting12:37
*** dosaboy has quit IRC12:37
*** dosaboy has joined #openstack-meeting12:39
*** martine_ has joined #openstack-meeting12:43
*** salv-orlando has quit IRC12:48
*** salv-orlando has joined #openstack-meeting12:48
*** eglynn has joined #openstack-meeting12:53
*** dprince has quit IRC13:01
*** dprince has joined #openstack-meeting13:02
*** esker has quit IRC13:04
*** eglynn is now known as hungry-eglynn13:09
*** mkollaro has quit IRC13:17
*** anniec has joined #openstack-meeting13:22
*** robertmyers has joined #openstack-meeting13:23
*** stevemar has joined #openstack-meeting13:25
*** lbragstad has joined #openstack-meeting13:25
*** johnthetubaguy has quit IRC13:28
*** SergeyLukjanov has quit IRC13:32
*** SergeyLukjanov has joined #openstack-meeting13:34
*** jbartels_ has joined #openstack-meeting13:34
*** sandywalsh has quit IRC13:37
*** ociuhandu has quit IRC13:39
*** jbartels_ has quit IRC13:40
*** martine_ has quit IRC13:40
*** ociuhandu has joined #openstack-meeting13:40
*** martine has joined #openstack-meeting13:40
*** ivasev has joined #openstack-meeting13:42
*** esker has joined #openstack-meeting13:42
*** esker has quit IRC13:45
*** alexpilotti has joined #openstack-meeting13:47
*** jbartels_ has joined #openstack-meeting13:49
*** hungry-eglynn is now known as eglynn13:50
*** markpeek has joined #openstack-meeting13:50
*** sandywalsh has joined #openstack-meeting13:51
*** sacharya has joined #openstack-meeting13:51
*** alexpilotti has quit IRC13:52
*** ryanpetrello has joined #openstack-meeting13:54
*** lloydde has joined #openstack-meeting13:54
*** jaypipes has joined #openstack-meeting13:54
*** martine_ has joined #openstack-meeting13:54
*** martine has quit IRC13:54
*** sacharya has quit IRC13:55
*** gongysh has quit IRC14:02
*** Guest36352 has quit IRC14:04
*** jcru has joined #openstack-meeting14:04
*** hanney has joined #openstack-meeting14:05
*** dolphm has joined #openstack-meeting14:05
*** rushiagr has joined #openstack-meeting14:05
*** jbartels_ has quit IRC14:07
*** martine_ has quit IRC14:08
*** martine has joined #openstack-meeting14:13
*** shanewang has joined #openstack-meeting14:16
*** zhuadl has quit IRC14:16
*** sacharya has joined #openstack-meeting14:19
*** jcoufal has joined #openstack-meeting14:21
*** amyt has joined #openstack-meeting14:25
*** shanewang has left #openstack-meeting14:25
*** AlanClark has joined #openstack-meeting14:30
*** topol has quit IRC14:33
*** sacharya has quit IRC14:33
*** imsplitbit has left #openstack-meeting14:33
*** matiu has quit IRC14:33
*** esker has joined #openstack-meeting14:34
*** ayoung is now known as ayoung-afk14:35
*** hanney has quit IRC14:35
*** markmcclain has joined #openstack-meeting14:36
*** dwcramer has joined #openstack-meeting14:37
*** ndipanov has quit IRC14:39
*** ndipanov has joined #openstack-meeting14:41
*** david-lyle has left #openstack-meeting14:42
*** lloydde has quit IRC14:43
*** dwcramer has quit IRC14:43
*** cp16net is now known as cp16net|away14:46
*** spzala has joined #openstack-meeting14:47
*** johnthetubaguy has joined #openstack-meeting14:49
*** kebray has joined #openstack-meeting14:49
*** ashwini has joined #openstack-meeting14:51
*** jbartels_ has joined #openstack-meeting14:52
*** litong has joined #openstack-meeting14:54
*** armax has joined #openstack-meeting14:54
*** tong|2 has joined #openstack-meeting14:56
*** tong|3 has joined #openstack-meeting14:57
*** litong has quit IRC14:59
johnthetubaguy#startmeeting XenAPI15:00
openstackMeeting started Wed May  8 15:00:53 2013 UTC.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: XenAPI)"15:00
openstackThe meeting name has been set to 'xenapi'15:00
johnthetubaguyhello, everyone15:01
johnthetubaguywho is around for the meeting?15:01
*** tong|2 has quit IRC15:01
* BobBall is15:01
*** matelakat has joined #openstack-meeting15:01
matelakathi15:01
BobBallNot sure if Mate can join us tod... hi Mate15:01
johnthetubaguycool15:01
matelakatI will be here, just in case :-)15:02
* johnthetubaguy will be back in 30 seconds15:02
*** woodspa has joined #openstack-meeting15:02
johnthetubaguyanyone got things they want to add to the agenda in the wiki?15:02
johnthetubaguy#link https://wiki.openstack.org/wiki/Meetings/XenAPI15:02
toansteri'm here15:02
johnthetubaguyalso note the additional info about how we organise the group, will bring that up in the open disscussion15:02
johnthetubaguytoanster: hey!15:03
matelakatI think it's worth mentioning, that I created a blueprint to clean-up xenapi code in devstack.15:03
*** otherwiseguy has quit IRC15:03
matelakatI added you guys to that bp.15:03
BobBallCould wait until the blueprints section for that Mate ;)15:03
matelakatSorry.15:03
BobBallBut that's fine!15:03
*** esker has quit IRC15:04
BobBallI guess the Agenda needs updating - it's still got some stuff from the last meeting hasn't it?15:04
*** hanney has joined #openstack-meeting15:04
johnthetubaguyyup, my bad15:04
*** sacharya has joined #openstack-meeting15:04
johnthetubaguywell, lets get cracking15:04
johnthetubaguy#agenda blueprints15:05
johnthetubaguy#topic blueprints15:05
*** openstack changes topic to "blueprints (Meeting topic: XenAPI)"15:05
johnthetubaguyso, we had a good summit session15:05
johnthetubaguy#link https://etherpad.openstack.org/HavanaXenAPIRoadmap15:05
johnthetubaguyI skipped stuff from the last meeting, it was too long again15:05
BobBallagreed15:06
johnthetubaguyThere are lots of blueprints15:06
johnthetubaguyBobBall and matelakat recently signed up to quite a few15:06
johnthetubaguyare the any more that people don't see as target for havana, but really should be?15:06
BobBallI think the main issue for Havana is getting the quantum+OVS integration working15:07
matelakatlet me see if the devstack one is targeted properly15:07
BobBallwhich isn't a blueprint(?) but is something that we're looking at too15:07
*** jbartels_ is now known as jasonb15:07
*** topol has joined #openstack-meeting15:07
johnthetubaguyshould it be a blueprint?15:07
matelakat#link https://blueprints.launchpad.net/devstack/+spec/xenapi-devstack-cleanup15:07
johnthetubaguyI guess it is in quantum?15:08
matelakatNot just quantum.15:08
BobBallProbably not.  The Quantum integration is more of a bug than a blueprint-needed?  I thought blueprints were for things that needed tracking+discussion on implementation?15:08
johnthetubaguywell, it probably needs docs and stuff15:08
BobBallSorry Mate - I guess we're talking at cross purposes atm!15:09
*** jasonb has quit IRC15:09
johnthetubaguyand it is a feature to be mentioned when the release goes out15:09
johnthetubaguyoh, not a nova blueprint15:09
BobBall*nod*15:09
matelakatCould you guys fire up a browser, and see if that bp is targeted or not?15:09
*** esker has joined #openstack-meeting15:09
BobBallit is not targeted15:09
johnthetubaguyits not15:09
matelakatI can't see Havana anywhere15:09
*** esker has quit IRC15:09
matelakatWhich field needs to be set?15:09
johnthetubaguynot sure devstack use blueprints like you would hope15:09
johnthetubaguyseries goal should be havana, but its quite project specific15:09
johnthetubaguyI wouldn't worry for now15:10
*** lloydde has joined #openstack-meeting15:10
johnthetubaguyOk… so back to quantum support15:10
johnthetubaguyhow it that looking?15:10
matelakatYes, I am looking at it.15:10
johnthetubaguyany update worth sharing?15:10
*** jcoufal has quit IRC15:10
BobBallProbably just that the instructions don't seem to work :)15:11
johnthetubaguyOK, I guess stuff changed, or its broken15:11
matelakatA rebase will be needed.15:11
BobBallProbably some setup that Maru had that doesn't match our setup15:11
matelakatI am on it, expecting to have something this week.15:11
johnthetubaguyOK15:11
BobBallMate hasn't got to the bottom of it yet though15:11
johnthetubaguyno worries15:12
matelakatIt's again the exotic network setup.15:12
*** lloydde has quit IRC15:12
johnthetubaguyso, I wanted to raise the blueprints we are tracking for Havana15:12
matelakatHowever, I am just getting rid of that.15:12
johnthetubaguyOK15:12
BobBallHe's not allowed to eat until he's figured it out though, so I'm sure we'll get the answer soon.15:12
matelakatI am starving.15:12
johnthetubaguylol15:12
johnthetubaguyyour new wife is very harsh...15:13
johnthetubaguyanyway...15:13
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/xenapi-move-driver-to-oslo15:13
BobBallok - drive away John.  I guess we should look at https://blueprints.launchpad.net/devstack/+spec/xenapi-devstack-cleanup to make sure we all agree with the plan too - even though it's not a nova blueprint :)15:13
johnthetubaguymate has taken this one15:13
johnthetubaguyOK, lets have a quick look at devstack15:13
johnthetubaguywe didn't cover that in the summit15:13
*** koolhead17 has joined #openstack-meeting15:13
matelakatI can do that, the issue is the review speed15:13
matelakatThat kills me.15:14
*** markmcclain has quit IRC15:14
johnthetubaguyyup, I hear you15:14
BobBallyeah... takes ages to get people to review and there are far too many minor -1's!15:14
*** vkmc has joined #openstack-meeting15:14
*** vkmc has joined #openstack-meeting15:14
BobBalltoo many cooks, coding by compromise and all of that ;)15:14
johnthetubaguywell, I am for clean code, but yes, I hear you15:15
johnthetubaguythe problem is that code is such a mess its hard to concentrate15:15
johnthetubaguybut anyway15:15
johnthetubaguythe approach15:15
johnthetubaguynot sure I understand where the blueprint is talking15:15
johnthetubaguyseparate stuff out?15:15
matelakatThe expected output is a usable devstack15:16
BobBallindeed - so Mate want's to simplify the XenAPI devstack process - but it'll probably contain some ugly bits of code too, even though it'll be an improvement on what's there at the moment.15:16
johnthetubaguyOK, but whats the approach?15:16
matelakatIsn't it on the bp?15:16
johnthetubaguyI see you list the steps15:16
matelakatDo we need to discuss it?15:16
BobBalldo you mean the steps or the work items?15:17
johnthetubaguyjust want to make sure expectations are good15:17
matelakatIt's like you touch here, and you see soo many things, that you just can't resist cleaning it up.15:17
johnthetubaguyso you pulling it out into a separate file?15:17
*** garyk has quit IRC15:17
johnthetubaguythe hypervisor bit vs VM creation, etc15:17
matelakatSeparate files/ functions, doesn't matter.15:18
matelakatMake those steps visible15:18
johnthetubaguyits just devstack was meant to be a very simple single script people can read as an example way to set things up15:18
matelakatMake the code readable.15:18
johnthetubaguyany clearly things have moved a bit since then15:18
johnthetubaguyOK, that all good, just its was designed as lightweight scripts, not super DRY code15:18
johnthetubaguyI agree there is lots to do15:19
johnthetubaguywas just wondering what you planned to focus on15:19
johnthetubaguyyou mention the variables and the settings15:19
johnthetubaguyit would be good to shake those into something more sensible15:19
matelakatI think as you suggested: more visible data flow15:20
johnthetubaguyOK15:20
matelakatI don't want to over-architect the stuff.15:20
*** maoy has quit IRC15:20
*** zul has joined #openstack-meeting15:20
johnthetubaguymaybe we should just see code, I will review the change you posted15:20
*** jamespage_ has joined #openstack-meeting15:20
johnthetubaguylets move on15:20
matelakatSo at the moment kicking the tyres, and doing the tidy-up.15:20
matelakatok, thanks.15:20
*** vincent_hou has joined #openstack-meeting15:20
johnthetubaguywe mentioned oslo split out15:21
*** maoy has joined #openstack-meeting15:21
johnthetubaguymate was taking that H-2 timeframe15:21
johnthetubaguywe discussed that at the summit15:21
johnthetubaguyall seems15:21
*** ayoung-afk is now known as ayoung15:21
johnthetubaguygood15:21
johnthetubaguymoving on...15:21
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/xenapi-compute-driver-events15:21
johnthetubaguyusing events to help update db and parent cell quicker15:21
johnthetubaguybobball took that one, for H-215:22
johnthetubaguyagain, that all seems good?15:22
BobBallI did - but my understanding is it's a nice-to-have15:22
BobBallPriorities might push it to H-315:22
*** danwent has joined #openstack-meeting15:22
johnthetubaguyIndeed, I think so15:22
johnthetubaguymaybe move it to H-315:23
johnthetubaguyOK, next...15:23
BobBallI'd like to leave it at H-2 for now though15:23
johnthetubaguyOK15:23
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/xenapi-guest-agent-cloud-init-interop15:23
*** lloydde has joined #openstack-meeting15:23
johnthetubaguyRick harris and I are trying to get cloud-init and config drive working better with XenAPI15:23
johnthetubaguybasically making the agent more optional15:23
johnthetubaguylike per VM or per image optional15:24
BobBallBrilliant - did you see the email thread on -dev about config drive?15:24
johnthetubaguyprobably not yet… if it was recent15:24
BobBallsubject "making file injection optional / removing it"15:24
*** boris-42 has quit IRC15:24
BobBallStarted talking about baremetal - but now moved onto config drive and fun things like that15:24
matelakatYeah, that could be related.15:24
johnthetubaguyoh, OK, its related15:25
*** jamespage_ has quit IRC15:25
BobBalljust thought you'd probably want to reply, given what you're doing, so bringing it to your attention :)15:25
johnthetubaguycool, thanks, not read through that all yet today15:25
johnthetubaguybug day fun15:25
matelakatfile inject/agent/configdrive trinity15:25
johnthetubaguyindeed, its a fun thing15:25
johnthetubaguymy view is cloud-init and cloudbase-init15:25
johnthetubaguythen make an extra agent for password without reboot if really needed15:26
*** adjohn has joined #openstack-meeting15:26
johnthetubaguymaybe extend cloud-init to do licence stuff15:26
johnthetubaguyetc etc15:26
johnthetubaguyanyways, we are on the case15:26
johnthetubaguy:-)15:26
*** robertmyers has left #openstack-meeting15:26
johnthetubaguy… so stuff that is on the maybe list15:27
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/xenapi-server-log15:27
*** SergeyLukjanov has quit IRC15:27
johnthetubaguywe need to decide if we want the server log in XenAPI15:27
*** mrodden has quit IRC15:27
johnthetubaguyI am tempted to kill it, or at least make the client discover if it is available15:27
BobBallclient discover?15:28
johnthetubaguybut it looks like there is a xenstore key + logrotate that could make it all work15:28
johnthetubaguynova-client can find out if the feature is enabled in the cloud15:28
johnthetubaguypart of the nova v3 API work15:28
johnthetubaguywell it could be, anyway15:28
BobBallOh right - because we just return a dummy console log atm15:28
johnthetubaguyyup15:28
johnthetubaguyit could be an extention that is enabled or not15:29
johnthetubaguyanyways15:29
johnthetubaguyI don't like the idea of filling up dom0 disk if a guest gets very chatty15:29
johnthetubaguyand there are some funky ways around that15:29
BobBallDo you know how that works in the KVM world?15:29
BobBall... or A.N.Other hypervisor's world that supports console log :)15:29
johnthetubaguylibvirt manages most of it, but I need to look closer15:30
*** garyk has joined #openstack-meeting15:30
johnthetubaguylibvirt may have code for xen anyways15:30
*** cp16net|away is now known as cp16net15:30
BobBallah - so perhaps libvirt treats it as a ring and only returns those lines directly.15:30
johnthetubaguyI have put it on my pile, but not targeted it for H15:30
johnthetubaguyso if others want it, ping me!15:30
johnthetubaguylets move on...15:30
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/xenapi-vif-hotplug15:31
johnthetubaguy#action we need a volunteer for xenapi-vif-hotplug15:31
johnthetubaguyif we want it done in H15:31
johnthetubaguyits a gap we have vs libvirt15:31
johnthetubaguyits seems more important / useful than some of the other gaps15:31
BobBallshoudl use #help for this one :) *been reading the meetbot commands*15:31
BobBall#help  need a volunteer for xenapi-vif-hotplug15:32
johnthetubaguyoh cool, I forgot about that one15:32
johnthetubaguyno one fancies it here I guess?15:32
matelakatIt's not that I don't like it.15:33
matelakatIt's the tome.15:33
matelakattime15:33
johnthetubaguywell according to the current plans, there will be loads of us free in H-315:33
johnthetubaguylol15:33
johnthetubaguyOK, lets move on from blueprint15:33
BobBallindeed15:33
johnthetubaguyunless people have something else?15:33
BobBallwe should have time by H-3 but it's impossible to commit atm15:33
johnthetubaguyso, going forward I would love to see progress reports in this meeting15:34
johnthetubaguybut code is good too...15:34
johnthetubaguy#topic docs15:34
BobBall*continues to read meetbot logs*15:34
*** openstack changes topic to "docs (Meeting topic: XenAPI)"15:34
BobBall#chair BobBall15:34
johnthetubaguymean15:34
BobBallno - you're permanent chair15:34
johnthetubaguyI guess I could probably transfer15:34
BobBallI was testing if we could then use this when someone's nick goes15:34
BobBallno15:34
BobBallI don't want it :)15:34
BobBall#chair matelakat15:35
johnthetubaguyhehe15:35
johnthetubaguyso, docs15:35
BobBalldoesn't seem to work anyway15:35
matelakatwow15:35
BobBallmaybe you have to do it john15:35
BobBallyes - docs15:35
johnthetubaguyany updates?15:35
johnthetubaguyI suspect it has to be me15:35
*** vipul|away is now known as vipul15:35
matelakatNo updates on docs side15:35
johnthetubaguyme neigther15:35
BobBallthe docs don't say so http://meetbot.debian.net/Manual.html - so maybe we need an action to update the meetbot docs!15:35
johnthetubaguy#topic Bugs and QA15:35
*** openstack changes topic to "Bugs and QA (Meeting topic: XenAPI)"15:35
johnthetubaguyso its bug day15:35
johnthetubaguybut smokestack15:36
johnthetubaguyany news on how that is going?15:36
BobBallI haven't poked Dan or Ant on it15:36
*** fnaval has quit IRC15:36
BobBallI've got a timed action to poke Dan by the end of this week for his backup task15:36
johnthetubaguy#action BobBall to poke Dan and Ant15:36
*** ryanpetrello has quit IRC15:36
johnthetubaguycool15:36
*** vipul is now known as vipul|away15:36
johnthetubaguyI guess it is post quantum work?15:36
*** SergeyLukjanov has joined #openstack-meeting15:36
*** fnaval has joined #openstack-meeting15:37
BobBallWe're blocked on Ant re-installing with 6.1 (which is blocked by Dan backing up the VM) - but yes, it's post-quantum, which is why I haven't been pushing uber hard15:37
johnthetubaguygotcha15:37
johnthetubaguyits bug day15:37
johnthetubaguyI did some triage15:37
johnthetubaguyworking on a few little fellas15:37
BobBallHappy Bug Day!15:37
*** johnpur has joined #openstack-meeting15:37
matelakatI was not doing bugs today.15:37
johnthetubaguymatelakat: what does your magic bug finder tell us?15:37
matelakatI must confess.15:38
johnthetubaguycan we have the URL again?15:38
matelakatyou can, but it's outdated.15:38
*** chuck_ has joined #openstack-meeting15:38
BobBallI also helped John with a couple of them, and worked on some potential bugs that haven't been reported yet - in XenAPI but reported by rackspace and trying to identify whether they are XenAPI or OpenStack "bugs"15:38
matelakat#link https://github.com/citrix-openstack/bugstat/blob/master/bugreport/main_report.md15:39
matelakatI will update it for the next time.15:39
johnthetubaguy+1 thanks for your help on those15:39
*** zul has quit IRC15:40
johnthetubaguycool, so I just used the tagged bugs15:40
BobBall#action matelakat to update https://github.com/citrix-openstack/bugstat/blob/master/bugreport/main_report.md :)15:40
johnthetubaguytagged with xenserver15:40
johnthetubaguyI will take a look at the others sometime15:40
johnthetubaguy#action matelakat to document bug finder in XenAPI team wiki15:40
johnthetubaguycool15:40
johnthetubaguyany more for any more?15:40
* johnthetubaguy checking bug list...15:40
*** fnaval has quit IRC15:41
matelakatThanks for the actions.15:41
johnthetubaguyOK, no more news for me15:41
johnthetubaguyhey, what are friends for :-P15:41
*** gyee has joined #openstack-meeting15:41
BobBallYou were looking bored Mate.15:41
matelakatAnd if you have such friends, you don't need enemies.15:41
BobBall:)15:42
johnthetubaguyyou took the works out of my… keyboard15:42
johnthetubaguyso, moving on15:42
johnthetubaguy#topic AOB15:42
*** openstack changes topic to "AOB (Meeting topic: XenAPI)"15:42
johnthetubaguyany other bussiness...15:42
johnthetubaguyI think the silly english term15:42
johnthetubaguylike^15:42
johnthetubaguylol15:42
johnthetubaguybad keyboard15:43
johnthetubaguyso, sub team, it turns out we are sub team15:43
johnthetubaguyno need to panic...15:43
johnthetubaguynothing changes15:43
johnthetubaguyI tried to document what we do in the wiki15:43
BobBallexcept other people are now copying us :( haha15:43
johnthetubaguyhehe15:43
*** eharney has joined #openstack-meeting15:43
*** otherwiseguy has joined #openstack-meeting15:44
matelakatNext meeting?15:44
johnthetubaguyyou mean like people who sell non-opensource hypervisors15:44
matelakatbi weekly?15:44
johnthetubaguywell I would be keen on keeping it weekly for the rest of May15:44
johnthetubaguyand see if there is any content in the meeting15:44
johnthetubaguythen move to bi weekly?15:44
BobBallI didn't realise there were other non-opensource hypervisors ;)15:44
johnthetubaguyBobBall: you must have the Citrix goggles on15:45
johnthetubaguywe can try next week, and see how it goes?15:45
BobBallI have, indeed, dunk the kool-aid.15:45
johnthetubaguyI am keen there is somewhere for users to drop in an annoy the dev team15:46
BobBallI think next week we'll talk through the bugs and probably have a decent amount to talk about on Quantum?15:46
BobBallso next week should be fine.15:46
johnthetubaguythat seems fair15:46
matelakatOK15:46
johnthetubaguywell, I good doing it week by week15:46
BobBallokiedokie15:46
johnthetubaguyI am good with us voting at the beginning of the meeting to not have the meeting15:46
johnthetubaguyit only takes 2 mins15:47
BobBallDamn.  Wish I knew that at the start of this meeting.15:47
johnthetubaguyshould not be too disruptive15:47
matelakatPlease, don't.15:47
*** jcoufal has joined #openstack-meeting15:47
johnthetubaguydon't what?15:47
matelakatthe voting.15:47
johnthetubaguywhy?15:47
matelakatI mean, OK, if you want it, OK.15:47
matelakatI was just joking.15:47
johnthetubaguysimple check to see if the agent is empty, and one has anything15:47
johnthetubaguylol15:48
johnthetubaguyare we all good?15:48
matelakaty15:48
BobBallI'm better than good15:48
rnirmalI have a question...    > 2TB disk.. is it just a limitation with xenserver or kvm and others as well ?15:48
johnthetubaguyVHD limitation I think15:48
BobBallthe >2TB disk is a VHD limitation15:48
BobBallindeed15:48
johnthetubaguyother may have it too15:48
matelakatisn't it the partition table?15:48
BobBalldo you know the qcow2 limitation?15:48
johnthetubaguynope15:48
BobBallpartition table can be fixed using gpt15:48
* johnthetubaguy googles...15:48
rnirmalok cool thanks guys15:49
BobBalllooks like qcow2 uses a 64-bit integer for the size15:49
rnirmalhas anyone thought about creating > 2TB disk on vms.. ephemeral or otherwise15:49
BobBallyes rnirmal - but the only way to do that if you're using VHD-backed storage is to use raid in-guest15:49
johnthetubaguynot seen anyone try15:50
johnthetubaguywhat about raw LVM?15:50
rnirmalhmm15:50
*** mrodden has joined #openstack-meeting15:50
johnthetubaguyyou could use that for ephemeral I guess, or PCI passthrough15:50
*** lloydde has quit IRC15:50
rnirmalbut that will have to be done outside of nova provisioning right ?15:50
johnthetubaguybut obviously you need to do things like scrub disks when passing between tenants15:50
BobBallindeed15:50
johnthetubaguywell one could change nova to cope with it15:50
johnthetubaguyephemeral are just empty, so that bit is easy ish15:51
rnirmalso we are using ephemeral disk.. and want to create more than 2 TB15:51
johnthetubaguyyou could do raw files (loop back) inside the EXT SR15:51
johnthetubaguyand create them inside nova15:51
johnthetubaguybut it is a code change15:52
rnirmalhow would I do that.. ah ok15:52
* johnthetubaguy looking for git hub link...15:52
*** glikson has quit IRC15:52
*** dtynan has joined #openstack-meeting15:52
*** bdpayne has joined #openstack-meeting15:52
johnthetubaguyhttps://github.com/openstack/nova/blob/master/nova/virt/xenapi/vm_utils.py#L86715:52
rnirmalfor my usecase.. even if I can get multiple disks attached amounting to the total size is acceptable as well15:52
johnthetubaguyI think you can use dd to create a raw file of the correct size (could take some time)15:53
johnthetubaguythen call it .raw, or something like that15:53
*** lloydde has joined #openstack-meeting15:53
johnthetubaguythen it gets picked up by xapi, I think15:53
*** jcru has left #openstack-meeting15:53
johnthetubaguybut not 100% sure, never tried it15:53
rnirmaljohnthetubaguy: hmm ok let me explore that option.15:53
BobBallI know that it's possible to have multiple disks attached to get to the total size.  "Support limits" say you can only attached 7 disks (should be 15) - but actually you can attach more as long as you've got PV drivers installed and specify the device number15:54
johnthetubaguywell, you can do a big raw file though?15:54
johnthetubaguynot VHD limit on that15:54
johnthetubaguyno^15:54
BobBallSorry, yes.  Probably.15:54
BobBallalthough how does that get mounted?15:54
rnirmalwould the performance be the same15:54
rnirmalor more or less same15:54
johnthetubaguyno idea, I have to admit, it could be better15:55
johnthetubaguyyou would have to try it15:55
BobBallFileSR is VHD backed15:55
*** adjohn has quit IRC15:55
johnthetubaguyit is, but I was told of an easter egg in those file types that detect .raw files, or something like that15:55
BobBallraw (if we have the SR for it) would be faster than VHD because it would have to skip some of the overhead.15:55
BobBallahhh okay15:55
johnthetubaguyyep, who knows what else might break15:56
johnthetubaguybut it should just about meet the ephemeral use case15:56
johnthetubaguycause it is created blank15:56
BobBalljohnthetubaguy, you're right - FileSR does identify a "raw" file extension15:56
johnthetubaguyI thought I read that in there15:56
johnthetubaguyits "special"15:56
johnthetubaguyso create the file, copy in, sr scan15:56
johnthetubaguyand booom15:56
*** kpavel has quit IRC15:57
BobBallAgreed.15:57
johnthetubaguybooom being possible success and possible hose your whole system15:57
rnirmalok cool.. thanks everyone this has been helpful.. I'll try some of the mentioned options and get back15:57
*** dwalleck has joined #openstack-meeting15:57
johnthetubaguycool, catch us on IRC15:57
johnthetubaguyopenstack-nova15:57
*** kebray has quit IRC15:58
*** varma has joined #openstack-meeting15:58
johnthetubaguyso, sounds like everything?15:58
BobBallor next week during the normal xenapi surgery hours!15:58
johnthetubaguylol15:58
johnthetubaguyyes15:58
BobBallactually rnirmal, some of us are more likely to be around on #xen-api and there are other funky people there who can help too15:58
johnthetubaguygood point15:58
rnirmalBobBall: thanks I'll hop in there as well15:58
johnthetubaguythat is probably better for that kind of hacking15:58
*** dwalleck has left #openstack-meeting15:59
johnthetubaguy#action johnthetubaguy to mention #xen-api on the team wiki15:59
johnthetubaguy#endmeeting15:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"15:59
openstackMeeting ended Wed May  8 15:59:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-08-15.00.html15:59
johnthetubaguythanks all15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-08-15.00.txt15:59
*** SergeyLukjanov has quit IRC15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-08-15.00.log.html15:59
BobBallWicked.  Thanks guys.15:59
*** xyang_ has joined #openstack-meeting16:00
*** jungleboyj has joined #openstack-meeting16:00
rushiagrtime for cinder guys to storm the channel!! attaaacckkk :P16:01
jgriffithFreeeedoooooooooooooooom!16:01
jgriffith#startmeeting cinder16:01
openstackMeeting started Wed May  8 16:01:38 2013 UTC.  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:01
jgriffithHey everyone16:01
eharneyhello16:01
* BobBall runs and hides16:01
vincent_houhi16:01
xyang_hi16:01
rushiagro/16:01
* jungleboyj sounds the trumpet16:01
jungleboyjHowdy16:02
varmahi16:02
flaper87o/16:02
jgriffithOk  so here's the agenda16:02
jgriffithhttps://wiki.openstack.org/wiki/CinderMeetings16:02
jgriffithThis should make for an interesting meeting :)16:02
jgriffithLooks like thingee may be delayed16:02
*** bswartz has joined #openstack-meeting16:02
jgriffithNo winston-d either16:02
bswartzhi16:02
jgriffithbswartz: howdy16:02
jgriffithPerhaps we'll go out of order a bit here16:03
jgriffith#topic core team expectations16:03
*** openstack changes topic to "core team expectations (Meeting topic: cinder)"16:03
jgriffithI just wanted to touch on some things real quick16:03
*** changbl has joined #openstack-meeting16:03
*** thingee has joined #openstack-meeting16:03
jgriffithI get a lot of emails from folks asking to be core, or asking for somebody they represent to be core16:04
jgriffithFirst, anybody on the team can nominate somebody for Core16:04
jgriffithYou can even nominate yourself16:04
jgriffithThe process is typically via the ML16:04
*** dwcramer has joined #openstack-meeting16:04
jgriffithThat being said.... I wanted to point out what the responsibilities are:16:04
*** glikson has joined #openstack-meeting16:05
jgriffithof course I lost the link :)16:05
rushiagrhttps://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess16:06
rushiagrjgriffith: ^16:06
jgriffithhaha16:07
jgriffithrushiagr: thnks16:07
jgriffithsorry, I had to step out for a second16:07
jgriffithSo there's the outline on things16:07
jgriffithBut I also want to point out that there's a lot of work expected to go along with it once you're nominated16:07
jgriffithReviews is the biggest thing16:07
jgriffithand the way I see it if you're not reviewing on a regular basis to begin with then you probably don't want to be core16:08
*** fnaval has joined #openstack-meeting16:08
*** vipul|away is now known as vipul16:08
jgriffithMy expectations here would be that you'd be very active in the review process at least a couple of days a week minimum16:08
jgriffithAlso... for those that are core16:08
jgriffithKeep in mind that you're allowed to do +2 and Approve16:09
jgriffithThere are a number of patches I see from time to time with 10 +1's on them16:09
jgriffithsome of which are from core team members16:09
jgriffithI'd like to keep the backlog of reviews down as much as possible16:09
jgriffithAlso... wondering if anybody is interested in assigned core member days?16:09
jgriffithThat's something they used to do in Nova, might be useful for us?16:10
jgriffiththoughts?16:10
jgriffithOr is this horribly booring for everyone?16:10
eharneywhat is an "assigned core member day"?16:10
vincent_hou?16:10
rushiagrya, what are guys expected to do exactly on such days?16:10
thingeeguaranteed available?16:10
jgriffitheharney: so the idea would be a published page that states what core members are available on what days16:11
jgriffiththingee: ok, guaranteed is a bit extreme :)16:11
eharneyah, ok16:11
jgriffithbut the idea being they're on the hoook for +2/A reviews on that day16:11
jungleboyjjgriffith: Not boring for those aspiring to be more involved.  :-)16:11
jgriffithand also hopefully around IRC for questions if they come up16:11
rushiagrjungleboyj: +1 ;)16:11
vincent_houok16:11
thingeejgriffith: is there a problem now that warrants this?16:12
jgriffiththingee: not necessarily no16:12
DuncanTSome of us are around most days but can't give much if any warning for being away...16:12
DuncanT(By that I mean me)16:12
jgriffiththingee: DuncanT k... maybe that doesn't fly16:12
jgriffithit was just an idea16:12
jgriffithOk, sounds like there's not much interest here so let's move along :)16:13
jgriffith#topic Defined core API features16:13
*** openstack changes topic to "Defined core API features (Meeting topic: cinder)"16:13
rushiagrI thought people (core/noncore both) are around on IRC atleast all the days of week16:13
jgriffithrushiagr: yeah, IRC isn't a problem at all16:13
jgriffith:)16:14
jgriffithrushiagr: don't sweet it, doesn't seem it's worth taking up any more time on16:14
*** SergeyLukjanov has joined #openstack-meeting16:14
jgriffithBack to the core API features16:14
*** annegentle has quit IRC16:14
rushiagrjgriffith: sure16:14
vincent_houthe problem is the time zone difference.16:14
jgriffithvincent_hou: indeed for IRC but not reviews16:15
jgriffithanyway.. moving along16:15
* thingee still on phone waiting for laptop to boot16:15
jgriffithhaha!16:15
jgriffithSo I'll segway here16:15
jgriffithI don't think this topic is any sort of a surprise to anyone16:15
jgriffithwe've talked about it on and off16:16
thingeemuc better16:16
jgriffithand we have a wiki page outh there that took a crack at it16:16
* guitarzan imagines jgriffith zipping around on a segway16:16
jgriffithhaha!16:16
*** anniec has quit IRC16:16
thingeejgriffith: so I guess speak about what came of the TC meeting16:16
jgriffiththingee: right16:16
jgriffithSo, one of the things that I brought up at the last TC meeting16:17
jgriffithwas how to deal with the issue we're starting to see16:17
jgriffithwith each vendor/backend wanting to implement some feature of the API their own way16:17
jgriffithI'll use Duncans trivial snapshot example becuase it's my favorite :)16:17
*** hemna_ is now known as hemna16:17
jgriffithSo HP has a back-end that they like to use snapshots for backups16:18
jgriffithThey charge the end user a different rate and all is good16:18
hemnamep16:18
jgriffithThe difference is they allow the parent to be deleted while the snap is still in existence16:18
jgriffithI believe RBD has a similar model16:18
jgriffithThere were discussions around letting each backend do it "how they want"16:19
hemnaafaik the 3PAR can't delete the parent volume of a snap16:19
*** gyee has quit IRC16:19
jgriffithTo me this seemed very very bad16:19
jgriffithdifferent behaviors based on what backend is in use and the user has no idea what to expect16:19
jgriffithor they have a road-map to read16:19
*** dontalton has joined #openstack-meeting16:19
jgriffithregardless... the TC for the most part agreed that the whole point of the openstack API's is software defined X16:19
jgriffithand that those delats should be extracted out16:20
*** ollie1 has joined #openstack-meeting16:20
jgriffithenhanced features above and beyond can be exposed in different ways16:20
*** SergeyLukjanov has quit IRC16:20
jgriffithbut there needs to be a common set of behaviors across the board16:20
*** kirankv has joined #openstack-meeting16:20
jgriffithfor us, that should be the reference implementation (LVM)16:20
*** jcoufal has quit IRC16:21
jgriffithSo for example if I can do "create/snapshot/delete/clone/copy-image"16:21
jgriffiththose should all be expectations for every backend in in the system16:21
thingeequantum for example has already dealt with this at the summit. They defined a set of features and vendors are expected to follow it.16:21
rushiagrjgriffith: I liked the idea of additional flags to do custom behavior for custom backends, I  guess DuncanT proposed it16:21
*** dwalleck has joined #openstack-meeting16:21
*** dwalleck has left #openstack-meeting16:21
guitarzanwait, everything we can do in lvm should be expected by every backend?16:21
hemnauh oh...this discussion again? :P16:22
thingeeI think we were all in an agreement that's the approach we wanted to take, but it's the reference that we follow that made this controversial.16:22
xyang_not every array can behave exactly like LVM though16:22
jgriffithguitarzan: IMO yes, if we want to choose a different reference or make one up based on a subset of the ref implementation that's fine16:22
*** boris-42 has joined #openstack-meeting16:22
guitarzanI just think equating the reference implementation with the base functionality is not the right move to make16:22
jgriffithguitarzan: But really, *reference* implementations are supposed to be just that16:23
*** terry7 has joined #openstack-meeting16:23
jgriffithguitarzan: but that's what a reference implementation is16:23
guitarzanI think it's only the reference because it's the easiest16:23
jgriffithhaha!  I disagree on tht16:23
jgriffiththat16:23
guitarzanso we should remove the extra stuff from the reference16:23
*** dperaza has joined #openstack-meeting16:23
jgriffithSolidFire is WAAAAYYYYY easier than LVM :)16:23
*** ndipanov has quit IRC16:23
guitarzanand have an extended lvm backend16:23
*** tong|3 has quit IRC16:23
DuncanTSo the question then becomes how do things evolve? e.g. I can make the reference implementation do 'allow parent volumes to be deleted' easily enough16:23
hemna:)16:23
thingeeguitarzan: the idea would be you can beyond the reference implementation16:23
jgriffithguitarzan: possibly, but what features is the real question I think16:23
guitarzanthingee: I understand16:23
bswartzguitarzan +116:23
*** dperaza has left #openstack-meeting16:24
jgriffithguitarzan: bswartz so the only thing we should require is create/delete volumes16:24
guitarzanlvm has support for lots of things that some of us consider extended16:24
jgriffithguitarzan: such as?16:24
guitarzanclone?16:24
*** gyee has joined #openstack-meeting16:24
guitarzanheck, even snapshots maybe :)16:25
*** gyee has quit IRC16:25
guitarzanbut I won't go there today16:25
hemnabut some features can be emulated by the arrays, in which it gives the impression that it still supports feature X to the end user.16:25
*** SergeyLukjanov has joined #openstack-meeting16:25
*** shang has joined #openstack-meeting16:25
jgriffithhemna: exactly16:25
bswartzfwiw, I don't consider anything in the current LVM driver to be exotic, but if we use it as the bar to all other drivers, there will be a huge incentive to NOT add functionality to the LVM driver, even if it would be easy to do so, if there are other driver that can't match the same feature16:25
jungleboyjguitarzan: +116:25
DuncanTAnd at some point you have to say if array donesn't have features X, Y and Z implemented or emulated, it doesn't work with cinder16:25
guitarzanbswartz: I think that's the tricky point here16:25
jgriffithbswartz: I disagree witht that completely16:25
jgriffithin fact it's just the opposite IMO16:25
jgriffithguitarzan: bswartz so what do you propose?16:26
thingeeguitarzan: with the proposal, it would have to be faked to support the idea that the user can request whatever without a matrice of the base features16:26
jgriffithguitarzan: bswartz create and delete are the only requirements?16:26
jgriffiththat seems really lame to me16:26
bswartzjgriffith: I just agree with the idea of separating the "reference LVM driver" from the "full feature LVM driver"16:27
*** lloydde has quit IRC16:27
hemnajgriffith, have to include attach/detach though no?16:27
guitarzanjgriffith: I think there's a big span between just create/delete and you have to do everything lvm can do16:27
DuncanTSo far, I'm pretty happy with the features we have in LVM all being core, even if I think online clone should require a force flag16:27
jgriffithbswartz: ok, but can you explain why?  And what the delta is?16:27
*** markmcclain has joined #openstack-meeting16:27
eharneyi have to agree with bswartz... so far NFS/Gluster seem useful but don't support much16:27
jgriffithguitarzan: not really16:27
* guitarzan shrugs16:27
jgriffiththere's snapshots and clones16:27
bswartzmaybe the full feature LVM driver should use awesome BTRFS features16:27
*** gyee has joined #openstack-meeting16:28
jgriffithboth of which you suggested shouldn't be required16:28
jgriffithbswartz: ?16:28
jungleboyjjgriffith: It seems that the definition of core needs to be separated from LVM given that others have strong opinions based on their drivers.  Sounds like something needs to be defined independently and voted upon.16:28
DuncanTMy worry is that the fact that a feature is easy to do on LVM doesn't mean it is easy on a different architecture16:28
hemnawe do have a wiki page now that describes the minimum driver requirements16:28
*** ryanpetrello has joined #openstack-meeting16:28
*** vish1 has joined #openstack-meeting16:28
jgriffithDuncanT: fair16:28
jgriffithSo let me backup a second16:28
jgriffithhere's my view on what Cinder is:16:29
jgriffithCinder is Software Defined Storage16:29
thingeehttps://wiki.openstack.org/wiki/Cinder#Minimum_Driver_Features16:29
bswartzI'm not very interested in this, just agreeing that we might need to reconsider the low bar16:29
jgriffithIt abstracts out a pool of backend storage devices for use by a consumer16:29
jungleboyjthingee: Thanks.16:29
hemnajgriffith, not just block storage now?16:29
jgriffithbswartz: well, now that we all know bswartz isn't interested in the project :)16:29
jgriffithhemna: yes, block storage16:29
*** vishy has quit IRC16:29
*** vish1 is now known as vishy16:29
jgriffithbut I'm not fighting that fight this morning16:30
hemnajgriffith, lol16:30
*** dolphm has left #openstack-meeting16:30
eharney:)16:30
DuncanTA reasonably high bar encourages more buy-in from those that chose to meet it16:30
jgriffithDuncanT: yes, and the other thing is if you're happy with just a piece of crap then we're done16:30
hemnaDuncanT, and if it's too high?  we risk not allowing drivers in that could be useful16:30
jgriffithPersonally I think there's a lot of potential for Cinder16:31
DuncanTA low bar encourages code-and-dump drive by contributions that aren't necessarily healthy for the project as a whole16:31
jgriffithbut it requires people to actually agree on what it's purpose is16:31
thingeeDuncanT: +116:31
hemnajgriffith, +116:31
jgriffithDuncanT: +100016:31
hemnaSo we need a middle ground IMO16:31
bswartzI'm just saying I don't feel the need to take us further down this rathole. NetApp doesn't have an issue with the current minimum feature set. I'll let the people who do have issues make the arguments.16:31
jgriffithSo looking at the wiki thingee reference:  https://wiki.openstack.org/wiki/Cinder#Minimum_Driver_Features16:31
DuncanTHema: So we've got a list on the wiki... is that a reasonable start or would you change it?16:32
jgriffithIs there anything on there that just makes people scream and kick?16:32
thingeesnapshot and clone seems to be what has been brought up.16:32
hemnaDuncanT, I think that's a great start and isn't an unreasonably high bar16:32
thingeeclone was proposed to be faked for avoiding a matrice of what's supported by drivers16:32
jgriffiththingee: yeah, and funny enough we included "volume from snap, but NOT snap" haha16:32
DuncanTOnline clone not needing a force flag makes me mutter darkly, but I'll raise a bug & patch for that and collect oppinions that way16:32
hemnawhat backends can't do a snap?16:33
thingeeEither way, I feel if drivers begin to diverge in going beyond the base features, we're going to end up with a matrice of some sort =/16:33
jgriffithDuncanT: I don't have a problem with it not being allowed online as the base16:33
xyang_this minimum features list didn't say how delete snapshot should work16:33
guitarzancreate/delete snap is there16:33
jgriffithDuncanT: IMO that's a perfect example of where differentiaton is good16:33
DuncanTjgriffith: Fantastic :-)16:33
*** nati_ueno has joined #openstack-meeting16:33
jgriffiththingee: Sorry... yeah, I see it now :(16:34
jgriffitherrr.. guitarzan ^^16:34
jgriffiththanks, I just missed it before somehow16:34
hemnaxyang_, do we really care how snapshot is implemented by a backend?16:34
jgriffithSo the key here is that we're not saying everybody has to do it the same way16:34
hemnaas long as it is...16:34
thingeejgriffith: +116:34
jungleboyjjgriffith: +116:34
jgriffithThey just have to provide something in the interface that at least gives the expected end-result16:35
xyang_hemna: I thought we started the discussion by whether the parent should can be deleted while snapshots are still there16:35
DuncanTI'm quite interested in turning the current feature set into a test suite that can give a yes/no answer to is that what you mean by snapshot....16:35
jgriffithxyang_: that was my lame example16:35
jgriffithDuncanT: +116:35
*** shang has quit IRC16:35
hemnaDuncanT, +116:35
*** shang has joined #openstack-meeting16:35
*** matelakat has quit IRC16:35
*** SergeyLukjanov has quit IRC16:35
jgriffithSo back to the prposal16:35
hemnaxyang_, I don't think we can require how the backend is implemented for snaps for example.   Not all arrays allow parent volumes to be deleted.16:35
jgriffithNote there's no implementation details or rules regarding online/offline16:36
xyang_hemna: agree16:36
jgriffithWe can add details around that, keeping the bar low16:36
jgriffithis there anything really that controversial, other than snapshots and clones for guitarzan ?16:36
jgriffithWhich BTW guitarzan I'm not sure why you care, you guys don't have a driver submitted anyway :)16:36
guitarzanhah16:36
jgriffithJust like HP16:36
guitarzanI'm just playing devil's advocate for lvm16:37
guitarzanor against maybe16:37
jgriffithguitarzan: haha... I'd say it's against16:37
jgriffithguitarzan: it does those things :)16:37
*** dontalton has quit IRC16:37
jgriffitheven if it isn't pretty :)16:37
jgriffithwhich is my whole point on this16:37
*** MarkAtwood has joined #openstack-meeting16:37
hemnaSo did we decide anything or just argue for fun?16:37
*** jamespage_ has joined #openstack-meeting16:37
*** kebray has joined #openstack-meeting16:37
jgriffithit doesn't have to be efficient/pretty or elegant16:37
guitarzanhemna: I haven't seen what we're voting on yet :)16:37
*** nati_ueno has quit IRC16:37
hemna:)16:37
DuncanTLooks like we generally agree on the current minimum feature list? And on the principle of having the list?16:38
jungleboyjDuncanT: +116:38
jgriffithguitarzan: hemna I would like for an agreement on the prposed list16:38
jgriffithguitarzan: hemna and I'd like to warn folks that if we agree I'm going to enforce it via reviews16:38
eharneyso where does the current minimum list leave drivers that already exist but fall short?16:38
hemnaso the current requirements + the new ones for Havana?16:38
jgriffithin fact even if we don't agree I still might :)16:38
thingeethe proposal is https://wiki.openstack.org/wiki/Cinder#Minimum_Driver_Features and that we don't care how you implement it, just don't raise an exception16:39
jgriffitheharney: the idea is they're supposed to be fixed in H16:39
guitarzanI don't think anyone has disagreed with the proposed list16:39
*** yamahata_ has quit IRC16:39
jgriffithOk.. Yippeee!16:39
eharneyjgriffith: ok.  i'm scheming something in that area but i'll get to that later16:39
guitarzanthe discussion started with something completely different, independent snapshots16:40
DuncanTI suggest we start submitting driver removal patches the day after H3 is cut.... that should get people's attention :-)16:40
jgriffitheharney: :)  care to give a preview?16:40
hemnayah I'm ok w/ it.   I have my TODO list to add copy image to volume/volume to image for Fibre Channel already, so the FC drivers should get that capability for Havana16:40
eharneyjgriffith: https://blueprints.launchpad.net/cinder/+spec/qemu-assisted-snapshots16:40
thingeeDuncanT: we agreed to split16:40
DuncanTthingee ;-)16:40
thingeeI am after all "that guy"16:40
eharneyjgriffith: ideas for snap support on gluster and maybe things like NFS too... still sketching out details to post soon16:40
jgriffitheharney: cool16:41
thingeejgriffith: https://review.openstack.org/#/c/25888/16:41
vincent_houy16:41
eharneyit changes things up a bit, but looks workable16:41
vincent_houit is related to https://bugs.launchpad.net/cinder/+bug/114859716:42
uvirtbotLaunchpad bug 1148597 in cinder "Snapshot a volume on a different cinder-volume node" [Wishlist,In progress]16:42
jgriffiththingee: vincent_hou you guys wanna talk about that one?16:42
thingeeit's next topic :)16:43
vincent_houyes16:43
jgriffith#topic https://review.openstack.org/#/c/25888/16:43
*** openstack changes topic to "https://review.openstack.org/#/c/25888/ (Meeting topic: cinder)"16:43
thingeevincent_hou: go for it16:43
*** bdpayne has quit IRC16:43
vincent_houOperation people in my company actually asked for this functionality. They wanted to put the snapshots in a different machines from where the volumes are located.16:43
jgriffithvincent_hou: understand but I have two issues:16:44
vincent_houThey want to to prevent the loss of both the volume and the snapshot on the same machine16:44
jgriffithvincent_hou: snapshots are not backups16:44
jgriffithvincent_hou: we now have backups16:44
vincent_houright16:44
jgriffithvincent_hou: if you want a backup, do a backukp :)16:44
hemna:)16:44
vincent_houthey said snapshot16:44
jgriffithvincent_hou: the other thing is, the concept of a snapshot we've pretty much made backend specific16:44
DuncanTTell them 'no' then?16:44
vincent_houbackend specific?16:45
*** bdpayne has joined #openstack-meeting16:45
vincent_houohhhhh16:45
DuncanTSome backends already do snapshot as a copy to swift....16:45
jgriffithvincent_hou: sure... on LVM it may be a qcow16:45
jgriffithdependent on the parent16:45
DuncanTSome do it as COW magic16:45
jgriffithon Ceph is't somethign else16:45
jgriffithetc etc16:45
DuncanTsome do dd16:45
vincent_houI see.16:45
thingeenot all backends are suppoorting snapshots now anyways. You avoid that problem with using the cinder-backup service....although that has recently changed in the last proposal.16:46
vincent_houI have one more question.16:46
DuncanTI've slightly lost track of all the directions people want to take backup in, looking forward to seeing code though16:46
vincent_houCan we backup directly on a different machine?16:47
thingeesure, have a separate swift machine16:47
guitarzanyou'd better have more than one swift machine :)16:47
jgriffithvincent_hou: I'm also hoping that somebody finds the time to do backups to block etc16:47
vincent_houMmmmm.......16:47
thingeeso what are we agreeing on here?16:48
vincent_houjgriffith: exactly16:48
jgriffithvincent_hou: the problem is ceph wouldn't know what to do with a SF snap, that wouldn't know what to do with an HP snap that wouldn't konw what to do with.....16:48
DuncanTThe whole idea behind backup is that you can put half your swift cluster in a different firecell and your data is safe even if your cinder & nova machines all catch fire16:48
thingeewhat are the disadvantages of having zoned snaps?16:49
thingeeis it going to hurt anything if the option is there?16:49
*** hub_cap has joined #openstack-meeting16:50
jgriffiththingee: the problem I see is there's no way for another backend device to know what to do with it16:50
DuncanTYou need to add a whole second code patch to do remote snaps16:50
thingeejgriffith: ok, and that's not addressed by that patch16:50
thingeeand in general not how cinder works16:51
*** SumitNaiksatam has quit IRC16:51
thingeeopen discussion?16:51
jgriffiththingee: correct, there's really no way to address it outside of the device itself16:51
jgriffith#topic open discussion16:51
*** openstack changes topic to "open discussion (Meeting topic: cinder)"16:51
jgriffithw00t16:52
jgriffithshort meeting16:52
bswartzi have a question about multipath/ALUA support in cinder -- do we have it?16:52
hemnajgriffith, so I need to start pulling in the FC attach code, and was going to put it in "brick"16:52
hemnawhere should I put it ?16:53
jgriffithhemna: hmmm....16:53
jgriffithhemna: I *think* what I'm going to do is16:53
*** dwcramer has quit IRC16:53
jgriffithput the dir structure in cinder16:53
jgriffithie cinder/brick/16:53
jgriffithpopulate and use it in Cinder first16:53
hemnaok16:53
jgriffiththen create a separate lib that we can use elsewhere similar to what we do with common16:53
* thingee has to cut out a bit early for a meeting16:54
jgriffithbswartz: we don't have it in the code currently no16:54
thingeebye all16:54
jgriffiththingee: cya16:54
jgriffiththingee: thanks!16:54
bswartzanyone interested in multipath support for iSCSI?16:54
*** thingee has left #openstack-meeting16:54
hemnabswartz, didn't that land in nova Grizzly?16:54
hemnaI have multipath support in my FC attach code in Nova already16:54
jgriffithbswartz: me16:54
xyang_nova has code for iscsi multipath16:54
*** martine has quit IRC16:54
jgriffithbswartz: oh... multipath or multiattach?16:55
bswartzxyang_: what does nova use it for if cinder doesn't support it?16:55
*** martine has joined #openstack-meeting16:55
jgriffithbswartz: sorry16:55
jgriffithbswartz: I misread16:55
bswartzjgriffith: does that mean not interested? lol16:55
xyang_xyang_: I think we just need to enable a flag, I am going to try it but haven't got chance16:55
jgriffithbswartz: sorry... no, doesn't mean that at all16:55
jgriffithxyang_: that would be awesome if you have time to do that and could let us know what you find16:56
bswartzI think the attach call should probably evolve to return multiple targets16:56
xyang_bswartz: just like FC multipath support in nova, I don't think we need to change cinder16:56
bswartzokay perhaps I need to look into it16:57
bswartzI find it hard to believe that it would work with no support from the drivers16:57
hemnawe didn't have to do anything in cinder to support multipath for FC16:57
xyang_bswartz: I looked at code.  seems that we don't need to change anything other than the flag.  I'll need to test it myself16:57
xyang_jgriffith: sure, will do16:57
*** Mandell has joined #openstack-meeting16:58
jgriffithbswartz: I think the iscsi layer does alot of that magic for you16:58
bswartzokay thanks16:58
bswartzI'll just do some testing then16:58
jgriffithbswartz: cool, let folks know how it goes16:58
jgriffithanything else from anybody?16:58
guitarzanI'll ask about the volume type stuff in #openstack-cinder16:59
guitarzanseems like DuncanT doesn't want it to be configurable, but always on16:59
jgriffithguitarzan: ohh, yes on the quotas16:59
jgriffithguitarzan: folks should join in so we can get that hammered out16:59
jgriffithalright, see ya in the channel16:59
*** salmon_ has joined #openstack-meeting16:59
jgriffiththanks everyone16:59
jgriffith#endmeeting16:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:59
openstackMeeting ended Wed May  8 16:59:48 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-08-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-08-16.01.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-08-16.01.log.html16:59
*** ollie1 has left #openstack-meeting16:59
rushiagrthanks, bye all17:00
jungleboyjBye.17:00
*** jungleboyj has left #openstack-meeting17:00
*** bswartz has left #openstack-meeting17:00
*** varma has quit IRC17:00
*** vkmc has quit IRC17:01
*** mattray has joined #openstack-meeting17:01
*** reed has joined #openstack-meeting17:02
*** marun has joined #openstack-meeting17:03
*** GheRivero is now known as Ghe-afk17:04
*** anniec has joined #openstack-meeting17:05
*** annegentle has joined #openstack-meeting17:08
*** dwalleck has joined #openstack-meeting17:08
*** nati_ueno has joined #openstack-meeting17:09
*** kirankv has quit IRC17:09
*** lloydde has joined #openstack-meeting17:12
*** jog0 has joined #openstack-meeting17:14
*** adjohn has joined #openstack-meeting17:16
*** FallenPegasus has joined #openstack-meeting17:20
*** MarkAtwood has quit IRC17:22
*** lloydde has quit IRC17:25
*** anniecheng has joined #openstack-meeting17:33
*** SergeyLukjanov has joined #openstack-meeting17:36
*** amyt has quit IRC17:39
*** jamespage_ has quit IRC17:39
*** lloydde has joined #openstack-meeting17:40
*** amyt has joined #openstack-meeting17:40
*** chuck_ has quit IRC17:41
*** marcusk has joined #openstack-meeting17:42
*** maoy_ has joined #openstack-meeting17:45
*** maoy has quit IRC17:45
*** maoy_ is now known as maoy17:45
*** FallenPegasus has quit IRC17:46
*** hanney has quit IRC17:46
*** dontalton has joined #openstack-meeting17:47
*** vincent_hou has quit IRC17:50
*** xyang_ has quit IRC17:51
*** otherwiseguy has quit IRC17:57
*** zul has joined #openstack-meeting18:00
*** nati_ueno has quit IRC18:00
*** beagles is now known as beagles_brb18:01
*** lloydde has quit IRC18:03
*** jamespage_ has joined #openstack-meeting18:03
*** flaper87 has quit IRC18:04
*** dwcramer has joined #openstack-meeting18:07
*** reed has quit IRC18:07
*** novas0x2a|laptop has quit IRC18:12
*** mattray has quit IRC18:15
*** zul has quit IRC18:18
*** krtaylor has quit IRC18:19
*** jamespage_ has quit IRC18:19
*** flaper87 has joined #openstack-meeting18:21
*** reed has joined #openstack-meeting18:24
*** hub_cap has left #openstack-meeting18:31
*** FallenPegasus has joined #openstack-meeting18:32
*** Ghe-afk is now known as GheRivero18:33
*** lloydde has joined #openstack-meeting18:33
*** pfreund has joined #openstack-meeting18:35
*** dani4571 has joined #openstack-meeting18:36
*** dwcramer has quit IRC18:36
*** wirehead_ has joined #openstack-meeting18:37
*** beagles_brb is now known as beagles18:39
*** egallen has joined #openstack-meeting18:39
*** mkollaro has joined #openstack-meeting18:41
*** lloydde has quit IRC18:43
*** egallen has quit IRC18:43
*** uma has joined #openstack-meeting18:44
*** novas0x2a|laptop has joined #openstack-meeting18:45
*** jamespage_ has joined #openstack-meeting18:45
*** rwsu has joined #openstack-meeting18:46
*** zul has joined #openstack-meeting18:48
*** dwcramer has joined #openstack-meeting18:49
*** johnthetubaguy has quit IRC18:49
*** egallen has joined #openstack-meeting18:53
*** jamespage__ has joined #openstack-meeting18:56
*** otherwiseguy has joined #openstack-meeting18:56
*** zzs has joined #openstack-meeting18:57
*** egallen has quit IRC18:58
*** jamespage_ has quit IRC18:58
*** krtaylor has joined #openstack-meeting18:59
*** egallen has joined #openstack-meeting18:59
*** cp16net is now known as cp16net|away19:00
*** cp16net|away is now known as cp16net19:00
*** jecarey has quit IRC19:02
*** gyee has quit IRC19:03
*** dwalleck has quit IRC19:06
*** dhellmann has joined #openstack-meeting19:11
*** markmcclain has quit IRC19:13
*** mattray has joined #openstack-meeting19:14
*** vipul is now known as vipul|away19:16
*** markmcclain has joined #openstack-meeting19:17
*** litong has joined #openstack-meeting19:17
*** egallen has quit IRC19:18
*** egallen has joined #openstack-meeting19:20
*** stevebaker has quit IRC19:24
*** stevebaker has joined #openstack-meeting19:26
*** rnirmal has quit IRC19:31
*** garyk has quit IRC19:33
*** adjohn has quit IRC19:34
*** jamespage__ has quit IRC19:36
*** zul has quit IRC19:36
*** lloydde has joined #openstack-meeting19:38
*** SergeyLukjanov has quit IRC19:39
*** topol has quit IRC19:40
*** cp16net is now known as cp16net|away19:41
*** dolphm has joined #openstack-meeting19:42
*** cp16net|away is now known as cp16net19:42
*** hanney has joined #openstack-meeting19:44
*** mattray has quit IRC19:45
*** dolphm has quit IRC19:46
*** radez is now known as radez_g0n319:49
*** koolhead17 has quit IRC19:53
*** therve has joined #openstack-meeting19:55
*** barefoot has joined #openstack-meeting19:55
*** shardy has joined #openstack-meeting19:55
*** mrutkows has joined #openstack-meeting19:55
*** dwcramer has quit IRC19:58
*** SpamapS has joined #openstack-meeting19:58
*** randallburt has joined #openstack-meeting19:58
*** adrian_otto has joined #openstack-meeting20:00
*** shengjie_home has joined #openstack-meeting20:00
shardy#startmeeting heat20:00
openstackMeeting started Wed May  8 20:00:29 2013 UTC.  The chair is shardy. 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
shardy#topic rollcall20:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:00
SpamapSo/20:00
therveHola20:00
mrutkowshere20:00
*** uma has quit IRC20:00
jpeelerhi20:00
randallburthi folks20:01
adrian_ottohi20:01
kebrayHello20:01
*** tspatzier has joined #openstack-meeting20:01
hanneyo/20:01
wirehead_heya20:01
stevebakero/ (i'll have to leave early)20:02
asalkeldo/20:02
harlowjayo20:02
shardyOk, cool, zaneb said he can't attend today also20:02
shardyWell hi all, let's get started :)20:02
shardy#topic Review last week's actions20:03
*** openstack changes topic to "Review last week's actions (Meeting topic: heat)"20:03
shardyall to take a look at harlowja's wiki page and patch20:03
*** jimbaker has joined #openstack-meeting20:03
* oubiwann high-fives therve 20:03
shardyI had a look at the wiki page, but forgot to look at the patch, sorry harlowja20:03
harlowjaits fine, the patch is 'evolving'20:03
adrian_ottothere are multiple wiki pages. Can you specify which you are referring to? Please offer a link.20:04
shardyadrian_otto: they are linked in the last weeks minutes, but here:20:04
shardy#link https://wiki.openstack.org/wiki/NovaOrchestration/WorkflowEngines20:04
harlowja*thats an old one :)20:04
shardy#link https://wiki.openstack.org/wiki/StructuredStateManagement20:04
*** adjohn has joined #openstack-meeting20:05
shardy#link http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-01-20.00.html20:05
adrian_ottothanks, I'm familiar with that one20:05
kebrayfamiliar here as well.20:05
harlowjathere are some ideas being thrown around as to placement of said library, still in progress i think20:05
*** m4dcoder has joined #openstack-meeting20:05
harlowja*its a little bit of an odd duckling20:05
shardyThe main question I have - is the plan still to create a small library, then build on it?20:05
shardyI didn't like the look of the long list of existing WorkflowEngines much20:06
harlowjashardy so yes i think the small library approach is still the ideal20:06
adrian_ottoyes, we want to create a StackForge project, make a small library, then iterate on it20:06
shardyOk, sounds good20:06
adrian_ottowhen it makes sense to start pulling in patches to add features or solve issues in Heat, we can pull those over20:06
shardyAnyone else got anything on this or should we move on?20:06
*** vipul|away is now known as vipul20:07
sdakeo/20:07
*** shengjie has joined #openstack-meeting20:07
shardyhey sdake20:07
sdakesorry late - late lunch20:07
adrian_ottowe are working to have representatives from multiple OpenStack projects on the TaskFlow Stackforge project in order to boost alignment20:07
*** jlucci has joined #openstack-meeting20:07
adrian_ottothat should make integration later easier, as there should be less to debate20:07
harlowjayup20:07
kebrayWe have confirmed representation on the STackForge TaskFlow project for Reddwarf.20:07
harlowjaand i am sorta connected with nova, but i am not a core represenative20:08
shardyadrian_otto: sounds good, definitely sounds like we'll have someone involved also20:08
adrian_ottoideally a core member from each interested project20:08
harlowjayes, that would be nice20:09
adrian_ottobut what I am concerned with mostly today is taht we don't stagger innovation and progress by having too much red tape20:09
shardyUnless anyone wants to volunteer now, perhaps we can discuss and come back to you with who (as zaneb is not here and I know he's possibly interested in this area)20:09
harlowjaadrian_otto 100% agree20:09
adrian_ottolet's get everyone thinking, organized and coding together.20:09
harlowja:)20:09
shardyadrian_otto: +120:09
*** cp16net is now known as cp16net|away20:10
shardyOk couple more actions to check:20:10
shardyrandallburt assign names to new BPs linked above20:10
*** stevemar has quit IRC20:10
shardyrandallburt: this is done now right?20:10
randallburtasalkeld got the assignments sorted so we should be good.20:10
shardyOk, great20:10
*** jamespage__ has joined #openstack-meeting20:11
shardyzaneb to add details to Provider BPs20:11
shardyI'm pretty sure zaneb did this20:11
*** jamespage__ has quit IRC20:11
shardyeveryone to target bp's likely to land in next 2-3 weeks to havana-120:11
randallburtHe did for the couple I looked at20:11
shardySo this looks good, if anyone has anything they expect to land for h-1 please make sure it's targetted in LP20:11
shardySpamapS to raise BP re available resources20:12
shardySpamapS: Pretty sure you did this?20:12
SpamapSI did20:12
shardyOk, thanks20:12
SpamapShttps://blueprints.launchpad.net/heat/+spec/discover-catalog-resources20:12
*** shengjie_home has quit IRC20:13
shardy#link https://blueprints.launchpad.net/heat/+spec/discover-catalog-resources20:13
*** FallenPegasus is now known as MarkAtwood20:13
* shardy should've been using info for all those action bullets, oops20:13
shardySo I only added one topic, which is:20:14
shardy#topic Stable Branch policy cont'd20:14
*** openstack changes topic to "Stable Branch policy cont'd (Meeting topic: heat)"20:14
*** adjohn has quit IRC20:14
shardyWe kinda discussed this last week, but I wanted to proposed that we align with what Ceilometer are doing:20:14
shardy- Support Folsom as a best-effort via stable/grizzly20:15
shardy- stop worrying too much about backwards compatibility in master20:15
shardy- Align with the openstack stable-branch policy for all backports20:15
shardy#link https://wiki.openstack.org/wiki/StableBranch20:16
therveIt sounds fine to me20:16
shardyDoes this sound reasonable to everyone?20:16
asalkeldyea20:16
sdakewill there be forward compatibility?20:17
SpamapS+1 for not worrying about BC w/ Folsom in master20:17
stevebakerThere are quite a few users interested in using latest heat will folsom/grizzly openstacks20:17
shardysdake: forward compatibility?20:17
sdakeie grizzly->havana20:17
shardyyou mean the templates?20:17
shardyupgrade path, db migrations etc?20:17
sdakean upgrade path20:17
sdakeyup20:17
shardyYes, definitely20:18
stevebakerI'd like users who want to use latest heat against folsom/grizzly to self-organise and do the regression testing themselves, and feed us fixes20:18
randallburtstevebaker:  +120:18
asalkeldthe move to ceilometer for alarms is going to be messy20:18
stevebakerso we don't have to worry about BC w/ Folsom in master but we are receptive to those who are20:18
SpamapSWe should not break network API compatibility.. but I stand by my charge that the software dependencies present/not-present are orthogonal to that20:18
asalkeldif people are using alarms20:18
shardystevebaker: agree, but there's some stuff, e.g trusts which only exist in >= grizzly, and as asalkeld say all the new CM alarm stuff20:19
*** cp16net|away is now known as cp16net20:19
stevebakerhmm alarms20:19
asalkeld(as the alarm table in heat will need to be ditched and recreated in ceilometer)20:19
SpamapSasalkeld: indeed, Havana should maintain "the old way" for alarms, but deprecate it. So that there is a phased migration path.20:19
shardyI think we've reached (or soon will be reaching the point where it's hard to keep master working on Folsom, and perhaps soon grizzly)20:19
SpamapSalso, IMO we need to get stuff like this in the gate20:20
shardyYep, make the new alarms code default, but have config option for the old stuff, say for one more cycle20:20
asalkeldnot so easy20:20
*** fsargent has left #openstack-meeting20:20
*** fsargent has joined #openstack-meeting20:20
*** shengjie_ has joined #openstack-meeting20:20
stevebakerits up to these users to explicitly tell us what is important to them. I'm going to send an email to kick the process off20:21
SpamapSasalkeld: not easy, but critical to holding on to early adopters20:21
shardyasalkeld: alarms will be a one-way change?20:21
asalkeldyea20:21
shardySpamapS: exactly20:21
therveWe would need some kind of functional testing to be able to maintain that properly20:21
SpamapSIf somebody has deployed grizzly heat, we should pretty much buy them tiaras and scepters and carry them around on a liter with a throne on top of it at the next summit.20:21
stevebakerI was thinking the new tempest tests could be also run against old openstacks, but that is handled by the people wanting that use case20:22
thervestevebaker, +120:22
SpamapSoh, and we should probably try to test their migration too. :)20:22
oubiwannSpamapS: man, you make a good princess pitch20:22
asalkeldI suspect xlcloud is someone we should talk to about it20:22
oubiwannI've got a couple takers here in the office20:23
SpamapSstevebaker: Yeah, lets get the tempest against current openstack first.. but an immediate goal thereafter should be to run it against havana heat + grizzly.20:23
*** zul has joined #openstack-meeting20:23
stevebakerSpamapS: yep, but I wouldn't count on the CI infrastructure doing that for us20:24
SpamapSstevebaker: I would... but.. my boss runs it and he loves stuff like that. :)20:24
*** senhuang has joined #openstack-meeting20:24
SpamapSmordred: ^^20:24
shardyOk, so master should ideally work with havana/devstack and stable/grizzly, but there may be documented workarounds to run on grizzly (e.g bleeding edge client libraries which we're already starting to need)20:25
* mordred reads scrollback20:25
*** spzala has quit IRC20:25
adrian_ottomordred: welcome20:25
mordredwe would LOVE to do cross-version testing of stuff - but we still don't have that with novaclient+nova yet20:25
mordredso - you know - it might not happen quickly :)20:25
clarkbstevebaker: fwiw I think we probably can run it, just that it probably wouldn't happen as part of the larger integration gate20:26
stevebakerimagine the cross-version permutations, ouch20:26
shardystevebaker: I think if we're not careful it could be come a huge resource-sink20:26
shardyBe better to say "n-1 version is untested and best-effort"20:26
shardyie if problems are reported we'll try to fix, and try to avoid knowingly merging stuff which will obviously break with grizzly?20:27
shardymaybe we need a vote, but I'm not sure exactly what we're voting on ;)20:28
stevebakeryep, but my point is it is less of a resource sink if we're not doing the work, the people who are interested in this are20:28
shardystevebaker: completely agree20:28
stevebakernothing yet, action point for me to email who is interested20:28
SpamapSOk, so we need to vote only on policy.20:28
SpamapSBasically, will we respond to bug reports about X with yay or nay.20:29
shardy#action stevebaker to send ML email re backwards-compatibility20:29
SpamapSX being. "trunk running against grizzly" or "stable running against folsom"20:29
stevebakerSpamapS: bug reports on old openstack versions without provided fixes may be politely declined ;)20:29
mrutkowsReally hate to leave early for the first Heat meeting, but have a conflict the 2nd half of this hour... hope to be more of a regular from now on20:30
therveshardy, it seems reasonable to include backward compatibility concerns in the review process. Without automation it's wishful thinking though20:30
shardymrutkows: np o/20:30
stevebakertherve: yep20:31
shardytherve: well until now we have done it manually, but yes agree automation would be great if someone's willing to do it for us ;)20:31
stevebakershould we move on?20:31
shardyyep20:31
shardywe can follow up on the ML thread started by stevebaker20:31
shardy#topic Open discussion20:32
*** openstack changes topic to "Open discussion (Meeting topic: heat)"20:32
*** gyee has joined #openstack-meeting20:32
shardyAnyone have anything to discuss?20:32
SpamapSheat-cfntools ...20:32
tspatzierI have some news on the open-api-dsl topic ..20:33
SpamapSoo lets do tspatzier's first20:33
shardytspatzier: go for it :)20:33
shardytspatzier: I saw your heat-templates review, not finished going through all three templates yet20:34
tspatzierSo, I've posted a patch for review about an hour ago to add some variants of the WordPress_Single_Instance template to the heat-templates repo20:34
tspatzier#link https://review.openstack.org/2859820:34
tspatzierWould be interested in everyone's feedback20:34
shardytspatzier: great, thanks for this20:35
tspatzierSpamapS: based on that, I also plan to sketch something in reply to the recent ML discussion ...20:35
shardy#action all to look at dsl examples and provide feedback20:35
shardyAny more to add on this, or should we go to SpamapS topic?20:36
tspatzierLet's move on20:36
SpamapSSo, heat-cfntools ..20:36
SpamapSI've been doing some poking and prodding of it, and generally trying to get it in shape for my use case..20:36
*** acfleury has quit IRC20:37
SpamapSBut shardy pointed out that this is all very cfn centric, so time spent on it is dead-tools time.20:37
SpamapSI am wondering if the HOT template developers have given much thought to an in-instance agent, which is most of what makes heat-cfntools interesting to me (cfn-hup)20:37
asalkeldno polling?20:38
tspatzierSpamapS: We thought of something like generic "providers" that do in-instance software config20:38
SpamapSnot config20:38
SpamapScfn-init does that...20:38
SpamapSand I don't like it at all20:38
tspatzierAh, I see20:39
SpamapScfn-hup is just a triggering mechanism20:39
SpamapSit is meant to expose the timing of updates from the orchestration engine to the instance software20:39
asalkeldwe need a communication path20:39
stevebakerSpamapS: have you thought of building what you need in (or on top of) python-heatclient?20:39
randallburtSpamapS: not really. Had hoped to avoid it tbh.20:39
SpamapSstevebaker: no, but that makes perfect sense.20:39
shardybasically we'll need heat-ostools to provide all of our current functionality without the cfn-compatible API20:39
SpamapSrandallburt: it cannot be avoided.20:39
SpamapSotherwise you're not doing real orchestration20:40
shardy(which is not necesarily related to the template format)20:40
randallburtSpamapS: yeah, but I had *hope*20:40
randallburt;)20:40
stevebakerSpamapS: do you need anything other than cfn-hup(ish)20:40
* SpamapS lights randallburt's hope on fire20:40
*** adjohn has joined #openstack-meeting20:40
wirehead_ugh20:40
shardyI think all we actually need is cloud-init and a metadata-monitor tool (cfn-hup-ish) which talks to the ReST API20:41
SpamapSstevebaker: not really, i just need "cache metadata locally, run hooks on update"20:41
therveSpamapS, what are your requirements, regardless of cfn-hup?20:41
SpamapSshardy: cloud-init is completely orthogonal to this.20:41
shardyWe don't need cfn-init for HOT templates IMO, it's a CFN compatibility thing20:41
SpamapScompletely.20:41
shardySpamapS: someone mentioned cfn-init20:41
SpamapSunless you re-work cloud-config to be its own tool, which is I suppose doable.20:42
sdakeif idea is to drop cfn, wont that break forward compatibility?20:42
* randallburt rekindles hope!20:42
asalkeldsdake, not drop20:42
shardysdake: not drop, make optional20:42
asalkeldjust add a new better tool20:42
sdakei see20:42
SpamapSok anyway, lets not design it here, but I wanted to see if anybody else was thinking on this subject20:42
asalkeldbetter response to updates20:42
adrian_ottoI'll add support to SpamapS to do away with config in the new DSL20:43
SpamapSMy thinking is if we can tap into the unified notifications bits that have been talked about on openstack-dev, we can use that.20:43
asalkeldSpamapS, +1 to a standalone tool that can respond to heat-engine quickly20:43
tspatzieradrian_otto: +1, we should do this20:43
shardyadrian_otto: it's not just config though, its triggering in-instance actions in response to stack updates20:44
SpamapSSo, as HOT is fleshed out, lets make sure we think about these tools as they will be important.20:44
tspatzierAre there concrete use cases documented somewhere?20:44
adrian_ottoI am looking at the https://review.openstack.org/#/c/28598/1/hot/WordPress_Single_Instance-alt1.yaml and I think we missed the mark a little20:44
adrian_ottothe idea is not to reconstruct the mappings in the DSL with options and inputs20:45
shardySpamapS: want to take an action to start a ML discssion on this topic?20:45
* stevebaker has to leave; later20:45
shardystevebaker: o/20:45
*** dprince has quit IRC20:45
SpamapStspatzier: when you replace your memcache server with a bigger server, the Metadata for your instances will all be changed. You want to re-apply config files to point at the new servers, re-start your app servers, and run cfn-signal to tell Heat you've completed that so its ok to move forward with orchestrating things dependent on that action.20:45
*** adjohn has quit IRC20:45
SpamapSshardy: I don't actually.. I think its premature.20:46
shardycfn-signal is just curl20:46
SpamapSshardy: I will add some notes to the HOT wiki page.20:46
sdakedefinitely need wait conditions20:46
shardySpamapS: Ok, as long as we start capturing some of the actual requirements somewhere20:46
tspatzieradrian_otto: sure, let's iterate on it. I laid much focus on cfn compatibility to keep supporting the content, but it's only a first shot20:46
adrian_ottook20:47
adrian_ottothanks for putting those up20:47
SpamapSshardy: right, thats what I'm going to add. I just think talking about the tools will get in the way of the HOT discussion.20:47
adrian_ottowe can polish them a bit more20:47
*** Yada has joined #openstack-meeting20:47
* asalkeld is not a fan of the mapping section20:47
shardySpamapS: Ok, well good to get the discussion started20:47
SpamapSadrian_otto: thats a nice direct translation, if we can make that work, we have something. Agreed that it has too many details about the systems to be the end goal.20:48
adrian_ottoSpamapS: YEP20:49
*** glikson has quit IRC20:49
shardyAny other topics to discuss?20:49
tspatzierSpamapS: nice use case. We handle this with actions attached to links in TOSCA (think of it as something like 'target-added', 'target-removed', 'target-changed' ...)20:50
SpamapSOnly that you are all amazing and its realy exciting to see all this steam build up behind Heat. :)20:50
randallburtbadumpump20:50
SpamapS:)20:50
* adrian_otto hits the hihiat20:50
shardyhaha20:51
* kebray wants to play cow bell.20:51
shardyYep, great job everyone :)20:51
shardyIf there's nothing else we can finish early?20:51
wirehead_well, given that this is heat, the calliope is our official musical instrument20:51
* shardy has to google calliope20:51
wirehead_steam powered musical instrument20:52
*** rushiagr has left #openstack-meeting20:52
SpamapSshardy: yes please make it stop20:52
shardy#endmeeting20:52
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:52
openstackMeeting ended Wed May  8 20:52:28 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-08-20.00.html20:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-08-20.00.txt20:52
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-08-20.00.log.html20:52
sdakespamaps lol20:52
shardythanks all20:52
wirehead_sorry for the final meeting-ending pun :D20:52
thervethanks shardy20:53
*** tspatzier has quit IRC20:53
*** shengjie has quit IRC20:53
*** shengjie_ has quit IRC20:53
*** flwang has joined #openstack-meeting20:54
*** SpamapS has left #openstack-meeting20:54
*** wirehead_ has left #openstack-meeting20:54
*** therve has left #openstack-meeting20:54
*** randallburt has left #openstack-meeting20:55
*** gordc has joined #openstack-meeting20:56
*** matiu has joined #openstack-meeting20:57
*** apmelton1 has joined #openstack-meeting20:57
*** shengjie has joined #openstack-meeting20:58
*** shengjie_ has joined #openstack-meeting20:58
*** danspraggins has joined #openstack-meeting20:58
*** n0ano has joined #openstack-meeting20:58
*** shengjie_ has quit IRC20:58
*** DanD has joined #openstack-meeting21:00
dhellmann#startmeeting ceilometer21:01
openstackMeeting started Wed May  8 21:01:35 2013 UTC.  The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: ceilometer)"21:01
openstackThe meeting name has been set to 'ceilometer'21:01
dhellmann#chair dhellmann21:01
openstackCurrent chairs: dhellmann21:01
dhellmann#link http://wiki.openstack.org/Meetings/MeteringAgenda21:01
dhellmannShow of hands, who is around for the ceilometer meeting?21:01
sandywalsho/21:01
dhellmanno/21:01
eglynno/21:01
litongo/21:01
flwango/21:01
salmon_o/21:01
n0anoo/21:02
asalkeldo/21:02
danspragginso/21:02
asalkeldwow that was fast21:02
dhellmann:-)21:02
dhellmann#topic Tracking of bug #1176017, releasing of MIM21:02
*** openstack changes topic to "Tracking of bug #1176017, releasing of MIM (Meeting topic: ceilometer)"21:02
uvirtbotLaunchpad bug 1176017 in ceilometer "Reinstate MongoDB testing with ming" [Critical,Confirmed] https://launchpad.net/bugs/117601721:02
apmelton1o/21:02
dhellmann#info dhellmann has contacted the upstream developers again (today) and is waiting for a reply21:02
dhellmannthis issue is related to getting MIM into a state where we can have our tests depend on it21:02
asalkeldwe really need that in21:02
dhellmannwe're negotiating the best approach21:03
dhellmannyeah21:03
*** jamespage_ has joined #openstack-meeting21:03
DanDo/21:03
*** adrian_otto has left #openstack-meeting21:03
dhellmannI hate to fork it, since they're open to giving us the keys to make releases, but communication is slow.21:03
*** zul has quit IRC21:04
dhellmannany other questions or comments on this before we move on?21:04
eglynnyeah, forking would be a last resort IMO21:04
*** dperaza has joined #openstack-meeting21:04
mrutkowsJoining Ceilometer meeting (late sorry)21:04
asalkeldwell, it could be a tempory measure21:04
dhellmannwelcome mrutkows, we're just getting started21:04
sandywalshdhellmann, we had to do the same thing with python-novaclient (which used to be a rackspace cloud client) ... no answer, we forked and moved on.21:04
dhellmannsandywalsh: we've had an answer, including an offer of getting the password to push releases21:05
dhellmannthen we hit OSDS, and jd__ and I were incommunicado for a while21:05
sandywalshah, gotcha21:05
dhellmannlet's give them a week and see where we get -- one of the guys is here in ATL so if he comes to the user group meeting tomorrow I can corner him21:05
*** adjohn has joined #openstack-meeting21:06
dhellmannjd__ wanted us to track this in our meetings until it's resolved, and to make sure everyone knew what was going on21:06
dhellmannlet's move on to the next topic21:06
dhellmann#topic Folsom support with G2 candidate21:06
*** openstack changes topic to "Folsom support with G2 candidate (Meeting topic: ceilometer)"21:06
dhellmann#link https://lists.launchpad.net/openstack/msg23332.html21:06
dhellmannWe have had several support requests or questions with old versions of ceilometer and folsom.21:06
dhellmannWhat level of support do we want/need to provide?21:06
* dhellmann hears crickets21:07
*** mkollaro has quit IRC21:07
asalkeldnot sure, it is expensive from a develop pov21:07
eglynnwe need to be actively pushing to deprecate Folsom if at all possible21:07
DanDdhellmann, is there a general policy on support of previous versions?21:07
DanDor is there anyone using ceilometer with folsom in production?21:08
eglynnat least getting the message accross that the Folsom support is strictly time limited21:08
dhellmannDanD: there is, but the folsom version of ceilometer doesn't strictly fall under those rules because it wasn't incubated21:08
eglynnDanD: ceilometer was only in incubation at Folsom time21:08
eglynn(so not stable/folsom branch etc.)21:08
DanDseems like thats the answer then :)21:09
*** hanney has quit IRC21:09
eglynnshardy was discussing the corresponding policy for Heat earlier21:09
dhellmannthat's what I think, too, but I thought we should talk about it :-)21:09
dhellmannto be clear, this was a pre-release version of grizzly ceilometer with other folsom components21:10
eglynnIIRC the idea was that heat:stable/grizzly would provde "best effort" support for folsom & grizzly21:10
dhellmannso I suspect it was people trying out ceilometer against their existing clouds21:10
*** nealph has joined #openstack-meeting21:10
dhellmannthat *should* work if they run ceilometer on a separate server so they don't have the version conflict with dependencies (esp. the client libs)21:10
asalkeldbe careful of "best-effort" more like occasional-effort21:10
eglynnnot actively test against folsom, but also not knowingly merge anything to stable/grizzlyy that's know the break folsom21:10
*** epende has joined #openstack-meeting21:10
dhellmannasalkeld: +1 on occasional-effort21:10
eglynnasalkeld: yep, I hear ya21:10
dhellmanneglynn: we've already passed the point where our grizzly code runs cleanly with folsom21:11
dhellmannafter g2 we started deleting some of the compatibility stuff21:11
*** johnpur has quit IRC21:11
dhellmannit is unusual to support mixed versions of components, isn't it?21:11
asalkeldyea21:11
asalkeldand makes things messy21:11
eglynndhellmann: OK, so it sounds like agressive pressure to move ceilo users off folsom is called for21:12
asalkeld(or hire devs)21:12
*** martine has quit IRC21:12
eglynn(the more we bend over backwards to support folsom, the slower folks will move off it I guess)21:12
dhellmanndo we need to make a formal statement about that somewhere, or just tell people we can't help them?21:13
asalkeldwe are not a huge team21:13
eglynnan agreed formal statement would be good21:13
flwangI think we need a statement for the support policy on the wiki or somewhere21:13
dhellmannok21:13
dhellmannjd__ isn't here, should I assign that to him? :-)21:14
asalkeldyea21:14
eglynngo for it! ;)21:14
*** sandywalsh has quit IRC21:14
DanDso is anyone currently running ceilometer against folsom in production?21:14
dhellmannDanD: I've no idea :-/21:14
asalkeldnot sure21:14
*** RajeshMohan has quit IRC21:14
dhellmannas I said, it's probably fine to do so if it is deployed in a way that separates the dependencies -- the RPC side didn't actually change all that much21:15
*** pcm__ has quit IRC21:15
dhellmann#action jd__ and dhellmann to write formal statement about limiting support for pre-grizzly versions of ceilometer21:15
dhellmannperhaps we will create a small market for contract work :-)21:16
*** lloydde has quit IRC21:16
asalkeldseriously niche21:16
flwanga start up for ceilometer support :)21:16
dhellmannok, moving on21:16
dhellmann#topic Priority of metadata features of SQL and HBase drivers21:16
*** openstack changes topic to "Priority of metadata features of SQL and HBase drivers (Meeting topic: ceilometer)"21:16
dhellmannI'm not sure what this one means. Who added it to the agenda?21:16
eglynnthat's from the release status meeting yesterday21:17
shengjiethis is about whether we should keep those bps as essential or just high priority21:17
*** zul has joined #openstack-meeting21:17
eglynnso we had two BPs on hbase & sqlalchemy metadata query support both with Essetntial priority set21:17
eglynnthis is a red flag to the release mgmt folks21:18
asalkeld # TODO implement metaquery support21:18
asalkeld        if len(metaquery) > 0:21:18
asalkeld            raise NotImplementedError('metaquery not implemented')21:18
*** sandywalsh has joined #openstack-meeting21:18
eglynn(as "Essential" == " we can't release Havana without this")21:18
dhellmannI'd be comfortable saying that about sqlalchemy, but not hbase21:19
flwangfor sqlalchemy, I think it's Esstential21:19
eglynnI think jd__'s motivation in setting these Essential was to ensure dev effort is dedicated to them early21:19
*** danwent has quit IRC21:19
asalkeldI think the sql version is more important21:19
eglynnOK we've alreasy downgrade hbase to High (with shengjie's agreement)21:19
eglynn*already21:19
shengjiewe are planning to do the HBase one anyway21:19
DanDat the summit there was a discussion about removing some drivers that didn't have full support21:20
shengjieso it doesn't make that much difference21:20
DanDwhat is the requirement in terms of updates and how they propgate into the drivers?21:20
*** shardy is now known as shardy_afk21:20
eglynnso conclusion is to keep sqlalchemy as Essential?21:20
*** vipul is now known as vipul|away21:20
flwangagree +121:20
asalkeldI think so eglynn21:20
eglynnDanD: yep the idea was a driver wouldn't be shipped until considered feature-complete21:21
asalkeldjust means we _really_ need to find someone to do it21:21
sandywalshsorry, vpn died, what's the concern with sqlalchemy?21:21
dhellmannDanD: I think that we agreed just to do that for new drivers, right?21:21
eglynn(various ideas around keeping on a branch or in a contrib dir until then ...)21:21
asalkeldsandywalsh, just we need everything implemeted21:21
eglynndhellmann: yep, just for new drivers IIRC21:21
dhellmannsandywalsh: whether finishing the metadata feature is "essential" or just "high" priority21:22
dhellmannwhile we're at it, how does this apply to the new alarm stuff asalkeld is doing?21:22
dhellmannI'm behind on reviews, are there changesets to update all of the storage drivers?21:22
DanDdhellman yes, that was the discussion. what I am trying to understand is what happens when a new API feature is added. who owns adding support for all the drivers?21:22
asalkeldwell I have done mongo and sql21:22
dhellmannDanD: right, like alarms21:22
*** jimbaker has quit IRC21:22
*** jimbaker has joined #openstack-meeting21:22
sandywalshdhellmann, right, we'll likely be going down that road as mysql is our main weapon ... not sure about our use of the metadata feature though21:22
ependeIf the v2 API depends heavily on metadata, that would seem to make it hard to ship w/o21:23
dhellmannsandywalsh: the metadata feature here is for querying against metadata values on resources, so it's pretty key for most realistic use cases21:23
sandywalshdhellmann, unless we point back to the underlying event as we'll be doing. But yes, we'll need "extra" attributes on aggregated metrics21:23
sandywalsh... at some point21:23
dhellmannI see a few options21:23
dhellmannI'm not sure what's best, though.21:24
asalkeldthis is the problem with adding new db drivers, adding new features get more and more complex21:24
dhellmannI think if we do drop drivers, we should do it later in the release cycle21:24
*** stevebaker has quit IRC21:24
*** gordc has quit IRC21:25
DanDwe should at least have a catalog of "required" meta data and test for those21:25
sandywalshsome db features should be considered essential and some optional (left to the driver maintainer)21:25
eglynnyep, once released, v. hard to drop if not initially marked as contrib/experimental21:25
sandywalshmetadata on metrics (if that's the only way to put extra attributes on metrics) ... should be essential21:25
sandywalshs/metrics/meters/21:25
asalkeldyip21:25
*** alexpilotti has joined #openstack-meeting21:26
eglynnmaybe we need to distinguish between "tier one" and "tier two" storage drivers21:26
sandywalsheglynn, t1 & t2 db api features, not drivers21:26
dhellmannour feature set is really small, though, is it worth that complexity?21:26
dhellmannotoh, if a driver doesn't support "alarms" but does support "meters" then it is still useful for some deployments21:27
sandywalshthat is, I shouldn't have to implement events in all drivers. So long as there is one reference driver implementation.21:27
dhellmannso maybe you're right, not "tiers" but list which features are fully supported21:27
shengjieasalkeld: +1 on the APIs should be splitter to to tiers21:27
shengjies/to/two/21:27
DanDso if a API feature is required an no one cares enough to update the driver, then it no longer qualifies and gets droppped?21:27
dhellmannDanD: no, but we do document that case21:27
*** dolphm has joined #openstack-meeting21:27
dhellmannthat way deployers can be informed21:27
shengjiesorry meant to +1 sandy21:28
asalkeldno worries21:28
dhellmannand maybe if a driver isn't being kept up to date with lots of new features, we consider dropping it21:28
sandywalshdhellmann, +121:28
eglynnor moving it out to a contrib dir21:28
*** danwent has joined #openstack-meeting21:28
dhellmanneglynn: meh, that's what git history is for21:28
shengjiesome of the features might be easy for sql , not easy for no-sql dbs21:28
litongnot only developers but also users , if an implementation can not keep up or has performance issues, then people will stop use it.21:28
asalkeldwell that indicates developer interest, not user intersest21:28
dhellmannshengjie: and the other way around, too21:29
DanDdhellmann so is it the responsiblity of the api server code to handle the fact that a driver doesn't implement a query?21:29
sandywalshit's a little tricky, since nosql is so easy to extend the schema in crazy ways, but a large effort in sql ... the nosql issue is when it comes to clustering, where sql shines.21:29
shengjiedhellmann: true21:29
litongI think it should be really just clearly documented. there is no need to really drop anything.21:29
eglynndhellmann: well contrib allows folks to continue to use it (at their own risk)21:29
dhellmannDanD: no, the API may just return errors21:29
ependedhellmann would no-op's be acceptable?21:29
sandywalshso, the mongo people can push the schema in ways that add a lot of work for the sql maintainers21:29
litong@dhellmann, or the api will just say it can not support that request.21:30
dhellmannepende: no, no-ops make it look like it's working when it isn't21:30
ependegood point21:30
dhellmannsandywalsh: we're all the same people, so we should be able to control for that21:30
dhellmannlitong: right, via an error message21:30
*** danflorea has joined #openstack-meeting21:30
*** ryanpetrello has quit IRC21:30
dhellmannI don't want to complicate the db api by having a way for the caller to ask "what do you do"?21:30
litongstatus code 50521:31
sandywalshdhellmann, +121:31
*** stevebaker has joined #openstack-meeting21:31
dhellmannok21:31
sandywalshthen the question becomes, should the functionality go in tests.storage.base or test.storage.test_<foo>21:31
litongif anyone really wants to support certain driver, then they will have to work harder to provide and maintain the driver.21:32
sandywalshif it's in the base, it should work for all drivers21:32
litongthis is Open Source after all.21:32
sandywalshif it's in the driver-specific test, it's optional21:32
dhellmannsandywalsh: we can segregate the tests for each feature and use scenarios to include the drivers that should be tested21:32
litong@sandywalsh, I think we are saying the samething.21:32
epende505 or 501?21:32
*** beagles has quit IRC21:32
dhellmannbut that's an implementation detail21:32
dhellmannwe can work out the exact error code later21:33
*** alexpilotti has quit IRC21:33
sandywalshlitong, yep, I think so21:33
litong@epende, I can go either way.21:33
dhellmannso it sounds like we've agreed that the db api will be defined in "chunks" and that a driver has to support a whole chunk or not claim to support it, is that right?21:33
dhellmannand then we will document that support21:33
eglynnsounds reasonble21:33
sandywalshyep21:33
asalkeldyea, ok21:33
shengjieagree21:34
eglynnclearly doc'd DB v. "functional chunk" matrix21:34
dhellmann#agreed the db api will be defined in "chunks" and that a driver has to support a whole chunk or not claim to support it. we will document which features are supported by each driver21:34
sandywalshand events are an optional chunk :p21:34
*** beagles has joined #openstack-meeting21:34
dhellmannsandywalsh: seems fair enough21:34
litongyes, clearly document what is working and what is not. with implementation returning either 501 or 50521:34
dhellmannwe have the base API now, the event API, and the alarm API21:35
ependelitong +121:35
dhellmannok, good. anything else to add before moving on?21:35
*** zul has quit IRC21:35
*** dosaboy has quit IRC21:35
shengjiewho should i talk to in terms of21:36
shengjieadding event APi alarm API to HBase21:36
dhellmannshengjie: probably sandywalsh21:36
sandywalshshengjie, looks like the alert api has landed already and I should be putting event api up this week.21:37
sandywalsh(in the db anyway)21:37
shengjiesandywalsh: cool, we take it off line then, Sandy21:37
dhellmannok, next topic21:37
dhellmann#topic Milestone assignment of Havana BPs21:37
*** jamespage_ has quit IRC21:37
*** openstack changes topic to "Milestone assignment of Havana BPs (Meeting topic: ceilometer)"21:37
*** dosaboy has joined #openstack-meeting21:37
sandywalshthe HP guys are going to be working on a web api proposal for events21:37
eglynnthat's another request from the release mgmt meeting yesterday21:37
dhellmann#link https://blueprints.launchpad.net/ceilometer/havana21:37
eglynnthat Havana BPs are lined up with individual milestones if possible21:37
eglynnh1, h2, h3 etc.21:37
dhellmannso we need to declare when we think we will finish each blueprint?21:38
eglynnmakes it easier for release mgr to track progress21:38
eglynnyes, an initial estimate at least21:38
dhellmannok21:38
dhellmannso, everyone should go do that this week! :-)21:38
eglynn(BPs can of course be bumped to a later milestone if necessary)21:38
eglynnyep, please do folks, it'll make Thierry happy :)21:38
dhellmann#action blueprint-owners, set milestones on all blueprints21:39
*** armax has left #openstack-meeting21:39
asalkeldis that only approved ones?21:39
eglynnyes, I would think so21:39
dhellmanndo we have any listed for havana that aren't approved?21:39
dhellmannah, yeah, "drafting"21:39
*** esker has joined #openstack-meeting21:39
DanDdhellman what is the deadline for submitting blueprints?21:40
eglynn"drafting" == "under the radar for now" ?21:40
dhellmannDanD: that's a question for jd__, but I thought it was before the summit21:40
sandywalshI have a "drafting" and to me it means "don't know what monsters live under those blankets just yet"21:40
eglynnLOL :)21:40
shengjieI have one waiting for approval21:41
sandywalsh:)21:41
asalkeldcrazy level of project management for an opensource project IMO21:41
dhellmannshengjie: prod jd__ to look at it?21:41
*** vipul|away is now known as vipul21:41
*** markmcclain has quit IRC21:41
dhellmannasalkeld: I think it gets more important when we have to coordinate with the doc team21:41
sandywalshasalkeld, it's all about the packaging apparently21:41
*** lbragstad has quit IRC21:41
eglynnre. submission deadline, I think a BP can still be submitted as long there's a developer willing to pick it up21:41
*** ayoung is now known as ayoung-afk21:41
eglynnDanD: ^^^21:42
*** hub_cap has joined #openstack-meeting21:42
shengjiedhellmann: eglynn is looking at it :)21:42
DanDdhellmann we put in an API blueprint but are still evaluating whether the current v2 API meets our requriements. I was assuming we would need to do a implementation blueprint if we find gaps21:42
DanDor are we covered with the one I reviewed at the summit?21:43
dhellmannDanD: good question :-/21:43
dhellmannis that one on the havana list?21:43
DanDdidn't see it. but we can check again21:43
dhellmannok. if it's not there, you should probably get something together asap21:44
DanDok21:44
dhellmannany other questions about blueprints?21:44
dhellmannok, moving on21:45
dhellmann#topic Open discussion21:45
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"21:45
salmon_I have a question21:45
flwangdhellmann, where can I get the calendar to add it into my Notes?21:45
asalkeldI could do with some ceilometerclient reviews21:45
dhellmannflwang: the havana schedule?21:46
flwangnope, the weekly meeting21:46
dhellmannasalkeld: I have a huge backlog, but I'll try to prioritize those21:46
asalkeldk21:46
salmon_I'm thinking about monitoring all users actions. Is ceilometer good place to implement such functionality?21:46
dhellmannflwang: there are links to HTML and ICS versions of the calendar on https://wiki.openstack.org/wiki/Meetings/MeteringAgenda#Agenda21:46
sandywalshsalmon_, the event mechanism will help with that.21:47
*** zul has joined #openstack-meeting21:47
dhellmannoops, I mean https://wiki.openstack.org/wiki/Meetings/MeteringAgenda#Weekly_Metering_meeting21:47
eglynnasalkeld: I'll pick up a few 1st thing tmrw also21:47
*** dani4571 has quit IRC21:47
asalkeldthanks eglynn21:47
dhellmannasalkeld: yeah, it will be at least 14 hrs for me, too21:47
sandywalshsalmon_, storing all the events that come out of nova, including the tenant id and Request ID ... essentially the entire user action.21:47
dhellmannsalmon_: what sandywalsh said :-)21:47
salmon_sandywalsh: but, is ceilometer designed to do such things?21:48
sandywalshsalmon_, it will be :)21:48
salmon_or is it just side effect?21:48
dhellmannsalmon_: we're building that feature during this release21:48
sandywalshsalmon_, that's the purpose of the feature21:48
flwangI remembered that you posted an google calendar last time, then I added this meeting into my notes calendar21:48
dhellmannthat's what the event feature is for21:48
salmon_ah, good :)21:48
sandywalshsalmon_, if you need something today, you can look at the ServerActions table in nova21:48
dhellmannflwang: https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics21:48
sandywalshsalmon_, but that's not a CM thing.21:49
salmon_sandywalsh: I need it also for glance so ServerActions is just part of solution21:49
dhellmann#link https://www.google.com/calendar/ical/h102rn64cnl9n2emhc5i3hjjso%40group.calendar.google.com/public/basic.ics21:49
litong@flwang, I tested that ics file and it worked great.21:49
litongon notes of course.21:49
sandywalshsalmon_, true21:49
dhellmannsalmon_: the event monitor in ceilometer will be able to listen to events from everywhere21:49
flwangcool, that's what I want, thanks dhellmann and litong21:49
salmon_dhellmann: cool21:49
*** afazekas has quit IRC21:50
dhellmanndoes anyone else have anything?21:51
shengjiedhellmann: btw, since we need more people working on HBase :) can u +2 this one https://review.openstack.org/#/c/28316/21:51
dhellmannshengjie: that's on my review backlog, but I'm dealing with some internal stuff at dh this week so I'm falling behind :-/21:51
shengjiedhellmann: I will force __jd to +2 it tomorrow, no worries :)21:52
dhellmannsounds good :-)21:52
dhellmannif that's all we have, we can end a few minutes early...21:52
litongif anyone can help review this patch, that will be great.21:52
litonghttps://review.openstack.org/#/c/27835/21:52
asalkeldlater all21:52
eglynncool, thanks all!21:52
*** litong has quit IRC21:53
dhellmannok, thanks everyone!21:53
dhellmann#endmeeting21:53
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:53
openstackMeeting ended Wed May  8 21:53:18 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:53
flwangthanks, dhellmann21:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-05-08-21.01.html21:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-05-08-21.01.txt21:53
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-05-08-21.01.log.html21:53
sandywalshthanks dhellmann21:53
sandywalshcheers y'all!21:53
*** danspraggins has quit IRC21:54
*** sacharya has quit IRC21:57
*** krtaylor has quit IRC21:59
*** salmon_ has quit IRC22:00
*** danflorea has quit IRC22:01
*** epende has quit IRC22:01
*** dhellmann has quit IRC22:02
*** mattray has joined #openstack-meeting22:03
*** m4dcoder has quit IRC22:04
*** anniec has quit IRC22:05
*** ijw has joined #openstack-meeting22:07
*** danwent has quit IRC22:09
*** lloydde has joined #openstack-meeting22:10
*** mrutkows has quit IRC22:10
*** anniec has joined #openstack-meeting22:13
*** boris-42 has quit IRC22:16
*** ivasev has quit IRC22:20
*** jlucci has quit IRC22:21
*** danwent has joined #openstack-meeting22:22
*** mrodden has quit IRC22:23
*** senhuang has quit IRC22:23
*** fesp has joined #openstack-meeting22:23
*** ladquin is now known as ladquin_brb22:25
*** jimbaker has left #openstack-meeting22:25
*** flaper87 has quit IRC22:25
*** eglynn has quit IRC22:27
*** shengjie has quit IRC22:28
*** flwang has quit IRC22:32
*** fnaval has quit IRC22:36
*** dolphm has quit IRC22:44
*** nealph has quit IRC22:44
*** fesp has quit IRC22:48
*** pfreund has quit IRC22:54
*** dolphm has joined #openstack-meeting22:54
*** kebray has quit IRC23:00
*** dperaza has quit IRC23:06
*** egallen has quit IRC23:07
*** lloydde has quit IRC23:08
*** mauilion has joined #openstack-meeting23:09
*** lloydde has joined #openstack-meeting23:09
*** egallen has joined #openstack-meeting23:10
*** jlucci has joined #openstack-meeting23:11
*** mauilion has quit IRC23:12
*** lloydde has quit IRC23:14
*** markpeek has quit IRC23:16
*** otherwiseguy has quit IRC23:17
*** ijw1 has joined #openstack-meeting23:17
*** ijw has quit IRC23:17
*** sacharya has joined #openstack-meeting23:18
*** acfleury has joined #openstack-meeting23:19
*** amyt has quit IRC23:19
*** egallen has quit IRC23:19
*** krtaylor has joined #openstack-meeting23:19
*** lloydde has joined #openstack-meeting23:31
*** fnaval has joined #openstack-meeting23:34
*** fnaval has quit IRC23:34
*** fnaval has joined #openstack-meeting23:35
*** hemna is now known as hemnafk23:37
*** ijw1 has quit IRC23:40
*** ijw has joined #openstack-meeting23:40
*** mdenny has quit IRC23:46
*** dolphm has quit IRC23:52
*** lloydde_ has joined #openstack-meeting23:54
*** rwsu is now known as rwsu-away23:55
*** lloydde has quit IRC23:56
*** FnordDownUnder has joined #openstack-meeting23:57
*** shang has quit IRC23:58

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