Thursday, 2012-04-12

*** littleidea has joined #openstack-meeting00:02
*** anotherjesse_zz is now known as anotherjesse00:11
*** anotherjesse is now known as anotherjesse_zz00:12
*** dolphm has joined #openstack-meeting00:28
*** joearnold has quit IRC00:34
*** patelna has quit IRC00:37
*** Yak-n-Yeti has joined #openstack-meeting00:55
*** dwcramer has joined #openstack-meeting01:03
*** dolphm has quit IRC01:05
*** dolphm has joined #openstack-meeting01:09
*** ywu has joined #openstack-meeting01:18
*** danwent has quit IRC01:35
*** mnewby has quit IRC01:37
*** dprince has joined #openstack-meeting01:40
*** novas0x2a|laptop has quit IRC01:42
*** soren has quit IRC01:45
*** ohnoimdead has quit IRC01:46
*** soren has joined #openstack-meeting01:46
*** ohnoimdead has joined #openstack-meeting01:46
*** dolphm has quit IRC01:55
*** dwcramer has quit IRC02:02
*** dwcramer has joined #openstack-meeting02:03
*** dprince has quit IRC02:06
*** reed has quit IRC02:09
*** ywu has quit IRC02:11
*** jakedahn is now known as jakedahn_zz02:18
*** ayoung has quit IRC02:20
*** shang has joined #openstack-meeting02:21
*** novas0x2a|laptop has joined #openstack-meeting02:34
*** dwcramer has quit IRC02:46
*** dwcramer has joined #openstack-meeting03:01
*** novas0x2a|laptop has quit IRC03:11
*** novas0x2a|laptop has joined #openstack-meeting03:11
*** milner has quit IRC03:25
*** sandywalsh has quit IRC03:26
*** milner has joined #openstack-meeting03:39
*** joearnold has joined #openstack-meeting03:48
*** dwcramer has quit IRC03:52
*** littleidea has quit IRC04:02
*** littleidea_ has joined #openstack-meeting04:02
*** shang has quit IRC04:13
*** deshantm has quit IRC04:28
*** reed has joined #openstack-meeting04:38
*** joearnold has quit IRC04:38
*** lloydde has joined #openstack-meeting04:45
*** reed has quit IRC04:51
*** dhellmann has quit IRC04:52
*** dhellmann has joined #openstack-meeting04:52
*** joearnold has joined #openstack-meeting05:01
*** Yak-n-Yeti has quit IRC05:10
*** joearnold has quit IRC05:30
*** littleidea has joined #openstack-meeting05:55
*** shwetaap has joined #openstack-meeting05:56
*** ozstacker has joined #openstack-meeting05:57
*** shwetaap_ has joined #openstack-meeting05:57
*** littleidea_ has quit IRC05:58
*** shwetaap has quit IRC06:00
*** shwetaap_ is now known as shwetaap06:00
*** lloydde has quit IRC06:53
*** lloydde has joined #openstack-meeting06:53
*** lloydde has quit IRC06:58
*** ozstacker has quit IRC07:11
*** littleidea has quit IRC07:13
*** ozstacker has joined #openstack-meeting07:14
*** GheRivero has quit IRC07:32
*** derekh has joined #openstack-meeting07:59
*** ghe_ has joined #openstack-meeting08:12
*** darraghb has joined #openstack-meeting08:19
*** ghe_ is now known as GheRivero08:25
*** shang has joined #openstack-meeting09:09
*** dwcramer has joined #openstack-meeting11:46
*** sandywalsh has joined #openstack-meeting12:03
*** _ozstacker_ has joined #openstack-meeting12:23
*** ozstacker has quit IRC12:25
*** dwcramer has quit IRC12:25
*** dolphm has joined #openstack-meeting12:27
*** dprince has joined #openstack-meeting12:35
*** eglynn has joined #openstack-meeting12:37
*** markvoelker has joined #openstack-meeting12:40
*** ryanpetrello has quit IRC12:41
*** eglynn has quit IRC12:42
*** eglynn has joined #openstack-meeting12:44
*** dhellmann_ has joined #openstack-meeting12:49
*** dhellmann_ has quit IRC12:51
*** dhellmann has quit IRC12:51
*** dhellmann has joined #openstack-meeting12:52
*** dhellmann has quit IRC12:52
*** ozstacker has joined #openstack-meeting13:07
*** _ozstacker_ has quit IRC13:08
*** pengyong has joined #openstack-meeting13:10
*** dwcramer has joined #openstack-meeting13:25
*** ttrifonov has joined #openstack-meeting13:27
*** ttrifonov_zZzz has joined #openstack-meeting13:28
*** ttrifonov_zZzz is now known as ttrifonov13:28
*** ayoung has joined #openstack-meeting13:29
*** deshantm has joined #openstack-meeting13:43
*** mdomsch has joined #openstack-meeting13:44
*** lloydde has joined #openstack-meeting13:50
*** mattray has joined #openstack-meeting13:52
*** lloydde has quit IRC13:59
*** zul has quit IRC14:01
*** zul has joined #openstack-meeting14:02
*** chuck_ has joined #openstack-meeting14:02
*** lloydde has joined #openstack-meeting14:07
*** ryanpetrello has joined #openstack-meeting14:11
*** lloydde has quit IRC14:13
*** zul has quit IRC14:14
*** chuck_ is now known as zul14:14
*** zul has quit IRC14:14
*** zul has joined #openstack-meeting14:14
*** chuck_ has joined #openstack-meeting14:15
*** zul has quit IRC14:19
*** chuck_ is now known as zul14:19
*** GheRivero_ has joined #openstack-meeting14:23
*** Yak-n-Yeti has joined #openstack-meeting14:30
*** deshantm has quit IRC14:39
*** Yak-n-Yeti has quit IRC14:43
*** dtroyer is now known as dtroyer_zzz14:51
*** deshantm has joined #openstack-meeting14:52
*** rnirmal has joined #openstack-meeting15:00
*** reed has joined #openstack-meeting15:06
*** kindaopsdevy has joined #openstack-meeting15:07
*** kindaopsdevy has left #openstack-meeting15:07
*** dtroyer_zzz is now known as dtroyer15:12
*** jog0 has joined #openstack-meeting15:14
*** jog0 has left #openstack-meeting15:14
*** dendrobates is now known as dendro-afk15:16
*** dendro-afk is now known as dendrobates15:18
*** Yak-n-Yeti has joined #openstack-meeting15:24
*** lloydde has joined #openstack-meeting15:35
*** danwent has joined #openstack-meeting15:36
*** deshantm has quit IRC15:44
*** nati has joined #openstack-meeting15:46
*** ryanpetrello has quit IRC15:47
*** shwetaap has quit IRC15:55
*** AlanClark has joined #openstack-meeting16:02
*** dendrobates is now known as dendro-afk16:14
*** dendro-afk is now known as dendrobates16:17
*** mattray has quit IRC16:19
*** mattray has joined #openstack-meeting16:20
*** dwcramer has quit IRC16:27
*** gyee has joined #openstack-meeting16:30
*** dendrobates is now known as dendro-afk16:33
*** dendro-afk is now known as dendrobates16:36
*** ryanpetrello has joined #openstack-meeting16:39
*** mdomsch has quit IRC16:46
*** GheRivero_ has quit IRC16:50
*** davidkranz_ has joined #openstack-meeting16:59
jaypipes#startmeeting17:00
openstackMeeting started Thu Apr 12 17:00:39 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.17:00
jaypipesmorning all.17:00
jaypipesor afternoon. :)17:00
davidkranz_Hi there.17:00
jaypipesdavidkranz_: heya17:01
jaypipesdavidkranz_: been kinda swamped this week and haven't been able to get the tempest devstack gate job completed. did debug it and make progress, but still need someone to push through some devstack and devstack-gate merge proposals. :(17:02
davidkranz_I understand. Some times this environment can feel like molasses.17:03
jaypipesdavidkranz_: need to get the final fix in for https://review.openstack.org/#change,630117:03
jaypipesdavidkranz_: indeed.17:03
jaypipesdavidkranz_: anything you want to discuss today?17:03
davidkranz_Just one thing.17:03
davidkranz_I think we should file a bug for any ERROR in the logs that does not represent an OpenStack bug or operator error or problem.17:04
davidkranz_What do you think?17:04
jaypipes+17:04
jaypipessorry, typo.17:04
jaypipesyes, I definitely agree with that. as I've gotten more experience operating trystack and running devstack + tempest I would really appreciate little things like that!17:05
davidkranz_OK, I will push on that at the devops sessions next week. We need the PTLs to buy in and establish conventions for the meaning of log files.17:06
davidkranz_So they can be both human and machine readable as needed.17:06
davidkranz_And we need a stable/essex tempest branch. There are already some differences needed.17:07
jaypipesdavidkranz_: ah, crap, yes... I will submit a ticket.17:07
davidkranz_jaypipes: Perhaps all PTLs should have to operate trystack for a few days :)17:08
jaypipesdavidkranz_: https://bugs.launchpad.net/openstack-ci/+bug/98007117:08
uvirtbotLaunchpad bug 980071 in openstack-ci "Tempest needs stable/essex branch" [Undecided,New]17:08
davidkranz_OK, great.17:08
jaypipesdavidkranz_: lol. I wouldn't wish that on the PTLs ;P17:08
jaypipesdavidkranz_: maybe once Essex is done for TryStack...17:08
*** derekh has quit IRC17:09
davidkranz_I don't have anything else right now.17:10
*** shwetaap has joined #openstack-meeting17:11
jaypipesdavidkranz_: alright, let's wrap it up then17:11
jaypipes#endmeeting17:11
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"17:11
openstackMeeting ended Thu Apr 12 17:11:46 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-17.00.html17:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-17.00.txt17:11
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-17.00.log.html17:11
*** davidkranz_ has quit IRC17:12
*** zigo has joined #openstack-meeting17:33
*** zul has quit IRC17:41
*** novas0x2a|laptop has quit IRC17:42
*** zul has joined #openstack-meeting17:42
*** reed has quit IRC17:50
*** ryanpetrello has quit IRC17:51
*** ryanpetrello has joined #openstack-meeting17:51
*** mnewby has joined #openstack-meeting17:56
*** mattray has quit IRC17:57
*** darraghb has quit IRC17:59
*** pengyong has quit IRC18:01
jgriffith#startmeeting18:02
openstackMeeting started Thu Apr 12 18:02:28 2012 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:02
jgriffithHey folks!18:02
jgriffithAnybody show up today?18:03
DuncanTI'm here18:03
jgriffithDuncanT: I can always count on you  :)18:03
*** jbrogan has joined #openstack-meeting18:03
DuncanTNothing to talk about though... saving it all for next week18:03
jgriffithDuncanT: I was going to hit you up to doa  presentation on the Glance backend work you did18:04
jgriffithRan out of time slots though...18:04
jgriffithWould you be interested in doing something in an unconference session maybe?18:04
DuncanTjgriffith: It wasn't me that got anything there working18:04
jgriffithOh?18:04
jgriffithMy bad...  It must've been JDurgin18:05
DuncanTSomebody certainly said they had last week18:05
jgriffithPofa18:05
jdurginoh, I'm here18:05
DuncanTI bought up the topic and had some musings, but nothing concrete18:05
jgriffithjdurgin: Was it you that mentioned the glance/ceph work last week?18:05
jdurginyeah18:06
jgriffithAhh... sorry, confused that with DuncanT18:06
jdurginno worries18:06
jgriffithDid you see my question about the conference?18:06
jdurginyeah, I'm not sure there's much to talk about it - it's pretty simple18:07
jgriffithjdgurgin: Ok.... just a thought18:07
jdurginbut if people are interested I'm happy to discuss it18:07
jgriffithWas actually thinking more along the lines of setting it up/using it18:07
jgriffithMaybe spin up devstack on some lap-tops and make it dance or something18:07
jgriffithNo big deal, just a thought18:08
jgriffithOk, well I don't know if anybody has much going on today....18:08
jgriffithMostly getting ready for next week on my side18:08
jgriffithThe volume UUID migration is pretty much done but I have 3 tests that are kicking my butt18:09
jgriffithOther than that, all of the Volume tracks are on sched.org18:10
jgriffithAnd the etherpads have been created and linked on the wiki page18:10
jgriffithhttp://wiki.openstack.org/FolsomSummitEtherpads18:11
jgriffithGuess we'll call it a short meeting18:11
jdurgincool, see you next week18:12
*** novas0x2a|laptop has joined #openstack-meeting18:12
DuncanTLooking forward to it18:12
jgriffithYeah, it'll be great to meet everybody face to face.18:12
jgriffithTravel safe and see ya Monday!!18:13
jgriffith#endmeeting18:13
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"18:13
openstackMeeting ended Thu Apr 12 18:13:29 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-18.02.html18:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-18.02.txt18:13
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-18.02.log.html18:13
*** jbrogan has quit IRC18:17
*** mdrnstm has joined #openstack-meeting18:34
*** esker has joined #openstack-meeting18:34
*** reed has joined #openstack-meeting18:37
*** ryanpetr_ has joined #openstack-meeting18:41
*** ryanpetrello has quit IRC18:44
*** dwcramer has joined #openstack-meeting18:45
*** zul has quit IRC18:45
*** zul has joined #openstack-meeting18:46
*** darraghb has joined #openstack-meeting18:53
*** darraghb has quit IRC19:01
*** adjohn has joined #openstack-meeting19:06
*** dwalleck has joined #openstack-meeting19:06
*** de_ has quit IRC19:09
*** mattray has joined #openstack-meeting19:12
*** de_ has joined #openstack-meeting19:13
*** sriramhere has joined #openstack-meeting19:23
*** dprince has quit IRC19:30
*** sandywalsh has quit IRC19:37
*** dendrobates is now known as dendro-afk19:37
*** nati has quit IRC19:39
*** dendro-afk is now known as dendrobates19:39
*** mdomsch has joined #openstack-meeting19:39
*** ryanpetr_ has quit IRC19:44
*** maoy has joined #openstack-meeting19:51
*** troytoman-away is now known as troytoman19:55
*** n0ano has joined #openstack-meeting20:01
n0anohello all, anyone here for the orchestration meeting?20:02
sriramheren0ano, me here20:02
maoyhi20:02
n0ano#startmeeting20:02
openstackMeeting started Thu Apr 12 20:02:34 2012 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:02
n0ano#topic get ready for the session next week20:02
*** openstack changes topic to "get ready for the session next week"20:02
*** ryanpetrello has joined #openstack-meeting20:03
n0anoSo, sriramhere (since you did all the work) are we ready for the session next week?20:03
sriramherelooks like Ziad has some notes on SpiffWorkflow20:03
sriramherei couldnt make much progress on SWF mock :( - pressure to deliver some work before i take a week off for the summit20:04
sriramheremaoy - any updates on ur side?20:04
sriramhereZiad's notes: http://wiki.openstack.org/NovaOrchestration/WorkflowEngines/SpiffWorkflow20:04
maoyi'm preparing another session on concurrency20:05
maoybut i'd like to present a few slides during the session if possible20:05
maoyi mean the orchestration session20:05
n0anoI would imagine that should be fine, sriramhere do you have slides you'll present?20:06
maoywhat's the format of our session?20:06
maoydo we have an agenda?20:06
sriramherei am putting some intro/ explaining current thought processes. WIll be done by tomorrow20:06
n0anowill you put that in the blueprint20:07
sriramherei would like to talk to you all about what we want to talk during the session20:07
sriramhereyes, i will20:07
sriramherewe had 3 topics considered/ wanted to be talked about during session20:07
n0anothen I think we can use the BP as the guide to the agenda20:07
sriramherestepping back - this is a brainstorming session20:07
sriramherealso, my first. can one of u tell me what to expect during the brainstorming session?20:08
sriramherei am using the following link as guideline20:08
n0anoagreed, but having a little structure to the discussion is always good.20:08
sriramherehttps://www.youtube.com/watch?v=GmY4cK_6NKY20:08
maoyi only been to one summit before20:08
*** ryanpetrello has quit IRC20:08
maoyi think if the session chair (leader?) is organized with an agenda, it works much better20:09
*** ryanpetrello has joined #openstack-meeting20:09
n0anome too but we're allowed to be fairly loose20:09
sriramherei like to have an agenda20:09
sriramherethat also helps to keep focussed.20:09
n0anohence making sure the BP has the right outline then I think we'll be good20:09
maoyok20:09
sriramherewhat i am thinking now, ur suggestions d help me20:09
sriramhereis - to start with the need for orchestration. though most of us agree, this is to set the tone20:10
sriramherethen introduce some of the back ground work. this will include Ziad's and maoys., if any progress i can make on aws swf mock20:11
* vishy jumps in20:11
sriramherethen incude the things we want to hash out - api design20:11
vishyhave you guys considered where the orchestration code will go?20:11
sriramhereopen up brainstorming20:11
*** markvoelker has quit IRC20:12
vishy(I ask because with volume splitting out it might be nice to have some/all of the code in openstack-common20:12
n0anovishy, not sure we've gone there yet beyond thinking that it'll be part of nova20:12
sriramhereu mean branch? general consensus so far is to have a branch20:12
sriramherein terms of project, under nova. a separate sevice20:13
maoyvishy, we did talk about the orchestration as a general service independent of nova-core20:13
vishyn0ano: it could go into nova branch initiially, but it would be great if it is useful for volume and/or network20:13
sriramherenova-orchestration.20:13
vishythat it eventually moves into openstack-common20:13
vishysimilar to how rpc code is moving now20:13
vishyjust wanted to put that thought in your heads, didn't mean to derail the meeting.20:14
vishy:)20:14
maoy3 components: nova-orch (server side), nova-orch (client library), and modify existing nova code to utilize nova-orch client20:14
sriramherevishy - i am hearing u suggest to keep this away from nova20:14
n0anoI like the idea of in the nova branch to begin with, keeping in mind that we might want to split out if it is useful for other projects.20:14
vishymaoy: hmm maybe we are discussing different things20:14
vishyI'm referring to the state management part of the code20:14
vishyas in workflow engine defining the states for a vm for example20:15
vishythat part will probably have to be in nova or integrated somehow20:15
vishybut it also applies to volumes and networks20:15
n0anoI thought that was where the spiff-workflow investigation applied20:15
vishyright, but nova-orch with a client library sounds like it is higher level orchestration20:16
maoyi think we are talking about the same thing..20:16
vishylike using a bunch of services together20:16
vishyah sorry i missed the last part of your sentence: modify existing nova code to utilize nova-orch client20:16
sriramhereso u like a nov-orch service, side by side with nova-volume, etc20:16
vishythat seems reasonable, as long as you keep it simple20:17
n0anomy only concern is would that too heavy weight for what we need20:17
vishyI see two approaches20:17
sriramherebut would like to keep it in openstakc-common?20:17
vishy1) a totally separate service with a rest-api for state management20:17
vishyother servies use it20:17
vishy2) a set of python libraries for state management20:17
vishyother services use it20:17
vishyi personally would lean towards 220:18
vishyyou could always add 1 later20:18
n0anopersonally, I like 2, maybe think about 1 later if needed20:18
vishyif it is going to be 2, openstack-common could be a good place for it to ultimately end up.20:18
sriramherein 2, other services would just include/ use this library?20:18
vishysriramhere: correct20:18
n0anoI think we're in violent agreement here20:19
maoyI feel 1) is a specific implementation of 2)20:19
vishyagreed20:19
sriramherena0no - wait please20:19
sriramherei am just typing20:19
vishyand it might be very cool long term20:19
vishyStateManagementaaS20:19
vishyor OrchestrationaaS20:19
sriramheremy only concern is orchestration layter may not sit on top if we need it to20:19
sriramhereif we are thinjking aaS, may be 1 is a better solution rt?20:20
*** dwcramer has quit IRC20:20
n0anoI think it's too early to do an aaS, walk before we run20:20
*** dwalleck has quit IRC20:20
vishyn0ano: +120:20
sriramherei agree, was commenting to vishy's long term names20:21
maoywe should dive deeper in the summit, e.g. talk about the actual persistent storage layer for state we manage. e.g. mysql vs zookeeper20:21
sriramhere2 is simple to start with - i agree. i think all agree to that20:21
sriramherebut is 2 going to be the end? and if we wan tto go towards1, how difficult would that be ?20:22
n0anoIf we keep 1 in mind as an option then, hopefully, we won't make design decisions that make transitioning to that difficult20:23
sriramherei like to have the ability to have orchestration running by itself20:23
maoyit's very hard to define 1 without having hands-on experience with 220:23
sriramheren0ano - agreed20:24
n0anocomes back to maoy's point that 1 can be used as an implementation for 220:24
sriramhererather on top of 2?20:24
*** jakedahn_zz is now known as jakedahn20:24
n0anoI see it as there are python APIs we create, they either execute python code (option 2 for now) or call out to a service (option 1 for later)20:25
sriramhereok - looks like the consensus is to start with 2, but keep in mind 1 as an option20:25
sriramherei personally would still servicify it20:26
sriramhereit may not be complex, but would like other services consider orch as a service. not library20:26
*** sandywalsh has joined #openstack-meeting20:27
n0anoto me, you call an API and what that API does is arbitrary20:27
maoyto make it as a service, you need to decide which functions live on the server, which live on the client.20:27
maoyif just having APIs, you can defer that decision. change it without changing the APIs20:28
sriramhereand it is better to answer the question sooner than later. else, it might be very difficult to do later20:28
n0anogiving us time to get some experience as to what is truly needed20:28
sriramhereok - something the experienced can help here20:29
maoysriramhere: rest service is nothing more than a specific way of remote API call semantics-wise20:29
sriramherewat has been the experience so far - to rip out a library in to a service20:29
sriramheremaoy - i agree, and we can start with that. but this would force the other services not to consider this as a library, there by not making themselves too tied20:30
sriramherei mean - just consider that as a rest end point. and it could be a light weight to begin with.20:30
*** zigo has quit IRC20:31
sriramhereas long as other services keep thinkint it as a service, we are better off, rt?20:31
n0anoI would hope that other services don't care, they want something done and the API does it, that's all that matters, not that it's a service20:31
maoyi don't think it matters..20:32
maoyn0ano: agree20:32
maoythe drawback of API is that is language dependent20:32
maoyso you have to use Python. and upgrading is hard20:32
maoynot a problem in openstack now since every component is released together, all written in python20:33
*** novas0x2a|laptop has quit IRC20:33
sriramherepausing for a moment - what is the difficulty tht i am missing on wrapping a rest end point on these apis?20:33
*** dwcramer has joined #openstack-meeting20:33
n0anono difficulty, comes back to I'd like to see something very light weight to begin with before we decide we need an extra service20:34
sriramhereok - everybody else seems to like to stat with 2. i will also go with it then for now.20:36
n0anoI think we'll have some good discussions at the session.20:36
n0anoBack to the seesion, I see the brief outline of the agenda as:20:37
*** novas0x2a|laptop has joined #openstack-meeting20:37
n0ano1)  Why orchestration is needed20:37
n0ano2)  Background20:37
n0ano3)  Current thoughts (3 topics)20:37
sriramhereso, this is another item to add for discussionduring summit20:37
n0anocertainly it would be appropriate20:37
maoysounds great20:37
maoydo we know which day the session is on?20:38
n0anoI curious about that also20:38
maoyi guess it's still in flux then20:39
sriramherei dont know tht e - as of yesterday night.20:39
sriramherelet me check quickly now20:39
maoyhopefully it won't conflict with my other sessionx20:39
maoysessions20:40
maoyI guess that's it for today?20:40
maoyI'm excited20:40
n0anothat's all I have, looking forward to the summit20:41
sriramhereaction items?20:41
n0ano#action sriramhere to finalize the BP20:41
sriramherealso , shall we ahve an offline sync by the week end just to make sure we have all ready for the summit?20:41
n0ano#action everyone to attend the session20:42
sriramherethis will include a slide deck20:42
n0anosriramhere, we're all available via email, when you have the deck ready just send it out and we'll review20:42
*** ttrifonov has quit IRC20:42
*** ttrifonov has joined #openstack-meeting20:42
sriramhereworks20:43
n0anoin that case, tnx everyone and we'll see you next week.20:43
sriramhere5 pm on tuesday is ours20:43
maoythx. bye20:43
n0anoexcellent, now we know20:43
maoywho did you talk to to get that?20:43
sriramherehttp://openstack.org/conference/san-francisco-2012/sessions/20:43
sriramhereits updated20:43
sriramhereno conflicts that we know of now?20:44
n0anoI'm certainly good20:45
maoynice. didn't know that link. no conflict from my end20:45
sriramhereother sesison is resource rationing in glance20:45
sriramheresame time i meant20:45
sriramhereok then.20:45
sriramherethanks, cya all next week20:45
n0anolater20:45
n0ano#endmeeting20:45
*** openstack changes topic to "Status and Progress (Meeting topic: keystone-meeting)"20:45
openstackMeeting ended Thu Apr 12 20:45:57 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-20.02.html20:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-20.02.txt20:46
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-12-20.02.log.html20:46
*** maoy has quit IRC20:46
*** joearnold has joined #openstack-meeting20:50
*** adjohn has quit IRC20:50
*** sriramhere has quit IRC20:50
*** mnewby has quit IRC21:04
*** shwetaap has quit IRC21:07
*** brni_skul has quit IRC21:08
*** brni_skul has joined #openstack-meeting21:09
*** joearnold has quit IRC21:10
*** shwetaap has joined #openstack-meeting21:11
*** joearnold has joined #openstack-meeting21:12
*** jakedahn is now known as jakedahn_zz21:13
*** hggdh has quit IRC21:18
*** joearnol_ has joined #openstack-meeting21:20
*** joearnold has quit IRC21:23
*** joearnol_ has quit IRC21:24
*** hggdh has joined #openstack-meeting21:24
*** nati has joined #openstack-meeting21:24
*** mnewby has joined #openstack-meeting21:29
*** ttrifonov has quit IRC21:31
*** ttrifonov_zZzz has joined #openstack-meeting21:31
*** ttrifonov_zZzz is now known as ttrifonov21:31
*** dwcramer has quit IRC21:32
*** joearnold has joined #openstack-meeting21:32
*** mdomsch has quit IRC21:43
*** ryanpetrello has quit IRC21:45
*** ryanpetrello has joined #openstack-meeting21:45
*** nati has quit IRC21:48
*** mestery has quit IRC21:49
*** adjohn has joined #openstack-meeting21:49
*** nati has joined #openstack-meeting21:50
*** ryanpetrello has quit IRC21:51
*** esker has quit IRC21:51
*** mestery has joined #openstack-meeting21:52
*** ayoung has quit IRC22:00
*** kindaopsdevy has joined #openstack-meeting22:07
*** kindaopsdevy_ has joined #openstack-meeting22:09
*** kindaopsdevy has quit IRC22:09
*** kindaopsdevy_ is now known as kindaopsdevy22:09
*** kindaopsdevy has left #openstack-meeting22:10
*** troytoman has quit IRC22:21
*** troytoman-away has joined #openstack-meeting22:21
*** troytoman-away is now known as troytoman22:21
*** joearnold has quit IRC22:31
*** joearnold has joined #openstack-meeting22:39
*** ttrifonov is now known as ttrifonov_zZzz22:42
*** dwcramer has joined #openstack-meeting22:43
*** mattray has quit IRC22:46
*** Yak-n-Yeti has quit IRC22:47
*** joearnold has quit IRC22:53
*** troytoman is now known as troytoman-away22:54
*** _cerberus_ has quit IRC23:03
*** _cerberus_ has joined #openstack-meeting23:03
*** dtroyer is now known as dtroyer_zzz23:04
*** joearnold has joined #openstack-meeting23:08
*** kindaopsdevy has joined #openstack-meeting23:09
*** ryanpetrello has joined #openstack-meeting23:09
*** kindaopsdevy has left #openstack-meeting23:10
*** lloydde has quit IRC23:10
*** dwcramer has quit IRC23:10
*** kindaopsdevy_ has joined #openstack-meeting23:12
*** AlanClark has quit IRC23:20
*** dwcramer has joined #openstack-meeting23:24
*** dwcramer has quit IRC23:29
*** rnirmal has quit IRC23:37
*** blamar has quit IRC23:39
*** dwcramer has joined #openstack-meeting23:42
*** joearnold has quit IRC23:45
*** gyee has quit IRC23:49
*** joearnold has joined #openstack-meeting23:56

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