Tuesday, 2011-03-08

*** pvo has quit IRC00:05
*** adjohn has joined #openstack-meeting00:08
*** ovidwu has joined #openstack-meeting00:26
*** littleidea has joined #openstack-meeting00:39
*** littleidea has quit IRC00:55
*** pvo has joined #openstack-meeting01:00
*** pvo has quit IRC01:22
*** zul has quit IRC02:35
*** zul has joined #openstack-meeting02:37
*** uvirtbot` has joined #openstack-meeting04:08
*** uvirtbot has quit IRC04:08
*** ovidwu has quit IRC05:37
*** ovidwu has joined #openstack-meeting05:42
*** spectorclan has quit IRC10:06
*** spectorclan has joined #openstack-meeting10:08
*** adjohn has quit IRC11:02
*** adjohn has joined #openstack-meeting11:03
*** adjohn has quit IRC11:04
*** adjohn has joined #openstack-meeting11:05
*** dovetaildan has quit IRC12:29
*** dovetaildan has joined #openstack-meeting12:31
*** dovetaildan has quit IRC12:33
*** dovetaildan has joined #openstack-meeting12:39
*** pvo has joined #openstack-meeting13:48
*** uvirtbot` is now known as uvirtbot13:49
*** dprince has joined #openstack-meeting14:06
*** thatsdone has joined #openstack-meeting15:22
*** dendrobates is now known as dendro-afk15:31
*** dendro-afk is now known as dendrobates15:31
*** thatsdone has quit IRC18:04
*** dprince has quit IRC18:08
*** dprince has joined #openstack-meeting18:09
*** zul has quit IRC18:15
*** zul has joined #openstack-meeting18:20
*** dprince has quit IRC18:20
*** pvo has quit IRC18:41
*** littleidea has joined #openstack-meeting19:01
*** littleidea has quit IRC19:04
*** littleidea has joined #openstack-meeting19:16
*** dprince has joined #openstack-meeting19:28
*** ramd has joined #openstack-meeting20:16
*** littleidea has quit IRC20:18
*** jaypipes has joined #openstack-meeting20:39
*** jlmjlm has joined #openstack-meeting20:39
*** ddumitriu has joined #openstack-meeting20:40
*** ttx has joined #openstack-meeting20:50
*** justinsb has joined #openstack-meeting20:50
*** ericrw has joined #openstack-meeting20:52
*** spectorclan_ has joined #openstack-meeting20:54
*** martinr has joined #openstack-meeting20:56
*** pvo has joined #openstack-meeting20:57
*** zedas has joined #openstack-meeting20:57
*** pvo has quit IRC20:57
*** pvo has joined #openstack-meeting20:57
*** sirp_ has joined #openstack-meeting20:57
* ttx waves20:59
dendrobateso/20:59
soreno/20:59
glencholá20:59
spectorclan_0/20:59
pvo\o21:00
westmaas_/o/21:00
ttxoook, let's get started !21:00
ttx#startmeeting21:00
openstackMeeting started Tue Mar  8 21:00:47 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:00
ttxWelcome everyone to our weekly team meeting...21:01
*** cynb has joined #openstack-meeting21:01
ttxToday's agenda is at:21:01
ttx#link http://wiki.openstack.org/Meetings21:01
* ttx checks for late additions21:01
sirp_howdy21:01
jaypipesyo.21:01
ttx#topic Actions from previous meeting21:01
*** openstack changes topic to "Actions from previous meeting"21:01
ttx* pvo to readjust prios for xs-resize and xs-migration: DONE21:01
ttx#topic Current release stage: Development21:02
*** openstack changes topic to "Current release stage: Development"21:02
ttxWe are 9 days from BranchMergeProposalFreeze (March 17).21:02
ttxYour branches should be proposed by then, so that we have the time to properly review and merge them before FeatureFreeze (March 24).21:02
ttxThat only affects "feature" branches, not bugfix branches.21:02
ttxAny questions on that stage ?21:03
*** dragondm has joined #openstack-meeting21:03
jaypipesnot from me.21:04
ttxok, moving on.21:04
ttx#topic Cactus Release status21:04
*** openstack changes topic to "Cactus Release status"21:04
ttxPlease check:21:04
ttx#link http://wiki.openstack.org/releasestatus/21:04
*** murkk has joined #openstack-meeting21:04
ttxNote that we have a few significant Nova BMPs (branch merge proposals) coming up that are not reflected in the plan:21:04
ttxopenstack-api-volumes, authn_and_authz, constraint-scheduler...21:04
ttxI guess that brings up a question.21:05
*** masumotok has joined #openstack-meeting21:05
ttxWe have lots of planned features that won't get delivered due to lack of resources...21:05
ttxAnd ~100 open bugs in a release focused on stability... and yet we have unplanned features proposed for landing.21:05
ttxAre we (as a project) doing something wrong ?21:05
jaypipesand lots of branches proposed for things that *aren't* in the proposed release...21:05
ttxIs it difficult to predict every three months the features we'll want to land during the short feature merge window we have ?21:06
ttxIs it a consequence of not having a design summit at the start of the cycle, so we miss a catalyst ?21:06
jaypipesttx: no, frankly, I think people are just working on whatever they want to regardless of whether it's in the release plan for Cactus or not. Sorry if I'm being blunt here.21:06
ttxOr is it that we are lazy to wait/defer them to the next cycle ?21:06
justinsbI think you're addressing the #1 problem, which is not having a decision maker on each project21:06
dendrobatesI think we are suffering from different groups having different priorities21:06
jaypipesyes21:06
jaypipeson both dendrobates and justinsb21:07
pvodendrobates: ++21:07
sorenYeah. There's a clear disconnect between the priorities set on the blueprints and the actual priorities of the various development teams.21:07
*** eday has joined #openstack-meeting21:07
dendrobatesI don't mean on blueprints21:07
sorenWell, that's relevant, too.21:07
sorenSince that's what is publically "known".21:07
ttxdendrobates: how do you see us fixing this ? Having a plan is quite essential to communicating what we are doing outside the project21:07
sorenWhere "known" really means "thought".21:08
jaypipesttx: there *is* a plan. it's been a plan since the summit. it's that a number of folks aren't particularly interested in that plan.21:08
sorenI suppose it's a question whether the priorities of blueprints should be definitive or descriptive.21:08
dendrobateswe need to enforce it21:08
ttxotherwise our Nova releases look like a collection of loosely-coupled merges that happened to land during that month21:08
jaypipesttx: yep.21:08
dendrobateswe need the will and the power to enforce it plan21:09
dendrobates'the' plan21:09
ttxwe need the will to act as a united project, that takes strong leadership, and meritocracy should help21:09
jaypipesjustinsb: as an example, I'd like to see some of your branches go through, but I'm having a tough time seeing how any of them fit into the declared release plan for Cactus.21:09
justinsbjaypipes: Well, they bring testing of the APIs21:10
jaypipesjustinsb: yes, the one does.21:10
ttxsoren: so far priorities on the blueprints mean how much nagging I apply to get updated status21:10
jaypipesjustinsb: but it's not clear how many of the others fit.21:10
justinsbjaypipes: Let's discuss the details off each branch offline21:10
jaypipesjustinsb: and I'm not just picking on you, please don't back away. the same can be said of the authn/authz brnach proposed.21:10
dendrobateswe should focus in the future21:11
dendrobateswhat do we need to do to not have these problems21:11
jaypipesdendrobates: well, is the root cause bad planning or bad execution?21:11
*** dabo has joined #openstack-meeting21:11
justinsbI think all we need is someone who is responsible for delivering the project's goals.  That's the project technical lead, in my book.  We need them yesterday, (or 9 months ago) IMHO21:11
ttxok, I guess the next summit will be essential for that. With the new PTLs and all that21:11
ttxjaypipes: I'd say both21:12
ttxwith the same root cause21:12
*** dubs has joined #openstack-meeting21:12
sorenjustinsb: I just don't see how that will work. It's not like they can actually manage the people working on stuff.21:12
dendrobateswithout the authority to enforce the goals the ptl's will be ineffective21:12
jaypipesjustinsb: we've had that, however, there have been a number of political issues that have prevented that person from actually pushing forward a direction for Nova.21:12
justinsbjaypipes: Who has it been, and what were the issues?21:13
*** johan_ has joined #openstack-meeting21:13
jaypipesjustinsb: dendrobates was the chief architect.21:13
dendrobatesjustinsb: it was me.21:13
dendrobatesbutg I have not been acting in that role for some time21:13
*** masumotok_ has joined #openstack-meeting21:13
justinsbAre there lessons to be learned from this experience for the PTL role?21:13
dendrobatesprobably not21:14
pvoshould we figure these out at a summit?21:14
jaypipesjustinsb: at this point, we have a number of teams (internal Rackers, OpenStack Rackers, Anso, NTT, etc) that are all basically doing their own thing. There isn't any technical lead that is pushing a concerted agenda, and I'm not sure that if there was one, that the teams would really care to follow a direction.21:14
dendrobatesbut I am extremely worried about the 6 month term for ptl21:14
devcamcaryou know, i think something as simple as a weekly report to mailing list about current priorities, progress of blueprints, etc. would go a long way21:15
jaypipesdevcamcar: that would be great.21:15
devcamcarjust to keep everyone focused21:15
sirp_devcamcar: ++21:15
alekibangodevcamcar: ++21:15
pvodevcamcar: spectorclan_ was doing something like this for a short time21:15
jaypipesdevcamcar: but sorry, that's really what blueprints and bug statuses are for.21:15
dendrobatespvo: yes, I think we should have a long discussion at the summit21:15
ttxdevcamcar: I can certainly do that. That duplicates a bit the info I'm giving at the meeting21:16
ttxanyway, we won't solve it now. For cactus we'll have to rely on nova-core to filter the proposals21:16
spectorclan_I can do something more project specific to what I have been doing21:16
*** masumotok has quit IRC21:16
devcamcarpvo: yea spectorclan_ was doing the higher level number of commits and stuff, and that is good info. i think something a bit more specific to developers within the project, just something to push priorities in front of eyeballs21:16
ttxfood for thought. definitely something to raise while we can pay people beers.21:16
spectorclan_OK, will look into it with ttx21:16
edayalso, we may need to rethink our methods. obviously a 6 month summit + 3 month blueprint proposal/approves are not able to encapsulate what people are doing. before trying to enforce the current system, we may need to rethink the system21:16
devcamcarsweet21:16
dendrobateseday: +121:17
dragondmtrue21:17
edayalso, afaik, swift/glance seem to be fine, it's really just nova21:17
ttx#action ttx and spectorclan_ to look at providing weekly focus ML post21:17
jaypipeseday: there's 10 times as many people working on Nova... to be fair.21:17
alekibangoeday: +121:17
devcamcarjaypipes: i'm not saying we create a bunch of overhead, just basically a report of current status of the blueprints, just the text thats already there in a prioritized list21:17
devcamcarthat goes to the list21:17
dragondmprobably because nova has such a wide scope21:17
edayjaypipes: yup, which is part of the thing we need to address :)21:17
ttxeday: also glance and swift do not suffer from the "multiple groups" syndrome21:18
jaypipesdevcamcar: you mean http://wiki.openstack.org/releasestatus/?21:18
edayjaypipes: in other words, out system doesn't scale to a project of nova's size21:18
jaypipesdevcamcar: my point being is that if people are just working on whatever, completely outside of blueprints and bug reports, it's almost impossible to tell what's going on.21:18
devcamcarjaypipes: it could be as simple as that, if it were pushed to the list once a week21:18
dendrobateswe need to discuss all of this at the summit21:18
devcamcarjaypipes: true, but at least this way we can reinforce the priorities so people are more aware that they're outside scope21:19
edaydendrobates: ++, nothing will be solved in IRC21:19
ttxok, let's close it for now21:19
*** Tushar has joined #openstack-meeting21:19
justinsbIt's an open source project: people will scratch their own itch21:19
justinsbYou don't have to merge it21:19
alekibangoscalable development of scalable cloud system :) .... thats endless fight against ever increasing entropy!21:19
ttxLike I said, we'll rely on nova-core to DTRT21:19
justinsbBut anyone can fork if they don't like the direction you're taking the project in21:19
jaypipesdendrobates: sure, at the summit, but in the meantime we've now got a backlog of reviews for branches that aren't in the release plan and don't have any blueprints tied to them. Specifically what are reviewers to do?21:20
alekibangojustinsb: people would love to have common standard. forking is bad21:20
justinsbForking is bad, which is why it's important to get the direction right and have a good leader that aligns everyone21:20
dendrobatesjaypipes: so we need criteria for rejecting merges?21:20
ttxjaypipes: I would prioritize reviews of planned stuff over unplanned stuff21:20
jaypipesdendrobates: no, we need someone to say "sorry this is not in Cactus. Deferred to Diablo." Period.21:20
*** ewanmellor has joined #openstack-meeting21:21
dragondmIMHO, all merges need a bp or bug associated.21:21
dendrobatesthe first step is to reject the merge21:21
glenc+121:21
ttxjaypipes: I can enforce that once we hit the freezes... before that, must be nova-core21:21
devcamcari think it would be helpful for the core teams to meet on irc once a week for discussing branches and whether they meet criteria21:21
devcamcarsomething more granular21:21
jaypipesand I'm not talking about justinsb's branches alone here... there's lots of stuff. and some of  justinsb branches ARE in plan...21:21
justinsbjaypipes: I'm fine for the constraint scheduler to target diablo21:22
*** dprince has quit IRC21:22
edayor perhaps we just need to break on of justinsb's hands to slow his hacking/mps down :)21:22
justinsbeday: :-)21:23
dendrobateswe need to figure out where the decision can and should be made21:23
jaypipesas a practical example of what has happened because of the chaos: we now are in a situation where masumotok_'s team's live migration patches have received less attention that they deserve, and it looks like we are heading down the same path we hit in January...21:23
dendrobatesat review time is not ideal21:23
ttxjaypipes: right, extraneous BMPs just dilute our focus21:23
ttxjaypipes: I think it's acceptable for nova-core to reject unplanned stuff21:24
* jaypipes acknowledges justinsb has a freakish hacking pace indeed.21:24
*** errr_ has joined #openstack-meeting21:24
ttxjaypipes: I'll ecrtainly not grant any release exception to unplanned stuff21:24
dragondmwe also need more reviewers.21:25
jaypipesttx: it's more the delay/chaos it creates for the planned stuff that has become an issue.21:25
dendrobatesit should be rejected and sent to another another queue to decide if it should be included in the release21:25
jaypipesdragondm: or we need all nova-core reviewers to be reviweing ;)21:25
jaypipessoren: whatever happened to that review days thing?21:25
ttxwe won't solve it now. I'd raise a thread about review focus for nova-core dudes that tackles that issue21:26
dragondmyes. reviewers == *active* reviewers.21:26
sorenjaypipes: It started yesterday.21:26
ttxjaypipes: feeling up to it ?21:26
sorenjaypipes: It took a while to get people to respond.21:26
jaypipesttx: sure21:26
sorenjaypipes: I failed to announce it, though. :(21:27
jaypipesttx: though I hate to keep coming across as the slavedriver...21:27
pvosoren: consider it announced! ;P21:27
sorenjaypipes: But that's only because I suck.21:27
ttx#action jaypipes to raise a ML thread about review focus for nova-core21:27
ttxjaypipes: you prefer to leave te stick with me :P21:27
devcamcarsoren: what does "it started yesterday" mean? :)21:27
ttxok, we need to move on21:27
alekibangosoren: btw i would rather make quota for weekly reviews for core members. like 4  reviews for week or something like that...21:27
ttxCompletion rate, based on the current data:21:28
jaypipesttx: no, I'll do it.21:28
sorendevcamcar: It means that it was my review day yesterday. It's someone else today.21:28
ttxEssential specs:21:28
ttxGlance: 3 completed, 1 proposed21:28
sorendevcamcar: http://wiki.openstack.org/Nova/ReviewDays21:28
ttxNova: 1 in progress21:28
ttxTushar: how far cactus-flatmanager-ipv6-support is from being proposed ?21:28
ttxHigh specs:21:28
ttxGlance: 1 proposed, 1 deferred21:28
ttxNova: 4 implemented, 2 started, 2 in jeopardy, 1 not started and 1 deferred21:29
ttxOther specs:21:29
ttx12 implemented, 6 proposed, 9 in progress, 10 not started and 1 deferred21:29
ttxGiven the number of "not started", I suspect there are a few specs we already know we won't be able to deliver in time...21:29
ttxDoes anyone want to raise a flag about a spec not likely to be completed in time ?21:29
cynbyes21:29
dendrobateslet's start deferring them, if they are not going to make it21:30
ttx(one that isn't already marked Slow Progress / Deferred on http://wiki.openstack.org/releasestatus/)21:30
jaypipescynb: which one?21:30
ttxdendrobates: done already21:30
cynberror codes...21:30
cynbsystem usage records21:30
cynbxs-guest-agent21:30
cynbxs-ovs21:30
ttxcynb: in jeopardy, or already deferred ?21:30
cynbbexar-distributed scheduler (already deferred)21:31
cynbdeferred - correct me if i'm wrong21:31
jaypipesdragondm: ^^21:31
ttxxs-ovs still ahd a chance, according to antonym today21:31
jaypipesdragondm: system usage records to be deferred? ok with that?21:31
dragondmyup.21:31
ttxhence the "slow progress" status21:31
jaypipesttx: defer on system usage records.21:32
ttx#action ttx to update status on cynb's deferred spec list if nobody beats him to it21:32
justinsbI'll take on the distributed scheduler if you want21:33
ttx#action ttx to sync with Tushar on  cactus-flatmanager-ipv6-support status21:33
ericrwI'm preparing to suggest a merge of my execvp patch (bug: 726359). I should have it ready by freeze, but it touches a lot of stuff and I want to make sure it is well tested before it goes into a release.21:33
sorenLooking forward to it!21:33
ttxericrw: cool21:33
ttxOn the Nova stabilization effort:21:33
edayjustinsb: it needs the zone dependencies too, which may not be ready in time21:33
ttxLast week we had 36 bugs opened and 29 fixes committed21:33
ttxThis week we had 16 bugs opened and 10 fixes committed21:34
ttxThat's a big drop, maybe the proximity of BMPFreeze made people concentrate on feature work...21:34
justinsbeday: Well, I could take that one on as well, but I think zones3 looks good21:34
* jaypipes notes last week he had a 3 day jury trial. this week he doesn't. big drop in jury trials.21:34
dendrobatesjaypipes: did they find you guilty?21:35
edayjustinsb: sandy and dabo are actively working on them, so might ask them if they need help21:35
jaypipesdendrobates: nah, got off by reason of insanity ;)21:35
ttxeday, justinsb: I think the problem is more that other stuff needs to land first21:35
edayttx: yeah21:35
daboeday: it's really in flux right now. Much depends on the multi-cluster/zones stuff, and the possible adoption of a central db21:36
ttxeday, justinsb: not really that they need help or resources21:36
ewanmellorttx: Regarding xs-ovs you said "waiting on OVS support from Citrix".  What does that mean?21:36
jaypipescynb: re: the error codes one, did you know Naveed had a branch proposed for merging? https://code.launchpad.net/~ironcamel/nova/http-error-codes/+merge/5249221:36
westmaas_I think those are different error codes.21:36
jaypipesah.21:36
Tusharttx:I have almost finished implementation of flatManager for IPV6. Most probably I will propose my branch for merge early next week.21:36
jaypipeswestmaas_: wanna ping Naveed on that? ;)21:36
ttxewanmellor: antonym told me he was in contact with Citrix to get OVS support in XenServer, and that was needed to implement this psec21:37
ttxewanmellor: I don't really know more than that.21:37
antonymewanmellor: we ran into some issues with the beta drop from citrix that we're working through, we can start coding the script up but we're trying to get ovs working so we can actually test out functionality21:37
westmaas_haha I can.  I know what Naveed's are, I will check in with cynb right after this :)21:37
ttxTushar: ok, thanks21:37
jaypipeswestmaas_: cheers mate21:37
ttxok, moving on to the next topic in 15 seconds21:38
ttx#topic Elections coming up21:38
*** openstack changes topic to "Elections coming up"21:38
ttxspectorclan: floor is yours21:38
spectorclan_Nomination Process at http://www.openstack.org/blog/2011/03/openstack-governance-nominations-and-election-process/; open until March 18 at Midnight CST21:38
ewanmellorttx, antonym: Will follow up on this offline.21:38
antonymewanmellor: sure thing21:39
spectorclan_If you want to be nominated or self-nominated, contact me or post yourself at http://etherpad.openstack.org/Spring2011-Elections21:39
spectorclan_We already have 2 people listed for SWIFT21:39
spectorclan_I will also be posting the election process later this week as there are rules for who can vote for each of the positions21:39
ttxspectorclan: will we know who owns the 4 RS-nominated seats on the PPB before or after voting ?21:40
spectorclan_Will find that our for you; as of now I do not know21:40
sorenWhat happens if the PTL elected is already on the PPB?21:40
dendrobatesspectorclan: the voting needs to be completely transparent and the results available immediately after the voting ends21:40
spectorclan_All voting will be done in public via the tool that ttx suggested21:41
pvospectorclan_: what tool is that?21:41
ttxThat's http://www.cs.cornell.edu/andru/civs.html21:41
sorenCIVS, probably.21:41
dendrobatesspectorclan: there are still options21:41
spectorclan_yes21:41
dendrobatesand it was not done correctly last time21:41
* jaypipes hopes he spelled vishy's name right ...21:41
ttxspectorclan: you just need to pick "results goes to everyone, not a selected group"21:41
spectorclan_My plan is to make sure there are no issues and everyone is pleased with process. That is why I am posting all process stuff ahead of time for comment and changes21:42
spectorclan_Thanks ttx, will do21:42
dendrobatessoren: it is an obvious fail, the ptl needed to be elected first21:42
jaypipesspectorclan: appreciated. thx :)21:42
ttxspectorclan: that's the default choice21:42
spectorclan_I am open to all suggestions on tools and process21:42
sorendendrobates: Yeah. Failing that though, I wonder what the resolution process is.21:42
ttxsoren: the case is already described in the governance21:43
sorenttx: orly?21:43
ttxsoren: PTL gets on PPB, next PPB winner gets a seat21:43
spectorclan_I will explain that issue in the Election Process blog post21:43
sorenttx: Ah. Neat.21:43
dendrobatesspectorclan: please send it to the mailing list21:44
justinsbSurely the real debate is on who gets a vote, not on the tool we use.  The former will determine the outcome, after all...21:44
dendrobatesspectorclan: you will find that you miss a large part of the community with blog posts21:44
ttxjustinsb: hopefully.21:44
spectorclan_dendrobates: ok, will do that next time, thanks21:44
ttxspectorclan: anything else you wanted to mention ?21:44
pvojustinsb: it is just as much about the transparency of the elections as the candidates21:44
spectorclan_Yes,,,21:44
spectorclan_Design Summit Registration site expected this week; waiting...21:45
spectorclan_on the Rackspace event team to get all the credit card processing in order21:45
spectorclan_Developer party is looking like Dave and Buster's but we are still waiting for other places to get back to us21:45
justinsbpvo: Why is one-vote-per-company less valid than one-vote-per-committer ?  :-)21:45
spectorclan_ttx: that's enough from me for the day; I hope21:46
pvojustinsb: ?? not what I was saying at all....21:46
ttx#topic Open discussion21:47
*** openstack changes topic to "Open discussion"21:47
justinsbpvo: It's just that everything else is a bit of a red herring!  But maybe I misunderstood your point!21:47
dendrobatesI've got something21:47
dendrobatesThis is my last meeting as a rackspace employee21:47
dendrobatesI resigned rackspace and accepted a position at cisco21:48
jaypipescongrats, dendrobates. well, on the new job part...21:48
dendrobatesI will still be working on openstack21:48
spectorclan_Congrats!21:48
dendrobateseven more so21:48
dendrobatesI no longer have the conflict of interest of working at rackspace21:49
ewanmellordendrobates: Congrats!  Will you still be chief benevolent dictator?21:49
dendrobatesso, if I think we RS is doing something wrong, I am free to speak21:49
ttxewanmellor: that position no longer exists in the new governance21:49
ttxewanmellor: a bit dissolved into PTLs.21:50
dendrobatesewanmellor: I'll still be aroundm, you guys will decide my role21:50
dendrobatesI'll do my review days though21:50
dendrobatescisco is building an openstack dev team, btw21:51
tr3buchetinteresting21:51
dendrobatesha21:52
dendrobatesI'm not trolling for rackers.  :)21:52
*** zedas has left #openstack-meeting21:52
edayFor folks not following the ML, burrow (queue service) is switching to Python (from Erlang). C/C++ will be used when optimizations are needed. See ML thread for details.21:53
ttxanything else, anyone ?21:53
dendrobateseday: woohoo21:54
devcamcaralso for folks using openstack-dashboard / django-nova, the django-nova repo has been decommissioned and both projects are rolled up into the openstack-dashboard repo.  the components are still separate but this makes administration much easier21:54
ttxdevcamcar: +121:54
ttxok, let's close this one21:55
*** spectorclan_ has quit IRC21:55
ttx#endmeeting21:55
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:55
openstackMeeting ended Tue Mar  8 21:55:25 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-03-08-21.00.html21:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-03-08-21.00.txt21:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-03-08-21.00.log.html21:55
ttxThanks everyone for attending !21:55
*** dubs has left #openstack-meeting21:55
*** eday has left #openstack-meeting21:55
jaypipesdevcamcar: ++ :)21:56
*** ewanmellor has quit IRC21:57
*** devcamcar has left #openstack-meeting21:57
*** devcamcar has joined #openstack-meeting21:58
*** annegentle has left #openstack-meeting21:59
*** martinr has quit IRC22:02
*** ericrw has left #openstack-meeting22:02
*** Tushar has quit IRC22:02
*** jlmjlm has left #openstack-meeting22:02
*** littleidea has joined #openstack-meeting22:14
*** cynb has quit IRC22:17
*** littleidea has quit IRC22:24
*** dendrobates is now known as dendro-afk22:32
*** sirp_ is now known as sirp22:32
*** martinr has joined #openstack-meeting22:37
*** martinr1 has joined #openstack-meeting22:38
*** martinr has quit IRC22:38
*** justinsb has left #openstack-meeting22:40
*** dabo has left #openstack-meeting22:46
*** johan_ has left #openstack-meeting22:51
*** sirp has quit IRC22:54
*** sirp has joined #openstack-meeting22:54
*** sirp has quit IRC22:54
*** sirp_ has joined #openstack-meeting22:55
*** annegentle has joined #openstack-meeting23:26

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