21:06:00 <ttx> #startmeeting
21:06:01 <openstack> Meeting started Tue Jan 10 21:06:00 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:06:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic.
21:06:13 <ttx> Today's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting
21:06:29 <ttx> Stay until the end -- we'll discuss the F release name :)
21:06:44 <notmyname> sure sure. keep it for the end so we all stick around :-)
21:06:44 <ttx> #topic Actions from previous meeting
21:06:58 <jaypipes> hehe
21:07:04 <LinuxJedi_tablet> :)
21:07:05 <ttx> vishy had two actions...
21:07:14 <ttx> * vishy to ping vladimir3p about volume-type-scheduler status
21:07:19 <ttx> * vishy to look up unplanned E3/E4 blueprints and confirm/unconfirm them
21:07:38 <ttx> that second one was done... for the first one we'll talk about it during Nova status, if he joins
21:08:08 <ttx> #topic Keystone status
21:08:18 <ttx> joesavak: o/
21:08:25 <ttx> #link https://launchpad.net/keystone/+milestone/essex-3
21:08:29 <joesavak> \o
21:08:35 <ttx> Is the status on this page accurate, afayct ?
21:08:50 <joesavak> Yup.
21:09:05 <ttx> About https://blueprints.launchpad.net/keystone/+spec/service-endpoint-location
21:09:17 <ttx> If you didn't hear anything from HP, I suppose we should remove it from the E3 targets ?
21:09:37 <joesavak> Endpoint location has not started yet but had conversations today from gyee on it today. I'm assuming he/she is hp
21:09:50 <gyee> service endpoing location blueprint will not make E3
21:09:53 <joesavak> they were waiting for feedback which I provided and anyone else can review too.
21:10:11 <joesavak> thanks gyee
21:10:15 <ttx> gyee: E3 is feature freeze for Keystone. Does that mean it won't make Essex ?
21:10:56 <gyee> it won't make E3
21:11:25 <ttx> gyee: ok, you should talk to zns for retargeting / getting a post-E3 exception / deferring to F
21:11:43 <joesavak> this should be developed as an extension, so i'm not sure if any service is dependent on it
21:11:46 <gyee> k
21:11:49 <ttx> #action gyee to talk to zns about service-endpoint-location milestone targeting
21:11:56 <joesavak> if that's the case then maybe delivery in e-4 is ok
21:12:02 <ttx> joesavak: Are those two still on track for completion in the next two weeks:
21:12:07 <ttx> https://blueprints.launchpad.net/keystone/+spec/keystone-refactor-backend (zns)
21:12:10 <ttx> https://blueprints.launchpad.net/keystone/+spec/keystone-client (anotherjesse)
21:12:27 <joesavak> Yes
21:12:33 <ttx> joesavak: Anything else ?
21:12:39 <joesavak> Nope
21:12:44 <ttx> Questions for Keystone ?
21:13:21 <ttx> #topic Swift status
21:13:25 <ttx> notmyname: o/
21:13:28 <notmyname> hi
21:13:39 <notmyname> we released swift 1.4.5 yesterday
21:14:04 <notmyname> https://github.com/openstack/swift/blob/master/CHANGELOG
21:14:23 <notmyname> we'll probably have a fairly fast follow for 1.4.6
21:14:41 <devcamcar> o/
21:14:52 <notmyname> we'd like to get form uploading (ie upload stuff to swift from html forms) in a release asap
21:15:38 <ttx> notmyname: ok, if we could get a bit more of an advance notice next time, would be great
21:15:44 * jaypipes imagines uploading image files via HTML to Swift...
21:15:54 <notmyname> jaypipes: yup
21:15:56 <jaypipes> hehe
21:16:26 <ttx> notmyname: Anything else ?
21:16:37 <notmyname> I don't think so. any questions?
21:17:04 <ttx> #topic Glance status
21:17:13 <ttx> jaypipes: yo! We missed you last week.
21:17:36 <ttx> What's Glance stance about feature blueprints vs. milestones ?
21:17:49 <ttx> All major features must land by E3 ? All features must land by E3 ? Or is it E4 ?
21:18:14 <jaypipes> ttx: ok... let me summarize
21:18:28 <ttx> jaypipes: you can use #info :)
21:19:02 <Guest36549> #info
21:19:23 <jaypipes> #info E3 is not going to contain any more blueprints with one possible exception: a cut-down image replication system
21:20:01 <ttx> jaypipes: so refactor-internal-api is deferred ?
21:20:04 <jaypipes> #info jay in process of negotiating what that image replication might entail with some Glance users (gcampbell and others). See blueprint here: https://blueprints.launchpad.net/glance/+spec/zones-replication
21:20:27 <jaypipes> ttx: no. that is in E3... already has been targeted.
21:20:36 <jaypipes> ttx:  I meant no *further* blueprints... sorry.
21:21:05 <ttx> ok
21:21:19 <ttx> and will you have features in E4 ?
21:21:22 <jaypipes> johannes got protected-images blueprint implemented and bcwaldon has just completed the multi-processing-server blueprint and should go in today.
21:21:32 <ttx> or is E3 a feature freeze ?
21:22:00 <jaypipes> ttx: no, there will be no features in E4 -- with the possible exception if the image-replication mentioned above is agreed upon and slips from E3 to early E4.
21:22:21 <ttx> jaypipes: Who is/willbe working on https://blueprints.launchpad.net/glance/+spec/refactor-internal-api ?
21:22:27 <jaypipes> ttx: however there will be NO 2.0 API stuff worked on in the essex release series.
21:22:36 <jaypipes> ttx: myself and bcwaldon most likely.
21:23:02 <jaypipes> ttx: and most of that work (refactor-internal-api) will be prep work for the 2.0 API series work...
21:23:02 <ttx> assigning to you, please reassign if necessary
21:23:06 <jaypipes> ttx: k
21:23:22 <ttx> jaypipes: Anything else ?
21:23:52 <jaypipes> ttx: nope, that's it for now. I'd like to thank the myriad contributors that have come out of the woodwork this cycle to help. much appreciated!
21:23:58 <jaypipes> #thankyou :)
21:24:21 <ttx> Questions on Glance ?
21:25:16 <ttx> #topic Nova status
21:25:22 <ttx> vishy: hey
21:25:23 <jaypipes> in case people thought the above was sarcastic, it definitely was not! please see new contributors in E3 milestone...
21:25:26 <vishy> hi
21:25:35 <ttx> #link https://launchpad.net/nova/+milestone/essex-3
21:25:41 <vishy> in response to the earlier action items
21:25:45 <ttx> jaypipes: good! your calls for help haven't been in vain!
21:25:59 <vishy> vladimir said he was going to try to do that branch this week
21:26:16 <ttx> vishy: do we have a plan B ? If this is Essential...
21:26:30 <vishy> ttx: we don't I think we may have to downgrade it
21:26:50 <ttx> vishy: if it's important but we can live without, should be High
21:27:13 <ttx> vishy: or would you consider it for post-E3 soft frozen world ?
21:27:14 <vishy> changed
21:27:39 <ttx> vishy: Would like to get a bit of progress status on a few more bps:
21:27:51 <ttx> * https://blueprints.launchpad.net/nova/+spec/interim-nova-authz-service (vishy) -- is that one complete ?
21:28:37 <vishy> no
21:28:45 <vishy> still has a few more merge props
21:28:49 <vishy> reassigned to waldon
21:28:53 <bcwaldon> thanks!
21:28:56 <vishy> he's doing the first prop today (for compute)
21:29:04 <ttx> * https://blueprints.launchpad.net/nova/+spec/separate-nova-adminapi (bcwaldon) -- Is there more to do on this one ?
21:29:04 <vishy> then we still have to do network and volume
21:29:42 <bcwaldon> ttx: yes, been side tracked lately
21:29:46 <ttx> * https://blueprints.launchpad.net/nova/+spec/openstack-api-ssl (HP) -- No progress on this since Nov 21, does it need to move out of the plan ?
21:30:21 <vishy> looks like hp has fallen behind on that one
21:30:34 <vishy> i will ping them
21:30:50 <ttx> #action vishy to ping HP on openstack-api-ssl status
21:30:55 <ttx> * https://blueprints.launchpad.net/nova/+spec/scaling-zones (comstud) -- What's the status of this one ? Started ?
21:31:17 <ttx> * https://blueprints.launchpad.net/nova/+spec/multiple-floating-ip-ranges (vishy) -- Is that one now complete ?
21:31:46 <vishy> i think comstud has started it
21:32:05 <vishy> second is complete, will mark
21:32:08 <ttx> * https://blueprints.launchpad.net/nova/+spec/nova-parity-floating (bhall) -- What's the priority of that one ?
21:32:22 <westmaas> ttx: comstud has started that one.
21:32:31 <ttx> westmaas: will mark started
21:33:45 <ttx> vishy: priority for nova-parity-floating ? Low ?
21:34:03 <vishy> yeah changed
21:34:07 <ttx> vishy: Anything else ?
21:34:23 <vishy> ttx: reviews are lagging a bit
21:34:37 <vishy> people are avoiding some of the larger 3rd party patches
21:34:43 <vishy> but other than that I think we're doing ok
21:34:45 <ttx> vishy: I wonder why :)
21:34:56 <ttx> Nova subteam leads: anything on your side ?
21:35:21 <ttx> Anyone else: Questions on Nova ?
21:35:55 <ttx> #topic Horizon status
21:35:59 <ttx> devcamcar: o/
21:36:04 <devcamcar> o/
21:36:05 <ttx> #link https://launchpad.net/horizon/+milestone/essex-3
21:36:09 <ttx> Is the status here accurate ?
21:36:15 <devcamcar> yes
21:36:25 <ttx> So https://blueprints.launchpad.net/horizon/+spec/ext-roles is not started yet ?
21:36:32 * ttx doesn't like Essential specs that are "not started" :)
21:36:41 <devcamcar> ttx: correct
21:36:46 <devcamcar> me neither :)
21:36:58 <ttx> devcamcar: still confident on delivery ? I have no idea of the amount of work involved.
21:37:01 <devcamcar> we'll know in the next day or two whether that one will be deliverable
21:37:16 <ttx> devcamcar: plan B is to defer to early E4 ?
21:37:19 <devcamcar> yes
21:37:25 <ttx> devcamcar: Anything else ?
21:37:29 <devcamcar> nope!
21:37:34 <devcamcar> quick and easy :)
21:37:40 <ttx> Questions for Horizon ?
21:37:52 <devcamcar> oh i do have one minor point - we got some localization pull requests
21:37:58 <devcamcar> while we are also changing a bunch of things
21:38:13 <devcamcar> so i've asked folks to plan on contributing localization updates starting march 1st
21:38:28 <devcamcar> things should stop moving so much then
21:38:44 <ttx> +1
21:39:13 <ttx> #topic Incubated projects and other Team reports
21:39:23 <ttx> danwent, troytoman-away: o/
21:39:29 <danwent> hello
21:39:42 <danwent> e-3 for quantum is in the "not great, not terrible" state: https://launchpad.net/quantum/+milestone/essex-3
21:40:01 <danwent> probably need to boot out a few things that haven't been started, but waiting with devs to confirm.
21:40:24 <danwent> we're also working with the openstack-common folks to identify good candidates of stuff that can be removed from quantum codebase to openstack-common
21:40:27 <tr3buchet> hmm
21:41:00 <ttx> danwent: I heard you plan to reuse the same bug squashing day as Nova, on Feb 2, with a slightly different objective ?
21:41:09 <danwent> finally, there's a thread on the netstack ML (openstack CC'd) to figure out whether we want to integrate quantum with the legacy cloudpipe VPN, or just go ahead and create a separate service.
21:41:34 <danwent> ttx: yes, plan is to focus on code quality, including code coverage, pylint, etc.
21:41:36 <ttx> Feel free to add to http://wiki.openstack.org/BugSquashingDay/20120202 in preparation.
21:41:40 <danwent> k
21:41:47 <danwent> tre3buchet: a particular concern?
21:42:02 <danwent> floating IP stuff for nova is coming along well.
21:42:03 <ttx> tr3buchet always hmms.
21:42:07 <danwent> :)
21:42:17 <tr3buchet> yeah i'm all up in yur melanges codes at the moment
21:42:29 <danwent> yuck :P
21:42:50 <danwent> in nova you mean?
21:42:55 <tr3buchet> both
21:43:02 <tr3buchet> trying to get everything tied together at the moment
21:43:18 <ttx> tr3buchet: anything you need help with ?
21:43:28 <danwent> feel free to ping me offline
21:43:30 <tr3buchet> ttx: not right at the moment
21:43:31 <ttx> Any other team lead with a status report ? CI, docs ?
21:43:34 <tr3buchet> danwent: will do
21:43:50 <annegentle> Docs met yesterday, summary at http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-09-20.03.html
21:44:11 <markmc> ttx, we should mention http://wiki.openstack.org/StableBranchRelease
21:44:19 <annegentle> Looking into ways to make diffs easier on XML docs as well as serve users with API docs.
21:44:24 <annegentle> The "usual"
21:44:26 <ttx> markmc: go for it
21:44:55 <markmc> ok, so we "release team" plan to do a 2011.3.1 release of nova and glance soonish
21:45:05 <markmc> from the stable/diablo branch
21:45:10 <markmc> it's all laid out in http://wiki.openstack.org/StableBranchRelease
21:45:21 <ttx> #link http://wiki.openstack.org/StableBranchRelease
21:45:22 <markmc> vishy, I meant to ping you about it earlier
21:45:33 <markmc> vishy, sounds sane and sensible earlier ?
21:45:34 <vishy> cool!
21:45:36 <ttx> #info "release team" plan to do a 2011.3.1 release of nova and glance soonish
21:45:47 * markmc notes jaypipes generously signed off on the idea already
21:46:00 <markmc> vishy, thanks :)
21:46:19 <markmc> ttx, should we set a release date or just see how it goes?
21:46:50 <ttx> markmc: I'd like us to get the bug series conversion done before... But we could set sometime next week
21:47:01 <markmc> ttx, sounds good
21:47:02 <ttx> markmc: to avoid collision with E3 release week
21:47:23 <ttx> probably Thursday next week.
21:47:33 <ttx> with a candidate built on Tuesday
21:47:37 <markmc> as the release date?
21:47:44 <markmc> or an RC date?
21:47:55 <ttx> RC tuesday, release thursday ?
21:48:04 <markmc> ok, cool
21:48:35 <ttx> I'll doublecheck by tomorrow but I think it should work
21:48:42 <ttx> #topic Open discussion
21:48:54 <ttx> There will be an OpenStack developers meeting during FOSDEM:
21:49:00 <ttx> #link http://fosdem.org/2012/schedule/event/osdem
21:49:10 <ttx> If you're around Brussels on February 4-5, please come and see us.
21:49:25 <ttx> And now, for the topic everyone was waiting for
21:49:38 <ttx> The location for the next design summit has been decided: it should happen in San Francisco.
21:49:49 <ttx> The date is not confirmed yet, but should be April 16-18.
21:49:56 <danwent> city by the bay!
21:50:00 <ttx> So now is the time to play our usual release naming game !
21:50:13 <ttx> This time with cities and counties in California starting with F (single words, 10 character or less)
21:50:21 <ttx> That gives the following candidates:
21:50:26 <westmaas> Francisco
21:50:26 <ttx> #link http://wiki.openstack.org/ReleaseNaming
21:50:36 <ttx> There are pretty good ones in there
21:50:42 <ttx> I have a personal preference for "Fawnskin"
21:50:49 <tr3buchet> ok guys
21:50:53 <tr3buchet> and i'm series here
21:50:55 <uksysadmin> lol @ttx
21:50:57 <glenc> Felton is awesome - Big Trees Steam Railroad
21:50:59 <danwent> folsom is a city and street fair
21:51:01 <tr3buchet> Frankenstein
21:51:16 <tr3buchet> it's time to put the pieces together and make it walk
21:51:21 <ttx> tr3buchet: that's not a city in California, and it's too long :P
21:51:28 <wwkeyboard> Folsom?
21:51:30 <jkoelker> Folsem
21:51:38 <bhall> fontana
21:51:40 <dragondm> and a prison.
21:51:51 <danwent> wwkeyboard: google about folsom street fair, if you dare
21:51:53 <jaypipes> Fillmore.
21:52:16 <ttx> I like that Freestone has "free" and "stone", but I still prefer Fawnskin.
21:52:18 <uksysadmin> http://www.theus50.com/california/cities.php
21:52:31 <wwkeyboard> danwent: it's also the subject of many songs
21:52:43 <glenc> Felton - http://www.roaringcamp.com/
21:52:46 <tr3buchet> wonder if we could found a town called Frankenstein
21:52:51 <ttx> uksysadmin: oh, there are a few new ones in there.
21:52:53 <tr3buchet> i could be mayor
21:53:07 <uksysadmin> tax, nothing like foreskin � I mean�
21:53:12 <danwent> wwkeyboard: yes, indeed
21:53:22 <westmaas> anyone know how to pronounce firebaugh?
21:53:44 <soren> westmaas: Doesn't matter. Noone knew how to pronounce Bexar either.
21:53:48 <uksysadmin> Fortuna sounds good� but a bit fishy
21:53:49 <westmaas> heh
21:53:56 <joesavak> For tuna
21:54:01 <dabo> against tuna
21:54:07 <ttx> I'll start a Launchpad poll with those options tomorrow, and will announce it on the ML.
21:54:11 <glenc> O Fortuna, velut luna, statu variabilis. Could be appropriate.
21:54:21 <ttx> I'll include the missing stuff from http://www.theus50.com/california/cities.php
21:54:54 <ttx> (Finley, Fellows and Friant)
21:54:55 <tr3buchet> well if i had to pick it'd be Flournoy
21:55:05 <ttx> oh, Flournoy.
21:55:15 <tr3buchet> !!
21:55:16 <openstack> tr3buchet: Error: "!" is not a valid command.
21:55:23 <tr3buchet> :{
21:55:37 <ttx> wow, plenty of good options. That poll will be disputed.
21:55:47 <ttx> Anything else, anyone ?
21:56:00 <joesavak> OpenStack austin meetup tonight
21:56:19 <joesavak> http://www.meetup.com/OpenStack-Austin/
21:57:17 <ttx> ok then.
21:57:21 <ttx> #endmeeting