Wednesday, 2013-03-06

*** joshuamckenty has quit IRC00:02
*** jmckenty has joined #openstack-meeting00:02
*** jmckenty is now known as joshuamckenty00:02
*** joshuamckenty has quit IRC00:02
*** fnaval has joined #openstack-meeting00:02
*** dscannell has quit IRC00:03
*** davidha has quit IRC00:05
*** davidha has joined #openstack-meeting00:06
*** topol has joined #openstack-meeting00:08
*** sacharya1 has quit IRC00:20
*** sdake has quit IRC00:20
*** bcwaldon has quit IRC00:22
*** otherwiseguy has quit IRC00:22
*** bcwaldon has joined #openstack-meeting00:22
*** bcwaldon has quit IRC00:23
*** bcwaldon has joined #openstack-meeting00:23
*** sacharya has joined #openstack-meeting00:28
*** Kharec_ has quit IRC00:32
*** tomoe_ has joined #openstack-meeting00:43
*** jaypipes has quit IRC00:58
*** anteaya has left #openstack-meeting00:59
*** gary_th has quit IRC00:59
*** salv-orlando has quit IRC01:02
*** pony has quit IRC01:06
*** tongli has quit IRC01:09
*** gongysh has joined #openstack-meeting01:10
*** johnpur has left #openstack-meeting01:17
*** vipul is now known as vipul|away01:26
*** ryanpetrello has joined #openstack-meeting01:28
*** ryanpetr_ has quit IRC01:31
*** colinmcnamara has quit IRC01:34
*** gyee has quit IRC01:34
*** jog0 has quit IRC01:45
*** nati_ueno has quit IRC01:57
*** topol has quit IRC02:01
*** dscannell has joined #openstack-meeting02:02
*** Mandell has quit IRC02:06
*** markmcclain has quit IRC02:11
*** novas0x2a|laptop has quit IRC02:12
*** sarob has quit IRC02:13
*** dscannell has quit IRC02:15
*** dscannell has joined #openstack-meeting02:26
*** ladquin has quit IRC02:29
*** vipul|away is now known as vipul02:36
*** otherwiseguy has joined #openstack-meeting02:39
*** sdake_ has quit IRC02:39
*** woodspa has quit IRC02:43
*** dscannell has quit IRC02:53
*** esker has joined #openstack-meeting02:55
*** SergeyLukjanov has joined #openstack-meeting03:18
*** mestery has quit IRC03:21
*** yaguang has joined #openstack-meeting03:22
*** cp16net|away is now known as cp16net03:26
*** danwent has quit IRC03:27
*** cp16net is now known as cp16net|away03:41
*** sandywalsh has quit IRC03:42
*** nati_ueno has joined #openstack-meeting03:47
*** koolhead17 has joined #openstack-meeting03:50
*** nati_ueno has quit IRC03:52
*** nati_ueno has joined #openstack-meeting03:53
*** ryanpetrello has quit IRC03:55
*** danwent has joined #openstack-meeting03:57
*** markmcclain has joined #openstack-meeting03:59
*** adjohn has quit IRC04:00
*** jamespage has quit IRC04:05
*** jamespage has joined #openstack-meeting04:05
*** jamespage has quit IRC04:05
*** jamespage has joined #openstack-meeting04:05
*** bdpayne has quit IRC04:14
*** topol has joined #openstack-meeting04:15
*** sandywalsh has joined #openstack-meeting04:20
*** Mandell has joined #openstack-meeting04:23
*** nati_ueno has quit IRC04:31
*** nati_ueno has joined #openstack-meeting04:32
*** SergeyLukjanov has quit IRC04:55
*** SergeyLukjanov has joined #openstack-meeting04:58
*** SergeyLukjanov has quit IRC05:03
*** adjohn has joined #openstack-meeting05:11
*** adjohn has quit IRC05:15
*** johnpur has joined #openstack-meeting05:23
*** vipul is now known as vipul|away05:33
*** johnpur has left #openstack-meeting05:35
*** esker has quit IRC05:36
*** sacharya has quit IRC05:43
*** egallen has quit IRC05:54
*** egallen has joined #openstack-meeting05:54
*** SergeyLukjanov has joined #openstack-meeting05:57
*** noslzzp has quit IRC05:58
*** cp16net|away is now known as cp16net06:06
*** markmcclain has quit IRC06:08
*** cp16net is now known as cp16net|away06:17
*** topol has quit IRC06:18
*** yaguang has quit IRC06:19
*** yaguang has joined #openstack-meeting06:19
*** nati_ueno has quit IRC06:23
*** reed has quit IRC06:33
*** nati_ueno has joined #openstack-meeting06:33
*** srini_g has joined #openstack-meeting06:51
*** spn has joined #openstack-meeting06:51
*** garyk has joined #openstack-meeting06:51
*** olaph has quit IRC07:16
*** olaph has joined #openstack-meeting07:17
*** mrunge has joined #openstack-meeting07:23
*** llu_away is now known as llu07:28
*** nati_ueno has quit IRC07:34
*** davidha has quit IRC07:35
*** muyInteresante has joined #openstack-meeting07:36
muyInteresante||07:37
muyInteresantehola07:37
*** muyInteresante has left #openstack-meeting07:41
*** johnpur has joined #openstack-meeting07:41
*** salv-orlando has joined #openstack-meeting07:46
*** psedlak has quit IRC07:50
*** pnavarro has joined #openstack-meeting07:51
*** anniec has joined #openstack-meeting07:52
*** dhellmann-afk has quit IRC07:56
*** yaguang has quit IRC07:58
*** rafaduran has joined #openstack-meeting07:59
*** yaguang has joined #openstack-meeting07:59
*** dhellmann has joined #openstack-meeting08:04
*** johnpur has quit IRC08:10
*** koolhead17 has quit IRC08:12
*** flaper87 has joined #openstack-meeting08:15
*** jhenner has joined #openstack-meeting08:19
*** almaisan-away is now known as al-maisan08:22
*** yaguang has quit IRC08:25
*** yaguang has joined #openstack-meeting08:25
*** Kharec has joined #openstack-meeting08:27
*** jhenner has quit IRC08:29
*** Kharec has quit IRC08:31
*** Kharec has joined #openstack-meeting08:34
*** psedlak has joined #openstack-meeting08:40
*** davidha has joined #openstack-meeting08:47
*** ndipanov has joined #openstack-meeting08:56
*** afazekas has joined #openstack-meeting08:57
*** afazekas has quit IRC08:59
*** jhenner has joined #openstack-meeting09:00
*** al-maisan is now known as almaisan-away09:01
*** danwent has quit IRC09:02
*** ndipanov has quit IRC09:02
*** dosaboy has joined #openstack-meeting09:02
*** Kharec has joined #openstack-meeting09:02
*** tomoe_ has quit IRC09:04
*** yaguang has quit IRC09:17
*** ndipanov has joined #openstack-meeting09:17
*** almaisan-away is now known as al-maisan09:24
*** afazekas has joined #openstack-meeting09:32
*** SergeyLukjanov has quit IRC09:36
*** SergeyLu_ has joined #openstack-meeting09:36
*** darraghb has joined #openstack-meeting09:38
*** darraghb has quit IRC09:38
*** darraghb has joined #openstack-meeting09:39
*** darraghb has quit IRC09:39
*** darraghb has joined #openstack-meeting09:40
*** davidha has quit IRC09:54
*** davidha has joined #openstack-meeting09:56
*** ndipanov has quit IRC10:08
*** davidha has quit IRC10:10
*** ndipanov has joined #openstack-meeting10:20
*** derekh has joined #openstack-meeting10:20
*** otherwiseguy has quit IRC10:27
*** yaguang has joined #openstack-meeting10:44
*** spn has quit IRC10:48
*** srini_g has quit IRC10:49
*** johnthetubaguy has joined #openstack-meeting10:53
*** SergeyLu_ has quit IRC10:55
*** SergeyLukjanov has joined #openstack-meeting11:22
*** davidha has joined #openstack-meeting11:23
*** mkollaro has joined #openstack-meeting11:35
*** pnavarro has quit IRC11:50
*** pnavarro1 has joined #openstack-meeting11:54
*** SergeyLukjanov has quit IRC11:55
*** SergeyLukjanov has joined #openstack-meeting11:57
*** topol has joined #openstack-meeting12:04
*** ijw has joined #openstack-meeting12:19
*** ijw1 has joined #openstack-meeting12:30
*** ijw1 has joined #openstack-meeting12:31
*** ijw has quit IRC12:33
*** yaguang has quit IRC12:36
*** dtroyer_zz has quit IRC12:40
*** dtroyer has joined #openstack-meeting12:40
*** ijw1 is now known as ijw12:44
*** tomoe_ has joined #openstack-meeting12:46
*** jhenner has quit IRC12:48
*** SergeyLukjanov has quit IRC12:57
*** tongli has joined #openstack-meeting12:57
*** dolphm has joined #openstack-meeting13:04
*** johnthetubaguy has quit IRC13:12
*** olaph has left #openstack-meeting13:13
*** eharney has quit IRC13:18
*** dprince has joined #openstack-meeting13:25
*** bryansd has left #openstack-meeting13:26
*** jhenner has joined #openstack-meeting13:31
*** eharney has joined #openstack-meeting13:33
*** brianr-gone has quit IRC13:41
*** brianr-gone has joined #openstack-meeting13:41
*** johnthetubaguy has joined #openstack-meeting13:45
*** johnpur has joined #openstack-meeting13:47
*** radez_g0n3 is now known as radez13:49
*** jhenner has quit IRC13:53
*** jhenner has joined #openstack-meeting13:54
*** psedlak has quit IRC14:03
*** dolphm has quit IRC14:05
*** dolphm has joined #openstack-meeting14:10
*** afazekas has quit IRC14:17
*** johnpur has left #openstack-meeting14:21
*** sdake_ has joined #openstack-meeting14:22
*** woodspa has joined #openstack-meeting14:25
*** ryanpetrello has joined #openstack-meeting14:26
*** dscannell has joined #openstack-meeting14:46
*** sandywalsh has quit IRC14:51
*** mtreinish has joined #openstack-meeting14:51
*** jhenner has quit IRC14:53
*** john5223 has joined #openstack-meeting14:55
*** sandywalsh has joined #openstack-meeting15:04
*** esker has joined #openstack-meeting15:06
*** annegentle has joined #openstack-meeting15:10
*** noslzzp has joined #openstack-meeting15:11
*** fnaval has quit IRC15:14
*** markmcclain has joined #openstack-meeting15:14
*** topol has quit IRC15:20
*** cp16net|away is now known as cp16net15:20
*** Gordonz has joined #openstack-meeting15:22
*** annegentle has quit IRC15:23
*** Gordonz has quit IRC15:23
*** Gordonz has joined #openstack-meeting15:24
*** lbragstad has quit IRC15:25
*** ladquin has joined #openstack-meeting15:26
*** annegentle has joined #openstack-meeting15:28
*** jaypipes has joined #openstack-meeting15:29
*** otherwiseguy has joined #openstack-meeting15:31
*** sandywalsh has quit IRC15:32
*** fnaval has joined #openstack-meeting15:33
*** Gordonz has quit IRC15:33
*** Gordonz has joined #openstack-meeting15:34
*** dolphm has quit IRC15:34
*** dolphm has joined #openstack-meeting15:36
*** markmcclain has quit IRC15:36
*** eharney has quit IRC15:40
*** sandywalsh has joined #openstack-meeting15:44
*** ryanpetrello has quit IRC15:49
*** ryanpetrello has joined #openstack-meeting15:49
*** dscannell has quit IRC15:49
*** dscannell1 has joined #openstack-meeting15:50
*** topol has joined #openstack-meeting15:51
*** diogogmt has joined #openstack-meeting15:52
*** sacharya has joined #openstack-meeting15:52
*** SergeyLukjanov has joined #openstack-meeting15:53
*** markmcclain has joined #openstack-meeting15:53
*** dontalton has joined #openstack-meeting15:54
*** jgallard has joined #openstack-meeting15:56
*** vincent_hou has joined #openstack-meeting15:57
*** smulcahy has joined #openstack-meeting15:58
*** bvibhu has joined #openstack-meeting16:00
*** mrunge has quit IRC16:00
jgriffith#startmeeting cinder16:00
openstackMeeting started Wed Mar  6 16:00:43 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
jgriffithHmmm... anybody here this morning?16:01
bvibhuHi16:01
jgallardhi!16:01
smulcahyhi16:01
vincent_houy16:01
*** thingee has joined #openstack-meeting16:01
jgriffithThere's some folks... morning guys16:01
thingeeo/16:01
jgriffithPretty short agenda today16:02
jgriffithmight be even shorter without some of the folks being around16:02
*** winston-d has joined #openstack-meeting16:02
guitarzanmorning!16:02
*** JM1 has joined #openstack-meeting16:02
JM1hi16:02
jgriffithheyhey16:02
jgriffithalright, now we're rolling, let's get started16:02
*** ryanpetrello has quit IRC16:02
jgriffith#topic RC1 status updates16:02
*** openstack changes topic to "RC1 status updates (Meeting topic: cinder)"16:02
jgriffithI'm hoping to cut next week unless folks see a problem getting their fixes in16:03
*** matelakat has joined #openstack-meeting16:03
*** xyang_ has joined #openstack-meeting16:03
jgriffithOr of course somebody finds something horrible between now and then16:03
*** ryanpetrello has joined #openstack-meeting16:03
jgriffithany objections on that?16:03
jgriffithBTW: https://launchpad.net/cinder/+milestone/grizzly-rc116:04
*** hub_cap has joined #openstack-meeting16:04
*** bswartz has joined #openstack-meeting16:04
jgriffithTake a look and if you have something new let me know, or if you have something that should be targetted and isn't let me know that as well16:04
bswartzhey sorry I'm late16:04
jgriffithbswartz: no worries16:04
winston-di see john's got 6 bug assigned. :)16:04
jgriffithwinston-d: :)16:04
kmartinjgriffith: It is too late to get the LeftHand driver fixes into RC116:04
jgriffithkmartin: nope16:05
jgriffithkmartin: I am not super strict about targetting16:05
jgriffithkmartin: but we should probably update those bugs with RC1 tags16:05
kmartinok, I 'll have hemna send bug to you today16:05
jgriffithkmartin: do you expect to get them in this week?16:06
kmartinyes16:06
jgriffithkmartin: we should be just fine then16:06
jgriffithwinston-d: that reminds me, do you want https://bugs.launchpad.net/cinder/+bug/113132216:06
uvirtbotLaunchpad bug 1131322 in cinder "Cinder service not logging exceptions from stevedore library" [High,Confirmed]16:06
winston-djgriffith: yes, please16:07
jgriffithwinston-d: All yours :)16:07
matelakatjgriffith: Can we have this in rc1 as well? https://bugs.launchpad.net/cinder/+bug/113129116:07
uvirtbotLaunchpad bug 1131291 in cinder "XenAPINFS: Volume always uploaded as vhd/ovf" [Undecided,Fix committed]16:07
smulcahyjgriffith: https://bugs.launchpad.net/cinder/+bug/1136174 has been fixed aswell so not sure if you want to target that too?16:07
uvirtbotLaunchpad bug 1136174 in cinder "cinder-backup doesn't use/check metadata version during restore" [Undecided,Fix committed]16:07
jgriffithwinston-d: do you think we can get that done this week?16:07
winston-djgriffith: but if it requires something in olso, it might not make it to RC116:07
*** gary_th has joined #openstack-meeting16:07
jgriffithmatelakat: committed ones don't need much persuasion frm me  :)16:07
jgriffithsmulcahy: I can if you'd like it for tracking/record keeping16:08
jgriffithsmulcahy: done16:08
winston-djgriffith: i'll try my best16:08
smulcahyjgriffith: ta16:08
*** Mandell has quit IRC16:08
jgriffithwinston-d: I was afraid of that16:08
thingeejgriffith: is there an update from j_king on https://bugs.launchpad.net/cinder/+bug/1087817 ?16:08
uvirtbotLaunchpad bug 1087817 in cinder "Update v2 with volume_type_id switch to uuid" [Medium,In progress]16:08
jgriffithwinston-d: Let me know if I need to work with Mark to try and get it in if you can get it proposed16:09
matelakatjgriffith: So I don't need to take actions to get that to rc1, right (sorry, if this is a stupid q)16:09
winston-djgriffith: sure16:09
jgriffiththingee: I've not heard back from him, I did ping him the other day on it16:09
thingeeI can do last minute work if needed there16:10
jgriffiththingee: wonder if we should just reassign and fix it16:10
jgriffith:)16:10
thingeeI'm sure he has it though16:10
jgriffiththingee: alright, let's give him another day or so16:10
jgriffiththingee: thanks!16:10
jgriffithmatelakat: nope, I already did it16:10
jgriffithand just in case others are not sure how that works...16:10
jgriffithbasicly anything that's going in to trunk right now is going in to RC116:11
*** otherwiseguy has quit IRC16:11
matelakatOh, ok.16:11
jgriffithThe targetting exercise just makes sure we know what we have deemed as *required* for rc116:11
jgriffithTechnically one could argue that everything that goes in should be targetted at this point16:12
jgriffithbut Cinder is a bit unique with it's heavy driver model :)16:12
jgriffithAny folks having the chance to do some good testing lately?16:13
jgriffithI'd like to see as many of us as possible start switching context to testing and documentation over the next few days if possible16:13
jgriffithand grenade testing as well (Folsom to Grizzly upgrade testing)16:14
*** mrodden has quit IRC16:14
jgriffithWell I see that was a popular topic :)16:14
matelakatbtw, I asked Anne About it, but is this the right place for the driver docs? #link http://docs.openstack.org/trunk/openstack-compute/admin/content/ch_volumes.html16:14
jgriffithmatelakat: it is for now, I have a todo item to create a "block storage" section and move all of that out of compute admin16:15
jgriffith#action jgriffith get the doc formatting stuff figured out with Anne and done16:15
jgriffithany other big questions/concerns for RC1?16:16
jgriffith#topic core team status16:16
*** openstack changes topic to "core team status (Meeting topic: cinder)"16:16
jgriffithSo we've talked about this before but always wait for the *next* mile marker16:17
jgriffithI'd like to propose that we clean out the core list of cinder16:17
jgriffithWhat I mean here is the folks that were set up in Folsom but never really participated16:17
bswartzjgriffith: is this "core list" published somewhere?16:18
*** eharney has joined #openstack-meeting16:18
*** eharney has quit IRC16:18
*** eharney has joined #openstack-meeting16:18
jgriffithI'd like to trim that list and make some new nominations this week if possible16:18
jgriffithbswartz: yes of course https://launchpad.net/~cinder-core16:19
bswartzthanks16:19
annegentlewhat do you all think about starting a storage admin manual?16:19
jgriffithannegentle: :)16:19
annegentlealso I would like eyes on https://review.openstack.org/#/c/23625/16:20
DuncanTDo we have a list of contributers and reviewers for the last few months? Seems like a good place to start for list trimming...16:20
jgriffithannegentle: That's what I was getting at earlier16:20
*** dricco has joined #openstack-meeting16:20
annegentlesorry I am late and the topic changed :)16:20
jgriffithannegentle: no worries16:20
thingeeannegentle: I'll check it out :)16:20
jgriffithI'll have a look at the review you pointed out as well16:20
jgriffithannegentle: and I'd definitely like to have a block-storage admin guide16:21
jgriffithmove the cinder stuff out of the compute admin doc16:21
annegentlejgriffith: yeah I think that's the way to go16:21
annegentlejgriffith: anyone in mind to do the refactor?16:21
*** cp16net is now known as cp16net|away16:21
jgriffithannegentle: unless somebody else steps up proabably me16:21
annegentlejgriffith: there may be others interested I can recruit for you if you want :)16:22
thingeeannegentle, jgriffith: I did it for api, why not? :)16:22
jgriffithI'd like this to be ASAP16:22
annegentlethingee: woo! :)16:22
annegentlethingee: yeah you have your plate full getting the API docs in shipshape16:22
jgriffiththingee: You're the MAN!!!16:22
jgriffithSo let's do this16:22
thingeethose are at least in a review phase. I still have more I want to do with them, but in the mean time can focus on admin16:22
jgriffithI'd like to have this refactor by next week at latest16:23
jgriffithIf anybody has some cycles and gets to it before I'll have a chance (which will be mid next week)16:23
jgriffithLet folks know16:23
jgriffithWe'll open a docs bug for it and target it so folks will know if it's picked up active etc16:24
jgriffithannegentle: thingee sound good?16:24
annegentlejgriffith: sounds jus tright16:24
annegentlejust right even16:24
jgriffithcoolness16:24
*** dontalton has quit IRC16:24
*** metral has joined #openstack-meeting16:24
thingeesounds good16:24
bswartzjgriffith: is there any officially organized group of "cinder team members" who are not not in the core team but more involved than your average Joe on the street?16:24
jgriffiththingee: if you've got the band-width that's awesome by me :)16:24
thingeeI don't have anything planned atm, so I'm fine with it16:24
jgriffithbswartz: nope16:24
jgriffithbswartz: DuncanT to that point searches in gerrit are the answer16:24
winston-djgriffith: i'll see if i can provide you some review numbers tomorrow16:25
DuncanTjgriffith: I'll try to produce some stats if you want...16:25
DuncanT(or winston-d can beat me to it... I'm easy ;-) )16:25
winston-dDuncanT: :)16:26
jgriffithwinston-d: oh, cool  I was going to be less formal and do it ad-hoc16:26
jgriffithwinston-d: however the stats would be good for *new* core nominees16:26
bswartzjgriffith: is there are difference between the "cinder core" team and the set of people who are "core approvers" (can +2 stuff)?16:26
jgriffithbswartz: nope, they're one in the same16:26
bswartzokay16:26
*** topol_ has joined #openstack-meeting16:27
jgriffithanybody have anything else on core team, or docs?16:27
kmartinjgriffith: Regarding docs, will they take changes all the way up to the end of the release or are the docs connected to the RC releases as well16:27
jgriffithkmartin: docs we have more flexibility there16:27
jgriffithbut we've procrastinated before and we always seem to run out of time16:28
*** johnpur has joined #openstack-meeting16:28
annegentlekmartin: right. We take a look at the bugs and figure out if the docs are releasable16:28
kmartinok we have doc person that wants to be a OpenStack contributor, so he is working though that process16:28
annegentlekmartin: it's that balancing act between "will this answer questions or cause more questions"16:28
jgriffithkmartin: NICE!16:28
*** garyk has quit IRC16:29
jgriffithalright, folks think about if you know of somebody that you think should be core, or if you want to nominate somebody (even yourself) and let me know16:29
kmartingoal is to get the changes in the end on next week16:29
bswartzregarding the core team -- I find the idea of a 2-tier core team structure appealing16:30
*** topol has quit IRC16:30
*** topol_ is now known as topol16:30
*** cp16net|away is now known as cp16net16:30
jgriffithbswartz: I'm not really interested in changing the OpenStack management/organization structure but I'm listening...16:30
jgriffithbswartz: what are you proposing?16:31
*** mrodden has joined #openstack-meeting16:31
bswartzwell I sympathize with the desire to keep the team small, and weed out non-participators, but I think it's good to have a wider group of people who are incentivised to be online answering questions and participating in code reviews, etc16:31
jgriffithbswartz: Actually that's what *core* is supposed to be16:31
*** dachary has joined #openstack-meeting16:32
jgriffithbswartz: our team is rather small because our consistent participation until the past couple of months has been relatively minimal16:32
bswartzI guess I worry that people who don't make the cut for the "core team" won't feel any incentive to contribute16:33
jgriffithbswartz: and everyone so here's my metric...16:33
jgriffithWhat I've been looking at the past week is this:16:33
jgriffith1. People that have contributed code to the core cinder project this cycle16:33
jgriffith2. People that have reviewed code16:33
jgriffith3. People that participate in IRC (including this meeting)16:33
bswartzmaybe your definition of core team includes my notion of both tiers or participation16:34
*** egallen_ has joined #openstack-meeting16:34
jgriffithbswartz: perhaps16:35
*** dolphm has quit IRC16:35
jgriffithAlso bear in mind core definition is an OpenStack wide policy16:35
bswartzI just wanted to throw it out there -- I haven't though this through fully16:35
jgriffithhttps://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess16:35
bswartzthought*16:35
jgriffithbswartz: believe me, I'm all for having more core team members!16:36
*** egallen has quit IRC16:36
*** egallen_ is now known as egallen16:36
jgriffithand I plan to nominate at least 3 folks later today16:36
*** markmcclain has quit IRC16:36
jgriffithbswartz: and if you'd like to step up and take on the responsibilities let me know16:36
dacharyas an occasional contributor to various free software, I would be very motivated to be on a separate list. I understand the separation between "core" and "contributor"16:36
dacharymy 2ct ;-)16:37
jgriffithdachary: I'm confused, we already have this16:37
jgriffithdachary: bswartz So we have contributors16:37
jgriffithcontributors can review, provide input, do anything they want16:37
dacharyjgriffith: yes, I was echoing on the "no motivation if not in the core" ;-)16:37
jgriffithcore just means you're especially active and responsible for +2/A authority16:37
*** spligak has joined #openstack-meeting16:38
jgriffithdachary: Ahh... ok, :)16:38
jgriffiththanks16:38
jgriffithMy thought is if you're not motivated when you're not core, you won't be much of a core contributor anyway16:38
jgriffithbut I digress16:38
jgriffithbswartz: If you have some structuring ideas we can definitely talk through them and see if there's a better system16:39
*** alexpilotti has joined #openstack-meeting16:39
jgriffithanything else regarding core?16:39
jgriffith#topic summit session16:40
*** openstack changes topic to "summit session (Meeting topic: cinder)"16:40
*** egallen has quit IRC16:40
thingeehttp://summit.openstack.org16:40
*** dolphm has joined #openstack-meeting16:40
winston-djgriffith: when is deadline for submitting session for summit?16:40
dachary#link http://summit.openstack.org/cfp/details/3816:40
jgriffithwinston-d: I actually don't have an answer on that for you16:41
*** anniec has quit IRC16:41
*** egallen has joined #openstack-meeting16:41
jgriffithWe haven't even begun talking about track scheduling etc yet16:41
*** bdpayne has joined #openstack-meeting16:41
winston-djgriffith: k. i'll submit my ideas ASAP anyway16:41
dacharyI've discussed this tentative session on the ceph mailing list and there is an interest. I feel it's better associated with cinder but I'm not 100% sure. Roadmap for Ceph integration with OpenStack http://summit.openstack.org/cfp/details/3816:42
jgriffithwinston-d: good idea :)16:42
jgriffithIf nothing else submit things as place holders16:42
jgriffithdachary: yeah, I've been following that16:42
*** henrynash has quit IRC16:43
dacharyjgriffith: what's your advice ?16:43
jgriffithdachary: I have no good advice at this point :)16:43
jgriffithdachary: So my take was/is16:43
jgriffithif there's room in Cinder tracks I don't mind it, however what you have planned seems much more nova related IMO16:44
jgriffithdachary: bottom line, if it needs a place to land and you're in a jam we can work it out in Cinder16:44
jgriffithbut it almost seems you need your *own* independent track16:44
thingeejgriffith: +116:45
jgriffithdachary: or if we do another *general all/around* bucket again that would be ideal16:45
dacharythat makes sense, I'll move it to nova then.16:45
jgriffithdachary: Your call, if you get in a bind scheduling wise let me know and we'll work something out16:45
dacharyjgriffith: thanks :-)16:45
jgriffithdachary: I also think we should ask about cross-project tracks16:45
dacharyI'll discuss this with ttx, good idea16:46
jgriffithcool16:46
*** johnpur has left #openstack-meeting16:46
jgriffithwe've had that sort of thing in the past IIRC16:47
jgriffithOk... anything else on sessions?16:47
jgriffithbswartz: ?16:47
jgriffithI'm assuming we're going to need to hash something out for real this time on File Shares16:47
jgriffithbswartz: But that might be better as it's own type of session as well (non-cinder track)16:48
jgriffithwell if nobody else has anything....16:48
bswartzWe're planning to address the feedback we've gotten so far on the NAS stuff so it's ready when Havana opens up16:48
DuncanTjgriffith: Would you rather have separate proposals for small things then combine them later?16:48
jgriffithDuncanT: small and combine later please16:49
thingeedachary: IMO, ceph has little to do with cinder's core. Unless your proposed changes are actually requesting big changes.16:49
jgriffithDuncanT: it tends to make things easier to schedule16:49
jgriffiththingee: +116:49
DuncanTjgriffith: Understood16:49
jgriffithDuncanT: but if you have a well organized grouping by all means, it's up to you16:49
*** johnthetubaguy has quit IRC16:49
bswartzI worry a little that another conference session might feel like a rerun given that the features have not changed significantly, just the impelmentation16:49
jgriffithDuncanT: It's just easier for me to see overlap and tie ins if they're seperated16:50
dacharythingee: yes, you are correct16:50
*** vipul|away is now known as vipul16:50
jgriffithbswartz: agreed, I have some suggestions for how to do this differently this time16:50
jgriffithbswartz: one is already taken care of (don't have a *surprise* proposal in the session)16:50
DuncanTbswartz: I think some of the concerns, particularly about buy-in from other users, might benefit from a session if we can get some of them there16:50
jgriffithif there had been some communication and the code was shared before the session I think it would have been moe productive16:51
jgriffiths/moe/more/16:51
bswartzjgriffith, DuncanT: I agree16:51
*** dontalton has joined #openstack-meeting16:51
jgriffithDuncanT: bswartz Recall in SanFran there was actually a storage panel that discussed this with a broader audience16:51
jgriffithThe resounding response was *yes, we want shared filesystem support*16:52
jgriffith*no, it shouldn't be in Cinder*16:52
*** davidha has quit IRC16:52
jgriffithIt's actually on video somewhere16:52
bswartzjgriffith: I'm not sure which session you're referring to16:52
jgriffithbswartz: It was a panel discussion... Rob, SF, Mirantis, Nexenta16:53
bswartzOn the first day? I think I was there16:53
jgriffithbswartz: I think it was the last day, but not sure16:53
bswartzI have a different memory of events -- but I might be remembering a different session16:53
jgriffithI'll see if I can't find the link16:53
bswartzplease do16:53
jgriffithYes you and Rob have pointed out that my memory is apparantly *wrong*16:54
*** otherwiseguy has joined #openstack-meeting16:54
*** jaypipes has quit IRC16:54
bswartzI think the point of contention is about how resounding the response was16:54
bswartzclearly some people think NAS doesn't belong in cinder16:55
jgriffithbswartz: sure...16:55
jgriffithanyway, we'll sort it this time around16:55
jgriffithanybody have anything else?16:55
jgriffithI'll find the link and hit you up in the channel with it16:56
jgriffithOk... thanks everyone16:56
jgallardThe work regarding multi backend / tempest integration test is in progress.16:56
jgriffith#end meeting16:56
dacharythanks :-)16:56
jgriffith#endmeeting16:56
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:56
openstackMeeting ended Wed Mar  6 16:56:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
jgallardI hope I will propose something for feedback asap16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-03-06-16.00.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-03-06-16.00.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-03-06-16.00.log.html16:56
jgallardthanks16:56
*** xyang_ has left #openstack-meeting16:56
guitarzanphew, one minute left16:56
bswartzended on time!16:56
*** bvibhu has quit IRC16:56
winston-d:)16:56
*** bswartz has left #openstack-meeting16:57
*** hub_cap has left #openstack-meeting16:57
*** winston-d has left #openstack-meeting16:57
*** dricco has left #openstack-meeting16:57
*** arbrandes has joined #openstack-meeting16:59
*** smulcahy has left #openstack-meeting17:00
*** johnthetubaguy has joined #openstack-meeting17:00
*** jaypipes has joined #openstack-meeting17:01
johnthetubaguy#startmeeting XenAPI17:01
openstackMeeting started Wed Mar  6 17:01:12 2013 UTC.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: XenAPI)"17:01
openstackThe meeting name has been set to 'xenapi'17:01
BobBallYay :)17:01
*** thingee has left #openstack-meeting17:01
johnthetubaguyhi everyone17:01
BobBallMorning John17:02
BobBallor afternoon17:02
BobBalldepending on where everyone is17:02
matelakathi17:02
johnthetubaguy#topic actions from last meeting17:02
*** openstack changes topic to "actions from last meeting (Meeting topic: XenAPI)"17:02
johnthetubaguySo I had a few actions17:02
*** westmaas_ has quit IRC17:02
johnthetubaguy#action johnthetubaguy needs to do the actions from last week17:03
BobBallhaha17:03
BobBallnice action17:03
johnthetubaguybeen stuck with XCP on CentOS, so not really started on the CentOS install docs17:03
johnthetubaguyhey ho17:03
matelakatI guess it was a busy week.17:03
*** dachary has left #openstack-meeting17:03
* johnthetubaguy bangs head against wall17:03
johnthetubaguyanyways...17:03
BobBallWhat's the progress on XCP on CentOS?17:04
johnthetubaguy#topic blueprints17:04
*** openstack changes topic to "blueprints (Meeting topic: XenAPI)"17:04
johnthetubaguywe got a meeting on that Tueday 17.00 UTC in #centos-devel17:04
*** SergeyLukjanov has quit IRC17:04
johnthetubaguysummary: broken with odd permissions errors, no one really can tell why17:04
*** al-maisan is now known as almaisan-away17:05
BobBallsounds fun17:05
johnthetubaguyjoyus17:05
johnthetubaguyso… blueprints?17:05
johnthetubaguyjust a call to look at the etherpad for the summit and add things17:05
BobBalloh17:05
johnthetubaguywe added the odd bit last time17:05
BobBallI forgot to add stuff17:05
BobBalllemme have a quick look17:05
johnthetubaguy#link https://etherpad.openstack.org/HavanaXenAPIRoadmap17:06
BobBallyeah17:06
BobBalljust got it from the web page17:06
BobBallmy bad, sorry17:06
johnthetubaguynp17:06
BobBallokay17:06
*** JM1 has left #openstack-meeting17:06
BobBallthere is one key thing that isn't there17:06
BobBallor if it is then I can't see...17:06
BobBallis quantum support for XS17:07
BobBalldidn't make grizzly-317:07
johnthetubaguyits a nova session though17:07
BobBallso it should definitely be on the roadmap even if we don't need a new blueprint17:07
BobBallahhhhh17:07
johnthetubaguyit was covered in the last summit17:07
BobBalldidn't spot that from etherpad!17:07
johnthetubaguyimplementation agreed, code pushed for review17:07
BobBall*nod*17:07
johnthetubaguybut only one quatum core ever reviewed17:07
*** arbrandes has left #openstack-meeting17:07
johnthetubaguyjust to document / share17:08
BobBallTis a shame it didn't make the grizzly cut!17:08
johnthetubaguyindeed, we half planned a backport to folsom17:08
johnthetubaguybut no one will review it, but hopefully that will change now17:09
johnthetubaguyso anything else?17:09
johnthetubaguyblueprint wise17:09
BobBallnot from my end17:09
johnthetubaguy#topic docs17:10
*** openstack changes topic to "docs (Meeting topic: XenAPI)"17:10
johnthetubaguyany news?17:10
johnthetubaguyI didn't do my things17:10
johnthetubaguythere was a note on the mailing list about live-migraiton docs17:10
BobBallbut I guess there will be an AOB for adding new features to the roadmap?17:10
johnthetubaguythey look fairly poor, might need to expand them17:10
johnthetubaguysure, we can do17:10
BobBallwe've got a plan to look at some docs - Mate has an action this week to go through and look at what's there17:10
johnthetubaguycool17:11
johnthetubaguy#action matelakat to look at state of XenAPI docs and report back next week17:11
BobBallthere we go :D17:11
BobBallI was going to say can you add an #action17:11
johnthetubaguycatch me on IRC if there are questions17:11
matelakat#link https://github.com/citrix-openstack/bugstat/blob/master/bugreport/main_report.md#openstack-manuals----2017:11
johnthetubaguycool17:12
matelakatA lot to do...17:12
johnthetubaguysome of those don't affect XenAPI17:13
matelakatit's just a dumb search17:13
johnthetubaguysure, no worries17:13
*** danwent has joined #openstack-meeting17:13
matelakatI will look at them, and put em to categories.17:13
BobBalle.g. https://bugs.launchpad.net/openstack-manuals/+bug/109509517:13
uvirtbotLaunchpad bug 1095095 in openstack-manuals "Configuring for resize with KVM" [Medium,Confirmed]17:13
BobBalljust says KVM docs aren't as good as XenServer for resize17:13
matelakatSo it includes the string "XenServer"17:14
BobBallindeed17:14
BobBallbut only in the context of "XenServer doesn't have this bug" :)17:14
*** gyee has joined #openstack-meeting17:14
johnthetubaguyits probably worth manually added xenserver tags, and having a tag only search17:15
johnthetubaguyanyways, lets move on17:15
*** koolhead17 has joined #openstack-meeting17:15
*** dscannell1 has quit IRC17:15
johnthetubaguyany more for any more?17:15
BobBallI'd like to keep the dumb search, but use the tagged search to say "this has been triaged by someone who knows it's a XS bug"17:15
johnthetubaguy+117:15
johnthetubaguythat is what I meant17:16
BobBallah right17:16
johnthetubaguy#topic QA and Bugs17:16
*** openstack changes topic to "QA and Bugs (Meeting topic: XenAPI)"17:16
johnthetubaguyanything major worrying people?17:16
johnthetubaguymatelakat have you got the link to your bug finder?17:17
BobBallI guess one thing that surprised me is that devstack multihost doesn't seem to be tested by anyone else17:17
matelakat#link https://github.com/citrix-openstack/bugstat17:17
guitarzanwe'd like to get some eyes on this: https://review.openstack.org/#/c/23662/17:18
BobBall*has a butchers*17:18
BobBallThat one's an interesting issue!17:20
guitarzanand a little painful :)17:20
guitarzanI'm going to try it out17:21
BobBallSo has the whole SR gone away?17:21
guitarzanhopefully with the patch, yes17:21
BobBallahhh - this an iSCSI SR?17:21
guitarzanyes17:21
johnthetubaguyI guess the point is, if your iSCSI target dies, then VM will not start17:21
guitarzanjohnthetubaguy: exactly17:22
BobBallyup - not surprising.17:22
BobBallokay17:22
BobBallgot it17:22
BobBallI was getting a little confused17:22
guitarzanI'm not sure what happens in the other HVs case17:22
guitarzanbut I also don't have to worry about that case17:22
BobBall*grin*17:23
BobBallI'll have to have a think about this one17:23
johnthetubaguyyeah, sounds like an excessive timeout, would be nice to be able to specify that in the check call17:23
guitarzans1rp and I talked about it quite a bit, and this seems to be the best we could come up with on short notice17:24
guitarzanmad props to him for making it work17:24
BobBallyou mean the XAPI timeout?17:24
johnthetubaguyerm, timeout in the xapi operation17:24
BobBallI guess this is currently a critical issue for you guys?17:25
guitarzanwell, it's an ugly one17:25
guitarzanrequires ops to go in and nuke the SR17:25
guitarzanit doesn't happen often17:25
johnthetubaguymaybe some kind of health check would be better, with tunable timeout17:25
guitarzanit should only happen if something happens to the network or we lose a storage node17:25
johnthetubaguyI like scan SR because it should be quick in the working cases17:26
BobBallso XS doesn't timeout the SR?17:26
*** lloydde has joined #openstack-meeting17:26
*** jhenner has joined #openstack-meeting17:26
*** vincent_hou has quit IRC17:26
johnthetubaguyoh, I see you only call that in error cases17:26
guitarzanjohnthetubaguy: yeah, we don't do anything unless it doesn't boot17:26
*** mrodden1 has joined #openstack-meeting17:27
johnthetubaguymakes sense17:27
*** reed has joined #openstack-meeting17:27
BobBallhow long ago had the SR gone away?17:27
BobBallor had it only just gone?17:27
johnthetubaguyshame we can't have a non destructive error case again, do we need to tell cinder we detached the volume?17:27
guitarzanthe sr is still there, it just can't make the iscsi connection17:27
guitarzanjohnthetubaguy: compute manager does that17:28
BobBallAlso, could you just post the XS error log to the bug so that we've got a traceback17:28
guitarzanthe fun part was propagating the bad devices back up to compute17:28
BobBall*grin* that does look fun17:28
johnthetubaguyah, got ya, didn't get there yet17:28
*** mrodden has quit IRC17:29
guitarzanBobBall: I'll try to remember to paste a stack17:29
BobBallthis _handle_bad_volumes_detached case?17:29
guitarzanwell, I'll grab the xen log from the failed boot17:29
BobBallthat's perfect17:30
johnthetubaguypull out the network cable between your iscsi target an hypervisor, it should repo OK17:30
* BobBall is impressed with this one17:30
BobBallI like that bug17:30
*** jhenner has quit IRC17:30
guitarzanglad you like it17:30
BobBallis there a Bug Of The Month award?17:30
guitarzanwe were hoping XS would boot without all the volumes, but alas17:31
*** SergeyLukjanov has joined #openstack-meeting17:31
BobBallyup17:31
*** SergeyLukjanov has quit IRC17:31
BobBallwell we might also be able to patch ISCSISR.py to do something17:31
BobBallnot sure17:31
johnthetubaguygood old xapi trying to protect us from doing bad things again17:31
BobBalldepends how the SR is failing17:31
BobBallunlikely to be XAPI17:31
johnthetubaguyoh, OK17:31
BobBallis it the vm start that fails? I'm almost surprised the shutdown works ok if the SR is timing out17:32
johnthetubaguyit probably got shutdown before that right?17:32
guitarzanI'm not sure17:32
johnthetubaguyor this is the first start?17:32
guitarzanit's a reboot, so it wasn't really shut down17:32
johnthetubaguyah17:32
* johnthetubaguy remembers bug report…drrr17:33
BobBallok well might I suggest that John, you and I take an action to look at it?17:33
BobBallI see you've already added yourself!17:33
BobBallhah :)17:33
johnthetubaguymake sure the SR is behaving correctly, for the "graceful" fix17:33
BobBallguitarzan, do you happen to know if this is a soft or hard reboot?17:34
*** lbragstad has joined #openstack-meeting17:34
johnthetubaguy#action johnthetubaguy guitarzan to look into broken SR issues https://review.openstack.org/#/c/2366217:34
guitarzanBobBall: not sure17:35
guitarzanI'll try both17:35
johnthetubaguymaybe hard because soft failed...17:35
johnthetubaguycool17:35
BobBallprobably both tbh17:35
*** dscannell has joined #openstack-meeting17:35
guitarzanthat's my guess17:35
johnthetubaguycool17:35
BobBall*not sure if XAPI handles the SRs differently for the two cases*17:36
BobBallAnyway - let's move on :)17:36
johnthetubaguyindeed17:36
johnthetubaguyany more bugs?17:36
johnthetubaguyme guessing that is a no...17:36
johnthetubaguy#topic Open Discussion17:36
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"17:36
johnthetubaguyso, bobball has a few things?17:37
s1rpohai guys...17:37
johnthetubaguyhey17:37
guitarzanwe were just talking about you17:37
s1rpyeah the clean_reboot operation hangs for 120 secs...17:37
s1rpluckily a subsequent SR.scan seems to be quick-ish17:37
BobBallahhhhh17:37
s1rponly the first-one after unplugging seems to be slow17:37
s1rpit's like it stores some data somewhere marking it as failed (?)17:38
guitarzanBobBall: I haven't tried that iscsi patch you sent me yet17:38
johnthetubaguythat figures, cool17:38
BobBalls1rp, I thought it was the SR scan that waited 120 seconds17:38
BobBallfailing fast in clean_reboot is likely to be a XAPI thing waiting for the SR to respond to it's attach request17:39
s1rpthat too... lemme clarify17:39
*** Mandell has joined #openstack-meeting17:39
BobBallsorry john - we're derailing the agenda :D17:39
s1rpso if you do an sr-scan w/o a reboot, then that call will take 120 secs (this is what i was doing on the comand line to troubleshoot this)17:39
johnthetubaguyits OK, its important17:40
s1rpbut, and i'm not 100% sure on this, but if you do a clean_reboot, that will cause an underlying timeout, but i *think* the next SR.scan will actually fail-fast17:40
BobBallah - but failed reboot followed by sr-scan to find the failing device is fast17:40
s1rpBobBall: yeah, need to triple check that case, but i believe so17:40
BobBallunfortunately that might mean the timeout is in iscsiadm ?17:40
BobBall... or fortunately :)17:40
BobBallthat might be easy to fix17:40
johnthetubaguyright, hack the RD17:40
johnthetubaguylol SR17:40
*** derekh has quit IRC17:40
BobBallor just an other-config17:41
BobBallI think we can pass some iscsiadm flags through17:41
johnthetubaguyeven better17:41
BobBallnot 100% on that though.  Maybe only 73% sure.17:41
BobBallbtw john, my stuff on libvirt can wait until next week if we have other things to get through :)17:41
johnthetubaguyBobBall: thanks17:42
*** jog0 has joined #openstack-meeting17:42
*** rafaduran has quit IRC17:42
BobBalls1rp, Was saying to guitarzan that we'd like some of the XS logs in the bug report just for tracability if that's ok17:43
s1rpBobBall: cool, we can get those over to you; luckily this is very easy to replicate!17:44
johnthetubaguysounds good, any more on that one?17:44
BobBallno :) Let's leave that one for now17:45
johnthetubaguycan always take it to the ML17:45
johnthetubaguycool, bobball summit stuff you wanted to mention?17:45
BobBallUhhhh maybe?  I don't remember which summit stuff you're referring to?17:46
*** Gordonz_ has joined #openstack-meeting17:46
*** Gordonz_ has quit IRC17:47
johnthetubaguyok, missunderstood17:47
johnthetubaguyput stuff on the etherpad to help discuss at the summit17:47
*** garyk has joined #openstack-meeting17:47
*** Gordonz_ has joined #openstack-meeting17:47
BobBallSorry - I could have been clearer! :)17:47
johnthetubaguyassuming that session goes ahead, if there is loads, might ask for extra sessions17:47
BobBallSummit stuff then - looking forward to it.  matelakat and I have booked our flights so we'll see you there17:48
johnthetubaguysounds like a Xen on libvirt vs XenAPI disucssion might be good, as long as it says sensible and not too religious17:48
johnthetubaguyI was thinking in the summit17:48
johnthetubaguybut bob you wanted to bring that up this weel?17:48
johnthetubaguyweek?17:49
BobBallWell what I'd like to understand is what the primary value that the XenAPI integration is using from XAPI that can't be provided by libvirt17:49
*** koolhead17 has quit IRC17:49
BobBallnot sure if we've got enough time to explore that question properly today17:50
BobBallwhich is fine :)17:50
*** Gordonz has quit IRC17:50
*** markmcclain has joined #openstack-meeting17:50
s1rpwe do alot of weird stuff w/ dom0 plugins, but that probably could be handled with proper hooks in the libvirt layer17:50
johnthetubaguys1rp: we can't use both today, we would freak out xapi17:51
johnthetubaguybut yes, I get your point17:51
johnthetubaguyI think the question is, should we evolve XAPI/XCP or should we evlove libvirt17:52
johnthetubaguyand how much effort is each approach, at this point17:52
johnthetubaguyI guess what is missing between libvirt+Xen vs xapi+Xen in openstack today17:52
BobBallWell the question is more that there are lots of things that are getting first-dibs in libvirt and whether a libvirt-on-xen/xapi hybrid approach would bring us much and what level of pain it would be for XAPI to tolerate such a hybrid approach17:53
johnthetubaguyI get the idea that gap could be quite small, but I never got libvirt+Xen working that well, but didn't try very hard17:53
johnthetubaguyhmm, maybe17:53
*** mattray has joined #openstack-meeting17:53
johnthetubaguybut that is like how many years out?17:54
BobBallIt's not this week, that's true17:54
johnthetubaguywell, maybe that fits into evolving XAPI actually...17:54
johnthetubaguyI wondered about using xenopsd instead17:54
johnthetubaguythats the thing under xapi17:55
johnthetubaguyanyways, we can take this offline17:56
johnthetubaguyanything else?17:56
*** nati_ueno has joined #openstack-meeting17:57
johnthetubaguycool17:57
johnthetubaguy#endmeeting17:57
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:57
openstackMeeting ended Wed Mar  6 17:57:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:57
johnthetubaguythanks all17:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-03-06-17.01.html17:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-03-06-17.01.txt17:57
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-03-06-17.01.log.html17:57
*** sarob has joined #openstack-meeting17:57
*** jgallard has left #openstack-meeting17:58
*** koolhead17 has joined #openstack-meeting18:01
*** sarob has quit IRC18:02
*** sarob has joined #openstack-meeting18:04
*** johnthetubaguy has quit IRC18:06
*** otherwiseguy has quit IRC18:06
*** dscannell has quit IRC18:07
*** darraghb has quit IRC18:09
*** metral has quit IRC18:09
*** adjohn has joined #openstack-meeting18:10
*** dolphm has quit IRC18:10
*** dolphm has joined #openstack-meeting18:13
*** cschwede has joined #openstack-meeting18:16
*** dscannell has joined #openstack-meeting18:17
*** beagles is now known as beagles|brb18:17
*** cody-somerville has quit IRC18:21
*** bdpayne has quit IRC18:28
*** bdpayne has joined #openstack-meeting18:29
*** SergeyLukjanov has joined #openstack-meeting18:30
*** johnpur has joined #openstack-meeting18:31
*** adjohn has quit IRC18:32
*** adjohn has joined #openstack-meeting18:35
*** aabes has joined #openstack-meeting18:37
*** cody-somerville has joined #openstack-meeting18:38
*** aabes has left #openstack-meeting18:39
*** metral has joined #openstack-meeting18:40
*** adjohn_ has joined #openstack-meeting18:40
*** henrynash has joined #openstack-meeting18:41
*** beagles|brb is now known as beagles18:42
*** sdake has joined #openstack-meeting18:42
*** jjm3lp has quit IRC18:42
*** johnpur has quit IRC18:42
*** adjohn has quit IRC18:42
*** davidh_ has joined #openstack-meeting18:49
*** clayg has joined #openstack-meeting18:50
*** caitlin-nexenta has joined #openstack-meeting18:56
*** sarob has quit IRC18:58
notmynameswift meeting time19:00
swifterdarrello/19:00
torgomaticahoy19:00
notmyname#startmeeting swift19:00
openstackMeeting started Wed Mar  6 19:00:54 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: swift)"19:00
openstackThe meeting name has been set to 'swift'19:00
notmynamethe openstack grizzly release is coming up soon, so we'll spend some time on that today19:01
notmynamebut first, some general announcements19:01
*** dfg has joined #openstack-meeting19:01
notmyname#info reminder that the CFP for talks at the summit is open at summit.openstack.org19:02
notmynameI'm curious as to how many swift devs will be coming from RAX. any idea right now?19:03
notmynamedfg: have you heard anything?19:03
dfgya19:03
dfgremember anything- is the question :)19:04
notmynameheh19:04
*** cp16net is now known as cp16net|away19:04
davidh_Do we have a deadline for submitting items for discussion? Can it wait till end of next week?19:04
notmynameok. well, if you all aren't there, I'll go gripe at your managers (who will be there) ;-)19:04
dfgnotmyname: chuck, redbo, maybe glange19:04
notmynamedavidh_: I don't remember the deadline off the top of my head. I think you've still got time. I'll need to check with ttx19:05
notmynamedfg: k, thansk19:05
davidh_As this is my first sumit -  these are items for technical discussions right?19:06
notmynameas we get closer to the next swift release, please let me know if your email needs to change in the AUTHORS or .mailmap file. I'll be updating that soon. let me know via email, IRC, or with patches19:06
*** cp16net|away is now known as cp16net19:06
notmynamedavidh_: yes. these are intended to be more like facilitated discussions rather than official presentations19:06
davidh_notmyname: great19:06
notmynamedavidh_: presenting material is ok, but you should have a good chunk of time devoted to discussion19:07
*** henrynash has quit IRC19:07
davidh_np19:07
clayghi19:07
notmynamealso, if you haven't re-signed the oepnstack CLA, please do so ASAP. it's all done through gerrit now, and it should be much simpler (yay!)19:07
dfgnotmyname: are ther instructions somewhere?19:08
chmouelthere is a faq on the list that got posted19:08
chmoueli can forward it to you if you like19:08
chmoueldone19:08
notmynamechmouel: thanks (or paste a link here)19:08
dfgchmouel: that would be nice- i delete a lot of openstack stuff :)19:08
chmouelyeah i figured ;)19:09
notmynameeveryone needs to sign a CLA, even if you are also covered by a corporate one19:09
claygdfg: but you come to the meetings!  Should be easy to keep up with the important stuff...19:09
notmynamelast announcement: pycon starts next week (3/15) in Santa Clara. on monday 3/18 there is a swift sprint focused on building things for the swift API (ie apps). if you are going to pycon, try to stay around for the sprint too. we have fabulous prizes19:10
dfgclayg: thats why go to the meetings. hi back btw19:10
notmynameany questions so far? next topic is the swift 1.8 release19:11
chmouel#link Gerrir CLA faq http://pastie.org/private/hkpk4lxekjlnhxs3w53dww19:11
notmynamechmouel: thanks19:12
dfgchmouel: thx19:12
notmynamemoving on to the upcoming release19:12
notmyname#topic swift 1.8.0 for grizzly19:12
*** openstack changes topic to "swift 1.8.0 for grizzly (Meeting topic: swift)"19:12
notmynamethe official openstack grizzly release is april 419:12
notmynamewhich pretty much gives us the rest of this month to finalize and QA our release19:13
notmynamedfg: (since you're the only racker in here) can you confirm that y'all's QA will not be able to do a sign off by mid next week?19:13
dfgnotmyname: thats what i hear- they're being stretched pretty thin19:14
notmynameok19:14
dfgplus there's a lot of new stuff19:15
*** akuznetsov has joined #openstack-meeting19:15
notmynameso that means we will cut our 1.8.0~rc1 next wednesday (the 13th). QA (from all of us, including RAX) will have the rest of the month to validate it. when/if things are found, patches will be backported and ~rcX+1 releases will be made19:15
notmynameyes19:16
*** afazekas has joined #openstack-meeting19:16
notmynamethe sooner we have a QA signoff, the sooner we don't have to worry about maintaining the separate milestone-proposed branch19:16
chmouelwhen is the deadline for features to get merged?19:16
dfgnotmyname: if you hear a sneeze in the background in a few minutes- it was chuck19:16
dfg(sorry)19:17
creihtlol19:17
notmynamechmouel: I'll cut the release with ttx next wednesday19:17
chmouelnotmyname: ok thanks.19:17
notmynamechqyou have the advantage of being many time zones ahead of me :-)19:17
notmynamechmouel: ^19:17
notmynamedfg: :-)19:17
chmouelheh19:17
notmynamethere are 3 patches that I would like to see merged by the release (of course if a patch is proposed, its author wants it merged..)19:18
notmynamefirst, davidh_ wants https://review.openstack.org/#/c/23585/ reviewed and included if possible19:18
claygidk, sometimes I think redbo submits stuff that he doesn't acctually care if it gets merged...19:19
chmouelit would be nice for us if we can get the quota account patch get merged  as well https://review.openstack.org/#/c/23434/19:19
creihtclayg: hah19:19
notmynamesecond, there is the separate replication network patch https://review.openstack.org/#/c/19618/ that needs reviewed. I'd liek to see it merged, if possible19:19
notmynamechmouel: thanks. good to know19:19
notmynameand torgomatic has a patch that he'll submit (today?) that includes the region tier19:19
notmynameif you're wondering what patches to review first, please take a look at these 419:20
torgomaticI'll submit it as soon as its dependency clears Jenkins19:20
torgomaticSo between 10 and 10000 minutes from now ;)19:20
*** dhellmann is now known as dhellmann-afk19:21
notmynamedon't forget about python-swiftclient patches. closer to the grizzly date I'll cut a new release there too19:21
*** mattray has quit IRC19:21
tongli@torgomatic, sam, this one https://review.openstack.org/#/c/22569/19:21
*** gary_th has quit IRC19:21
tongliyou asked for it to be fixed. please review it. it is about the swift client busy-waiting fix.19:22
notmynameany questions about the swift 1.8.0 release or the schedule until 4/4?19:22
dfgnotmyname: btw- i'm just about done with static large update support for python-swiftclient19:22
notmynamedfg: cool19:22
notmynamedfg: I got to talk about that yesterday to someone who was visiting our office. he likes it :-)19:22
dfgnotmyname: i'll try to get in today so it can go out with the release i guess19:22
torgomatictongli: ok, I'll look at it soon19:22
dfgnotmyname: cool.19:23
tongliit will be nice to include that as well in the relase.19:23
notmynamedfg: no rush. the client release won't happen for another few weeks19:23
dfgok19:23
torgomaticAlthough the client follows its own release cycle, so it doesn't have this hard deadline19:23
notmynameif no questions about the 1.8.0 release, let's move on to a specific patch that needs some discussion19:23
chmouelyep client is easy :)19:23
tongli@notmyname, john, are you saying that swift and swift client releases are on different schedule?19:23
*** henrynash has joined #openstack-meeting19:24
chmoueltongli: everything openstack works like that19:24
notmynametongli: yes. they have a their own separate cadence (but in the case of the semi-annual openstack releases, it's nice to have them close)19:24
tongliok19:24
notmyname#topic endpoints patch19:24
*** openstack changes topic to "endpoints patch (Meeting topic: swift)"19:24
swifterdarrellSo I asked for this to be brought up...19:25
*** gary_th has joined #openstack-meeting19:25
notmynamea patch has been proposed that adds the funtionality to get the storage nodes for an object: https://review.openstack.org/#/c/21015/19:25
swifterdarrellI'm happy with including it, but thought it was worth discussing one more time the criteria for inclusion in "core swift" for middleware19:25
notmynamethe question came up: "if this is included, why not swift3?"19:25
chmouelswift3 is basically a screenscraping of an api19:26
davidh_This patch allows a client to know on which nodes his data is right?19:26
chmouelit's not really maintainable compared to the endpoint listing IMO19:26
notmynameI've not heard anything say that this endpoints patch is bad functionality, but I think the question is more about if it should be in core (right swifterdarrell?)19:26
torgomaticThis is a reasonable extension to the swift API, while  swift3 implements a different API with the same functionality19:26
torgomaticThat's why, IMHO19:26
creihtdavidh_: this is needed for hadoop functionality to run on top of swift19:27
swifterdarrellnotmyname: correct, and I'm not even trying to argue that it shouldn't be in core (I did +2 it at one point, after all)19:27
davidh_This patch is problematic - as it exposes internal info out19:27
creihtnotmyname: yeah I don't see why to not include it19:27
notmynameI agree, re swift3: the S3 api is a separate (closed) api, and we've rejected other things like that too (*wink* tongli)19:27
creihtdavidh_: it is optional19:27
davidh_There should be a way for haddop to get the info - but there shouldnt be a way for a regular client to get that info19:27
tongli@notmyname, that is right john,19:28
torgomaticAlso it is sufficiently generic that any app that bypasses the proxy can use it; its not hadoop specific19:28
claygcreiht: it's only "optional" until clients start depending on it19:28
davidh_creiht: than its less of an issure19:28
cschwedemaybe limit the info to configurable client ips?19:28
creihtclayg: how would a client depend on it?19:28
davidh_Default should be not to offer this service19:28
claygcreiht: a map reduce client?19:28
caitlin-nexentaHow could a client *ever* depend on it. The set of servers that an object is stored upon is subject to change without notice.19:29
notmynamecaitlin-nexenta: a client could depend on the info, not what the info is19:29
caitlin-nexentaIt's useful information, but you could never *rely* on an answer.19:29
*** sarob has joined #openstack-meeting19:29
claygsorry, client may have been the wrong term, a service that is using this info to implement it's funtionality19:29
chmouelcaitlin-nexenta: i think they are talking about providing an api contract19:29
davidh_It assumes that the haddop is running on the same servers right?19:29
claygit's api access to the ring19:29
notmynameit's more general than hadoop. it's..ya, what clayg jsut said19:30
claygwhy expose it all if NO ONE can use or depend on it19:30
claygneway, I think it's great, different than s319:30
davidh_clayg: why do we need to offer an API access to the ring19:30
claygI just think it's a paper tiger argument to keep calling api expansion "optional"19:30
cschwedemight be useful for a future erasure coding implementation as well (have to think about it)19:30
swifterdarrellOkay, so the criteria for middleware inclusion is something like A) adds something (presumably useful) to the Swift API, and B) does not implement a different API than the Swift API?19:31
claygdavidh_: I didn't write it, but the gneral idea is that stuff can do cleaver things running on the nodes, and if it has to first write a native binding to the ring structure (which may change) then it's a barrier to entry19:31
notmynameswifterdarrell: well, there's also the "do the core devs want to maintain it"19:32
clayglol19:32
claygthat's the only one that matters19:32
claygsorry, bad joke19:32
*** akuznetsov has quit IRC19:32
*** rj_ has quit IRC19:32
dfgits not a lot of code19:32
cschwededo the core devs maintain all patches from contributors?19:32
creihtnotmyname: so if you go down this route, then do you plan to do the same with the rest of the middleware?19:32
claygcschwede: only if they break or if we need to change something they use19:32
davidh_This exposes internal data out - does not make sense -  if it is used only by internal elements - we need to offer an internal API - not one that can be used by a client19:33
notmynamecreiht: we tried that already :-)19:33
creihtlike for example the domain remap/cname stuff?19:33
creihtdavidh_: From their description the purpose would be to run on a proxy that is only running internally19:33
claygdavidh_: I think there's a class of "services" that will run "in cluster" which can make use of ring information directly19:33
*** caitlin-nexenta has quit IRC19:33
swifterdarrellbtw, IIRC, the "why" of this was discussed at the patch by the actual author19:34
creihtswifterdarrell: correct19:34
creihtthey need the info for their hadoop integration19:34
SergeyLukjanovthis feature will provide an ability to run "in cluster" services using "data locality"19:34
davidh_Using the ring directly is fine  as long as it uses the Ring.py or some CLI that uses Ring.Py19:34
*** AlexanderKuznets has joined #openstack-meeting19:35
dfgi think its simple and generic enough to be useful to a bunch of different applications. also serves as an example of how you can do stuff like this.  i don't think the swift3 is a good comparison. what's the problem with it?19:35
torgomaticalso, it's as close to disabled-by-default as any middleware can be, in that it's not in the sample config's middleware pipeline19:35
swifterdarrellPersonally, I'm not interestedin a discussion of the merits of the patch for its intended purpose.  I care more about whether it's fine to include it in core and what the criteria for that are.19:35
*** caitlin-nexenta has joined #openstack-meeting19:35
swifterdarrellSo notmyname, you mentioned that core-dev interest in maintenance is a pre-req to middleware inclusion?19:36
creihtwell there isn't any official criteria that I am aware of19:36
creihtso are you proposing that we define it?19:36
swifterdarrellcreiht: correct19:36
claygi feel like swifterdarrell wants to try out the vote fucntion in this meeting thing...19:36
torgomaticswifterdarrell: I think what you said earlier are good criteria, FWIW.19:36
dfgplease lets not try to make one ;)19:36
creihtlol19:36
notmynameswifterdarrell: it's an implicit one, I think. your list earlier is good too19:36
torgomaticalthough there's some official OpenStack thingy saying you can't implement third-party APIs unless you're Nova19:37
notmynamethe only real criteria there is right now is that we have one officially supported API (eg we wont' include S3 or CDMI in core)19:37
swifterdarrellI don't care if it's "official"19:37
creihttorgomatic: no that is up to the project to decide on 3rd party apis19:37
*** jog0_ has joined #openstack-meeting19:37
*** gary_th has quit IRC19:37
torgomaticcreiht: ah, I misunderstood then19:37
claygwhy do we need to "define the critera" if we can change them on a case by case basis... if it's just a question of posting a "guideline" somewhere we can point contributers to so they know our currently line of thinking... let's just put what swifterdarrell said in the sphinx docs under "contributing"19:38
creihtto which we did decide to not include 3rd party apis19:38
notmynamecreiht: actually, torgomatic is right19:38
creihtoh did they change that again?19:38
notmynamecreiht: ya, while you were off being a manager ;-)19:38
creihtheh19:38
*** jog0 has quit IRC19:38
*** jog0_ is now known as jog019:38
davidh_Regardless of maintainance - the problem is not with what this patch wish to achieve  - it is with the how  - it should preferably not be an external API.19:38
*** johnpur has joined #openstack-meeting19:39
tongliI think that patch should be in is because it enables swift to serve the purpose that is important now and in future.19:39
notmynameok, so to summarize: there is no official requirements for inclusion in core other than it's got to be a good patch and can't implement a 3rd party API19:39
creihtdavidh_: so you suggest that we should have an official java api for the ring then?19:39
dfg2 core-devs approval means core-devs are willing to support it. i'll look at it again later and approve it. if someone else agrees- done.  what's wrong with that? any kind of official criteria can be put off til needed. cause it will be a pain19:39
swifterdarrellsounds great; so there's no prob w/this patch or the account quota19:39
creihtor insert favorite language19:39
torgomaticnotmyname: agreed 100%19:39
swifterdarrellwe done with this topic?19:39
swifterdarrell:)19:39
notmynamedavidh_: that discussion should be taken to the review19:39
tongliif someone wants to use swift for hadoop, then they can.19:39
davidh_creiht: we will have (already have) a python one - if someone would convert it to a Java one - he can use it19:40
claygdavidh_: until we change the ring - then he has to fix it19:40
swifterdarrelldfg: agreed19:40
creihtthat's the problem is that it isn't trivial, and possibly very error prone19:40
davidh_notmyname: ok.19:40
creihtand the reason he wanted to expose it as an api19:40
notmynameswifterdarrell: ya, I think we're done with this. you can move forward on your review now :-)19:41
clayg... so we DON'T get to use the vote feature :'(19:41
swifterdarrellsweet19:41
*** pnavarro1 has quit IRC19:41
swifterdarrellclayg: sorry :)19:41
notmyname#topic general discussion19:41
creiht#vote no to bringing it to a vite19:41
*** openstack changes topic to "general discussion (Meeting topic: swift)"19:41
notmynameanything else?19:42
creihtvote even19:42
creiht:)19:42
claygobject-replicator-2 looks pretty sweet19:42
notmynameI wanted to ask gholt about a blueprint he has...19:42
notmynameya that one19:42
notmynamebut he's not here (and it's not time critical)19:42
creihtI'm sure it will solve world hunger ;)19:42
clayglast I checked there wasn't a sqlite schema, but the native rest calls where starting to form up19:42
notmynameok, let's call it. thanks for your time today19:43
davidh_clayg: does replicator-2 uses rsync or just PUT?19:43
notmyname#endmeeting19:43
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:43
openstackMeeting ended Wed Mar  6 19:43:45 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-03-06-19.00.html19:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-03-06-19.00.txt19:43
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-03-06-19.00.log.html19:43
notmynamedavidh_: ah, sorry. (and I don't know. gholt seems to be writing it)19:44
*** dfg has left #openstack-meeting19:44
creihtdavidh_: I think the last he was testing with, it uses straight PUT19:44
*** caitlin-nexenta has quit IRC19:44
creihtbut I haven't talked to him about it recently19:44
torgomaticdavidh_: code's here https://github.com/gholt/swift-object-replicator219:44
torgomaticI haven't read it enough to answer your questions though19:44
creihtlooks like right now it is configurable to use either19:45
*** clayg has left #openstack-meeting19:47
*** AlexanderKuznets has quit IRC19:49
*** dhellmann-afk is now known as dhellmann19:52
*** asalkeld has quit IRC19:54
*** asalkeld has joined #openstack-meeting19:54
*** zbitter has joined #openstack-meeting19:58
*** shardy has joined #openstack-meeting19:59
*** SpamapS has joined #openstack-meeting19:59
sdake#startmeeting heat19:59
openstackMeeting started Wed Mar  6 19:59:30 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
sdakesteak here19:59
shardyshardy here19:59
SpamapSspam here19:59
asalkeldhere20:00
jpeelerhere20:00
*** cschwede has left #openstack-meeting20:00
zbittero/20:00
*** zbitter is now known as zaneb20:01
sdakeok lets get rolling20:01
sdake#topic bugs20:01
*** openstack changes topic to "bugs (Meeting topic: heat)"20:01
sdakeon the project planning meeting, got the message that we need to have our buglist at zero20:01
sdakethen we release rc120:01
sdakeso i'll go through the bugs that don't have activity on them20:02
sdakehttps://bugs.launchpad.net/bugs/112848620:02
uvirtbotLaunchpad bug 1128486 in heat/grizzly "creating a stack without a required param, fails correctly but leaves the stack created" [High,New]20:02
sdakethis almost seems critical to me...20:02
asalkeldthat was mine20:03
sdakeokie i'll assign you20:03
zanebis this just due to rollback not being the default any more?20:03
asalkeldit was a while back20:04
asalkeldI'll need to retest20:04
stevebakerhere!20:04
SpamapSIf anybody is overwhelmed I have cycles for bug fixes20:04
SpamapSJust been focused on testing and planning lately.20:04
sdakehttps://bugs.launchpad.net/bugs/107294920:05
uvirtbotLaunchpad bug 1072949 in heat/grizzly "Reset DB migrations" [Critical,Triaged]20:05
*** bdpayne has quit IRC20:05
zanebstarted investigating20:05
sdakespamaps we can use help in reviews ;)20:05
SpamapSSeems to me like the Low's should just be dropped from rc120:05
sdakereviews piling up20:05
SpamapSsdake: roger that20:05
zanebI actually think DB migrations is not as high a priority as I first thought; it shouldn't break existing users20:06
sdakeatm we only have 5 bugs and have until 20th20:06
sdakesuggest high prio then?20:06
sdake(rather then critical)20:06
*** bdpayne has joined #openstack-meeting20:06
zanebsure20:06
SpamapShttps://launchpad.net/heat/+milestone/grizzly-rc1 says rc1 is the 14th btw20:07
*** henrynash has quit IRC20:07
zanebI see nova have moved to a different tool altogether and I'm kinda envious ;)20:07
sdakehttps://bugs.launchpad.net/bugs/113597020:07
uvirtbotLaunchpad bug 1135970 in heat "--timeout doesn't work for heat-boto" [Medium,Triaged]20:07
zanebit can generate the migrations for you20:07
sdakeya, i'd like it to be 14th :)20:07
sdakebut 20th is drop dead date20:07
shardysdake: I'm on that, simple fix20:07
shardyprobably get it done tomorrow20:08
sdakehttps://bugs.launchpad.net/bugs/115009120:08
uvirtbotLaunchpad bug 1150091 in heat "API policy debug logging is too noisy" [Low,Triaged]20:08
shardyditto20:08
sdakehttps://bugs.launchpad.net/bugs/110210120:08
uvirtbotLaunchpad bug 1102101 in heat/grizzly "--host option to heat-boto is ignored" [Low,Triaged]20:08
shardylikewise.. :)20:08
sdakeshardy superman for rc1 ;)20:09
sdakeok, rest look like they are in progress with patches queued up20:09
shardythese ones are really simple fixes, I've just prioritized the more serious problems20:09
sdakeremember, put a bug and the bug number for fixes for rc1 in the changelogs20:09
*** vipul is now known as vipul|away20:09
*** vipul|away is now known as vipul20:09
sdakeare there any outstanding bugs not in the bug tracker people are aware of?20:10
shardysdake: I found an issue with update today, bug pending20:10
sdakeok20:10
SpamapSI've been testing a lot, spinning up nested stacks and stuff.. it all seems to be working quite well.20:10
sdakefor the next week if your not working on bugs recommend running heat manually make sure there aren't bugs our test cases don't catch20:11
sdakeand once bug count hits zero, i'll do rc1 release20:11
sdake#topic new core members20:11
*** openstack changes topic to "new core members (Meeting topic: heat)"20:11
sdakeevery 6 months, we should select new core members for heat20:12
sdake(ie before summit)20:12
sdakecore gives folks the rights to +2 a patch or approve a patch20:12
asalkeldhopefully a bit more dynamic than that20:12
sdakewell atleast every 6 months ;)20:12
asalkeldif I get stuck into heat, I might have to wait 5 months to get into core?20:13
sdakelet me rephrase, few weeks prior to summit, we should consider the candidates20:13
asalkeldI think it shoud be continous20:13
sdakethink a few months wfm20:13
sdakewan't to make sure core members are really ready to commit to that20:13
sdakein my mind the criteria are20:13
sdake1) understand code base20:13
sdake2) have some level of reviews in the system20:13
sdake3) participate in irc on #heat channel20:14
sdake4) submit patches20:14
asalkeldbut none of that takes 6 months to prove20:14
sdakewith #4 being less of a concern then others20:14
sdakei agree20:14
sdakeI said few months..20:14
asalkeldweeding out could be every 6 months20:14
asalkeld(removing from core)20:14
*** dscannell has quit IRC20:14
SpamapSPerhaps its just something people can bring up at any meeting if they feel a candidate is ready for core status?20:14
asalkeld+120:15
sdakeya, if you have a candidate for submission and your core send it my way and I'll put on submission20:15
*** dscannell has joined #openstack-meeting20:15
sdakefor this cycle Spamaps seems like a good core candidate20:15
SpamapSIf there's a quorum of core people, a vote can be taken, and done in any meeting, right?20:15
sdakeso I'll send his name to the list and get a +1/0/-1 vote from folks in core20:15
SpamapSsdake: :) thank you.20:15
sdakewould rather do on mailing list20:15
sdakeanyone have suggestions for other core members20:16
SpamapSsure, ML is even more dynamic actually :)20:16
sdakewe have a few patches from other folks but not much patch review or irc participation20:16
sdakeso unless I'm missing someone I'll move on ;)20:17
sdake#topic plugin interface20:17
*** openstack changes topic to "plugin interface (Meeting topic: heat)"20:17
sdakethere was a review that zaneb spawned which generated some controversy around plugin api lockdown20:17
sdakei think we had some disjointed conversations about it but it is worth discussing in one place20:18
sdakezaneb care to restate your thoughts on that20:18
zanebI think the conclusion we came to is that we would not freeze the plugin api until Havana?20:19
asalkeldwhat is the "policy" with drivers in say quantum20:19
asalkeldre: stability20:19
sdakegood question20:19
SpamapS+1 from me, there aren't very many plugins, and if there are, they're likely nascent20:19
asalkeldI suspect only on stable branches20:19
SpamapSso freezing this early would possibly miss some needs that early plugin devs will find as grizzly sees use20:19
*** henrynash has joined #openstack-meeting20:20
sdakeok well seems to me freezing in havana makes sense20:20
asalkeld(on the stable branch)20:20
asalkeld?20:20
sdakeafter we have sorted out parallel launch20:21
stevebakerI think we should encourage plugins to be developed in tree at this point, the carrot is that we will take the burden of updating for api changes20:21
SpamapSIt would be great to make an effort to not break backward compatability w/ grizzly if at all possible... but better to break it in Havana and never again than miss important pieces20:21
shardyYeah, only freeze the stable branch, versioned per major release IMO20:21
sdakeyes we had talked about adding a version to the plugins20:21
sdakeso the engine could work with older plugins20:21
sdakeif ver = 1 do x if ver =2 do y20:21
zanebversioning sounds like a bag of hurt to me20:21
zanebdo people have suggestions of how to do it?20:22
asalkeld-1 to versioning20:22
sdaketheoretically heat is perfect so no need to update the version :)20:22
SpamapS:)20:22
SpamapSI prefer API's that only move forward with new aspects, rather than version themselves aggressively20:23
shardyI don't really get why we're making plans to freeze this interface now, I mean we've had very few users asking about custom resources in #heat20:23
sdakewell we are not freezing in g20:23
sdakethe proposal was to freeze in h20:24
shardywhich I assume means most people are only using the internally defined resources, so we can keep changing it until people start making significant use of the plugin capability20:24
asalkeldshardy, not everyone will tell us20:24
SpamapSshardy: I look at what will happen if, say, HP Cloud or Rackspace deploy heat.. they'll want to plugin to things that are specific to their clouds with plugins that are not public at all.20:24
*** vipul is now known as vipul|away20:24
shardysdake: I guess I'm saying I don't see the motivation behind committing to that, when the interface is still maturing (as evidenced by the discussion today re zaneb's patch)20:24
sdakei'll shoot a mail to Dan ask him what they are doing with quantum20:25
SpamapSshardy: if the API is unversioned but also stays backward compatible with havana's API.. there will be nothing but happy heat users. If old versions start getting dropped.. there will be sad heat users.20:25
zanebshardy: people will stop following trunk once we have a proper grizzly release out there20:25
shardySpamapS: Yep, but they will have to re-test those in-house plugins every major release anyway, so would it be a huge problem if there are clearly documented interface tweaks between major releases occasionally?20:25
zanebshardy: we may not have time to react20:26
zanebbut I am still find with holding off until havana20:26
*** dwcramer has joined #openstack-meeting20:26
SpamapSshardy: no its not a problem at all. I'm suggesting simply that the less backward compatibility breakage allowed, the less important versioning becomes.20:26
sdakein h3 we will have to make a decision about versioning the api20:26
SpamapSand yes, I think we can table this until havan20:26
SpamapSa20:26
SpamapShrm20:26
SpamapSperhaps we should start a discussion before h3?20:27
shardyOk, I guess I'm saying I support stability of the interface, but not at the expense of subsequent innovation (implied by the "frozen forever" idea)20:27
sdakeso lets put it off until then20:27
zanebshardy: +120:27
zanebI don't think anyone is talking about frozen forever20:28
asalkeldzaneb, converting instanceGroups into a stackedResource would make that change large not needed20:28
SpamapSno not frozen forever. "BC breaks discouraged".20:28
zanebthe discussion was sparked by "breaking changes that we know already might be on the horizon"... it's always good to get those in early20:28
SpamapSRight, especially when the impact will be almost nil.20:29
shardyOk, provided we have some flexibility for future changes then all good :)20:29
sdakeyes, I think we don't know what that should be tho from the debate on the patch in question20:29
zanebso, for the patch in question, the breaking change was adding a parameter to check_active()20:29
zanebthere are a bunch of ways to fix that20:30
*** adjohn_ has quit IRC20:30
zaneb1) just document now that people should expect there may be parameters in the future20:30
sdakei'd rather not change the api at this point in the release20:30
zaneb2) do introspection on the method before calling it to see how many parameters it takes20:30
asalkeldurg20:30
asalkeldmore complexity20:31
zanebbut if we _know_ we want to change it, better to do so now20:31
*** mkollaro has quit IRC20:31
zanebthere's no consensus for change though, so I'm happy to delay20:31
sdakei'm not convinced we know *how* we want to change it20:31
*** henrynash has quit IRC20:31
zanebright20:31
zanebI know how I want to change it, and everybody else disagrees ;)20:31
asalkeldalso when/if the rackspace get stuck in20:31
zanebbut that's fine20:32
sdakeok all done with that topic then ?20:32
asalkeldya20:32
sdake#topic open items20:32
*** openstack changes topic to "open items (Meeting topic: heat)"20:32
sdakesummit proposals for heat20:33
stevebakerheat-cfntools should be in gerrit any second now, so expect some review requests20:33
sdakeif you have them, submit them ;)20:33
sdakenice work there stevebaker20:33
SpamapScool20:33
shardystevebaker: I made a pull request today, do I need to gerrit-ify it?20:33
stevebakershardy: yeah, I've got a pull request that I'll withdraw too20:33
shardyok, cool20:34
shardysdake: re summit, I was going to propose a design session to revisit the in-instance credentials issue20:34
shardywhere do I propose it?20:34
sdakeshardy sounds good20:34
SpamapSshardy: +120:34
sdakehttp://summit.openstack.org/20:35
SpamapSI'm also keenly interested in the possiblity of per-instance metadata for instance groups20:35
sdakepush the suggest ession button20:35
SpamapSsomething I've only recently figured out I probably need20:35
asalkeldso trusts are in, do we want to make use of them now?20:35
SpamapScan perhaps fold it into the rolling updates session, but that seems like it will be quite a full discussion20:35
shardysdake: ok, I'll add a suggestion, thanks20:36
sdakeif by now, you mean havana, possibly20:36
asalkeldsince they were put in for us20:36
SpamapSasalkeld: probably worth investigation in that session yeah20:36
shardyasalkeld: they don't solve the in-instance problem, but might help with the stored context problem20:36
asalkeldagree20:36
asalkeldbut for the cloud watch poller20:36
sdakeone thing that came up re openshift integration that kraman is doing20:36
sdakeis a method for autoscaling to be triggered by the application itself20:37
SpamapSdo people feel like per-instance metadata for groups is a thing we can discuss? I'll put together a proposal spec and everything.20:37
sdakerather then infrastructure outside20:37
shardyYep, I'll add usage of trusts to the authentication-way-forward session proposal20:37
sdakespamaps ack20:37
sdakeasalkeld you have any thoughts on app triggered scaling20:37
zanebSpamapS: AutoscalingGroups or InstanceGroups?20:37
SpamapSzaneb: InstanceGroups20:37
zanebcool20:38
SpamapSzaneb: specifically, I want to provide them with per-instance credentials to a database and a queue system.20:38
asalkeldzaneb, SpamapS just use nested stacks20:38
shardySpamapS: The main thing I'm not sure on is the interface, since the interfaces share a launch configuration, meaning you can't define the metadata update via UpdateStack20:38
shardybut happy to discuss it so we can work out a solution ;)20:38
SpamapSshardy: yeah thats the bit that needs some thought, and I'm willing to design that if you guys think its not totally insane. :)20:38
asalkeldsdake I'll need to think that through20:39
SpamapSI do have some ideas for combining LaunchConfiguration with WaitCondition20:39
sdakeasalkeld can you think about it and shoot me an email ;)20:39
SpamapSbut, lets not design it in here :)20:39
shardySpamapS: As asalkeld says, a possibly easier solution would be nested stacks, with the nested template effectively defining the InstanceGroup20:39
asalkeldyip20:40
SpamapShm20:40
SpamapSyou're basically saying give each one an Instance resource?20:40
asalkeldyes20:40
SpamapSthats my workaround currently.20:40
shardyyep20:40
SpamapSbut then that plays poorly with rolling updates.20:40
shardybut in a nested template20:40
asalkeldhow so20:41
SpamapSas I end up having to build rolling updates using WaitConditions.. which.. will work, but seems inelegant and crude.20:41
asalkeldwell we can talk at summit about that20:41
SpamapSexactly20:42
zanebidea of per-instance metadata sounds fine for InstanceGroups if you can find a sane interface20:42
shardy+120:42
* SpamapS will propose a session and send a ML post with a draft proposal20:42
zanebfor AutoscalingGroups we should stick to the AWS interface IMO20:42
SpamapSzaneb: +1, lets not break AWS for my crazy use cases. :)20:42
asalkeldzaneb, for sure - more ment to use the resourcestack class20:43
SpamapSbtw CloudFormation added rolling updates to autoscaling groups in case anybodymissed that20:43
asalkeldyea, they are sneaking features out all the time20:43
asalkeld(just like us)20:44
sdakeok anything else?20:44
shardyI have another item re template format20:44
sdakeshoot20:44
shardyI was asked if we plan to stick with the AWS templates, or if we are working towards supporting some "openstack blessed" more open template syntax20:45
sdakeasked by who?20:45
asalkeldmany ask that20:45
sdakenobody has proposed a new template format20:46
shardyI know near-term we'll stick to CFN/yaml, but do we have a longer term objective to support something else, if so is there a viable alternative?20:46
sdakethat is what summit submissions are for20:46
SpamapShttp://summit.openstack.org/cfp/details/78  btw20:46
zanebdifferent != better20:47
SpamapSshardy: I think it would be a fundamental change for little gain.20:47
zanebI would happily entertain any suggestions for a better template format20:47
shardyOk, I just wanted to see if anyone had any thoughts on the matter20:47
stevebakerI'm thinking incremental improvements at the moment20:47
*** gary_th has joined #openstack-meeting20:47
SpamapSI definitely can see wanting to get away from potential trademark infringement by removing AWS/EC2/S3/etc. though20:47
sdakemy thought is if someone wants to add a new template format, they will submit a talk at openstack summit20:48
zaneball I hear is suggestions for a different template format, with no justification except that it can be incompatible20:48
stevebakerSpamapS: yes, a full suite of native resources should be on the plan20:48
zanebas if that were a good thing20:48
* stevebaker ponders ansible integration20:48
*** henrynash has joined #openstack-meeting20:48
sdakenew shinies !20:48
sdakeok20:48
sdakewell I'd like to wrap up20:48
*** ayoung is now known as ayoung-afk20:48
sdake#topic agenda setting20:48
*** openstack changes topic to "agenda setting (Meeting topic: heat)"20:48
SpamapSThe template format, sans amazon trademarks, is up for discussion as a way to express the full deployment of OpenStack20:48
sdakewe have alot of stuff in the open discussoin session that should be on the agenda20:49
sdakeI'm guilty as everyone else ;)20:49
SpamapSgood point sdake20:49
*** koolhead17 has quit IRC20:49
*** henrynash has quit IRC20:49
sdakebut in the future, if you could add your topics to the agenda it may help the meeting avoid some crosstalk20:49
*** henrynash has joined #openstack-meeting20:49
sdake#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda20:49
sdakeadd right under "Open Discussion"20:49
sdakesorry right above20:50
shardysdake: yeah, sorry, my topic came up late in the day20:50
sdakenp20:50
shardys/topic/question20:50
sdakefeel free to add before meeting and if we can get to it we will20:50
sdakeok thanks20:50
sdakeremember, march 14th would like all the buggies fixed 20th latest20:50
sdake#endmeeting20:51
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:51
openstackMeeting ended Wed Mar  6 20:51:00 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-03-06-19.59.html20:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-03-06-19.59.txt20:51
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-03-06-19.59.log.html20:51
*** vkmc has joined #openstack-meeting20:53
*** dolphm has quit IRC20:54
*** radez is now known as radez_g0n320:57
*** shardy has left #openstack-meeting20:57
*** adjohn has joined #openstack-meeting21:00
*** fifieldt_ has joined #openstack-meeting21:03
*** dwcramer has quit IRC21:03
*** john5223 has quit IRC21:05
*** adjohn has quit IRC21:06
*** dwcramer has joined #openstack-meeting21:06
*** dprince has quit IRC21:09
ttxdavidh_: you've got plenty of time. Like until the end of the month21:15
ttxcc: notmyname ^21:15
*** metral has quit IRC21:16
notmynamettx: thanks21:22
*** tomoe_ has quit IRC21:24
*** tomoe_ has joined #openstack-meeting21:25
*** adjohn has joined #openstack-meeting21:26
*** vipul|away is now known as vipul21:27
*** novas0x2a|laptop has joined #openstack-meeting21:27
*** tomoe_ has quit IRC21:29
*** henrynash has quit IRC21:30
*** otherwiseguy has joined #openstack-meeting21:36
*** diogogmt has quit IRC21:38
*** annegentle has quit IRC21:39
*** diogogmt has joined #openstack-meeting21:41
*** henrynash has joined #openstack-meeting21:42
*** ayoung-afk is now known as ayoung21:43
*** markmcclain has quit IRC21:44
*** annegentle has joined #openstack-meeting21:45
*** metral has joined #openstack-meeting21:47
*** metral has quit IRC21:51
*** annegentle has quit IRC21:51
*** alaski_ is now known as alaski21:53
*** SergeyLukjanov has quit IRC21:53
*** SergeyLukjanov has joined #openstack-meeting21:55
*** maoy has joined #openstack-meeting21:57
*** maoy has quit IRC21:59
*** maoy has joined #openstack-meeting21:59
*** markwash has joined #openstack-meeting22:14
*** SergeyLukjanov has quit IRC22:15
*** metral has joined #openstack-meeting22:15
*** markwash has quit IRC22:19
*** esker has quit IRC22:25
*** dscannell has quit IRC22:25
*** markwash has joined #openstack-meeting22:26
*** dscannell has joined #openstack-meeting22:27
*** markmcclain has joined #openstack-meeting22:28
*** afazekas has quit IRC22:32
*** tomoe_ has joined #openstack-meeting22:33
*** dscannell has quit IRC22:33
*** johnpur has quit IRC22:34
*** johnpur has joined #openstack-meeting22:35
*** vipul is now known as vipul|away22:35
*** chmouel has quit IRC22:35
*** sarob has quit IRC22:41
*** sarob has joined #openstack-meeting22:41
*** mtreinish has quit IRC22:41
*** pony has joined #openstack-meeting22:43
davidh_ttx, thans22:44
*** chmouel has joined #openstack-meeting22:44
davidh_thanks22:44
*** dontalton has quit IRC22:45
*** dontalton has joined #openstack-meeting22:46
*** Gordonz_ has quit IRC22:50
*** tongli has quit IRC22:52
*** topol has quit IRC22:54
*** ryanpetrello has quit IRC22:55
*** vipul|away is now known as vipul22:57
*** hemnafk is now known as hemna22:57
*** dwcramer has quit IRC22:58
*** lbragstad has quit IRC22:59
*** sdake_ has quit IRC23:07
*** sdake_ has joined #openstack-meeting23:07
*** sandywalsh has quit IRC23:08
*** sdake_ has quit IRC23:09
*** sdake_ has joined #openstack-meeting23:09
*** eharney has quit IRC23:14
*** cp16net is now known as cp16net|away23:17
*** cp16net|away is now known as cp16net23:21
*** vkmc has quit IRC23:26
*** sandywalsh has joined #openstack-meeting23:28
*** markmcclain has quit IRC23:30
*** markmcclain has joined #openstack-meeting23:33
*** hemna is now known as hemnafk23:33
*** woodspa has quit IRC23:34
*** fnaval has quit IRC23:35
*** henrynash has quit IRC23:42
*** diogogmt has quit IRC23:43
*** gary_th has quit IRC23:45
*** henrynash has joined #openstack-meeting23:46
*** dhellmann is now known as dhellmann-afk23:51
*** henrynash has quit IRC23:52
*** fnaval has joined #openstack-meeting23:53
*** fnaval has quit IRC23:53
*** fnaval has joined #openstack-meeting23:54

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