[15:00] <danilos> me
[15:00] <bigjools> bonjour
[15:00] <matsubara_> oops, I'm late
[15:00] <matsubara_> :D
[15:00] <danilos> just in time
[15:00] <matsubara_> #startmeeting
[15:00] <MootBot> Meeting started at 09:00. The chair is matsubara_.
[15:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:00] <matsubara_> so, welcome to this week's production meeting
[15:00] <matsubara_> who's here today?
[15:00] <mrevell> me
[15:00] <rockstar> me
[15:00] <sinzui> me
[15:00] <intellectronica> me
[15:01] <danilos> me
[15:01] <flacoste> me
[15:01] <bigjools> me
[15:02] <Ursinha> me
[15:02] <matsubara_> herb: ?
[15:02] <herb> me
[15:02] <matsubara_> ok everyone here but stub. I've pinged him already. let's move on and stub can catch up later
[15:02] <matsubara_> [TOPIC] Agenda
[15:02] <matsubara_>  * Next meeting
[15:02] <matsubara_>  * Actions from last meeting
[15:02] <matsubara_>  * Oops report & Critical Bugs
[15:02] <matsubara_>  * Operations report (mthaddon/herb/spm)
[15:02] <matsubara_>  * DBA report (DBA contact)
[15:02] <MootBot> New Topic:  Agenda
[15:02] <matsubara_> [topic] next meeting
[15:03] <MootBot> New Topic:  next meeting
[15:03] <matsubara_> so, same time next week?
[15:03] <intellectronica> i won't be here next week. i'm on holiday
[15:03] <matsubara_> intellectronica: can you arrange with someone from your team to send a qa contact?
[15:03] <intellectronica> matsubara_: sure
[15:03] <danilos> same time next week is just fine
[15:03] <matsubara_> [action] add intellectronica to apologies on MeetingAgenda.
[15:03] <MootBot> ACTION received:  add intellectronica to apologies on MeetingAgenda.
[15:04] <matsubara_> all right then, same time next week.
[15:04] <matsubara_> [topic] actions from last meeting
[15:04] <MootBot> New Topic:  actions from last meeting
[15:04] <matsubara_> no actions from last meeting.
[15:04] <matsubara_> there were a couple of old ones which i cleaned up
[15:04] <matsubara_> [topic] oops report & critical bugs
[15:04] <MootBot> New Topic:  oops report & critical bugs
[15:04] <Ursinha> okay
[15:04] <matsubara_> Ursinha: please take the stage
[15:05] <Ursinha> it will be fast
[15:05] <Ursinha> have one oops, want to know if someone of bugs (which I presume to be the owner) knows about that
[15:05] <Ursinha> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1047S138
[15:05]  * intellectronica looking
[15:05] <Ursinha> intellectronica, thanks
[15:05] <matsubara_> hmm that's probably abel's turf
[15:06] <Ursinha> matsubara_, yes
[15:06] <intellectronica> i'll relay that to abel. it's black magic to me, tbh
[15:06] <Ursinha> intellectronica, ok, thanks
[15:06] <Ursinha> may I file a bug about it?
[15:06] <Ursinha> intellectronica, I'll do that and give you the #
[15:06] <matsubara_> should have already :-)
[15:06] <Ursinha> anyway
[15:06] <intellectronica> Ursinha: plesae do
[15:07] <Ursinha> matsubara_, just saw it man :)
[15:07] <Ursinha> all other bugs are being handled, so no need to mention
[15:07] <matsubara_> Ursinha: fair enough
[15:07] <Ursinha> re critical bugs
[15:08] <Ursinha> we have one, triaged
[15:08] <Ursinha> code people
[15:08] <matsubara_> bug 297448
[15:08] <Ursinha> bug 297448
[15:08] <matsubara_> rockstar: any news about that one?
[15:09] <rockstar> matsubara_, there has been discussion about it, but I'm not sure it's being worked.  That makes me question the Critical status.
[15:10] <matsubara_> exactly, can you down the importance to high or find someone to work on it? critical bugs need to be worked on immediately and a IncidentLog reported
[15:10] <rockstar> I think me all know the cause.  I'll bring it up in the meeting tonight, and get it assigned and fixed or downgrade the status
[15:10] <rockstar> :)
[15:10] <matsubara_> great. thanks rockstar!
[15:10] <rockstar> I think we're on the same page about this.  :)
[15:10] <bigjools> bingo
[15:10] <Ursinha> great
[15:10] <matsubara_> great. I think that's all for the oops & critical bugs section
[15:11] <matsubara_> thanks everyone
[15:11] <Ursinha> thanks guys
[15:11] <matsubara_> [topic] * Operations report (mthaddon/herb/spm)
[15:11] <MootBot> New Topic:  * Operations report (mthaddon/herb/spm)
[15:11] <herb> - 2008-11-10: Cherry pick r7246 the app servers and private xmlrpc server to fix bug #288064
[15:11] <herb> - 2008-11-12: Cherry pick r7257 to the scripts server to fix bug #286362
[15:11] <herb> - Bugs #118625 and #156453 continue to be a problem. We again had to restart codebrowse several times this week.
[15:11] <herb> - Bug #239569 became a real problem this week when coupled with some sort of svn issue with the codeimport worker, as was noted in my email to the list. It ended up effectively DoSing the DB. We've put limits in at the DB level to hopefully prevent this in the future, but we should raise the importances of this bug.
[15:11] <herb> - We have a production rollout coming up on 2008-11-19. Have we nailed down the time on that yet?
[15:12] <danilos> hey stub :)
[15:13] <danilos> herb: I suppose time is something you guys decide on with kiko, no?
[15:13] <matsubara_> hey Ursinha, since the cp for bug 288064, did you notice if the timeouts are now sane again?
[15:13] <herb> danilos: We get some input. :) I think it's typically decided a bit higher up the chain of command than the LOSAs
[15:13] <danilos> herb: and I believe it fluctuates a lot with last-minute fixes, no?
[15:13] <Ursinha> matsubara_, yes, they are
[15:13] <danilos> herb: ah, ok
[15:13] <herb> danilos: it does, but it really shouldn't
[15:14] <Ursinha> since it landed to edge it's working ok
[15:14] <danilos> herb: yeah, I see your point
[15:14] <matsubara_> cool thanks Ursinha
[15:14] <danilos> herb: is the date confirmed at least?
[15:14] <matsubara_> herb: mrevell sent an announcement with dates and estimated down time
[15:15] <herb> danilos: My understanding is we're firm on the date.
[15:15] <herb> matsubara_: ok. cool.
[15:15] <mrevell> My understand is that we're not really firm on it
[15:15] <danilos> herb: cool, thanks
[15:15] <herb> matsubara_: I haven't waded through all my email yet this morning.
[15:15] <mrevell> Sorry to be a pain but I think there's still some confusion over it
[15:15] <mrevell> I may yet have to correct my announcement
[15:15] <herb> mrevell: haha
[15:15] <matsubara_> oh
[15:15] <herb> mrevell: ok
[15:15] <mrevell> i've emailed kiko
[15:15] <matsubara_> I guess this can be sorted out outside this meeting anyway.
[15:16] <mrevell> sure
[15:16] <matsubara_> rockstar: any new about the loggerhead bug?
[15:16] <matsubara_> s/new/news/
[15:16] <rockstar> matsubara_, I'm making a note to STRONGLY bring it up again.
[15:16] <rockstar> With mwhudson on holiday, we haven't moved too much.
[15:16] <matsubara_> been critical for some time now. how do we handle critical bugs outside of the main launchpad code?
[15:17] <rockstar> I'll work with beuno and see if we can't get something together.
[15:17] <rockstar> matsubara_, maybe we should bring it in and make it critical with launchpad-bazaar.
[15:17] <rockstar> It's not critical for loggerhead, since they never see it.
[15:18] <herb> rockstar: just to give you some idea, it's the most common cause for nagios alarms for the OSAs.  which means our phones ring at us, which means it really annoys us. doesn't necessarily raise the importance, but definitely adds a story to the problem.
[15:18] <rockstar> In fact, the bzr playground for gnome never sees it.  It's just us that is affected by it.
[15:18] <intellectronica> if it can plausibly be dealt with like a critical, maybe it shouldn't be? there's always a risk of debasing that term
[15:18] <rockstar> herb, I know the false alarm dance.  I'll do what I can to make some noise.
[15:18] <matsubara_> [action] rockstar to work with beuno re: critical loggerhead (bug 156453)
[15:18] <MootBot> ACTION received:  rockstar to work with beuno re: critical loggerhead (bug 156453)
[15:19] <herb> rockstar: thanks
[15:19] <matsubara_> thanks rockstar
[15:19] <matsubara_> anything else herb?
[15:19] <herb> nothing.  thanks
[15:19] <matsubara_> ok thank you herb
[15:19] <matsubara_> moving on
[15:20] <matsubara_> [topic] * DBA report (DBA contact)
[15:20] <MootBot> New Topic:  * DBA report (DBA contact)
[15:20] <stub> All known issues we have had with replication in the staging environment are understood and sorted. I don't see any blockers for switching things on in production this cycle assuming QA doesn't show up anything (in particular, Launchpad APIs).
[15:20] <stub> DB patches are all landed except for the Job control system (in discussion between the bazaar team and Mark I believe), and data migration to take advantage of the ProductRelease -> Milestone linkage. When the data migration is done will depend on the functionality of the code rolled out (no point migrating the data on rollout or mid cycle if there is not code in place to maintain the migrated data correctly).
[15:20] <stub> oot.
[15:21] <matsubara_> thanks stub
[15:21] <matsubara_> stub: was an email sent re: the staging db name change?
[15:22] <stub> Nope.
[15:22] <stub> So the name of the staging db has changed to lpmain_staging and lpmain_staging_slave
[15:22] <matsubara_> really?
[15:22] <matsubara_> isn't launchapd_staging to lpmain_staging only?
[15:23] <matsubara_> stub: can you email the list about that change?
[15:23] <matsubara_> thanks stub
[15:23] <stub> People can query the slave if they want, but they probably don't want
[15:24] <matsubara_> stub: all right
[15:24] <matsubara_> anything else before I close?
[15:24] <stub> Names will change again at some point in the future (I've learnt more now), but the scripts are working fine atm and no gains for messing with it right now.
[15:25] <matsubara_> Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs.
[15:25] <matsubara_> stub: ok. let us know once it changes :-)
[15:25] <rockstar> Thanks matsubara_!
[15:25] <intellectronica> thanks matsubara_
[15:25] <matsubara_> #endmeeting
[15:25] <MootBot> Meeting finished at 09:25.
[15:26] <Ursinha> thanks matsubara_
[15:27] <danilos> thanks all