Wednesday, 2013-04-03

*** john5223 has joined #openstack-meeting00:02
*** jog0 has quit IRC00:06
*** dwcramer has joined #openstack-meeting00:06
*** lloydde has quit IRC00:06
*** ladquin has quit IRC00:06
*** bdpayne has quit IRC00:07
*** ladquin has joined #openstack-meeting00:08
*** rmohan has quit IRC00:08
*** rmohan has joined #openstack-meeting00:08
*** anteaya has left #openstack-meeting00:09
*** ladquin has quit IRC00:11
*** danwent has joined #openstack-meeting00:14
*** ladquin has joined #openstack-meeting00:14
*** salv-orlando has quit IRC00:17
*** donaldngo_hp has quit IRC00:18
*** maoy has joined #openstack-meeting00:20
*** ladquin has left #openstack-meeting00:20
*** maoy has quit IRC00:21
*** salv-orlando has joined #openstack-meeting00:21
*** salv-orlando has quit IRC00:23
*** colinmcnamara has quit IRC00:25
*** mrodden has quit IRC00:30
*** dhellmann has quit IRC00:32
*** dhellmann has joined #openstack-meeting00:37
*** asalkeld has quit IRC00:50
*** asalkeld has joined #openstack-meeting00:54
*** zhuadl has quit IRC00:54
*** MarkAtwood has quit IRC01:00
*** beagles_back_l8r is now known as beagle01:04
*** beagle is now known as beagles01:04
*** Mandell has quit IRC01:13
*** matiu has joined #openstack-meeting01:15
*** matiu has joined #openstack-meeting01:15
*** vipul is now known as vipul|away01:17
*** vipul|away is now known as vipul01:19
*** gongysh has joined #openstack-meeting01:21
*** uramanan has joined #openstack-meeting01:21
*** anilkb has joined #openstack-meeting01:23
*** shang has joined #openstack-meeting01:31
*** colinmcnamara has joined #openstack-meeting01:35
*** krtaylor has joined #openstack-meeting01:36
*** colinmcnamara has quit IRC01:36
*** dwcramer has quit IRC01:42
*** sdake_ has quit IRC01:43
*** cdub_ has joined #openstack-meeting01:43
*** MarkAtwood has joined #openstack-meeting01:46
*** anilkb has quit IRC01:52
*** dwcramer has joined #openstack-meeting01:58
*** dhellmann is now known as dhellmann-away01:59
*** mfaraji has joined #openstack-meeting01:59
*** jaypipes has quit IRC01:59
*** beagles has quit IRC02:02
*** adalbas has quit IRC02:06
*** sdake_ has joined #openstack-meeting02:09
*** danwent has quit IRC02:15
*** vkmc has quit IRC02:17
*** colinmcnamara has joined #openstack-meeting02:19
*** novas0x2a|laptop has quit IRC02:22
*** reed has quit IRC02:23
*** tomoe_ has joined #openstack-meeting02:29
*** fnaval has joined #openstack-meeting02:38
*** rmohan has quit IRC02:39
*** rmohan has joined #openstack-meeting02:39
*** yaguang has joined #openstack-meeting02:43
*** colinmcnamara has left #openstack-meeting02:45
*** ivasev has joined #openstack-meeting02:46
*** mscott has joined #openstack-meeting02:51
*** sandywalsh has quit IRC02:51
*** cdub_ has quit IRC02:52
*** colinmcnamara has joined #openstack-meeting02:52
*** cdub_ has joined #openstack-meeting02:56
*** Mandell has joined #openstack-meeting02:59
*** cdub_ has quit IRC03:05
*** mscott has quit IRC03:06
*** nati_ueno has quit IRC03:19
*** nati_ueno has joined #openstack-meeting03:20
*** reed has joined #openstack-meeting03:21
*** radez is now known as radez_g0n303:23
*** sandywalsh has joined #openstack-meeting03:32
*** hemna has quit IRC03:37
*** anilkb has joined #openstack-meeting03:39
*** asalkeld has quit IRC03:47
*** asalkeld has joined #openstack-meeting03:47
*** john5223 has quit IRC03:49
*** ivasev has quit IRC03:51
*** ivasev has joined #openstack-meeting03:52
*** SergeyLukjanov has joined #openstack-meeting03:54
*** danwent has joined #openstack-meeting04:09
*** vipul is now known as vipul|away04:10
*** uramanan has quit IRC04:12
*** vipul|away is now known as vipul04:12
*** uramanan has joined #openstack-meeting04:12
*** tomoe__ has joined #openstack-meeting04:14
*** tomoe_ has quit IRC04:17
*** nati_ueno has quit IRC04:17
*** koolhead17 has joined #openstack-meeting04:22
*** vipul is now known as vipul|away04:27
*** sacharya has quit IRC04:27
*** topol has quit IRC04:28
*** openstack has joined #openstack-meeting04:36
*** ChanServ sets mode: +o openstack04:36
*** garyk has quit IRC04:43
*** boris-42 has joined #openstack-meeting04:48
*** koolhead17 has joined #openstack-meeting04:50
*** SergeyLukjanov has quit IRC04:57
*** vipul|away is now known as vipul05:02
*** colinmcnamara has quit IRC05:03
*** gongysh has quit IRC05:07
*** ivasev has quit IRC05:08
*** tomoe__ has quit IRC05:16
*** tomoe_ has joined #openstack-meeting05:17
*** boris-42 has quit IRC05:21
*** mfaraji has quit IRC05:22
*** mfaraji has joined #openstack-meeting05:23
*** mfaraji has quit IRC05:25
*** zbitter has joined #openstack-meeting05:26
*** zaneb has quit IRC05:30
*** reed has quit IRC05:33
*** garyk has joined #openstack-meeting05:41
*** nati_ueno has joined #openstack-meeting05:41
*** nati_ueno has quit IRC05:50
*** SergeyLukjanov has joined #openstack-meeting05:55
*** gongysh has joined #openstack-meeting06:01
*** nati_ueno has joined #openstack-meeting06:13
*** lillie has quit IRC06:14
*** lillie has joined #openstack-meeting06:15
*** markwash has joined #openstack-meeting06:21
*** nimi has joined #openstack-meeting06:23
*** mrunge has joined #openstack-meeting06:24
*** flaper87 has joined #openstack-meeting06:32
*** ctracey has quit IRC06:40
*** ctracey has joined #openstack-meeting06:47
*** tomoe_ has quit IRC07:01
*** tomoe_ has joined #openstack-meeting07:01
*** tomoe__ has joined #openstack-meeting07:05
*** tomoe_ has quit IRC07:05
*** nati_ueno has quit IRC07:07
*** almaisan-away has joined #openstack-meeting07:07
*** almaisan-away is now known as al-maisan07:07
*** nati_ueno has joined #openstack-meeting07:08
*** al-maisan is now known as almaisan-away07:09
*** boris-42 has joined #openstack-meeting07:11
*** nati_ueno has quit IRC07:13
*** yaguang has quit IRC07:15
*** koolhead17 has quit IRC07:19
*** matiu has quit IRC07:20
*** pnavarro has joined #openstack-meeting07:21
*** mordred has quit IRC07:22
*** hanney has joined #openstack-meeting07:28
*** reed has joined #openstack-meeting07:30
*** Mandell has quit IRC07:32
*** yaguang has joined #openstack-meeting07:33
*** yaguang has left #openstack-meeting07:35
*** henrynash has joined #openstack-meeting07:50
*** danwent_ has joined #openstack-meeting07:52
*** danwent has quit IRC07:53
*** danwent_ is now known as danwent07:53
*** danwent_ has joined #openstack-meeting07:58
*** davidha has quit IRC07:59
*** danwent has quit IRC08:01
*** danwent_ is now known as danwent08:01
*** psedlak has joined #openstack-meeting08:07
*** henrynash has quit IRC08:08
*** dwcramer has quit IRC08:12
*** derekh has joined #openstack-meeting08:12
*** anilkb has quit IRC08:13
*** nati_ueno has joined #openstack-meeting08:17
*** danwent has quit IRC08:21
*** johnthetubaguy has joined #openstack-meeting08:21
*** henrynash has joined #openstack-meeting08:23
*** johnthetubaguy1 has joined #openstack-meeting08:28
*** zbitter is now known as zaneb08:28
*** johnthetubaguy has quit IRC08:29
*** afazekas has quit IRC08:35
*** afazekas has joined #openstack-meeting08:35
*** ndipanov has joined #openstack-meeting08:43
*** egallen has joined #openstack-meeting08:43
*** johnthetubaguy1 is now known as johnthetubaguy08:44
*** davidha has joined #openstack-meeting08:49
*** anilkb has joined #openstack-meeting08:53
*** dosaboy_ has joined #openstack-meeting08:57
*** dosaboy_ has quit IRC08:58
*** shardy has joined #openstack-meeting09:00
*** dosaboy_alt has joined #openstack-meeting09:00
*** shardy has left #openstack-meeting09:06
*** mkollaro has joined #openstack-meeting09:10
*** pnavarro has quit IRC09:10
*** anilkb has left #openstack-meeting09:27
*** sileht is now known as fortran7709:27
*** esker has joined #openstack-meeting09:27
*** fortran77 is now known as sileht09:28
*** esker has quit IRC09:33
*** darraghb has joined #openstack-meeting09:37
*** boris-42 has quit IRC09:39
*** salv-orlando has joined #openstack-meeting09:51
*** SergeyLukjanov has quit IRC09:52
*** alexpilotti has joined #openstack-meeting09:54
*** tomoe__ has quit IRC09:56
*** SergeyLukjanov has joined #openstack-meeting09:56
*** tomoe_ has joined #openstack-meeting09:56
*** Yada has joined #openstack-meeting09:57
*** tomoe_ has quit IRC10:01
*** davidhadas has joined #openstack-meeting10:03
*** Yada has quit IRC10:04
*** davidha has quit IRC10:05
*** henrynash has quit IRC10:11
*** zyluo has joined #openstack-meeting10:17
*** egallen has quit IRC10:17
*** arata has joined #openstack-meeting10:21
*** egallen has joined #openstack-meeting10:23
*** tomoe_ has joined #openstack-meeting10:23
*** pcm_ has joined #openstack-meeting10:28
*** pcm_ has quit IRC10:29
*** pcm_ has joined #openstack-meeting10:29
*** nati_ueno has quit IRC10:29
*** nati_ueno has joined #openstack-meeting10:30
*** egallen has quit IRC10:33
*** tomoe_ has quit IRC10:34
*** nati_ueno has quit IRC10:34
*** tomoe_ has joined #openstack-meeting10:35
*** tomoe_ has quit IRC10:39
*** egallen has joined #openstack-meeting10:50
*** topol has joined #openstack-meeting11:06
*** davidha has joined #openstack-meeting11:07
*** davidhadas has quit IRC11:10
*** SergeyLukjanov has quit IRC11:12
*** sandywalsh has quit IRC11:14
*** zhuadl has joined #openstack-meeting11:17
*** SergeyLukjanov has joined #openstack-meeting11:24
*** adalbas has joined #openstack-meeting11:26
*** sandywalsh has joined #openstack-meeting11:27
*** beagles has joined #openstack-meeting11:35
*** zyluo has quit IRC11:36
*** noslzzp has joined #openstack-meeting11:51
*** matiu has joined #openstack-meeting11:53
*** jpich has joined #openstack-meeting11:54
*** markvoelker has joined #openstack-meeting11:56
*** esdaniel has joined #openstack-meeting12:00
*** jhenner has joined #openstack-meeting12:01
*** arata has quit IRC12:09
*** dolphm has joined #openstack-meeting12:11
*** dolphm has joined #openstack-meeting12:12
*** dolphm has left #openstack-meeting12:12
*** rnirmal has joined #openstack-meeting12:15
*** SergeyLukjanov has quit IRC12:18
*** boris-42 has joined #openstack-meeting12:18
*** tomoe_ has joined #openstack-meeting12:24
*** dolphm has joined #openstack-meeting12:30
*** joesavak has joined #openstack-meeting12:35
*** dprince has joined #openstack-meeting12:37
*** zhuadl has quit IRC12:43
*** davidkranz_ is now known as david-kranz12:43
*** zhuadl has joined #openstack-meeting12:44
*** david-kranz is now known as davidkranz12:45
*** zhuadl has quit IRC12:45
*** rnirmal has quit IRC12:47
*** anteaya has joined #openstack-meeting12:47
*** radez_g0n3 is now known as radez12:47
*** egallen has quit IRC12:51
*** zhuadl has joined #openstack-meeting12:51
*** zhuadl has quit IRC12:55
*** colinmcnamara has joined #openstack-meeting12:57
*** SergeyLukjanov has joined #openstack-meeting12:58
*** cdub_ has joined #openstack-meeting12:59
*** egallen has joined #openstack-meeting12:59
*** zhuadl has joined #openstack-meeting13:01
*** henrynash has joined #openstack-meeting13:01
*** zhuadl has quit IRC13:01
*** dolphm has quit IRC13:01
*** zhuadl has joined #openstack-meeting13:02
*** rnirmal has joined #openstack-meeting13:02
*** dhellmann-away is now known as dhellmann13:03
*** henrynash has quit IRC13:03
*** henrynash has joined #openstack-meeting13:05
*** zhuadl has quit IRC13:05
*** matiu has quit IRC13:06
*** zhuadl has joined #openstack-meeting13:10
*** ijw1 is now known as ijw13:10
*** zhuadl has quit IRC13:14
*** martine has joined #openstack-meeting13:15
*** zhuadl has joined #openstack-meeting13:16
*** darraghb has quit IRC13:16
*** zhuadl has quit IRC13:16
*** darraghb has joined #openstack-meeting13:16
*** zhuadl has joined #openstack-meeting13:17
*** ctracey has quit IRC13:18
*** zhuadl has quit IRC13:18
*** SergeyLukjanov has quit IRC13:21
*** darraghb has quit IRC13:21
*** darraghb has joined #openstack-meeting13:23
*** zhuadl has joined #openstack-meeting13:24
*** MarkAtwood has quit IRC13:24
*** stevemar has joined #openstack-meeting13:25
*** zhuadl has quit IRC13:26
*** esker has joined #openstack-meeting13:30
*** markmcclain has joined #openstack-meeting13:36
*** zhuadl has joined #openstack-meeting13:37
*** mfaraji has joined #openstack-meeting13:40
*** woodspa has joined #openstack-meeting13:43
*** sirushti has joined #openstack-meeting13:44
*** dguitarbite has joined #openstack-meeting13:45
*** ewindisch has quit IRC13:48
*** mtreinish has joined #openstack-meeting13:51
*** eharney has joined #openstack-meeting13:58
*** Gordonz has joined #openstack-meeting14:01
*** mfaraji has quit IRC14:01
*** cp16net is now known as cp16net|away14:02
*** mscott has joined #openstack-meeting14:04
*** esdaniel has quit IRC14:05
*** mrodden has joined #openstack-meeting14:05
*** gongysh has quit IRC14:06
*** topol has quit IRC14:07
*** Gordonz has quit IRC14:09
*** Gordonz has joined #openstack-meeting14:09
*** ewindisch has joined #openstack-meeting14:10
*** dwcramer has joined #openstack-meeting14:12
*** egallen has quit IRC14:14
*** zyluo has joined #openstack-meeting14:18
*** egallen has joined #openstack-meeting14:19
*** mscott has quit IRC14:19
*** gongysh has joined #openstack-meeting14:21
*** zhuadl has quit IRC14:22
*** fnaval has quit IRC14:23
*** MarkAtwood has joined #openstack-meeting14:25
*** sacharya has joined #openstack-meeting14:30
*** cp16net|away is now known as cp16net14:32
*** mordred has joined #openstack-meeting14:36
*** vkmc has joined #openstack-meeting14:37
*** vkmc has joined #openstack-meeting14:37
*** dprince has quit IRC14:38
*** egallen has left #openstack-meeting14:40
*** davidha has quit IRC14:40
*** topol has joined #openstack-meeting14:40
*** egallen has joined #openstack-meeting14:40
*** pschaef has joined #openstack-meeting14:42
*** markwash has quit IRC14:42
*** marun has quit IRC14:44
*** jaypipes has joined #openstack-meeting14:45
*** mfaraji has joined #openstack-meeting14:46
*** sacharya has quit IRC14:46
*** lloydde has joined #openstack-meeting14:48
*** lloydde_ has joined #openstack-meeting14:49
*** lloydde_ has quit IRC14:50
*** lloydde_ has joined #openstack-meeting14:52
*** lloydde_ has quit IRC14:52
*** lloydde has quit IRC14:52
*** mfaraji has quit IRC14:53
*** lloydde has joined #openstack-meeting14:53
*** lloydde has joined #openstack-meeting14:53
*** lloydde_ has joined #openstack-meeting14:55
*** dachary has joined #openstack-meeting14:58
*** lloydde has quit IRC14:58
*** fnaval has joined #openstack-meeting14:59
*** lloydde has joined #openstack-meeting14:59
*** avishay has joined #openstack-meeting14:59
*** lloydde_ has quit IRC15:01
*** jgallard has joined #openstack-meeting15:01
dacharyjgallard: \o15:02
jgallarddachary, hi!15:03
jgallarddachary, can you confirm me that, the meeting is at 4PM UTC, so... 6PM for us?15:03
dacharygood point :-)15:04
* dachary fixes his agenda15:04
avishaythe meeting will be in another hour?15:05
jgallardavishay, I think this will be the case15:05
jgallardin one hour15:05
avishayjgallard: i hate daylight savings :-/15:05
jgallardavishay, yes :(15:05
avishayok, see you in an hour!15:06
jgallardhéhé, see you!15:06
*** lbragstad has quit IRC15:10
*** danwent has joined #openstack-meeting15:16
*** garyk has quit IRC15:18
*** sacharya has joined #openstack-meeting15:18
*** cp16net is now known as cp16net|away15:22
*** boris-42 has quit IRC15:27
*** lbragstad has joined #openstack-meeting15:30
*** cp16net|away is now known as cp16net15:32
*** lloydde has quit IRC15:33
*** ryanpetrello has joined #openstack-meeting15:35
*** bdpayne has joined #openstack-meeting15:36
*** john5223 has joined #openstack-meeting15:37
*** danleyden has quit IRC15:38
*** danleyden has joined #openstack-meeting15:38
*** Yada has joined #openstack-meeting15:49
*** kebray has quit IRC15:55
*** lloydde has joined #openstack-meeting15:55
*** rushiagr has joined #openstack-meeting15:56
*** vincent_hou has joined #openstack-meeting15:58
*** yaguang has joined #openstack-meeting15:58
*** davidhadas has joined #openstack-meeting15:58
*** JM1 has joined #openstack-meeting15:59
*** thingee has joined #openstack-meeting15:59
jgriffith#startmeeting cinder16:00
openstackMeeting started Wed Apr  3 16:00:33 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** bswartz has joined #openstack-meeting16: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
jgriffithhey everybody!16:00
rushiagrjgriffith: o/16:00
eharneyhello16:00
dacharyhi16:00
*** ivasev has joined #openstack-meeting16:00
rushiagrsorry, missed the last meeting. Was a bit sick16:01
avishayhey16:01
jgriffithrushiagr: hope you're feeling better16:01
jgriffithavishay: hola!16:01
thingeeo/16:01
jgallardhi16:01
jgriffithand there's the man thingee16:01
*** lakhindr_ has joined #openstack-meeting16:01
jgriffithalright... let's get started16:01
rushiagrjgriffith: yes16:01
bswartzI'm a bit sick this week, but I'm here16:01
kmartinhello16:01
jgriffithkmartin: howdy16:01
vincent_houhi16:02
* DuncanT wakes up16:02
jgriffithOk... so short agenda at: https://wiki.openstack.org/wiki/CinderMeetings#Agenda_for_next_meeting16:02
jgriffithDuncanT: !!!!16:02
jgriffithI thought you were on vacation!16:02
jgriffithAlright... good turn out this week16:02
DuncanTGot back this morning16:02
jgriffithLet's get started16:02
jgriffith#topic finalize session topics16:02
*** openstack changes topic to "finalize session topics (Meeting topic: cinder)"16:02
jgriffithhttp://summit.openstack.org/16:03
jgriffithSo I've narrowed it down a bit16:03
avishayjgriffith: for first-timers at the summit, can you give a quick intro as to how a session is run?16:03
jgriffithavishay: sure... good idea16:03
jgriffithSo each session is about 45 minutes16:03
jgriffithThat's going to include your time to get everybody in the room, get started and present your topic16:04
jgriffithWe almost ALWAYS run out of time16:04
jgriffithThe idea behind the sessions...16:04
jgriffithThey're intended to be design sessions, not user sessions, tutorials etc16:04
*** mkollaro has quit IRC16:05
jgriffithThey're intended to make design and feature decisions for the upcoming dev cycle16:05
jgriffithUnfortunately it's common for folks not involved in the project to wander in and try to learn about OpenStack16:05
jgriffithSo....16:05
avishayPresenter shows up with intro slides, then discussion?16:05
thingeeavishay: slides is optional from what I've seen. some people just began with an etherpad up16:06
jgriffithavishay: doesn't even need to be that formal (ie the intro slides)16:06
*** jbrogan has joined #openstack-meeting16:06
jgriffithit's a pretty ad-hoc deal, and it's mostly about collaborating and working16:06
avishayok16:06
jgriffithDon't get carried away worrying about formal presentation etc16:06
creihtoften just having an ehterpad up works while you discuss something works very well16:06
avishayif i don't have to make slides, i'm a happy camper16:06
* creiht goes back to lurking :)16:06
jgriffithcreiht: +116:06
jgriffithI was going to get to that16:06
jgriffithetherpad is the BEST way to go about things16:07
dachary:-D a few slides with URLs & references are helpful, IMHO16:07
jgriffiththat way everybody get's to contribute and take notes and we have a record16:07
thingeedachary: I'll give you a giant QR code16:07
*** uramanan_ has joined #openstack-meeting16:07
jgriffithdachary: that's not really the point of the design session though16:07
dacharyneat :-)16:07
avishaythingee: :)16:07
jgriffithI *think* there are some recordings of design sessions out on the web16:07
jgriffithI'll see if I can find some and provide a link to folks that haven't experienced the mahem yet ;)16:08
*** ladquin has joined #openstack-meeting16:08
*** uramanan_ has quit IRC16:08
avishayhaha16:08
jgriffithSo the key thing here is it's the rare opportunity that we all get to meet face to face and has some of our decisions out16:08
* DuncanT hopes there are no videos...they're all going to make him out as an argumentative sod...16:08
jgriffithDuncanT: HA!!!16:08
creihtDuncanT: we already new that anyways :)16:09
bswartzjgriffith: the design summit sessions are broadcast but not recorded16:09
creihtknew16:09
jgriffithbswartz: some have been recorded16:09
jgriffithanyway.....16:09
jgriffithavishay: does that help?16:09
bswartzthe conference sessions are definitely recorded -- I've looked and failed to find any design session videos16:09
avishayjgriffith: yes, sure does - thanks!16:09
*** mfaraji has joined #openstack-meeting16:10
jgriffithkmartin: DuncanT thingee creiht did I miss anything important to point out?16:10
kmartinto create a new eithepad start here, https://etherpad.openstack.org/ then being it up in your session16:10
*** marun has joined #openstack-meeting16:10
kmartinsounds good16:10
DuncanTjgriffith: I think that covers it16:10
jgriffithKey things....16:10
*** uramanan has quit IRC16:10
jgriffithShow up and start ON TIME!!!!16:10
jgriffithIf you're an attendee... show up ON TIME!!!16:11
thingeesounds good to me. Expect to run out of time and to have this be a stepping stone towards a decision. Spend the design summit discussing things are difficult to convey over ML and irc16:11
jgriffithThe alloted time goes by VERY quickly and there's never a shortage of discussion16:11
bswartzseriously -- it's often standing room only if you're late16:11
jgriffiththingee: exactly16:11
*** mrodden has quit IRC16:11
jgriffiththe idea is to focus on the *hard* things16:12
dacharyany advice on how to make sure people get a chance to speak ? sometime it's difficult to say something without interrupting16:12
thingeeotherwise you'll be a bit discouraged if you expected everyone to agree right away :)16:12
jgriffithand to have a few beers with the folks we all work with throughout the world on a daily basis :)16:12
* thingee thinks jgriffith needs to take a break during the summit this time16:12
jgriffiththingee: sadly my employer doesn't agree :)16:13
DuncanTdachary: That's really up to whomever is running the session16:13
jgriffithdachary: you'll kinda see how it goes, but usually getting people to be able provide input is not a problem with our groups16:13
jgriffithin fact it's the opposite16:13
thingeeheh16:14
jgriffiththe harder part is keeping some focus in the group16:14
bswartzdachary: getting a seat towards the front of the room helps16:14
jgriffithso the only thing I would say....16:14
DuncanTAre we planning on an early unconference like last year to rough some of this stuff out without the extended audience? It seemed to really help last year to get the core team singing from roughly the same hymn sheet...16:14
jgriffithbe respectful, let people talk, especially presenters16:14
bswartzDuncanT: +116:14
*** dricco has joined #openstack-meeting16:14
jgriffithDuncanT: yeah, probably on some of the topics we'll want to do that16:15
jgriffithbut I also think we're more cohesive than we were at this time last year16:15
thingeeah yes, they call the front the fish bowl...at least it was that back at bexar. But you should be speaking up if you're in the front or have a real invested interest and now just on facebook on your lappy :)16:15
kmartinbswartz: don't give out to many of the secrets :)16:15
jgriffithand we're a bigger group16:15
thingeenow=not16:15
kmartindid we get a bigger room this year?16:15
jgriffithkmartin: I sure hope so16:15
jgriffith:)16:16
jgriffithOk... we can talk more about what to expect etc in cinder channel16:16
*** tomoe_ has quit IRC16:16
* avishay looks at the #topic .. sorry for hijacking :P16:16
jgriffith#topic Finalize session topics16:16
*** openstack changes topic to "Finalize session topics (Meeting topic: cinder)"16:16
*** tomoe_ has joined #openstack-meeting16:16
jgriffithI've hacked things a bit here16:17
jgriffithCombined a couple of sessions and just removed one or two altogether16:17
jgriffithI've got it down to 7 remaining16:17
jgriffithWhich puts about 3 over budget16:17
*** cdub_ has quit IRC16:18
kmartinsee a few ones showed up since the last meeting16:18
* DuncanT still sees bazzilions on the list16:18
jgriffithkmartin: yeah, baremetal16:18
kmartinCinder FC SAN Zone/Access Control Manager16:18
jgriffithYeah...16:18
avishayjgriffith: how many total do we get?16:19
jgriffithavishay: about 1216:19
jgriffithavishay: I may be able to steal a session or two if needed16:19
avishayjgriffith: I think my topic on capabilities is similar to winston's on extra specs - i'd be happy to co-present with him16:19
avishay(if it's indeed the case)16:20
jgriffithavishay: yeah, that's what I put in the review I believe16:20
avishayoh, he has two...16:20
avishayI would say "Standardizing vol type extra spec as driver input" and "Cinder Capability Standardization" are similar16:21
avishayAlso "Revisit backend capabilities/stats reporting" is in the same direction16:21
jgriffithavishay: notice I refused "Revist backend...."16:21
jgriffithavishay: or do you guys not see the review status and notes?16:22
avishayjgriffith: yes i did, but if you need you can probably refuse mine too and winston and i can do 1 session on volume types / extra specs / etc16:22
*** noslzzp has quit IRC16:22
*** ollie1 has joined #openstack-meeting16:22
avishayjgriffith: i don't see the notes, just status16:22
jgriffithavishay: Ok, so that's what I stated in the notes16:23
jgriffithI'll send updates to all of you that I lumped together :)16:23
DuncanTUnit testing can easily become a unconference... I don't think it is of that much general interest16:23
jgriffithOut of the ones that remain... we need to pick what we want to cover16:23
jgriffithDuncanT: that'll work16:24
DuncanT(We might have already agreed that last week... rings a bell)16:24
thingeeDuncanT: definitely intersted in it. I just thought it would be more useful for us cinder folks.16:24
jgriffithOk... so "cinder plugin interface"16:25
jgriffithJust to clarify16:25
jgriffithThe idea here is that 3'rd party drivers would no longer be a part of the Cinder project proper16:25
jgriffithVendors would be free to do their own thing and distribute how the see fit16:26
jgriffithWhat that would mean for us though...16:26
jgriffithIs some architecture/framework to provide some black-box compatability testing/verification16:26
vincent_houremove all the drivers?16:26
jgriffithSome sort of certification process16:26
jgriffithvincent_hou: ultimately that's sort of what it boils down to16:27
DuncanTThat sucks and would mean an epic amount more work16:27
jgriffithDuncanT: up front it would for sure16:27
guitarzanwe basically just test ours functionally16:27
kmartinI think the community would suffer with quality of the drivers and cinder as a whole as most active members have drivers16:27
DuncanT(and that is a rather more apocalyptic vision of what was proposed than I understood it to be)16:27
jgriffithguitarzan: yeah, so actually it is sort of what you guys are doing anyway16:28
*** zul has quit IRC16:28
avishayIMHO the session would be a heated debate with no outcome16:28
jgriffithOk, so it sounds like we're not ready to go down that path16:28
bswartz-1 on plugin interface/removing drivers16:28
jgriffithI'll nix it16:28
guitarzanI think we did have a bit of discussion about this a couple weeks ago in the meeting16:28
*** zul has joined #openstack-meeting16:28
kmartinavishay: bswartz +116:29
guitarzanit didn't sound clear what it would mean, since it seems we already have a plugin interface :)16:29
thingeeI think it would be a lot of work upfront, however, core would have more bandwidth to spend well, on core.16:29
dacharyjgriffith: it makes sense to me since there is no way to run actual integration tests with proprietary solutions. It would be good however, to keep free software drivers for which a tempest can be run using standard packages.16:29
jgriffithjust FYI, this is more along the lines of how Quantum is working I believe16:29
*** koolhead17 has joined #openstack-meeting16:29
*** MarkAtwood has quit IRC16:29
jgriffithdachary: huh?16:29
vincent_houissue: who is supposed to ensure the further quality of the drivers16:29
vincent_houcommunity?16:29
jgriffithdachary: There's no suggestion that the reference impl driver would go away16:29
jgriffithvincent_hou: the vendor providing the driver16:30
jgriffithso no need to debate it sounds like16:30
jgriffithdoesn't seem that there's much interest in this so we can just move on16:30
jgriffithNext one:16:30
dacharyjgriffith: I was refering to ceph. I understand that lvm is going to stay. Does that make sense ?16:30
DuncanTI think we can aim to put some more though into the subject for the next summit? There are clearly people who already work that way, so how the core supports / doesn't support such endeavours *is* an issue, but I don't think it is a pressing one yet16:30
jgriffithDuncanT: +116:31
jgriffithdachary: Oh I see...16:31
DuncanT(I'd rather put the thought into how to test what we have while it is easy, then deal with the hard problems later)16:31
jgriffithdachary: well that's riddled with some other issues that I'd be concerned about16:31
jgriffithDuncanT: agreed16:32
jgriffithI think right now that's a better thing to focus on16:32
jgriffithOk16:32
jgriffith#topic independent scheduler16:32
*** openstack changes topic to "independent scheduler (Meeting topic: cinder)"16:32
jgriffithI'm not sure how I feel about this one16:32
jgriffithIt's a neat idea, but we haven't really identified a real problem here as of yet that I'm ware of16:33
jgriffithaware16:33
*** otherwiseguy has quit IRC16:33
DuncanTIt seems to mostly just work. Might need some tweeking to the retry logic, but that seems like bug fixing not design work16:33
jgriffithDuncanT: what seems to mostly just work?16:33
DuncanTIt is not entirely deterministic, but that isn't necessarily a sensible design aim16:34
DuncanTjgriffith: Having two schedulers runnign16:34
bswartzwhat is the current remedy when the node hosting your scheduler or API service goes poof? just detect this case and start up a new one?16:34
jgriffithDuncanT: you mean in our current code16:34
jgriffithbswartz: build an HA cinder setup16:34
jgriffithjust like in Nova16:34
DuncanTjgriffith: Yeah. I only smoke tested it but it looks basically good though non-deterministic16:34
jgriffithDuncanT: got ya16:34
DuncanTNova works fine with multiple copies of the scheduler too... no need to mess with pacemaker etc16:35
jgriffithSo my take on this is...16:35
DuncanTMuch nicer from an HA POV16:35
jgriffithI'd rather focus on HA guides for implementation than go down this built in approach16:35
bswartz+116:35
dachary+116:36
hemnafk+116:36
jgriffithAs we move into H we can revisit if vincent_hou would like16:36
*** hemnafk is now known as hemna16:36
avishay+216:36
jgriffithvincent_hou: sound reasonable?16:36
DuncanTI much prefer to make multiple copies work / keep working16:36
vincent_houcool16:36
jgriffithvincent_hou: my only reasoning here is setting priorities, not because I don't like the idea16:36
*** rahmu has joined #openstack-meeting16:37
vincent_hou;-) i understand.16:37
*** xyang has joined #openstack-meeting16:37
jgriffithcool16:37
jgriffithalrighty....16:37
jgriffith#topic cinder for baremetal16:37
*** openstack changes topic to "cinder for baremetal (Meeting topic: cinder)"16:37
*** leseb has joined #openstack-meeting16:37
jgriffithI'm interested in this but to be honest I need some more detail than what's provided16:38
jgriffithanybody have any insight on this one?16:38
bswartzI know we have some customers who are already using cinder for baremetal, so I'm not sure what's missing16:38
hemnaWhat do we need to support it other than what we are doing for nova already?16:38
jgriffithSo this is the problem I think16:38
jgriffithI don't think any of us are on the same page WRT what they're going for here16:39
bswartzwho proposed it?16:39
jgriffithI suspect this is manage local storage on a baremetal install maybe?16:39
*** markmcclain has quit IRC16:39
jgriffithRobert Collins16:39
clarkblifeless: ^16:40
jgriffithclarkb: thank you :)16:40
dachary#link http://summit.openstack.org/cfp/details/4516:40
clarkbit is early morning his time right now but should be around in a few hours?16:40
jgriffithif folks would like I'll ping him later and get some details16:40
*** MarkAtwood has joined #openstack-meeting16:40
jgriffithOk... that's what I'll do16:41
guitarzanit almost sounds interesting just because I have no idea what it means :)16:41
thingeeguitarzan: +116:41
jgriffith#action jgriffith sync up with lifeless on cinder baremetal16:41
jgriffithguitarzan: indeed! :)16:41
*** winston-d has joined #openstack-meeting16:41
jgriffithOk, the only other one I had some questions about16:41
bswartzthe session proposal scores high on buzzword compliance16:41
jgriffithbswartz: haha16:42
dacharymy interpretation is that it's about attaching a LV directly to the VM without going thru iSCSI16:42
jgriffith#topic volume give/take16:42
*** openstack changes topic to "volume give/take (Meeting topic: cinder)"16:42
avishaydachary: that's what i thought as well16:42
jgriffithdachary: I believe you're correct but dont' want to guess16:42
hemnadachary, isn't that the job of nova's baremetal support though?16:42
jgriffithand it's useful in other places (Glance)16:42
jgriffithanyway....16:42
jgriffithDuncanT: give/take16:42
jgriffithIs this something that's really high demand?16:43
winston-dHey, guys. Sorry I'm late.16:43
jgriffithand is it full of peril to update context on volumes to change tenant ID?16:43
DuncanTjgriffith: We've people interested in it. It's really a special case of ACL though...16:43
avishaywinston-d: hey!16:43
dachary#link https://wiki.openstack.org/wiki/VolumeTransfer16:43
jgriffithDuncanT: So if we get ACL's implemented it *should* help with this16:43
avishayI wanted to say, this seems like it has overlap with the ACL topic16:44
winston-dAvishay hi16:44
bswartzis there any session to cover multi-attach? because give/take sounds like a degenerate case of multi-attach16:44
DuncanTjgriffith: Yeah...16:44
jgriffithbswartz: yes there is and no it's not the same16:44
DuncanTMulti-attach != give-take16:44
hemnabswartz, yah jgriffith and us want to talk about multi-attach16:44
bswartzok16:44
avishaybswartz: http://summit.openstack.org/cfp/details/13016:44
*** branen has joined #openstack-meeting16:44
*** garyTh has joined #openstack-meeting16:44
jgriffithgive-take in a nut-shell is transfer volumes among tenants16:44
jgriffithCMIIW DuncanT16:44
hemnabswartz, we want to allow ESX cluster nodes to attach the same volume16:45
jgriffithSo here's the thing on give/take16:45
jgriffithI don't know that's it's going to be a terrible thing to implement16:45
DuncanTYou're spot on. It just adds a bit of beurocracy to make it hard to do by accident16:45
jgriffithand I don't know that there's a huge debate on whether to do it or not16:45
jgriffithI think we can has that one out unconf or even over IRC16:45
DuncanTI've not heard anybody who hates it...16:45
jgriffithand I'd rather get ACL's figured out before trying to tackle it16:46
jgriffithI think some implementation details may fall out as a result of ACL's16:46
DuncanTSure. Can we just mention it at the ACL session? Then anybody who might want to kick off will know about it16:46
jgriffithDuncanT: For sure!16:46
avishayDuncanT: +116:46
*** jpich has quit IRC16:46
dachary+116:46
jgriffithI think we weave it in as a use case of ACL's16:46
jgriffithor a motiviator16:46
winston-d+116:46
jgriffithor whatever you somebody wants to call it :)16:46
*** Mr_T has joined #openstack-meeting16:47
vincent_houDuncanT: is the ACL for cinder project only?16:47
DuncanTvincent_hou: I'm not the main driver for ACLs, just an interested bystander16:47
jgriffithvincent_hou: isn't ACL's you?16:48
vincent_houyes, i submitted it16:48
*** leseb has quit IRC16:48
dachary#link http://summit.openstack.org/cfp/details/9816:48
winston-dVincent_Hou will u attend this summit?16:49
vincent_houyes16:49
*** yaguang has quit IRC16:49
winston-dCool16:49
vincent_houvisa received today16:49
dacharyvincent_hou: "Use case: several users can share the data in one volume." do you mean read-only ?16:49
jgriffithvincent_hou: DuncanT I've approved the ACL and added the note about give/take16:49
jgriffithand the link to the give/take wiki16:50
vincent_houyes. it came from that use case.16:50
jgriffithI'll expect the two of you to synch up and run this one together if that's ok?16:50
*** dprince has joined #openstack-meeting16:50
vincent_houok.16:50
avishaydachary: VMs might share read-write volumes too...16:50
DuncanTSure16:50
jgriffithEverybody good with read/only multi-attach?16:51
dacharyavishay: that is scary :-)16:51
bswartzjgriffith: no16:51
kmartinjgriffith: yes16:51
bswartzread/write multi attach is important16:51
avishaydachary: why?  some file systems / applications handle it just fine16:51
avishaybswartz: +116:51
jgriffithbswartz: sure16:51
vincent_houyes16:52
jgriffithI have no problem with looking into that16:52
*** boris-42 has joined #openstack-meeting16:52
dacharyavishay: interesting16:52
*** tomoe_ has quit IRC16:52
jgriffithMy focus however first is R/O multi-attach and go from there16:52
*** tomoe_ has joined #openstack-meeting16:52
xyanghemna: is there a session on multiattach in nova too?16:52
hemnaI don't know.16:52
*** tomoe_ has quit IRC16:52
bswartzI fail to understand why it's hard to do -- we go out of our way to prevent multi attach16:52
kmartinbswartz: I'll be talking about that in the same session with jgriffith16:53
hemnaThere is a group here at HP that is working on the ESX changes to support attaching a volume to multiple vmware server nodes.16:53
bswartzat the driver level multi-attach can already work16:53
jgriffithbswartz: really?16:53
hemnaI'd just like to avoid needing to touch every driver to support it.16:53
jgriffithit's not that it's hard to do, it's that it breaks shit!16:53
*** terry7 has joined #openstack-meeting16:53
*** tomoe_ has joined #openstack-meeting16:53
DuncanTbswartz: It is hard because data consistency issues crop up all over the shop16:53
JM1what's the use case for R/W multi-attach?16:53
guitarzanwe just need a --yes-i-really-mean-it flag16:54
jgriffithlatencies, consistencies, lost data, encryption16:54
jgriffithguitarzan: +1 :)16:54
bswartzJM1: the use case for R/W multi attach is clustered filesystems with a quorum disk16:54
*** markwash has joined #openstack-meeting16:54
jgriffithJM1: allowing somebody to F'themeselve in a serious manner16:54
DuncanTWe also need a guest stress test IMO16:54
thingeeguitarzan: that really does exist for RGW :)16:54
kmartinjgriffith: we can discuss in the session that's what we are working on16:54
JM1bswartz: and people want to run such things on cloud storage?16:54
bswartzJM1: absolultely16:55
DuncanTSo that people who *think* they've gotten it right can test at least some of the edge cases16:55
jgriffithSounds good... I've modified the description to include discuss R/W multi-attach16:55
guitarzanfolks definitely want multiattach (RW/clustered/whatever)16:55
JM1bswartz: what kind of benefit does it give them?16:55
jgriffithguitarzan: indeed16:55
hemnaDuncanT, we wrote some python stress tests to test out our drivers.  I'd like to eventually make it usable by others in cinder to stress test cinder itself.16:55
hemnaguitarzan, +116:55
jgriffithand I think we'll get there, but I'm wonderinf if it needs limits via things like Gluster plugin, NFS plugin etc16:55
DuncanTJM1: Clustered FS in the cloud makes some types of HA really easy16:55
jgriffithanyway....16:56
bswartzJM1: the ability to run existing applications that rely on clustered filesystems and quorum disks (such as any Microsoft Clustering solution)16:56
jgriffith#topic encryption16:56
*** openstack changes topic to "encryption (Meeting topic: cinder)"16:56
*** mfaraji has quit IRC16:56
guitarzanthingee: rgw?16:56
jgriffithSo it doesn't seem like anybody else has been following the ML discussions on this16:56
jgriffithbut you REALLy need to take a look at this IMO16:56
* bswartz has16:56
jgriffithIt has VERY serious implications for all of us16:56
*** derekh has quit IRC16:57
bswartzevil encryption is evil16:57
avishaythat sounds rather ominous16:57
guitarzanall of the discussions sound very handwavy to me16:57
* DuncanT is a bit behind, I assumed it would get properly hashed out at the summit - the way they are proposing to do it in nova is just broken, for usability and security16:57
jgriffithDuncanT: don't assume :)16:57
avishayI still don't understand the thread model16:57
DuncanTOh dear16:57
* hemna waves hands16:57
jgriffithSo if folks are following this and have input, I'm a bit disappointed that I've been the only one objecting16:58
avishay*threat model16:58
DuncanTI objected to two reviews ont he subject16:58
jgriffithDuncanT: indeed!  thanks for that BTW16:58
jgriffithavishay: what do you mean?16:58
jgriffithavishay: you mean why it's bad?16:58
hemnawhich subject?  encryption? or multi-attach ?16:58
DuncanTDiscussing the implementation details on the mailing list is just painful16:58
jgriffithDuncanT: that's very true...16:58
avishayjgriffith: no, what they are trying to solve.  what is trusted?  what are they trying to protect against?16:59
jgriffithSo we have a session in Cinder and in Nova that should not overlap16:59
jgriffithso we can all attend both16:59
jgriffithavishay: https://wiki.openstack.org/wiki/VolumeEncryption16:59
DuncanTI'm hoping to get our encryption guy to go to both too16:59
jgriffithSo encryption aside17:00
jgriffithIt take a key management piece out of Cinder17:00
thingeeavishay: the focus isn't exactly vendor centric. the fear is once we have something, no one would be working with it really. some backends might have their own solution to this already.17:00
dacharybefore any kind of encryption can be implemented, there needs to be a way to store keys, which is missing.17:00
jgriffithwhich I think is full of issues17:00
avishayjgriffith: i've seen that, but it doesn't answer my question - it goes right into architecture without going into the threat model first17:00
jgriffithThe other thing is the fact that if you're device does things like encryption built-in or de-dup, or compression this could cause some unexpected behaviors17:00
jgriffithavishay: they touch on it17:00
jgriffithbut regardless, I didn't write it so you're not going to get insight from me :)17:01
jgriffithand we're out of time17:01
jgriffithbut I wanted to make sure folks were aware of this and that they look at the patch etc17:01
DuncanT"There are some additional unknowns about how the encrypted device will  interact with other OpenStack features. For example,  exporting/snapshotting volumes and live migration will need to be  investigated"17:01
avishayi'd like a summit topic on it and get it all sorted out17:01
jgriffiththink about implications, alternative implementations (ie same impl in Cinder) that the drivers can over-ride with their own impls17:02
jgriffithavishay: as I just said, you've got two17:02
jgriffithOk...17:02
thingeeavishay: It's in the first paragraph of the intro17:02
thingeethanks, bye!17:02
thingee:)17:02
jgriffiththanks everyone17:02
*** danwent has quit IRC17:02
jgriffith#endmeeting17:02
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:02
openstackMeeting ended Wed Apr  3 17:02:54 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-04-03-16.00.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-04-03-16.00.txt17:02
avishaybye all!17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-04-03-16.00.log.html17:03
*** thingee has left #openstack-meeting17:03
vincent_houc u17:03
*** hanney has quit IRC17:03
winston-dBye17:03
*** jgallard has quit IRC17:03
rushiagrbye17:03
*** ollie1 has left #openstack-meeting17:03
*** avishay has left #openstack-meeting17:03
*** bswartz has left #openstack-meeting17:03
*** winston-d has left #openstack-meeting17:03
*** eharney has left #openstack-meeting17:03
*** garyk has joined #openstack-meeting17:03
*** matelakat has joined #openstack-meeting17:03
*** JM1 has left #openstack-meeting17:04
*** nati_ueno has joined #openstack-meeting17:04
*** Mandell has joined #openstack-meeting17:05
johnthetubaguyhi all17:05
johnthetubaguy#startmeeting XenAPI17:05
openstackMeeting started Wed Apr  3 17:05:31 2013 UTC.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:05
*** openstack changes topic to " (Meeting topic: XenAPI)"17:05
openstackThe meeting name has been set to 'xenapi'17:05
BobBallMorning John17:05
johnthetubaguywho is around for today's meeting?17:05
johnthetubaguygood evening bob17:05
* BobBall waves excitedly17:05
matelakatHi17:05
*** Nachi has joined #openstack-meeting17:06
*** nati_ueno has quit IRC17:06
*** dwcramer has quit IRC17:06
johnthetubaguyOK, lets get cracking17:06
johnthetubaguy#topic actions17:07
*** openstack changes topic to "actions (Meeting topic: XenAPI)"17:07
johnthetubaguyOK, not reviewed the release notes properly17:07
johnthetubaguymatelakat: I saw you /boot/guest stuff, thank you!17:07
johnthetubaguyhow is the ISO stuff?17:08
matelakatI committed a patch to devstack, so hopefully will document it during the week.17:08
matelakatISO -no porgress17:08
*** danwent has joined #openstack-meeting17:08
BobBallWhat's the deadline for the release notes?17:08
matelakattbh, I would like to play with it, while I am documenting it.17:08
BobBallIsn't that urgent now?17:08
johnthetubaguyyep17:09
matelakatISO is likely to be next week.17:09
johnthetubaguyits like due yesterday17:09
matelakatI am re -raising the iso action.17:09
johnthetubaguy#action matelakat to look at documenting ISO boot17:10
johnthetubaguymy patch got in, which is nice17:10
matelakat#action johnthetubaguy to review blueprints for release notes17:10
BobBallOk - where are the changes that we need to review for the release notes, or who has the action to change them?  I didn't think I had an action, so I'm hoping it's one of you two :D17:10
johnthetubaguythank you :-)17:10
johnthetubaguyit was me17:10
BobBallWell - we had some proposed release notes to add - should we just add them in case you don't have time John?17:10
johnthetubaguylooking at the blueprints17:10
matelakat#action matelakat to document /boot/guest17:10
johnthetubaguyyes, go for adding what you have17:10
matelakat#action matelakat to add https://wiki.openstack.org/wiki/XenServer/BootFromISO to the install docs17:11
johnthetubaguyOK, shall we move onto docs?17:11
matelakatSure.17:11
johnthetubaguymatelakat: I would test those first, see if it works OK for you!17:11
johnthetubaguywe should have tempests tests for this at some point17:11
matelakaty.17:12
johnthetubaguy#topic Docs17:12
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"17:12
johnthetubaguyany docs news / questions?17:12
matelakatI only document stuff, that I have seen working - don't take it personally17:12
*** dachary has left #openstack-meeting17:12
matelakatSmall doc improvements last week: #link https://review.openstack.org/#/c/25643/17:13
BobBallok - so this is where we were meant to talk about release notes I guess! Sorry!17:13
johnthetubaguycool17:13
johnthetubaguywell, it was actions from last meeting too17:13
matelakatShould we do it now?17:14
BobBallyes17:14
BobBallI'm trying to find links :D17:14
johnthetubaguyadd what you fancy17:14
johnthetubaguyI was going to review all the blueprints for xenapi impact17:14
matelakatLet's try to put on the obvious ones now.17:14
BobBallhmmmm17:14
johnthetubaguy+117:14
BobBallhow do you see the previous agenda?  That's not archived with the meeting minutes!17:15
BobBallrubbish!17:15
johnthetubaguyah, yes, we should add the links really17:15
johnthetubaguyyou can see the history in the wiki I thought17:15
BobBallI'm trying to find it and I'm clearly incompetent...17:16
*** vincent_hou has quit IRC17:16
BobBallhttps://wiki.openstack.org/w/index.php?title=Meetings/XenAPI&oldid=19604 is this week's17:16
BobBall#link https://wiki.openstack.org/w/index.php?title=Meetings/XenAPI&oldid=19604 Agenda for this week17:16
BobBallIs that the right syntax? :)17:16
*** pschaef has quit IRC17:16
matelakat#link https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly17:16
BobBallhttps://wiki.openstack.org/w/index.php?title=Meetings/XenAPI&direction=prev&oldid=19604 is last week's agenda which includes suggestions for release notes changes17:16
matelakatNova17:17
matelakatWhat pops up in your mind?17:17
BobBallThe only nova one from https://wiki.openstack.org/w/index.php?title=Meetings/XenAPI&direction=prev&oldid=19604 was config drive 2... but if it's not tested/demoed, not sure we can add it17:17
BobBallCinder has the XenAPINFS driver stuff17:18
BobBallso we could add that17:18
matelakatOkay, I am adding that.17:18
matelakatnow17:18
BobBallGreat - then if John has a chance to go through blueprints there may be other additions17:18
johnthetubaguyBobBall: I think config drive support is OK to add, maybe mark as experimental17:19
matelakatOkay, that was a one-word addition.17:19
matelakatdone.17:19
johnthetubaguycool17:19
matelakatnot really much, it's frustrating.17:19
matelakatBob, what do you think, should we put some effort to try out ConfigDrive?17:20
johnthetubaguyits not zero17:20
johnthetubaguyI was just about to say, Rick Harris and I will be looking at Config Drive17:20
*** rahmu has quit IRC17:20
matelakatOh, that's cool.17:20
johnthetubaguy#topic blueprints17:21
*** openstack changes topic to "blueprints (Meeting topic: XenAPI)"17:21
BobBallgreat.17:21
johnthetubaguyso, we should cover more of this at the summit17:21
johnthetubaguyand get that page update17:21
johnthetubaguybut we are looking into ways to deprecate the current agent, and move towards cloud-init17:21
matelakatFair enough.17:21
*** colinmcnamara has quit IRC17:21
johnthetubaguyespecially now the windows version is getting there17:21
matelakaty.17:22
johnthetubaguybit issue is online password reset, not 100% sure about that one yet17:22
johnthetubaguylol, I keep reading y as why rather than yes17:22
*** xyang has quit IRC17:22
*** otherwiseguy has joined #openstack-meeting17:22
matelakatDon't do that.17:23
johnthetubaguyOK, anything more for blueprints while we are on this?17:23
matelakatNot really.17:23
johnthetubaguyOK17:23
*** cp16net is now known as cp16net|away17:23
johnthetubaguy#topic bugs and qa17:23
*** openstack changes topic to "bugs and qa (Meeting topic: XenAPI)"17:23
johnthetubaguyso hows tempest stuff going?17:23
BobBallwhich tempest stuff?17:23
johnthetubaguymatelakat getting tempest running against XenServer17:23
johnthetubaguyI keep seeing the odd patch, how is it all looking?17:24
matelakatYou mean the XML client stuff.17:24
BobBallah17:24
matelakat#link https://review.openstack.org/#/c/25609/17:24
*** jbrogan has quit IRC17:25
*** mattray has joined #openstack-meeting17:25
matelakatSo, last time I ran the full tempest, I had issues around the console support.17:25
matelakatBut, another stuff popped up last week.17:25
*** Yada has quit IRC17:25
matelakatWhich might be qa related.17:25
*** Shree has quit IRC17:26
matelakatBoot from volume - As we got rid of the kernel lockups, I tried to run the bfv exercise.17:26
johnthetubaguyah, OK17:26
matelakatAnd that raised two (known) issues: XenServer type images not supported with Cinder (create volume from image)17:27
*** lakhindr_ has quit IRC17:27
matelakatSo I got rid of that by setting up a raw image.17:27
matelakatAnd came the next issue: Nova did not detect that it's a PV17:27
johnthetubaguyhmm17:28
*** colinmcnamara has joined #openstack-meeting17:28
matelakatSo these are two things which we could discuss in detail during the summit.17:28
johnthetubaguythat should be part of the glance settings really17:28
matelakatI would like to eliminate both.17:28
johnthetubaguyPV mode17:28
johnthetubaguythe detection code is never going to be super awesome17:28
matelakatY, I will try to set the xen tag on the image, and see if that works.17:28
BobBallwe can probably detect if the kernel is PV using readnotes17:28
matelakatBut I had to stop investigation at that point.17:29
johnthetubaguybut its filesystem dependent, and other things, maybe take a peak at how we detect that today17:29
matelakatAnyhow, bfv is sitting in the backlog at the moment.17:29
BobBallpygrub has to be able to identify the kernel (i.e. dom0 attach to the filesystem) to boot as PV - so once we have the kernel we only need to check if it's a pvops kernel which is where readnotes comes in17:30
*** markwash_ has joined #openstack-meeting17:30
*** colinmcnamara has quit IRC17:30
*** hemna has quit IRC17:31
johnthetubaguyOK17:31
johnthetubaguyconsole issues you mentioned?17:31
*** Nachi has quit IRC17:31
johnthetubaguythe serial console has not been implemented yet, maybe that is related to your issue?17:32
matelakatI guess so.17:32
matelakatAfaik, there is a patch somewhere in review.os17:32
matelakatI am adding this task to the backlog.17:32
johnthetubaguyindeed, its on the summit discussion17:32
*** markwash has quit IRC17:32
*** markwash_ is now known as markwash17:32
matelakatit wasn't the serial one, I think.17:33
matelakatI am not sure.17:33
johnthetubaguyhmm, ok17:33
matelakatLet's shelve this.17:33
johnthetubaguyyes17:33
johnthetubaguy#topic OpenDiscussion17:33
*** openstack changes topic to "OpenDiscussion (Meeting topic: XenAPI)"17:33
johnthetubaguySo any other items for today17:33
johnthetubaguyI guess the meeting time is one17:34
matelakatCould we do it a bit later?17:34
*** hemna has joined #openstack-meeting17:34
BobBallhaha17:34
BobBallwell I looked last week17:34
johnthetubaguyTuesday 1600 UTC?17:35
BobBallwe can move to a diff day and have it an hour or two earlier17:35
BobBallsounds good to me.17:35
matelakat+117:35
BobBallShould still be fine for US ppl17:35
johnthetubaguyyes17:35
*** hemna has quit IRC17:35
matelakatAnd, we should send out email to the mailing list17:35
*** dwcramer has joined #openstack-meeting17:35
johnthetubaguy#action email about time change17:35
johnthetubaguyabsolutally17:35
johnthetubaguyI will see if people object17:35
BobBallPerfect17:35
johnthetubaguyand its a good excuse to advertise the meeting again17:35
johnthetubaguyand the summit session17:36
BobBallsounds like the bot is down17:36
matelakatWould be nice to see more guys here.17:36
johnthetubaguyOK17:36
johnthetubaguyany more for any more?17:36
BobBalloh17:36
BobBallmaybe not17:36
matelakatsys.exit(0)17:36
johnthetubaguylol17:36
BobBallsurely you mean sys.exit(1)17:36
johnthetubaguy#endmeeting17:36
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:36
openstackMeeting ended Wed Apr  3 17:36:41 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:36
matelakatimport sys17:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-04-03-17.05.html17:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-04-03-17.05.txt17:36
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-04-03-17.05.log.html17:36
*** hemna has joined #openstack-meeting17:36
BobBallI'm sure this classifies as an error condition17:36
*** matelakat has quit IRC17:36
johnthetubaguyit wasn't that bad, surely :-P17:37
BobBall:)17:37
*** ewindisch has quit IRC17:37
*** nati_ueno has joined #openstack-meeting17:37
BobBallSee you next week John17:38
BobBall*gone*17:38
*** BobBall is now known as BobBallAway17:38
*** Mr_T has left #openstack-meeting17:38
*** johnthetubaguy has quit IRC17:42
*** maoy has joined #openstack-meeting17:42
*** rnirmal has quit IRC17:43
*** EstevaoHessHP_ has quit IRC17:43
*** cdub_ has joined #openstack-meeting17:45
*** darraghb has quit IRC17:48
*** clayg has joined #openstack-meeting17:50
*** dosaboy1 has joined #openstack-meeting17:53
*** dosaboy1 has quit IRC17:54
*** dosaboy_alt has quit IRC17:54
*** dosaboy_alt has joined #openstack-meeting17:55
*** rnirmal has joined #openstack-meeting17:56
*** dosaboy_alt has quit IRC17:58
*** cschwede has joined #openstack-meeting18:00
*** danwent has quit IRC18:01
*** Mandell has quit IRC18:02
*** mrodden has joined #openstack-meeting18:03
*** dwcramer has quit IRC18:04
*** danwent has joined #openstack-meeting18:06
*** mrunge has quit IRC18:08
*** adrian17od has joined #openstack-meeting18:10
*** cp16net|away is now known as cp16net18:10
*** Mandell has joined #openstack-meeting18:11
*** Gordonz has quit IRC18:11
*** esker has quit IRC18:16
*** leseb has joined #openstack-meeting18:21
*** danwent has quit IRC18:25
*** mfaraji has joined #openstack-meeting18:26
*** mfaraji has quit IRC18:26
*** esker has joined #openstack-meeting18:27
*** lcheng has joined #openstack-meeting18:27
*** dwcramer has joined #openstack-meeting18:30
*** vipul is now known as vipul|away18:31
*** mestery has quit IRC18:34
*** adrian17od has quit IRC18:36
*** donaldngo_hp has joined #openstack-meeting18:38
*** Nachi has joined #openstack-meeting18:39
*** mattray has quit IRC18:40
*** zaro has quit IRC18:41
*** noslzzp has joined #openstack-meeting18:41
*** noslzzp has quit IRC18:41
*** noslzzp has joined #openstack-meeting18:41
*** nati_ueno has quit IRC18:42
*** diogogmt has joined #openstack-meeting18:43
*** danwent has joined #openstack-meeting18:44
*** zyluo has quit IRC18:44
*** danwent has quit IRC18:45
*** danwent has joined #openstack-meeting18:46
*** sandywalsh has quit IRC18:47
*** vipul|away is now known as vipul18:47
*** hemna is now known as hemnafk18:48
*** rushiagr has quit IRC18:49
*** MarkAtwood has quit IRC18:49
*** ewindisch has joined #openstack-meeting18:50
*** ewindisch has quit IRC18:51
*** ewindisch has joined #openstack-meeting18:51
*** tongli has joined #openstack-meeting18:51
*** rushiagr has joined #openstack-meeting18:51
*** egallen has quit IRC18:52
*** jog0 has joined #openstack-meeting18:53
*** zaro has joined #openstack-meeting18:53
*** rushiagr has quit IRC18:56
*** henrynash has quit IRC18:56
*** zaitcev has joined #openstack-meeting19:00
notmynameswift meeting time19:01
ogelbukho/19:01
chmouelo/19:01
swifterdarrello/19:01
notmynameanyone from RAX here?19:01
cschwedeo/19:01
lifelessjgriffith: hi19:01
notmynamecschwede: ah, glad to see you. I want to make sure you're here fro the summit session summary19:02
lifelessjgriffith: cinder as an API for reserving local disk space on a baremetal node19:02
*** cdub_ has quit IRC19:02
lifelessjgriffith: clearly using cinder provided iscsi block devices from baremetal is pretty straight forward19:02
chmouellifeless: this is #openstack-meeting this is better suited in openstack-dev19:02
* ttx lurks19:02
notmynamelet's get started and see if any racker joins19:02
notmyname#startmeeting swift19:02
openstackMeeting started Wed Apr  3 19:02:49 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** sandywalsh has joined #openstack-meeting19:02
*** openstack changes topic to " (Meeting topic: swift)"19:02
openstackThe meeting name has been set to 'swift'19:02
*** MarkAtwood has joined #openstack-meeting19:02
notmynamenot a lot on the agenda today19:03
*** novas0x2a|laptop has joined #openstack-meeting19:03
notmyname(and will go very fast if we don't get a QA update for RAX)19:03
notmynamebut let's leave that for later19:03
lifelesschmouel: fair enough; was following up on my name being mentioned :P19:03
notmynamefirst up, general QA question. are there any QA efforts beyond rackspace that anyone is doing now?19:03
*** dwcramer has quit IRC19:04
notmynameI'm guessing that's a now19:04
notmyname*no19:04
chmouelnoip not for me19:04
notmynamecreiht: ping. know anything about RAX QA status?19:05
*** jhenner has quit IRC19:05
notmynameuntil we get that, let's move on to summit scheduling19:05
cschwedeplease let me know if i can help out with some QA tasks19:05
*** psedlak has quit IRC19:05
zaitcevRHOS and Fedora have some QA running, but the former goes release to release, while the latter is a bit bug-oriented and package oriented.19:05
notmynamecschwede: thanks. we'll talk about that at the summit. the basic answer is "YES!"19:05
*** spzala has joined #openstack-meeting19:06
cschwedenotmyname: ok :)19:06
notmynamezaitcev: cool. do you know if they've been looking at the 1.8.0 RC?19:06
notmynamewe've backported just about everything that's come in since the RC cut, so we're probably ok. I haven't heard of any showstoppers yet19:07
zaitcevnotmyname: No. Latest is 1.7.6.19:07
notmynameok19:07
notmynamezaitcev: I'd love to chat at the summit about how to potentially do that more often (ie for each swift release)19:08
notmynamewe had 18 sessions proposed for our 8 slots at the summit. I think all of you have proposed at least one session19:08
notmynamebut since there is no more room left in the official schedule for oveerflow slots, I've got to schedule 8 of the proposals. I'm planning on signing up for unconference sessions on tuesday as soon as I get to PDX.19:09
notmynameit's first-come-first-server as far as I know, so I'll try to be early :-)19:09
notmynamethe goal will be to write in our overflow sessions19:10
cschwedewhen does the unconference signing start?19:10
notmynamejust about all of the proposals have been great. things that various people in the community have been asking for and talking about19:10
notmynamettx: ^?19:10
zaitcevI'm ok with going into an overflow session, but I leave on Thursday.19:11
ttxMonday morning. Usually people start signing up a bit later19:11
ttxAnd most general incubaton wanabees should go on monday19:11
*** Shree has joined #openstack-meeting19:11
notmynameI've got stuff going on (ie other talks and meetings) on wednesday and thursday, so I'll be shooting for tuesday time slots19:11
ttxso you should be able to get most of tuesday without too much issues19:11
ttxbut some grouping and merging couldn't hurt. Each session is 40min long19:12
notmynameI should point out for the official record that the lack of scheduling space is not something that could have been predicted based on previous summit participation. we generally matched our slots 1:1 for previous summits19:12
*** dfg has joined #openstack-meeting19:13
dfghello19:13
notmynameyay, dfg!19:13
dfgsorry for being late and stuff19:13
notmynamenp. thanks for coming19:13
notmynamedfg: can you give a status update on QA?19:13
dfgum- i'll go ask19:13
notmynamedfg: thanks. basically, it comes down to 1) stop everything we can't release 2) looks ok 3) we need an rc3 with one or 3 more backports19:14
* notmyname is hoping for 219:14
notmynamefor the official summit sessions, I'm planning on performance-related talks and API-related talks. these are 2 of the big things that I think we'll be working on over the next 6 months19:15
ShreeI have a question regarding the Grizzly API doc release, are the Grizzly API docs ready and are the post on wiki the final released version?19:15
*** dwcramer has joined #openstack-meeting19:15
notmynameShree: I think that'd be a question for annegentle and the doc team. AFAIK, yes19:16
Shreeyes ping her but waiting for her response19:16
notmynameunfortunately, a focus on performance and API work will mean that other really cool stuff will be pushed to the unconference19:16
ShreeBTW, +1 for performance. is it  uconf session or part of the summit?19:17
notmynameI've "preapproved" all of the talks in order that each of you can still prepare your session, even if I can't promise a time slot19:17
notmynameShree: we've got 4 sessions related to performance that I'll target for the official time slots, I think19:17
*** glange has joined #openstack-meeting19:18
notmynamesorry for the confusion some of you got from having sessions approved, refused, approved19:18
zaitcevI've already beated my preso on my coworkers but the main part is a discussion and decisions how to proceed.19:18
*** MarkAtwood has quit IRC19:18
notmynamezaitcev: ya, I want your LFS talk too :-)19:18
*** MarkAtwood has joined #openstack-meeting19:19
dfgnotmyname: regression is passing, there's still a couple smallish features he's testing. CORS, tempurl fix, couple other things.19:19
notmynameare there any questions about the summit of scheduling or what to expect?19:19
notmynamedfg: cool, thanks. do you have an ETA? like today or next week? or ...?19:19
dfgi don't know. our QA situation has gotten pretty annoying because they're pulling our guys off onto other projects. nothing i can do about that though19:20
notmynameif there are no questions about the summit, are there questions about anything else?19:20
ogelbukhnotmyname: does replication network fall into performance? )19:21
notmynamedfg: I understand. thanks for letting me know.19:21
notmynameogelbukh: no :-(19:21
*** dwcramer has quit IRC19:21
ogelbukhok, thanks )19:21
*** portante has joined #openstack-meeting19:21
notmynameI'm hoping we can do some code review for the repl network patch and perhaps get it merged next week.19:22
notmynameso it looks like our time window is closing for the release and we'll do a final release for grizzly this evening (dfg)19:23
notmynamettx: ^19:23
notmynameah. almost forgot19:23
ttxnotmyname: sounds good. Just push the Final=True review when you're happy wit hit19:23
notmynamettx: will do19:23
*** mestery has joined #openstack-meeting19:24
*** noslzzp has quit IRC19:24
ttxnotmyname: the common release will be out by the time you ge tup19:24
notmynameour "Every two week" meeting means that our next meeting will be scheduled for the wednesday of the summit. I propose that we skip it19:24
ttxunless shit happens in some othe rproject, but unlikely at htis point19:24
notmynamettx: ok19:24
claygnotmyname: or move it to a bar19:25
swifterdarrellclayg: ++19:25
ogelbukh)19:25
notmynamelet's just schedule all our sessions there :-)19:25
zaitcevoh god, no, those are so noisy, you cannot multicast worth anything19:25
zaitcevI managed a bunch of 1:1 in San Antonio bars but it's a PITA19:26
notmynameI'm sure there will be plenty of opportunity for free booze next week19:26
notmynameerr..two weeks19:26
portantewhew19:26
notmynameso if there's nothing else, let's call the meeting. 30 seconds.....19:27
*** SergeyLukjanov has joined #openstack-meeting19:27
claygsee ya'll in a couple weeks!19:27
*** clayg has left #openstack-meeting19:27
chmouellooking forward to it!19:27
*** portante has left #openstack-meeting19:28
notmynamethanks again for coming. dfg, if anything comes up this afternoon, please let me know ASAP19:28
notmynamesee you in portland19:28
notmyname#endmeeting19:28
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:28
openstackMeeting ended Wed Apr  3 19:28:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-04-03-19.02.html19:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-04-03-19.02.txt19:28
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-04-03-19.02.log.html19:28
*** zaitcev has left #openstack-meeting19:29
*** glange has left #openstack-meeting19:29
*** cschwede has left #openstack-meeting19:31
*** dfg has left #openstack-meeting19:32
*** dprince has quit IRC19:33
*** noslzzp has joined #openstack-meeting19:37
*** vkmc has quit IRC19:42
*** egallen has joined #openstack-meeting19:48
*** noslzzp has quit IRC19:49
*** Nachi has quit IRC19:50
*** hanney has joined #openstack-meeting19:50
*** nati_ueno has joined #openstack-meeting19:50
*** ryanpetrello has quit IRC19:51
*** stevebaker has quit IRC19:52
*** noslzzp has joined #openstack-meeting19:52
*** stevebaker has joined #openstack-meeting19:53
*** zul has quit IRC19:54
*** dguitarbite has left #openstack-meeting19:55
*** vkmc has joined #openstack-meeting19:58
*** vkmc has joined #openstack-meeting19:58
*** dwcramer has joined #openstack-meeting19:59
*** mattray has joined #openstack-meeting20:01
sdake#startmeeting heat20:01
openstackMeeting started Wed Apr  3 20:01:39 2013 UTC.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: heat)"20:01
openstackThe meeting name has been set to 'heat'20:01
sdake#topic rollcall20:01
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:01
*** mrodden has quit IRC20:01
asalkeldo/20:01
*** mfaraji has joined #openstack-meeting20:02
stevebakerstevebaker20:02
zanebyo20:02
jpeelerhey20:02
hanneyhi20:02
Slowero/20:02
fsargenthi20:02
sdakehi20:02
sdakelooks like we have enough for a meeting20:03
sdake#topic blueprint review20:03
*** openstack changes topic to "blueprint review (Meeting topic: heat)"20:03
sdakewe have a ton of blueprints, many more then we can get through in this meeting20:03
asalkeldyea20:03
sdakeI'd like for folks to start thinking about them20:03
sdakeand how it relates to our other items of docs and tempest integration and general unit test improvements20:04
sdakelets get rolling20:04
sdakehttps://blueprints.launchpad.net/heat/+spec/resource-type-route20:04
stevebakermaybe possible thanks to this https://blueprints.launchpad.net/quantum/+spec/quantum-l3-routes20:05
asalkeldthat seems contained20:05
stevebakerI think you can set attributes on a quantum router to specify routes20:05
sdakejpeeler looking to get more involved in quantum20:06
stevebakerneed a quantum developer to provide some examples though20:06
sdakelooks like a good opportunity20:06
stevebakeryep20:06
SpamapSo/20:06
sdakehey spam we are just doing bp reviews20:06
*** vipul is now known as vipul|away20:06
SpamapSexcellent, sorry for the tardy, other meeting went long20:06
sdakehappens all the time ;)20:07
sdakestevebaker would you mind putting that link in the blueprint to help jpeeler get rolling20:07
stevebakerits already a dependency of the blueprint20:07
sdakecool20:08
sdake#link https://blueprints.launchpad.net/heat/+spec/moniker-resource20:08
*** dwcramer has quit IRC20:08
asalkeldso I started this20:09
asalkeldbut at the time the moniker client was a wip20:09
asalkeldso halted20:09
sdakeok well then I'll unapparove it20:09
stevebakerthis could be 2 separate blueprints, native moniker, and route53 resource types20:09
asalkeldalso zaneb suggested moniker could keep the resourcees20:09
asalkeldstevebaker, -120:10
asalkeldtoo many bp20:10
zanebI'm still in favour of that, but I expect we probably will still have to implement it for them20:10
asalkeldmakes life difficult20:10
stevebakerok, still native + route53 would be good though20:10
asalkeldyea20:10
sdakehttps://blueprints.launchpad.net/heat/+spec/raw-template-db20:11
sdakethis seems like a could add if we were out of other work to do, which is not the case20:12
sdakeso I'll set priority to low20:12
zanebtbh I think it's time we just cleaned that up20:12
stevebakerI think that should be rejected, template is parsed so early in the process these days that there is no raw to store20:12
zanebstevebaker: huh? we only ever store the template raw20:13
stevebakerzaneb: not raw yaml. it is parsed then serialized to json20:13
zanebright, but that's not what the raw_template table is20:14
asalkeldwell imagine a case were a cloud provides standard templates20:14
zanebit's called that because we used to also store the parsed template20:14
asalkeldwouldn't it make sense to try save space?20:14
zanebi.e. after parameter subsititutions and stuff20:14
asalkeldand store the template once20:15
zaneband we got rid of the parsed template because it was unnecessary state20:15
zanebasalkeld: we do only store the template once20:15
asalkeldwell this is suggesting not doing that20:15
SpamapSI think having the actual template submitted, not the parsed one, is incredibly useful for developer workflow where they can ask for the current running template and review the diff.20:15
asalkeldthat won't go away20:16
SpamapSIf its all parsed templates then the diff they're looking at is not the code they wrote.20:16
stevebakerSpamapS: a structural diff might be more helpful anyway20:16
zanebI'm not following this discussion at all. This blueprint is about the fact that what should be a Column in the database is actually a separate table.20:16
SpamapSThat BP is just suggesting moving the template into the main stack table as a blob right?20:16
*** vipul|away is now known as vipul20:17
stevebakeryeah, that seems harmless, and low priority20:17
*** mfaraji has quit IRC20:17
zanebSpamapS: parsed templates are completely ephemeral, we parse them on demand and there is no user access to them20:17
SpamapSI'd say measure the latency of calls and define a target. If the latency is too high, this would be just one of many things (some less impactful) to do to bring it down.20:17
sdakelatency in heat is not an issue with current openstack design20:18
zanebI don't care about latency, but I care about maintainability of the code20:18
sdakeso even more reason to make low priority20:18
*** vipul is now known as vipul|away20:18
SpamapSzaneb: sounds like it should be a bug, not a blueprint.20:18
asalkeldI am not sure priorty really matters, it what the devs want to work on20:19
zanebSpamapS: as I've said before, the distinction is entirely specious ;)20:19
asalkeldlets move on20:19
* zaneb blames Shuttleworth20:19
zanebasalkeld: +120:19
sdakewell for the moment i'll keep priority low20:19
sdakehttps://blueprints.launchpad.net/heat/+spec/quantum-security-group20:20
SpamapSzaneb: blueprints are good for keeping users unaware of the problem and unable to comment.. ;)20:20
zaneblol20:20
stevebakerthat change can be resurrected now that feature freeze is over20:21
stevebakernext!20:21
sdakestevebaker you indicated good progress on this blueprint, interested in handing off to jpeeler?20:21
sdakeguess not ;)20:21
sdakehttps://blueprints.launchpad.net/heat/+spec/rest-xml20:21
* jpeeler will take any quantum stuffs that people are willing to give up20:21
stevebakerjpeeler: you could have a crack at rebasing https://review.openstack.org/#/c/22280/ and see if it still applies20:21
*** niska has quit IRC20:22
asalkeldI think we should just use pecan+wsme20:23
stevebakershould we wait until a user actually asks for xml, then give it a higher priority?20:23
*** metral has quit IRC20:23
asalkeldthat handles a range of serialization20:23
*** matiu has joined #openstack-meeting20:23
*** matiu has joined #openstack-meeting20:23
SpamapSwho actually wants XML?20:23
asalkeldthere is a bp for that20:23
sdaketend to agree with stevebaker nobody cares for xml20:23
stevebakerGeorge Reese20:23
zanebI assumed we needed it because all the other APIs have it20:24
SpamapSThe TOSCA bits that are being discussed will satisfy the XML lovers.20:24
stevebakerglance doesn't20:24
SpamapSI say let he who requests XML implement it :)20:24
zanebif nobody wants it then I'm more than happy to kill it20:24
* zaneb never wanted to implement it anyway20:24
sdakespamaps +120:24
zanebSpamapS: +520:25
stevebakerhttp://lists.openstack.org/pipermail/openstack-dev/2012-August/000857.html20:25
*** niska has joined #openstack-meeting20:26
sdakejay makes alot of sense there20:26
zanebagree20:26
asalkeldthat's why pecan+wsme is good20:26
asalkeldit does the conversion for you20:27
asalkeldyou don't have to do anything20:27
sdakeok lets move on20:27
zanebasalkeld: there would be work to massage the data though (see discussion in the blueprint)20:27
asalkeldI'll read20:28
sdakehttps://blueprints.launchpad.net/heat/+spec/raw-template-db20:28
sdakehttps://blueprints.launchpad.net/heat/+spec/function-plugins20:28
stevebakerdidn't we just do that one?20:28
sdakewrong cp ;)20:28
zanebI started on this, but didn't get very far20:29
zanebdistracted by other work20:29
asalkeldI think if we get a new format this gets less important20:29
asalkeldwe could have a solid aws format and a pluggable native one20:29
*** rnirmal has quit IRC20:29
sdakeI believe one thing we are struggling with is helping to define priorities as a team20:29
stevebakershould it be a depencency for these https://blueprints.launchpad.net/heat/+spec/bash-environment-function https://blueprints.launchpad.net/heat/+spec/template-string-function20:30
asalkeldor just merge them20:30
sdakewould everyone be open to voting on setting "Design to approved" before working on the code20:30
zanebI don't know if we're doing a new format or what it would look like, so it's very hard to comment20:30
asalkeldzaneb, that was just a thought20:31
*** mestery has quit IRC20:31
zanebstevebaker: not necessarily, we can add those natively20:31
zanebstevebaker: i.e. not using plugins20:31
*** adalbas has quit IRC20:32
stevebakersdake, I wouldn't be keen on that process. it might discourage some interesting experiments20:32
asalkeldyea lets not add more process than we need20:32
SpamapSsdake: I think that "Approved" merely means "pay attention to this, the project is on board" not "go ahead and work on it"20:33
*** metral has joined #openstack-meeting20:33
asalkeldI think a problem with bp is they are a requirements/request view ; we then need a design/development view20:33
sdakespamaps it seems to mean to most folks "go crazy its a blueprint" :)20:33
zanebso, Approved could be a useful signal for people looking at which blueprints to implement first20:34
zanebwouldn't want to treat it as gating though20:34
SpamapSIndeed, the history of that particular value is that in the Ubuntu process teams sponsored Canonical would submit the specs to team managers and they would be approved for dev time..20:34
SpamapSfor an autonomous project like heat, its way too heavy20:35
*** ryanpetrello has joined #openstack-meeting20:35
asalkeldyip20:35
asalkeldlots of overlapping blueprints20:36
*** Shree has quit IRC20:37
*** vipul|away is now known as vipul20:37
asalkeldsdake i think you can kill this one : https://blueprints.launchpad.net/heat/+spec/cloud-init-metadata-section20:38
sdakedone20:38
stevebakeractually, that sounds interesting20:39
sdaketoo late now ;)20:39
stevebakeroh well ;)20:40
sdakethis is how voting would help us move through blueprints20:40
asalkeldstevebaker, you could always redo it20:40
stevebakersdake, can you ask the tech committee how they handle bp tsunamis in their projects?20:41
sdakeyes that is a great suggestion stevebaker20:41
sdakethanks20:41
sdakehttps://blueprints.launchpad.net/heat/+spec/prebuilding-images20:42
asalkeldwow that's old20:42
jpeeleri thought that was killed a long time ago20:42
sdakeya should be killed off20:42
asalkeldbrought over from github20:42
asalkeldyea +1 - kill20:43
sdakehttps://blueprints.launchpad.net/heat/+spec/rolling-updates20:43
SpamapSThat spec needs updates to be compatible with Amazon's rolling updates20:43
SpamapSbut in general I'm suggesting going more anyway20:44
*** jhenner has joined #openstack-meeting20:44
asalkeldthis seems odd (maybe kill it) -> https://blueprints.launchpad.net/heat/+spec/pulgins-way-to-resource20:44
*** leseb has quit IRC20:45
sdakehttps://blueprints.launchpad.net/heat/+spec/abstract-aws20:46
stevebakersavana could use Heat without any special resource types20:46
sdakeabstracting aws seems like a good idea20:46
asalkeldsure20:46
stevebakerthere are some separate bps for specific native resource types20:46
asalkeldwell it will  be interesting how the native format goes20:47
SpamapSI think abstract-aws can be broken up into a few efforts20:47
stevebakeryep20:48
asalkeldif we get that then almost no point to this20:48
SpamapSnative resources, doc fixes, and code reorg20:48
SpamapSasalkeld: I think native format is just yaml + native resource types :)20:48
zanebnot sure abstract is the right word here20:48
asalkeldcan we kill this: https://blueprints.launchpad.net/heat/+spec/stack-id-to-scheduler-hints20:49
zanebbut operators should be able to disable the built-in resources types20:49
SpamapSzaneb: partition?20:49
stevebakershould we spend some time talking about tomorrow's docsprint? (today for me)20:49
SpamapSbifurcate?20:49
SpamapSoh tomorrow is doc sprint? Count me in. (missed meeting last week)20:49
zanebSpamapS: I got nothing20:49
asalkeldjust have a map {'aws::*: disabled}20:49
SpamapSzaneb: I'll work on a better word before teh summit20:50
sdake#topic docsprint20:50
*** openstack changes topic to "docsprint (Meeting topic: heat)"20:50
* ttx lurks20:50
sdakeso stevebaker brings up a good point20:50
asalkeldwe need some word items20:50
asalkeldand direction (format etc..)20:50
asalkelds/word/work20:50
sdakeI think what would make sense is a docsprint on 4/4 for US and 4/5 for NZ/AU20:51
stevebakerI could write the cli guide, zaneb keen to do the api-ref?20:51
sdakethat way we can follow each other's work20:51
*** jhenner has quit IRC20:51
zanebstevebaker: yep, that seems like a good idea20:51
asalkeldwhat else is there?20:52
sdake#topic open discussion20:52
*** openstack changes topic to "open discussion (Meeting topic: heat)"20:52
stevebakersomeone needs to do the heat-admin. but I think the missing manual that we all need to help on is the template writing guide20:52
asalkeldI assume in yaml?20:52
stevebakersnippets in both formats I guess20:53
asalkeldthat's a pain20:53
*** spzala has quit IRC20:53
sdake#undo20:53
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x32ac250>20:53
sdakelets hold off on the full template guide20:54
sdakethat is months of work20:54
SpamapSI'd recommend snippets in yaml, as it is meant for readability20:54
sdakeand things may change after summit20:54
stevebakermaybe we could have a crack at the skeleton structure, so we know what we're in for20:54
zanebwell, I think we should autogenerate as much as possible20:54
asalkeldwell we can do something basic20:54
sdakethere we go, skeleton structure20:54
stevebakerzaneb: +120:54
zanebI believe stevebaker already made a blueprint for that20:55
SpamapSsdake: I do feel like writing the guide, before having 100% native resource types, is a bit suspect20:55
sdakespamaps I agree20:55
stevebakerzaneb: that still leaves a lot of tutorial style stuff though20:55
zanebthat's true20:55
zaneband that's a good place to start20:55
SpamapSso, skeleton with the current native types well documented would be a pretty good goal20:55
SpamapSalso another goal for a doc sprint: *test* the docs20:55
SpamapSas in, do everything it tells you to do20:55
stevebakerSpamapS: once we have a docs, new features will need to be flagged for DocImpact20:56
sdakeok 4 minutes left20:56
sdakemoving to open discussion now20:57
sdake#topic open discussion20:57
*** openstack changes topic to "open discussion (Meeting topic: heat)"20:57
sdakewe got through 10 blueprints in this meeting, just to review them20:57
zanebsdake: so it's open slather for delivery of Havana features now?20:57
sdakewe have 40 more to go20:57
* zaneb is working on parallel launch20:57
sdakeya we can start development now20:58
stevebakerif someone is vaguely interested in an unassigned blueprint they should assign it to themselves20:58
*** mfaraji has joined #openstack-meeting20:58
ttxsdake: still good to go for tagging the release tomorrow ?20:58
sdakettx yes20:58
ttxShall be done around 1500 UTC20:58
stevebakeractually, I should release python-heatclient too20:59
ttxexpect some bugmali while I move stuff to final milestone in LP20:59
ttxbugmail*20:59
sdakettx will watch for it20:59
sdakeour meeting time is over, so ending meeting enjoy ;)20:59
sdake#endmeeting20:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:59
openstackMeeting ended Wed Apr  3 20:59:50 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-04-03-20.01.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-04-03-20.01.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-04-03-20.01.log.html20:59
*** SpamapS has left #openstack-meeting21:01
*** SpamapS has joined #openstack-meeting21:01
*** rmohan has quit IRC21:01
*** rmohan has joined #openstack-meeting21:02
*** vipul is now known as vipul|away21:02
*** john5223 has quit IRC21:04
*** martine has quit IRC21:06
*** MarkAtwood has quit IRC21:07
*** sacharya has quit IRC21:08
*** egallen has quit IRC21:10
*** hanney has quit IRC21:10
*** jsavak has joined #openstack-meeting21:11
*** vipul|away is now known as vipul21:12
*** joesavak has quit IRC21:13
*** mfaraji has quit IRC21:13
*** tongli has quit IRC21:16
*** egallen has joined #openstack-meeting21:16
*** leseb has joined #openstack-meeting21:16
*** henrynash has joined #openstack-meeting21:23
*** radez is now known as radez_g0n321:24
*** leseb has quit IRC21:25
*** koolhead17 has quit IRC21:25
*** henrynash has quit IRC21:26
*** vipul is now known as vipul|away21:28
*** SergeyLukjanov has quit IRC21:31
*** afazekas has quit IRC21:32
*** henrynash has joined #openstack-meeting21:33
*** henrynash has quit IRC21:34
*** stevemar has quit IRC21:35
*** vipul|away is now known as vipul21:36
*** diogogmt has quit IRC21:38
*** jhenner has joined #openstack-meeting21:46
*** psedlak has joined #openstack-meeting21:49
*** sacharya has joined #openstack-meeting21:57
*** mtreinish has quit IRC22:03
*** jsavak has quit IRC22:06
*** psedlak has quit IRC22:06
*** mrodden has joined #openstack-meeting22:10
*** ewindisch has quit IRC22:13
*** boris-42 has quit IRC22:17
*** sacharya has quit IRC22:19
*** topol_ has joined #openstack-meeting22:20
*** topol has quit IRC22:24
*** topol_ has quit IRC22:25
*** otherwiseguy has quit IRC22:25
*** ivasev has quit IRC22:26
*** ryanpetrello has quit IRC22:26
*** maoy has quit IRC22:26
*** ewindisch has joined #openstack-meeting22:26
*** cdub_ has joined #openstack-meeting22:27
*** vkmc has quit IRC22:32
*** rezax` has joined #openstack-meeting22:35
*** fnaval has quit IRC22:36
*** donaldngo_hp has quit IRC22:37
*** zul has joined #openstack-meeting22:38
*** esker has quit IRC22:40
*** donaldngo_hp has joined #openstack-meeting22:40
*** henrynash has joined #openstack-meeting22:40
*** garyTh has quit IRC22:40
*** donaldngo_hp has quit IRC22:41
*** jhenner has quit IRC22:42
*** mattray has quit IRC22:43
*** bdpayne has quit IRC22:46
*** bdpayne has joined #openstack-meeting22:48
*** esker has joined #openstack-meeting22:51
*** mrodden has quit IRC22:52
*** henrynash has quit IRC22:52
*** lbragstad has quit IRC22:54
*** egallen has quit IRC22:55
*** cdub_ has quit IRC22:56
*** crank has quit IRC22:58
*** cdub_ has joined #openstack-meeting23:01
*** vipul is now known as vipul|away23:02
*** colinmcnamara has joined #openstack-meeting23:04
*** colinmcnamara has joined #openstack-meeting23:04
*** alexpilotti has quit IRC23:08
*** esker has quit IRC23:08
*** esker has joined #openstack-meeting23:10
*** esker has quit IRC23:11
*** dwcramer has joined #openstack-meeting23:12
*** noslzzp has quit IRC23:14
*** lbragstad has joined #openstack-meeting23:15
*** noslzzp has joined #openstack-meeting23:16
*** pcm_ has quit IRC23:18
*** ryanpetrello has joined #openstack-meeting23:19
*** vipul|away is now known as vipul23:19
*** otherwiseguy has joined #openstack-meeting23:20
*** dwcramer has quit IRC23:32
*** tomoe_ has quit IRC23:36
*** ryanpetrello has quit IRC23:37
*** anniec has joined #openstack-meeting23:39
*** mestery has joined #openstack-meeting23:40
*** lloydde has quit IRC23:40
*** salv-orlando has quit IRC23:40
*** jaypipes has quit IRC23:42
*** diogogmt has joined #openstack-meeting23:43
*** salv-orlando has joined #openstack-meeting23:44
*** markwash has quit IRC23:46
*** anteaya has left #openstack-meeting23:46
*** crank has joined #openstack-meeting23:48
*** salv-orlando has quit IRC23:52
*** noslzzp has quit IRC23:52
*** danwent has quit IRC23:53
*** ryanpetrello has joined #openstack-meeting23:54
*** gary has joined #openstack-meeting23:54
*** gary is now known as Guest3203623:55
*** danwent has joined #openstack-meeting23:56
*** Guest32036 has quit IRC23:59

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