/srv/irclogs.ubuntu.com/2008/06/19/#launchpad-meeting.txt

=== thumper_laptop is now known as thumper
=== mwhudson_ is now known as mwhudson
=== thumper_laptop is now known as thumper
=== mrevell is now known as mrevell-lunch
=== mrevell-lunch is now known as mrevell
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== mwhudson__ is now known as mwhudson
salgadome19:00
abentleyme19:00
thumperme19:00
bigjoolsmoo19:00
flacostechair is late19:01
mwhudsonme19:01
stubme19:01
flacosteroll call hasn't started yet19:01
gmbRincheeeeeeeeeeeeeeeeeen....19:01
mptRinchen's on holiday19:01
sinzu1All is moot without mootbot19:01
mptall this week19:01
marsRinchen's off in the wilderness somewhere...19:01
gmbAh, so it's kiko's show is it?19:01
backiiiiiiiiiiko19:01
=== sinzu1 is now known as sinzui
gmbAnd he's not even in the room19:01
flacostestub: did you get my email about the api-acl-db DB patch?19:01
matsubarakiko's on the phone19:01
flacostestub: i'd like you to land it unless there is good reason not to do it19:02
* stub has a look19:02
mpt#startmeeting19:03
MootBotMeeting started at 13:06. The chair is mpt.19:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:03
mptnono, the chair is kiko19:03
kikompt, can you help be chair? I'm still on the phone19:03
gmbpwned.19:03
mptok, MEETING TIME19:03
mthaddonme19:03
mptWho is here today?19:03
matsubarame19:03
allenapme19:03
schwukme19:03
sinzuime19:03
mrevellme19:04
flacosteme19:04
stubme19:04
gmbme19:04
kikoem19:04
intellectronicame19:04
bacme19:04
EdwinGrubbsme19:04
marsme19:04
bigjoolsme19:04
statikme19:04
adeuringme19:04
salgadome19:04
leonardrme19:04
mptme19:04
thumperme19:04
mwhudsonme19:04
abentleyme19:04
thumperrockstar: ?19:05
mptTeam leads, please ensure all your team members who should be here are19:05
mptThat, by the way, was19:05
mpt[TOPIC] Roll call19:05
MootBotNew Topic:  Roll call19:05
mptAnd now it's time for19:05
mpt[TOPIC] Agenda19:05
MootBotNew Topic:  Agenda19:05
bigjoolscprov ping19:05
mpt * Next meeting19:06
mpt * Actions from last meeting19:06
mpt * Oops report (Matsubara)19:06
mpt * Critical Bugs (Rinchen)19:06
mpt * Bug tags19:06
mpt * Operations report (mthaddon/herb)19:06
mpt * DBA report (stub)19:06
mpt * Sysadmin requests (Rinchen)19:06
mpt * New packages required (salgado)19:06
mpt * A top user-affecting issue (mrevell)19:06
mpt * Doc Team report (mrevell)19:06
herbme19:06
al-maisanme19:06
cprovme19:06
mptIf anyone has other items, please /msg me19:06
barryme19:06
mpt[TOPIC] Next meeting19:06
MootBotNew Topic:  Next meeting19:06
mptIf anyone knows of any reason why the next meeting should not be same time, same channel, let them speak now, or forever hold their peace19:07
mptIs there anyone who won't be here?19:07
kikoI will be :)19:07
mptA resounding silence, that's good19:07
mptok19:07
mpt[TOPIC] Actions from last meeting19:07
MootBotNew Topic:  Actions from last meeting19:07
mpt *  Joey to ping Salgado about documenting package dependency policy19:08
salgadonot done19:08
mpt[TOPIC] Oops report19:08
MootBotNew Topic:  Oops report19:08
matsubaraToday's oops report is about bugs 24135519:09
ubottuLaunchpad bug 241355 in launchpad-bazaar "OOPS requesting cvs code import using the new code import interface" [Undecided,New] https://launchpad.net/bugs/24135519:09
matsubarathumper, can you assign and schedule 241355?19:09
thumperok19:09
matsubarathumper: thanks19:09
matsubarampt: that's it for the oops report.19:09
mptthanks matsubara19:09
mpt[TOPIC] Critical Bugs19:10
MootBotNew Topic:  Critical Bugs19:10
matsubaraNo critical bugs open.19:10
mptexcellent19:10
matsubarathat's it for critical bugs :-)19:10
mpt[TOPIC] Bug tags19:10
MootBotNew Topic:  Bug tags19:10
mptThere is one proposed tag19:10
matsubarawe have package-diff as a proposed tag19:10
bigjoolsthat was last week19:10
kikoand we approved it :)19:10
matsubarayes, was that accepted or moved to this one?19:11
mptok19:11
cprov:)19:11
bigjoolscprov, did you want to raise another one for p3a?19:11
matsubaraok19:11
mptIt was approved19:11
cprovbigjools: yes, probably, but I will propose it next week19:11
mptmatsubara, can you take care of moving it to the Approved section?19:11
matsubarampt: yep19:11
mptthanks19:11
mpt[TOPIC] Operations report19:12
MootBotNew Topic:  Operations report19:12
mptmthaddon or herb?19:12
herbFriday (2008-06-13) - Librarian seemed to have problems which caused a knock-on effect on app servers. Caused about 10 minutes of downtime. Tom might have more in the way of details.19:12
herbWednesday (2008-06-18) - Upgraded a bunch of servers to hardy. Took about 4 hours of planned downtime to do so.19:12
herbThere are 2 cherry picks (r6410 and r6451) awaiting approval that, I'm assuming, won't be approved prior to the rollout.19:12
herbThe only remaining hosts to be updated to hardy are the Soyuz machines. They are scheduled for tonight.19:12
herbThe Debian import machine is up and configured. Celso and I have been working through remaining issues and are making good progress.19:12
herbBug #224623 is still hanging around. We haven't seen the problem crop up again and I know Stuart has been very busy with the 8.3 upgrades. If there is anything we can do to help, Tom and I are happy to do so.19:12
ubottuherb: Bug 224623 on http://launchpad.net/bugs/224623 is private19:12
herbThat's it from Tom and me unless there are any questions.19:12
mptthanks herb19:12
stubWhen is bug expiry going to be implemented?19:13
stubThen annoying unreproducible issues will silently die...19:13
mptsinzui, is that something you can answer?19:13
intellectronicawasn't it already implemented, then cancelled?19:13
sinzuimpt: No19:14
flacostempt: sinzui is off the hook fo rthat nor19:14
flacosteit's a bugs team decision19:14
mptBjornT?19:14
stubI'm not that serious...19:14
intellectronicampt: he's not here today19:14
marsBjornT is off today19:14
mptok, we'll move on19:14
mptHe looks here19:14
mpt[TOPIC] DBA report19:14
MootBotNew Topic:  DBA report19:14
stubEverything is running PG 8.3 now. It seems faster. Todays OOPS reports will give us not-a-metric.19:15
stubThe first stage of the Auth/Person split has landed. yay. This opens launchpad/devel up for db changes so land 'em if I haven't done it for you.19:15
stubAll the db patches I'm aware of have been reviewed for this cycle.19:15
stubWe need to work out where staging and demo are going to live. Demo needs to go first as I will use staging for testing replication and there just isn't enough disk atm for everything.19:15
stubAfter we have worked out and tested how this replication stuff is going to be glued together I'd like the launchpaddb master and authdb replica running on hackberry and the authdbmaster and launchpaddb replica running on chokecherry.19:15
mthaddonstub, if we drop launchpad_demo from 8.2 on chokecherry, would that give us enough space?19:15
stubI didn't drop it already? Better do that now or the staging restore will likely blow up again...19:16
stubIf it fits, it will be very tight.19:16
mthaddonstub, it did blow up - I dropped launchpad_langpack and it now is okay with restore19:16
mthaddonstub, but I suspect if we drop launchpad_demo as well we'll get some more space again19:17
mthaddonstub, should I just do that now?19:17
rockstarme19:17
stubSo we might be fine for testing.19:17
stubdropping it now19:17
mthaddoncool (and session_demo too I presume)19:17
stubIf we run staging and production and demo on chokecherry that will be 4 full copies of the production db (because staging will need to be replicated too).19:18
mthaddonstub, our current staging restore also means creating another db (launchpad_staging_new) and then dropping and renaming if the restore works19:19
stubAnd it will be a production server, highly visible if it goes down, so I still vote for demo and staging on different hardware.19:19
stubOk. 5 full copies.19:19
mthaddonstub, would definitely be better, just don't know if we have other hardware anywhere near the same class19:19
mptOk, anything more from the DB department?19:20
stubI don't think we need it in the same class personally - I'd prefer staging to be underpowered compared to production.19:20
stub(If we need production level hardware to cope with one or two users, how can we expect production to cope?)19:21
mthaddonstub, tough one that, as ideally we want to be able to see how performance compares on similar hardware, but load is different, so....19:21
stubmpt: next...19:22
mptthanks stub19:22
mpt[TOPIC] Sysadmin requests19:22
MootBotNew Topic:  Sysadmin requests19:22
mptmatsubara is filling in for Rinchen19:22
matsubaraAny outstanding RT requests? I'll send those out to Joey and he'll follow up19:22
matsubaraon Monday. If there's anything that can't wait until Monday, I'll follow up19:22
matsubarawith elmo.19:22
bigjoolsThe Soyuz team has RT 3101619:23
cprovkees and ubuntu-security team need access to http://private-ppa.buildd19:23
mptI'd like to express my appreciation for RT 27357 being closed after 15 months :-)19:23
matsubaracprov, bigjools I'll ask elmo to take a look. how important is it?19:24
bigjoolsmatsubara: very19:24
bigjoolsthank you19:24
matsubaranp19:24
mptthanks again matsubara19:25
mpt[TOPIC] New packages required19:25
MootBotNew Topic:  New packages required19:25
salgadoanything for launchpad-dependencies this week?19:25
kikowell19:26
kikoyes19:26
kikoflacoste has a profiling package we want19:26
kikooh, no, that goes to sourcecode/.19:26
kikosorry.19:26
flacostekiko: no, it's in sourcecode19:26
abentleyI encountered some issues because TG isn't a dependency.19:26
kikoabentley, TG?19:26
abentleyTurboGears19:26
stubbzr-loom might need to be packaged - there are looms in the review queue (salgado)19:26
mwhudsontg won't be a dependency for much longer19:26
flacostesalgado will use export-loom19:26
flacosteas everybody using loom should19:27
flacosteit makes better thread on the mailing list19:27
salgadoyeah, I'll use that19:27
flacosteotherwise all branches look the same19:27
stubyay. sftp really sucks here. need the smart server.19:27
barrythough it would be nice not to have to export, as it's a bit of extra work19:27
flacosteabentley, salgado: i thought there were issues packaing turbo-gears19:27
salgadoflacoste, no, it's already packaged.  there are issues running it, IIRC19:28
flacostebarry: i don't agree, i hate record :-)19:28
salgadoit doesn't run against our sqlobject19:28
barryflacoste: i hate record too!  still if you have 5 thread, you have an issue :)19:28
abentleysalgado: I haven't seen any reports of issues running it.  AFAICT, the sqlobject one is a non-issue.19:28
abentleyIt runs against its own sqlobject just fine.19:29
flacostebarry: i don't understand what is the issue19:29
mwhudsonabentley: is this an issue if i land the loggerhead branch that removes the dependency on turbogears?19:29
salgadoabentley, the issue is whether or not we want our developer dependencies to include sqlobject19:29
emgenthello19:29
abentleysalgado: I think make run_all should not require anything above our developer dependencies.19:30
barryflacoste: i'll explain after the meeting19:30
abentleymwhudson: No, if you land that, it goes away.19:30
mwhudsonlet's do that then19:30
mwhudson(it's very nearly ready)19:30
salgadompt, guess we're finished here19:31
mptthanks salgado19:31
mpt[TOPIC] Storm update19:31
MootBotNew Topic:  Storm update19:31
mptkiko?19:32
jtvHe's on the phone I believe.19:32
mptok, we can leave that for a few minutes19:32
mpt[TOPIC] A top user-affecting issue19:33
MootBotNew Topic:  A top user-affecting issue19:33
mptmrevell!19:33
mrevellhey hey19:33
mrevellRecently, we've had a number of users who have written to the feedback address complaining that they are receiving large numbers of bug related emails. They've subscribed to a project or distro and don't know how to turn it off.19:33
kikoback back. sorry mpt, jtv.19:33
mrevellAlongside the "kill bug mail" button that we're planning, I think we should make it clearer that a structural subscription could result in a great deal of email. I also think we should show structural subs on people bug pages. I've filed bug 241387 to reflect this.19:33
ubottuLaunchpad bug 241387 in malone "Can't view the projects whose bugs I've subscribed to" [Undecided,New] https://launchpad.net/bugs/24138719:33
mrevellAs an aside, we've had no emails to the feedback address or -users complaining about the Hardy upgrade related service interruptions. One person complained about an Internal Server Error but the time he reported doesn't seem to tie up with our recent interruptions.19:33
mrevellthanks mpt19:34
mptthanks mrevell (and I think 241387 might be a duplicate;-)19:34
mrevellmpt: gosh darn it, I did look19:34
mpt[TOPIC] Storm update19:34
MootBotNew Topic:  Storm update19:34
kikomrevell, yeah, it appears they went through very smoothly -- thankfully, too. :)19:34
kikovery good.19:34
kikostorm's been running on staging for the past days, but it's been upgraded today to r6527, which includes perf work which gustavo and niemeyer have been doing19:34
stubDo we want to record metrics of how many bugs a particular structural subscription would generate per day? The average so far? Then we could warn users how much traffic they are going to get.19:35
thumpersome, many, lots19:35
intellectronicastub: i think that's a really cool idea!19:35
kikostub, I actually think these people are subscribing for the wrong reason -- they don't actually know19:35
kikothey are just clicking on buttons and hoping their bugs get fixed19:35
kikoanyway19:35
kikoso staging's running a recent version of storm19:35
kikoI need to ask you to please spend 10 minutes today trying to navigate, modify and check out staging19:36
mptmatsubara, can you report a bug on implementing stub's suggestion?19:36
mptit's a neat idea19:36
kikofrom the oops logs I am still seeing significant non-sql time in many pages19:36
kikofor instance:19:36
kikohttps://devpad.canonical.com/~matsubara/oops.cgi/2008-06-19/S83319:36
kikohttps://devpad.canonical.com/~matsubara/oops.cgi/2008-06-19/S59919:36
kikohttps://devpad.canonical.com/~matsubara/oops.cgi/2008-06-19/S88619:36
kikohttps://devpad.canonical.com/~matsubara/oops.cgi/2008-06-19/S88819:37
kikoit's not happening on every page, thankfully19:37
kikobut those pages will need further investigation. just how much is a question for flacoste, SteveA, niemeyer and me after this very meeting. :)19:37
kikowe will decide together whether to rollout edge or not.19:37
kikoif we do roll out, you'll be notified through email19:38
kikonote also that 1.2.6 remains targeted for Wednesday next week19:38
kikoask me questions now :)19:38
mptkiko, if we do, when will it happen? intellectronica and mars will be wanting to watch to see if the help frame appears like it did at the last edge rollout19:38
intellectronicaindeed19:38
kikompt, later today.19:38
marsok19:39
kikoI know -- I have the same thing on my mind.19:39
mptok19:39
stubThat peoplelist one is a high start - I hope Storm isn't sucking the first 1.9 million people to render the next 50...19:39
kikothe one which concerns me the most is MailingListAPIView19:39
kikoso we'll see19:40
barrykiko: we have an open bug on that one19:40
kikobarry, it's about to be made critical :)19:40
kikomore seriously, let me talk to francis19:40
barrykiko: yay!19:40
kikookay.19:41
kikolet me steal the spotlight for another announcement.19:41
mpt[TOPIC] Another announcement19:41
MootBotNew Topic:  Another announcement19:41
flacostekiko: that one only happens on Staging iirc19:41
kikoI'm running an experimental test service for branches in PQM19:41
flacostekiko: it's not clear why it's only a problem on staging though19:41
kikoflacoste, I still want it fixed :-/19:41
kikothis experimental service does the following:19:41
kiko- merges all branches in the PQM queue19:41
kiko- reports conflicts19:41
kiko- runs tests19:41
jtvYay!19:42
kikolook at the topic in #launchpad-code for the URL19:42
salgadodoes it revert the merges which caused conflicts?19:42
thumperkiko: so if it is good, you could clear the pqm queue :)19:42
kikoyes19:42
kikothumper, indeed :)19:42
mptnifty19:42
kikothumper, however, I haven't managed to get the tests to pass :)19:42
salgadojust like pqm19:42
kikosalgado, yeah, it does -- it has to :)19:42
stubThe trick will be inserting a branch containing the merged branches into the front of the pqm queue19:43
kikostub, when tests pass, yes19:43
kikoanyway19:43
kikoif you have a branch in PQM19:43
kikowatch that URL19:43
flacostekiko: that kind of lose al commits messages19:43
flacostebut saves us processing time19:43
mptand could make it harder to back out changes19:44
kikoflacoste, I commit the individual logs with the commit messages.19:44
flacosteand that too19:44
stubYou might want something dumber in reality - pick three random branches from the queue, merge, run tests, if pass stick an integration branch to the front of the queue.19:44
intellectronicaflacoste: they can comitted separately19:44
thumperkiko: you should get it to not stop on the first failure19:44
stubRather than the entire queue, which will be more likely to fail when we need it most.19:44
kikompt, flacoste: well, we DO use a revision control system.. :)19:44
matsubarastub, mpt: https://bugs.edge.launchpad.net/malone/+bug/241398 did I get it right?19:44
ubottuLaunchpad bug 241398 in malone "Record metrics on how many notifications a structural subscription will generate." [Undecided,New]19:44
kikoright now, it looks like al-maisan's branch is still failing in PQM :)19:44
al-maisanWhoops19:45
kiko    testDelayedBinaryUpload (canonical.archiveuploader.ftests.test_buildduploads.TestBuilddUploads)19:45
mptmatsubara, pretty much19:45
kikoetc.19:45
mptok19:45
mptAnything more kiko?19:45
kikono, that's it from me.19:45
mptthanks19:45
mpt[TOPIC] Doc Team report19:45
MootBotNew Topic:  Doc Team report19:45
mrevellhi19:45
intellectronicamatsubara: that should probably be on launchpad itself, rather than malone, because structural subscriptions are nt (in the long run) a malone-only feature19:46
mrevellJust a quick one: I've sent a new translations section of the user guide to the team list for review. I'd really appreciate your review of it. Thanks mpt.19:46
mptthanks mrevell19:46
mptAnd now, as the Storm of indecision rolls in over the streetscape of #launchpad-meeting19:46
mptAnd the Janitor of time sweeps away the dust of our agenda19:46
mptIt's time to bring this week's meeting to a close.19:46
mrevellmpt: heh :)19:47
mpt#endmeeting19:47
MootBotMeeting finished at 13:49.19:47
intellectronicathanks mpt19:47
mptThanks everyone19:47
mrevellnicely done mpt and I love the tribute to Humphry Littleton at the end there :)19:47
jtvMootBot: what timezone are _you_ in?19:47
kikoheh19:47
kikompt, thanks so much for saving my bacon :)19:47
intellectronicatz -4219:47
mptmatsubara, so the actual problem is "People don't realize how much mail a structural subscription will send them"19:49
mptthat wouldn't be solved just by recording the average messages/month19:49
mptit would be solved by recording it *and* presenting it on the page for subscribing19:49
mptan alternative (though highly unlikely) way of fixing the problem would be to get rid of structural subscriptions19:50
mptthere might be other ways of fixing the problem that we haven't thought of19:50
matsubararight, I'll update the description.19:50
mptReporting it as a problem (and suggesting possible ways to solve it) makes it less likely to end up marked Invalid :-)19:51
=== salgado is now known as salgado-brb
=== spiv_ is now known as spiv
=== _thumper_ is now known as thumper

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!