Tuesday, 2011-11-01

*** novas0x2a|laptop has quit IRC00:48
*** novas0x2a|laptop has joined #openstack-meeting00:49
*** jog0_ has joined #openstack-meeting00:55
*** jog0_ has quit IRC00:56
*** jog0_ has joined #openstack-meeting00:56
*** jog0_ has quit IRC01:00
*** jog0 has joined #openstack-meeting01:12
*** dragondm has quit IRC01:23
*** jog0 has left #openstack-meeting01:27
*** jaypipes has quit IRC02:11
*** dendrobates is now known as dendro-afk02:23
*** dendro-afk is now known as dendrobates02:23
*** nati2 has joined #openstack-meeting02:27
*** jaypipes has joined #openstack-meeting02:28
*** cmagina has joined #openstack-meeting02:34
*** novas0x2a|laptop has quit IRC02:44
*** novas0x2a|laptop has joined #openstack-meeting02:46
*** tsuzuki_ has joined #openstack-meeting03:28
*** ecarlin has joined #openstack-meeting04:16
*** ecarlin has quit IRC04:17
*** dendrobates is now known as dendro-afk04:20
*** novas0x2a|laptop has quit IRC04:26
*** mdomsch has quit IRC04:28
*** novas0x2a|laptop has joined #openstack-meeting04:30
*** novas0x2a|laptop has quit IRC04:42
*** novas0x2a|laptop has joined #openstack-meeting04:42
*** nati2_ has joined #openstack-meeting05:27
*** nati2 has quit IRC05:28
*** novas0x2a|laptop has quit IRC05:39
*** novas0x2a|laptop has joined #openstack-meeting05:39
*** novas0x2a|laptop has quit IRC05:59
*** novas0x2a|laptop has joined #openstack-meeting05:59
*** Arminder has joined #openstack-meeting06:04
*** Arminder has left #openstack-meeting06:22
*** novas0x2a|laptop has quit IRC08:50
*** darraghb has joined #openstack-meeting09:48
*** tsuzuki_ has quit IRC10:55
*** jaypipes has quit IRC10:56
*** deepakn has joined #openstack-meeting11:17
*** deepakn has left #openstack-meeting11:19
*** markvoelker has joined #openstack-meeting11:31
*** hggdh has joined #openstack-meeting11:57
*** dprince has joined #openstack-meeting11:59
*** cdub has quit IRC12:02
*** cdub has joined #openstack-meeting12:39
*** hggdh has quit IRC12:58
*** cdub has quit IRC12:59
*** zns has joined #openstack-meeting13:13
*** |newbie| has joined #openstack-meeting13:36
*** |newbie| has left #openstack-meeting13:36
*** |newbie| has joined #openstack-meeting13:43
*** reed_ has joined #openstack-meeting13:43
*** |newbie| has left #openstack-meeting13:43
*** reed_ is now known as reed13:44
*** mattray has joined #openstack-meeting14:15
*** mattray has joined #openstack-meeting14:15
*** zns has quit IRC14:22
*** zns has joined #openstack-meeting14:31
*** baraber has joined #openstack-meeting14:50
*** rnirmal has joined #openstack-meeting14:56
*** zns has quit IRC14:57
*** dragondm has joined #openstack-meeting15:02
*** zns has joined #openstack-meeting15:03
*** adjohn has joined #openstack-meeting15:05
*** cdub has joined #openstack-meeting15:15
*** adjohn has quit IRC15:21
*** cdub has quit IRC15:24
*** nati2_ has quit IRC15:38
*** nati2 has joined #openstack-meeting15:38
*** nati2 has quit IRC15:44
*** sec_prof has joined #openstack-meeting15:48
*** reed has quit IRC15:50
*** reed has joined #openstack-meeting15:54
*** jog0 has joined #openstack-meeting16:04
*** jog0 has joined #openstack-meeting16:05
*** jog0 has left #openstack-meeting16:05
*** jog0 has joined #openstack-meeting16:05
*** jog0 has left #openstack-meeting16:05
*** mattray has quit IRC16:12
*** mattray has joined #openstack-meeting16:12
*** reed has quit IRC16:31
*** zns has quit IRC16:32
*** zns has joined #openstack-meeting16:36
*** reed has joined #openstack-meeting16:39
*** zns has quit IRC16:46
*** zns has joined #openstack-meeting16:51
*** shang has quit IRC16:55
*** maoy has joined #openstack-meeting16:58
*** reed has quit IRC16:59
sandywalshOrchestration meeting17:00
openstackMeeting started Tue Nov  1 17:00:52 2011 UTC.  The chair is sandywalsh. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.17:00
sandywalsh#topic plead forgiveness17:01
*** openstack changes topic to "plead forgiveness"17:01
sandywalsh#link http://wiki.openstack.org/Meetings/Orchestration17:01
sandywalshthis will be a short meeting I think17:02
sandywalshso, I haven't had a lot of time to get any prep done17:03
sandywalsh(specifically the video)17:03
maoythat's fine by me, since I watched your talk..17:03
sandywalshbut regardless there are two issues I think (and please jump in to correct me)17:03
sandywalsh1. the tactical issues17:04
sandywalsha. how to get events back to the orchestration layer from the services17:04
sandywalshb. where the orchestration service lives (in scheduler?)17:04
sandywalshand 2. what is the strategic approach to orchestration17:04
sandywalsha. a trivial state machine17:05
*** vladimir3p has joined #openstack-meeting17:05
sandywalshb. a more complex state machine (petri)17:05
sandywalshc. another service (some pre-existing library)17:05
sandywalshd. other?17:05
sandywalshmaoy, I think this is where your paper comes in17:05
sandywalsh(which I have to apologize for, I haven't read yet, but it's at the top of my stack)17:06
sandywalshIn the link I have a list of what I think are tactical items17:06
maoygreat. i was about to say that the paper is quite relevant here.17:06
sandywalshwhich I think are applicable regardless of the strategic approach17:06
sandywalshgood ... I'm keen to read it. I'll try to get some meaningful feedback on it by next meeting17:07
maoyI think that the orchestration might make more sense to be below the scheduler.17:07
maoysandy, i'm also looking at petri net.17:08
sandywalshok, so scheduler talks to orchestration and steps out of the way?17:08
sandywalshI sort of envisioned orchestration talking to scheduler, but you suggest the other way around?17:09
maoyto me it depends on how we define what exactly the orchestration layer does17:10
sandywalshwell, maoy if you can perhaps create a wiki page to summarize your idea (nothing fancy), we can comment on it there?17:10
maoyi'll work on that17:10
maoyi have a question on the petri net17:11
sandywalshwe've started considering what it would take to do simple retry, so hopefully that will give us a little bit of the tactical stuff we need17:11
vladimir3pHi All, Sorry for being late and you probably already discussed it, but I guess we need to divide it into several parts, where one of them - return status over AMQP is kind of related to Orchestrator, but not really the orchestrator17:11
vladimir3pto me it seems like the orchestrator should be the one who requests from scheduler what to do ...17:12
maoypetrinet is a great way to model concurrent processes. i'm just curious after the modeling what could we do with it17:12
sandywalshvladimir3p, yes, I outlined one suggestion in the agenda: http://wiki.openstack.org/Meetings/Orchestration17:12
sandywalshmaoy, can you give an example?17:12
sandywalshvladimir3p, I think Orch should ask of the scheduler, but maoy is going to propose an alternative approach.17:13
vladimir3pah, sorry. I was definitely late for this meting :-)17:14
maoyi'm completely unfamiliar with celery and the other tool you mentioned in the talk, but I am wondering what benefit we have with the modeling effort17:14
sandywalshvladimir3p, np17:14
sandywalshmaoy, from the feedback I got, we don't want to use celery tasks.17:14
maoysandy and vlad, I think we might have a similar idea, but use different understanding in the terminologies, esp on "orchestration"17:15
sandywalshquite likely17:15
*** bhall has joined #openstack-meeting17:15
sandywalshstill, write up your suggestion and we'll make sure we're on the same page17:16
sandywalsh#action maoy to write up his suggestions for how the orch service works with the scheduler (and other services)17:16
*** hisaharu has joined #openstack-meeting17:16
maoydo we deal with high availability issues here?17:17
sandywalshmaoy, my ideas for using petri net was simply to be a "better state machine". There were no other immediate plans from there. Just generic hooks to the outside world17:17
maoye.g. the orchestrator crashes.17:17
maoygot it17:17
sandywalshmaoy, that's a big issue ... we're running into that now with the scheduler. How do synchronize state when there are many concurrent workers17:18
sandywalshMaster-Slave works great for these problems since there's only one decision maker. But it's a single point of failure17:18
maoyin the paper, we use ZooKeeper who provides a quorum-based highly available storage and coordination service17:18
sandywalshWorkers are great for scalability, but only when the tasks can be idempotent and can be done in parallel. Scheduling/State-management doesn't seem to be one of those problems.17:19
sandywalsh#action sandy to learn about ZooKeeper17:19
vladimir3poops :-) sorry17:20
sandywalshok ... I think those are two good starts. Ideally for next meeting we should be in some agreement how to tackle the concurrency problem.17:20
maoyin the paper, we addressed 4 problems:17:21
sandywalshlet's keep the discussion going on the mailing list. If zookeeper looks promising perhaps we work it into the tactical parts?17:21
sandywalshmaoy, carry on ...17:21
maoyconcurrency, high availability, unexpected errors during worker execution, and imposing policies to prevent mis-operations17:22
maoywe can probably ignore the 4th one17:22
sandywalshgreat ... that's the stuff we need to nail down.17:22
maoyand see if the ideas in the others can be applied in nova in an non-disruptive way17:22
sandywalsh#action give maoy some good feedback on his paper17:23
vladimir3pa quick question - do you plan to apply same principles of "opertation" orchestration not only for between scheduler-compute/volume nodes, but between API nodes - scheduler?17:23
sandywalsh#link http://dl.dropbox.com/u/166877/CloudTransaction.pdf17:23
sandywalshvladimir3p, can you give an example?17:23
vladimir3pwhen you create bunch of instances the call goes to scheduler17:24
vladimir3pbut if it was not accepted/received you probably want to retry it17:24
vladimir3pespecially if we have multiple schedulers17:24
vladimir3pactually, it applies to any operation performed over AMQP17:24
maoyis AMQP lossy?17:25
maoyi'm not very familiar with it.. sorry17:25
vladimir3pit may stuck there17:25
maoythis is undesirable..17:26
vladimir3pI was thinking of case when particular scheduler accepted request but crashed...17:26
vladimir3p(as an example)17:26
maoyseems like either we can retry and make scheduling job idempotent, or to fix amqp..17:28
sandywalshmy assumption was the first step was to create the workflow and that would get picked up by orch layer and worked on from there.17:28
vladimir3pok, np17:29
sandywalshok, well guys I think we have a good start here. Let's keep the discussion going on the ML once we review all the materials.17:29
maoyi'll put up a wiki17:30
sandywalsh... thanks for your time guys17:30
maoymy idea is still quite rough since I don't know nova that well17:30
vladimir3psandy, just to make sure - the same error/reply logic we could make "generic"17:30
maoybut you guys will help me. :)17:30
vladimir3pand try to apply it for API-sched communications17:30
vladimir3pand it willbe kind of an essential part of orch, but not really the orch17:31
sandywalshyes, makes sense17:31
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"17:32
openstackMeeting ended Tue Nov  1 17:32:36 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-17.00.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-17.00.txt17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-17.00.log.html17:32
*** bengrue has joined #openstack-meeting17:37
sandywalshrobertn, time for a new password?17:40
*** bengrue has quit IRC17:40
*** bengrue has joined #openstack-meeting17:42
*** zns has quit IRC17:54
*** markvoelker has quit IRC17:59
*** zns has joined #openstack-meeting18:00
zns#startmeeting Keystone Team Meeting18:00
openstackMeeting started Tue Nov  1 18:00:48 2011 UTC.  The chair is zns. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:00
*** openstack changes topic to " (Meeting topic: Keystone Team Meeting)"18:00
*** joesavak has joined #openstack-meeting18:01
znsLet me know if you're here for the Keystone meeting.18:02
znsjoesavak: anything you want to log for the record? I'll also stay online in case anyone shows up.18:04
*** hggdh has joined #openstack-meeting18:04
joesavakzns: We are looking into RBAC design and would appreciate any community feedback. The blueprint is at https://blueprints.launchpad.net/keystone/+spec/rbac-keystone18:05
znsjoesavak: thanks.18:07
znsI've also heard through the grapevine that some folks are still having challenges running the Diablo branch. I'm trying to dig in to the details to see if we have anything to fix and we'll backport as soon as we identify any real issues blocking Diablo deploys.18:07
*** hggdh has quit IRC18:14
*** Yogi_ has joined #openstack-meeting18:17
*** Yogi_ has joined #openstack-meeting18:19
znsjoesavak: Looks like nobody here outside of the core team. Feel free to leave. I'll hang around in case anyone shows up with questions.18:19
joesavakzns: will do. Thanks18:19
* joesavak moonwalks out18:19
*** joesavak has quit IRC18:20
*** dolphm has joined #openstack-meeting18:21
*** Yogi_ has quit IRC18:23
*** dolphm has quit IRC18:34
*** dolphm has joined #openstack-meeting18:35
*** gyee has joined #openstack-meeting18:36
robertnno kidding...doing that now18:37
*** mattray has quit IRC18:38
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:45
openstackMeeting ended Tue Nov  1 18:45:10 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-18.00.html18:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-18.00.txt18:45
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-18.00.log.html18:45
*** gyee has quit IRC18:48
*** dprince has quit IRC18:55
*** gyee has joined #openstack-meeting18:57
*** yehudasa has joined #openstack-meeting18:58
*** zns1 has joined #openstack-meeting18:59
*** darraghb has quit IRC19:00
*** dolphm has quit IRC19:00
*** zns has quit IRC19:01
*** maoy has quit IRC19:13
*** dolphm has joined #openstack-meeting19:17
*** joesavak has joined #openstack-meeting19:22
*** baraber has left #openstack-meeting19:25
*** zns1 has quit IRC19:37
*** hisaharu has quit IRC19:41
*** zns has joined #openstack-meeting19:41
*** jsavak has joined #openstack-meeting19:43
*** joesavak has quit IRC19:44
*** dolphm has quit IRC19:45
*** jaypipes has joined #openstack-meeting19:49
*** jakedahn has joined #openstack-meeting19:51
*** dolphm has joined #openstack-meeting19:51
*** anotherjesse has joined #openstack-meeting19:52
*** dolphm has quit IRC19:55
*** jbryce has joined #openstack-meeting19:57
*** ewanmellor has joined #openstack-meeting19:59
ttxare we having a meeting today ?20:00
jbrycenothing made it onto the agenda for today and we've got a few of you at uds so i don't know if it makes sense20:01
ttx(vishy, jaypipes, mtaylor are at UDS with me... somewhere)20:01
vishyi'm here20:01
jaypipesttx: here.20:01
jbrycewell that's 720:01
ttxmtaylor is not very far away from me, if he is required20:01
openstackMeeting started Tue Nov  1 20:02:01 2011 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:02
jbrycedoes anyone have anything they want to cover today?20:02
*** bencherian has joined #openstack-meeting20:03
jaypipesnot from me.20:04
notmynamestuff always comes up, but it's not worth discussing if we don't have a goal20:04
jbryceall right. does any object to adjourning early?20:05
*** jrouault has joined #openstack-meeting20:05
pvolater all20:05
mtaylorI don't object20:05
mtaylorsorry - I was just saying I was here20:05
mtaylorbut now everyone's leaving20:05
* mtaylor sniffs20:05
* anotherjesse here20:05
jbrycemtaylor: you cleared the room20:05
mtaylorjbryce: I'm going to blame anotherjesse20:06
anotherjessemtaylor: it is ALWAYS MY FAULT :)20:06
mtayloranotherjesse: well, it's either yours or mine20:06
*** dolphm has joined #openstack-meeting20:07
anotherjesseif we are both here then we can't blame each other … maybe I should /nick anotherdeveloper and so we can blame me now20:07
*** joesavak has joined #openstack-meeting20:07
notmynameseveral other people have joined20:07
notmynamedo they have something that needs to be covered?20:08
jbrycemtaylor, anotherjesse: either of you have something to cover?20:08
notmynameI was also thinking about non-ppb people20:08
anotherjessejbryce: I'm good20:08
ttxWeekly release meeting in 50min. See you there :)20:09
mtaylorjbryce: nope20:09
*** liemmn has joined #openstack-meeting20:09
jbryceok. last call for any topics from anyone20:10
*** jsavak has quit IRC20:10
jbrycethanks everyone20:11
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:11
openstackMeeting ended Tue Nov  1 20:11:25 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-20.02.html20:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-20.02.txt20:11
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-20.02.log.html20:11
notmyname /shortestemeetingever20:11
ttxsee you in a bit20:12
*** reed has joined #openstack-meeting20:13
*** reed has quit IRC20:13
*** jmckenty has joined #openstack-meeting20:15
*** hggdh has joined #openstack-meeting20:15
*** dolphm has quit IRC20:17
*** jbryce has quit IRC20:18
*** dolphm has joined #openstack-meeting20:20
*** markvoelker has joined #openstack-meeting20:29
*** bencherian has quit IRC20:31
*** hggdh has quit IRC20:35
*** ewanmellor has quit IRC20:37
*** bencherian has joined #openstack-meeting20:38
*** bencherian has quit IRC20:42
*** bencherian has joined #openstack-meeting20:43
*** troytoman-away is now known as troytoman20:43
*** primeministerp has joined #openstack-meeting20:45
*** joesavak has quit IRC20:48
*** wwkeyboard has joined #openstack-meeting20:50
*** Vek has joined #openstack-meeting20:50
*** Tushar has joined #openstack-meeting20:51
*** bcwaldon has joined #openstack-meeting20:51
*** bencherian has quit IRC20:53
*** dubsquared has joined #openstack-meeting20:53
*** bencherian has joined #openstack-meeting20:54
*** novas0x2a|laptop has joined #openstack-meeting20:55
*** danwent has joined #openstack-meeting20:58
* ttx waves from UDS at Orlando20:59
* carlp waves at danwent20:59
ttxzns, notmyname, jaypipes, vishy, devcamcar: around ?20:59
wwkeyboardttx: a conference with connectivity?!21:00
ttxwwkeyboard: also known as UDS.21:00
ttxwwkeyboard: they have a pretty good setup here21:01
jmckentyIs it time?21:01
wwkeyboardttx: glad to hear it21:01
*** jog0 has joined #openstack-meeting21:01
*** amrox has joined #openstack-meeting21:01
ttxit's time for the general meeting. PPB was last hour, if that's what you're looking for21:01
ttxwaiting for PTLs to show up21:01
jmckentyah, someone should fix the calfeeds then21:01
jmckentythey list PPB as being 2pm today for some reason21:02
devcamcarttx: o/21:02
jmckentyand 1pm next week21:02
ttxjmckenty: the calfeeds are alright to me21:02
*** renuka has joined #openstack-meeting21:02
* jmckenty hates all the calendars21:02
* ttx hates time21:03
*** ewanmellor has joined #openstack-meeting21:03
ttxzns, notmyname, jaypipes, vishy: ?21:03
Vekjmckenty: DST skew, perhaps?21:03
ttxok, let's statr21:03
jmckentyVek, yeah, likely.21:03
ttxstart, even21:03
openstackMeeting started Tue Nov  1 21:03:59 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:04
ttxWelcome everyone to the weekly general meeting... Today's agenda is at:21:04
ttx#link http://wiki.openstack.org/Meetings/TeamMeeting21:04
ttxSo today I'd like to focus project status topics on essex-121:04
ttx...since we have only one week left before that milestone21:04
ttx#topic Keystone status21:04
*** openstack changes topic to "Keystone status"21:04
*** somik has joined #openstack-meeting21:04
ttxnetwork is actually better here than at home.21:04
ttxzns: Looking at:21:05
ttx#link https://launchpad.net/keystone/+milestone/essex-121:05
ttxzns: I'd like to review the status of the 5 blueprints in there21:05
znsAction items from last week I think closed. Did we miss anything?21:05
ttxmaking sure they are all relevant to essex-1 and their status correct ?21:05
ttxzns: yes, action items were covered21:05
ttxis that actually something that can be "completed" ?21:06
ttxi.e. is there a clear target ?21:06
znsI just got off the phone with some of the team working on the docs. We are making good progress and will continue driving this to support adopters and intewgrators.21:06
*** jk0 has joined #openstack-meeting21:06
ttxzns: does it make sense to target it to a specific milestone, though ?21:07
znsI think it can be completed, but there is no clear target.21:07
ttxhmm, ok.21:07
ttxmight need to push to some other milestone then21:07
annegentleI believe that the cleanup and segmentation can be called completed but yes it is ongoing work21:07
znsThe intention is that we are focusing much of our energies in this milestone on it.21:07
ttxis that one close to be completed, you think ?21:08
znsSubmitted and worked on by HP. THey've done a nice job. We've validating the testing and will approve soon.21:08
znsCode complete.21:08
*** jbryce has joined #openstack-meeting21:08
ttx(I'll adjust statuses where needed)21:08
znsIn progress and on track.21:08
ttxso the code should land any time now ?21:09
ttxzns: ideally we would branch miletsone-proposed next Tuesday21:09
znsFor the previous one: https://review.openstack.org/#change,122121:09
jrouaultupdate, keystone swift acls will likely hit essex 221:10
znsOn ACLs, I don't know status yet. I'll have to check with HP (unless Liem or Jason are here?)21:10
*** thingee has joined #openstack-meeting21:10
ttxok, will adjust21:10
jrouaultjust chimed in21:10
znsjrouault: Hi! Thanks.21:10
ttxzns: Anything else ?21:10
znsttx: that's for database-migrations. Under review.21:10
ttxDid you make progress on the stable/diablo branch lots of people have asked for ?21:11
*** debo_os has joined #openstack-meeting21:11
*** mcohen has joined #openstack-meeting21:11
znsOne quick note; we've heard from people they need help with integration. Let us know or post bugs! We're here to help.21:11
ttxRaise your hand if you have questions on Keystone...21:11
vishyzns: i thought chmouel had acls working21:11
jmckentyzns: I'll have Mandell ping you, we've had issues21:11
*** jaypipes has quit IRC21:12
znsAlso, ttx, if we want to backport bug fixes into Diablo, is there a tag or release naming convention to go by?21:12
znsjmckenty: please do! Tx21:12
ttxzns: I'll connect you with the stable updates team21:12
ttxzns: I'm not sure of their conventions21:12
ttxping daviey, zul or markmc21:12
znsvishy: I'll reach out to him.21:13
ttxok, switching to swift in 10 seconds21:13
znsjrouault: have you connected or collaborated with chmouel?21:13
znsYou guys might be able to help each other out on swift ACLs...21:13
znsI'll email-hook-you-up.21:14
ttx#topic Swift status21:14
*** openstack changes topic to "Swift status"21:14
znsttx: Thanks. On to swift...21:14
ttxnotmyname: o/21:14
ttxLooking at https://launchpad.net/swift/+milestone/1.4.421:14
ttxIf that page is current, looks like you have two things left to complete (self-destructing files and man pages)21:14
ttxIs that accurate ?21:14
notmynamethat page is current with the work that has been done and is currently under review21:15
ttxAny ETA for 1.4.4 based on that ?21:15
*** bhall has quit IRC21:15
notmynamenothing official. just "when it's done" or "when it's needed"21:15
ttxnotmyname: Anything else ?21:15
notmynameI think we're getting close21:15
notmynameI expect to have a swift release in the next week or two (maybe three)21:16
*** bhall has joined #openstack-meeting21:16
ttxQuestions on Swift ?21:16
ttx#topic Glance status21:17
*** openstack changes topic to "Glance status"21:17
ttxLooks like jaypipes is not around21:17
ttxbcwaldon: can you step up ?21:17
bcwaldonttx: sure21:17
ttxshould be easy21:17
bcwaldonAs many of you have seen, there is an RFC out on api v2.021:17
bcwaldonwould *love* any comments anybody has21:17
bcwaldonit should be up to date from all of the comments already made21:17
bcwaldonother than that, nothing to report21:18
ttx#link https://launchpad.net/glance/+milestone/essex-121:18
ttxYour blueprints look very much on track.21:18
ttxYou have a lot of targeted bugs though... Do you think they can all be fixed by next week ?21:18
bcwaldonyep, I think we're pretty well targeted at this point21:18
bcwaldonttx: doubtful, I'll take a look and work with Jay21:18
ttxprobably better to keep the list reasonable and doable21:18
bcwaldonwe should see some more blueprints created for the v2.0 stuff, too21:18
ttxok. Questions on Glance ?21:19
ttxbcwaldon: better to keep that bug list down to things you *need* to fix for a milestone, rather than random targets of opportnuity21:19
bcwaldonOk, I'll talk to Jay21:19
ttxotherwise you keep on carrying it on from milestone to milestone21:20
ttx#topic Nova status21:20
bcwaldonwhich we have been doing ;)21:20
*** openstack changes topic to "Nova status"21:20
ttxvishy: yo21:20
* ttx waves at vishy physically21:20
ttx#link https://launchpad.net/nova/+milestone/essex-121:20
ttxquick status check21:21
ttxthis one is not "accepted for essex"21:21
vishyyeah i don't recognize that one21:21
danwentthat is from quantum team21:22
bhallfiled that recently -- I should've filed it earlier, sorry21:22
danwentwe created it kind of late....21:22
danwentbut its been done and in review for a while21:22
ttxif it comes with code it's ok :)21:22
ttxvishy: ok, could you prioritize it ?21:22
danwentyeah, code is ready for review https://review.openstack.org/#change,91621:22
ttxhopefully will raise awareness21:22
vishygot it21:22
danwentthanks guys.  will do a better job of surfacing this stuff earlier in the future21:22
ttxthe other 3 i nprogress looks very much on track I think21:23
vishydanwent: if you reference the blueprint in the commit message it will link automatically21:23
ttxI mean, the other "needs code review" look on track21:23
ttxIn progress, in jeopardy:21:23
danwentvishy:  will do.21:23
ttxvishy: think that one can still hit ?21:23
ttx(missing priority too)21:23
troytomanttx: we decided that it would be best to move melange to an incubated project21:24
troytomanI have the todo to put that in motion. we will not merge into nova21:24
ttxah ? Changing every week :)21:24
vishywe had an offline discussion after last week21:24
ttxok, will remove that one from Nova essex plans then21:24
vishydecided incubated was better since it has its own api21:24
vishythat one is close21:25
ttxvishy: ok21:25
ttxthat one has the first step proposed21:25
ttxbut I don't know how much more work there is21:26
vishyxenapi-sm is here: https://review.openstack.org/#change,89721:26
*** dolphm has quit IRC21:26
ttxeveryone: please mention blueprint name in commit message or topic name. Sets up the magic links21:26
*** russellb has joined #openstack-meeting21:26
vishyi think the admin api refactor will hit21:27
vishyi don't know if that will count as "complete" or not21:27
ttx#info please mention blueprint name in commit message or topic name. Autosets up the magic LP/Gerrit links21:27
bcwaldonvishy: the bp I'm working on?21:27
ttxwe'll see21:27
ttxbcwaldon: yes21:27
bcwaldonI could see that waiting for essex-2, just because of the immense amount that needs to be done21:27
pvovishy: did we care about the doc request for the xen volume stuff?21:27
vishyok lets retarget then21:28
vishypvo: there is a separate bug and proposal for docs21:28
ttxvishy: Anything else ?21:28
pvoI saw the separate bug, but I didn't know if we'd hold the branch up for docs21:28
annegentlevishy pvo two doc bugs actually since they go into different projects21:28
vishypvo: no21:28
annegentlepvo: testing is just as important21:28
ttxvishy: did the subteams pick up their respectively-assigned blueprints yet ?21:28
vishyttx: to varying degrees21:28
annegentlepvo: but we also need to hold the line against large merges with no docs at all21:29
vishyapi team seems fine, network team, and block storage teams are making progress21:29
vishyorchestration is underway21:29
vishyscaling is stalled at the moment21:29
ttxvishy: I think the security team won't have anything for Essex except the rootwrap stuff21:29
vishythe other ones i haven't heard much from21:29
vishyttx: ok, I was hoping for some planning at least21:29
vishyno code though21:30
ttxQuestions on Nova ?21:30
ttx(vishy: the idea is to produce BPs but not necessarily for Essex)21:30
ttxgoing for the horizon in 10 seconds21:31
ttx(and beyond)21:31
*** mcohen has quit IRC21:31
ttx#topic Horizon status21:31
*** openstack changes topic to "Horizon status"21:31
*** mcohen has joined #openstack-meeting21:31
ttxdevcamcar: o/21:31
ttx#link https://launchpad.net/horizon/+milestone/essex-121:31
ttxYou still have 6 incomplete blueprints there -- do you think they will all be complete by next week?21:32
devcamcarso everything is tracking well for essex-1, though the javascript unit test framework may slip: https://blueprints.launchpad.net/horizon/+spec/javascript-unit-tests21:32
devcamcareverything else should be there for next week21:32
ttxdevcamcar: so ideally we branch to milestone-propsoed late on Tuesday evening21:33
ttxand live it there to bake for two days21:33
ttx(backporting any critical last-minute thing)21:33
devcamcarthe 8th?21:33
devcamcarshould be fine21:33
ttxyes. Actually I do the branching very early on the 9th21:33
ttxif you give me the goahead on the EOD before21:34
devcamcarsounds good21:34
devcamcaronly other update i have is that we are fully converted to gerrit workflow now21:34
ttxhttps://blueprints.launchpad.net/horizon/+spec/improve-dev-documentation is marked slow progress -- is it in jeopardy as well ?21:35
ttxor is that another of those uncompletable things ?21:35
devcamcargood question21:35
devcamcari suppose it is a bit of an ongoing item21:35
ttxBP are good t otrack things tha tcan be completed -- but a bit wrong to tack ongoing efforts21:36
devcamcarfair enough21:36
ttxI'll have to think about how to track that better21:36
ttxbtw I'm working on release automation with jeblair this week so that horizon CI toolchain is ready for essex-121:36
devcamcari think i can rephrase the BP to have a specific scope21:36
devcamcarspecific items that need documentation21:37
ttxdevcamcar: the best way I found so far is to have a generic blueprint "improve doc" and then have it depend on lots of smaller, targeted efforts21:37
ttxso that you can find the relationship21:37
devcamcarsounds good, i'll follow that pattern21:37
ttxbut still having "things that can be completed" in your essex plans21:38
ttxso onc ethe toolchain is ready we'll have tarballs generated for every commit, from trunk and milestone-proposed21:38
ttxdevcamcar: I might ping you so that we can the versioning code right21:38
ttxdevcamcar: will look into it soon.21:39
ttx(basically copy what we have for nova/swift/glance)21:39
ttxif it's not there already21:39
ttxdevcamcar: Anything else ?21:39
ttxQuestions on Dashboard ?21:39
ttxon Horizon ?21:39
ttxlate renaming is difficult !21:40
devcamcarfor real21:40
ttx#topic Incubated projects and other Team reports21:40
*** openstack changes topic to "Incubated projects and other Team reports"21:40
ttxdanwent: o/21:40
danwent#info:  quantum essex-1 filling out nicely: https://launchpad.net/quantum/+milestone/essex-121:40
danwentmajor focus now is just reviews.21:41
danwentwe need to help with two external reviews:21:41
danwentnova networking dhcp changes: https://review.openstack.org/#change,91621:41
danwentpython-novaclient changes: https://github.com/rackspace/python-novaclient/pull/13721:41
danwentthat is pretty much it21:41
ttxwho can help wit hthat second one ?21:41
ttxdanwent: Am I right in assuming Quantum will depend on Melange (if not already) ?21:42
*** debo_os has quit IRC21:42
danwentttx:  quantum can run in two modes, one that uses the traditional nova IPAM, one that uses melange21:42
danwentlong-term, we will require melange as more advanced features will probably rely on melange21:42
danwentand we don't back-port them to work with old nova IPAM>21:42
ttxdanwent: ok. Just trying to see how urgent it is for Melange to be proposed in incubation21:42
danwentwe definitely have people using it already...21:43
danwentso sooner is better21:43
danwentthat's everything on my end, unless folks have questions21:43
ttx#help  with two external reviews https://review.openstack.org/#change,916 and https://github.com/rackspace/python-novaclient/pull/13721:43
ttxOther team leads with a status report ?21:44
vishylooks like that first review has a couple dependencies as well21:44
bhallI can always reorder the commits if that becomes an issue21:45
ttxCI / doc / QA ?21:45
ttxif not, moving on21:46
ttx#topic Open discussion21:46
*** openstack changes topic to "Open discussion"21:46
ttxAnything, anyone ?21:46
vishycan i replug for keystone stable branch asap21:46
*** salv-orlando has joined #openstack-meeting21:46
annegentleWas going to talk about the wiki maintenance work in Open discussion.21:46
vishyi think a lot of the frustration is because people are trying to track keystone trunk21:46
vishy(and ec2 at the very least doesn't work with keystone diablo tag)21:46
znsvishy: we're working on it. We'll be backporting these https://bugs.launchpad.net/keystone/+bugs?field.tag=diablo-backport21:47
annegentleSent an email to the mailing list - summary is, we're testing single sign on with Launchpad IDs for the OpenStack wiki.21:47
znsbut… can you let us know what issues you are experiencing in particular?21:47
ttxvishy: we should talk to Daviey and make sure zns has everything he needs to work on that branch21:47
bhallI'd like to add a plug for installing the gerrit trival rebase hook: https://bugs.launchpad.net/openstack-ci/+bug/88118421:47
uvirtbotLaunchpad bug 881184 in openstack-ci "consider trivial rebase hook for gerrit" [Wishlist,Confirmed]21:47
vishyzns: i think the holdup is just getting the branch made in the repo and it should be editable via reviw by the backports team21:48
znsvishy: so getting EC2 working on Diablo/stable would stop people from tracking trunk?21:48
vishyzns: that is the only show-stopping bug i know about21:48
*** mattray has joined #openstack-meeting21:48
vishyzns: otherwise it is education and perhaps some admin apis21:48
znsvishy: OK! Good to know. Actionable data21:48
vishythere have been some comments in the openstack channel about frustration becasue they can't create and delete tenants21:48
vishy(except through keystone-manage)21:49
ttxbhall: will try to attract jeblair attention on it21:49
zns* is on it *21:49
vishyzns: the main thing is having a std config and install, and people with enough expertise to be able to respond to questions21:49
bhallttx: thanks :)21:49
vishydevstack will help in this regard i think once we have swift included in the mix21:50
znsvishy: I read that as people with expertise available on IRC?21:50
ttxFor anyone at UDS, join us for Rackspace-sponsored OpenStack-themed happy hour21:50
vishyzns: there was a while with nova where it was just me answering the same questions over and over21:51
znsOK. openstack-dev, right?21:51
vishyeventually there are more people that can help21:51
vishyboth openstack and openstack-dev21:51
vishyzns: but the main thing is expertise in configuring it to work with everything21:51
vishyand operate it21:51
vishyas opposed to code-specific expertise21:52
znsvishy: thank you for answering the questions! I don't want to put the onus on you, but pls feel free to reach out to me if you need help. We'll also work on bolstering our IRC presence.21:52
ttxok, we'll close this meeting unless someone has anything to add21:53
ttxok then21:53
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:53
openstackMeeting ended Tue Nov  1 21:53:48 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-21.03.html21:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-21.03.txt21:53
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-21.03.log.html21:53
*** jog0 has left #openstack-meeting21:53
*** Vek has left #openstack-meeting21:54
*** jk0 has left #openstack-meeting21:54
*** liemmn has quit IRC21:56
*** dolphm has joined #openstack-meeting21:56
*** hisaharu has joined #openstack-meeting21:57
*** renuka has quit IRC21:57
*** SumitNaiksatam has joined #openstack-meeting21:58
*** shwetaap has joined #openstack-meeting21:59
danwenthello netstackers!21:59
*** thingee has left #openstack-meeting22:00
danwentsalv: how was your trip?22:00
*** bencherian has quit IRC22:00
*** russellb has left #openstack-meeting22:00
salv-orlandogood. 4 days out for work, 4 days for holydays22:00
danwentsalv-orlando: sweet22:00
openstackMeeting started Tue Nov  1 22:00:59 2011 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:01
somiksalv-orlando: living the good life :)22:01
danwent#info Agenda: http://wiki.openstack.org/Network/Meetings22:01
danwenttroytoman around?22:01
*** Tushar has quit IRC22:01
danwent#topic melange status22:02
*** openstack changes topic to "melange status"22:02
danwentcongrats to melange… going to be its own project22:02
troytomanmain update is that I conferred with vishy and a number of others and we decided melange should stand alone22:02
troytomanso I am going to submit it for incubator status.22:02
carlpawesome, congrats!22:02
troytomanso, we are setting that up this week and hope to have it in front of PPB next week22:03
troytomanthis will simplify packaging, etc. and help us build a community around the project22:03
danwenttroytoman: what does this mean for packaging.  going to do it on your own?22:03
troytomanit was getting lost in the noise with nova22:03
*** edgarmagana has joined #openstack-meeting22:03
edgarmaganahi everybody!22:03
danwenttroytoman:  one question.  melange is already working with keystone, is that correct?22:04
troytomanwe have also start implementing MAC address assignment in Melange22:04
troytomandanwent: yes22:04
troytomanthis will allow us to assure unique MAC addresses across Nova installations that use a single melange instance22:04
danwenttroy: saw that review in nova.  we probably have some suggestions on how the QuantumManager code can be structured to be more inline with the existing QM code.22:04
danwentbrad will be reviewing22:05
bhalldanwent: already provided feedback to them (and got a response)22:05
troytomanit will also help carlp sort out how to tie in DCHP/address discovery22:05
bhallthey're going to talk it over and figure out another way to do it22:05
danwentbut overall, we should easily be able to integrate melange mac generation into QM22:05
danwentbhall: great22:05
danwentok, anything else on melange?  questions?22:05
troytomandanwent: good22:06
troytomanI think that is it on melange22:06
danwent#topic quantum status22:06
*** openstack changes topic to "quantum status"22:06
danwentessex-1 is about a week away: https://launchpad.net/quantum/+milestone/essex-122:06
danwentwant to go through any bp/bugs that aren't already in code review or done22:07
danwentsalv: https://blueprints.launchpad.net/quantum/+spec/authentication-for-quantum22:07
danwentstill comfortable with putting the keystone code back in?22:07
salv-orlandoI'm facing an issue with that at the moment22:07
salv-orlandoBasically the code does not work anymore :)22:07
danwentan issue indeed :)22:07
danwentdue to keystone changes?22:08
danwentor quantum changes?22:08
salv-orlandoI need to spend a few hours on it; something probably changed server-side.22:08
danwentok, good to know.22:08
salv-orlandoAuth is quite independent from quantum. What I'm observing is basically that I always get a 401 on token validation.22:08
danwentplease do update the status of the BP once you spend some time on it.  we can probably pull in keystone folks if needed.22:08
salv-orlandoAnyway, I hope to propose code for merge on thurs22:09
danwentgreat, thanks.22:09
salv-orlandotomorrow instead I will propose for merge api-framework-essex22:09
danwentanticipating my next question… smart :P22:09
salv-orlandoFinally, I have a couple of bugs on my plate. They should be merge-prop by friday.22:09
danwentbhall, two bugs on your plate22:10
vishysalv-orlando: make sure you are testing based on keystone diablo22:10
danwentthat are "in progress"22:10
bhallthey're in code review22:10
vishysalv-orlando: i wouldn't try to track keystone trunk at this point22:10
bhallthere is no launchpad bug state for "in code review" that I can find22:10
danwentbhall: ok, please update status22:10
vishybhall: if you reference the bug or blueprint in the commit message it will create a link and a comment for you22:10
danwentvishy:  will that remain true for a while?22:11
*** bencherian has joined #openstack-meeting22:11
danwentvishy:  my question was about keystone22:11
salv-orlandovishy: thanks for the advie. will do that.22:11
vishydanwent: yes, I don't think any of the projects will move to keystone trunk until the api changes have stabalized22:11
danwentvishy: ok, good to know22:11
*** vladimir3p has quit IRC22:11
danwenti hate spelling22:12
bhallvishy: noted.. I'm going to go through and amend the quantum commits that haven't merged yet with bug/bp references22:12
danwentOk, any other oustanding issues we have mentioned for essex-1?  we'll talk reviews next.22:12
danwenthave -> have not22:12
salv-orlandonot that I know of22:13
danwent#info big review in quantum for essex-1 is quantum packaging: https://review.openstack.org/109422:13
danwent#info other big review is actually in nova, dhcp changes to quantum manager: https://review.openstack.org/#change,91622:14
bhallI have a few more comments on the packaging review but I don't think they're major.. I'll submit the comments today22:14
danwentwe definitely need a big review push for the packaging.  I think Brad and I have committed to reviewing this week.22:14
bhallwould be nice to get some more eyes on it22:14
salv-orlandoTo be honest, I won't have time for doing that review before the weekend.22:14
edgarmaganaI am also reviewing packaging and testing it22:14
danwentthere will be more smaller reviews coming down the pipeline later in the week, so I'd like to get started on the packaging one ASAP22:14
danwentedgar: great22:15
*** bcwaldon has quit IRC22:15
danwentsalv: yeah, sounds like you have dev on your plate this week.  maybe you can do a final review early next week.22:15
edgarmaganadan: I already provided some comments and more to come22:15
salv-orlandothis merge is likely to cause conflicts with all other branches.22:15
salv-orlandowhich are currently under development.22:15
*** dolphm has quit IRC22:15
danwentsalv: agreed.22:15
salv-orlandoIt woul dbe great if we could merge it by the end of the week. This will leave us time to fix the conflicts in branches under dev.22:16
danwentsalv: I think that's a good idea.22:16
danwentlet's target reviews tomorrow, so hopefully we can get a few rounds of feedback in by end of week.22:16
bhallwouldn't the other way around be easier?22:16
bhallget the other revies in first and then fix conflicts in one fell swoop?22:17
salv-orlandobhall: push back packaging?22:17
danwentbhall: I don't think salv's work is ready yet.22:17
bhallI meant early next week.. but I guess we don't have much time next week22:17
bhallok.. either way is ok with me22:17
danwent#help please review https://review.openstack.org/#change,1094 ASAP22:17
*** ewanmellor has quit IRC22:17
danwent#info tyler + team should be ready for reviews + quick feedback this week22:18
danwentboth tyler and mark couldn't attend today, but I will sync with them via email.22:18
danwentOk, any other concerns around essex-1 reviews?22:18
*** dolphm has joined #openstack-meeting22:18
salv-orlandothat changeset is the only one currently waiting for review for quantum, is that correct?22:19
bhallthere is more22:19
bhalllemme find a link22:19
danwent#info current reviews: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z22:20
bhallok, dan got it22:20
danwentwe're going to try and branch a bit before the actual milestone drop, like other openstack projects.22:20
*** bencherian has quit IRC22:20
*** Gordonz has quit IRC22:20
danwent#info we're going to try and branch a bit before the actual milestone drop, like other openstack projects.  If you're committed right before a milestone, please be aware.22:20
danwentOk, anything else essex-1 related, before we move on?22:21
danwentOk, carlp, want to give an update on jenkins + quantum?22:22
*** jmeredit has joined #openstack-meeting22:22
carlpI worked with Monty last week and we got the jenkins slave setup.  I've been really busy with real-life obligations but as of this morning it appears to be working.  Details are in the blueprints.22:23
danwentcarlp: can you send out links with #info tags?22:23
carlpWe have two worker nodes, both VT capable machines.  Jenkins can login to both of them.  They have 100 VLANs for use in testing22:23
carlp#info https://jenkins.openstack.org/job/netstack-dreamhost/22:24
carlp#info https://blueprints.launchpad.net/quantum/+spec/quantum-functional-tests22:24
danwentok so what is our goal in terms of getting the first functional test up and running?22:24
carlpThe biggest issue at the moment is that we need to define the actual testing environment.  We can now spin up libvirt VMs on the workers to do the testing, but we need to define that OS and package set22:25
carlpHardware and networking wise, we should be good to go22:25
danwentcarlp:  cool.  brad is doing some work with devscript that may be of use22:25
danwentmay save you some work.22:25
bhallhe means22:25
danwentindeed :)22:25
carlpbhall: Here is some info monty sent me on how they do bare metal installs now :http://ci.openstack.org/jenkins.html#integration-testing22:26
carlpwe can steal from that or not22:26
bhallok, I'll take a look22:26
carlpWe can also just run code without a VM.  That is ready to rock now.22:26
danwentcarlp: I know several other people are looking to draft behind you in terms of setting up jenkins + quantum, so please do send out docuemtnation when you have the chance.  great work so far.22:26
carlpIt's actually pretty simple, but I will document the environment and the slave better in those blueprints22:27
*** rnirmal has quit IRC22:27
danwentcool.  please send an email to the list with any info on how we can help22:27
danwentanything else on jenkins/functional test?22:27
carlpI think that's it for now22:28
znsdanwent, vishy: you there?22:28
danwenti'm here22:28
danwentok, and final update for quantum is that we should be targeting blueprints at essex-2 now: https://launchpad.net/quantum/+milestone/essex-222:29
danwentAny other questions or comments on quantum?22:29
znsI just read you and vishy were talking about moving to Keystone and API stabalization (sp!). The API implementation in 2011.3 has been stable since Sept 30. So wondering if I understood that right?22:29
danwentI think vishy was just telling salv-orlando that he should be using the keystone api from diablo, not tracking trunk.22:30
salv-orlandozns: I think we were talking about Quantum's auth middleware not working at the moment.22:30
danwentsalv-orlando was seeing 401 issues with keystone22:30
salv-orlandoand danwent told the rest :)22:30
znsah. OK.22:30
znsAnything you need us to do, salv-orlando?22:30
salv-orlandozns: I spend only a few hours on it. That might be something very trivial. I'll get back at you If I'm not able to solve the issue in the next couple of days.22:31
salv-orlandoI'm doing probably too many things in parallel :)22:31
danwent#topic open discussion22:31
*** openstack changes topic to "open discussion"22:31
danwentanything else folks?22:31
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:32
openstackMeeting ended Tue Nov  1 22:32:13 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-22.00.html22:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-22.00.txt22:32
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-01-22.00.log.html22:32
danwenthave a good one :)22:32
salv-orlandoyou too!22:32
*** jmeredit has left #openstack-meeting22:33
*** anotherjesse has quit IRC22:33
*** markvoelker has quit IRC22:34
*** cdub has joined #openstack-meeting22:36
*** shwetaap has quit IRC22:37
*** dmd17 has joined #openstack-meeting22:40
*** sec_prof has quit IRC22:43
*** mattray has quit IRC22:51
*** danwent has left #openstack-meeting22:52
*** jrouault has quit IRC22:52
*** dolphm has quit IRC22:53
*** mcohen has quit IRC22:54
*** dmd17 has left #openstack-meeting22:55
*** jakedahn has quit IRC23:08
*** troytoman is now known as troytoman-away23:11
*** SumitNaiksatam has quit IRC23:16
*** dubsquared has quit IRC23:24
*** zns has quit IRC23:31

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