Wednesday, 2013-02-06

*** eharney has quit IRC00:02
*** lloydde has quit IRC00:02
*** lloydde has joined #openstack-meeting00:03
*** anniec has quit IRC00:03
*** anniec_ has joined #openstack-meeting00:03
*** fnaval has joined #openstack-meeting00:04
*** fnaval has quit IRC00:04
*** fnaval has joined #openstack-meeting00:05
*** ewindisch has quit IRC00:06
*** lloydde has quit IRC00:06
*** blamar has quit IRC00:12
*** blamar has joined #openstack-meeting00:12
*** nati_ueno has quit IRC00:13
*** kebray has joined #openstack-meeting00:14
*** kmartin is now known as kmartin_zz00:16
*** alexpilotti_ has joined #openstack-meeting00:18
*** alexpilotti__ has joined #openstack-meeting00:18
*** lcheng has quit IRC00:18
*** alexpilotti has quit IRC00:18
*** alexpilotti__ is now known as alexpilotti00:18
*** vkmc has quit IRC00:21
*** alexpilotti_ has quit IRC00:22
*** ewindisch has joined #openstack-meeting00:23
*** tr3buchet has joined #openstack-meeting00:23
*** ewindisch has quit IRC00:27
*** anteaya has quit IRC00:27
*** ewindisch has joined #openstack-meeting00:31
*** kebray has quit IRC00:32
*** nati_ueno has joined #openstack-meeting00:35
*** patelna_ has quit IRC00:35
*** markmcclain has quit IRC00:37
*** beagles_music_le is now known as beagles00:40
*** dwcramer has joined #openstack-meeting00:40
*** Nachi has joined #openstack-meeting00:40
*** nati_ueno has quit IRC00:43
*** nati_ueno has joined #openstack-meeting00:45
*** ewindisch has quit IRC00:45
*** dolphm has joined #openstack-meeting00:47
*** Nachi has quit IRC00:48
*** ewindisch has joined #openstack-meeting00:49
*** lbragstad has joined #openstack-meeting00:51
*** gongysh_ has joined #openstack-meeting00:58
*** chmouel has quit IRC01:03
*** sarob has joined #openstack-meeting01:14
*** mikor has quit IRC01:15
*** sarob has quit IRC01:16
*** sarob has joined #openstack-meeting01:16
*** dolphm has quit IRC01:20
*** nati_ueno has quit IRC01:31
*** topol has joined #openstack-meeting01:35
*** nati_ueno has joined #openstack-meeting01:36
*** ewindisch has quit IRC01:39
*** yuanz has quit IRC01:47
*** dwcramer has quit IRC01:48
*** hemna_ has joined #openstack-meeting01:50
*** hemna has quit IRC01:54
*** ryanpetrello has joined #openstack-meeting01:57
*** ewindisch has joined #openstack-meeting01:58
*** dwcramer has joined #openstack-meeting02:02
*** psedlak has joined #openstack-meeting02:05
*** alexpilotti has quit IRC02:05
*** jog0 has quit IRC02:16
*** Hg_ has quit IRC02:19
*** dprince has joined #openstack-meeting02:21
*** salv-orlando has quit IRC02:24
*** dosaboy has quit IRC02:25
*** dprince has quit IRC02:28
*** alrs has quit IRC02:30
*** bencherian has quit IRC02:40
*** dosaboy has joined #openstack-meeting02:40
*** ayoung has quit IRC02:48
*** colinmcnamara1 has joined #openstack-meeting02:51
*** colinmcnamara has quit IRC02:53
*** colinmcnamara1 has quit IRC02:56
*** yaguang has joined #openstack-meeting02:59
*** otherwiseguy has joined #openstack-meeting03:02
*** yuanz has joined #openstack-meeting03:05
*** dwcramer has quit IRC03:07
*** alrs has joined #openstack-meeting03:07
*** anniec_ has quit IRC03:09
*** ijw has quit IRC03:13
*** dwcramer has joined #openstack-meeting03:20
*** devananda has quit IRC03:20
*** devananda has joined #openstack-meeting03:21
*** martine has joined #openstack-meeting03:23
*** danwent has quit IRC03:24
*** nati_ueno has quit IRC03:28
*** woodspa has quit IRC03:32
*** novas0x2a|laptop has quit IRC03:33
*** maurosr has quit IRC03:36
*** same5336 has quit IRC03:37
*** same5336 has joined #openstack-meeting03:38
*** vipul|away is now known as vipul03:39
*** anniec has joined #openstack-meeting03:39
*** vipul is now known as vipul|away03:39
*** markvan has joined #openstack-meeting03:42
*** colinmcnamara has joined #openstack-meeting03:42
*** ijw has joined #openstack-meeting03:46
*** yaguang has quit IRC04:00
*** yaguang has joined #openstack-meeting04:04
*** bdpayne has quit IRC04:08
*** otherwiseguy has quit IRC04:08
*** dwcramer has quit IRC04:23
*** bdpayne has joined #openstack-meeting04:24
*** sdake has quit IRC04:24
*** anniec has quit IRC04:27
*** markmcclain has joined #openstack-meeting04:28
*** yaguang has quit IRC04:29
*** martine has quit IRC04:34
*** jdurgin1 has joined #openstack-meeting04:37
*** sandywalsh_ has quit IRC04:37
*** dwcramer has joined #openstack-meeting04:38
*** martine has joined #openstack-meeting04:40
*** yaguang has joined #openstack-meeting04:42
*** iben has joined #openstack-meeting04:45
*** martine has quit IRC04:45
*** bencherian has joined #openstack-meeting04:46
*** novas0x2a|laptop has joined #openstack-meeting04:58
*** alrs has quit IRC05:07
*** devananda has quit IRC05:08
*** ryanpetrello has quit IRC05:08
*** sarob has quit IRC05:15
*** alrs has joined #openstack-meeting05:34
*** reed has quit IRC05:40
*** stevebaker has quit IRC05:41
*** bencherian has quit IRC05:43
*** koolhead17 has joined #openstack-meeting05:45
*** enikanorov has quit IRC06:09
*** markvan has quit IRC06:09
*** enikanorov has joined #openstack-meeting06:10
*** bdpayne has quit IRC06:17
*** colinmcnamara has quit IRC06:18
*** markmcclain has quit IRC06:19
*** bencherian has joined #openstack-meeting06:22
*** bdpayne has joined #openstack-meeting06:23
*** mnewby has quit IRC06:27
*** shang__ is now known as shang06:33
*** iben has quit IRC06:33
*** garyk has joined #openstack-meeting06:33
*** iben has joined #openstack-meeting06:33
*** iben has quit IRC06:38
*** koolhead17 has quit IRC06:43
*** bdpayne has quit IRC06:46
*** henrynash has joined #openstack-meeting07:00
*** flaper87 has joined #openstack-meeting07:04
*** reed has joined #openstack-meeting07:11
*** mrunge has joined #openstack-meeting07:13
*** topol has quit IRC07:16
*** Mandell has quit IRC07:23
*** henrynash has quit IRC07:24
*** bencherian has quit IRC07:26
*** bencherian has joined #openstack-meeting07:29
*** psedlak has quit IRC07:46
*** rafaduran has joined #openstack-meeting08:08
*** davidha has quit IRC08:13
*** henrynash has joined #openstack-meeting08:14
*** sleepsonthefloor has quit IRC08:19
*** jhenner has joined #openstack-meeting08:25
*** zul has quit IRC08:28
*** zul has joined #openstack-meeting08:33
*** adjohn has quit IRC08:35
*** psedlak has joined #openstack-meeting08:38
*** psedlak has quit IRC08:38
*** psedlak has joined #openstack-meeting08:41
*** psedlak has quit IRC08:46
*** psedlak has joined #openstack-meeting08:47
*** shang has quit IRC08:47
*** psedlak has quit IRC08:47
*** ketan985 has joined #openstack-meeting08:47
*** psedlak has joined #openstack-meeting08:49
*** bencherian has quit IRC08:52
*** derekh has joined #openstack-meeting09:04
*** adjohn has joined #openstack-meeting09:06
*** adjohn has quit IRC09:15
*** salv-orlando has joined #openstack-meeting09:16
*** davidha has joined #openstack-meeting09:18
*** darraghb has joined #openstack-meeting09:22
*** stevebaker has joined #openstack-meeting09:33
*** adjohn has joined #openstack-meeting09:42
*** vkmc has joined #openstack-meeting09:42
*** yaguang has quit IRC09:45
*** adjohn has quit IRC09:46
*** davidha has quit IRC10:01
*** davidha has joined #openstack-meeting10:01
*** alexpilotti has joined #openstack-meeting10:02
*** yaguang has joined #openstack-meeting10:09
*** adjohn has joined #openstack-meeting10:12
*** corrigac has quit IRC10:13
*** adjohn has quit IRC10:17
*** ccorrigan has joined #openstack-meeting10:18
*** afazekas has joined #openstack-meeting10:29
*** adjohn has joined #openstack-meeting10:43
*** adjohn has quit IRC10:47
*** maurosr has joined #openstack-meeting10:50
*** davidha has quit IRC11:10
*** yaguang has quit IRC11:11
*** adjohn has joined #openstack-meeting11:14
*** henrynash_ has joined #openstack-meeting11:18
*** adjohn has quit IRC11:18
*** henrynash has quit IRC11:19
*** henrynash_ is now known as henrynash11:19
*** henrynash has quit IRC11:28
*** henrynash has joined #openstack-meeting11:33
*** ketan985 has quit IRC11:43
*** adjohn has joined #openstack-meeting11:45
*** davidha has joined #openstack-meeting11:47
*** adjohn has quit IRC11:49
*** dosaboy has quit IRC11:53
*** dosaboy has joined #openstack-meeting11:53
*** alrs has quit IRC11:54
*** alrs has joined #openstack-meeting11:55
*** amotoki has quit IRC12:35
*** dosaboy has quit IRC12:39
*** sandywalsh has joined #openstack-meeting12:40
*** dosaboy has joined #openstack-meeting12:54
*** anniec has joined #openstack-meeting12:54
*** dosaboy has quit IRC12:59
*** ijw has quit IRC13:01
*** ijw has joined #openstack-meeting13:01
*** dosaboy has joined #openstack-meeting13:02
*** dolphm has joined #openstack-meeting13:04
*** anniec has quit IRC13:06
*** anniec has joined #openstack-meeting13:06
*** ctracey has quit IRC13:14
*** ctracey has joined #openstack-meeting13:15
*** john12345 has joined #openstack-meeting13:17
*** markvoelker has joined #openstack-meeting13:22
*** dwcramer has quit IRC13:33
*** jaypipes has quit IRC13:36
*** otherwiseguy has joined #openstack-meeting13:37
*** annegentle has joined #openstack-meeting13:45
*** adjohn has joined #openstack-meeting13:47
*** adjohn has quit IRC13:52
*** anteaya has joined #openstack-meeting13:52
*** markmcclain has joined #openstack-meeting14:00
*** john12345 has quit IRC14:00
*** ryanpetrello has joined #openstack-meeting14:03
*** awataszko has quit IRC14:03
*** chmouel has joined #openstack-meeting14:05
*** awataszko has joined #openstack-meeting14:05
*** jaypipes has joined #openstack-meeting14:06
*** annegentle has quit IRC14:07
*** otherwiseguy has quit IRC14:08
*** markvan has joined #openstack-meeting14:13
*** jhenner has quit IRC14:14
*** esker has joined #openstack-meeting14:16
*** adjohn has joined #openstack-meeting14:18
*** esker has quit IRC14:18
*** joesavak has joined #openstack-meeting14:22
*** egallen has joined #openstack-meeting14:22
*** adjohn has quit IRC14:23
*** woodspa has joined #openstack-meeting14:26
*** otherwiseguy has joined #openstack-meeting14:30
*** gongysh_ has quit IRC14:39
*** martine_ has joined #openstack-meeting14:40
*** awataszko has quit IRC14:41
*** awataszko has joined #openstack-meeting14:42
*** matiu has quit IRC14:43
*** mattray has joined #openstack-meeting14:46
*** matiu has joined #openstack-meeting14:47
*** martine_ has quit IRC14:48
*** adjohn has joined #openstack-meeting14:48
*** martine_ has joined #openstack-meeting14:50
*** adjohn has quit IRC14:53
*** ryanpetrello has quit IRC14:54
*** lbragstad has quit IRC14:55
*** fnaval has quit IRC14:56
*** eharney has joined #openstack-meeting15:01
*** blamar has quit IRC15:02
*** mrodden has joined #openstack-meeting15:04
*** bdpayne has joined #openstack-meeting15:06
*** dprince has joined #openstack-meeting15:09
*** ayoung has joined #openstack-meeting15:09
*** ryanpetrello has joined #openstack-meeting15:15
*** fnaval has joined #openstack-meeting15:16
*** dwcramer has joined #openstack-meeting15:18
*** adjohn has joined #openstack-meeting15:19
*** iben has joined #openstack-meeting15:21
*** adjohn has quit IRC15:24
*** maoy has joined #openstack-meeting15:25
*** iben has quit IRC15:25
*** iben has joined #openstack-meeting15:25
*** iben has quit IRC15:30
*** lbragstad has joined #openstack-meeting15:31
*** rnirmal has joined #openstack-meeting15:33
*** vkmc has quit IRC15:38
*** maoy_ has joined #openstack-meeting15:39
*** maoy has quit IRC15:41
*** maoy_ is now known as maoy15:41
*** rushiagr has joined #openstack-meeting15:42
*** markwash has quit IRC15:45
*** topol has joined #openstack-meeting15:47
*** winston-d_ has joined #openstack-meeting15:49
*** adjohn has joined #openstack-meeting15:50
*** jgallard has joined #openstack-meeting15:52
*** noslzzp has joined #openstack-meeting15:53
*** derekh is now known as derekh_brb15:54
*** Gordonz has joined #openstack-meeting15:54
*** adjohn has quit IRC15:55
*** smulcahy has joined #openstack-meeting15:55
*** bvibhu has joined #openstack-meeting15:57
*** thingee has joined #openstack-meeting15:57
*** derekh_brb is now known as derekh15:58
*** blamar has joined #openstack-meeting15:58
*** bswartz has joined #openstack-meeting16:00
*** garyTh has joined #openstack-meeting16:00
*** xyang_ has joined #openstack-meeting16:01
*** pschaef has joined #openstack-meeting16:01
*** DuncanT1 is now known as DuncanT16:01
DuncanT#startmeeting Cinder16:01
openstackMeeting started Wed Feb  6 16:01:41 2013 UTC.  The chair is DuncanT. 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
*** JM1 has joined #openstack-meeting16:01
openstackThe meeting name has been set to 'cinder'16:01
*** Mr_T has left #openstack-meeting16:01
DuncanTLo all16:01
JM1hi16:01
bswartzhi16:01
hemna_:)16:01
winston-d_hi16:01
xyang_hi16:01
rushiagrhi16:01
*** Yada has joined #openstack-meeting16:02
thingeeo/16:02
*** jsavak has joined #openstack-meeting16:02
eharneyhi16:02
*** jbrogan has joined #openstack-meeting16:02
DuncanTJGriffith is away, so he's asked me to chair. There's the bare bones of an agenda at http://wiki.openstack.org/CinderMeetings as usual but PM me or shout up if there's something you want to discuss16:02
hemna_So I saw avishay's comments on his issues he's having with FC16:03
hemna_I'm going to try and see if I can dig up a QLogic HBA today at work and try and reproduce his issues.16:03
*** kmartin_zz is now known as kmartin16:04
DuncanTFC still isn't merged, correct?16:04
hemna_correct16:04
DuncanT(sorry, been away for a bit, still playing catchup)16:04
hemna_it's been getting a good amount of reviews from the nova guys lately though16:04
DuncanTSounds like testing is progressing anyway, which is great16:04
hemna_yup16:04
*** adjohn has joined #openstack-meeting16:04
DuncanTAnything else you need16:05
*** joesavak has quit IRC16:05
DuncanT?16:05
hemna_don't think so16:05
DuncanTGood stuff16:05
*** markmcclain has quit IRC16:05
DuncanTThe only blueprint I'm involved with is volume backup... we're fixing uuids and iscsi attach and a new review will be up shortly. I don't understand the comments from ronenkat but I'm hoping they'll get back to me with more detail16:06
hemna_need more eyes for the review?16:07
bswartzDuncanT: is volume backup working completely now?16:08
DuncanTbswartz: Multi-node is broken in some cases until the iscsi attach change turns up16:08
thingeeDuncanT: some of the questions I've been asking about coverage with the backup manager seemed to get missed last time. Francis was saying it has 100% but I just can't see that with coverage report.16:08
*** john5223 has joined #openstack-meeting16:08
*** markmcclain has joined #openstack-meeting16:09
bswartzDuncanT: cool16:09
DuncanTthingee: He's going to mail you about that... definitely not seeing what you're seeing16:09
smulcahythingee: We've re-ran the coverage report on fresh devstacks with the branch and we're getting very different coverage reports16:09
smulcahythingee: So not sure why the discrepancy16:09
DuncanThemna: More eyes are always good, particularly as we thing the next patch will be pretty much done, except possibly some testing issues16:10
thingeeit must be something weird in my env. I'll try a fresh repo this time instead of just new venv16:10
thingeesmulcahy, DuncanT ^16:10
DuncanTthingee: Thanks for that16:10
hemna_coolio16:11
DuncanTAny other blueprints to comment on? Multi backend scheduler?16:11
smulcahythingee: thanks - yeah, maybe try from scratch because we're not seeing your coverage results.16:11
thingeeDuncanT: o/16:11
winston-d_yup16:11
DuncanTthingee: Yup16:12
thingeeDuncanT: cinderclient v2 is up for review.16:12
thingeeDuncanT: jgriffith mentioned he wanted args to be consistent. I'll make a comment to the review and switch back to wip16:12
DuncanTOoo, hadn't spotted that16:12
winston-d_i have some comment with multi back-end volume service patch. but haven't gone through the whole patch yet. i'll talk to hub_cap offline16:12
rushiagrand so is 'NAS as a separate service' code16:12
thingeeDuncanT: I'm going to deprecate the other arg style for a release so everyone is happy :)16:13
DuncanTthingee: People are never happy16:13
thingeeDuncanT: I'm happy16:13
DuncanTWe've a general plea for reviews... quite a few open and quite a few un-responded to review comments16:14
thingeeDuncanT: docs are coming along. not too worried about "feature freeze" deadline with 'em ;)16:14
DuncanThttps://review.openstack.org/#/q/status:open+project:openstack/cinder,n,z16:14
thingeeDuncanT: v1 doc is just about done. will be doing that more and maybe starting v2 over the weekend16:14
DuncanThttps://review.openstack.org/#/q/status:open+project:openstack/python-cinderclient,n,z16:15
DuncanTthingee: Good stuff. Will take a look at the v2 client stuff asap16:15
bswartzDuncanT: is there any way we, as reviewers, can prioritize what to review?16:16
*** jbr_ has joined #openstack-meeting16:16
thingeebswartz: yea hang on16:16
thingeebswartz: https://launchpad.net/cinder/+milestone/grizzly-316:16
winston-d_bswartz: i think those reviews that are targeted to G3 should come first16:16
thingeebswartz: whatever is in code review16:16
DuncanTbswartz: I tend to go with stuff I've previously commented on that has been updated, followed by G3 stuff16:17
bswartzokay, all good suggestions16:17
DuncanTbswartz: I also encourage people to shout up when they've something they feel is being ignored16:17
bswartzit would be ideal if we there was a way to minimize overlapping review work so everything gets equal coverage, but perhaps that's not possible16:17
bswartzDuncanT: +1 that works too16:17
xyang_what about reviews for bug fixes?  they are not targeted, but have to go in, right16:18
bswartzxyang_: technically, bugfixes could go in after G-316:18
*** bdpayne has quit IRC16:19
xyang_bswartz: ok16:19
thingeexyang_: you can ping core devs available in #openstack-cinder too16:19
thingeeor #openstack-dev16:19
bswartzthat's not a reason to ignore them, but they feel lower priority to me than new features16:19
*** lloydde has joined #openstack-meeting16:19
thingeeDuncanT: what else?16:19
xyang_thingee: ok16:20
DuncanT#topic Policy on what's required for a new driver16:20
Yadawhat about bugs which impact BP devs (volume_create issues) ?16:20
*** openstack changes topic to "Policy on what's required for a new driver (Meeting topic: Cinder)"16:20
DuncanTYada: If you think something needs bumping up the priority, your best bet is to poke people in #openstack-cinder16:20
*** joesavak has joined #openstack-meeting16:21
DuncanTYada: Most of the core team hang about in there, and are more likely to be responsive to people being keen16:21
YadaWe will cause it may block our cinder BP approval : currently not working anymore (was ok days ago) ;-)16:21
YadaWorking on it to dig and provide as much infos as possible16:22
DuncanTYada: Will follow up with you in the cinder room after the meeting if you want16:22
Yadano worries16:22
DuncanTSo John posted something to the openstack mailing list a week and a bit ago about minimum features in new drivers16:23
DuncanTI can't find it right now but the gist was that new drivers should be at least as functional as the LVM one is at time of merging, unless they explain why they can't be16:23
thingeeDuncanT: I haven't been able to find it either. Maybe that's why he feels he got no reply :P16:24
DuncanTSince nobody replied, this is likely to become policy unless somebody complains sharpish16:24
*** jsavak has quit IRC16:24
DuncanTthingee: I did find it earlier... it was a reply down a thread16:24
DuncanTAh ha, in the thread "[Openstack] List of Cinder compatible devices"16:25
DuncanT"Having to go through and determine what feature is or is not  supported per driver is EXACTLY what I want to avoid. If we go down the  path of building a matrix and allowing partial integration it's going to  create a huge mess and IMO the user experience is going to suffer  greatly.  Of course a driver can do more than what's on the list, but I  think this is the minimum requirement and I've been pushing back on  submissions based o16:25
rushiagrthe problem is partly due to his sentences come at the very bottom of the mail16:25
kmartinYeah, I missed it as well...maybe he could add it to http://wiki.openstack.org/Cinder16:25
YadaYep he replied to an email from : Xiazhihui (Hashui, IT) <xiazhihui09@huawei.com>16:25
bswartzDuncanT: so that policy implies that as new features are added to the LVM driver, all of the other drivers have to catch up eventually -- can we say something about how quickly that needs to happen?16:25
DuncanTbswartz: I'd like a statement about that too, but not sure how to word it16:26
JM1it would also be useful to list said features16:26
DuncanTbswartz: Certainly I'd like a policy where we can threaten to drop unmaintained drivers16:26
bswartzJM1: +116:26
DuncanTJM1: +116:26
DuncanTJM1: Any such list becomes stale if it is external to the code, but certainly a list of 'as of xxx date, the minimum feature list is...'16:27
DuncanTAnybody got a problem with the concept?16:28
kmartinclearly list each feature that needs implemented and add it to http://wiki.openstack.org/Cinder, since all new developers tend to start there16:28
winston-d_nope, sounds good to me16:28
*** sdake has joined #openstack-meeting16:28
JM1kmartin: +116:28
xyang_+116:28
rushiagrkmartin: +1, good point16:28
YadaBased on my understanding and chat with John it is : Volume create | delete | attach | detach + Snapshot create | delete + Create Volume from Snapshot16:28
bswartzalso, if a driver needs to updated to comply with a new feature, does that update count as a bugfix, or does it need a blueprint, and milestone, etc16:28
DuncanTbswartz: bugfix in general I think16:29
JM1how about volume to/from image?16:29
xyang_there's a generic function now in driver.py16:29
DuncanTJM1: That and clone are there now in LVM, so I guess they are needed for a new driver16:29
kmartinEach new release the list of features should be revisted and updated16:29
xyang_I'm testing that function, but have to override something to get it to work16:29
*** ijw has quit IRC16:30
*** johngarbutt has joined #openstack-meeting16:30
*** ijw has joined #openstack-meeting16:30
kmartinJM1: some of the new features should have a little lag time for the drivers to be updated, like the next release.16:30
*** colinmcnamara has joined #openstack-meeting16:31
DuncanTNext milestone release or next full release?16:31
*** colinmcnamara has quit IRC16:31
kmartinNext full release, some features are not completed until the last sprint and its hard for all the drivers to get updated that quickly16:32
bswartzkmartin: +116:32
*** colinmcnamara has joined #openstack-meeting16:32
YadaAnd what about the new BP ? Will be "fair" if it is the same rules for all and if it does not block BP validation IMHO16:32
*** psedlak has quit IRC16:32
*** afazekas has quit IRC16:32
DuncanTFair enough, though I think we should strongly encourage quicker updates where we can16:33
DuncanTYada: I don't understand the question sorry16:33
kmartinDuncanT: I agree, strongly encouraged but not required16:34
bswartzI know speaking for NetApp, we have development schedules, and it's not always easy to make time for stuff that comes up at the last minute. However if driver changes to comply with new features count as bugfixes then that relaxes the deadline to get them done.16:34
*** adjohn has quit IRC16:34
YadaI mean : if all agree on the minimum cinder features supported than can we apply the same for the new BP instead of asking new BP to commit on all the features I listed above16:34
xyang_any new feature need legal approval too, that could take very long16:34
kmartinHave to remember some of these features may require legal approval from the bigger companies...and we all know how fast that happens16:35
DuncanTkmartin: I work for HP too, I know your pain ;-)16:35
kmartinxyang_: :) beat me to it16:35
xyang_kmartin:  :)16:36
DuncanTYada: That makes sense, though sometimes it is a matter for taste... we can discuss exceptions at these meetings16:36
DuncanTRight, it sounds like we have a general agreement. Any volenteers to draft it on the wiki?16:36
DuncanTAnybody at all?16:37
kmartinHell, I'll do it16:38
DuncanT:-)16:38
DuncanT#action kmartin to draft new driver policy for the wiki16:38
winston-d_phew16:38
DuncanTSo the last item on our agenda is...16:38
DuncanT#topic AZs (again)16:39
*** openstack changes topic to "AZs (again) (Meeting topic: Cinder)"16:39
jgriffithsorry... but legal ain't my problem :)16:39
thingeehe lives16:39
jgriffith:)16:39
thingeeDuncanT: are we educated in this topic now?16:39
DuncanTthingee: I don't think so, no16:39
thingeemake that an action item :P...someone should take lead and get that figured out16:40
* jgriffith pretends he's not back yet :)16:40
DuncanTWe have our own ideas, but it comes down to 'There is an AZ field in several parts of our API. What do we want it to mean?'16:41
jgriffithI'll look at getting something documented16:41
jgriffithDuncanT: not that simple16:41
jgriffithDuncanT: It actually has a distinct meaning16:41
jgriffithDuncanT: Particularly in the context of EC216:41
jgriffithDuncanT: You can only attach volumes to instances in the same AZ16:41
winston-d_so who raised this issue?16:41
DuncanTwinston-d_: Me16:41
bswartzjgriffith: we assigned all the action items to you while you were gone16:42
jgriffithhaha :)16:42
DuncanTjgriffith: I'm not sure of the details of the EC2 API16:42
bswartzjk16:42
winston-d_then  you should educate us, at least a problem statement16:42
jgriffithwinston-d_: who me?16:42
*** avishay has joined #openstack-meeting16:42
jgriffithwinston-d_: I'm not the one who asked what they were :)16:43
avishayHi all, sorry I'm (very) late16:43
winston-d_DuncanT: ^^16:43
jgriffithwinston-d_: Ohh... :)16:43
DuncanTwinston-d_: The problem is that the fields in the API currently don't do much in relation to the same fields in the nova api16:43
*** bdpayne has joined #openstack-meeting16:43
DuncanTThey have no clear meaning, and inconsitent behaviour16:43
xyang_avishay:  hi.  can I talk to you after the meeting?  I'm merging with your changes but have issues16:44
DuncanT*consistent16:44
avishayxyang_: of course16:44
jgriffithDuncanT: hmmm... interesting16:44
*** annegentle has joined #openstack-meeting16:44
jgriffithSo I'll look at getting this documented and cleared up a bit16:44
winston-d_what kind of consistency are you looking for ?16:44
DuncanTNova seems to treat them as a specific specialisation of aggregates that the scheduler treats specially16:44
jgriffithDuncanT: That's new :(16:45
jgriffithDuncanT: so we have to play some catch up16:45
*** johngarbutt has quit IRC16:45
jgriffithThe disparity you see currently is because they've moved forward with aggregates and such16:45
DuncanTwinston-d_: A definition of what they mean, and what the limitations are (e.g. can an instance in az-xyz mount a volume in az-abc?)16:45
*** johnthetubaguy has joined #openstack-meeting16:46
*** devananda has joined #openstack-meeting16:46
DuncanT(I hope the answer to that ends up being 'no', but currently it isn't enforced (draft patch from a colleague to fix that in the queue) but currently no two people seem to entirely agree)16:46
winston-d_the 2nd part of the question is controlled by Nova API or Cinder API?16:46
DuncanTwinston-d_: Both16:47
DuncanTwinston-d_: Can you clone a volume between AZs? (pure cinder)16:47
DuncanTwinston-d_: Attach is a decision for both16:47
DuncanTwinston-d_: There are other questions16:47
DuncanT#action jgriffith and DuncanT to look at documenting availability zones16:48
jgriffith:)16:48
winston-d_how do OPS people think about it?  do think they nova/cinder should allow such action?16:48
winston-d_since AZ is defined by them16:49
DuncanTI have no idea what providers are using availability zones. We are, I'm pretty sure Rackspace don't16:49
*** danwent has joined #openstack-meeting16:49
jgriffithSo the best advice I can provide for a quick overview is lookat AWS16:49
*** cp16net is now known as cp16net|away16:49
winston-d_AWS did16:49
*** cp16net|away is now known as cp16net16:49
DuncanTwinston-d_: There is no definition of an AZ, so different people have totally different models in mind16:49
jgriffithThta's it was intially modeled after16:49
*** anniec has quit IRC16:49
winston-d_DuncanT: that is the real problem i guess16:49
DuncanTwinston-d_: Cells have removed some of the confusion I think16:49
jgriffithDuncanT: I'd argue that cells introduced more confusion but anyway :)16:50
winston-d_DuncanT: but cell is transparent to end user (aka API)16:50
DuncanTwinston-d_: We (HP) don't want cross az mounting16:50
jgriffithOK... time out16:50
jgriffithNo sense beating on this right now16:50
DuncanTwinston-d_: Indeed, so pan-cell mounting is a 'it should just work'16:50
jgriffithDuncanT: and jgriffith will flush this out and doc it for folks16:50
*** maurosr has quit IRC16:51
rushiagrAWS has cells too? or is it a new concept by us folks?16:51
DuncanTrushiagr: Unknown since they aren't user visible16:51
winston-d_rushiagr: no, we don't know since it transparent to end users16:51
jgriffithWell never mind then... carry on :)16:51
winston-d_jgriffith: :)16:52
DuncanTSo, any other business? We've ten minutes left16:52
DuncanT#topic any other business16:52
*** openstack changes topic to "any other business (Meeting topic: Cinder)"16:52
DuncanTjgriffith?16:52
jgriffithI don't have much, but I haven't gone through evertyhging you guys covered yet16:53
jgriffithMy main thing is the usual plea for reviews :)16:53
jgriffithWe're getting a pretty good back-log again16:53
jgriffithJust a note on stable/folsom16:53
jgriffithThose patches need to be reviewed/approved by OSLO core team16:53
*** vipul|away is now known as vipul16:54
rushiagrjgriffith: Status of blueprint: NAS as a separate service. WIP submitted.16:54
jgriffithrushiagr: Saw that... thanks!16:55
DuncanTWith core team discussions coming up, I expect people will be extra keen on reviews ;-)16:55
jgriffithrushiagr: It helps a TON to have something in progress for folks to work on16:55
DuncanTrushiagr: Got a link to that?16:55
rushiagrDuncanT: https://review.openstack.org/#/c/21290/16:56
DuncanTCheers16:56
avishayI'd like to bring up a topic to start thinking about - a framework for certifying hardware16:56
rushiagrjgriffith: I know, its better than having a multi thousand line code drop at the last moment16:57
winston-d_wow, big topic16:57
bswartzavishay: rackspace is working on something like that16:57
avishayThe Nova FC code doesn't happen to work with my HBA.  We'll try to fix that.  But there should be a way to certify hardware (HBAs, controllers, etc.).16:57
bswartzare you in touch with them?16:57
avishaybswartz: No.  I'd appreciate any pointers.16:58
*** maurosr has joined #openstack-meeting16:58
bswartzavishay: I will get some and get back to you16:58
avishaybswartz: thanks a lot16:58
bswartzIt's called Alamo16:58
DuncanTWould be good to hear about those plans too16:58
jgriffithI'd rather focus first on black-box driver qualification16:59
jgriffithBut I agree... if we're going down the paths folks seem to be taking us these days, Hardware may start to become an issue16:59
bswartzAlamo has a driver+hardware qualification suite16:59
avishayjgriffith: That too16:59
*** Mr_T has joined #openstack-meeting17:00
xyang_bswartz: Alamo doesn't cover unreleased code though.  I think avishay is asking about that17:00
avishayjgriffith: sounds something to discuss at the summit17:00
*** bobba has joined #openstack-meeting17:00
avishayxyang_: not necessarily17:00
bswartzI think it's reasonable to say that the cinder core team will NOT worry about hardware qualification, and we will leave that to distros and vendors who support this stuff?17:00
jgriffithavishay: +117:01
avishayxyang_: but there should be some "official" test suite that vendors can run to make sure their HW works with OpenStack17:01
DuncanT+1million17:01
jgriffithbswartz: I would agree up to a point17:01
jgriffithbswartz: since we're going to introduce things like FC we have to be slightly more pro-active I htink17:01
jgriffiththink17:01
DuncanTThe trouble with 'official tests' is they turn into 'it passes the test suite, cinder must be broken'17:01
jgriffithTBH to me that just means... "supported HBA/driver list"17:02
jgriffithbswartz: but I would agree, that should fall to the vendors who want/use FC17:02
xyang_avishay:  good idea17:02
DuncanTSupported by whom?17:02
jgriffithbswartz: else from my perspective, take FC out17:02
jgriffithDuncanT: Supported is a bad choice of words17:02
DuncanT:-)17:02
bswartztime check, we're about to get booted17:03
DuncanTI've been spending too much time around lawyers ;-)17:03
jgriffithhaha17:03
DuncanTAny final words?17:03
JM1"rosebug"17:03
DuncanT#endmeeting17:03
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:03
openstackMeeting ended Wed Feb  6 17:03:38 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-02-06-16.01.html17:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-02-06-16.01.txt17:03
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-02-06-16.01.log.html17:03
*** tongli has joined #openstack-meeting17:04
*** davidha has quit IRC17:04
*** avishay has left #openstack-meeting17:04
johnthetubaguy#startmeeting XenAPI17:04
openstackMeeting started Wed Feb  6 17:04:38 2013 UTC.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: XenAPI)"17:04
openstackThe meeting name has been set to 'xenapi'17:04
*** bswartz has left #openstack-meeting17:04
bobbaMorning!17:05
johnthetubaguy#topic blueprints17:05
*** openstack changes topic to "blueprints (Meeting topic: XenAPI)"17:05
johnthetubaguyhi all17:05
*** JM1 has left #openstack-meeting17:05
johnthetubaguyso there haven't been any agenda additions on the wiki17:05
johnthetubaguyso has anyone got any pressing issues?17:05
bobbaI probably should have added one17:05
*** rushiagr has left #openstack-meeting17:06
bobbanot a pressing issue - but have got devstack successfully installed on Quantal17:06
*** jgallard has left #openstack-meeting17:06
johnthetubaguycool17:06
johnthetubaguyis there a patch for that yet?17:06
bobbaChanges aren't in devstack yet, but they are in a github repo if anyone else wants to test it17:06
*** smulcahy has left #openstack-meeting17:06
bobbaWill be pushing to gerrit in the next couple of days17:06
johnthetubaguyis there a timeframe / bug raised against devstack?17:06
johnthetubaguycool17:06
johnthetubaguy#info Devstack soon to support Quantal17:07
bobbaNo bug yet - but I'll probably do that as well just to justify the change17:07
johnthetubaguyalways good to advertise17:07
bobbaVery true!17:07
bobbaBut I'm sure it'll be in gerrit this time next week.17:08
johnthetubaguyany more blueprint issues?17:08
*** xyang_ has quit IRC17:08
bobbaNone from me17:09
bobbaUnfortunately I don't think that pvo or any of the other guys have made it to the meeting today17:09
johnthetubaguyOK, clash I guess17:10
bobbaI know that Mate wasn't able to make it due to a clash17:10
johnthetubaguy#topic Docs17:10
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"17:10
johnthetubaguyany one got any plans to help with the docs backlog for XenAPI feature, or anyone got effort to get the docs a quick look17:11
bobbaMaybe17:11
bobbaI'd be interested in having a look but I'm not sure of the most important issues to look at?17:11
johnthetubaguyWell, once we hit feature freeze, it should concentrate the mind a little17:11
bobbaThe timeing for it might even be beyond this week, so maybe better to think about that at the next meeting17:11
johnthetubaguylook at blueprint in folsom, then give a quick pass17:11
johnthetubaguybeyond this week?17:12
bobbaI meant I might not have the time I want to look at some docs until after next Wednesday (thinking that weeks go between meetings!)17:12
*** bvibhu has quit IRC17:13
*** winston-d_ has left #openstack-meeting17:13
johnthetubaguyI see17:14
johnthetubaguygot ya17:14
johnthetubaguy#topic Bugs / QA17:14
*** openstack changes topic to "Bugs / QA (Meeting topic: XenAPI)"17:14
johnthetubaguyI guess nothing here?17:14
bobbaApart from the quantal bug that's been fixed17:15
bobbaThere are a couple of other improvements to devstack to be pushed too17:15
*** cp16net is now known as cp16net|away17:16
*** cp16net|away is now known as cp16net17:17
johnthetubaguyOK17:17
johnthetubaguywould be good to open bugs I guess17:17
johnthetubaguy#topic OpenDiscussion17:17
*** openstack changes topic to "OpenDiscussion (Meeting topic: XenAPI)"17:17
johnthetubaguyonly other thing I was going to raise is blogs and videos to advertise new feaures17:17
johnthetubaguyit might be good to tell people what is happening17:17
bobbaThat's true...17:17
bobbaWe don't do enough of that at the moment17:17
*** koolhead17 has joined #openstack-meeting17:18
johnthetubaguywell its usually only done at the end of each release, for max impact17:18
johnthetubaguylike the storage motion video and blog17:18
bobbaahhh fair enough - well hopefully we can get something out at the end of the release17:18
johnthetubaguybut I am happy for more17:18
johnthetubaguyOK so I guess we are done?17:19
johnthetubaguyLets hope more people can make it next time17:19
johnthetubaguyif you are reading the logs, do email me17:19
bobbaI'm sure we'll get Mate - but let's also make sure that pvo can attend too17:19
johnthetubaguy#info My (JohnGarbutt/johnthetubaguy)'s last day at Citrix tomorrow, starting at Rackspace next week, john@johngarbutt.com will get always get to me17:20
johnthetubaguyother than that I guess we are done?17:21
bobbaI think so!17:21
johnthetubaguy#endmeeting17:21
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:21
openstackMeeting ended Wed Feb  6 17:21:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-02-06-17.04.html17:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-02-06-17.04.txt17:21
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-02-06-17.04.log.html17:21
*** annegentle has quit IRC17:24
*** ayoung_ has joined #openstack-meeting17:27
*** ayoung has quit IRC17:30
*** lloydde has quit IRC17:32
*** diogogmt has joined #openstack-meeting17:32
*** annegentle has joined #openstack-meeting17:34
*** hemnafk is now known as hemna17:34
*** jog0 has joined #openstack-meeting17:39
*** annegentle has quit IRC17:43
*** anniec has joined #openstack-meeting17:43
*** anniec has quit IRC17:44
*** anniec has joined #openstack-meeting17:45
*** annegentle has joined #openstack-meeting17:47
*** annegentle has quit IRC17:50
*** andrewbogott has joined #openstack-meeting17:50
*** lloydde has joined #openstack-meeting17:50
*** annegentle has joined #openstack-meeting17:53
*** nati_ueno has joined #openstack-meeting17:54
*** lloydde has quit IRC17:54
*** thingee is now known as thingee_zzz17:56
*** thingee_zzz is now known as thingee17:57
*** anniec has quit IRC17:59
*** anniec_ has joined #openstack-meeting17:59
*** anniec_ is now known as anniec17:59
*** noslzzp has quit IRC18:00
*** otherwiseguy has quit IRC18:03
*** cp16net is now known as cp16net|away18:03
*** sarob has joined #openstack-meeting18:03
*** sarob has joined #openstack-meeting18:04
*** egallen has quit IRC18:05
*** Mandell has joined #openstack-meeting18:09
*** markmcclain has quit IRC18:09
*** darraghb has quit IRC18:09
*** davidha has joined #openstack-meeting18:09
*** dosaboy has quit IRC18:12
*** diogogmt has quit IRC18:14
*** noslzzp has joined #openstack-meeting18:18
*** dosaboy has joined #openstack-meeting18:19
*** markwash has joined #openstack-meeting18:21
*** mattray has quit IRC18:21
*** mattray has joined #openstack-meeting18:23
*** beagles is now known as beagles|brb18:24
*** dosaboy1 has joined #openstack-meeting18:25
*** dosaboy1 has quit IRC18:25
*** dosaboy1 has joined #openstack-meeting18:25
*** dosaboy1 has quit IRC18:25
*** devananda has quit IRC18:27
*** devananda has joined #openstack-meeting18:27
*** bdpayne has quit IRC18:27
*** bdpayne has joined #openstack-meeting18:28
*** vkmc has joined #openstack-meeting18:29
*** garyk has quit IRC18:29
*** andrewbogott has left #openstack-meeting18:31
*** thingee is now known as thingee_zzz18:34
*** ttrifonov is now known as ttrifonov_zZzz18:35
*** pschaef has quit IRC18:37
*** davidha has quit IRC18:38
*** davidha has joined #openstack-meeting18:38
davidhaHi, is there and agenda sent out?18:39
davidhaand=an18:39
*** dansmith is now known as joebob18:40
*** joebob is now known as dansmith18:40
*** bobba has quit IRC18:41
*** lloydde has joined #openstack-meeting18:42
*** derekh has quit IRC18:42
*** johnthetubaguy has left #openstack-meeting18:45
*** clayg has joined #openstack-meeting18:49
*** mnewby has joined #openstack-meeting18:50
*** Mr_T has left #openstack-meeting18:51
*** cp16net|away is now known as cp16net18:52
*** vipul is now known as vipul|away18:56
*** vipul|away is now known as vipul18:56
*** mattray has quit IRC18:57
*** danwent has quit IRC18:57
*** lloydde has quit IRC19:00
notmynametime for the swift meeting.19:01
*** redbo has joined #openstack-meeting19:01
claygyay!19:01
notmynameyour favorite time of the fortnight19:01
notmyname#startmeeting19:01
openstacknotmyname: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'19:01
notmynamebah19:01
notmyname#startmeeting swift19:01
openstackMeeting started Wed Feb  6 19:01:41 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: swift)"19:01
openstackThe meeting name has been set to 'swift'19:01
notmynameshould be a pretty short meeting, I think19:01
notmynameat least I don't have much on my agenda to talk about19:02
*** danwent has joined #openstack-meeting19:02
notmyname1) is encryption in the scope of swift? 2) docs / copyright 3) any patches need considering19:02
notmynameand at the end, torgomatic has volunteered to answer all your questions about global clusters19:02
notmyname#topic is encryption in the scope of swift?19:03
*** openstack changes topic to "is encryption in the scope of swift? (Meeting topic: swift)"19:03
*** adrian17od has joined #openstack-meeting19:03
notmynameok, there have been some mailing list threads and ideas floating around about adding various flavors of encryption to swift19:03
chmouelI think having tools or client librarie making it maybe easier to encrypt bfore uploading to swift would be more in scope19:04
notmynamethere are 2 use cases that I know of: users don't want anyone to read their data and deployers want to easily recycle drives by simply throwing away a key19:04
*** dfg has joined #openstack-meeting19:04
redbodmcrypt is good for the second one19:04
swifterdarrellWe've had at least one hard requirement from a customer deploying Swift for encryption of data, but only at rest; that was solved with disk-level encryption out-of-band to Swift19:05
davidhaif adding encryption in the server side, we need key management19:05
notmynamedoes anyone want to argue in favor of either of these being in scope for swift itself (ie should there be code in swift's codebase that handles this)?19:05
torgomaticyep, dm-crypt or luks or something else underneath Swift19:05
chmouelyeah that or luks19:05
*** metral has joined #openstack-meeting19:05
notmynameso does that mean we all agree that encryption should be out-of-band to swift itself?19:06
swifterdarrellI'm perfectly happy with keeping encryption (and the associated problems and complexity which come with key management) outside the scope of Swift19:06
chmouel+1 to out19:06
swifterdarrellPush that stuff out to deployments19:06
swifterdarrell(IOW +1 to out)19:06
torgomatic+1 to encryption being outside the scope of Swift19:06
redbobuy a drive shredder19:06
notmynameredbo: or a ball-peen hammer ;-)19:07
davidhaHow would you shred only files form one customer?19:07
*** mattray has joined #openstack-meeting19:07
*** markmcclain has joined #openstack-meeting19:07
notmynamedavidha: that data is spread out over all drives in the entire cluster19:07
redbowhy would I need to shred one customer's files?19:07
davidhaRight, this is a real use case for server side encryption.19:08
notmyname"this"? the user use case or the deployer use case?19:08
swifterdarrellLet's not pretend that encrypting data at rest and possibly in-flight as well are not valid requirements for an object storage system.  The question is whether that use-case should be satisfied by code in Swift or not.19:08
notmynameswifterdarrell: exactly19:08
davidhaI think Swift should enable it - we at least need to see that one can add it to Swift19:09
notmynamedavidha: what is "it"?19:09
davidhaIt being server side encryption19:10
notmynamedavidha: full drive encryption or encryption of the object data?19:10
*** beagles|brb is now known as beagles19:10
davidhaIt is possible it can be done as a middleware ... :)19:10
davidhaencr of the object data by  a per user key19:10
*** Dieterbe has joined #openstack-meeting19:11
notmynamedavidha: so that the deployer then has access to both the encrypted data and the key? what use case does that solve?19:11
davidhanotmyname: Shreding of data whne the user leaves19:11
davidhaI need to go deaper on that19:11
*** mrodden has quit IRC19:12
davidhaI will ask the team here, lets leave that to next meeting19:12
redbowho's that serving, the user or the provider?19:12
chmouelthat's going bad for performances for both19:12
*** dolphm has quit IRC19:13
notmynameok. for now it looks like we are agreed that encryption should stay outside of swift, unless there is another use case that cannot be efficiently implemented in middleware19:13
davidhaAgreed19:13
notmyname#agreed that encryption should stay outside of swift19:14
notmyname#topic docs and copyright19:14
*** openstack changes topic to "docs and copyright (Meeting topic: swift)"19:14
notmynamejust as an FYI, as I've been looking at some of the docs lately (like the SAIO and multinode install instructions), it seems that they are getting somewhat dated19:15
notmynameif you are looking for something to do in your free time (hah!), re-reading the docs is a good place to start19:15
notmynamethis applies as much to me as anyone19:15
notmynamejust wanted to bring it up19:15
chmouel(or get the newcommers in your company to do it while learning swift 8-))19:16
notmynameheh19:16
notmynamechmouel: aren't you the newcomer in your company?19:16
notmyname:-)19:16
chmouelhaha19:16
*** novas0x2a|laptop has quit IRC19:16
notmynameannegentle proposed a patch that mentions copyright (https://review.openstack.org/#/c/18889/). looks like there may be a little more clarification needed (as per the comments)19:16
notmynamebut review the http://wiki.openstack.org/Documentation/Copyright page19:17
notmynamealso, I've heard that we should stop assigning copyright to openstack (btw, openstack llc doesn't exist any more) and should be keeping it for whatever company you work for19:17
swifterdarrell(I hate to be annoying, but if we got legal guidance, we might as well follow all of it.)19:17
notmyname#topic patches?19:18
*** openstack changes topic to "patches? (Meeting topic: swift)"19:18
notmynameare there any patches that we need to discuss in here that can't be handled in gerrit comments?19:18
notmynamehttps://review.openstack.org/#/q/status:open+swift,n,z19:19
davidhaI would like to see account qouta as an enhancement to the container one - seem to be trivial enhancement19:19
davidhaI can work on this unless this is already being worked on19:19
chmoueldavidha: yeah i can do that since we are going to use it19:19
*** ayoung has joined #openstack-meeting19:20
notmynamecool19:20
notmynameredbo: any big reason not to extend your container quotas to handle entire accounts?19:20
*** jd__ has left #openstack-meeting19:21
swifterdarrellpatches welcomed, perhaps?  There's at least one account quota middleware floating around outside Swift (don't have link handy)19:21
chmouel#link https://github.com/cschwede/swquota19:21
davidhaI think it should be a single middleware doing both19:22
swifterdarrellchmouel: thanks!19:22
chmouel#link https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota19:22
notmynamechmouel: davidha: I look forward to seeing your patches :-)19:22
redboNot that I know of.  It just wasn't a use case we had.19:22
chmoueland last one19:22
chmouel#link https://github.com/chmouel/swift-quota19:23
chmouel(it actually works need to update the README)19:23
swifterdarrellI'm happy having two middlewares with different names which differentiate their different behavior (most importantly that container quotas are mostly voluntary and account quotas would presumably be most useful to resellers enforcing restrictions on customers);  but that assesment of the use-cases could be biased/inaccurate.19:23
*** ayoung_ has quit IRC19:24
davidhaWhy would that make more sense?  A single quota middleware will not be less efficient if only container quota is used19:24
chmouelI think having them merged would make more sense19:24
swifterdarrellIOW, I think if two things both implement "quotas" but they're substantially different, they needn't be implemented in one piece of code/middleware19:24
chmouelit may be confusing for deployers and it's not much of biggie to have the two19:24
*** annegentle has quit IRC19:24
davidhaas much as I enjoy long pipelines..... this is becoming too long :)19:25
notmynamechmouel: really? _this_ is what will be confusing to deployers about swift? ;-)19:25
redbowe could call them user_quotas and provider_quotas or something19:25
chmouelnotmyname: good point :)19:25
redboor deployer_quotas19:25
chmouelredbo: +119:25
notmynameredbo: +119:25
*** otherwiseguy has joined #openstack-meeting19:26
chmoueland a nice quota.txt explaining the difference between the two :)19:26
chmouel.rst19:26
davidhaI would guess userrs would expect both to work together and be aligned, and the performance of both will be affected19:26
davidhaso -1 for me19:26
notmynamelet's carry this on in the gerrit comments on the patch that comes in19:27
notmyname#topic other19:27
*** openstack changes topic to "other (Meeting topic: swift)"19:27
notmynameanything else need to be brought up today?19:27
davidhaIs there any work on one of the following topics:19:28
davidhaMetadata, search19:28
davidha?19:28
notmynameI wanted to point out that I got a lot of positive comments last week at linux conf australia. people like the stuff you all are working on. good job :-)19:28
torgomaticdavidha: you mean metadata beyond Swift's existing support for account/container/object metadata?19:29
notmynamedavidha: softlayer has a metadata search feature using an external system for their swift cluster19:29
chmoueli think the guys of keystone v3 want to talk more about swift19:29
redboumm I have a branch somewhere where I just stuck a fts3 table in the container db and indexed metadata19:29
chmouelswift integration i mean with ACL19:29
davidhatorgomatic: yep19:29
davidhachmouel: right, I know of a change needed to support v3 also19:30
notmynamechmouel: they can define whatever they want. the ACL tokens are opaque to swift, and the only thing that needs possibly updating is the keystoneauth middleware in swift. if they decide to change things, they'll have to accound for a migration path, of course19:30
zykes-is v3 supported ? : p19:30
notmynamezykes-: does v3 exist? ;-)19:30
davidhaWe may need to add domain id as a MD for containers19:30
chmouelnotmyname: yep that's correct, it just has to be to authorize to whatever acl they are giving to us by auth_token19:31
*** sdake has quit IRC19:31
davidhaSince there is not another hirarchy in v3, we would need to add some support for it to work19:31
*** sdake has joined #openstack-meeting19:31
chmouelI don't think I would like much if they are taking in account migration (we have a large v2 swift/keystone cluster here)19:31
chmouelif they are not19:32
zykes-doesn't it in G notmyname ? :)19:32
notmynamezykes-: I'm just half joking. I thought they were still defining it19:32
*** annegentle has joined #openstack-meeting19:32
chmouelfrom the discussion on the ml they seem so19:32
chmouel(i.e: making email attr compulsory)19:33
notmynamechmouel: but that shouldn't change anything in swift, from what I could tell19:33
chmouelif they decide to give tenant_email instead of tenant_id19:33
chmouelthat would get difficult for migration19:34
*** dolphm has joined #openstack-meeting19:34
torgomaticso accounts would look like /v1.0/AUTH_#{tenant_email} ?19:34
*** mrodden has joined #openstack-meeting19:34
*** colinmcnamara has quit IRC19:34
notmynamea user gives X to keystone in order to get back a token and and endpoint. swift's middleware then give the request and the token to keystone for authorization. I don't see what changes19:34
*** lloydde has joined #openstack-meeting19:35
zykes-notmyname: v3 apparantly has a goal to be fully implemented in G19:35
torgomaticnotmyname: as long as the endpoint is immutable, that's true19:35
redbotorgomatic: I think he just means for acls19:35
chmoueltorgomatic: that's what i am worried about will clarify with those guys19:35
zykes-fyi :)19:35
notmynamethey can redefine how they are passing out the endpoints all they want, but you can't do that for existing data19:35
torgomaticredbo: I hope you're right19:36
*** annegentle has quit IRC19:36
*** colinmcnamara has joined #openstack-meeting19:37
notmynamechmouel: you've got an existing keystone v2 cluster. when you get a clarifying answer, can you let me know what you find out? (I thought this had been settled on the ML)19:37
chmouelnotmyname: yep will do19:38
davidhaAs far as I understand it, there is an additional hirarchy - this mean that you may have the same "account name"  in two different domains -  we would therfore need to store another attribute as a system MD being the domain id to which the account belong to19:38
notmynamethanks19:38
*** lloydde has quit IRC19:38
redbowe have accounts, keystone can delegate access to those however it wants19:38
davidharedbo, the previous mapping betweeing users and account no longer stanbd19:39
davidhaI expect to see a blueprint on that soon that will elaboarte on how it can be done, than we can discuss issues it may bring19:41
redbothere's been a huge mailing list discussion19:41
notmynamelet's see what chmouel comes back with19:41
notmynameanything else that needs to be brought up today?19:41
torgomaticif anyone has spare review time, the multi-range GET patch for segmented objects could use some eyeballs19:42
torgomaticit's the oldest in the review queue, and it's been resurrected at least once19:42
notmynameok19:43
*** annegentle has joined #openstack-meeting19:43
notmynamenext meeting is in two weeks19:43
notmyname#endmeeting19:43
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:43
openstackMeeting ended Wed Feb  6 19:43:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-02-06-19.01.html19:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-02-06-19.01.txt19:43
*** dfg has left #openstack-meeting19:43
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-02-06-19.01.log.html19:43
*** redbo has left #openstack-meeting19:43
*** fnaval has quit IRC19:44
*** adrian17od has quit IRC19:44
*** dwcramer has quit IRC19:45
*** anniec has quit IRC19:45
*** colinmcnamara has quit IRC19:46
*** jbrogan has quit IRC19:50
*** dosaboy has quit IRC19:50
*** shardy has joined #openstack-meeting19:56
*** colinmcnamara has joined #openstack-meeting19:56
*** clayg has left #openstack-meeting19:57
*** SpamapS has joined #openstack-meeting19:57
*** fnaval has joined #openstack-meeting19:58
sdake#startmeeting heat19:59
openstackMeeting started Wed Feb  6 19:59:41 2013 UTC.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.19:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:59
*** openstack changes topic to " (Meeting topic: heat)"19:59
openstackThe meeting name has been set to 'heat'19:59
sdake#topic rollcall19:59
*** openstack changes topic to "rollcall (Meeting topic: heat)"19:59
*** zaneb has joined #openstack-meeting20:00
sdakesdake here20:00
zanebo/20:00
shardyshardy here20:00
sdakehidey zaneb20:00
SpamapSo/20:00
stevebaker\O20:00
jpeelerjpeeler here20:00
sdake\<>20:00
sdakeascii art ftw20:01
asalkeldhere20:01
sdakeno asalkeld?20:01
sdakehi there20:01
sdakeok looks like we got enough to get started20:01
Slowerhere20:01
sdake#topic action review from last meeting20:01
*** openstack changes topic to "action review from last meeting (Meeting topic: heat)"20:01
*** colinmcnamara has quit IRC20:01
sdakeACTION: asalkeld, shardy, stevebaker, jpeeler to set implementation field in BPs20:02
sdakethat looks done20:02
sdakeACTION: sdake to set all VPC blueprints to high20:02
sdakethat looks done20:02
stevebakersdake: do you run the ttx.py script?20:02
sdakeACTION: heat devs to sort out if updatestack can update rather then delete in coming week20:02
sdakei dont run that20:02
sdakehave a link?20:03
*** mattray has left #openstack-meeting20:03
shardysdake: that's done for instance and autoscaling now20:03
shardywhich was the objective for G IIRC20:03
sdakeok so done then?20:03
shardyyup20:03
stevebakersdake: https://github.com/ttx/bp-issues <- his sanity check on LP fields20:03
*** maurosr has quit IRC20:04
sdake#info all actions from 1-23-2013 meeting completed20:04
sdakefor those  that weren't here last week, we cancelled the meeting since most were travelling20:04
*** vkmc_ has joined #openstack-meeting20:04
sdakeI'd like to go through the blueprints and bugs and make sure we are set for g320:04
sdake#topic blueprint review20:04
*** openstack changes topic to "blueprint review (Meeting topic: heat)"20:04
*** vkmc has quit IRC20:04
*** vkmc_ is now known as vkmc20:04
*** vkmc_ has joined #openstack-meeting20:05
sdake#link https://launchpad.net/heat/+milestone/grizzly-320:05
sdakestevebaker still blocked on the vpc work?20:05
stevebakerI should be able to start soon, just waiting for some network ports to arrive in the mail20:06
*** vkmc has quit IRC20:06
sdakehttps://blueprints.launchpad.net/heat/+spec/raw-template-db20:06
stevebakerthat might have to be bumped20:06
*** vkmc_ has quit IRC20:06
*** mattray1 has joined #openstack-meeting20:06
sdakemight or should, lets make a decision here ;)20:06
asalkelddoesn't look needed20:07
stevebakerOK, bump it. Any spare cycles will be spent on the vpc blueprints20:07
shardylooks low priority to me20:07
zaneb+120:07
sdake#info bump https://blueprints.launchpad.net/heat/+spec/raw-template-db to H cycle20:07
zanebsdake: will we be doing a db migrations reset for G?20:07
sdakei think we should20:08
shardy+120:08
sdakebut should probably have a vote on it20:08
zanebok, so that should probably be done at the same time20:08
zaneb(or before)20:08
asalkeldwhat about current users?20:08
asalkeldthey have to reinstall?20:08
asalkeldmaybe talk to ppetit20:08
zanebno, just restart the numbering where it is20:09
sdake#action sdake to bring up thread on openstack-dev about dumping the db migrations20:09
*** vkmc has joined #openstack-meeting20:09
*** lloydde has joined #openstack-meeting20:09
*** dprince has quit IRC20:09
zanebasalkeld: if nova can get away with it, we certainly can20:09
*** annegentle has quit IRC20:10
sdake#link https://blueprints.launchpad.net/heat/+spec/resource-properties-schema20:10
sdakelets have discussion about it on ml and see what pops up20:10
*** colinmcnamara has joined #openstack-meeting20:10
sdakezaneb your assigned to that last link20:10
sdakefeb 21 is deadline for blueprints20:11
zanebbump20:11
zanebthat's low priority20:11
stevebakerits a nice-too-have, but low priority20:11
sdake#info bump https://blueprints.launchpad.net/heat/+spec/resource-properties-schema to H cycle20:11
stevebakerat least until horizon ui picks up20:11
zanebstevebaker: +120:11
shardy+120:12
asalkeldyea20:12
sdake#link https://blueprints.launchpad.net/heat/+spec/aws-cloudformation-init20:12
sdakejpeeler?20:13
jpeelerthanks to pfreund, i think the only thing left is implementing configsets20:13
jpeelerso i'm working on that20:13
sdakeok, so looks goot for feb 21?20:13
sdakegoot/good ;)20:13
jpeeleryep, question about cfntools though20:13
zanebgut20:13
jpeelerare we trying to maintain the copy in heat-jeos with the separate repo or what?20:14
sdake#info https://blueprints.launchpad.net/heat/+spec/aws-cloudformation-init on target for g3 deadline20:14
jpeeler(i can wait on that question)20:14
asalkeldjust seperate cfn20:14
*** vipul is now known as vipul|away20:14
stevebakerjpeeler: I plan to rip cfntools out of heat-jeos and replace with a pip install20:14
*** vipul|away is now known as vipul20:15
*** mattray1 is now known as mattray20:15
*** mattray has joined #openstack-meeting20:15
*** diogogmt has joined #openstack-meeting20:15
stevebakerin the meantime, any changes will be manually synced between heat-jeos and heat-cfntools20:15
sdakewe will try to get through as many bugs as possible - but may not be able to tackle them all in this meeting20:15
sdake#topic bug review20:15
*** openstack changes topic to "bug review (Meeting topic: heat)"20:15
sdake#link https://bugs.launchpad.net/bugs/107290620:15
uvirtbotLaunchpad bug 1072906 in heat "Handle XML as well as JSON in ReST API" [Medium,Confirmed]20:15
zanebthat's more of a bluprint20:16
sdakeok, so make blueprint and remove as bug?20:16
asalkeldif we used wsme it comes for free20:16
asalkeld(what is in ceilometer)20:16
shardyzaneb: have you looked at the controller code, I think it could be quite simple?20:16
zanebsdague: probably20:16
zanebsdake: probably20:17
*** novas0x2a|laptop has joined #openstack-meeting20:17
sdake#action zaneb to move 1072906 to blueprint20:17
zanebI think selecting between the two is not that hard20:17
shardywe already have JSON and XML serializer/deserializer implementations IIRC, so we just have to fix the content type detection20:17
sdakeso as a blueprint, that going to make 21?20:17
zanebactually getting the output in an acceptable XML format... possibly hard20:17
zanebsdake: no20:17
shardyassuming same wsgi middleware as the CFN api that is20:17
*** cdub has joined #openstack-meeting20:18
sdakeok - file as a blueprint and we can take up in h cycle and close the bug please ;)20:18
zanebok20:18
sdake#link https://bugs.launchpad.net/bugs/107290520:18
uvirtbotLaunchpad bug 1072905 in heat "make template functions "Fn::" pluggable." [Medium,In progress]20:18
stevebakeranother blueprint ;)20:18
asalkeldtho not a big job20:19
* stevebaker notes that its Mark Shuttleworth's fault that blueprints are a separate thing in launchpad20:19
shardyit is a confusing distinction20:19
sdake#action zaneb refile 1072905 as blueprint20:19
sdakeso as a blueprint that going to make 21?20:19
*** sandywalsh has quit IRC20:20
asalkeldlet's wait and see?20:20
sdakewould like blueprints to be stabilized so we know what work we have on our plates20:20
zanebFn:: pluggableness is actually a pretty big job20:21
sdakeif we aren't going to finish something for g3, no sense spending effort on it now20:21
*** colinmcnamara has quit IRC20:21
sdakeneed to focus on g3 specific tasks20:21
asalkeldwe could just prioritize?20:21
zanebas in, Havana cycle job20:21
sdakeok - well still please file blueprint and close bug ;)20:21
asalkeldand do what we can20:21
sdake#link https://bugs.launchpad.net/bugs/107291720:21
uvirtbotLaunchpad bug 1072917 in heat "heat cli: Template Body maximum length problem." [Medium,Triaged]20:21
shardyI need to investigate this, it's broken with qpid but works with rabbit20:21
shardyprobably something simple, but not sure yet20:22
stevebakerhmm, so not much chance of replicating it in a unit test20:22
shardyplanning to look into it next week20:22
sdake#link https://bugs.launchpad.net/bugs/107294020:22
uvirtbotLaunchpad bug 1072940 in heat "backtrace on console 3-5 minutes after HA test completes" [Medium,In progress]20:22
shardyI'm pretty certain this is fixed now20:22
shardyThe backtrace was because the create greenthread didn't get deleted, which is now does20:23
shardyI just need to re-run the integration test to prove20:23
sdakeok - so state of bug is wrong?20:23
shardyI was just going to re-test then close it as invalid20:23
sdake#action shardy to rerun ha test for 1072940 and fix state20:23
sdakeit was a valid bug th o ;)20:23
sdakeso close as fix commited i think20:23
shardyYeah, it's not notabug anymore20:24
shardywas valid previously :)20:24
shardyok will do20:24
sdake#link https://bugs.launchpad.net/bugs/107294820:24
uvirtbotLaunchpad bug 1072948 in heat "some resource create and delete operations could block in failure scenarios" [Medium,In progress]20:24
sdakeso this is fixed, but shardy had some problems with the patch20:24
sdakewhat is your thinking here shardy20:24
*** anniec has joined #openstack-meeting20:25
shardyI think if nova is broken, heat is broken, introducing some hard-coded timeout logic is just wrong IMO20:25
asalkeld+120:25
zanebI think there are enough safeguards on create already20:25
asalkelddelete bug20:25
zanebsome on delete would be good though20:25
asalkeldwe have a stack create timeout20:25
zanebbecause state may go from ERROR -> ERROR and we have no way of detecting the transition20:26
asalkelddon't we have a timeout on delete?20:26
zanebasalkeld: should use the same one as for create20:26
zanebi.e. timeout for whole stack20:26
asalkeldyip20:26
zanebbut has same value as create timeout20:26
sdakehowever if nova breaks, there is no way for the heat user to identify nova is broken, and they may then think heat is broken20:27
zanebso, pretty long wait20:27
zanebsdake: I think you need timeout on nova only if instance starts in ERROR state20:27
asalkeldsdake, you can adjust the timeout20:27
sdakewedging heat entirely because nova misbehaves at some point seems wrong20:27
shardybut if nova (or any other core service we rely on) is broken, everything is broken20:28
asalkeldsdake, it won't wedge heat20:28
*** Hg has joined #openstack-meeting20:28
shardyIs this a real problem, ie do we have any sort of reproducer?20:28
asalkeldit will timeout and fail20:28
sdakei have seen it happen but no reproducer20:28
sdakebut didn't wait for a timeout from heat proper20:28
sdakeok well we can close bug then if everyone feels current functionality is ok20:29
shardyThe real problem is the while True loops in the instance resource20:29
asalkeldya, the timeout is big20:29
shardywe should just make that a specific number of retries20:29
sdake#action sdake 1072948 should be closed20:29
asalkeldwe need parallel resource startup!20:29
sdake#action shardy to file bug with what he thinks are necessary steps to deal with problems in 107294820:29
sdake;)20:30
*** vipul is now known as vipul|away20:30
zanebshardy: +120:30
shardysdake: Ok, will do20:30
sdakeok #link https://bugs.launchpad.net/bugs/107295220:30
uvirtbotLaunchpad bug 1072952 in heat "Implement Rollback feature of AWS API" [Medium,Triaged]20:30
sdakeblueprint?20:30
shardyI'm planning to do that next week20:30
shardycan convert to blueprint if you prefer20:31
sdakelooks like one to me20:31
shardyok, will do20:31
sdake#action shardy to convert 1072952 to blueprint20:31
*** Gordonz has quit IRC20:31
sdake#link https://bugs.launchpad.net/bugs/107295520:31
uvirtbotLaunchpad bug 1072955 in heat "Implement Fn::Base64" [Low,Triaged]20:31
sdakeI dont think this is needed20:31
stevebakerblueprint?20:31
asalkeldnoop20:32
zanebyeah, extremely low priority20:32
sdakei think it is a noop20:32
zanebcurrently, yeah20:32
sdakeI did implemenet this once, and it broke heat20:32
sdakebecause it passed base64 to cloudinit which didn't expect it20:32
zanebcould set the mime-type to cloudinit to base6420:32
zaneber, mime-encoding20:33
sdake#action sdake to close 107295520:33
sdake#link https://bugs.launchpad.net/bugs/108753020:33
uvirtbotLaunchpad bug 1087530 in heat "sendfile possibly problematic with eventlet" [Medium,In progress]20:33
*** alrs has quit IRC20:33
zanebsdake: don't close it, people might want to use Base64 elsewhere in their template20:33
stevebakerhttps://review.openstack.org/#/c/21184/20:33
*** sandywalsh has joined #openstack-meeting20:33
stevebakerI realise now it is client side code only, but no harm in removing it20:34
sdakezaneb do you plan to fix this before 21st then?20:34
sdakeor bump to h20:34
sdake#undo20:34
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x195de10>20:34
sdake#undo20:34
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x1d820d0>20:34
zanebsdake: no, just leave it open and bump imo20:34
*** alrs has joined #openstack-meeting20:34
sdake#action zaneb to turn 1072955 into blueprint and bump to h20:34
sdake#link https://bugs.launchpad.net/bugs/108753020:35
uvirtbotLaunchpad bug 1087530 in heat "sendfile possibly problematic with eventlet" [Medium,In progress]20:35
sdakeok that review looks good stevebaker, i'll approve after meeting20:35
sdakeok the rest are unassigned20:36
sdakelets go through those and see if any interest folks ;)20:36
stevebakerhttps://bugs.launchpad.net/heat/+bug/1096013 is what I'll be working on next20:36
sdakealso, zane is a bit busy with another task unrelated to heat for 2-4 weeks so wont be able to help with our final g push20:36
uvirtbotLaunchpad bug 1096013 in heat "Instance resource doesn't allow IP assignment to VPC/quantum network" [High,Triaged]20:36
sdake#link https://bugs.launchpad.net/bugs/107293520:37
uvirtbotLaunchpad bug 1072935 in heat "interrupting a nosetest results in backtrace on future creations of stacks" [Low,Triaged]20:37
sdakedeveloper focused bug, can probably bump to h20:37
zanebsdake: can we add some more milestones? current buckets are only "grizzly-3" or "everything else"20:37
asalkeldh20:38
sdakeya i'll see if i can yet20:38
sdake#action sdake to bump 1072935 to h20:38
sdake#link https://bugs.launchpad.net/bugs/107293720:38
uvirtbotLaunchpad bug 1072937 in heat "odd error from heat list after a delete" [Low,Triaged]20:38
sdakethis is super hard to reproduce20:39
sdakeand may not be present any longer20:39
stevebakerthat should be heat-cfn list, not heat list20:39
sdakeold bug20:39
sdakefrom v4 days i think ;)20:39
zanebshould still be around, hard to reproduce though20:40
asalkeldjust delete it and if it happens again re-create?20:40
zanebfix is there in the comments20:40
sdakeprefer to keep a record20:40
stevebakeri say delete20:40
sdakebut doens't mean we have to fix for h20:40
asalkeldwell bump it then20:41
zanebwhy delete when we have collected all that info about how to fix it in the bug20:41
stevebakerI mean close, it is still searchable20:41
zanebit's still a bug too, so why close20:42
asalkeldyar, you can't actually delete20:42
sdake#link https://bugs.launchpad.net/bugs/107295820:42
uvirtbotLaunchpad bug 1072958 in heat "Create a getting started guide for scaling out" [Medium,Triaged]20:42
sdakethis seems like h material20:42
*** colinmcnamara has joined #openstack-meeting20:42
sdake#link https://bugs.launchpad.net/bugs/107295720:43
uvirtbotLaunchpad bug 1072957 in heat "Add role to users, similar to nova's user role assignment" [Medium,Triaged]20:43
sdake#action shardy to speak with keystone folks about this20:43
shardyI think this is an internal user->role mapping, not a keystone role?20:44
sdakewasn't this the bug we were speaking about earlier in the week shardy?20:44
sdake#undo20:44
shardynot high priority IMO, no users have asked for this20:44
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x1dd10d0>20:44
shardyno, the one we discussed is the create stack as non-admin when it creates User/AccessKey resources20:44
sdakeright20:44
sdake#link https://bugs.launchpad.net/bugs/109600120:45
uvirtbotLaunchpad bug 1096001 in heat "Parser Fn::GetAZs intrinsic function returns hard-coded value" [Medium,Triaged]20:45
shardyI contacted ayoung about it today, he thinks trusts should help us address it for h20:45
sdakenice20:45
shardyOur AZ handling is all a bit broken I think (we don't pass AZ's to nova), so I say bump to H and have an multi AZ test/fix then20:46
sdake#link https://bugs.launchpad.net/bugs/109601720:47
uvirtbotLaunchpad bug 1096017 in heat "AutoScalingGroup missing VPCZoneIdentifier property" [Medium,Triaged]20:47
shardyUnless the VPC features are landing for G, we can bump this20:48
sdakei am hopeful the vpc features land for g20:48
sdakeok well thats all the high/med bugs20:48
sdakethere are still a few unassigned - feel free to take those up if your bored ;)20:48
sdake#topic integrated status20:49
*** openstack changes topic to "integrated status (Meeting topic: heat)"20:49
sdakeSo basically we need to present our case as to why we are integrated ready20:49
sdake(which is like core)20:49
asalkeldserious?20:49
sdakei'd suggest everyone send me a couple paragraphs and i'll sort it out into one email20:50
sdakeya serious20:50
stevebakerok20:50
asalkeldI thought it was a review not marketing exercise20:50
asalkeldweird20:50
sdakewell i could be wrong on what i read in the meeting but thats what it looked like to me20:50
shardyI assumed we'd be incubated for ~6months then reviewed20:50
stevebakerso there is "core" and "integrated" now?20:51
sdakeya, i think they passed new rules just yesterday on this point20:51
zanebstevebaker: core is a subset of integrated20:51
stevebakerseems sensible, depending on the specifics of what each means20:52
sdake#topic open items20:52
*** openstack changes topic to "open items (Meeting topic: heat)"20:52
*** thingee_zzz is now known as thingee20:52
zanebstevebaker: the only difference is trademarks, effectively20:52
*** thingee has left #openstack-meeting20:52
stevebakercan we talk heat-horizon?20:52
sdakeok guys 3 weeks left20:52
* stevebaker invokes mordred20:52
sdakeplease wrap up blueprints and bugs20:52
sdakeya what do you want to discuss about heat-horizon20:53
stevebakerMonty mentioned that HP need a working horizon UI to heat, and have a developer ready to pick up some heat-horizon work20:53
sdakecool20:54
stevebakerI'm thinking we should at least get heat-horizon into gerrit and launchpad20:54
sdakeas a plugin you mean?20:54
asalkeldsure, stackforge?20:54
stevebakerit could stay in github/heat for now?20:55
asalkeldsure20:55
sdakegithub/heat is easy to work with20:55
sdakethere is alot of overhead to gerrit integration20:56
stevebakersdake: as a horizon plugin. Once we're "integrated" we could propose that it goes into horizon20:56
sdakebut we can do it20:56
sdakeya just thinking about short circuiting the need for a plugin :)20:56
sdakeie propose directly in a few weeks20:56
sdakevs setup a bunch of infrastructure for 3-4 weeks of time20:56
asalkeld+120:56
*** anniec has quit IRC20:57
stevebakertrue. I guess there is a risk that horizon devs will want it to stay as a plugin20:57
asalkeldtho I think you only get integrated after 8 months?20:57
sdakebut the core of the issue is the hp dev needs a way to develop on the codebase20:57
sdakeand that is easy to solve20:57
sdakemay make more sense as a plugin20:57
sdakethat is for horizon devs to decide imo ;)20:57
stevebakerhttps://github.com/heat-api/heat-horizon fyi20:58
sdakeyup20:58
asalkeld1 min...20:58
stevebakerthats all from me20:58
sdakeok thanks guys20:59
sdake#endmeeting20:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:59
openstackMeeting ended Wed Feb  6 20:59:26 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-02-06-19.59.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-02-06-19.59.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-02-06-19.59.log.html20:59
*** mrunge has quit IRC20:59
*** shardy has left #openstack-meeting21:00
*** jsavak has joined #openstack-meeting21:00
*** vipul|away is now known as vipul21:00
*** dwcramer has joined #openstack-meeting21:01
*** otherwiseguy has quit IRC21:03
*** joesavak has quit IRC21:04
*** adjohn has joined #openstack-meeting21:05
*** colinmcnamara has quit IRC21:05
*** diogogmt has quit IRC21:06
*** adjohn_ has joined #openstack-meeting21:07
*** eharney has quit IRC21:09
*** gyee has joined #openstack-meeting21:09
*** diogogmt has joined #openstack-meeting21:09
*** adjohn has quit IRC21:09
*** eharney has joined #openstack-meeting21:10
*** eharney has joined #openstack-meeting21:10
*** anniec has joined #openstack-meeting21:11
*** bdpayne has quit IRC21:12
*** sacharya has joined #openstack-meeting21:18
*** novas0x2a|laptop has quit IRC21:22
*** novas0x2a|laptop has joined #openstack-meeting21:22
*** zbitter has joined #openstack-meeting21:26
*** zaneb has quit IRC21:30
*** colinmcnamara has joined #openstack-meeting21:32
*** Gordonz has joined #openstack-meeting21:34
*** Gordonz has quit IRC21:35
*** sarob has quit IRC21:36
*** Gordonz has joined #openstack-meeting21:36
*** tongli has quit IRC21:39
*** jsavak has quit IRC21:40
*** colinmcnamara has quit IRC21:44
*** colinmcnamara has joined #openstack-meeting21:46
*** rafaduran has left #openstack-meeting21:48
*** otherwiseguy has joined #openstack-meeting21:49
*** koolhead17 has quit IRC21:50
*** eharney has quit IRC21:51
*** grog500 has joined #openstack-meeting21:55
*** eharney has joined #openstack-meeting21:56
*** maurosr has joined #openstack-meeting21:56
*** markvoelker has quit IRC21:57
*** annegentle has joined #openstack-meeting22:03
*** Linuturk has quit IRC22:05
*** martine_ has quit IRC22:06
*** ewindisch has quit IRC22:14
*** annegentle has quit IRC22:20
*** otherwiseguy has quit IRC22:25
*** ryanpetrello has quit IRC22:26
*** dhellmann is now known as dhellmann-afk22:27
*** otherwiseguy has joined #openstack-meeting22:28
*** cp16net is now known as cp16net|away22:30
*** cp16net|away is now known as cp16net22:31
*** anniec has quit IRC22:31
*** anniec has joined #openstack-meeting22:31
*** terryw has joined #openstack-meeting22:35
*** john5223 has quit IRC22:35
*** ewindisch has joined #openstack-meeting22:36
*** adjohn_ has quit IRC22:37
*** otherwiseguy has quit IRC22:38
*** dolphm_ has joined #openstack-meeting22:40
*** flaper87 has quit IRC22:40
*** dolphm_ has quit IRC22:41
*** noslzzp has quit IRC22:42
*** dolphm has quit IRC22:43
*** sandywalsh has quit IRC22:44
*** maoy has quit IRC22:45
*** diogogmt has quit IRC22:47
*** ewindisch has quit IRC22:47
*** terryw is now known as otherwiseguy22:47
*** vipul is now known as vipul|away22:48
*** mtreinish has quit IRC22:49
*** jrodom has joined #openstack-meeting22:55
*** colinmcnamara has quit IRC22:56
*** sandywalsh has joined #openstack-meeting22:59
*** otherwiseguy is now known as POST-REVIEW23:02
*** POST-REVIEW is now known as otherwiseguy23:03
*** danwent has quit IRC23:03
*** sarob has joined #openstack-meeting23:03
*** sacharya has quit IRC23:03
*** sarob has quit IRC23:05
*** dwcramer has quit IRC23:05
*** sarob has joined #openstack-meeting23:05
*** markmcclain has quit IRC23:07
*** markmcclain has joined #openstack-meeting23:07
*** danwent has joined #openstack-meeting23:09
*** cdub has quit IRC23:10
*** stevebaker has quit IRC23:11
mordredsdake: crap. I was away23:15
mordredheat-horizon?23:16
mordredwhich is to say ... yes, I thnk we should get it into stackforge23:16
mordredand I thnk that we should put it in as stackforge/thermal23:16
* mordred will send email23:16
*** topol has quit IRC23:18
*** colinmcnamara has joined #openstack-meeting23:18
*** stevebaker has joined #openstack-meeting23:19
*** bencherian has joined #openstack-meeting23:20
*** markmcclain has quit IRC23:22
*** vipul|away is now known as vipul23:25
*** lloydde has quit IRC23:28
*** Mandell has quit IRC23:28
*** novas0x2a|laptop has quit IRC23:28
*** lloydde has joined #openstack-meeting23:28
*** Mandell has joined #openstack-meeting23:28
*** novas0x2a|laptop has joined #openstack-meeting23:29
*** lloydde has quit IRC23:32
*** annegentle has joined #openstack-meeting23:36
*** fnaval has quit IRC23:38
*** iben has joined #openstack-meeting23:40
*** annegentle has quit IRC23:45
*** stevebaker has quit IRC23:48
*** adjohn has joined #openstack-meeting23:48
*** mattray has quit IRC23:48
*** eharney has quit IRC23:51
*** adjohn has quit IRC23:52
*** diogogmt has joined #openstack-meeting23:52
*** ewindisch has joined #openstack-meeting23:54
*** diogogmt has quit IRC23:55
*** diogogmt has joined #openstack-meeting23:55

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