21:02:03 <ttx> #startmeeting
21:02:04 <openstack> Meeting started Tue May  1 21:02:03 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:21 <ttx> Welcome everyone to our weekly Project/release meeting
21:02:27 <ttx> Today's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting
21:02:34 <ttx> Should be a quick one. We'll have a look at the current state of the Folsom plans.
21:02:47 <ttx> #topic Keystone status
21:02:57 <ttx> Let's start with heckj while the wifi works
21:03:02 <ttx> maybe
21:03:06 <heckj> Keystone meeting this morning nailed down most of the blueprints
21:03:13 <ttx> #link https://blueprints.launchpad.net/keystone/folsom
21:03:26 <heckj> We have a few undeteremined for who's going to do them, but most are assigned out at this point
21:03:32 <ttx> service-endpoint-location is marked "obsolete", should we unset the series goal ?
21:03:40 <ttx> or is it still very much a goal ?
21:03:53 <heckj> unset - I'll get it
21:04:07 <ttx> Also I don't really get what draft-v3-blueprint is about. A blueprint about drafting a blueprint ?
21:04:33 <heckj> it's for drafting the next rev API
21:04:38 <heckj> just typoed the name
21:04:48 <vishy> heckj: you can change it
21:04:49 <dolphm> draft-v3-api?
21:05:06 <ttx> heckj: so this will be a non-code blueprint, right ?
21:05:11 <dolphm> vishy: the url is a permalink though, i think
21:05:18 <heckj> vishy: would love to - haven't figured out how
21:05:24 <vishy> dolphm: nope just fixed it for you
21:05:32 <heckj> the text in the blueprint is correct
21:05:38 <dolphm> https://blueprints.launchpad.net/keystone/+spec/draft-v3-api
21:05:40 <dolphm> magic!
21:05:46 <ttx> awesome
21:05:48 <heckj> thank you!
21:05:57 <devcamcar_> ooo
21:06:08 * cloudfly reads furiously
21:06:10 <vishy> heckj, dolphm : ffr it is the 'Set the URL for this specification' link under the summary
21:06:19 <ttx> heckj: so this will be a non-code blueprint, right ?
21:06:27 * vishy knows way too much about blueprints :(
21:06:45 <heckj> ttx: correct. API document opened for feedback - much like what jaypipes/bcwaldon have done for Glance
21:06:55 <ttx> heckj: ok
21:07:06 <ttx> Do you expect more blueprints to be targeted to folsom-1, or is the map pretty much complete ?
21:07:58 <heckj> for F1, we're complete - I expect some churn and change in F2/F3 though
21:08:04 <heckj> very dependent on the V3 API core BP
21:08:09 <ttx> sure, that's ok
21:08:13 <ttx> heckj: anything else ?
21:08:17 <heckj> nope
21:08:21 <ttx> Questions about Keystone ?
21:08:42 <ttx> #topic Swift status
21:08:47 <ttx> notmyname: o/
21:08:47 <notmyname> o/
21:08:53 <ttx> notmyname: Do you expect any major new feature in your next release ?
21:09:09 <notmyname> yes. object versioning has been added since essex
21:09:09 <ttx> (something that would warrant a blueprint ?)
21:09:42 <ttx> notmyname: could you create a blueprint retrospectively ?
21:09:51 <notmyname> ya, I can do that
21:09:59 <ttx> Should the next Swift release be 1.4.10, 1.5...
21:10:12 <ttx> Or do we need to discuss a bit more how we want to actually do it ?
21:10:31 <notmyname> I think it will probably 1.5
21:10:49 <ttx> 1.5.0 probably, then
21:10:55 <notmyname> but I don't have strong feeling either way
21:11:59 <ttx> me neither... at least 1.5.0 makes the minor version number mean something (series mapping)
21:12:08 <ttx> Any vague idea on the date, so that I start planning ?
21:12:20 <notmyname> I'll add the blueprints for other things that have happened as well
21:12:44 <notmyname> no, I don't have a date yet. I can work on that this week
21:13:08 <ttx> doesn't have to be a precise date. More like an indication :)
21:13:12 <ttx> notmyname: Anything else ?
21:13:19 <notmyname> nope
21:13:24 <ttx> Questions on Swift ?
21:13:53 <ttx> notmyname: I'll create the 1.5.0 milestone so that you can target your blueprints against it
21:13:57 <notmyname> ok
21:14:10 <ttx> #topic Glance status
21:14:16 <ttx> bcwaldon: yo
21:14:19 <bcwaldon> eyyyy
21:14:23 <ttx> #link https://blueprints.launchpad.net/glance/folsom
21:14:35 <bcwaldon> yeah...
21:14:37 <bcwaldon> I'm looking for feedback on a couple of emails I sent to the list, one about 'Glance Architecture' and one on 'Blueprints!'.
21:14:45 <ttx> bcwaldon: glance-get-cmd is marked obsolete, should we unset the series goal for it ?
21:14:55 <bcwaldon> if I marked it Obsolete, then yes
21:15:02 <ttx> on it
21:15:27 <ttx> you should start targeting some of them to folsom-1 when they have someone signed up to do it
21:15:34 <bcwaldon> Yep, definitely will
21:15:46 <ttx> Would separate-client be a folsom-1 target ?
21:15:47 <bcwaldon> I've got a couple that are superblueprints that wont be targeted for a while
21:16:14 <bcwaldon> ttx: definitely
21:16:29 <bcwaldon> (had to look up when f1 was)
21:16:29 <ttx> ok, please set the folsom-1 targets before the end of the week
21:16:41 <bcwaldon> don't you boss me around
21:16:42 <ttx> so that we can start tracking progress towards the milestone
21:16:43 <bcwaldon> but I will
21:17:02 <ttx> bcwaldon: "no target" is a valid answer :P
21:17:14 <bcwaldon> Sounds good. I'm looking for assignees for several of those blueprints
21:17:29 <bcwaldon> So if anybody has been poking me about how to help with Glance inFolsom, go read my email 'Blueprints!'
21:17:43 <ttx> bcwaldon: Anything else you wanted to mention ?
21:18:05 <bcwaldon> ttx: nope, I'm trying to release my thoughts directly to the ML so I don't forget anything around meeting time
21:18:15 <bcwaldon> so that's it for me :)
21:18:23 <ttx> works for me :)
21:18:24 <ttx> Questions on Glance ?
21:18:51 <ttx> #topic Quantum status
21:18:57 <ttx> danwent: hey
21:18:59 <danwent> https://launchpad.net/quantum/+milestone/folsom-1
21:19:01 <danwent> hey
21:19:06 <ttx> https://blueprints.launchpad.net/quantum/folsom is empty because you didn't set the series goal to Folsom on the blueprints
21:19:15 <ttx> Setting the series goal lets you compile a list of "Folsom" blueprints which is generally more useful than the list of all blueprints, so I recommend doing it
21:19:19 <danwent> ah, sorry, i've just been targeting things to milestones
21:19:31 <danwent> Ok, will do that.
21:19:39 <ttx> danwent: not a big deal, gives you those nice "Folsom" views
21:19:51 <danwent> so far, I've flushed out folsom-1 and folsom-2 milestones
21:19:55 <ttx> for some reason LP doesn't automatically build that
21:20:03 <danwent> which is where we're targeting to get must of our "must haves" for Folsom release
21:20:10 <ttx> I see 9 blueprints were targeted to folsom-1...
21:20:14 <ttx> #link https://launchpad.net/quantum/+milestone/folsom-1
21:20:38 <ttx> You probably should set them to "Approved" and prioritize all of them if you're OK with them.
21:20:44 <danwent> yup, many of them are fairly small, but two are very large (new API work to merge melange, and authz work)
21:21:17 <danwent> ok, I was waiting on designs on some of them before approving.
21:21:28 <ttx> I tend to check status on things that you set Essential/High
21:21:34 <danwent> will make sure that we get designs and approval for next week.
21:21:38 <ttx> so lowering prio is a good way to get rid of me
21:21:57 * oubiwann makes a note of that...
21:22:03 <danwent> ok, i expect only two high/essential blueprints left after this week.
21:22:23 <danwent> two other ones will be done
21:22:37 <ttx> oubiwann: priority is an indication of how important the blueprint is for release. So it's not totally a joke :)
21:23:01 <ttx> danwent: Anything else ?
21:23:04 <danwent> nope
21:23:07 <ttx> Questions on Quantum ?
21:23:25 <ttx> #topic Nova status
21:23:35 <ttx> vishy: hey
21:23:36 <vishy> hi
21:23:40 <ttx> #link https://blueprints.launchpad.net/nova/folsom
21:23:47 <vishy> so I've been doing massive blueprint triaging
21:23:48 <ttx> Looks quite good. You're getting used to that game
21:23:53 <vishy> had 180 blueprints
21:24:02 <vishy> i think i'm only about halfway done
21:24:03 * oubiwann chokes
21:24:15 <vishy> (actually 188)
21:24:37 <vishy> so I've targetted all the ones i am familiar with, but there are still a few that I have no idea about
21:24:41 <ttx> oubiwann: vishy tries to beat me a blueprint-handling LP karma.
21:24:46 <ttx> at*
21:24:51 <oubiwann> hehehe
21:24:59 <vishy> ttx: i'm considering declaring blueprint bankruptcy
21:25:03 <ttx> You should set the priority for all the undefined ones...
21:25:08 <ttx> at least those who have a clear assignee that signed up to do the work
21:25:24 <vishy> basically saying, if you own a blueprint and it isn't targetted for folsom, let me know because i'm going to delete all of the others in 2 weeks
21:25:33 <ttx> ec2-id-compatibilty is targeted to folsom-1 and has no assignee ?
21:25:40 <vishy> ttx: does that seem reasonable
21:25:49 <vishy> ttx: there are a bunch with no assignee
21:26:06 <vishy> ttx: I din't man to target a milestone though
21:26:11 <vishy> * mean
21:26:13 <ttx> vishy: by "deleting" you mean obsoleting ?
21:26:17 <vishy> ttx: yes
21:26:34 <ttx> vishy: oh, hellyes
21:26:40 <vishy> there are just a whole bunch of random blueprints that are good ideas but have no one to work on them
21:27:01 <vishy> and a bunch that are just old and I have no idea about
21:27:30 <vishy> ttx: I haven't prioritized the ones in there yet so a lot are still undefined
21:27:42 <heckj> vishy: burn them all to the ground and start again :-) Worked for me
21:27:42 <vishy> ttx: i was going to do a prioritization after I got them all targetted to folsom
21:27:58 <ttx> vishy: sounds good. Try to prioritize the folsom-1 by next week
21:28:14 <vishy> ok i will do one more pass through all of them, then I will send out an email notifying about pending deletion
21:28:15 <ttx> the rest is not that urgent
21:28:25 <ttx> vishy: Anything else ?
21:29:17 <vishy> nope
21:29:28 * vishy sharpens his email pen
21:29:33 <cloudfly> it's possible some of the existing side projects satisfy blue prints
21:29:48 <vishy> cloudfly: ?
21:29:58 <cloudfly> admin-cli vs unified-cli for instance
21:30:19 <vishy> cloudfly: possibly, I've been attempting to obsolete those
21:30:43 <vishy> cloudfly: if you notice any that you feel should be obsoleted, feel free to let me know
21:30:49 <vishy> cloudfly: I can use help
21:30:54 <cloudfly> will do
21:31:14 <vishy> actually that is true for anyone, if anyone notices blueprints that should be removed, let me know :)
21:31:25 <ttx> Other questions on Nova ?
21:31:59 <ttx> #topic Horizon status
21:32:04 <ttx> devcamcar: o/
21:32:12 <devcamcar> o/
21:32:33 <ttx> #link https://blueprints.launchpad.net/horizon/folsom
21:32:35 <ttx> Looks good...
21:32:44 <devcamcar> most of whats there is only what we've targeted for folsom-1
21:32:57 <ttx> devcamcar: there are two blueprints targeted to folsom-1 that don't have series goal = Folsom:
21:32:58 <devcamcar> still have a lot of blueprints to add from the summit which hopefully i can get to this week
21:33:02 <devcamcar> oops, which?
21:33:02 <ttx> https://blueprints.launchpad.net/horizon/+spec/scaffolding
21:33:03 <devcamcar> i'll fix
21:33:05 <ttx> https://blueprints.launchpad.net/horizon/+spec/transition-to-lesscss
21:33:19 <ttx> I was about to set them but thought you might want to confirm
21:33:50 <ttx> (series targeting is limited to drivers, while milestone-targeting is open to everyone, so people may add stuff that you don't agree with
21:34:00 <devcamcar> hm, they both say proposed for folsom
21:34:15 <devcamcar> oh i see
21:34:15 <devcamcar> nm
21:34:17 <devcamcar> fixed :)
21:34:33 <ttx> devcamcar: soon you'll become a Jedi master
21:34:35 <devcamcar> but yes, F1 is looking good for us
21:34:36 <devcamcar> ttx: hah
21:34:43 <devcamcar> F2 and on are mostly undefined right now
21:35:14 <devcamcar> i also have a list of tickets we'll be back porting to stable/essex
21:35:21 <gabrielhurley> devcamcar: maybe we won't be adding features until the last second this release ;-)
21:35:32 <devcamcar> https://bugs.launchpad.net/horizon/+bugs?field.tag=essex-backport-potential
21:35:43 <devcamcar> mostly trivial fixes
21:35:53 <ttx> devcamcar: you can use series targeting there too
21:36:00 <devcamcar> ok
21:36:08 <ttx> "Target to series" and select "Essex"
21:36:24 <ttx> then it shows on https://bugs.launchpad.net/horizon/essex
21:36:29 <devcamcar> ahh perfect
21:36:33 <ttx> and we can track completion
21:36:48 <devcamcar> i'll update those now as well
21:36:59 * ttx still needs to fix the bugstatus-updating gerrit hook so that it understands the series, but otherwise it's pretty functional
21:37:11 <devcamcar> yep, i had marked a few as fix released by mistake
21:37:35 <ttx> for some reason I thought that the weeks after the design summit would be pretty calm for me
21:37:46 <ttx> devcamcar: Anything else ?
21:37:51 <devcamcar> ttx: that is all!
21:37:58 <ttx> Questions for Horizon ?
21:38:18 <ttx> #topic Other Team reports
21:38:25 <ttx> annegentle, jaypipes, mtaylor: ?
21:38:40 <ttx> Or any other team lead with a status report ?
21:38:50 <annegentle> me!
21:38:58 <ttx> hey, you made it :)
21:39:06 <annegentle> Working on a branch that switches all links to /essex for the docs.
21:39:09 <annegentle> yup just!
21:39:27 <annegentle> so I can release docs.openstack.org/essex today and open doc comments on all those pages
21:39:50 <annegentle> also going to eliminate the /bexar and /cactus "sites" by doing 301 redirects to /trunk
21:39:58 <ttx> ok
21:40:10 <annegentle> then I'll get cracking on a blueprint or two.
21:40:47 <ttx> annegentle: we should open a "folsom" series for openstack-manuals
21:41:03 <ttx> annegentle: so that you can target your blueprints to the series, at least
21:41:15 <annegentle> that would be great.
21:41:28 <ttx> willdo that for you
21:41:32 <annegentle> also you may have seen on the mailing list a post for an intern, needs to be a full time student and it is the Austin location of Rackspace. Approximately May to August.
21:42:45 <ttx> saw that. Great opportunity :)
21:42:50 <ttx> annegentle: anything else ?
21:42:59 <annegentle> also the docs site now has all nova.conf flags listed at http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html and another writer is working on a list of all swift flags
21:43:12 <annegentle> and _that_ is all for this week.
21:43:30 * oubiwann high-fives annegentle
21:43:52 <ttx> #topic Open discussion
21:43:56 <ttx> Anything else, anyone ?
21:44:48 <jog0> are we still planning on trying a shorter folsom release cycle?
21:44:54 <ttx> I'll be at UDS in Oakland next week, maybe speaking
21:45:05 <ttx> jog0: the release cycle will be 6 months
21:45:37 <jog0> so folsom-1 will not have an associated 2 week code freeze?
21:45:50 <ttx> jog0: we /might/ consider late Folsom milestones as full releases, but it's pretty unlikely
21:45:59 <ttx> no it won't
21:46:02 <jog0> ttx: thanks
21:46:15 <ttx> folsom-1 will be cut on the Tuesday and delivered on the Thursday.
21:46:20 <ttx> May 22-24
21:47:12 <ttx> ok then, if nobody has anything, we'll close early
21:47:43 <ttx> #endmeeting