| *** reed has joined #openstack-meeting | 00:03 | |
| *** dragondm has quit IRC | 00:26 | |
| *** vladimir3p has quit IRC | 00:37 | |
| *** ohnoimdead has quit IRC | 00:43 | |
| *** reed has quit IRC | 01:00 | |
| *** adjohn has quit IRC | 01:50 | |
| *** reed has joined #openstack-meeting | 03:01 | |
| *** novas0x2a|laptop has quit IRC | 03:07 | |
| *** novas0x2a|laptop has joined #openstack-meeting | 03:07 | |
| *** jakedahn has quit IRC | 04:07 | |
| *** jakedahn has joined #openstack-meeting | 04:34 | |
| *** zul has quit IRC | 04:36 | |
| *** adjohn has joined #openstack-meeting | 04:37 | |
| *** zul has joined #openstack-meeting | 04:40 | |
| *** jakedahn has quit IRC | 04:43 | |
| *** jdag has quit IRC | 05:15 | |
| *** novas0x2a|laptop has quit IRC | 05:27 | |
| *** novas0x2a|laptop has joined #openstack-meeting | 05:40 | |
| *** adjohn has quit IRC | 06:25 | |
| *** novas0x2a|laptop has quit IRC | 06:50 | |
| *** shang has quit IRC | 07:00 | |
| *** shang has joined #openstack-meeting | 07:04 | |
| *** martines has quit IRC | 07:06 | |
| *** martines has joined #openstack-meeting | 07:09 | |
| *** mancdaz has joined #openstack-meeting | 07:29 | |
| *** adjohn has joined #openstack-meeting | 07:33 | |
| *** jakedahn has joined #openstack-meeting | 07:36 | |
| *** adjohn has quit IRC | 08:44 | |
| *** darraghb has joined #openstack-meeting | 08:50 | |
| *** shang has quit IRC | 10:27 | |
| *** shang has joined #openstack-meeting | 10:48 | |
| *** Binbin has joined #openstack-meeting | 10:57 | |
| *** shang has quit IRC | 11:09 | |
| *** darraghb has quit IRC | 11:14 | |
| *** shang has joined #openstack-meeting | 11:19 | |
| *** darraghb has joined #openstack-meeting | 11:22 | |
| *** zul has quit IRC | 11:36 | |
| *** zul has joined #openstack-meeting | 11:36 | |
| *** Binbin has quit IRC | 11:48 | |
| *** Binbin has joined #openstack-meeting | 11:48 | |
| *** joesavak has joined #openstack-meeting | 13:56 | |
| *** zul has joined #openstack-meeting | 13:57 | |
| *** martine has joined #openstack-meeting | 14:07 | |
| *** martine has quit IRC | 14:11 | |
| *** jdag has joined #openstack-meeting | 14:12 | |
| *** jsavak has joined #openstack-meeting | 14:14 | |
| *** joesavak has quit IRC | 14:16 | |
| *** mattray has joined #openstack-meeting | 14:29 | |
| *** mattray has quit IRC | 14:30 | |
| *** mattray has joined #openstack-meeting | 14:30 | |
| *** rnirmal has joined #openstack-meeting | 14:31 | |
| *** adjohn has joined #openstack-meeting | 14:57 | |
| *** dragondm has joined #openstack-meeting | 14:59 | |
| *** joesavak has joined #openstack-meeting | 15:04 | |
| *** jsavak has quit IRC | 15:04 | |
| *** vladimir3p has joined #openstack-meeting | 15:14 | |
| *** mdomsch has joined #openstack-meeting | 15:31 | |
| *** jsavak has joined #openstack-meeting | 15:32 | |
| *** joesavak has quit IRC | 15:33 | |
| *** dendro-afk is now known as dendrobates | 15:39 | |
| *** mattray has quit IRC | 15:41 | |
| *** Gordonz has joined #openstack-meeting | 15:43 | |
| *** HowardRoark has joined #openstack-meeting | 16:03 | |
| *** HowardRoark has quit IRC | 16:05 | |
| *** rnirmal has quit IRC | 16:19 | |
| *** jsavak has quit IRC | 16:21 | |
| *** jsavak has joined #openstack-meeting | 16:21 | |
| *** heckj has joined #openstack-meeting | 16:26 | |
| *** heckj has quit IRC | 16:29 | |
| *** heckj has joined #openstack-meeting | 16:29 | |
| *** blakeyeager has joined #openstack-meeting | 16:30 | |
| *** heckj has quit IRC | 16:32 | |
| *** heckj has joined #openstack-meeting | 16:32 | |
| *** ohnoimdead has joined #openstack-meeting | 16:59 | |
| *** zul has quit IRC | 17:01 | |
| *** zul has joined #openstack-meeting | 17:01 | |
| *** zul has quit IRC | 17:11 | |
| *** zul has joined #openstack-meeting | 17:13 | |
| *** dragondm has quit IRC | 17:22 | |
| *** adjohn has quit IRC | 17:23 | |
| *** darraghb has quit IRC | 17:45 | |
| *** mattray has joined #openstack-meeting | 18:01 | |
| *** novas0x2a|laptop has joined #openstack-meeting | 18:05 | |
| *** martine has joined #openstack-meeting | 18:09 | |
| *** dragondm has joined #openstack-meeting | 18:28 | |
| *** jk0 has joined #openstack-meeting | 19:02 | |
| *** jakedahn has quit IRC | 19:08 | |
| *** mrmartin has joined #openstack-meeting | 19:09 | |
| *** johnpur has joined #openstack-meeting | 19:11 | |
| carlp | o/ | 19:13 |
|---|---|---|
| carlp | Are we not meeting today? | 19:13 |
| jeblair | i think our chair may have been pulled away from the keyboard... | 19:16 |
| jeblair | it's looking like "no" to me... | 19:17 |
| jeblair | considering all the action items were assigned to him, i'm not sure a formal meeting would be useful. | 19:18 |
| jeblair | informally: nova moved to git, and i'm working on some hardware for integration testing (expanding and cleaning up what we're doing with the openstack-deploy-rax and openstack-integration-rax jenkins jobs) | 19:20 |
| *** mrmartin has quit IRC | 19:34 | |
| carlp | thanks for the info! | 19:38 |
| *** mattray has quit IRC | 19:44 | |
| *** nati has joined #openstack-meeting | 19:50 | |
| *** mdomsch has quit IRC | 19:53 | |
| *** markvoelker has joined #openstack-meeting | 19:56 | |
| *** ewanmellor has joined #openstack-meeting | 19:57 | |
| jaypipes | o/ | 20:00 |
| jaypipes | oh wait, we're skipping PPB today. | 20:01 |
| johnpur | skipping? | 20:01 |
| notmyname | yes, be we can argue about something, if you want ;-) | 20:01 |
| johnpur | ah, must have missed the email | 20:01 |
| jaypipes | notmyname: no brazil for you. one year! | 20:01 |
| notmyname | :-( | 20:02 |
| *** joesavak has joined #openstack-meeting | 20:02 | |
| jk0 | I wasn't sure if we were skipping the entire meeting or just that one discussion | 20:02 |
| jaypipes | notmyname: :) just kiddin | 20:02 |
| jaypipes | jk0: skipping the whole meeting I think | 20:02 |
| johnpur | are we meeting f2f next week? | 20:02 |
| ewanmellor | jk0: jbryce's email looks like we're skipping the whole meeting. | 20:02 |
| notmyname | is there other stuff that should be discussed unofficially? | 20:02 |
| jk0 | ahah | 20:02 |
| ewanmellor | johnpur: Definitely! Beers are on jbryce. | 20:03 |
| *** jorgew has joined #openstack-meeting | 20:03 | |
| pvo | o/ | 20:03 |
| notmyname | heh, we've almost got a quorum anyway | 20:03 |
| jaypipes | ewanmellor: ++ | 20:03 |
| *** zul has quit IRC | 20:04 | |
| *** AndroUser has joined #openstack-meeting | 20:05 | |
| *** jsavak has quit IRC | 20:05 | |
| mtaylor | o/ | 20:05 |
| johnpur | mtaylor: we have been waiting for you! | 20:06 |
| mtaylor | oh- I have now read the scrollback | 20:06 |
| mtaylor | johnpur: I'll bet you have! | 20:06 |
| jeblair | now you can have an official vote not to have a meeting. :) | 20:06 |
| *** joesavak has quit IRC | 20:06 | |
| *** zns has joined #openstack-meeting | 20:07 | |
| vishy | does anyone have any opinions about point releases? | 20:07 |
| vishy | we're going to discuss at the summit | 20:07 |
| vishy | but it is on my mind lately | 20:07 |
| notmyname | vishy: what specifically | 20:07 |
| notmyname | it's soemthing that matters to me cause swift is "different" | 20:08 |
| zns | Just joined. Sorry for being late. | 20:08 |
| notmyname | 8 here, I guess we can have the meeting if we want | 20:08 |
| *** Binbin has quit IRC | 20:09 | |
| *** Binbin has joined #openstack-meeting | 20:09 | |
| vishy | notmyname: well we have never had one | 20:10 |
| vishy | notmyname: and I think we should | 20:10 |
| johnpur | vishy: are you thinking that we will update diablo? | 20:10 |
| notmyname | vishy: we == openstack or we == nova? | 20:10 |
| vishy | we == nva | 20:11 |
| vishy | johnpur: i hope we can | 20:11 |
| vishy | johnpur: cuz it is pretty broke | 20:11 |
| ttx | vishy: actually we had one | 20:11 |
| vishy | ttx: did we? | 20:11 |
| *** nati has quit IRC | 20:11 | |
| ttx | when translations were missing from the original tarball | 20:11 |
| ttx | 2011.1.1 | 20:12 |
| johnpur | vishy: thinking about bringing in keystone & dash at some point on a diablo release? or just in general? | 20:12 |
| notmyname | does a project's updates mean a new openstack version is cut? | 20:13 |
| ttx | (for Bexar) | 20:13 |
| johnpur | ttx: a blast from the past! | 20:13 |
| pvo | weren't we talking about a diablo+ which included keystone? | 20:13 |
| ewanmellor | I'd definitely like a Diablo+1 with Keystone all working. | 20:13 |
| vishy | ttx: ah yeah forgot about that | 20:13 |
| *** AndroUser has quit IRC | 20:13 | |
| ttx | I think we should discuss that next week. Point releases have a cost, especially in a "common release" setting | 20:14 |
| vishy | i think that was just a keystone release, not an openstack release pvo | 20:14 |
| ttx | pvo: keystone won't be included before Essex | 20:14 |
| *** joesavak has joined #openstack-meeting | 20:14 | |
| *** jsavak has joined #openstack-meeting | 20:14 | |
| ewanmellor | vishy: Wouldn't we need Nova updates? | 20:14 |
| zns | There was work on nova-client to keep up with Keystone too… I think | 20:14 |
| ewanmellor | vishy: i.e. to revert the change that you made just before the release. | 20:15 |
| ttx | so far we've said it was up to the downstream distributors to track updates to stable releases | 20:15 |
| vishy | ewanmellor: we moved the middlewares into keystone, so theoretically it is just keystone / dash / novaclient updates | 20:15 |
| ttx | we can change that | 20:15 |
| vishy | without touching nova/glance/swift | 20:15 |
| ttx | one way is to make it easier to build updates (maintain a stable branch) | 20:15 |
| ttx | the other is to try to do point releases | 20:15 |
| notmyname | just to offer it for consideration: let each project version/release as necessary and then build openstack releases (major or point) on its own schedule | 20:16 |
| ttx | Personally I prefer that we become stable and release often, rather than enter the maintenance game | 20:16 |
| devcamcar | o/ | 20:16 |
| zns | This highlights a need for Keystone to maintain it's own client code (which klmitch had started working on) so that updates to the keystone interaction would not impact nova-client if it just imported the keystone client library. | 20:16 |
| notmyname | ttx: swift has been stable and releases often and I still get questions about bexar and cactus code in #openstack | 20:16 |
| ttx | notmyname: would you maintain cactus stable branches with all bugfixes from diablo ? | 20:17 |
| ttx | not sure that would make any sense | 20:17 |
| ewanmellor | ttx: I agree -- it's better for OpenStack to be linear and for downstream to maintain stability branches where necessary. However, it would be great to have a thing with a name that we were happy with, and it sounds like people aren't happy with Diablo. | 20:17 |
| ttx | ewanmellor: so that's another issue -- how to avoid releases that suck | 20:18 |
| notmyname | no, I'd prefer to follow more of the chome model of releasing often with stable updates (I think that's what we have been doing) | 20:18 |
| ttx | ewanmellor: and unless people start focusing on the release (before it's released) it won't happen | 20:18 |
| ttx | notmyname: agreed | 20:18 |
| notmyname | ttx: where we == swift | 20:18 |
| ewanmellor | ttx: Yes, but that's two questions: how to avoid releases that suck, and what to do about the water-under-the-bridge that is Diablo. | 20:18 |
| ttx | ewanmellor: the problem with Diablo is that only a handful of people actually cared about the milestone-proposed branch | 20:19 |
| ttx | so in the end it's untested, and our testing framework is not sufficiently strong (yet) as a safety net | 20:20 |
| johnpur | ttx: that sounds like a fundamental issue? | 20:20 |
| ewanmellor | vishy: When you said "cuz it is pretty broke", were you referring to the Keystone issue, or are there other sucky things? | 20:20 |
| ttx | johnpur: lack of people caring for the end result ? Definitely | 20:20 |
| vishy | ttx: on the bright side, we got testers as soon as we announced it | 20:20 |
| ewanmellor | ttx: Yes, and my team is as much a part of that problem right now. I'm working to fix that. | 20:20 |
| vishy | ewanmellor: there are other sucky things | 20:20 |
| johnpur | ttx: was it "worse" this time? | 20:20 |
| ttx | johnpur: we need to move from tactical to strategic contributions. | 20:21 |
| ttx | johnpur: no, but it was not better this time | 20:21 |
| devcamcar | ttx: i was confused greatly by the fact that some projects followed our official milestones, and others (see also: keystone) just ignored them | 20:21 |
| devcamcar | caused a lot of problems for folks | 20:21 |
| vishy | ewanmellor: the keystone one was very annoying but I am more concerned about the db_pool instability | 20:21 |
| ttx | devcamcar: taht's because they are not core projects, so they are not subjected to release management rules | 20:21 |
| pvo | weren't they promoted to core? | 20:21 |
| johnpur | they are now :) | 20:22 |
| pvo | before the release? | 20:22 |
| pvo | I assumed that mean they would release with everything else | 20:22 |
| ttx | pvo: for the essex cycle. It takes a whole cycle to make a successful release | 20:22 |
| vishy | ewanmellor: https://bugs.launchpad.net/nova/+bugs?field.tag=diablo-backport | 20:22 |
| pvo | isn't that what the incubation is for? | 20:22 |
| *** jakedahn has joined #openstack-meeting | 20:22 | |
| ttx | you can't add them one month before release and expect them to be aligned | 20:22 |
| devcamcar | ttx: not according to incubation policies - all incubated projects are to follow official milestones as part of consideration for core | 20:22 |
| notmyname | devcamcar: ttx: but keystone especially was given pseudo-core status because everyone assumes it will be the future | 20:22 |
| pvo | to get integrated properly? | 20:22 |
| vishy | ewanmellor: the first one is really nasty and the others range from bad to troublesome | 20:22 |
| devcamcar | notmyname: i understand, but that's still not a reason for it to follow milestones | 20:22 |
| ttx | devcamcar: yes, following milestones during incubation is a great way to prove you're ready -- but not the only way | 20:22 |
| devcamcar | er, not follow milestones | 20:22 |
| ttx | devcamcar: in Keystone case, they are ready because all projects start to depend on it | 20:23 |
| devcamcar | ttx: we should require incubated projects to follow milestones for consideration to core | 20:23 |
| *** martines has quit IRC | 20:23 | |
| ttx | devcamcar: clearly not because they (don't) follow milestone | 20:23 |
| notmyname | devcamcar: totally agree. I think that incubated projects should, but they were only added as incubated late in the cycle yet the expectation was to treat them as a core piece. I think that's where the disconnect happened | 20:23 |
| devcamcar | its crazy to have a project that all other projects depend on that doesn't follow milestones | 20:24 |
| notmyname | devcamcar: swift also doesn't really follow the nova milestones (yet sometimes they line up) | 20:24 |
| johnpur | ttx, vishy: are we going to discuss/decide on updating Diablo next week? | 20:24 |
| zns | Owning up here, as well; I was mistakenly thinking Diablo was releasing 9/28 so on 9/21 we were scrambling to finish within 24 hours. | 20:24 |
| ttx | devcamcar: it's crazy that all other projects depend on a project that is not ready, period | 20:24 |
| ewanmellor | vishy: Thanks -- very useful. | 20:24 |
| mtaylor | I think we might should look at the incubated/core process, because it seems that the reality is that things aren't lining up with the state process | 20:24 |
| notmyname | ttx: +1 | 20:25 |
| mtaylor | stated | 20:25 |
| ttx | johnpur: yes | 20:25 |
| johnpur | ttx: this is super important for folks that are deploying Diablo | 20:25 |
| devcamcar | ttx: can't really argue with that, though in this case i feel it was not well communicated that keystone wasn't being released with diablo (at least as a preview) | 20:26 |
| ttx | johnpur: yes -- though it's a matter of knowing the scope of intervention for "OpenStack", and where to put our resources | 20:26 |
| devcamcar | i only learned a few days ago that it was being released in between diablo and essex | 20:26 |
| ttx | johnpur: saying it's important won't make it magically happen | 20:26 |
| ttx | devcamcar: from the beginning of the cycle we knew the core projects that would be released in the end | 20:27 |
| johnpur | ttx: i wish that was true... | 20:27 |
| ttx | devcamcar: doesn't prevent synchronized releases though | 20:27 |
| devcamcar | ttx: what was that list in your mind? | 20:27 |
| ttx | devcamcar: the core projects as they stand at the beginning of a cycle, with design summit etc, are the ones that are released in the end | 20:27 |
| ttx | devcamcar: you can't just promote one in the middle of a cycle and pray | 20:28 |
| devcamcar | ttx: yes, we are in agreement there | 20:28 |
| ttx | devcamcar: that's why Dashboard was promoted recently: in order to be core during the whole Essex cycle | 20:28 |
| devcamcar | ttx: yes i am aware | 20:28 |
| johnpur | we need to (in a transparent manner) let the community know what the intention/plan is for updating Diablo... so folks can plan on what "release" to based Diablo deployments on | 20:28 |
| devcamcar | ttx: i think this whole conversation highlights the need for incubated projects to follow official openstack milestones so we don't have this problem again | 20:29 |
| johnpur | maybe the answer is, Diablo is done, look at Essex | 20:29 |
| ttx | johnpur: the current position from PPB (well, from POC) is that maintenance is done by downstream | 20:29 |
| devcamcar | ttx: i feel that keystone could have had a functional preview release, but they weren't considering diablo milestones. we had stuff working and they made breaking changes the week before release. so it was possible, it just wasn't something anyone seemed to care about | 20:29 |
| ttx | johnpur: but we should definitely discuss if that's the right thing to do | 20:29 |
| notmyname | ttx: the "downstream" being...who? | 20:30 |
| ttx | notmyname: distributions, or customized packages | 20:30 |
| ttx | notmyname: basically so far we've said -- rely on distributions, or maintain your own, but openstack only provides snapshots | 20:30 |
| notmyname | ttx: so canonical (for example) would be responsible for packaging newer version of nova/glance/swift/etc for packaging and release? | 20:31 |
| ttx | notmyname: canonical will ship a diablo+ in oneiric | 20:31 |
| notmyname | or piston or nebula or etc | 20:31 |
| ttx | and maintain it | 20:31 |
| vishy | johnpur: i don't like that answer | 20:31 |
| notmyname | vishy: what about a nova-specific release? | 20:31 |
| ttx | the trouble with maintaining a version is that it's csotly, and all distributions happen to do it anyway, under their own maintenance terms | 20:32 |
| ttx | what we can (should) do, is facilitate that | 20:32 |
| ttx | but releasing point releases ? maybe not | 20:32 |
| vishy | notmyname: i'm ok with that | 20:32 |
| zns | This was also the first integration release for Keystone. Future releases will not break the previous version of the API. | 20:33 |
| dendrobates | ttx: should we at least backport patches for some period of time? | 20:33 |
| ttx | dendrobates: we could maintain a branch with bugfixes | 20:33 |
| ttx | dendrobates: that would help everyone | 20:33 |
| vishy | notmyname: but i know that glance for example has one bugfix that was supposed to make the milestone and got missed | 20:33 |
| zns | Would it make sense for projects like Keystone that other projects depend on to freeze ahead of the release freeze (basically, freezing by E4 for Keystone). | 20:33 |
| johnpur | vishy: a nova specific release would have the same assumptions around intergation with other services that a major milestone has? | 20:33 |
| *** martines has joined #openstack-meeting | 20:34 | |
| dendrobates | ttx: if we don't we could end up with different fixes in each distro, which would be a nightmare | 20:34 |
| ttx | dendrobates: but it takes time and resources. Currently people are not even looking at the existing bug list. So I fear resources will be missing | 20:34 |
| notmyname | vishy: do you think having separate versions/releases for the individual projects may help solve these problems? release a new version of one project and, if needed, package it up with the rest again as an openstack point release | 20:34 |
| mtaylor | if we are not maintaining our releases long term, I do not know that I see the benefit in our 6-month releases. if we're expecting that ubuntu will release whatever they decide to release, as will piston and nebula - then why not just adopt a chrome rolling model like notmyname uses for swift? | 20:34 |
| vishy | johnpur: i think it would have to continue to support the other diablos | 20:35 |
| ttx | mtaylor: because Nova breaks things and monthly milestones are even more broken than release ? | 20:35 |
| mtaylor | ttx: that's an implementation detail because we haven't been focused on rolling releases | 20:35 |
| mtaylor | but if we're ignoring releases as soon as we cut them, then what's the point of cutting them? | 20:35 |
| ewanmellor | mtaylor: We're _nowhere_ near having a good enough build on a monthly basis. | 20:35 |
| johnpur | vishy: i am just wondering about the level of qa and integration testing we will get, comparable to the final release milestone? | 20:35 |
| ttx | ewanmellor: +1 | 20:36 |
| mtaylor | ewanmellor: not saying we are - I'm just wondering what the point of he releases is if they don't really mean anything | 20:36 |
| ttx | mtaylor: when we have confidence in CI that stuff in trunk is not broken, then yes | 20:36 |
| ewanmellor | mtaylor: The point is to slow everyone down towards the end of the release, so that we focus on stability and QA. | 20:36 |
| vishy | johnpur: if ttx and I install it on a few machines we will have euqivalent qa and testing :) | 20:36 |
| mtaylor | ewanmellor: sure. but did we do that/did that happen? | 20:36 |
| johnpur | vishy: :) | 20:36 |
| ewanmellor | mtaylor: Sure, we definitely took fewer risks in the last milestone. | 20:37 |
| * vishy is exaggerating (but only a little) | 20:37 | |
| ewanmellor | mtaylor: Obviously not enough for us to get it right, mind you. | 20:37 |
| ttx | anyway, this should really be discussed in a more open forum | 20:37 |
| devcamcar | zns: +1 to freezing keystone by E4. that would help a lot! | 20:37 |
| ttx | devcamcar: yes, I was playing with the idea to freeze keystone early in cycle, since everyone depends on it | 20:38 |
| ewanmellor | ttx: ...or over a beer in a week's time? | 20:38 |
| * mtaylor isn't specifically advocating continuously rolling releases - just saying that a 6 month release cycle carries with it an expectation that some sort of longer-lived support will exist for that release | 20:38 | |
| ttx | ewanmellor: in a session *and* over a beer | 20:38 |
| mtaylor | ttx: what? there will be beer next week? | 20:38 |
| ttx | mtaylor: it just carries the expectation that components will have a longer stabilization time to ensure they work well together | 20:39 |
| ttx | mtaylor: the 6-month cycle was never about long-lived support | 20:39 |
| zns | devcamcar, ttx: I think when we have a new API under a higher version the old one should be unchanged. But if we're releasing an API with features that everyone is integrating to we'll do that. I think, given the experience this time around and the maturity of the process, for Essex we'll freeze by E4. | 20:39 |
| mtaylor | ttx: I disagree. that's what we've said we're doing - but I think when people see a "release" they expect to be able to file bugs against it | 20:39 |
| ttx | it was always about more stability than your random milestone | 20:39 |
| devcamcar | zns: happy to hear that | 20:40 |
| ttx | mtaylor: not seeing any update should cure that expectation fast. | 20:40 |
| mtaylor | ttx: I doubt it- but ok | 20:40 |
| notmyname | mtaylor: agree | 20:41 |
| mtaylor | my point is that people have been consuming software for years, and there are built in cultural assumptions that come with naming and with practices | 20:42 |
| mtaylor | we can try until we're blue in the face to subvert those | 20:42 |
| mtaylor | but we're going to fail | 20:42 |
| devcamcar | mtaylor: i agree - having a LTS style release is a reasonable thing to do | 20:43 |
| mtaylor | what we should do is figure out what it is we're doing, and then use terminology and models to communicate reality in a way that will be perceived appropriately | 20:43 |
| ttx | mtaylor: I hear you -- just saying that a lot of projects out there just say" upgrade to the next version", we are not the only in blue | 20:43 |
| mtaylor | ttx: yes - but most of them don't have a 6-month cycle | 20:43 |
| ttx | mtaylor: that's where distros shine, provide stable release updates | 20:43 |
| mtaylor | ttx: "upgrade to the next version" is much more costly when the next version is 6 months away | 20:43 |
| notmyname | ttx: wait, so are you saying that openstack is a distro? | 20:44 |
| ttx | notmyname: no | 20:44 |
| notmyname | ah. too bad ;-) | 20:44 |
| ttx | heh | 20:44 |
| ttx | on the phone for a bit | 20:45 |
| mtaylor | I think distros do a wonderful job of things - but I also think that OpenStack as a brand and as an idea has a responsibilty to name things such that people understand what they are | 20:45 |
| notmyname | ttx: but yet above you said that we are snapshots of the projects | 20:45 |
| mtaylor | otherwise, we will have Ubuntu OpenStack Diablo and Fedora OpenStack Diablo - and the two will look NOTHING alike | 20:45 |
| mtaylor | so the words OpenStack Diablo will carry absolutely no sigificance than anyone can count on | 20:45 |
| notmyname | mtaylor: not to mention nebula, HP, Dell, piston, etc | 20:46 |
| notmyname | rackspace | 20:46 |
| ttx | mtaylor: they will be different anyway | 20:46 |
| mtaylor | we can't just say "the distros will solve it" , wave our hands in the air and expect magic | 20:46 |
| mtaylor | ttx: they do not HAVE to be completely different code bases | 20:46 |
| *** clayg has joined #openstack-meeting | 20:46 | |
| ttx | mtaylor: they probably won't. | 20:47 |
| devcamcar | notmyname: this is why the idea of FITS is getting a lot of support | 20:47 |
| devcamcar | so that it *does* mean something | 20:47 |
| notmyname | devcamcar: I think FITS is a good thing (tm). I think our current practices for packaging/releasing/versioning have caused some...confusion | 20:48 |
| mtaylor | notmyname: ++ | 20:48 |
| devcamcar | agreed | 20:48 |
| *** joesavak has quit IRC | 20:49 | |
| *** jsavak has quit IRC | 20:49 | |
| *** bcwaldon has joined #openstack-meeting | 20:49 | |
| johnpur | i assume that jmckenty is not here? | 20:50 |
| johnpur | just wondering if any pogress has been made on the fits front | 20:50 |
| johnpur | progress | 20:50 |
| notmyname | johnpur: last week he said his timeline was more on the quarter scale (have soemthing by the end of the year) | 20:51 |
| *** jorgew has quit IRC | 20:52 | |
| devcamcar | johnpur: yea sounds more like a way of certifying for essex rather than diablo | 20:53 |
| pvo | is there any merit to *not* sticking strickly to time based releases if we are more interested in not having things broken? | 20:55 |
| johnpur | devcamcar: looks like it. from the discussion last week we need to iterate on a regular basis on the fits definition. | 20:55 |
| pvo | I mean, stay a close as we can, but it seems we release because its release day, not because everything is working the way we want. | 20:56 |
| notmyname | pvo: watch out. there be dragons there | 20:56 |
| pvo | I don't feel a day or week slip to fix what is truly broken isn't the end of the world. | 20:56 |
| pvo | notmyname: just being pragmatic. | 20:56 |
| johnpur | pvo: channeling ttx, isn't that the definition of time based releases? we just need to get better at making sure the content is stable, tested, and work correctly on release day :) | 20:57 |
| pvo | no one is going to care that we slipped a week 2 years from now to make sure we didn't ship with a useless release. | 20:57 |
| notmyname | pvo: I'm with you. this is what swift argued for many months ago :-) | 20:57 |
| ewanmellor | pvo: We'd have slipped, wouldn't we, if it was a question of day or a week? The problem with Keystone is that people said 6 weeks. | 20:57 |
| johnpur | pvo: love the quote, have used it many time myself! | 20:57 |
| *** jrouault has joined #openstack-meeting | 20:57 | |
| ttx | pvo: how would 2 more weeks help ? | 20:58 |
| pvo | johnpur: we haven't had a really useful release with time based, have we? | 20:58 |
| *** Vek has joined #openstack-meeting | 20:58 | |
| ttx | pvo: only a handful of people worked on stabilizing. | 20:58 |
| devcamcar | ewanmellor: true. I think we will have a working preview in a week though for dhboard plus keystone | 20:58 |
| ewanmellor | Having time-based releases is very useful to me, because I have my own release to get out the door, but by time-based I mean +/- a week is no problem at all. | 20:58 |
| ttx | and that hand was missing quite a lot fingers | 20:58 |
| pvo | ewanmellor: ++ | 20:58 |
| notmyname | ttx: it's the job of every dev to ensure stability. not some group at the end of a cycle | 20:59 |
| ttx | notmyname: indeed | 20:59 |
| devcamcar | ewanmellor: +1 | 20:59 |
| ttx | notmyname: but not happening in Nova | 20:59 |
| *** markmc has joined #openstack-meeting | 20:59 | |
| ttx | notmyname: I know only 3 people that actually tested milestone-proposed. Me included | 20:59 |
| johnpur | i think that some of the big deployers should/will step up to the bar going forward to ensure that more effort is applied to qa/stabilization/functional testing | 20:59 |
| pvo | notmyname: I don't disagree but with every dev team running off babysitting their own patches, it usually ends up being only a few testing *everything* | 20:59 |
| notmyname | ttx: so we can't try to promote the idea that "not enough people worked on stability" at the end of the cycle | 20:59 |
| johnpur | bt also agree that it is a community effort | 21:00 |
| devcamcar | enter the ci project | 21:00 |
| *** pem has joined #openstack-meeting | 21:00 | |
| ttx | pvo: I would have delayed the release one+ week if I thought it would have changed something. | 21:00 |
| pvo | devcamcar: yes | 21:00 |
| *** rafadurancastane has joined #openstack-meeting | 21:00 | |
| pvo | ttx: ok. Fair enough. | 21:00 |
| *** zns has quit IRC | 21:00 | |
| *** pem is now known as Guest21732 | 21:00 | |
| ttx | anyway, it's meeting time | 21:00 |
| jaypipes | o/ | 21:01 |
| ttx | \o | 21:01 |
| *** somik has joined #openstack-meeting | 21:01 | |
| ttx | vishy: still around ? | 21:01 |
| vishy | o/ | 21:01 |
| ttx | devcamcar, zns: ? | 21:01 |
| devcamcar | may lose me for 5 while I get food :) | 21:02 |
| ttx | (sorry if I appear to be ranting, it's post-release depression) | 21:02 |
| vishy | ttx: understandable. I've been ranting a lot as well. It is a good thing I don't have a GF or I'd probably be in a lot of trouble | 21:02 |
| devcamcar | o/ | 21:02 |
| devcamcar | I'll just get food on my devices | 21:03 |
| ttx | ok, hopefully zns will catch up | 21:03 |
| ttx | #startmeeting | 21:03 |
| openstack | Meeting started Tue Sep 27 21:03:19 2011 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:03 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 21:03 |
| ttx | Welcome to our weekly team meeting... Today's agenda is at: | 21:03 |
| ttx | #link http://wiki.openstack.org/Meetings/TeamMeeting | 21:03 |
| ttx | #topic Actions from previous meeting | 21:03 |
| *** openstack changes topic to "Actions from previous meeting" | 21:03 | |
| *** troytoman-away is now known as troytoman | 21:03 | |
| ttx | * ttx to push his session propose rant to the ML: DONE | 21:03 |
| ttx | #topic 2011.3 release postmortem | 21:04 |
| *** openstack changes topic to "2011.3 release postmortem" | 21:04 | |
| ttx | so we started that earlier... | 21:04 |
| ttx | Last Thursday we released OpenStack 2011.3. | 21:04 |
| ttx | While the memory is still present, anything we need to do differently next time ? | 21:04 |
| pvo | ttx: fwiw, we're getting some dedicated QA folks to work embedded with us. | 21:05 |
| notmyname | ttx: beyond the big picture issues of releases and versioning, the diablo swift release went well | 21:05 |
| ttx | personally, like I just mentioned, I think we've not been focused enough on the milestone-proposed branch over the last month | 21:05 |
| *** novas0x2a|laptop has quit IRC | 21:05 | |
| *** danwent has joined #openstack-meeting | 21:05 | |
| ttx | resulting in a few high-profile bugs in the release on Nova/Glance side | 21:05 |
| pvo | ttx: I agree with you, though we're running pretty close to trunk for our Alpha and fixing a lot of issues that arise. | 21:05 |
| jaypipes | ttx: ++ | 21:05 |
| ttx | I'm not sure adding more time would have changed anything though, except increase Vish and Jay pain | 21:05 |
| ttx | We need a mindset change -- developers caring more about the project deliverables | 21:06 |
| pvo | ttx: I 100% agree with you there. | 21:06 |
| jaypipes | instead of cramming in features at the last minute? | 21:06 |
| *** mattray has joined #openstack-meeting | 21:06 | |
| vishy | ttx: real deployment tests | 21:06 |
| vishy | ttx: we found out about major bugs as soon as people actually tried it out | 21:06 |
| ttx | jaypipes: the release cycle should ensure that -- do you think we (I) was a bit light on that front ? | 21:06 |
| annegentle | I think that expectations around an incubated project were difficult when reality hit. | 21:07 |
| jaypipes | vishy: right, which is why integration tests are so important to gate trunk... | 21:07 |
| ttx | (Note: Adaptations to the cycle will be discussed during the "Essex release cycle" session at the summit) | 21:07 |
| jaypipes | annegentle: yup | 21:07 |
| vishy | ttx: i thought the main issue is all of the teams were getting pulled away focusing on their own deliverables | 21:07 |
| ttx | vishy: not sure how we can address that though | 21:08 |
| annegentle | I don't think testing is all of it though, having an ops mindset would help as well, for docs especially. | 21:08 |
| *** mcohen has joined #openstack-meeting | 21:08 | |
| jaypipes | vishy: well, that is because those "own deliverables" don't take into account a real baking/QA process for weeks before the release. feature work just continues at a feverish pace instead of testing and bug fixing focus | 21:08 |
| pvo | vishy: I think thats true for most teams | 21:08 |
| ttx | vishy: well, I have a few ideas, you heard them last week :) | 21:08 |
| notmyname | automated tests are not QA | 21:08 |
| jaypipes | notmyname: they are better than nothing. | 21:09 |
| *** liemmn has joined #openstack-meeting | 21:09 | |
| ttx | notmyname: could you enlighten us on the mysterious QA that Swift undergoes inside RAX ? | 21:09 |
| ttx | notmyname: seems to be working wekk | 21:09 |
| ttx | well | 21:09 |
| notmyname | jaypipes: yes, but they don't replace QA | 21:09 |
| jaypipes | notmyname: and if we could write a functional/integration test suite based on the *specs*, that would be rocking. Unfortunately, the specs being driven by the implementation means that this is nigh impossible. | 21:10 |
| notmyname | ttx: we have 2 dedicated QA testers who do end-to-end testing at scale across all deployments | 21:10 |
| jaypipes | notmyname: that's awesome, but not all teams have those resources. | 21:10 |
| jaypipes | notmyname: and are you referring to just cloud files? | 21:10 |
| jaypipes | notmyname: because I am referring to the whole kit and caboodle :) | 21:10 |
| ttx | ok, we won't resolve all here and now, but think about what we need to change and come with your ideas at the design summit | 21:11 |
| *** edconzel has joined #openstack-meeting | 21:11 | |
| ttx | because we need to improve | 21:11 |
| jaypipes | I'm not trying to be argumentative, just stating some obvious things... | 21:12 |
| ttx | jaypipes: I completely agree with you, in the end it's a question of project-centered resources | 21:12 |
| ttx | jaypipes: but you know that already :) | 21:12 |
| *** edconzel_ has joined #openstack-meeting | 21:12 | |
| jaypipes | indeed | 21:12 |
| ttx | Which brings us to the next subject, unless someone has anything more definitive to add | 21:13 |
| ttx | #topic Design Summit | 21:13 |
| *** openstack changes topic to "Design Summit" | 21:13 | |
| ttx | If you are a registered attendee, you still have until the end of today to submit your session proposals | 21:13 |
| ttx | We already have enough, so only submit one if a critical subject is missing :) | 21:14 |
| ttx | Any question on session proposing ? | 21:14 |
| carlp | Do we know when that list will be finalized and scheduled? | 21:14 |
| ttx | carlp: well, first step is to get them all, so that we know how many we have to refuse | 21:15 |
| carlp | ttx: hehe fair enough :) | 21:15 |
| ttx | I hope we can get a final list of sessions by Thursday, and the schedule will be work in progress until the start of the summit | 21:15 |
| ttx | we'll do a quick overview of tracks during this meeting | 21:16 |
| ttx | The "OpenStack Core" track is already full with interesting talks | 21:16 |
| ttx | Lots of proposals in the "Other" track as well | 21:16 |
| ttx | It looks like we'll have to move a few of the proposals from there to the Unconference | 21:17 |
| ttx | Any question on the summit, before we move to Swift ? | 21:17 |
| *** zns has joined #openstack-meeting | 21:18 | |
| ttx | #topic Swift status | 21:18 |
| *** openstack changes topic to "Swift status" | 21:18 | |
| ttx | notmyname: o/ | 21:18 |
| notmyname | howdy | 21:18 |
| ttx | Is the Swift track for the summit coming together ? | 21:19 |
| notmyname | yes. all of the submitted sessions have been reviewed | 21:19 |
| notmyname | I think some the discovery sessions (currently on hold) are as important as the others | 21:19 |
| notmyname | really hope they can get in | 21:19 |
| ttx | notmyname: any chance you could tell me which ones are the most important ? | 21:19 |
| ttx | notmyname: note that the others can be scheduled in the unconference anyway | 21:20 |
| notmyname | ya, I can follow up with a priority list | 21:20 |
| ttx | cool, thx | 21:20 |
| notmyname | looks like a lot of good stuff covered, though | 21:20 |
| ttx | Anything else ? | 21:20 |
| notmyname | not from me | 21:20 |
| notmyname | any questions? | 21:21 |
| ttx | notmyname: when we have a near-final list of sessions, I'll ask you (and the other PTLs) for a list of sessions you need to attend, so that I try to build the schedule in a way that allows you to attend them all | 21:21 |
| jaypipes | notmyname: yes, were you referring to just Cloud Files above? | 21:21 |
| notmyname | jaypipes: with QA? | 21:21 |
| jaypipes | notmyname: yes. | 21:22 |
| *** johnpur has quit IRC | 21:22 | |
| *** mcohen has quit IRC | 21:22 | |
| jaypipes | "we have 2 dedicated QA testers who do end-to-end testing at scale across all deployments" | 21:22 |
| notmyname | jaypipes: yes. we have 2 QA people for cloud files. cloud files == swift, for all intents and purposes | 21:22 |
| *** mcohen has joined #openstack-meeting | 21:22 | |
| jaypipes | notmyname: OK. Thank you. | 21:22 |
| ttx | #topic Glance status | 21:23 |
| jaypipes | notmyname: I was trying to determine whether you were referring to QA folks who were testing an OpenStack deployment | 21:23 |
| *** openstack changes topic to "Glance status" | 21:23 | |
| ttx | Any high-profile bug in Glance 2011.3 ? | 21:23 |
| notmyname | jaypipes: yes. a swift deployment is an openstack deployment, is it not? | 21:23 |
| jaypipes | ttx: had one major bug that didn't make it into diablo final (my mistake... just missed it in milestone-proposed) | 21:23 |
| jaypipes | notmyname: I was referring to OpenStack - the entire project. | 21:23 |
| jaypipes | notmyname: but I see your point. | 21:24 |
| ttx | We should at the very least mention it in the release notes, with links to patches/commits, if not done already | 21:24 |
| jaypipes | ttx: yes, doing so. | 21:24 |
| ttx | #link http://wiki.openstack.org/ReleaseNotes/Diablo | 21:24 |
| ttx | ...so that downstream can fix it in their packaging. | 21:24 |
| jaypipes | ttx: there is the broader discussion needed about a maintenance branch | 21:24 |
| jaypipes | ttx: yes, already working with smoser on it. will edit the release notes. | 21:24 |
| ttx | jaypipes: Daviey is filing one | 21:24 |
| jaypipes | ttx: all glance track sessions are reviewed. | 21:25 |
| ttx | (session on maintenance branch) | 21:25 |
| jaypipes | ttx: k | 21:25 |
| ttx | Is the Glance track starting to look cool ? | 21:25 |
| jaypipes | ttx: as cool as talking about an image service will be. | 21:25 |
| jaypipes | ttx: I'm excited more about some OpenStack Core sessions ;) | 21:25 |
| ttx | a "cloud" image service ! | 21:25 |
| ttx | Other questions on Glance ? | 21:26 |
| * jaypipes very excited about the new Ceph/RADOS driver contributed today... an alternate high-available/distributed storage driver | 21:26 | |
| *** martine has quit IRC | 21:27 | |
| ttx | #topic Nova status | 21:27 |
| *** openstack changes topic to "Nova status" | 21:27 | |
| ttx | vishy: o/ | 21:27 |
| *** novas0x2a|laptop has joined #openstack-meeting | 21:27 | |
| vishy | heyo | 21:27 |
| ttx | So, a few days later, is Earth still standing ? | 21:27 |
| vishy | well as I've mentioned a few times there were a few nasty bugs that made it in | 21:28 |
| vishy | https://bugs.launchpad.net/nova/+bugs?field.tag=diablo-backport | 21:28 |
| Vek | (technically, Earth doesn't "stand"...) | 21:28 |
| vishy | source security groups are broken, block migration is broken | 21:28 |
| ttx | vishy: are they documented in release notes ? | 21:28 |
| vishy | and the two pretty nasty ones are 1) in some cases flatdhcp will remove your default gateway | 21:28 |
| vishy | 2) the db-pool will blow up on any allocations that use lockmode concurrently | 21:29 |
| vishy | ttx: no they are not | 21:29 |
| *** bcwaldon has quit IRC | 21:30 | |
| ttx | vishy: would be good to have them, so that other downstreams know what to apply. I know canonical is on top of the issues, but others might be interested in pointers | 21:30 |
| ttx | at least until we can have that discussion on stable branches | 21:30 |
| markmc | ttx, Fedora is using vishy's diablo-backport tag to know what to cherry-pick too | 21:31 |
| *** adjohn has joined #openstack-meeting | 21:31 | |
| ttx | markmc: good. | 21:31 |
| Daviey | o/ | 21:31 |
| vishy | i will add them to the release notes | 21:31 |
| Daviey | markmc: Interesting! | 21:31 |
| markmc | Daviey, will cherry-pick into https://github.com/markmc/nova/tree/fedora-patches | 21:32 |
| Daviey | markmc: I want, no need, you at http://summit.openstack.org/sessions/view/106 | 21:32 |
| markmc | Daviey, will be there :) | 21:32 |
| ttx | vishy: The Nova track(s) are still very much work in progress... | 21:32 |
| Daviey | currently we are carrying flat, cherrry picked patches in Ubuntu packages. | 21:33 |
| Daviey | This is bad team play. | 21:33 |
| ttx | vishy: did you find time to submit any session you feel is missing from them ? | 21:33 |
| vishy | yes, I've been doing some reviewing | 21:33 |
| vishy | i just submitted two | 21:33 |
| * ttx looks at his pretty graph going through the roof | 21:33 | |
| *** troytoman is now known as troytoman-away | 21:34 | |
| ttx | vishy: anything else on your mind ? | 21:34 |
| Daviey | That is a very open ended question. | 21:35 |
| vishy | nope | 21:35 |
| ttx | vishy, jaypipes: we haven't any "discovery" session in Glance and Nova | 21:35 |
| ttx | I think they offer a great opportunity to recruit for specific areas of code | 21:36 |
| ttx | should we ask for a bit more ? | 21:36 |
| vishy | ttx: I should do one on networking | 21:37 |
| ttx | vishy: I was wondering if we should have a 101 to cover i18n, logging, command execution... | 21:37 |
| Daviey | vishy: a session on all nova-* components sounds useful IMO. | 21:38 |
| Daviey | For example, i imagine people would like to be more involved in scheduling algorithms | 21:38 |
| vishy | Daviey: sandywalsh should do another one on scheduling | 21:39 |
| *** troytoman-away is now known as troytoman | 21:39 | |
| vishy | that was great last time | 21:39 |
| Daviey | nova-api enrichment? | 21:39 |
| ttx | ok, we'll work on that for the remaining of the week | 21:39 |
| ttx | Other questions on Nova ? | 21:40 |
| ttx | #topic Keystone status | 21:40 |
| *** openstack changes topic to "Keystone status" | 21:40 | |
| ttx | zns: o/ | 21:41 |
| ttx | So it looks like we still need a Diablo-compatible release of Keystone, any ETA on that ? | 21:41 |
| ttx | hmm, looks like we've lost zns | 21:43 |
| ttx | devcamcar: around ? Maybe we can do you first | 21:43 |
| devcamcar | o/ | 21:43 |
| ttx | #topic "Dashboard" status | 21:43 |
| *** openstack changes topic to ""Dashboard" status" | 21:43 | |
| ttx | devcamcar: There aren't so many sessions around Dashboard proposed. | 21:43 |
| ttx | Maybe you should split "Dashboard Diablo review and Essex roadmap" into something more... descriptive ? | 21:44 |
| devcamcar | ttx: i'd be happy to split diablo review and essex planning up, certainly could use the time | 21:44 |
| devcamcar | our general update is that we're trying to land a version compatible with diablo and the latest changes to keystone | 21:44 |
| ttx | devcamcar: we don't really do retrospectives at the summit | 21:44 |
| devcamcar | ttx: fair enough, i can split up into a few smaller more descriptive chunks | 21:45 |
| heckj | (maybe we should) | 21:45 |
| devcamcar | we only have a few outstanding issues with keystone | 21:45 |
| devcamcar | i am hopeful we can land a "preview" version compatible with diablo whenever keystone is ready for us to | 21:46 |
| devcamcar | we are ready now | 21:46 |
| ttx | heckj: I think I didn't express myself correctly. I mean, we are not doing a full session to look at the features we just added -- the idea is to look forward | 21:46 |
| ttx | heckj: doesn't prevent learning from mistakes :) | 21:46 |
| * Daviey remembers to take rotten fruit with him to throw at people for retrospective/post-mortem sessions. | 21:46 | |
| devcamcar | ttx: i have lots of idea to split up into smaller sessions, i will take your advice and do that | 21:46 |
| *** zul has joined #openstack-meeting | 21:46 | |
| ttx | devcamcar: that allows people to know what they are going to see | 21:47 |
| devcamcar | i do want to say thanks to the folks at rackspace who have helped us with keystone migrations during diablo cycle | 21:47 |
| devcamcar | and that is my update | 21:47 |
| ttx | Questions on "Dashboard" ? | 21:47 |
| Daviey | Is Diablo dashboard released now? | 21:48 |
| ttx | devcamcar: do you need 25min for your naming ceremony ? I thought it could be done as a lightning talk on the first day | 21:48 |
| *** mcohen_ has joined #openstack-meeting | 21:48 | |
| ttx | i.e. put names on wall, let people yell for a bit, then choose. | 21:48 |
| devcamcar | ttx: lightning talk is good with me | 21:48 |
| ttx | ok, will decline that one then | 21:48 |
| Daviey | devcamcar: ^^ | 21:49 |
| devcamcar | Daviey: we will drop code as soon as keystone is ready | 21:49 |
| devcamcar | Daviey: hopefully in the next week | 21:49 |
| Daviey | devcamcar: ok, thanks. | 21:50 |
| ttx | zns: around ? | 21:50 |
| ttx | anyone from keystone ? | 21:50 |
| ttx | danwent: around ? | 21:50 |
| danwent | yup | 21:50 |
| ttx | #topic Incubated project news | 21:50 |
| *** openstack changes topic to "Incubated project news" | 21:50 | |
| *** mcohen has quit IRC | 21:51 | |
| *** mcohen_ is now known as mcohen | 21:51 | |
| danwent | Quantum diablo was released on friday | 21:51 |
| danwent | now includes a v1.0 spec and a draft administrator guide | 21:51 |
| * annegentle cheers | 21:51 | |
| ttx | Congrats on that | 21:51 |
| danwent | appropriate for "early adopters" :) | 21:51 |
| danwent | thanks. | 21:51 |
| danwent | Please check out the NetStack track for the Essex summit, lots of great things to talk about in Boston | 21:51 |
| annegentle | danwent: so can I just point a Jenkins job to your source repo to build the docs? | 21:52 |
| danwent | in particular, several people have contacted us about how to integrate higher level network services | 21:52 |
| danwent | so we will have a session or two on that. if you build things that plug into networks, please drop by. | 21:52 |
| danwent | annegentle: sorry, still need to reply to your mail. yes, we'll get the docbook sources into repos so we can build them automatically | 21:53 |
| danwent | that's all from me | 21:53 |
| annegentle | danwent: great, thanks | 21:53 |
| ttx | danwent: are you going to edit the sessions based on Ram's feedback ? | 21:53 |
| ttx | danwent: I still need a prioritized list, btw | 21:53 |
| danwent | ttx: ram already edited some himself, I will edit others based on feedback from the team | 21:54 |
| ttx | so that I can start accepting the most important ones | 21:54 |
| danwent | I was waiting to see if anyone was planning on proposing anythign else, will know this by the end of the netstack meeting today :) | 21:54 |
| danwent | hopefully everything is in already | 21:54 |
| ttx | Anything else ? | 21:55 |
| bmcconne | just wanted to say I've been running quantum for a few weeks now and it's been quite stable for me. working well :) | 21:55 |
| danwent | bmcconne: great to hear :) | 21:55 |
| danwent | ttx: that's all | 21:55 |
| ttx | zns / anyone from the Keystone crew ? | 21:56 |
| ttx | I guess we won't have them today | 21:57 |
| *** shwetaap has joined #openstack-meeting | 21:57 | |
| ttx | fwiw I'm working with Joe Savak on finalizing the Keystone track at the summit | 21:57 |
| annegentle | ttx: I just asked yogirackspace to join | 21:57 |
| *** yogirackspace has joined #openstack-meeting | 21:57 | |
| ttx | yogirackspace: welcome ! | 21:57 |
| yogirackspace | thanks! | 21:57 |
| ttx | #topic Keystone status | 21:57 |
| *** openstack changes topic to "Keystone status" | 21:57 | |
| ttx | yogirackspace: Any news on ETA for a Diablo-compatible release of Keystone ? | 21:58 |
| yogirackspace | all the calls that were supposed to work we have completed as of now | 21:58 |
| *** edconzel_ has quit IRC | 21:59 | |
| ttx | do you plan to release / tag something D / 1.0 / 2011.3 ? | 21:59 |
| yogirackspace | we shall be tagging soon | 21:59 |
| devcamcar | yogirackspace: https://bugs.launchpad.net/keystone/+bug/857671 | 21:59 |
| uvirtbot | Launchpad bug 857671 in keystone "Auth protocol doesn't work properly for admin users" [Undecided,New] | 21:59 |
| yogirackspace | would let every one know when it happens | 21:59 |
| devcamcar | this one is needed for dashboard | 21:59 |
| yogirackspace | we are working on pending things and wrapping up | 22:00 |
| yogirackspace | would make sure that all issues are addressed | 22:00 |
| devcamcar | yogirackspace: can you be more specific than "soon"? | 22:00 |
| yogirackspace | need to talk with others as well.Would end of week (max) suit every one? | 22:01 |
| devcamcar | having something i could release for dashboard before the summit sure would be nice | 22:01 |
| devcamcar | but dropping code friday doesn't give us much time | 22:01 |
| devcamcar | but i'll take it | 22:01 |
| yogirackspace | time outlined is worst case | 22:02 |
| ttx | yogirackspace: was saying just before you joined I'm working with Joe Savak on finalizing the Keystone track at the summit | 22:02 |
| yogirackspace | we might veryfy everything and might release tomorrow | 22:02 |
| devcamcar | ok tomorrow then, will hold you to that :) | 22:02 |
| ttx | yogirackspace: anything else on your mind ? | 22:02 |
| yogirackspace | might => a mighty word ;) | 22:02 |
| *** ying has joined #openstack-meeting | 22:03 | |
| yogirackspace | we have started implementing | 22:04 |
| yogirackspace | our extensions | 22:04 |
| yogirackspace | and also finding featyres for Essex | 22:04 |
| *** edconzel_ has joined #openstack-meeting | 22:04 | |
| yogirackspace | would keep every one posted if there is anything else | 22:04 |
| *** edgarmagana has joined #openstack-meeting | 22:04 | |
| edgarmagana | hello world! | 22:05 |
| danwent | edgar: network meeting hasn't started yet | 22:05 |
| ttx | time running up | 22:05 |
| ttx | #topic Open discussion | 22:05 |
| *** openstack changes topic to "Open discussion" | 22:05 | |
| ttx | anything / anyone before we let our networked friends take over ? | 22:06 |
| *** adjohn has quit IRC | 22:06 | |
| annegentle | Thursday morning of the Conference portion of next week I'd like to hold a discussion about how to get more women involved in OpenStack. All welcome! | 22:06 |
| vishy | annegentle: Nice! | 22:06 |
| *** mattray has quit IRC | 22:07 | |
| *** primeministerp2 has joined #openstack-meeting | 22:07 | |
| ttx | annegentle: I promise I didn't reject any woman from the summit waiting list. There just wasn't any. | 22:07 |
| *** adjohn has joined #openstack-meeting | 22:07 | |
| annegentle | We may even have a yoga class or something to enlighten our minds prior to discussion. :) | 22:07 |
| annegentle | ttx: yes, understood. | 22:07 |
| annegentle | of course :) | 22:07 |
| ttx | ok then | 22:08 |
| ttx | #endmeeting | 22:08 |
| *** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 22:08 | |
| openstack | Meeting ended Tue Sep 27 22:08:40 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:08 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-21.03.html | 22:08 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-21.03.txt | 22:08 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-21.03.log.html | 22:08 |
| *** wwkeyboard has joined #openstack-meeting | 22:08 | |
| *** Vek has left #openstack-meeting | 22:08 | |
| ttx | danwent: floor is yours | 22:08 |
| *** markmc has left #openstack-meeting | 22:09 | |
| danwent | thx ttx | 22:09 |
| danwent | #startmeeting | 22:09 |
| openstack | Meeting started Tue Sep 27 22:09:07 2011 UTC. The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot. | 22:09 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 22:09 |
| edgarmagana | Dan: Thanks for the heads up | 22:09 |
| dendrobates | o/ | 22:09 |
| markvoelker | o/ | 22:09 |
| danwent | hey all. | 22:09 |
| carlp | hello! | 22:09 |
| danwent | edgar: np | 22:09 |
| bhall_ | howdy | 22:09 |
| danwent | btw, salv is stuck at SFO trying to get his car rental | 22:09 |
| troytoman | o/ | 22:09 |
| *** Jamey_ has joined #openstack-meeting | 22:09 | |
| *** liemmn has quit IRC | 22:10 | |
| danwent | he sends his regrets | 22:10 |
| *** troytoman is now known as troytoman-away | 22:10 | |
| danwent | should be a pretty short meeting though | 22:10 |
| *** troytoman-away is now known as troytoman | 22:10 | |
| danwent | ok | 22:10 |
| danwent | agenda: http://wiki.openstack.org/Network/Meetings | 22:10 |
| danwent | #topic general status | 22:10 |
| *** openstack changes topic to "general status" | 22:10 | |
| danwent | design summit is next week, hope to see you all in boston | 22:11 |
| danwent | today is the last day to get proposals in, but space for netstack items is already overflowing. | 22:11 |
| dendrobates | I highly suggest we make use of the unconference for overflow | 22:11 |
| danwent | we've had to drastically cut down on the time for our sessions. hopefully we can make a lot of use of the unconference space though, as I want to make sure everyone gets a chance to discuss what they want to cover | 22:11 |
| danwent | :) | 22:12 |
| danwent | does anyone have a session that they think is really important, but haven't proposed? | 22:12 |
| danwent | its now or never…. (or rather, not until the next summit) | 22:12 |
| danwent | Ok, so the plan is to start the summit focusing on more tactical items that are fairly well understood (e.g., API v1.1) | 22:13 |
| danwent | Then we'll branch into general discussions about how to insert more advanced network services. | 22:13 |
| danwent | finally, we'll have sessions to talk about a few of those specific services that people are most interested in. | 22:14 |
| danwent | does that sound reasonable? | 22:14 |
| dendrobates | yes | 22:14 |
| danwent | hopefully we can leave some space at the end so people can find unconference space to branch out from there | 22:14 |
| danwent | Ok, great. Any other questions/concerns about the summit/conference? | 22:14 |
| *** wwkeyboard has left #openstack-meeting | 22:15 | |
| danwent | schedules still aren't set. | 22:15 |
| danwent | ttx said that summit schedule may not be finalized until close to monday. | 22:15 |
| edgarmagana | dan: the session about networking services is the one that you have submitted? | 22:15 |
| danwent | edgar: I think we'll merge your session and mine into a 55-minute session. | 22:15 |
| danwent | does that sound reasonable? | 22:15 |
| edgarmagana | dan: Absolutely! | 22:16 |
| danwent | I think this will be a key topic of interest, so I definitely want to make sure it gets time. | 22:16 |
| *** jamesurquhart has joined #openstack-meeting | 22:16 | |
| danwent | great | 22:16 |
| *** rafadurancastane has quit IRC | 22:16 | |
| danwent | Ok, that's it for the summit. let's move on to the regular agenda | 22:16 |
| danwent | #topic donabe status | 22:16 |
| *** openstack changes topic to "donabe status" | 22:16 | |
| danwent | (shaking it up, putting donabe in front of melange :P) | 22:16 |
| dendrobates | ha | 22:16 |
| *** adjohn has quit IRC | 22:16 | |
| dendrobates | I sent out an email about tomorrows meeting | 22:17 |
| dendrobates | we are going to try webex but fall back to irc, if there is a problem | 22:17 |
| danwent | dendrobates: I may need to channel salvatore and request that we alternate between webex and go-to-meeting | 22:17 |
| dendrobates | I will be sending out an agenda before the meeting | 22:17 |
| dendrobates | danwent: that is fine as long as we can record the session | 22:18 |
| danwent | :P | 22:18 |
| danwent | actually, i prefer webex | 22:18 |
| dendrobates | It may be a total failure, but it is worth a try | 22:18 |
| danwent | I think its great to try to get people on the same page pre-summit | 22:18 |
| dendrobates | That's really the only update I have. | 22:19 |
| danwent | ok, any questions for donabe? | 22:19 |
| danwent | #topic melange status | 22:19 |
| *** openstack changes topic to "melange status" | 22:19 | |
| danwent | troy? | 22:19 |
| troytoman | have moved the merge prop over to git/gerrit | 22:19 |
| troytoman | working through comments | 22:19 |
| troytoman | also closing gaps between the nova/quantum/melange flow | 22:20 |
| troytoman | finally, should finish up some of the nova refactoring to make the integration cleaner | 22:20 |
| danwent | troytoman: yeah, i definitely things there still room for that as well. I would add dashboard to the mix too. | 22:20 |
| troytoman | that's about it | 22:20 |
| danwent | one of the sessions we'll have on monday is going to focus on that flow from the user perspective. should be very helpful. | 22:21 |
| carlp | troytoman: TV and I would love to chat with you next week re: discovery | 22:21 |
| troytoman | may have host a unconference discussion about how to enable multi-nic/quantum in nova api | 22:21 |
| troytoman | carlp: sure thing | 22:21 |
| danwent | troy: I think we can cover that to some degree in the flow session, then perhaps have an unconference to do more detailed design. | 22:22 |
| troytoman | so that you can select networks and add vifs at create time | 22:22 |
| danwent | agree that it is really important | 22:22 |
| troytoman | danwent: perfect | 22:22 |
| danwent | ok, any other questions for melange? | 22:22 |
| troytoman | danwent: sounds like the right place | 22:22 |
| danwent | #topic quantum status | 22:22 |
| *** openstack changes topic to "quantum status" | 22:22 | |
| troytoman | ok. see everyone next week! | 22:23 |
| danwent | troy: thx | 22:23 |
| danwent | quantum release went out. | 22:23 |
| danwent | Big thanks to Salvatore for the v1.0 API doc. | 22:23 |
| danwent | Thanks for all for reviews on the Quantum Admin Guide. | 22:23 |
| bhall_ | thanks to dan for the admin guide and last minute merges :) | 22:23 |
| danwent | it would be great to have input on how to setup quantum + dashboard, so we are ready to go once keystone releases. | 22:23 |
| troytoman | danwent: thanks for all your leadership on that. awesome work everyone! | 22:24 |
| danwent | markvoelker here? | 22:24 |
| edgarmagana | dan: +1 last time I tried ran into some issues | 22:24 |
| danwent | or arvind? | 22:24 |
| markvoelker | o/ | 22:24 |
| zns | ttx: sorry - missed you. If you're still around, my understanding is that Keystone is now Diablo compatible. Is there anything missing? | 22:25 |
| danwent | hey mark, are you folks planning on doing a session at the summit about dashboard + quantum? | 22:25 |
| zns | devcamcar: is this bug a show-stopper for you or does it just result in admins seeing all tenants? | 22:25 |
| danwent | or should be just roll that into the flow discussion? | 22:25 |
| danwent | zns: sorry, main openstack meeting is over and people have likely left. This is the NetStack meeting. | 22:25 |
| markvoelker | I don't currently have one planned, but there has been some chatter about what we'd like to see. May be a good topic for unconference | 22:26 |
| zns | danwent: ok - sorry to butt in. | 22:26 |
| *** edconzel has left #openstack-meeting | 22:26 | |
| danwent | zns: np | 22:26 |
| somik | unconference or I did see salvatore propose a session, so roll dashboard discussions into that.. | 22:26 |
| markvoelker | Either way works for me. =) | 22:27 |
| danwent | markvoelker: ok, great. I'm sure this will come up in the discussion on flow, which Salv proposed. If there are details beyond that, we can do an unconference. | 22:27 |
| danwent | I'll try to make sure day 3 has sufficient time for unconference sessions resulting from earlier sessions. | 22:27 |
| danwent | Ok, any other comments on the release or docs? | 22:27 |
| danwent | I think we probably already covered the summit + conference at the begining of the meeting. | 22:28 |
| danwent | we got a lot of good press for quantum, as Quantum was mentioned in the main OpenStack release announcement. very cool. | 22:28 |
| danwent | bhall, anything you need to discuss about the shift to github, gerrit? | 22:28 |
| danwent | is everyone getting review emails now? | 22:29 |
| *** mcohen has quit IRC | 22:29 | |
| bhall_ | danwent: I talked to jeblair about this this morning | 22:29 |
| bhall_ | the way it works now is that anyone that wants emails about new reviews/etc needs to go add themselves as watchers in gerrit to the quantum project | 22:29 |
| danwent | got a link? | 22:30 |
| bhall_ | I can send out an email about how to do this | 22:30 |
| danwent | ok great. thanks. | 22:30 |
| *** mcohen has joined #openstack-meeting | 22:30 | |
| danwent | in that email, could you also include the pointer on how to transfer a diff from launchpad over the github? | 22:31 |
| bhall_ | but, until I do that, just go here: https://review.openstack.org/#settings,projects | 22:31 |
| bhall_ | and add quantum | 22:31 |
| bhall_ | sure | 22:31 |
| danwent | Ok, great. Any other questions on quantum? | 22:31 |
| *** troytoman is now known as troytoman-away | 22:31 | |
| danwent | #topic open discussion | 22:31 |
| *** openstack changes topic to "open discussion" | 22:31 | |
| danwent | ok, that was short and sweet. | 22:32 |
| danwent | everyone please do send out what you have as far as blueprints ahead of the summit meeting itself | 22:32 |
| danwent | hopefully we'll have an finalized netstack agenda by tomorrow. We may have to wait longer to know the exact time of sessions though. | 22:33 |
| danwent | see you all in boston :) | 22:33 |
| danwent | #endmeeting | 22:33 |
| *** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 22:33 | |
| openstack | Meeting ended Tue Sep 27 22:33:30 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:33 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-22.09.html | 22:33 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-22.09.txt | 22:33 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-22.09.log.html | 22:33 |
| * markvoelker is already in Boston, but sadly hasn't had time to scope out a place for Quantum 1.0 celebratory drinks =) | 22:33 | |
| danwent | edgar: I still owe you an email… hope to get to that very soon! | 22:33 |
| *** jk0 has left #openstack-meeting | 22:33 | |
| *** shwetaap has quit IRC | 22:34 | |
| somik | have a good one everybody till next week! | 22:34 |
| *** jamesurquhart has left #openstack-meeting | 22:35 | |
| *** edgarmagana has quit IRC | 22:36 | |
| *** ying has quit IRC | 22:36 | |
| *** zns has left #openstack-meeting | 22:41 | |
| *** somik has quit IRC | 22:45 | |
| *** yogirackspace has left #openstack-meeting | 22:45 | |
| *** Guest21732 has quit IRC | 22:47 | |
| *** medberry is now known as med_out | 22:52 | |
| *** mcohen has left #openstack-meeting | 22:52 | |
| *** dendrobates is now known as dendro-afk | 22:55 | |
| *** Binbin has quit IRC | 22:57 | |
| *** Binbin has joined #openstack-meeting | 22:57 | |
| *** Jamey_ has quit IRC | 22:59 | |
| *** dragondm has quit IRC | 23:09 | |
| *** edconzel_ has quit IRC | 23:12 | |
| *** markvoelker has quit IRC | 23:32 | |
| *** Gordonz has quit IRC | 23:43 | |
| *** jrouault has quit IRC | 23:47 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!