21:01:23 <ttx> #startmeeting
21:01:24 <openstack> Meeting started Tue Mar 27 21:01:23 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic.
21:01:33 <ttx> Today's agenda: http://wiki.openstack.org/Meetings/ProjectMeeting
21:01:42 <ttx> #topic Keystone status
21:01:47 <ttx> heckj: o/
21:01:51 <heckj> RC1 cut! Yeah!!!
21:02:01 <ttx> yes, and no RC2 planned yet
21:02:07 <ttx> #link https://bugs.launchpad.net/keystone/+bugs?field.tag=essex-rc-potential
21:02:18 <ttx> 11 bugs on the essex-rc-potential list
21:02:23 <heckj> No RC2 focused, although some bugs that were tagged essex-potential may be backported into milestone-proposed before the cut
21:02:32 <heckj> ttx: yep
21:02:34 <dolphm> i'd like to see that happen
21:02:38 <ttx> heckj: so nothing in there that warrants a respin at this point ?
21:02:52 <ttx> soren: could you confirm bug 960977 is invalid (see comment before last) ?
21:02:53 <uvirtbot> Launchpad bug 960977 in keystone "Can't create user" [Medium,Incomplete] https://launchpad.net/bugs/960977
21:03:06 <heckj> dolphm +1 - especially the swifth auth pieces
21:03:42 <ttx> Anyone has a Keystone issue they think should be fixed in Essex ?
21:03:44 <heckj> So call for #help - please test, please use it - and help point out places where docs need to be updated
21:03:49 <dolphm> and i'd like to see a solution for bug 963056 land in essex (just a big UX issue)
21:03:49 <uvirtbot> Launchpad bug 963056 in keystone "Object references not validated (returning 500 instead of 404)" [Medium,In progress] https://launchpad.net/bugs/963056
21:03:55 <soren> ttx: No.
21:04:19 <soren> ttx: Someone with a clue about keystone should. I have no way to tell if gongysh is correct.
21:04:37 <ttx> heckj, dolphm ^
21:04:49 <soren> Something's definitely up. user-create has a --tenant_id option. What's it for, if not for this?
21:05:21 <annegentle> heckj: I see there are API doc updates, do you think the API doc is in good shape now?
21:05:35 <dolphm> i'll follow up on bug 960977
21:05:35 <uvirtbot> Launchpad bug 960977 in keystone "Can't create user" [Medium,Incomplete] https://launchpad.net/bugs/960977
21:05:43 <soren> dolphm: Wicked, thanks
21:05:44 <heckj> annegentle: I haven't read through them thorough to know yet
21:05:57 <heckj> thanks dolphm!
21:06:03 <ttx> heckj: note that we'll need an RC2 if you want to include more fixes before the final cut. The "final cut" is actually just a promotion (take RCx and make it the release).
21:06:30 <ttx> heckj: So what are your plans ? Keep RC1 unless something critical is discovered ? Or do an RC2 later this week ?
21:06:40 <heckj> ttx: so the process to get those tagged ones in to to make another RC and then target those bugs to RC2 and backport those?
21:06:41 <dolphm> ttx: can rc2 happen whenever we want?
21:07:11 <heckj> ttx: I'm rather looking to you for process here - what's the right way to do this to land some additional fixes in before the release
21:07:12 <ttx> dolphm: yes
21:07:33 <ttx> heckj: so fixes must land in master (Folsom) first, for the usual review.
21:07:45 <ttx> heckj: then at some point we open an RC2 list and target bugs to it
21:07:57 <ttx> heckj: those bugs in the RC2 list get backported to milestone-proposed
21:08:14 <ttx> heckj: and RC2 is published from milestone-proposed when you tell me it's ready
21:08:18 <heckj> Okay - I'll open RC2 now then so we can start targetting to get them in
21:08:26 <ttx> heckj: ok
21:08:26 <dolphm> cool
21:09:10 <ttx> Ideally RC2 should contain everything you want in the final release... and only do a respin if something very unexpected hits us
21:09:26 <ttx> (in which case we'll do an RC3)
21:09:38 <ttx> heckj: anything else ?
21:09:50 <heckj> nothing from me - rc2 series is created.
21:10:05 <heckj> (dolphm - tag up yer bugs! I'll take a swing through them later today too)
21:10:29 <ttx> heckj: note that bugfixes when they land in master get "FixCommitted" and when they are in milestone-proposed they get "FixReleased" -- that allows tracking where you are
21:10:48 <dolphm> heckj: on it
21:10:53 <heckj> ttx: k
21:11:01 <ttx> heckj: updated milestone name
21:11:08 <ttx> (must match future tag)
21:11:20 <ttx> Questions about Keystone ?
21:12:11 <ttx> #topic Swift status
21:12:12 <annegentle> heckj: do youneed PDF and/or schema links for the API?
21:12:17 <annegentle> rats can't type fast enough :)
21:12:19 <ttx> oops :)
21:12:30 <annegentle> sorry :(
21:12:34 <dolphm> bug 963546 sounds important -- is there a discussion about it somewhere?
21:12:35 <uvirtbot> Launchpad bug 963546 in keystone "swift_auth validates the tenant:user acl incorrectly" [Undecided,In progress] https://launchpad.net/bugs/963546
21:12:40 <heckj> annegentle: If you can easily provide, that would be lovely, thank you!
21:12:57 <heckj> chmouel^^ you around?
21:12:57 <annegentle> heckj: ya, not easy :) so was going to negotiate. we can talk after meeting.
21:13:12 <heckj> notmyname?
21:13:16 <notmyname> I'm here
21:13:28 <ttx> Go Swift!
21:13:32 <ttx> 1.4.8 is out.
21:13:32 <notmyname> just waiting to see if there is mores tuff you need to address for keystone
21:13:42 <notmyname> yes, 1.4.8 is out. it's our essex release
21:13:44 <heckj> You know anything about 963546? - eh, I'll follow up later
21:14:32 <chmouel> heckj: i'll need to double check, but that should not be hard to fix if that's the case
21:14:32 <ttx> notmyname: No showstoppers detected in there ?
21:15:07 <notmyname> nope. bugfixes (and an optional feature contributed from HP)
21:15:14 <notmyname> I think the priority now (for the swift community) is getting stuff for the summit/conference
21:15:35 <ttx> notmyname: ack
21:15:53 <ttx> will mention it again at the end of the meeting
21:16:01 <ttx> notmyname: Anything else you wanted to mention ?
21:16:12 <notmyname> no, I don't think so
21:16:20 <notmyname> I'll have to duck out soon
21:16:21 <ttx> Questions on Swift ?
21:16:27 <notmyname> so I won't be here fro the end of the meeting
21:16:39 <ttx> or any question directed to notmyname ?
21:16:46 <ttx> (before he leaves)
21:17:29 <ttx> apparently not.
21:17:32 <ttx> #topic Glance status
21:17:42 <ttx> bcwaldon: yo
21:17:47 <bcwaldon> hey
21:17:49 <ttx> RC1 is out, RC2 targeting is open
21:17:54 <ttx> #link https://launchpad.net/glance/+milestone/essex-rc2
21:18:03 <bcwaldon> yep, a few bugfixes for that little guy
21:18:05 <ttx> Two bugs in there so far, in good progress
21:18:14 <ttx> 3 other issues have been tagged for consideration:
21:18:14 <bcwaldon> Currently I'm working on triaging blueprints/bugs, getting the fourth draft of the OpenStack Image API v2 spec up for review, and getting python-glanceclient off the ground!
21:18:23 <ttx> #link https://bugs.launchpad.net/glance/+bugs?field.tag=essex-rc-potential
21:18:40 <ttx> bcwaldon: Would you include the two "High" in there in RC2 ?
21:18:53 <ttx> or are they left off for a reason ?
21:18:59 <bcwaldon> ttx: I'll talk to eglynn about the copy_from bug
21:19:12 <bcwaldon> ttx: we can target the second high bug at rc2
21:19:25 <bcwaldon> ttx: last bug doesn't really matter
21:19:30 <ttx> we need the same fix in Nova
21:19:35 <ttx> OK will target the second one
21:19:39 <bcwaldon> thanks
21:19:45 <ttx> Anyone has a Glance issue they think should be fixed in Essex ?
21:20:25 <ttx> I would like to suggest bug 962385
21:20:27 <uvirtbot> Launchpad bug 962385 in glance "S3 & swift secrets leaked into logs" [Medium,Fix committed] https://launchpad.net/bugs/962385
21:20:53 <ttx> bcwaldon: should I add it to essex-rc-potential or directly to RC2 ?
21:20:58 <bcwaldon> rc2
21:21:07 <ttx> ok. I was also wondering about bug 959670 + bug 963050
21:21:09 <uvirtbot> Launchpad bug 959670 in glance "Notification message format is incorrect" [Undecided,Fix committed] https://launchpad.net/bugs/959670
21:21:11 <uvirtbot> Launchpad bug 963050 in glance "Qpid notifier needs content_type set" [Undecided,Fix committed] https://launchpad.net/bugs/963050
21:21:12 <bcwaldon> I'll go over recent commits to make sure I didnt miss anything
21:21:18 <bcwaldon> I guess neither jay nor I have done that yet
21:21:26 <bcwaldon> target them, too
21:21:35 <ttx> bcwaldon: I did that, hence my suggestions. Doesn't mean you shouldn't as well
21:21:44 <ttx> rc2 directly ?
21:21:46 <bcwaldon> ok, will do later this afternoon
21:21:51 <bcwaldon> whatever you think is best :)
21:22:12 <ttx> bah, potential for the time being. I'm not sure I understand the impact of the bug that well
21:22:31 <ttx> bcwaldon: what's the plan ? Would issuing a "final until proven otherwise" RC2 by the end of the week work for you ?
21:22:32 <bcwaldon> ok, I'll review later
21:22:41 <bcwaldon> yep
21:23:22 <ttx> bcwaldon: Anything else ?
21:23:40 <bcwaldon> nope, just wanted to bring the v2 api back up
21:23:49 <bcwaldon> and python-glanceclient
21:23:58 <bcwaldon> which should be in gerrit shortly
21:24:19 <bcwaldon> other than that, I'm done
21:24:24 <ttx> Questions on Glance ?
21:24:32 <soren> Er... yes.
21:24:44 <ttx> soren: go ahead
21:24:51 <soren> How is python-glanceclient different from the glance client included in glance?
21:25:26 <bcwaldon> soren: it's a reimplementation of the client that lives in glance proper to align with the rest of the openstack clients
21:25:32 <bcwaldon> like python-keystoneclient and python-novaclient
21:25:40 <ttx> bcwaldon: for Folsom right ?
21:25:45 <soren> bcwaldon: This is for ...
21:25:48 <soren> Right, what ttx said.
21:25:49 <bcwaldon> folsom
21:25:56 <soren> Ok, carry on, then :)
21:26:04 <bcwaldon> sorry to frighten you, no I'm not trying to rewrite glance client for essex!
21:26:16 <bcwaldon> I think I would be killed If I did that
21:26:26 <ttx> adjusting release deliverables on week-1 is not exactly a gentleman's sport
21:26:39 <ttx> more like cage deathmatch
21:26:53 <ttx> #topic Nova status
21:26:57 <ttx> vishy: hey
21:27:08 <vishy> hi
21:27:10 <ttx> RC1 is out, RC2 targeting is open
21:27:15 <ttx> #link https://launchpad.net/nova/+milestone/essex-rc2
21:27:22 <ttx> Already 17 issues listed, most of them already pushed to milestone-proposed
21:27:40 <ttx> bug 965540 needs to be backported to milestone-proposed
21:27:41 <uvirtbot> Launchpad bug 965540 in nova "nova does not handle glance_exception.Forbidden " [Medium,Fix committed] https://launchpad.net/bugs/965540
21:28:03 <ttx> There are also 13 issues on the essex-rc-potential list
21:28:07 <vishy> on it
21:28:10 <ttx> #link https://bugs.launchpad.net/nova/+bugs?field.tag=essex-rc-potential
21:28:24 <ttx> vishy: I think bug 964824 would be a bit disruptive at this point, untag ?
21:28:25 <uvirtbot> Launchpad bug 964824 in nova "Database tuning required" [Medium,Confirmed] https://launchpad.net/bugs/964824
21:28:43 <justinsb_> ttx: There are some pretty serious DB issues in there
21:29:22 <ttx> justinsb_: I would really like to avoid doing DB migration post RC1
21:29:23 <vishy> justinsb_: we could do a blog post for how to tune the db
21:29:34 <ttx> (if that's what is required)
21:29:36 <vishy> rather than do it in a migration?
21:30:03 <justinsb_> The risk is that someone doesn't apply those patches & then we have to figure out why it's going so slow
21:30:31 <johnpur> we are running into scaling issues that a good tuning effort would aoid
21:30:31 <ttx> ok, we can discuss this on the bug itself
21:30:43 <ttx> it's not targeted yet, just on the list foir consideration
21:30:47 <vishy> justinsb_: lets see what the changes are
21:31:07 <ttx> I have a few suggestions for additions to the essex-rc-potential list:
21:31:20 <ttx> vishy: Two bugs had some commits before RC1 and some commits after:
21:31:28 <ttx> bug 953235 and bug 956366
21:31:32 <uvirtbot> Launchpad bug 953235 in nova "remove old sql api calls" [Wishlist,Fix committed] https://launchpad.net/bugs/953235
21:31:34 <uvirtbot> Launchpad bug 956366 in nova "self-referential security groups can not be deleted" [High,Fix committed] https://launchpad.net/bugs/956366
21:31:42 <ttx> so they are half in Essex, which is unconvenient
21:32:05 <ttx> I guess we should have the last part of the bugfixes pushed to RC2 ?
21:32:14 <vishy> the second one is just a test addition so that is no problem
21:32:21 <ttx> ok
21:32:31 <vishy> they both seem fine
21:32:34 <vishy> i will add them
21:33:15 <ttx> Any other bug or post-RC1 fix that should be considered for Essex release ?
21:33:32 <vishy> not that i am aware of yet
21:33:35 <devcamcar> seems like 964824 should be split up into a number of smaller issues
21:33:37 <vishy> but i may have missed something
21:33:53 <vishy> ttx: the one about connecting to mysql seems really important
21:33:58 <vishy> but i don't know if anyone is working on it
21:34:17 <vishy> we may have to port the session and reconnect code from glance to fix it
21:34:22 <ttx> Adam is working on the Glance fix, maybe the Nova fix will be relatively similar
21:34:47 <ttx> we'll see if Adam can do both
21:35:02 <justinsb_> devcamcar: I didn't want to send the bug count through the roof :-)
21:35:17 <ttx> vishy: How does publishing a "final until proven otherwise" RC2 on Thursday or Friday sound ?
21:35:25 <ttx> justinsb_: the prize for bug 1000000 is still up
21:35:51 <devcamcar> ttx: no schema changes post RC1 - is this a formal policy or "we'd rather not"
21:36:00 <justinsb_> ttx: You got me.  I'm holding them back until 9,999,950...
21:36:34 <ttx> devcamcar: we'd rather not
21:36:49 <ttx> devcamcar: those proved very regression-prone in the past
21:37:01 <devcamcar> reason i ask is because justinsb_'s bug has some pretty big fixes proposed
21:37:03 <vishy> sounds good
21:37:09 <justinsb_> ttx: If it's just adding an index though?  Better to change the code or add an index?
21:37:37 <ttx> devcamcar: I wonder why thos critical performance issues were only detected one week before release, so I question how critical they are
21:38:41 <ttx> justinsb_: in previous releases, we broke some database support by adding innocent-looking migrations a few days before final
21:38:49 <justinsb_> The MyISAM -> InnoDB needs to happen, I think though.
21:38:56 <ttx> "oops, no more postgres"
21:39:19 <justinsb_> Well, we can discuss on the bug, I guess!
21:39:25 <ttx> If we want to risk that, I want the fix to be worth that risk.
21:39:35 <ttx> indeed.
21:39:38 <jog0> ttx: IMHO the issues were detected just before release due to larger scale Essex testing of RC1?
21:40:28 <ttx> all in all it's about benefit of fix vs. risk of regression. And as we move closer to release, the benefit has to be extra-high and the risk extra low.
21:40:44 <ttx> vishy: Anything else ?
21:40:58 <vishy> nope
21:41:04 <ttx> Other questions on Nova ?
21:41:37 <ttx> #topic Horizon status
21:41:43 <ttx> devcamcar: o/
21:41:45 <devcamcar> o/
21:41:49 <ttx> RC1 is out, RC2 targeting is open
21:41:54 <ttx> #link https://launchpad.net/horizon/+milestone/essex-rc2
21:42:03 <ttx> with 49 bugs already on it :)
21:42:10 <devcamcar> generally we are looking good.  we went from a number of larger issues in rc1 to essentially just polishing in rc2
21:42:15 <ttx> Looks like you have a good handle on those...
21:42:22 <devcamcar> yes, rc2 is moving well
21:42:26 <ttx> No issue proposed on https://bugs.launchpad.net/horizon/+bugs?field.tag=essex-rc-potential
21:42:27 <devcamcar> we expect rc2 to be final
21:42:33 <ttx> So I suppose you caught them all in RC2
21:42:40 <mdrnstm> devcamcar: awesome news!
21:42:50 <devcamcar> ttx: yes, all essex-rc-potential's have been targeted to rc2 or released in rc1
21:42:59 <ttx> devcamcar: so only release-critical fixes should warrant a respin after it ?
21:43:06 <devcamcar> ttx: yes
21:43:10 <ttx> works for me
21:43:20 <devcamcar> as a community we've been opening tickets for all the rough edges and fixing
21:43:43 <ttx> devcamcar: ETA for RC2 ? by the end of the week ?
21:43:43 <justinsb_> Any thoughts on bug #960656 ?  Looks like I forgot to propose for Essex
21:43:44 <uvirtbot> Launchpad bug 960656 in horizon "local_settings.py makes horizon difficult to package" [Medium,Confirmed] https://launchpad.net/bugs/960656
21:44:10 <gabrielhurley> justinsb_: we should chat about that offline
21:44:10 <devcamcar> ttx: i'm hoping we can drop by Friday
21:44:18 <ttx> devcamcar: awesome
21:44:19 <devcamcar> ttx: progress has been good
21:44:20 <justinsb_> gabrielhurley: Cool!
21:44:34 <ttx> devcamcar: Anything else ?
21:45:01 <devcamcar> justinsb_: that's primarily just a deployment issue and is somewhat easy to deal with - wouldn't consider it a release blocker
21:45:14 <devcamcar> may just need some better docs around it
21:45:30 <devcamcar> ttx: that's it from my point of view
21:45:35 <ttx> Other questions for Horizon ?
21:46:52 <ttx> #topic Incubated projects and other Team reports
21:47:01 <ttx> danwent: around ?
21:47:03 <danwent> yup
21:47:05 <danwent> https://bugs.launchpad.net/quantum/+bugs?field.tag=essex-rc-potential
21:47:12 <ttx> no RC2 planned yet ?
21:47:12 <danwent> we have just a few RC issues so far
21:47:22 <danwent> two are in review
21:47:30 <danwent> the 'missing files' issues should be easy fixes.
21:47:40 <danwent> can definitely have an RC2 by later this week.
21:47:49 <ttx> danwent: you need to, right ?
21:48:00 <danwent> was hoping to get testing on Ubuntu done before cutting RC2, but we're still working through some issues.
21:48:08 <danwent> ttx: yes
21:48:40 <ttx> we can wait a bit. You're not stuck to the common release date, so we can have more risky behavior
21:48:45 <ttx> yay non-core-yet.
21:48:57 <ttx> so if you want to do RC2 early next week...
21:49:00 <danwent> yes, but i'm pretty conservative :)
21:49:05 <danwent> ok, we'll play it by ear
21:49:17 <ttx> troytoman: around ?
21:49:30 <troytoman> yes
21:49:34 <ttx> Melange RC1 is out, RC2 planned with two bugs targeted so far...
21:49:37 <troytoman> we found two issues that have been resolved
21:49:48 <troytoman> so we should be ready for RC2 to get cut now
21:50:03 <ttx> troytoman: let's wait a bit just in case Murphy finds another one
21:50:15 <troytoman> fair enough
21:50:20 <ttx> I can cut RC2 on Thursday is things stay the same
21:50:29 <troytoman> ttx: sounds like a good plan
21:50:49 <ttx> Any other team lead with a status report ?
21:50:52 <ttx> annegentle: ?
21:51:17 <annegentle> plenty of doc reviews in the queue, please join in the fun: https://review.openstack.org/#q,status:open+project:openstack/openstack-manuals,n,z
21:51:58 <annegentle> I'd like to poll the mailing list too to see how the perceptions of doc readiness is. The doc bug list is still long, but the updates are many.
21:52:41 <ttx> annegentle: trying to scan post-RC1 changes to avoid things that impact the doc, like new flags
21:53:01 <ttx> but the backlog is pretty significant :)
21:53:08 <annegentle> ttx: thanks for that. Also would like input on the Release Notes
21:53:11 <annegentle> #link http://wiki.openstack.org/ReleaseNotes/Essex
21:53:22 <ttx> Good point.
21:53:36 <ttx> I added a section on distros, so packagers are welcome to brag about their work.
21:54:23 <ttx> annegentle: Post-RC2 I expect people to update their section of the release notes
21:54:31 <ttx> annegentle: anything else ?
21:55:08 <annegentle> ttx: so did you find new flags?
21:55:39 <ttx> no, but some bugs in the list would create some, and I think they should be folsom
21:55:46 <annegentle> ttx: ok, thanks. Nothing more.
21:55:59 <ttx> like https://bugs.launchpad.net/nova/+bug/831704
21:56:00 <uvirtbot> Launchpad bug 831704 in nova "No validation of arch type on image upload" [Low,Confirmed]
21:56:14 <ttx> #topic Open discussion
21:56:28 <ttx> #info People participating to the Folsom Design Summit in three weeks should file their session topics ASAP, ideally before the end of the week.
21:56:34 <ttx> #link http://summit.openstack.org
21:56:45 <ttx> Looks like we'll merge 'Nova networking' and 'Quantum' tracks
21:57:03 <annegentle> Would like to suggest some hands-on workshops in the Ecosystem track as well, they were requested at the last summit. Please propose!
21:57:41 <ttx> annegentle: the Ecosystem track will "inherit" a number of talks that can't fit in the (more time-limited) session tracks
21:57:48 <annegentle> ttx: that works
21:57:59 <ttx> most tracks already have more proposed than they can fit
21:58:18 <ttx> Anything else, anyone ?
21:59:13 <ttx> ok then
21:59:14 <ttx> #endmeeting