| *** dendrobates is now known as dendro-afk | 00:18 | |
| *** jc_smith has quit IRC | 00:24 | |
| *** jc_smith has joined #openstack-meeting | 00:50 | |
| *** jc_smith has quit IRC | 01:16 | |
| *** dendro-afk is now known as dendrobates | 01:45 | |
| *** littleidea has quit IRC | 01:58 | |
| *** littleidea has joined #openstack-meeting | 02:13 | |
| *** spectorclan has quit IRC | 05:47 | |
| *** spectorclan has joined #openstack-meeting | 05:51 | |
| *** dabo has joined #openstack-meeting | 13:24 | |
| *** littleidea has quit IRC | 14:39 | |
| *** littleidea has joined #openstack-meeting | 14:41 | |
| *** littleidea has quit IRC | 14:42 | |
| *** littleidea has joined #openstack-meeting | 14:46 | |
| *** littleidea has quit IRC | 14:49 | |
| *** littleidea has joined #openstack-meeting | 15:43 | |
| *** xfaf has joined #openstack-meeting | 16:00 | |
| *** zul has quit IRC | 16:01 | |
| *** xfaf is now known as zul | 16:01 | |
| *** creiht has joined #openstack-meeting | 20:17 | |
| *** masumotok has joined #openstack-meeting | 20:53 | |
| *** jbryce has joined #openstack-meeting | 20:54 | |
| *** dubs has joined #openstack-meeting | 20:54 | |
| *** ttx has joined #openstack-meeting | 20:54 | |
| *** annegentle has joined #openstack-meeting | 20:57 | |
| ttx | o/ | 21:00 |
|---|---|---|
| chmouel | hello | 21:00 |
| dabo | o/ | 21:00 |
| *** ewanmellor has joined #openstack-meeting | 21:00 | |
| * ttx waits one more minute | 21:01 | |
| *** alekibango has quit IRC | 21:01 | |
| *** jk0 has joined #openstack-meeting | 21:01 | |
| *** alekibango_ has joined #openstack-meeting | 21:01 | |
| ttx | ok, let's go | 21:01 |
| soren | o/ (-ish) | 21:01 |
| ttx | #startmeeting | 21:01 |
| openstack | Meeting started Tue Dec 7 21:01:56 2010 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 21:01 |
| vishy | o/ | 21:02 |
| ttx | Welcome to our weekly OpenStack team meeting... | 21:02 |
| *** mattt has joined #openstack-meeting | 21:02 | |
| ttx | Today's agenda is at: http://wiki.openstack.org/Meetings | 21:02 |
| ttx | Nobody added any topics, should be a quick one. | 21:02 |
| ttx | #topic Actions from previous meeting | 21:02 |
| ttx | * dendrobates to merge (or delegate merging of) the MLs, keep the archives | 21:02 |
| ttx | I saw the email about the simplification of the development MLs | 21:03 |
| ttx | Apparently the 8 remaining mailing-lists at http://wiki.openstack.org/MailingLists are still up, though. | 21:03 |
| ttx | spectorclan: do you plan to remove them ? or merge them into a single "partner" list ? | 21:03 |
| *** alekibango_ is now known as alekibango | 21:03 | |
| *** romohr has joined #openstack-meeting | 21:03 | |
| ttx | For the record, all combined, those 8 mailing-lists had 3 messages posted to them so far. | 21:03 |
| ttx | Mostly "welcome to the list" messages. | 21:03 |
| *** termie has joined #openstack-meeting | 21:04 | |
| ttx | #action ttx to clarify with spectorclan / dendrobates the future of the "other" MLs | 21:05 |
| alekibango | merging is not needed imho | 21:05 |
| spectorclan | ttx: sorry, on wrong list | 21:05 |
| alekibango | if some of those lists will be low traffic, good for them | 21:05 |
| ttx | <spectorclan> ttx: the plan is to keep all the other lists up and running for now | 21:05 |
| spectorclan | ttx: I still plan to keep them alive for now even though most are not in use yet | 21:05 |
| ttx | spectorclan: ok, we can discuss that off-meeting | 21:05 |
| spectorclan | the operators list will be the user community support list | 21:05 |
| ttx | * jaypipes and mtaylor to help Tushar set up his i18n efforts | 21:06 |
| soren | I thought we all aggreed on that last week? | 21:06 |
| soren | Err. | 21:06 |
| soren | Not the i18n thing. | 21:06 |
| soren | The consolidation thing. | 21:06 |
| *** johnpur has joined #openstack-meeting | 21:06 | |
| soren | Of the mailing lists. | 21:06 |
| ttx | soren: for some definition of "all" | 21:06 |
| *** murkk has joined #openstack-meeting | 21:06 | |
| soren | Enough for it to matter, I thought. | 21:07 |
| ttx | I'll clarify with the owners, let's move on | 21:07 |
| ttx | jaypipes and mtaylor are not around | 21:07 |
| *** sirp1 has joined #openstack-meeting | 21:08 | |
| ttx | nor Tushar. | 21:08 |
| ttx | I'll report it to next week | 21:08 |
| ttx | #action jaypipes and mtaylor to help Tushar set up his i18n efforts | 21:08 |
| ttx | #topic Current release stage: Implementation | 21:08 |
| ttx | We are one month away from the BranchMergeProposalFreeze (Jan 6). | 21:08 |
| ttx | Given that the end of month is likely to be disturbed by holiday celebrations, we should get as much as we can done this week and the next. | 21:09 |
| ttx | For core team(s), do you think there is value in having some common calendar where we can enter our planned vacation days ? | 21:09 |
| ttx | That could help people to know who will or won't be around... That would be opt-in obviously. | 21:09 |
| ttx | opinions ? | 21:10 |
| soren | I wouldn't mind that at all. | 21:10 |
| eday | I wouldn't really use it, but don't mind :) | 21:10 |
| johnpur | sounds good to me. | 21:10 |
| termie | perhaps a better question would be to ask who would use it | 21:11 |
| *** Tushar has joined #openstack-meeting | 21:11 | |
| soren | I would put my info in it, and I would look up other people's availability. | 21:11 |
| ttx | sandywalsh suggested it. he said that could help people proposing branches to know which reviewers they can expect to work during the christmas break | 21:11 |
| creiht | or we can just be reasonable, and expect nothing to get done, and be happy if something does :) | 21:12 |
| ttx | #action ttx to investigate calendar options | 21:13 |
| ttx | ok, moving on, too much enthusiasm :) | 21:13 |
| ttx | #topic Release status | 21:13 |
| ttx | #info Swift: https://blueprints.launchpad.net/swift/1.2 | 21:13 |
| soren | ttx: There's something I think we need to clarify with regards to the blueprint process. | 21:13 |
| ttx | soren: fire | 21:14 |
| soren | I had a bit of chat earlier today with someone not currently involved with the project who wanted to work on something, but the blueprint for it was "awaiting approval". They thought that meant they weren't allowed to work on it and that proposals for it to be merged would be rejected. | 21:14 |
| soren | ...and that's not entirely accurate, but I can totally see why they think that. | 21:14 |
| ttx | hmm, I can see why too | 21:14 |
| soren | Good patches (before the deadline) are always welcome, but I'm not sure how to convey this in a way that also explains why people really should write design documents first and discuss them. | 21:15 |
| soren | Something to think about. | 21:15 |
| ttx | "Pending approval" is not a permanent state anyway | 21:15 |
| *** dragondm has joined #openstack-meeting | 21:15 | |
| ttx | it should definitely get accepted or back to drafting | 21:15 |
| ttx | that said... | 21:16 |
| ttx | Blueprints have two sets of status. One for Design and one for Implementation | 21:16 |
| ttx | You can have a branch ready 'implementation in "beta available" and still not have your design approved | 21:16 |
| *** pino201 has joined #openstack-meeting | 21:17 | |
| ttx | soren: but I see your point, I'll try to insist on that in doc | 21:17 |
| ttx | Back to release status: | 21:17 |
| ttx | Swift is looking good, with client-side-chunking branch getting reviewed now | 21:17 |
| ttx | #info Glance: https://blueprints.launchpad.net/glance/bexar | 21:18 |
| ttx | Glance is also looking good. The clients stuff apparently landed (wanted a confirmation from jaypipes that the spec was complete now), and teller-api is almost complete | 21:18 |
| ttx | #info Nova: https://blueprints.launchpad.net/nova/bexar | 21:18 |
| ttx | Nova is a bit more complex, like I mentioned in a recent email I'm trying to come up with a list of stuff that we can reasonably announce will be in Bexar. | 21:19 |
| ttx | By next week I'll have talked to most of you and the list should be much more usable. | 21:19 |
| ttx | Questions ? | 21:19 |
| johnpur | 1 essential bp that is not started | 21:19 |
| ttx | johnpur: xs-snapshots ? | 21:20 |
| johnpur | yes | 21:20 |
| pvo | it has been looked at but not started. I know our guys were looking at it. | 21:20 |
| pvo | I owe ttx an owner by friday | 21:20 |
| soren | I don't think assigned stuff to a team is generally a good idea. | 21:20 |
| johnpur | ok | 21:20 |
| pvo | not to a team, but to a single person. | 21:20 |
| ttx | I think the core xenserver dev env is now set up, so xs-snapshots is next | 21:20 |
| soren | It's assigned to Ozone. | 21:20 |
| soren | Who's he? :) | 21:21 |
| johnpur | soren: i agree | 21:21 |
| pvo | right, because no one has owned it yet. | 21:21 |
| soren | Right,that's my point. | 21:21 |
| soren | It shouldn't be assigned. | 21:21 |
| pvo | as I said above, I'm going to have it assigned to a person by friday | 21:21 |
| alekibango | if blueprint is not accepted it looks like its feature not wanted... unaccepted blueprints should be talked about with authors... imho | 21:21 |
| pvo | soren: but I see what you mean | 21:21 |
| ttx | pvo will assign someone I can pester all the time, by the end of the week. | 21:21 |
| soren | It was more of a general observation really, just triggered by seeing it here. | 21:21 |
| soren | Assigned to a team == not really assigned to anyone | 21:22 |
| soren | In my reading, at least. | 21:22 |
| ttx | soren: in my reading too. | 21:22 |
| alekibango | so they will have chance to redraft it soon enough, or to know what is wrong, why it is not accepted | 21:22 |
| *** sandywalsh has joined #openstack-meeting | 21:22 | |
| ttx | soren: but BP don't have tags, so sometimes assigning to a random group help you get a list | 21:22 |
| pvo | soren: I saw it was Ozone was responsible, but not assigned to a person yet. | 21:22 |
| ttx | #topic Open discussion | 21:23 |
| ttx | anything else anyone ? | 21:23 |
| johnpur | has someone picked up responsibility for the OpenStack API? | 21:23 |
| eday | reviews!! (for nova) | 21:23 |
| soren | ttx: Good point. | 21:23 |
| johnpur | i know we are waiting on RAX updates (to the RS API 1.0->1.1) | 21:24 |
| eday | we had 24 outstanding branches this morning, that's way too many | 21:24 |
| eday | so, if you have a branch in there, bug people to review it for you :) | 21:24 |
| alekibango | i am just working on 25th | 21:24 |
| alekibango | :) | 21:24 |
| johnpur | if we are to get this into Bexar (with an appropriate namespace) we will need to jump on this when ready | 21:24 |
| ttx | johnpur: I'm not exactly sure which spec supports this | 21:24 |
| johnpur | i will follow-up | 21:25 |
| ttx | johnpur: or if it's split between the xs- specs | 21:25 |
| johnpur | we need to have a clean had-off from RAX, and then all innovation in the API will be on the OpenStack side | 21:26 |
| alekibango | will live migration land into bexar? | 21:26 |
| masumotok | now we | 21:26 |
| ttx | johnpur: I've already trouble with the number of specs in the list, I've not started to chase the ones that may be missing from the list, yet | 21:26 |
| johnpur | ttx: i understand | 21:27 |
| masumotok | about live migration, we are struggling to get over individual cla thing. | 21:27 |
| ttx | alekibango: live-migration has a bit of a complex dep on network-service, which I/dendrobates need to clarify | 21:28 |
| masumotok | that's why branch is not updated. | 21:28 |
| johnpur | masumotok: what are you strugling with? | 21:28 |
| masumotok | CLA | 21:28 |
| alekibango | ttx: if some help is needed with that, ask me to help you | 21:28 |
| masumotok | Licence agreement | 21:28 |
| ttx | masumotok: struggling with the process, or the legal content ? | 21:28 |
| masumotok | legal content | 21:29 |
| alekibango | i signed CLA, but i do not see the number anywhere | 21:29 |
| masumotok | you know, in my company, it takes a bit for paper work | 21:29 |
| creiht | I signed the CLA a long time ago, and not sure how to get my number | 21:29 |
| alekibango | btw this cla is not valid in czech republic. it needs to be paper :) | 21:29 |
| ttx | alekibango: the number is at the bottom of the document, in the mail you receive from echosign | 21:29 |
| alekibango | do you want to exchange snailmails? | 21:29 |
| alekibango | :) | 21:29 |
| soren | alekibango: Print it out. :) | 21:29 |
| alekibango | really? | 21:29 |
| ttx | masumotok: anything we can do do ease the process for you ? | 21:30 |
| ttx | s/do do/do to/ | 21:30 |
| masumotok | it's just my company's problem | 21:30 |
| soren | alekibango: If it just needs to be on paper, feel free to print it out. :) | 21:30 |
| ttx | masumotok: ok | 21:30 |
| ttx | masumotok: your live migration spec is marked as depending on the network-service one. Do you really depend on that work ? Or is the code you're working on based on the current Nova code ? | 21:31 |
| masumotok | Now we are checking | 21:31 |
| masumotok | we developed based on rev 439 | 21:32 |
| masumotok | and on that revision, there are no | 21:32 |
| masumotok | dependencies | 21:32 |
| ttx | ok, so that's independant. | 21:32 |
| masumotok | do you recooment | 21:32 |
| masumotok | sorry | 21:32 |
| masumotok | do you recommend some branch that I have to check? | 21:32 |
| alekibango | ttx: i might split my blueprint into 2 easier ones -- one which will be only about CPU - for bexar, and another for later work... would that be good idea? https://blueprints.launchpad.net/nova/+spec/resource-partitioning | 21:32 |
| ttx | masumotok: no. I prefer independent works, easier to merge and not block on others | 21:33 |
| alekibango | ttx: but that can wait after meeting | 21:33 |
| ttx | alekibango: I'll talk to you this week about it | 21:33 |
| alekibango | k | 21:33 |
| *** armando has joined #openstack-meeting | 21:33 | |
| ttx | masumotok: I'll also talk to you soon about this spec, to see if we should target it for bexar. | 21:34 |
| masumotok | ttx:OK | 21:34 |
| ttx | ok, let's wrap up, any last minute question ? | 21:34 |
| ttx | Next meeting, next week, same time same batcave. | 21:34 |
| ttx | When does the US decide it's no longer summer ? | 21:35 |
| eday | ttx as far as DST, or season change? | 21:36 |
| dragondm | you mean dst end? | 21:36 |
| ttx | dst end -- already done ? | 21:36 |
| dragondm | dst ended late november | 21:36 |
| eday | yeah, coule weeks ago | 21:36 |
| eday | couple | 21:36 |
| soren | ttx: dst end is just one week off from Europe. | 21:36 |
| soren | ttx: dst start is 3 or 4 weeks off. | 21:37 |
| eday | you know, ust to be difficult | 21:37 |
| ttx | ah ok, I missed the usual disruption period | 21:37 |
| ttx | #endmeeting | 21:37 |
| openstack | Meeting ended Tue Dec 7 21:37:40 2010 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:37 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-12-07-21.01.html | 21:37 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-12-07-21.01.txt | 21:37 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-12-07-21.01.log.html | 21:37 |
| *** romohr has quit IRC | 21:37 | |
| ttx | Thansk everyone ! | 21:37 |
| alekibango | its imho best to use zulu imperial time | 21:37 |
| alekibango | ttx: also to you. i am glad we have you | 21:38 |
| *** creiht has left #openstack-meeting | 21:38 | |
| *** jk0 has left #openstack-meeting | 21:38 | |
| *** johnpur has left #openstack-meeting | 21:38 | |
| *** Tushar has quit IRC | 21:38 | |
| *** ttx has left #openstack-meeting | 21:38 | |
| *** jbryce has left #openstack-meeting | 21:38 | |
| *** armando has quit IRC | 21:39 | |
| *** dragondm has left #openstack-meeting | 21:39 | |
| *** annegentle has left #openstack-meeting | 21:40 | |
| *** dubs has left #openstack-meeting | 21:43 | |
| *** jaypipes has joined #openstack-meeting | 21:56 | |
| *** jaypipes has left #openstack-meeting | 21:57 | |
| *** pino201 has quit IRC | 22:08 | |
| *** ewanmellor has quit IRC | 22:13 | |
| *** mattt has left #openstack-meeting | 22:34 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!