Ubuntu Wiki

Agenda

• Review ACTION points from previous meeting
  • ttx to coordinate testing for Alpha 2
  • smoser to train someone on the release team on the cloud image release
  • smoser to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades
  • all to keep their specs uptodate with workitems and update their status monday EOB
• Maverick development (jib)
  • Blueprints should be near 50% completion now (jib)
  • Alpha2 subcycle status (ttx)
  • Feature Definition Freeze this week (ttx)

• Weekly Updates & Questions for the QA Team (hggdh)

• Weekly Updates & Questions for the Kernel Team (jjohansen)

  • atop kernel patch

• Weekly Updates & Questions for the Documentation Team (sommer)

  • Sections that need input from the server team
• Papercuts Alpha2 subcycle status (ttx)

• Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)

  • New SRU Tracker (zul)

• Open Discussion
• Announce next meeting date and time
  • Tuesday 2010-06-22 at 1800 UTC - #ubuntu-meeting

Minutes

Review ACTION points from last meeting

* ttx to coordinate testing for Alpha 2 - carry over * smoser to train someone on the release team on the cloud image release - carry over

Maverick development (jib)

Most specs should be around 50% completion right now. If you're off that mark, you may want to review work items and see if any can be postponed or dropped, or ask for some support some are well ahead of that curve so we should have some slack in that area.

ttx confirmed we are going reasonably well, adding that the UEC specs are slightly late but we've been addressing that.

mathiaz has been experimenting with a new format/template for the status section of BP and stated that we should be seeing the output of this in the coming days.

ttx noted that: * UEC testing was rescoped to concentrate on fixing the current issues to get to a stable situation, and engage in training new people. * qa workflow was moved to A3 to give priority to uec-testing. * cloud-init was trimmed down to move prio-3 things as targets of opportunity * cloud-utils first work items were reassigned to clint * uec-ec2-kernel-updates work items were clarified

ttx feels that everyone now has a stable and clear view on what's expected from everyone and that if someone thinks he cannot make it, please raise the red flag !

Feature Definition Freeze this week (ttx)

ttx drew attention to http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html and stated it gives a clear commonly shared view on what's expected.

ttx reminded that Final Definition Freeze is this week, and warned the need to freeze the design on all specs that affect main packages and present those to the release team .

Weekly Updates & Questions for the QA Team (hggdh)

(ttx checks that the awesome Daviey is scribe)

hggdh shares that he has been testing the metadata issue fix, and preparing to get to Lexington next week for a sprint. He notes that the current fix seems to be insufficient, and is still producing issues.

hggdh confirms that the latest lucid SRU for eucalyptus has been moved from -proposed to -updates.

Weekly Updates & Questions for the Kernel Team (jjohansen)

jjohansen shares the pv-ops kernel for EC2 hasn't been working out so we are shelving it for at least alpha2 and will update the Xen patches, and comments that zul seems to want to volunteer to work on it. zul clarifies that he wasn't.

jjohansen confirms the kernel has some known performance regressions, that will probably be in alpha2, freeing time to work on some Amazon EC2 issues, and the performance issues are known upstream and a fix should be in a later RC release.

jjohansen states the kernel team has would like to know some more about Bug #588861. The awesome Daviey confirms that triaging has been somewhat blocked at the moment, as it seems there are other foundation related issues stopping us from even getting as far as that to reproduce the issue. Since, the latest kernel, we haven't had an enviroment where we can reproduce that. Therefore, i've been unable to provide further information OR confirm if the issue is still ongoing in the latest kernel. jjohansen confirms we know its kernel related, and not an update to something else. jjohansen requests that he is kept posted and will recommend adding it to the top 50 bugs for the kernel team.

[ACTION] jjohansen to review atop patchset for Alpha3 planning purposes [ACTION] Daviey to update #588861, if needed against alpha1

Weekly Updates & Questions for the Documentation Team (sommer)

sommer confirms he added some items to the blueprint: https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-serverguide-updates , but feels he will need the most help with is the UEC section. kirkland points at Daviey, who tries to point it back to kirkland.

