Tuesday, 2011-01-18

*** dendrobates is now known as dendro-afk00:24
*** westmaas has joined #openstack-meeting01:16
*** dendro-afk is now known as dendrobates02:07
*** westmaas has quit IRC02:31
*** thatsdone has joined #openstack-meeting02:34
*** dendrobates is now known as dendro-afk02:55
*** dendro-afk is now known as dendrobates02:56
*** thatsdon_ has joined #openstack-meeting08:08
*** thatsdone has quit IRC08:10
*** thatsdone has joined #openstack-meeting09:36
*** thatsdon_ has quit IRC09:39
*** thatsdon_ has joined #openstack-meeting12:00
*** thatsdone has quit IRC12:00
*** thatsdon_ has quit IRC12:20
*** thatsdone has joined #openstack-meeting12:20
*** thatsdon_ has joined #openstack-meeting12:38
*** thatsdone has quit IRC12:40
*** dabo has joined #openstack-meeting13:30
*** thatsdone has joined #openstack-meeting13:48
*** thatsdon_ has quit IRC13:50
*** anticw_ has joined #openstack-meeting14:04
*** anticw has quit IRC14:05
*** dendrobates has quit IRC14:08
*** dendrobates has joined #openstack-meeting14:09
*** thatsdon_ has joined #openstack-meeting14:09
*** thatsdone has quit IRC14:10
*** dabo has quit IRC14:19
*** dabo has joined #openstack-meeting14:22
*** dendrobates is now known as dendro-afk14:40
*** thatsdon_ has quit IRC14:50
*** dendro-afk is now known as dendrobates14:59
*** dendrobates has joined #openstack-meeting14:59
*** thatsdone has joined #openstack-meeting15:23
*** westmaas has joined #openstack-meeting15:46
*** bcwaldon has joined #openstack-meeting15:50
*** thatsdone has quit IRC15:52
*** troytoman has joined #openstack-meeting15:56
*** cynb has joined #openstack-meeting16:36
*** thatsdone has joined #openstack-meeting16:53
*** thatsdon_ has joined #openstack-meeting16:54
*** thatsdone has quit IRC16:58
*** nixpert has joined #openstack-meeting17:47
*** nixpert has quit IRC18:33
*** nixpert has joined #openstack-meeting18:34
*** thatsdon_ is now known as thatsdone18:49
*** thatsdone has quit IRC19:05
*** GasbaKid has joined #openstack-meeting19:11
*** dendrobates is now known as dendro-afk19:18
*** bcwaldon has quit IRC19:27
*** glenc has joined #openstack-meeting19:38
*** westmaas has quit IRC19:40
*** westmaas has joined #openstack-meeting19:41
*** bcwaldon has joined #openstack-meeting19:43
*** dendro-afk is now known as dendrobates19:43
*** creiht has joined #openstack-meeting19:54
*** nixpert has quit IRC20:00
*** gustavomzw has joined #openstack-meeting20:02
*** gustavomzw has quit IRC20:05
*** gustavomzw has joined #openstack-meeting20:05
*** gustavomzw has quit IRC20:08
*** henrichrubin has joined #openstack-meeting20:15
*** bcwaldon has quit IRC20:17
*** groo has joined #openstack-meeting20:21
*** groo has quit IRC20:25
*** DigitalFlux has joined #openstack-meeting20:27
*** groo has joined #openstack-meeting20:29
*** bcwaldon has joined #openstack-meeting20:32
*** groo has left #openstack-meeting20:36
*** johnpur has joined #openstack-meeting20:46
*** User613 has joined #openstack-meeting20:47
*** gholt has joined #openstack-meeting20:47
*** User613 has quit IRC20:47
*** User613 has joined #openstack-meeting20:47
*** colinnich has joined #openstack-meeting20:47
*** gustavomzw has joined #openstack-meeting20:48
*** Tushar has joined #openstack-meeting20:49
*** spectorclan has joined #openstack-meeting20:50
*** ttx has joined #openstack-meeting20:50
*** masumotok has joined #openstack-meeting20:54
*** gustavomzw is now known as groo20:55
*** jk0 has joined #openstack-meeting20:55
spectorclanI'm here for a bit20:56
*** jaypipes has joined #openstack-meeting20:57
*** dragondm has joined #openstack-meeting20:58
* ttx feels a bit older today.20:59
* dragondm waves 20:59
*** kpepple has joined #openstack-meeting21:00
*** vishy has joined #openstack-meeting21:00
ttxooook, let's get started, we have a large agenda today21:00
*** koji-iida has joined #openstack-meeting21:00
openstackMeeting started Tue Jan 18 21:00:48 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
*** eday has joined #openstack-meeting21:00
ttxWelcome to our weekly OpenStack team meeting...21:00
ttxToday's (long) agenda is at:21:01
ttx#link http://wiki.openstack.org/Meetings21:01
ttx#topic Actions from previous meeting21:01
ttx* ttx to document simplified exception procedure in wiki: DONE21:01
ttx#topic Current release stage: QA21:01
ttx#info We are now passed FeatureFreeze and well into QA stage. The goal is to test, find and fix as many bugs as we can before GammaFreeze.21:02
ttxAfter GammaFreeze the idea is to restrict bugfixing to release-critical issues only, in order to avoid introducing regressions... a known bug being better than an unknown regression21:02
ttxThat said, on the release schedule, GammaFreeze is EOD on Tuesday, January 25. I wonder if we shouldn't push that back to EOD Thursday, January 27.21:02
*** sandywalsh_ has joined #openstack-meeting21:02
ttxGiven the number of new things that landed in this release, maximizing random bugfix time sounds like a good idea for Nova...21:02
*** ewanmellor has joined #openstack-meeting21:03
ttx3 business days between GammaFreeze and RCFreeze should be enough to spot and fix regressions.21:03
ttxThoughts ?21:03
dendrobatesonly if we stop new merges21:03
ttxdendrobates: new merges ?21:03
devcamcarwould be nice to have til 27th for gamma21:04
devcamcarhow are we supposed to fix bugs if we can merge? :)21:04
dendrobatesttx: there are still some outstanding questions that we are going to discuss later in the meeting.21:04
dendrobatesttx: I just mean we need to decide today and not draw anything out21:04
ttxok, maybe revisit that question at the end of the meeting then.21:05
ttxMoving on21:05
ttx#topic Release status21:05
ttx#link http://wiki.openstack.org/releasestatus/21:05
ttxWe still have 2 feature branches in the FeatureFreezeException track:21:05
ttxjaypipes: could you give us a quick summary of the situation ?21:06
*** DigitalFlux has quit IRC21:06
ttxor maybe ewan21:06
ewanmellorright here21:06
ttxewanmellor: could you give us a quick summary of the situation ?21:06
jaypipesxenapi-glance-2 was delayed because of Glance packaging issues. that has been fixed, but there were other bugs in Glance that showed up. the one right now that is a showstopper is appparent large file upload limitations...21:07
jaypipesSo, while citrix' code is fine, glance has bugs that may be showstoppers for merging that code in.21:07
ttxjaypipes: and we are still a few days away from getting those ironed out, right21:08
ewanmellorWe've worked around those problems by registering images by URL rather than by upload21:08
jaypipesttx: and since I'm currently the only one working on glance bugs, it's a little tough to predict if I can get them all fixed in time .21:08
jaypipesewanmellor: sure, but that's a limitation for sure..21:08
*** DigitalFlux has joined #openstack-meeting21:08
ttxSo from a release management perspective, I want us to stop merging new code asap...21:08
ttxBut it's up to the nova-core team to determine if it's ready to go in or not.21:09
jaypipesttx: like I said, it's not the xenapi-glance-2 code that's buggy, it's glance...21:09
ewanmellorThere's no reason to block the Nova half of the code because of a bug in Glance.21:09
ewanmellorjaypipes: Thanks ;-)21:09
ttxjaypipes: so should we merge the code ?21:10
ttxthe code is fine, the feature is not, IIUC21:10
devcamcarewanmellor: agree, lets merge the branch and let the glance bug be a glance bug21:10
jaypipesttx: that is true, actually, there are 2 workarounds... one for glance (use x-image-meta-location) and one is just use nova-objectstore...21:10
ewanmellorI can get someone to help with the Glance bugs.21:10
jaypipesttx: I don't want to make the final call, because it's my bugs that are the issue...21:10
* jaypipes hides sheepishly...21:11
ttxany other nova-core dev wanting to chime in ?21:11
jaypipesttx: devcamcar says proceed...21:11
sorenjaypipes: Are the glance problems likely to be resolved any time soon?21:11
jaypipessoren: hopefully, yes.21:11
dendrobatesI say merge it21:11
jaypipessoren: there were, like 6 bugs, and I've fixed all but 1 of them..21:11
xtoddxare we talking about merging a branch we can't test?21:11
jaypipesxtoddx: no.21:11
xtoddxthen merge21:12
jaypipesxtoddx: it has unit tests and has functional testing ability (with the workarounds mentioned above)21:12
ttxok, then please one of you set the branch to approved now :)21:12
jaypipesdevcamcar: go for it.21:12
creihtjaypipes: If the only problem is the large file uploading one, that should be fixable21:12
ttxsecond feature branch left:21:13
jaypipesttx: I'll try to get that remaining bug resolved, and in the unlikely event I cannot resolve it, we'll make a note in the release about the workarounds.21:13
*** bcwaldon has quit IRC21:13
ttxtermie: could you give us a quick summary of the situation, though I guess that will quickly bring us to the next topic...21:13
ttxjaypipes: works for me21:13
jaypipescreiht: yeah, that's the only bug left.21:13
termiethe branch is essentially done, it has just been being updated to track trunk changes to db schema21:13
termiethe latest tracking brought me to the changes introduced by live_migration21:13
*** tonywolf has joined #openstack-meeting21:14
termiewhich is up for some debate and the db_migration branch is stalled on it21:14
sorenCan you explain how db_migration is stuck because of it? It's not entirely clear to me.21:14
jaypipesno debate in my mind... I've voted for a reversion of live-migration and a merge of db-migration...21:14
*** enigma has joined #openstack-meeting21:14
termielargely in that the schema changes it suggests do not appear to be completely thought out21:14
ttxok, let's switch to the next topic then21:15
ttx#topic Live-Migration patch21:15
ttxvishy/termie: floor is yours.21:15
*** bcwaldon has joined #openstack-meeting21:15
termiesure, some discussion has already happened over on https://code.launchpad.net/~termie/nova/revert_live_migration/+merge/4666021:15
vishybasically there are a number of issues with the patch21:16
ttxtermie: wouldn't it be simpler at this point to just fix the remaining issues ?21:16
termiethe gist of it is that i think the code review of the live_migration branch failed to identify issues21:16
vishythere are two options: keep the merge in and fix the issues21:16
termiettx: not nearly so simple as reverting the patch, no21:16
termiettx: there are no tests in the patch21:16
vishyor revert the merge and let the original author fix the issues21:16
ttxtermie: "revert+fix+rereview" is not simpler than "fix"21:17
termiettx: yes it is when there are no tests21:17
termiettx: and we are only talking about revert here21:17
sorentermie: I can't help but wonder why you didn't raise these issues while this patch was being reviewed?21:17
termiesoren: i didn't review the patch21:17
termiesoren: i don't believe i am expected to review them all?21:17
sorenAre you in nova-core?21:18
*** glenc_ has joined #openstack-meeting21:18
jaypipesOK guys, let's cool it.21:18
vishyI think we have failed as a team in terms of reviewing21:18
ttxtermie: if we revert it, that means we push it back to Cactus. We can't wait for another review cycle.21:18
dragondmcouldn't we implement some test-coverage requirement hook/test in hudson??21:18
jaypipesA number of us were on vacations, let's be more reasonable here..21:18
termiettx: i think it should be pushed back to after bexar, yes21:18
ttxtermie: I'm fine with that, just explaining what "reverting" exactly means21:18
dendrobatesvishy: I agree we have failed21:18
edaydragondm: we already have coverage checks, we're just not enforcing anything. but, yes, we could21:18
sorendragondm: Current trunk would fail such a test, probably.21:19
vishywe need to have a discussion about nova-core and reviews.  We proposed to the community that they could submit patches before BMPF and that we would help them prepare for FF21:19
vishywe clearly did not do that well for this patch21:19
*** glenc has quit IRC21:19
vishyand most of the external patches were probably under-reviewed21:19
jaypipesagreed, for this specific patch. most other patches had a lot of review, however (xenapi-glance-2, for instance..)21:20
vishysoren and I hit most of them, but we did it too late and too quickly imo21:20
*** glenc_ is now known as glenc21:20
jaypipesvishy: sorry, what did you mean by "external patches"?21:20
termiejaypipes: i think he means patches not coming from core team members21:20
vishyjaypipes: patches done by non- nova-core members21:21
jaypipesah, k.21:21
termiejaypipes: we tend to talk about our own patches amongst ourselves more21:21
devcamcaryea i did notice a number of patches that weren't reviewed by nova-core but were still approved21:21
sorenvishy: At some point, I did switch into "alright, I think this is `good enough`, we can fix the remaining issues after the freeze" sort of mode.21:21
devcamcaris there some way to enforce that?21:21
sorenvishy: Perhaps not entirely consciously.21:21
jaypipesI think some non-core patches were very heavily reviewed (all of the citrix ones at least). the reason is because we were able to go through 5-6 cycles for each of the patches..21:21
*** westmaas has quit IRC21:21
ttxIn the end it's a chief architect / nova-core decision. Is it good enough ? I just set the deadline.21:21
vishysoren: me too21:22
sorendevcamcar: Whuh?21:22
sorendevcamcar: Example?21:22
jaypipesdevcamcar: that's not possible AFAIK...21:22
*** westmaas has joined #openstack-meeting21:22
ttxdevcamcar: only nova-core can approve21:22
vishyit is possible if someone from nova-core doesn't wait for the second approval21:22
devcamcari could have sworn i saw a few, maybe i'm wrong21:22
dendrobatesadding to nova core and having more people doing reviews would be helpful21:23
jaypipesvishy: yes, that is true.21:23
sandywalsh_dendrobates, +121:23
sorenTo me, being in nova-core means you *must* do reviews.21:23
ttxsoren: +121:23
ttxnova-core is a duty, not a right21:23
sorenMembership in nova-core is..21:23
sorenright, precisely.21:23
*** spectorclan has quit IRC21:23
dendrobatessoren: I am working on a definition of core dev for the wiki21:24
vishypeople that don't have time to review sould remove themselves from nova-core so we know how many active reviewers we have21:24
jaypipesGuys, I think we should keep some perspective here... granted, this live-migration patch was a mess, but overall, we reviewed dozens of patches in the last week or so...21:24
dendrobatesshould be published tonight21:24
sorenvishy: Fully agreed.21:24
*** pvo has joined #openstack-meeting21:24
termieif nova-core means must then require sizeof(nova-core) approvals21:24
vishyjaypipes: true...its the big ones that no one wants to touch21:24
creihtWe should ask lp to have a popup when you hit the approve button to confirm that all unit tests were run and that they did indeed read the code21:25
termiecreiht: we should ask lp to have line-by-line code review21:25
jaypipesvishy: not necessarily :) I reviewed some pretty big ones...but just did not get around to live-migrations for some reason..21:25
vishyin any case we can go on about fixes to the process, but we need to take action on this particular patch, so what should we do?21:25
sorentermie: No, we shouldn't. I don't want to use a web UI to do code review.21:25
sorenFix the patch.21:25
devcamcarit can be tough to review the larger patches solo21:26
jaypipesis this a vote then? revert vs. fix patch?21:26
devcamcarit would be valuable to have a way to review virtually as a group21:26
vishyi feel that it was our (nova-core's) failure and to show good faith to the community we should fix it ourselves.21:26
termiedevcamcar: standard line-by-line code review handles group interaction well21:26
dendrobatesfix, basically because we messed up.21:27
devcamcartermie:  yes it does but lp doesn't do it =x21:27
xtoddxrevert, and fix in a branch ourselves?21:27
sorenJust to be clear: Revert means revert the patch and refuse the feature for bexar?21:27
xtoddxdefinitely revert though21:27
ttxxtoddx: there is no time left for that option21:28
devcamcarjust playing devil's advocate - why is it our job to fix as opposed to authors21:28
xtoddxttx: for cactus then21:28
jaypipessoren: yes21:28
sorendevcamcar: We approved it.21:28
ttxxtoddx: ack21:28
dendrobateswe shoudn;t have merged it, but once we did, we all own it.21:28
ttxsoren: yes21:28
sorenIf people hated the patch so much, they should have said something. Really.21:28
vishydevcamcar: and we didn't review it in a timely manner as outlined for the process for getting stuff in.21:28
devcamcarok, change my vote to fix21:28
devcamcarotherwise its not going in this release21:29
termiesoren: you should have reviewed it better, you can't blame that on somebody else21:29
ttxI'm not nova-core, but I prefer to "fix", not because otherwise it won't make it into this release, but to be fair to the proposer21:29
sorentermie: I'm not.21:29
jaypipestermie: it's not all on soren. we all played a role.21:29
sorentermie: How am I blaming anyone else?21:29
ttxsince he proposed well before the branchmergeproposalfreeze21:29
termiesoren: "if people hated the patch so much..." etc21:30
sorentermie: If I were proposing to revert, *then* I'd be a hypocrite.21:30
termiesoren: we depend on the people who review something to do it correctly21:30
termieotherwise we _all_ have to look at eevery patch21:30
devcamcartermie, soren: take it to pms21:30
vishytermie: I'll take credit for being lazy with the review21:30
sorenMe too, for sure.21:31
ttxI take my part in the blame -- I pushed for getting stuff merged21:31
xtoddxwe don't need to assess blame, we just need to move on21:31
jaypipesxtoddx: ++21:31
ttx(though I also pushed for getting stuff reviewed :)21:31
sorenI decided to let it in and fix things after the fact.21:31
ttxit's about half/half votes21:31
sorenI figured it'd be faster, and the really tricky bits seemed ok.21:31
vishyforget blame, I'm taking credit...laziness is an asset! :)21:31
dendrobatesI think we can agree to fix the process and not let this happen again.21:31
creihtat least it was pep8 compliant ;)21:31
ttxsounds like it's time for some chief architect fiat21:31
jaypipescreiht: had to go there, didn't ya? :P21:32
ttxcreiht: it wasn't until the last review21:32
johnpurwho is volunteering to make the fix and get it reviewed if we vote for fix?21:32
xtoddxwe have a policy of piece-meal commits to keep size down, so approving a half-baked commit should be expected occasionally.21:32
dendrobatesttx: what was the vote?21:32
termiejohnpur: looks like me21:32
ttx"fix" vs. "revert and defer to cactus"21:32
termiethere are no tests though21:32
termieso it can't be fixed21:32
johnpurtermie: how much time will this take?21:32
ttxI don't tjhink it would just fall on termie21:33
dendrobatessoren: you should help to.21:33
johnpurcan we get tests from the original author21:33
vishymasumotok can probably help21:33
vishyjohnpur: lets ping him for some tests21:33
termietests usually take longe rot write than the code, for the record21:33
johnpurtermie: a sad fact!21:33
vishymeanwhile we can clean up formatting issues and such21:34
masumotokhow much time ca I have to add the test?21:34
johnpurttx: how long can we reasonably take?21:34
xtoddxlets aim for landing the fix before gamma freeze?21:34
ttxjohnpur: depends on how much that blocks db-migration21:34
ttxI want db-migration in21:34
sorenMe too.21:34
johnpurme too21:35
ttxsince its 1k lines still needing to hit trunk21:35
termiettx: they are self-contained lines21:35
vishymasumotok: hi, didn't know you were here21:36
termiettx: so it doesn't affect much by waiting, i'd like it in too but we will have to change that code again once the new changes happen21:36
termieso either i update it to fit with current and then make another branch after this fixes branch goes in21:36
jaypipesisn't gamma freeze in 8 days? can we get tests in next 2 days and reviews in an additional day?21:36
ttxOK. Let's give the db-migration branch until the end of the week21:36
johnpurttx: agree21:36
xtoddxdo we want to aim for tests from masumotok by end of week, leaving the weekend and until tuesday to land fixes to that branch and migrations before gamma freeze?21:36
ttxsince it was expected to be the last branch anyway, by design21:36
termiemasumotok: i am happy enough to work wiht you to write tests, i don't think this will be a very easy thing to test21:37
jaypipesxtoddx: that's pushing it a bit thin IMHO.21:37
termiemasumotok: but i have worked with testing a lot so maybe can offer assistance21:37
dendrobatesdown to the wire again :(21:37
johnpurdendrobates: that's how we roll!21:37
xtoddxjaypipes: then lets make a post-gamma exception and get it in before release candidate freeze?21:37
ttxxtoddx: no way21:37
xtoddxwe want both features, what the other option?21:38
jaypipesxtoddx: no, I was suggesting the other way :) reviews complete by end of week, tests done by Thursday.21:38
ttxI think we have enough time21:38
dendrobatesif the tests don;t arrive at that late date, what would we do?21:38
dendrobatesrevert right before release21:38
jaypipesmasumotok: think you can get your team to get tests done by Thursday end of day UTC?21:39
ttxdendrobates: the end of this week is not right before release21:39
termiei would say revert now if matsumotok is on board and he can just work on cleaning the branch up more21:39
masumotokjaypipes: yes21:39
dendrobatesttx: I meant post gamma21:39
*** MrKohonen has joined #openstack-meeting21:39
johnpurdendrobates: let's make sure that doesn't happen.... sounds like there is a lot of help ready to write the tests21:39
edayI'm thinking we revert and merge db migration today. if we can get it fixed up before freeze, it makes it, if not, it's not a big revert at the last minute21:39
ttxdendrobates: no way I'll let that overflow to next week, lest postgamma21:39
termieeday: +121:39
jaypipestermie: I'm on the fence with this one...21:39
dendrobateseday: that is starting to seem more sane to me21:40
jaypipeseday: that was termie's original suggestion, and what I voted for originally...21:40
vishyeday: I'm ok with that proposal if masumotok is ok with it21:40
edayjaypipes: yup21:40
johnpurjaypipes: time to get off the fence, let's decide21:40
dendrobatesI think we are waiting for masumotok21:40
ttxI feel comfortable merging db-migration late... but not so much merging live-migration late21:40
dendrobatesttx: why?>21:41
*** pvo is now known as pvo_away21:41
jaypipesjohnpur: revert live-migrations, merge db-migrations, masumotok to make tests by thursday, nova-core to get reviewed by end of this week.21:41
*** pvo_away is now known as pvo21:41
masumotokEnd of the thursday I submit the test code, do I?21:41
ttxbecause db-migration is relatively self-contained21:41
jaypipesmasumotok: yes, along with the rest of the patch, which we'll revert to get the db-migrations patch in.21:41
masumotokjaypipes: that is fine.21:42
dendrobatesok, done.21:42
jaypipesmasumotok: and you have nova-core to assist with you in the tests as you need it.21:42
*** MrKohonen has quit IRC21:42
dendrobatesnot really, who is going to handle reverting?21:42
jaypipesdendrobates: it's already proposed by termie..21:42
ttxdendrobates: termie has a branch up for it21:42
termiedendrobates: already submitted the merge prop21:42
xtoddxdendrobates: termie has a branch21:43
dendrobateseasy then21:43
sorenttx: Can you post a summary of this discussion?21:43
sorenttx: On that bpm?21:43
johnpurall: nice conclusion21:43
sorenbmp, even.21:43
ttxsoren: I will. Tomorrow21:43
*** annegentle has joined #openstack-meeting21:43
xtoddxhaha, i read that as "eday then"  which was quite the non-sequitur.21:43
ttx#action ttx to summarize the decision on live-migration21:43
*** diegoparrilla has joined #openstack-meeting21:43
dendrobatesttx: what, you can't work all night?21:43
ttxdendrobates: that depends how much more you can pay me21:43
ttx#topic D release naming21:44
ttxOK, funnier discussion now.21:44
ttxAs we move closer to Bexar release, we need to discuss the name of the "D" release.21:44
ttxI summed up the rules of the game at:21:44
ttx#link http://wiki.openstack.org/ReleaseNaming21:44
ttxThere aren't so many cities and counties in California starting with a D, but some people added new ones21:44
ttxPlease dump your preference on the channel for a highly scientific popularity contest !21:44
ttxSounds like it boils down to dublin vs. Diablo21:45
xtoddxI like Dublin.  Mostly because of Dr Pepper21:45
ttxDublin !21:45
termiei think danville is pretty funny21:45
termieas a california native21:45
kpeppleDownieville (http://en.wikipedia.org/wiki/Downieville,_California)21:45
ttxstephenspector asked me to vote "Diablo" for him21:45
sorenDiablo sounds awesome.21:45
* jaypipes was joking... diablo sounds good to me.21:45
xtoddxDublin does double duty as a tx city and a ca city21:45
diegoparrillaDiablo, no doubt21:46
* creiht like Dublin21:46
termieeasier to drink beer from dublin to celebrate, also21:46
* vishy votes for Dorris21:46
jaypipesdiegoparrilla: ah, hola. :)21:46
edayso we are ok with diablo but not corpus-christi? :)21:46
sorenYes. :)21:46
ttxeday :)21:46
creihtand don't forget dublin sugar dr pepper :)21:46
daboDiablo has more non-city meaning than Dublin21:46
* sandywalsh_ looks for the lightning clouds21:46
jaypipescorpus christi isn't in California. :P21:46
termiediablo just makes me think of the video game21:47
daboHard to explain it's supposed to be a city reference21:47
* creiht thinks diablo is a dumb name for a release21:47
termieclicking on pale yellow artifacts21:47
* dabo votes for Dublin21:47
edayjaypipes: for the C release we shot it down due to religious implications21:47
jaypipeseday: yes, I know. :) I was pulling your chain.21:47
ttxso let's count21:47
zuldiablo is not religious? ;)21:47
soreneday: What's that? diablp?21:47
daboeday: Diablo should go for the same reason21:47
creihtHow about... wait for it... 1.0? :)21:47
* jaypipes kickbans creiht.21:48
diegoparrillajaypipes: hi!21:48
xtoddxcreiht: pffft.  thats so 1990s21:48
xtoddxcreiht: did you just vote to name it dabo?21:48
dabocreiht: 1.0 doesn't start with 'D'21:48
daboYeah, let's call it dabo!! :)21:48
ttxso it looks like it's Diablo vs. Dublin21:48
vishywe'll create a new city21:48
ttxwith Diablo leading a bit, but having strong advocates against it21:49
jaypipesDublin then is my vote...since it's more identifiable as a city..21:49
sandywalsh_Dumas (dumbass)21:49
annegentleDanville LOL. Just got it. I'm slow.21:49
* creiht thinks it is funy that you drop Corpus Christi for religious reasons, but don't for diablo21:49
* vishy still thinks Dorris is incredible21:49
creihtsandywalsh_: ++21:49
dabojaypipes: ...even if most won't know it's in CA21:49
pvottx: surveymonkey?21:50
ttxpvo: yeah, that dodn't exactly turned out to be the global consensus I hoped :)21:50
edayI say DIablo, and during the diablo summit, we take a field trip and hike mt diablo21:50
sorenOf course we want the one with the *fewest* google hits for better ranking. :)21:50
johnpurDeath Valley?21:51
creihtrelease del diablo21:51
ttxjohnpur: rha21:51
dabojohnpur: yeah, that's the vibe we want!21:51
vishysoren: http://www.googlefight.com/index.php?lang=en_GB&word1=diablo&word2=dorris21:51
xtoddxjohnpur: i like it, its edgy21:51
sandywalsh_Dumas is just down the road from Cactus actually21:51
ttxdendrobates: do you have enough momentum for Diablo to decide it, or should we move to a more scientific voting technique ?21:52
pvoscience. meh21:52
dendrobatesI say put up a voting21:52
pvoyea, I do too21:52
ttxok, I'll condorcet it21:52
dendrobateslet everyone vote, not just those on IRC now.21:52
termiehow can you vote against puppies?21:53
edayshoudl we really spend more time on this? setting up a vote and whatnot? dendrobates, just pick one :)21:53
ttx#action ttx to turn his failed IRC attempt to a real vote21:53
sandywalsh_so, top three choices are Diablo, Death Valley and Dublin?21:53
creihtanyone but diablo21:53
annegentleDanville, Dumas, Death Valley, Dublin?21:54
*** kpepple has quit IRC21:54
devcamcarvote = dublin21:54
termiei can hook us up with some danville locals if we want to celebrate in danville21:54
ttxok, dendrobates said "put up a vote", I'll do that unless someone else feels up to it21:54
ewanmellorPlease not Death Valley.  Two-word release names are really irritating.21:55
ttx#topic open discussion21:55
creihtSo is it still in question on weather or not diablo is in the running?21:55
ttxewanmellor: rules of the game say "single word, 10 char max"21:55
edaydendrobates: dublin or diablo, pick one :)21:55
dendrobatesdamn, lay off!21:55
* notmyname votes dublin21:55
xtoddxyea, more dublin momentum, keep it coming!21:56
* ttx makes mental note: Never discuss release naming on IRC again21:56
dendrobatescorpus christie was not officially rejected, so I see no reason that diablo should be21:56
edayfunny thing is, ultimately, no one really cares ;)21:56
ewanmellorttx: lol21:56
xtoddxtts: you should know how the internet works by now21:56
jk0eday: ++21:56
ttxeday: exactly21:56
xtoddxjohnpur: to apple21:56
jaypipeseday: exactly. the only release anyone ever cares about is the one that isn't released yet...21:57
ttx"Downey" seems a bit dangerous for a production release21:57
xtoddxttx: it'll probably develop a drug habbit21:57
johnpurooooh.... Dulzura?21:57
ttx"The Disneyland release"21:57
* jaypipes picked a bad week to stop sniffing glue.21:57
* eday goes back to real work21:57
openstackMeeting ended Tue Jan 18 21:57:48 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-01-18-21.00.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-01-18-21.00.txt21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-01-18-21.00.log.html21:57
pvothank you21:57
jaypipesAnd I'm spent.21:58
ttxThanks everyone, keep them coming :)21:58
johnpurha ha21:58
*** creiht has left #openstack-meeting21:58
*** jk0 has left #openstack-meeting21:58
*** eday has left #openstack-meeting21:58
*** ewanmellor has left #openstack-meeting21:59
*** bcwaldon has left #openstack-meeting21:59
*** koji-iida has left #openstack-meeting21:59
*** henrichrubin has left #openstack-meeting21:59
vishyoh doh I had one other thing that i had...taking it to openstack21:59
*** groo has left #openstack-meeting22:00
*** westmaas has quit IRC22:03
sorenannegentle: Don't feel bad. I *still* don't see what's funny about "Danville".22:03
*** dragondm has left #openstack-meeting22:03
annegentlesoren: it's funny to me because of watching Phineas and Ferb - that's where they live. Sorta like the Simpson's Springfield.22:04
sorenannegentle: Oh!22:04
annegentlesoren: there's one in every state I suppose :)22:04
sorenannegentle: I've only seen two or three episodes. :( Not enough for that sort of trivia to stick :)22:05
sorenOur S release should totally be Springfield.22:05
annegentleheh, yeah :)22:05
*** annegentle has left #openstack-meeting22:08
*** gholt has left #openstack-meeting22:08
*** dendrobates is now known as dendro-afk22:13
*** dendro-afk is now known as dendrobates22:13
*** colinnich has left #openstack-meeting22:20
*** masumotok has quit IRC23:02
*** johnpur has left #openstack-meeting23:24
*** diegoparrilla has left #openstack-meeting23:29
*** pvo is now known as pvo_away23:37
*** troytoman has quit IRC23:37
*** zul has quit IRC23:37
*** GasbaKid has quit IRC23:45
*** dendrobates is now known as dendro-afk23:48
*** enigma has left #openstack-meeting23:50
*** Tushar has quit IRC23:51

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