Thursday, 2012-03-29

*** Adri2000 has quit IRC00:04
*** Adri2000 has joined #openstack-meeting00:11
*** dendrobates is now known as dendro-afk00:24
*** dendro-afk is now known as dendrobates00:24
*** dolphm has joined #openstack-meeting00:27
*** novas0x2a|laptop has quit IRC00:33
*** dtroyer is now known as dtroyer_zzz00:44
*** dolphm has quit IRC00:49
*** nati has joined #openstack-meeting00:49
*** dolphm has joined #openstack-meeting00:50
*** nati has quit IRC00:55
*** gyee has quit IRC01:11
*** Yak-n-Yeti has joined #openstack-meeting01:11
*** dolphm has quit IRC01:12
*** mdrnstm has quit IRC01:13
*** mdrnstm has joined #openstack-meeting01:22
*** sleepsonzzz is now known as sleepsonthefloor01:50
*** danwent has quit IRC02:08
*** dolphm has joined #openstack-meeting02:10
*** davlaps has joined #openstack-meeting02:18
*** reed has joined #openstack-meeting02:32
*** davlaps has quit IRC02:50
*** mtaylor has quit IRC02:54
*** dtroyer_zzz is now known as dtroyer02:58
*** jdurgin has quit IRC03:10
*** sandywalsh has quit IRC03:12
*** Yak-n-Yeti has quit IRC03:12
*** dendrobates is now known as dendro-afk03:14
*** dtroyer is now known as dtroyer_zzz03:24
*** dtroyer_zzz is now known as dtroyer03:25
*** reed has quit IRC03:31
*** sandywalsh has joined #openstack-meeting03:52
*** Lance604 has quit IRC04:09
*** davlaps has joined #openstack-meeting04:24
*** ravi has joined #openstack-meeting04:35
*** dolphm has quit IRC05:01
*** dolphm has joined #openstack-meeting05:07
*** Yak-n-Yeti has joined #openstack-meeting05:13
*** mnewby has quit IRC05:17
*** dolphm has quit IRC05:20
*** danwent has joined #openstack-meeting05:26
*** dolphm has joined #openstack-meeting05:29
*** dolphm_ has joined #openstack-meeting05:30
*** dolphm has quit IRC05:34
*** garyk has joined #openstack-meeting05:34
*** davlaps has quit IRC05:41
*** ravi has quit IRC05:45
*** mnewby has joined #openstack-meeting05:45
*** dolphm_ has quit IRC05:46
*** ravi has joined #openstack-meeting05:46
*** mnewby has quit IRC05:47
*** mnewby has joined #openstack-meeting05:48
*** danwent has quit IRC05:48
*** sleepsonthefloor is now known as sleepsonzzz06:14
*** Yak-n-Yeti has quit IRC06:18
*** dolphm has joined #openstack-meeting06:37
*** mnewby has quit IRC06:44
*** mdrnstm has quit IRC06:57
*** Lance604 has joined #openstack-meeting07:00
*** Lance604 has quit IRC07:09
*** dolphm has quit IRC07:19
*** derekh has joined #openstack-meeting08:00
*** darraghb has joined #openstack-meeting08:05
*** derekh has quit IRC09:16
*** derekh has joined #openstack-meeting09:28
*** garyk has quit IRC09:59
*** littleidea has joined #openstack-meeting11:28
*** Lance604 has joined #openstack-meeting11:34
*** littleidea has quit IRC11:51
*** markvoelker has joined #openstack-meeting12:00
*** ravi_ has joined #openstack-meeting12:08
*** ravi has quit IRC12:10
*** ravi_ is now known as ravi12:10
*** dprince has joined #openstack-meeting12:14
*** jaypipes has quit IRC12:23
*** ravi has quit IRC12:41
*** ravi_ has joined #openstack-meeting12:41
*** hggdh has quit IRC13:00
*** hggdh has joined #openstack-meeting13:05
*** sandywalsh has quit IRC13:07
*** sandywalsh has joined #openstack-meeting13:21
*** mdomsch_ has joined #openstack-meeting13:46
*** tongli has joined #openstack-meeting13:49
*** tongli is now known as Tong13:51
*** dendro-afk is now known as dendrobates13:52
*** AlanClark has joined #openstack-meeting13:57
*** troytoman-away is now known as troytoman14:01
*** sandywalsh has quit IRC14:23
*** Yak-n-Yeti has joined #openstack-meeting14:26
*** sandywalsh has joined #openstack-meeting14:38
*** Yak-n-Yeti has quit IRC14:39
*** nikhil__ has quit IRC14:49
*** uvirtbot has quit IRC14:50
*** uvirtbot has joined #openstack-meeting14:51
*** rnirmal has joined #openstack-meeting14:51
*** aclark_ has joined #openstack-meeting14:51
*** sandywalsh has quit IRC14:51
*** derekh has quit IRC14:51
*** derekh has joined #openstack-meeting14:52
*** AlanClark has quit IRC14:52
*** aclark_ has quit IRC14:54
*** aclark_ has joined #openstack-meeting14:56
*** nikhil_ has joined #openstack-meeting15:02
*** sandywalsh has joined #openstack-meeting15:05
*** GheRivero has joined #openstack-meeting15:14
*** Yak-n-Yeti has joined #openstack-meeting15:15
*** mtaylor has joined #openstack-meeting15:15
*** mtaylor has quit IRC15:16
*** mtaylor has joined #openstack-meeting15:16
*** danwent has joined #openstack-meeting15:17
*** gyee has joined #openstack-meeting15:39
*** nikhil_ has quit IRC15:43
*** nikhil_ has joined #openstack-meeting15:44
*** sleepsonzzz is now known as sleepsonthefloor15:48
*** jdurgin has joined #openstack-meeting15:57
*** aclark_ has quit IRC16:01
*** aclark_ has joined #openstack-meeting16:02
*** davidkranz_ has joined #openstack-meeting16:02
*** Carlos_Swift has joined #openstack-meeting16:03
*** Carlos_Swift has quit IRC16:04
*** fattarsi has joined #openstack-meeting16:07
*** johngarbutt has joined #openstack-meeting16:08
*** kindaopsdevy has joined #openstack-meeting16:11
*** kindaopsdevy has left #openstack-meeting16:12
*** danwent has quit IRC16:18
*** jakedahn_zz is now known as jakedahn16:20
*** jakedahn is now known as jakedahn_zz16:23
*** Gordonz_ has quit IRC16:23
*** Gordonz has joined #openstack-meeting16:24
*** dtroyer is now known as dtroyer_zzz16:24
*** jakedahn_zz is now known as jakedahn16:26
*** kindaopsdevy has joined #openstack-meeting16:26
*** dtroyer_zzz is now known as dtroyer16:35
*** dendrobates is now known as dendro-afk16:41
*** dendro-afk is now known as dendrobates16:43
*** reed has joined #openstack-meeting16:50
*** derekh has quit IRC16:52
*** bhall has joined #openstack-meeting16:53
*** bhall has quit IRC16:53
*** bhall has joined #openstack-meeting16:53
*** JoseSwiftQA has joined #openstack-meeting16:58
*** GheRivero has quit IRC16:59
*** Carlos_Swift has joined #openstack-meeting17:00
*** davidkranz__ has joined #openstack-meeting17:02
*** Gordonz has quit IRC17:02
davidkranz__Any one here for the QA meeting?17:03
*** littleidea has joined #openstack-meeting17:03
JoseSwiftQAraises hand17:03
davidkranz__Jay is on a plane and Daryl could not make it.17:03
JoseSwiftQAah well.  I have nothing to report but lack of significant progress.17:04
davidkranz__Jay's "one last time" incompatible change to the config files should be going in soon.17:04
*** esker has joined #openstack-meeting17:05
davidkranz__OK, then. I guess we will reconvene next week.17:05
JoseSwiftQAcoolbeans17:05
*** JoseSwiftQA has left #openstack-meeting17:05
*** Carlos_Swift has quit IRC17:06
esker¡Hola!  Anyone here for the nova-volume meeting?17:06
*** davidkranz__ has quit IRC17:06
eskerAh... nevermind... damned UTC conversion broke for daylight savings time... ;-)  back in an hour17:07
*** esker has quit IRC17:08
*** johngarbutt has quit IRC17:10
*** Tong has quit IRC17:13
*** debo-os has joined #openstack-meeting17:27
*** novas0x2a|laptop has joined #openstack-meeting17:40
*** darraghb has quit IRC17:43
*** novas0x2a|laptop has quit IRC17:47
*** novas0x2a|laptop has joined #openstack-meeting17:47
*** littleidea has quit IRC17:50
*** esker has joined #openstack-meeting18:00
esker!Hola! Anyone here for the nova-volume meeting?18:00
openstackesker: Error: "Hola!" is not a valid command.18:00
*** littleidea has joined #openstack-meeting18:01
eskerHi - anyone here for the nova-volume meeting?18:01
*** jdg has joined #openstack-meeting18:01
jdg#startmeeting18:04
openstackMeeting started Thu Mar 29 18:04:16 2012 UTC.  The chair is jdg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:04
jdgAnybody here?18:04
DuncanTYup18:04
*** jpb_ has joined #openstack-meeting18:04
jdgHey Duncan...18:05
eskerLikewise, here...18:05
*** mnewby has joined #openstack-meeting18:05
jdgOk, great... have a few folks18:05
*** mnewby has quit IRC18:05
jdg#topic Boot From Volume18:05
*** openstack changes topic to "Boot From Volume"18:05
*** mnewby has joined #openstack-meeting18:05
jdgSo there was pretty limited feedback from the email JDurgin sent out last week.18:06
jdgThat's good and bad I suppose, means less controversary18:06
eskerCould you forward to esker@netapp.com.... I don't seem to have the email in question.18:07
jdgI propose we polish up his use cases get something a little more concrete and send it out18:07
jdgesker: sure18:07
eskerthanks18:07
DuncanTI didn't see said email either18:07
DuncanTduncan.thomas@hp.com18:07
jdgAnyone else before I hit send?18:08
jdgGoing once, twice....18:08
jdgSent18:08
*** mdrnstm has joined #openstack-meeting18:08
eskerIt seems the list established for communication on this topic isn't used so much.18:09
eskeropenstack-volume@lists.launchpad.net18:09
jdgesker: Good point, I think folks stopped using the sub-lists18:09
jdgWe discussed at the last meeting doing the subset first before the onslaught from the overall community18:09
jdgI propose we clean it up over the next day or two and send it to the entire Openstack list18:10
jdgParticularly inputs from DuncanT and esker would be good.  I plan to add some detail to it later today or tomorrow morning18:11
DuncanTI certainly see no problems with John's use-cases18:11
jdgI think there are more that could be added,  but at least this will be a starting point18:11
DuncanTI've a couple more possibilities to add18:11
jdg:)18:12
jdgDuncanT:  Good... do you want to go through them here or add them and send via email?18:12
*** ravi has joined #openstack-meeting18:12
DuncanTProbably via email is easiest, I don't think they are either contentious or incompatable with John's, they are mostly just fleshed out life-cycles18:13
jdgOk, sounds good...18:13
jdgSo is there anything we need/want to talk about on this topic right now?18:13
jdgOk... I wanted to talk about the summit real quick18:14
jdg#topic Folsom Summit18:14
*** openstack changes topic to "Folsom Summit"18:14
jdgAny folks here planning to attend?18:14
*** dolphm_ has joined #openstack-meeting18:14
*** dolphm_ has quit IRC18:14
eskerI think there's a case to be made for Glance modification so that references to "persistent" bootable volumes are understood... and to avoid copying out from Glance when something might already be available18:15
jdgI'd like to see some propsals for the Nova-Volume tracks18:15
DuncanTTimR and I are planning to attend18:15
eskerSo... go to glance to get image RHEL whatever w/ appstack  whatever... Glance says... well, there's something like that over here already.18:15
eskerI'll broach that via email.18:16
jdgesker: Sounds good, write some ideas up and send it18:16
DuncanTesker: We've been debating that internally quite a lot... interested in hearing other views before I detail my thoughts18:16
jdgDo we want to talk more here?18:16
*** dolphm_ has joined #openstack-meeting18:16
DuncanTI'd like to hear the case for making glace aware of bootable volumes18:17
DuncanTDon't mind if it is here or via email18:17
jdgesker: DuncanT: are you proposing using a "nova volume" as backend storage for Glance as well as primary storage for instances?18:17
eskerEssentially18:18
jdgThat's a use case I've thought of and would like to make work as well18:18
DuncanTI have proposed that, but then realised it isn't actually necessary18:18
jdgDuncanT: why is that?18:18
jdgThere are advantages to having Glance images and instances on the same device18:19
DuncanTWe can (in our case) use the fact that a glace image has a persistent and never-reused ID to cache the glace image on first use, transparently to glance and without needing to modify glance18:19
jdgDoesn't have to be the same volume of course, but the same device18:19
DuncanTI'm not necessarily against making glance volume-aware, just that it isn't necessarily necessary18:20
jdgSo you're just caching the image on your device regardless?18:20
jdgThat's great for you :)18:20
DuncanTjdg: Not caching yet, but realised we could18:21
DuncanTHence being interested in other points of view18:21
jdgDuncanT: cool... from my perspective I'm looking at the similar use case18:21
jdgThe difference is I need to be able to use the same device/appliance18:22
jdgOr at least that's what I want18:22
jdgDifferent volumes on the same device18:22
*** jakedahn is now known as jakedahn_zz18:23
eskerDuncanT...  is the scheme you described predicated on using something other than an object store to back Glance?18:23
jdgTBH I don't know much about Glance yet and what the possibilities are for configuring backend storage18:23
DuncanTesker: No, I don't believe so18:24
jdgDuncanT: If I understand correctly you're saying you'll just cache the image when you create an instance....18:24
jdgThen you don't care where it came from correct?18:24
DuncanTCorrect18:24
jdgYou'll have it in cache based on uuid so any time it gets used again you just pull it from your cache18:25
DuncanTSpot on18:25
DuncanTWe actually use COW layers so we don't even need to copy, but that is an optimisation18:25
jdgWhat does that require in terms of driver/extension work?18:25
jdgAhhh18:25
DuncanTIt requires your volume backend to have some sort of table of imageid to cached copy mapping, and probably a way of aging out cached copies that haven't been referenced for some time18:26
*** littleidea has quit IRC18:27
jdgSo you'd still need some sort of tie in to override pulling the image from Glance and using your cached copy instead correct?18:27
eskerThat's what I'm thinking through18:27
DuncanTThere's a bit of messing needs doing to get nova-compute to let you know it is copying down an image, which I haven't fully figured yet, but it looks like you can make that layer pluggable / overridable and default to the current behaviour18:28
eskerHow do you prevent new instances querying Glance and getting back a glance response... instead of a "I'm cached here" response18:28
eskerah, okay18:28
jdgDuncanT: I like the idea, I'm trying to figure out how to generalize it18:29
jdgSo it might look something like this:18:29
jdgThe volume driver implementated has like a cache volume on it18:30
DuncanTThere is already code in nova-compute that knows when an image is cached for ephemeral (local) volumes18:30
jdgAny time an instance is pulled from Glance and created on the device it stores the glance image in that cache volume18:30
jdgDuncantT:  Oh...18:30
jdgI'm still torn though, I'd like to have the ability to specify block storage for Glance back-end storage18:31
*** ravi has quit IRC18:31
jdgI think both cases are good/useful18:31
jdurginhi guys, sorry I'm late18:32
DuncanTWhat does doing it explicitly gain you?18:32
jdgDuncanT: One copy of the Glance image instead of two18:32
DuncanTYup, ok, I can buy that18:33
jdgWe start getting into vendor specific behaviors so I don't want to push too hard18:33
jdurginDuncanT: having the same backing store for glance as for volumes allows you to do CoW too18:33
jdgBut in my case then you take advantage of things like dedupe, internal copy capabilities etc18:33
DuncanTI think as long as using block store as a glance backend doesn't stop you using it as a normal glance store (i.e. still supports pull over http and similar) it's a fine idea18:34
*** littleidea has joined #openstack-meeting18:34
jdgDuncanT: Yes, I would not propose taking away capabilities, just adding18:34
jdgI need to talk with Glance folks to get an idea of what's possible and how much investment it would take18:35
eskerWHo's PTL on Glance?18:35
jdurginwe wrote a glance backend for rbd in september18:35
DuncanTCertainly I'd be interested in hearing the answers18:35
jdgJayPipes18:35
jdurginit was pretty simple18:35
jdurginptl is actually Brian Waldon now18:35
jdgjdurgin: Thanks forgot about the last election18:36
jdgjdurgin: Did you submit something in the core Glance code or is it a custom deal?18:37
jdurginno, it was upstream as soon as I wrote it18:37
jdurginyou might be able use glance's existing filesystem backend though, not sure what level of customization you'd need18:38
jdgjdurgin: thanks, think I stumbled across it18:38
*** debo-os has quit IRC18:40
jdgjdurgin: So this uses some ceph components to implement object store on top of a Block  Dev?18:40
jdgOr am I missing something18:41
jdurginyeah, rbd stripes objects across ceph's object storage layer, RADOS18:41
*** jakedahn_zz is now known as jakedahn18:41
jdgDid you notice any significant performance hits or anything?18:42
jdurginI haven't benchmarked other glance backends really18:43
jdgjdurgin: Ok, just curious... probably irrelevant18:43
jdgSo that's good, it sounds like my use case is pretty much covered so that leaves the one DuncanT proposed18:44
jdgesker: DuncanT: do you agree?18:44
DuncanTIf you're using a block store backend, don't you still need to make some changes to stop nova-compute pulling the copy over http anyway? Or am I missing something?18:44
jdurginDuncanT: yeah, that part still needs work18:45
jdgDuncanT: I would assume yes18:45
*** littleidea has quit IRC18:45
jdurginbut I have to run now, see you guys later18:45
eskerwouldn't the modification consist of:  don't pull anything, boot from volume18:46
DuncanTAs long as that is plugable, I think my usecase just falls out as a subset of yours18:46
jdgDuncanT: That's what I'm thinking18:46
jdgesker: No, you can't boot from the Glance side18:46
*** aclark_ is now known as AlanClark18:46
DuncanTesker: I assume there would be some call out so that the block storage system can make the volume ready to be used? You don't want to mess up your golden cached copy18:46
eskeryep... which would clone from golden18:47
eskerusing CoW or other pointer tricks18:47
jdgesker:  so I think we're all on the same page.  As DuncanT said if it's pluggable we just do the transfer internally via our driver18:48
jdgWhether that be using CoW or whatever... shouldn't necessarily matter18:48
eskerright18:48
eskerthat's up to you...18:48
jdgSo if we spin out block storage as a seperate project/api we can tie all of this together rather neatly I believe18:49
jdgOf course we could do it either way, but I like clean seperation :)18:50
DuncanTIt would be nice if 'local' volumes in nova were provided by the block store service too, it would mean much of this code was common...18:50
jdgDuncanT: My point exactly18:50
eskerSo is that topic in scope for today's meeting?  The spinout?18:51
jdgI've been avoiding that topic because I know Vish has some ideas already... but we can surely talk about it folks are interested18:51
*** kindaopsdevy has quit IRC18:51
jdgWe're going to run out of time I'm afraid18:51
DuncanTI think we're starting to get a feel for what we want out of the spinout18:52
eskerOh... well no point in colliding w/ Vish on this.  Perhaps we can invite him next week to discuss?18:52
*** jakedahn is now known as jakedahn_zz18:52
jdgDuncanT: Yes, I agree18:52
jdgI was hoping to start tackling the spin out idea during the summit18:52
jdgWhich brought up the topic of "Folsom Summit"18:52
DuncanTI was hoping there'd be some poking of it in the meetings before the sumit so people aren't so much thinking on their feet... I suspect it will be a long discussion at the summit18:53
jdgDuncanT: Yes, I agree...  so how about this:18:53
jdgNext meeting we start the converstation?18:53
jdgGet some sort of foundation started so we can be effective at the Summit?18:54
DuncanTSeems sensible to me18:54
jdgI think there's plenty to talk about regarding use cases and high level architecture without getting stuck if somebody has something in progress already18:54
DuncanTThere'll also be a BFV blueprint kicking round next week from us, and that ends up tying into the volume-as-a-service in several ways18:55
jdgDuncanT: Sounds great, I'll keep my eyes open for it18:55
jdgI'll also clean up JDurgin's email and add what we talked about today as a seperate section18:56
jdgAs far as the Summit goes I'd still like some input if folks have it.  Otherwise I'll propose sessions for spin out, boot from volume/snap-shot etc18:56
jdgWe may be passed the point of brainstorming so they'd be presentation or workshop slots18:57
DuncanTI don't mind who proposes sessions, as long as they happen ;-)18:57
jdg:)18:57
jdgOk, just want to make sure I'm not the only one sitting in the room and that I'm not missing topics people want to discuss :)18:58
jdgAlright, well if nobody has anything else for now?18:58
DuncanTI'll check with the rest of my team here and make sure we have a list of what we'd like sessions on... there is a lot of overlap between things that need discussing18:59
jdgDuncanT: Excellent, you can either put it on the website or send it to me directly18:59
DuncanTWill do18:59
jdgAlright, well we're out of time.  Thanks for showing up guys!!19:00
jdg#end meeting19:00
jdg#endmeeting19:01
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"19:01
openstackMeeting ended Thu Mar 29 19:01:08 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-29-18.04.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-29-18.04.txt19:01
DuncanTThanks19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-29-18.04.log.html19:01
eskerThanks19:02
*** esker has quit IRC19:02
*** maoy has joined #openstack-meeting19:03
*** jdg has quit IRC19:06
maoyhello?19:15
*** mdrnstm has quit IRC19:15
maoyanyone here for the nova-orchestration meeting?19:15
*** mdrnstm has joined #openstack-meeting19:15
*** jpb_ has quit IRC19:24
dolphm_maoy: i think you've got another ~24 minutes for that19:35
*** dendrobates is now known as dendro-afk19:49
*** n0ano has joined #openstack-meeting19:53
maoydolphm_: thanks19:56
*** mikeyp has joined #openstack-meeting19:57
dolphm_maoy: 3 minutes now :)19:57
mikeypmikeyp is getting coffee19:59
*** mdrnstm has left #openstack-meeting20:00
n0anoAnyone here for the Orchestration meeting?20:00
maoyI am20:01
maoyhi all20:01
n0ano#startmeeting20:01
openstackMeeting started Thu Mar 29 20:01:45 2012 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:01
n0anomaoy, do you have an open for today, I don't have anything specific myself.20:02
maoycould someone give me the link for previous meetings log?20:02
maoyI'd like to discuss how to merge/collaborate on related orchestration blueprints20:03
mikeyp#link http://wiki.openstack.org/Orchestration/MeetingLogs20:03
maoyespecially at the summit20:03
n0ano#topic orchestration blueprints for the Summit20:04
*** openstack changes topic to "orchestration blueprints for the Summit"20:04
maoythere is this one https://blueprints.launchpad.net/nova/+spec/transaction-orchestration20:04
n0anoI know that sriram (looks like he won't make the meeting today) is proposing a BP, then there's that one, are the any others?20:05
maoyand also this one proposed from me20:05
maoyhttps://blueprints.launchpad.net/nova/+spec/task-management20:05
maoyIn the wiki from this bp: http://wiki.openstack.org/TransactionalTaskManagement20:06
maoyseveral related BPs are listed20:06
maoymikeyp: thx20:06
n0anoindeed, seems like we should try an consolidate the orchestration BPs into one discussion at the Summit20:07
mikeypand of course, the main 'orchestration link on the wiki http://wiki.openstack.org/NovaOrchestration20:07
maoydo we know how long timeslot we'll get at the summit?20:08
maoythere seems to be way too many proposals for the summit20:08
mikeyphas anyone even proposed something for the summit yet - I haven't20:08
n0anoI'm no expert, who/how is the summit schedule decided, does anyone know?20:08
n0anosriram definitely wanted to propose something for the summit, it's a pity he can't be here today20:09
maoyhttp://summit.openstack.org/sessions/view/6920:09
maoyI wanted to propose one, but after I saw this one I want to work with folks here together20:10
*** dprince has quit IRC20:10
mikeypwe need to poporse a summit session to get feedback, and we also need to spend time before that consolidating the existing work and ideas20:11
maoyabsolutely.20:11
maoyhas anyone started coding towards the bps?20:11
n0anolooks like the session is proposed, what else needs to be done to get it on the schedule20:12
mikeypsriram said he was going to propose a branch soon20:12
n0anohe said hopefully by the end of this week he'd create the branch20:13
maoythat's promising20:14
mikeypI believe there are two pieces to this20:16
*** dendro-afk is now known as dendrobates20:16
mikeyp1. the transaction management / workflow service20:16
mikeyp2. changes to Nova to leverage that service20:17
mikeypmake sense ?20:17
n0anomaybe, are seeing this as a new service (ala Glance) or more like just changes to Nova20:18
maoysure20:18
maoyIt seems to be very nova centric20:18
mikeypwas thinking a nova service initially, ala nova-compute, nova-network, et al20:19
mikeypbut a higher level service isn't out of the question20:19
maoyagree. but making it a separate component seems not a top priority to me20:19
maoybut no doubt that it will be utilized by many sub nova components, such as nova-compute, nova-sched, nova-volume20:20
n0anoI kind of like the idea of a separate component, that compartmentalizes things and makes it potentially usable by different areas.20:20
mikeypmy reasoning is mainly driven by how to do this, without having to sync up with the main nova branch all the time during development20:21
maoye.g. right now there are cross component race conditions that not addressed20:21
n0anowhen you talk about `changes to Nova' isn't that really just defining the APIs to be used?20:21
mikeypn0ano: I think there will be changes within nova to call those api's as well.20:23
maoymikeyp: the devil will be revising current nova code to use the orchestration APIs20:23
*** jdg has joined #openstack-meeting20:23
*** jdg has quit IRC20:23
maoywill have to work closely with nova-core folks on that20:23
mikeypmaoy: yup - I agree.20:23
n0anogiven the right set of APIs (hopefully ones that don't change much) then changes to nova can be done once and further development is in the service20:24
*** jdg has joined #openstack-meeting20:24
*** jdg has left #openstack-meeting20:24
maoyi sense some reluctant reaction from them in adopting this idea. nova-core is a big monster with 100K lines of code. :)20:24
*** jakedahn_zz is now known as jakedahn20:25
mikeypn0ano: maybe - depends on how and where  specific workflows are defined and stored20:25
n0anoit's possible that we can move some of the nova-core code into the orchestration service, reduing the size of nova-core (in a perfect world of course)20:25
mikeypwhat about swift and glance integration ?20:27
maoyi'm very unfamiliar with swift and glance. do they have tasks/workflows to orchestrate?20:27
mikeypcurrently I believe nova calls out to swift for images.20:27
mikeypwould that operation now be done from orchestrator ?20:28
mikeypmaoy: not really, but they are involved in nova operations20:28
maoyI believe it's to the glance image service?20:28
mikeypmy bad - meant glance20:28
maoyI believe orchestration is best to define control plane state transition. are you saying we want to get involved with the data path of glance as well?20:30
mikeypmaoy: definitely not20:30
n0anowell, who's driving things then, is nova-core scheduling/creating/destroying tasks, utilizing orchestration services for serialization, or is everything driven through the orchestration service?20:30
n0ano(my vision would be the first alternatvie)20:31
mikeypn0ano: that is the question I"m asking20:31
n0anowell, to me nova-core does the work, asking for help from orchestration when needed.20:32
*** jakedahn is now known as jakedahn_zz20:32
n0anoThat way the orchestration service is also available to other components if they need it.20:32
maoyagree.20:32
maoythe orchestration service should be purely state management, including workflow progress, status, resource lock management, etc20:33
maoybut we'll provide client side APIs to easily utilize the service20:34
n0anothat would work for me20:34
mikeypI also agree that is the right approach20:35
maoyexcellent20:35
n0ano#agreed orchestration service provides state management with client side APIs20:36
maoyin the wiki I posted, it talked a bit about the APIs. I have a simple, half-baked MySQL based implementation.20:36
maoysome APIs make sense, some perhaps don't20:36
maoyI was hoping to use ZooKeeper to implement the service side20:37
n0anoI think an API discussion would be a good topic at the summit20:37
maoybut that'd introduce another new external dependency. not sure if people like it20:37
n0anothe counter is why re-invent the wheel, it ZooKeeper does what we want we should use it (note I know nothing about it)20:38
maoyAPI design and where to store orchestration state are great topics to discuss..20:39
mikeypmaoy: discuss at the summit ?20:40
n0ano#idea add API design and state storage as topics for the orchestration session at the Summit20:40
maoymikepy: yeah. that's what i meant20:41
n0anoI agree20:41
maoyof course it's the best if we have something in mind before summit. :)20:41
n0anoindeed, some sort of template to start from20:41
mikeypI think another topic is the implementation plan - how we do openheart surgery on nova while folsom development is running full steam ahead20:42
maoyabsolutely20:42
maoythat seems to be the biggest blocker..20:43
n0ano#idea implementation plan as session topic20:43
maoywe need someone from the nova core team to be onboard20:43
n0anohence the need for a session where we can get wider coverage20:43
mikeypwho will update the session proposal - I think sriramhere, because he proposed / has edit permissions20:47
maoyagree20:48
maoylet's ping him via email..20:48
n0anoI'll send sriram an email and see if he's willing, shouldn't be a problem20:48
maoycool20:48
n0ano#action sriram to update the Orchestration session proposal20:48
n0ano(I won't comment on giving ARs to non-attendees who can't defend themselves :-)20:49
mikeypAlso, Sandy metioned the efforts by HP and IBM re: HPC scheduling, and some thoughs from RedHat20:51
maoyhopefully orchestration service should be scheduler (algorithm) agnostic20:51
n0anoyeah, I saw that, i'd be interested in the details on that but, without Sandy being here ...20:51
mikeypmaoy: true, but I'm in the dark about those efforts and ideas.20:52
maoymikeyp: me 220:52
maoydo we have links for those?20:52
maoyi didn't see Sandy's email20:52
n0anomaoy, I'll forward it to you, but there's not much detail in it.20:53
maoyok cool20:53
mikeypBTW, procedural point: we'r supposed to be using the main list with a prefix of [Orchestration], rather than the independent mailing list20:54
n0ano#action n0ano to forward Sandy's email to maoy20:54
mikeypthat was decided rounde begninng of the year, I think.20:54
mikeypand other  items for today ?20:55
n0anomikeyp, looks like we missed that, we'll try and be better in the future.20:55
n0anonothing else from me20:55
maoynot from me20:55
maoytake care guys20:55
n0anoOK, let's maybe discuss the details of the Orchestration session in a little more detail next week, think about it in the meantime.20:56
mikeypthats all from me for today.20:57
n0anolater everyone20:57
n0ano#endmeeting20:57
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:57
openstackMeeting ended Thu Mar 29 20:57:28 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-29-20.01.html20:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-29-20.01.txt20:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-29-20.01.log.html20:57
*** novas0x2a|laptop has quit IRC20:58
*** maoy has quit IRC20:59
*** dolphm_ has quit IRC20:59
*** mikeyp has left #openstack-meeting21:00
*** dolphm has joined #openstack-meeting21:01
*** novas0x2a|laptop has joined #openstack-meeting21:05
*** markvoelker has quit IRC21:06
*** dwcramer has joined #openstack-meeting21:14
*** dwcramer has quit IRC21:26
*** jakedahn_zz is now known as jakedahn21:30
*** dolphm has quit IRC21:30
*** jakedahn is now known as jakedahn_zz21:31
*** dolphm has joined #openstack-meeting21:31
*** dwcramer has joined #openstack-meeting21:34
*** dcramer_ has joined #openstack-meeting21:38
*** dcramer__ has joined #openstack-meeting21:41
*** dwcramer has quit IRC21:42
*** AlanClark has quit IRC21:43
*** dcramer_ has quit IRC21:44
*** jakedahn_zz is now known as jakedahn22:07
*** danwent has joined #openstack-meeting22:10
*** jakedahn is now known as jakedahn_zz22:12
*** Yak-n-Yeti has quit IRC22:24
*** sandywalsh has quit IRC22:28
*** jakedahn_zz is now known as jakedahn22:32
*** dcramer__ has quit IRC22:38
*** bhall has quit IRC22:56
*** sandywalsh has joined #openstack-meeting22:57
*** rnirmal has quit IRC23:00
*** davidkranz_ has quit IRC23:08
*** mnewby_ has joined #openstack-meeting23:17
*** mnewby_ has quit IRC23:17
*** mnewby has quit IRC23:18
*** troytoman is now known as troytoman-away23:34
*** littleidea has joined #openstack-meeting23:43
*** jakedahn is now known as jakedahn_zz23:44
*** dwcramer has joined #openstack-meeting23:57

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