sommer mentions he'll request help on the clustering section from RoAkSoAx / ivoks, and that he has some updates from ttx regarding tomcat.

Priase is given to sommer for his awesome work. Hugs also seem to be unanimous to Bryce for unclutterring the launchpad whiteboard.

Papercuts Alpha2 subcycle status (ttx)

ttx shares https://launchpad.net/server-papercuts/+milestone/maverick-alpha-2 , and notes that all are assigned and 65% are already fixed, and that there are a shortage of nominations for the next cycle.

New SRU Tracker (zul)

zul introduces that at maverick uds we agreed to change the way we do nominations for SRU. we are taking it to the ubuntu-server list to get more feedback, the email will be starting shortly after some introduction. States that we are also monitoring the status of the SRU nominated bugs (work in progress) at http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html

zul explains that it is a cron job that sucks in launchpad into a sql database and displays the results. Only running daily, the information might be out of date sometimes.

[ACTION] zul to move the sru tracker code to it's own project

Open Discussion

(Nothing to discuss)

Agree on next meeting date and time

Next meeting will be on Tuesday, 22nd June at 1800 UTC in #ubuntu-meeting.

Log

[19:00] <jiboumans> #startmeeting
[19:00] <MootBot> Meeting started at 13:00. The chair is jiboumans.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:01] <jiboumans> thanks all for joining, today's scribe will be Daviey
[19:01] <Daviey> \o
[19:01] <jiboumans> [TOPIC] Review ACTION points from last meeting
[19:01] <MootBot> New Topic:  Review ACTION points from last meeting
[19:01] <jiboumans> ttx to coordinate testing for Alpha 2
[19:01] <jiboumans> for those following along at home, the agenda is up at: https://wiki.ubuntu.com/ServerTeam/Meeting
[19:01] <ttx> when alpha2 is near.
[19:02] <ttx> carryover.
[19:02] <jiboumans> very well.
[19:02] <jiboumans> smoser to train someone on the release team on the cloud image release
[19:02] <smoser> o/
[19:02] <smoser> not done.
[19:02] <jiboumans> smoser: anything blocking you?
[19:03] <smoser> i will contact release team to make sure someone else is able.
[19:03] <jiboumans> alright, let's carry over to next week then; if for any reason there's a block, feel free to flag it early so we can help resolve it
[19:03] <jiboumans> smoser to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades
[19:03] <smoser> that is done.
[19:04] <jiboumans> smoser: ta
[19:04] <jiboumans> all to keep their specs uptodate with workitems and update their status monday EOB
[19:04] <jiboumans> seems we have nice status updates on our WI tracker, thanks all
[19:04] <jiboumans> http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html for those following along
[19:04] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html for those following along
[19:05] <jiboumans> leaving sommer's action point till his section as he'll be a bit late today
[19:05] <jiboumans> moving on:
[19:05] <jiboumans> [TOPIC] Maverick development (jib)
[19:05] <MootBot> New Topic:  Maverick development (jib)
[19:05] <jiboumans> we're half way through the development cycle to the Alpha2 milestone right now
[19:06] <jiboumans> most specs should be around 50% completion right now. If you're off that mark, you may want to review work items and see if any can be postponed or dropped, or ask for some support
[19:06] <jiboumans> some are well ahead of that curve so we should have some slack in that area
[19:06] <jiboumans> I now give you ttx to go throught he specifics:
[19:06] <jiboumans> [TOPIC] Alpha2 subcycle status (ttx)
[19:06] <MootBot> New Topic:  Alpha2 subcycle status (ttx)
[19:06] <mathiaz> jiboumans: I've added some WI as I've refined some of the work to be done
[19:07] <mathiaz> jiboumans: so the percentage completion may move around as I've recorded more accurately what needs to be done
[19:07] <jiboumans> mathiaz: excellent; the WIs are meant to reflect the work you intend to do. the numbers are just there to give us a sense of of progress
[19:07] <ttx> oops
[19:07] <jiboumans> mathiaz: in all cases accuracy trumps number juggling :)
[19:07] <ttx> missed the last 5 minutes
[19:08] <jiboumans> ttx: sorry, you still have to do your bit
[19:08] <jiboumans> ttx: [TOPIC] Alpha2 subcycle status (ttx)
[19:08] <ttx> About alpha2 status ?
[19:08] <ttx> ok
[19:08] <ttx> We are going reasonably well
[19:09] <ttx> the UEC specs are slightly late but we've been addressing that
[19:09]  * hggdh blushes
[19:09] <ttx> jiboumans: want to do a quick oneliner on progress ?
[19:10] <jiboumans> ttx: i'd like to highlight the ones that we've just reviewed and rescoped somewhat
[19:10] <mathiaz> ttx: should the update section cover that?
[19:10] <jiboumans> which i believe is UEC testing, qa-workflow and cloud-init right?
=== Ursinha is now known as Ursinha-bbl
[19:10] <mathiaz> ttx: I'll be experimenting with a new format/template for the status section of BP
[19:10] <mathiaz> ttx: you should see the output of this in the coming days
[19:10] <ttx> and cloud-utils and uecec2-kernel-updates
[19:11] <jiboumans> ttx: can you fill us in what happened on those specs?
[19:11] <ttx> mathiaz: good
[19:11] <ttx> sorry, my IRc client is acting funny
[19:11]  * mathiaz hands a bottle of wine to ttx 
[19:11] <ttx> UEC testing was rescoped to concentrate on fixing the current issues to get to a stable situation, and engage in training new people
[19:12] <ttx> qa workflow was moved to A3 to give priority to uec-testing
[19:12] <ttx> cloud-init was trimmed down to move prio-3 things as targets of opportunity
[19:12] <ttx> cloud-utils first work items were reassigned to clint
[19:13] <ttx> and uec-ec2-kernel-updates work items were clarified
[19:13] <ttx> I think we now have a stable and clear view on what's expected from everyone
[19:13] <ttx> if someone thinks he cannot make it, please raise the red flag !
[19:14]  * mathiaz raises a bottle of wine towards ttx 
[19:14] <jiboumans> thanks for that summary ttx
[19:14] <jiboumans> this segways nicely to:
[19:14] <jiboumans> [TOPIC] Feature Definition Freeze this week (ttx)
[19:14] <MootBot> New Topic:  Feature Definition Freeze this week (ttx)
[19:14] <ttx> Looking at http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html gives you a clear commonly shared view on what's expected
[19:14] <ttx> Right, this Thursday is FDF*
[19:14] <ttx> we need to freeze the design on all specs that affect main packages
[19:14] <ttx> and present those to the release team
[19:15] <ttx> We should be in good shape there, with the A2+A3 planning we've done so far
[19:15] <mathiaz> ttx: do you have a list of WI that are impacted by FF?
[19:15] <mathiaz> ttx: is this what you're looking for?
[19:15] <ttx> mathiaz: no
[19:15] <mathiaz> ttx: or is it more at the BP level?
[19:15] <ttx> mathiaz: I ean, no, I'm not really needing that
[19:16] <ttx> I need to come up with a list of all specs that will land features in main
[19:16] <SpamapS> ttx: we've had to play with libmemcached a bit and fork it into two source packages, should I add that to the spec to clarify that we only want the new one in main, not the forked lucid package?
[19:16] <jiboumans> SpamapS: yes
[19:16] <jiboumans> clarity++
[19:16] <ttx> and the release team will look into them, so applying some polish to the spec docs can't hurt
[19:16] <ttx> yes, updating the spec wikidoc with current design is necessary
[19:17]  * SpamapS digs around under the kitchen sink and emerges with a bottle of windex
[19:17] <mathiaz> ttx: are MIR considered new features?
[19:17] <ttx> mathiaz: that's an ongoing debate.
[19:17] <ttx> I'd say in that context, yes.
[19:17] <ttx> They want to know what will be hitting them
[19:18] <jiboumans> i'd err on the side of caution here too and highlight these
[19:18] <mathiaz> ttx: ok - so what do you expect from the team members?
[19:18] <ttx> even if MIRteam != ReleaseTeam it still affects the contents of main.
[19:19] <ttx> take some time[tm] to review the specs and making sure they are current.
[19:19] <mathiaz> ttx: should I review all my specs and flags wether they're impacted by FF?
[19:19] <ttx> I'll take it from there.
[19:19] <mathiaz> ttx: ok
[19:19] <ttx> If I have any question, I'll ask them.
[19:19] <jiboumans> mathiaz, ttx: looking at the specs and work items, it looks fairly straightforward
[19:20] <ttx> jiboumans: ack, should be straightforward.
[19:20] <jiboumans> but to all, please be aware yourself which items affect FDF so you can answer any questions if need be
=== Ursinha-bbl is now known as GoBrazil
[19:21] <jiboumans> ttx: anything more on FDF?
[19:21] <ttx> no.
[19:21] <jiboumans> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:21] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:21] <ttx> Did anyone mention that Daviey was the scribe yet ?
[19:21] <jiboumans> ttx: first thing, yes
[19:21] <zul> ttx: off hand yes
[19:21] <hggdh> on my side
[19:21] <Daviey> ttx: Shh!
[19:21] <ttx> I missed tat as well :)
[19:22] <hggdh> rigth now testing the metadata issue fix, and preparing to get to Lexington next week
[19:22] <hggdh> no real other news right now (except that the fix does not absolutely good right now)
[19:22] <ttx>  does not absolutely good ?
[19:23] <ttx> as in, doesn't work ?
[19:23] <hggdh> ttx: sort of. I am still getting metadata failures
[19:23] <mathiaz> hggdh: what's the state of the lucid ubuntuX.2 SRU
[19:23] <mathiaz> hggdh: ?
[19:23] <mathiaz> hggdh: has the package been pushed from -proposed to -updates?
[19:24] <hggdh> mathiaz: this was tested last week, and marked verification-done. I think today they made it into -updates
[19:24] <mathiaz> hggdh: indeed - thanks for testing all the bugs
[19:25] <jiboumans> hggdh++ indeed
[19:25] <jiboumans> any questions for the QA team?
[19:25] <jiboumans> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:25] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:25] <jiboumans> thanks hggdh
[19:26] <jjohansen> well first off some updates
[19:26]  * sommer arrives
[19:26] <jjohansen> the pv-ops kernel for EC2 hasn't been working out so we are shelving it for at least alpha2 and will update the Xen patches
[19:26] <zul> boo!
[19:27] <jiboumans> sommer: good timing, you're up after this ;)
[19:27] <jjohansen> seems zul wants to volunteer to work on it
[19:27] <sommer> :-)
[19:27] <jjohansen> :)
[19:27] <zul> NO!
[19:27] <jjohansen> the kernel has some known performance regressions, that will probably be in alpha2
[19:27] <smoser> boo indeed.
[19:28] <jiboumans> jjohansen: as in, the alpha2 kernel will have these known regressions?
[19:28] <jjohansen> smoser: well part of that is so I have time to do testing of other amazon stuff
[19:28] <jjohansen> yes
[19:28] <jiboumans> jjohansen: then i assume targeted for alpha3 are the fixes to those regressions?
[19:29] <jiboumans> jjohansen: where can we read about these regressions btw?
[19:29] <jjohansen> hopefully, the problem is known upstream
[19:29] <jjohansen> and the fixes will be coming from upstream kernels in later a RC
[19:30] <jjohansen> the kernel team has would like to know some more about Bug #588861
[19:30] <ubottu> Launchpad bug 588861 in linux (Ubuntu Maverick) "Instances block in pending state, and don't start" [High,Triaged] https://launchpad.net/bugs/588861
[19:30] <Daviey> jjohansen: hey
[19:30] <jjohansen> hey Daviey
[19:30] <ttx> Daviey: what's the status of your investigations there ?
[19:31] <Daviey> Triaging that is somewhat blocked at the moment, as it seems there are other foundation related issues stopping us from even getting as far as that to reprdouce
[19:31] <Daviey> So since, the latest kernel, we haven't had an enviroment where we can reproduce that
[19:31] <ttx> Daviey: if you have bug numbers for those foundations issues, they can be raised in the release team meeting
[19:32] <Daviey> Therefore, i've been unable to provide further information OR confirm if the issue is still ongoing in the latest kernel
[19:32] <jjohansen> Daviey: so we know its kernel related, and not an update to something else
[19:32] <ttx> as blocking us.
[19:32] <Daviey> ttx: That is what i'm spending all tommorrow attempting to triage
[19:32] <ttx> Daviey: ok, keep us posted if we need to escalate how blocking this is
[19:32] <jjohansen> Daviey: okay, the question came up as we were considering adding to the kernel teams top 50
[19:32] <Daviey> jjohansen: That bug is kernel related.. but due to other platform issues - it can't yet have an enviroment to attempt to triage/reproduce
[19:33] <ttx> Daviey: alpha1 was exhibiting the bug, right ?
[19:33] <jjohansen> Daviey: okay, keep me posted and I will recommend adding it to the top 50
[19:33] <Daviey> jjohansen: Yes
[19:33] <ttx> Daviey: so we could install alpha1 and reproduce it
[19:33] <Daviey> jjohansen: I'll update the bug and EOP tommorrow, with the current status
[19:33] <Daviey> ttx: yes
[19:33] <jjohansen> okay, thanks Daviey
[19:34] <Daviey> Hmm, alpha1 with current kernel might be an interesting experiment to see if it is fixed
[19:34] <Daviey> <-- /me will do that
[19:34] <ttx> Daviey: ping me if you need help -- I can spend some cycles on reproducing that
[19:34] <Daviey> ttx: super, more hands the better
[19:35] <ttx> jjohansen: any progress on the atop patchset ?
[19:35] <jjohansen> not yeet
[19:36] <jjohansen> s/yeet/yet/
[19:36] <ttx> jjohansen: ok
[19:36] <jjohansen> any other questions for the kernel team?
[19:36] <Daviey> jjohansen: nothing server related from me, thanks!
[19:36] <jiboumans> jjohansen: do you think we can get some cycles on the atop patch in the next week?
[19:36] <jiboumans> we have to present our alpha3 plan at the end of next week and atop would be part of that ideally, but only if you give it the thumbs up
[19:36] <jjohansen> jiboumans: yes
[19:37] <jiboumans> jjohansen: thanks, let me action that
[19:37] <Daviey> Do we have some ACTION's here?
[19:37] <jiboumans> [ACTION] jjohansen to review atop patchset for Alpha3 planning purposes
[19:37] <MootBot> ACTION received:  jjohansen to review atop patchset for Alpha3 planning purposes
[19:37] <jjohansen> jiboumans: I'll see if I can't get you an answer on them by eob tomorrow
[19:37] <jiboumans> [ACTION] Daviey to update #588861, if needed against alpha1
[19:37] <MootBot> ACTION received:  Daviey to update #588861, if needed against alpha1
[19:38] <jiboumans> jjohansen: that'd be great, but this week is good already
[19:38] <jjohansen> okay
[19:38] <Daviey> awesome.
[19:38] <jiboumans> alright, thanks lads
[19:38] <jiboumans> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:38] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:39] <jiboumans> sommer: first question is of course what can we help you with ?
[19:39] <sommer> I added some items to the blueprint: https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-serverguide-updates
[19:39] <sommer> but I think the one I'll need the most help with is the UEC section
[19:40] <jiboumans> alright; daviey, kirkland, who of you would be up for taking that on?
[19:40]  * kirkland points at Daviey 
[19:40] <Daviey> Depending on the UEC blocking stuff, i could spare some.
[19:40] <sommer> for lucid I took the information from the wiki, so it would be great if someone could at least review what's  there
[19:40] <kirkland> sommer: Daviey there are a couple of good resources available for this already
[19:40] <ttx> sommer: deadline is ?
[19:41] <kirkland> Daviey: sommer: much has been written, just needs re-publication into the Server Guide format
[19:41] <sommer> ttx: september 9th
[19:41] <kirkland> sommer: you can start with http://help.ubuntu.com/community/UEC
[19:41] <Daviey> Currently UEC /doesn't work/ on Maverick.. I need to work on that first.. but after that i can spare some.
[19:41] <jiboumans> sommer: i'll edit the bp now, feel free to translate that to work items as appropriate
[19:41] <Daviey> Otherwise.. /me points at kirkland :)
[19:41] <kirkland> sommer: can you read through what we've written at that link above?
[19:41]  * ttx would advise having those items for the beta iteration
[19:41] <kirkland> sommer: come back to us in a week or so, and let us know what you need more directly?
[19:41] <kirkland> sommer: based on what you need, i bet daviey and i can help
[19:42] <Daviey> +1
[19:42]  * kirkland agrees with Daviey, UEC is busted in Maverick; that needs fixing first
[19:42] <sommer> kirkland: sure, I'd planned to, but only have two machines with the vt extensions
[19:42] <kirkland> sommer: you only need 1 to do UEC ;-)
[19:42] <Daviey> sommer: two is plenty! :)
[19:42] <jiboumans> sommer: i see a few more items you need assistance wtih
[19:42] <jiboumans> shall we add some names to that list?
[19:43] <sommer> jiboumans: that'd be great, I planned on pinging ivoks about the clustering sections
[19:43] <jiboumans> clustering sounds like RoAkSoAx / ivoks indeed
[19:43] <jiboumans> vmbuilder?
[19:43] <sommer> ttx gave me some updates for the Tomcat section a while back, but I can also test that
[19:44] <jiboumans> sommer: puppet(mathiaz) and tomcat (ttx) seem straight forward too
[19:44] <ttx> ufw -> jdstrand
[19:44] <sommer> I'll ping soren about the vmbuilder stuff
[19:44] <ttx> vmbuilder -~~> soren?
[19:44] <sommer> hopefully get ahold of him at some point :)
[19:44] <Daviey> sommer: Awesome, this is sounding like the best doc's yet!
[19:44] <jiboumans> that leaves install tasks & opennebula
[19:45] <ttx> I'd drop opennebula, it's not really in our core cloud strategy
[19:45] <sommer> is opennebula widely used?
[19:45] <sommer> ttx: sounds good to me
[19:45]  * ttx never used it
[19:45] <jiboumans> sommer: there's some people experimenting with it
[19:45] <ttx> I think it's still universe ?
[19:45] <jiboumans> sommer: i couldn't speak to the state of opennebula on ubuntu right nwo though
[19:45] <zul> no i dont think so...afaik it still in unvierse and didnt build afaik
[19:45]  * mathiaz agrees
[19:45] <SpamapS> what about documentation for pending MIR's ?
[19:45] <mathiaz> sommer: I'd drop opennebula for maverick
[19:46] <jiboumans> it's the same as in karmic
[19:46] <ttx> SpamapS: ?
[19:46] <sommer> mathiaz: sounds good will do
[19:46] <jiboumans> which is a minor patch on jaunty
[19:46] <SpamapS> ttx: I'm not clear on what needs to be in the docs.. everything in main that is server related?
[19:46] <jiboumans> ttx: are you ok with supporting sommer on documenting the new install tasks?
[19:46] <mathiaz> SpamapS: not necessarly (actually not at all)
[19:46] <ttx> jiboumans: sure
[19:47] <SpamapS> Ok, I've filed a few mir's .. mostly developer related stuff, not operational, so I don't think its necessary to document it either.. just wanted to make sure.
[19:47] <mathiaz> SpamapS: we've got to decide what is *worth* putting in the server guide
[19:47] <jiboumans> sommer: could you please double check that the spec reflects the new reality? https://blueprints.edge.launchpad.net/ubuntu/+spec/server-maverick-serverguide-updates/+whiteboard
[19:47] <sommer> SpamapS: historically the serverguide has included items that will help an admin new to ubuntu to get up and running quickly
[19:47] <sommer> jiboumans: sure
[19:48] <jiboumans> on that note: edge.launchpad.net++ for having wider whiteboards
[19:48]  * ttx hugs Bryce for unclutterring the whiteboard
[19:48] <SpamapS> ok so the monitoring framework stuff for alpha3 may need some docs (though the spec is stil "pending approval")
[19:48] <jiboumans> sommer: i've added the names we just discussed; go ahead and change that to work items as appropriate. for the canonical guys, please schedule it for the beta iteration
[19:48]  * kirkland high fives bryce too
[19:48] <jiboumans> sommer: for the others, whenever is good for them of course
[19:49] <sommer> jiboumans: will do
[19:49] <jiboumans> SpamapS: that'll be true until just before Alpha3
[19:49] <jiboumans> we don't 'approve' them until we've commited to work on them
[19:49] <jiboumans> and we decide that on a per-iteration basis
[19:50]  * SpamapS continues absorbing the process
[19:50] <SpamapS> :)
[19:50] <jiboumans> sommer: anything else from you?
[19:50] <sommer> I think that's it... thanks everyone for your help :)
[19:51] <jiboumans> sommer++ no, thank you
[19:51] <jiboumans> [TOPIC] Papercuts Alpha2 subcycle status (ttx)
[19:51] <MootBot> New Topic:  Papercuts Alpha2 subcycle status (ttx)
[19:51] <ttx> quick status
[19:51] <ttx> https://launchpad.net/server-papercuts/+milestone/maverick-alpha-2
[19:51] <ttx> all assigned
[19:51] <ttx> 65% fixed
[19:51] <ttx> Remember to nominate for the next cycle
[19:51] <ttx> we have a shortage in nominations
[19:52] <ttx> done.
[19:52] <jiboumans> ttx++ thanks
[19:52]  * SpamapS has a couple in mind but cannot nominate for milestones.. yet
[19:52] <jiboumans> [TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)
[19:52] <MootBot> New Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)
[19:52] <jiboumans> SpamapS: tell ttx about 'm and he can nominate on yoru behalf
[19:52] <ttx> SpamapS: you can "nominate for papercuts"
[19:52] <mathiaz> zul: what's the state of the weekly nomination script?
[19:52] <SpamapS> ttx: right, right. :)
[19:52] <ttx> SpamapS: just mark as "Also affecting" server-papercuts
[19:53] <mathiaz> zul: the WI is marked as done - I haven't seen an email going out though
[19:53] <zul> so the weekly nomination stuff is a work in progress
[19:53] <mathiaz> one bug nominated for lucid: bug 588293
[19:53] <ubottu> Launchpad bug 588293 in qemu-kvm (Ubuntu) "Memory leak" [Medium,Triaged] https://launchpad.net/bugs/588293
[19:54] <mathiaz> anything worth SRUing on http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html ?
[19:54] <mathiaz> ^^?
[19:54] <SpamapS> https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/419091  not on that list, but worth SRU'ing into karmic
[19:54] <ubottu> Launchpad bug 419091 in couchdb (Ubuntu) "couchdb init script doesn't properly control processes" [Undecided,Fix released]
[19:54] <zul> mathiaz: bug 572410
[19:54] <ubottu> Launchpad bug 572410 in samba (Ubuntu) "nmbd doesn't start because of missing testparm" [Medium,Fix released] https://launchpad.net/bugs/572410
[19:55] <Daviey> possibly 579584
[19:55] <Daviey> bug 579584
[19:55] <ubottu> Launchpad bug 579584 in libvirt (Ubuntu) "setgid, setuid needed by /etc/apparmor.d/abstractions/libvirt-qemu" [Medium,Fix released] https://launchpad.net/bugs/579584
[19:56] <ttx> SpamapS: karmic ?
[19:56] <SpamapS> ttx: it was fixed in lucid, but karmic cannot stop couchdb.
[19:56] <mathiaz> SpamapS: that's annoying
[19:56] <mathiaz> SpamapS: if the patch is really simple it may be worth SRUing
[19:56] <SpamapS> the init script was totally rewritten for lucid .. and would be a simple backport.
[19:57] <mathiaz> SpamapS: hm - I've approved the nomination for now
[19:57] <jiboumans> SpamapS: the only real answer is: http://www.youtube.com/watch?v=Fow7iUaKrq4 #light-hearted
[19:57] <jiboumans> any other nominations?
[19:57] <SpamapS> jiboumans: ++
[19:57] <jiboumans> [TOPIC] New SRU Tracker (zul)
[19:57] <MootBot> New Topic:  New SRU Tracker (zul)
[19:58] <zul> hi
[19:58] <zul> so for the maverick uds we are changing the way we do nominations for SRU...
[19:58] <mathiaz> Daviey: does the bug fit the SRU criteria?
[19:58] <jiboumans> [LINK] http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html
[19:58] <MootBot> LINK received:  http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html
[19:58] <zul> we are taking it to the ubuntu-server list to get more feedback, the email will be starting shortly after some introduction
[19:59] <Daviey> mathiaz: possibly, requires more investigation
[19:59] <zul> we are also monitoring the status of the SRU nominated bugs (work in progress) at http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html
[19:59] <jiboumans> zul++
[19:59] <zul> basically its a cron job that sucks in launchpad into a sql database and displays the results
[20:00] <zul> it runs nightly so the information might be out of date sometimes
[20:00] <mathiaz> zul: this is great work
[20:00] <ttx> The results are slightly false though
[20:00] <jiboumans> i'd like to integrate this in our SRU reviews as well
[20:00] <ttx> I hear you have a fix for the "all boxes are green" issue
[20:00] <zul> ttx: yeah because i havent worked out all the bugs yet
[20:00] <ttx> ack
[20:00] <jiboumans> it's work in progress, but even the early version is helpful imho
[20:01] <jiboumans> zul: moving it to an LP branch a la work-item-tracker's good i think
[20:01] <zul> in the second table on that page is a list of nominated bugs that no one has worked on
[20:01] <mathiaz> yes - we can already spot bugs that could handle some testing
[20:01] <zul> funny that you mention that https://code.edge.launchpad.net/~zulcss/+junk/server-sru-tracker
[20:01] <mathiaz> zul: of *accepted* bugs
[20:01] <jiboumans> zul: minues the +junk? :)
[20:01] <zul> but it has to be moved to its own project
[20:02] <zul> jiboumans: ack
[20:02] <jiboumans> zul: indeed
[20:02] <jiboumans> [ACTION] zul to move the sru tracker code to it's own project
[20:02] <MootBot> ACTION received:  zul to move the sru tracker code to it's own project
[20:02] <jiboumans> zul++ thanks for whipping this up
[20:02] <jiboumans> any more questions on the tracker?
[20:02] <ttx> yay, let's branch it
[20:02] <zul> ttx: and mock the code? :)
[20:02] <Daviey> fork that.
[20:02] <jiboumans> [TOPIC] Open Discussion
[20:02] <MootBot> New Topic:  Open Discussion
[20:03] <jiboumans> going once...
[20:03] <Daviey> None here.
[20:03] <jiboumans> going twice...
[20:03] <ttx> ...
[20:03] <jiboumans> sold to the bearded lady in the back
[20:03] <jiboumans> [TOPIC] Announce next meeting date and time
[20:03] <jiboumans> Tuesday 2010-06-22 at 1800 UTC - #ubuntu-meeting
[20:03] <MootBot> New Topic:  Announce next meeting date and time
[20:03] <jiboumans> #endmeeting