[10:00] <head_victim> Good evening all, Asia/Oceania Membership Board meeting just about due
[10:03] <head_victim> Good evening Destine
[10:04] <Destine> head_victim, hey, i logged in from two devices and that was a mess...
[10:05] <head_victim> No dramas, the first order of business it to make quorum :)
[10:05] <Guest80767> head_victim, hey, I am Destine II :)
[10:06] <head_victim> lifeless or elky about?
[10:06] <head_victim> I can't see any of the other members in the channel at the moment.
[10:07] <Destine> head_victim, me neither...
[10:07] <Destine> ejat?
[10:07] <head_victim> Actually lifeless = Rob so he advised on the mailing list he wouldn't be able to make tonight
[10:08] <Destine> head_victim, oh, he is Robert.
[10:08] <Destine> head_victim, then we need to look for the others.
[10:08] <head_victim> Yep, I just trawled launchpad :)
[10:08] <czajkowski> I can step in if yer stuck
[10:09] <head_victim> czajkowski: thank you :) I just also wanted to confirm applicants had shown before hassling others so are vibhav or bonepyaesone around here with different nicks?
[10:16] <head_victim> It's not looking good on either front, applicants or board members :
[10:17] <czajkowski> nope
[10:20] <head_victim> Destine & czajkowski thanks for showing but I think we'll have to call it. We're 20 minutes in and have neither applicants nor quorum. I'll write an email to the list as we can't keep going on like this.
[10:20] <head_victim> I was hoping the addition of extra members recently (myself included) was going to improve our ability to meet quorum.
[10:22] <Destine> head_victim, I guess so. Thank you for your work.
[10:23] <head_victim> Destine: thanks for showing up :)
[10:23] <czajkowski> head_victim: sorry
[10:24] <head_victim> czajkowski: don't be, at least this time no applicants were hindered
[11:21] <vibhav> Has the meeting ended?
[11:22] <head_victim> vibhav: yes sorry, it started at 1000UTC (about an hour and 20 minutes ago)
[11:22] <vibhav> head_victim: What were the outcomes
[11:22] <vibhav> I had gone for classe
[11:22] <vibhav> classes *
[11:22] <head_victim> None of the applicants were present so we had to postpone to next meeting.
[11:23] <vibhav> gah
[11:23] <head_victim> We don't usually like to make judements without applicants present.
[11:23] <vibhav> :(
[11:24] <vibhav> well thanks head_victim
[11:24] <vibhav> Is it important for the applicants to be present?
[11:24] <head_victim> vibhav: hopefully you can make the january 10th meeting :)
[11:25] <vibhav> head_victim: I dont think so , I can
[11:25] <vibhav> cannot*
[11:25] <head_victim> vibhav: I'm not sure to be honest, my suggestion is if you have problems attending the meetings due to timezone issues I'd email the membership board. Hang on I'll grab the address
[11:26] <vibhav> head_victim: Nice idea
[11:28] <czajkowski> vibhav: if you cant attend the A/O board you can attend another membership board
[11:28] <czajkowski> like Americas or EMEA
[11:29] <vibhav> czajkowski: But I am not in the respective geographical reigon
[11:29] <czajkowski> vibhav: that doesnt matter
[11:29] <czajkowski> vibhav: your wiki page should detail all your work done and the board members can make decisions based on that and talking to you
[11:29] <vibhav> czajkowski: Thanks!
[11:29] <czajkowski> np
[11:31] <vibhav> Is there any way for getting membership ?
[11:32] <vibhav> czajkowski : All the timings of the Meetings are colliding with my schedule :(
[11:33] <vibhav> czajkowski: including Americas and EMEA
[11:33] <czajkowski> vibhav: you do have to attend one of them
[11:33] <vibhav> :9
[11:34] <vibhav> :(
[11:34] <vibhav> Cant do that
[11:34] <czajkowski> maybe in another month or so you could arrange to get 10-15 mins and attend one of them
[11:34] <vibhav> For the americas meeting , I can be available for 5 mins or so
[11:35] <czajkowski> it takes a bit longer. it's up to you vibhav
[11:35] <vibhav> Maybe I should contact the membership board
[15:59] <smoser> the honorable utlemming will be presiding.
[16:00] <hallyn_> three cheers
[16:00]  * Ursinha waves
[16:01] <zul> oh...hello
[16:03] <utlemming> honorable? how about Distinguished?
[16:03] <zul> how about awesome-x
[16:03] <zul> how about awesome-o even
[16:03] <smoser> its your meeting. whatever you want.
[16:03] <utlemming> lol
[16:04] <rbasak> awesome-p, surely?
[16:04] <hallyn_> but let's get this show on the ROAD
[16:04] <utlemming> okay, lets get rolling then
[16:04] <utlemming> #startmeeting Ubuntu Server Team Meeting
[16:04] <meetingology> Meeting started Tue Dec 13 16:04:53 2011 UTC.  The chair is utlemming. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[16:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:05] <utlemming> #TOPIC Review ACTION points from previous meeting
[16:05] <utlemming> Reviewing items from last week...
[16:05] <utlemming> and it doesn't look like there are any
[16:06] <utlemming> does anyone have any follow up on last weeks discussion items?
[16:06] <utlemming> okay then
[16:06] <utlemming> #topic Precise Development
[16:06] <utlemming> I believe that we are sans Daviey today
[16:07] <zul> improvise! improvise!
[16:07] <hallyn_> ok, zul - take charge
[16:07] <zul> not me
[16:07] <utlemming> zul, bug 883988?
[16:07] <zul> still need to be looked at
[16:07] <SpamapS> o/
[16:07] <jamespage> o/
[16:08] <utlemming> bug 893926
[16:08] <utlemming> still doesn't have an owner....any takers?
[16:09] <utlemming> no?
[16:09] <SpamapS> lol .. draw straws
[16:09] <utlemming> and SpamapS drew the shortest one!
[16:10] <utlemming> fancy that
[16:10] <SpamapS> I think we probably should try to sync with Debian at this point
[16:10] <utlemming> lets leave this for an action then
[16:11] <utlemming> bug 855030
[16:11] <utlemming> zul, it looks like its fixed released?
[16:12] <zul> utlemming: yeah
[16:12] <zul> the fix landed in percise
[16:12] <smoser> percise, yo
[16:12] <utlemming> hallyn: how is bug 881903 moving along?
[16:12] <hallyn_> bot?
[16:12] <hallyn_> utlemming: it's not
[16:13] <hallyn_> we're waiting on lxc upstream release
[16:13] <utlemming> k
[16:13] <hallyn_> and that is lower prio than the container reboot stuff, which is holding him up
[16:13] <hallyn_> so i don't care to push :)
[16:13] <utlemming> fair enough
[16:13] <utlemming> (if anyone can't tell, I'm working down last weeks meeting notes)
[16:14] <hallyn_> good idea :)
[16:14] <utlemming> jamespage: how is bug 888124 looking?
[16:14] <jamespage> oh - fixable; its part of a larger piece of work to transition default-java from 6->7
[16:15] <jamespage> I should prob fix it so it comes off the list
[16:15] <SpamapS> jamespage: is there a transition tracker for that, or does it just require rebuilds for rebuild sake?
[16:16] <jamespage> SpamapS, well it does not really need one per say
[16:16] <jamespage> as stuff thats already in the archive will continue to work
[16:16] <jamespage> as Java is bytecode backwards compatibile - but not source
[16:16] <SpamapS> right, but rebuilding so we know it will not FTBFS
[16:16] <jamespage> SpamapS, thats the one
[16:17] <jamespage> java7-ftbfs tag in lp will tell you what it broken
[16:17] <utlemming> it looks like we never found an adopter for bug 607039
[16:17] <utlemming> any takers this week?
[16:18] <smb> err
[16:18] <smb> Well wanted to try to supply a debdiff but got distracted
[16:19] <smb> I'd propose to have an alias defined in /etc/modprobe.d
[16:19] <smb> ..
[16:20] <hallyn_> smb: i like the idea of goin gthrough debian,
[16:20] <hallyn_> question is just whether the submitter needs a faster fix.  but i assume they can just fix it locally with a modprobe alias?
[16:20] <hallyn_> you've tested that?
[16:21] <smb> hallyn_, either that or just replace fstype nfs4 (which is deprecated anyway) by nfs
[16:21] <smb> hallyn_, in small scale tested both
[16:21] <smb> But apparently the reporters lost interest...
[16:21] <hallyn_> in auto.mnt.  sounds good
[16:22] <hallyn_> well,
[16:22] <hallyn_> if they lost interest, let's go through debian, i say...
[16:22] <hallyn_> (fwiw)
[16:22] <utlemming> RoAkSoAx: there was a bit of discussion last week with around bug 887186
[16:22] <smb> hallyn_, Agreed. Guess I need to file a bug with fix there then
[16:22] <hallyn_> i'd like to think they lost interest bc the s/nfs4/nfs/ fix worked for them locally :)
[16:23] <smb> hallyn_, My guess too :)
[16:23] <hallyn_> ok - i'm not 100% clear how you'd do the debdiff, do you mind doing it?
[16:23] <smb> hallyn_, I would not mind. Can take a bit of time though
[16:23] <smb> my only working day this year is Thursday. :-P
[16:24] <utlemming> adam_g:  bug 862558
[16:25] <utlemming> no adam_g?
[16:25] <utlemming> back to zul then: bug 871278
[16:26] <zul> utlemming: working on that now
[16:26] <zul> or trying to
[16:26] <hallyn_> ouch
[16:26] <SpamapS> utlemming: cobbler-enlist is undergoing quite a few revisions, so that bug may become moot in the near future.
[16:26] <utlemming> okay, good to know
[16:27] <utlemming> koolhead: how is bug 890362 moving along?
[16:27] <smoser> i thought adam_g had a merge proposal for tath
[16:27] <zul> it got merged and uploaded
[16:28] <smoser> yeah... but the nova task is still open
[16:28] <smoser> apparently, "should glance user's shell be /bin/false" also affects nova
[16:28] <smoser> i'm assuming someone thinks' nova's shell should be /bin/false also
[16:29] <utlemming> utlemming: bug 891433
[16:29] <utlemming> I need to put in the merge proposal, but otherwise its fixed
[16:31] <utlemming> RoAkSoAx: bug 898840
[16:32] <utlemming> okay
[16:33] <utlemming> finally...I think we're through the list
[16:33] <utlemming> does anyone else have Precise Development topics?
[16:33] <utlemming> #topic Ubuntu Server Team Events
[16:33] <utlemming> any topics here?
[16:33] <SpamapS> SCALE10X
[16:34] <SpamapS> http://www.socallinuxexpo.org/
[16:34] <SpamapS> Jorge Castro and I will be presenting, and there will be a Juju Charm School on Friday!
[16:34] <SpamapS> ALso there is a CFP for Velocity out
[16:35] <utlemming> Moving on then...
[16:35] <utlemming> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:35] <utlemming> hggdh, ?
[16:36] <SpamapS> Last bit, get your talks submitted: http://velocityconf.com/velocity2012
[16:36] <utlemming> no hggdh...so well move on then
[16:36] <utlemming> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:36] <utlemming> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:36]  * hggdh is here
[16:37] <smb> The fix for the thing that required idle=halt on ec2 has been fixed upstream and in latest precise.
[16:37] <smb> Im currently trying to bisect bug 901305
[16:37] <smb> Unfortunately I ended up on something unreasonable on first run
[16:37] <smb> Not sure I did something wrong or what happened. So I go again
[16:37] <smb> ..
[16:38] <smoser> smb, the other thing on your list is the atop bug.
[16:39] <smoser> which seems fairly iportant for 11.10 even though its fix-released in precise already.
[16:39] <smb> smoser, right. That one seems only to happen on ec2
[16:39] <smoser> oh...
[16:39] <smb> Not in my test system
[16:39] <smoser> are you convinced that it is fix-released in precise ?
[16:39] <smoser> or was i just lucky
[16:39] <smb> Thats why I asked whether people know which xen version that instance got
[16:40] <smb> So when trying first grep for dmseg|grep Xen and note the Xen version
[16:40] <smoser> right.
[16:40] <smoser> well.. i'll launch a bunch of instances later and see what i find.
[16:40] <smb> smoser, Thanks a lot
[16:41] <utlemming> smb: anything else?
[16:41] <smb> not from here..
[16:41] <utlemming> okay, hggdh, back to you
[16:41] <utlemming> hggdh, do you have anything for us?
[16:41] <hggdh> utlemming: just some questions:
[16:42] <hggdh> (1) is cloud-init on Lucid expected to work with Cobbler on Oneiric? If so, we have a bug
[16:42] <hggdh> (2) are you all good on the QA resources?
[16:43] <smoser> cobbler will not work with version of cloud-init in lucid.
[16:43] <hggdh> smoser: ah, thank you. So we need to adjust the cobbler setup on the Lab
[16:44] <smoser> as cobbler uses /var/lib/cloud/nocloud/seed which i think only exists in at earliest maverick.
[16:44] <smoser> but the cloud-init stufff is only used for juju i think.
[16:44] <smoser> right?
[16:45] <hggdh> I think it is needed for cobbler commands, like reboot, is it not?
[16:45] <SpamapS> no
[16:45] <smoser> not that i'm aware of
[16:45] <smoser> but i could be wrong
[16:45] <SpamapS> hggdh: it is only used in first-boot config stuff
[16:46] <smoser> i was not aware of anything that did power control other than "real power control" (ie, lights-out or ipmi or something)
[16:46] <hggdh> OK. will check more carefully. Right now I know I cannot reboot via cobbler on Lucid
[16:46] <hggdh> thank you
[16:46] <hggdh> ..
[16:47] <SpamapS> hggdh: cobbler doesn't have the ability to "reboot" stuff AFAIK, only to turn the power off/on.
[16:48] <utlemming> anything else here?
[16:48] <hggdh> SpamapS: heh. RTFM seems to be needed for me, then. I based myself on the cobbler URL
[16:48] <hggdh> nope, I am done
[16:48] <utlemming> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:48] <utlemming> NCommander, ?
[16:49] <NCommander> Not much to say
[16:49] <NCommander> Mostly waiting on hardware (not sure how much I can sya behond that)
[16:49] <SpamapS> armhf seems to be moving along nicely
[16:49] <NCommander> armhf bootstrap is proceeding nicely
[16:49] <NCommander> bah, ninja'ed
[16:49] <SpamapS> JINX
[16:49] <utlemming> Okay then...
[16:49] <utlemming> #topic Weekly Updates & Questions from the Ubuntu Community
[16:49] <NCommander> fortunately, that only applies to speaking, not typing ;-)
[16:49] <NCommander> anyway, done
[16:50] <utlemming> Anyone have anything from or for our fine community of users?
[16:50] <utlemming> I will take that as a no...
[16:50] <utlemming> #topic Open Discussion
[16:50] <utlemming> Any open discussion topics?
[16:51] <Ursinha> Santa is coming
[16:51] <SpamapS> I think we should eliminate the "Community" topic. It implies that there are people here at the meeting who are not in the community.
[16:51] <m_3> SpamapS: +1
[16:51] <utlemming> +1
[16:52] <smoser> i'm not in the community
[16:52] <hallyn_> you ARE the community
[16:52] <smoser> ignore me.
[16:52] <SpamapS> We can table it until January though, since we are already missing quite a few who may have strong opinions on that.
[16:52] <SpamapS> But it just ocurred to me.
[16:52] <utlemming> #action invite smoser into the community
[16:52] <meetingology> ACTION: invite smoser into the community
[16:52] <SpamapS> NICE
[16:52] <Ursinha> lol
[16:52] <SpamapS> Another thing that I noticed.. meeting minutes not going out... ???
[16:52] <smoser> i did not send them out.
[16:52] <smoser> :-(
[16:52] <smoser> fail.
[16:53] <smoser> i can do that. i just didn't get to it.
[16:53] <smoser> they are supposed to
[16:53] <SpamapS> The bot like, generates them automatically.. so is there any reason they're not going out to ubuntu-devel and ubuntu-server ?
[16:53] <smoser> where does it generate them to ?
[16:54]  * rbasak wonders if adam_g and RoAkSoAx are DST-induced laggards
[16:54] <SpamapS> smoser: meetingology help page explains it
[16:54] <SpamapS> rbasak: adam_g most likely yes.. RoAkSoAx is in EDT , so he has no excuse. ;)
[16:55] <utlemming> isn't adam_g in Oregon?
[16:55] <utlemming> okay, lets call this
[16:55] <SpamapS> yes
[16:55] <utlemming> #Announce next meeting date and time
[16:55] <smoser> fwiw, i'm not seeing in https://wiki.ubuntu.com/meetingology where minutes are kept.
[16:56] <rbasak> Speaking of DST, Google Calendar doesn't seem to support UTC times for meetings - but it's been pointed out to me that if you specify Reykjavik then meetings will be pegged to UTC
[16:56] <smoser> and if they *are* kept somewhere, then personally, i dont see a lot of reason to manually email them to some mailing lists.
[16:56] <robbiew> rbasak: huh?
[16:56] <robbiew> yes it does...you just have to have UTC as your default TZ
[16:56] <SpamapS> smoser: #endmeeting sends you the link, IIRC
[16:56] <hallyn_> smoser: I'd like to do either m-l or blog, not both
[16:57] <SpamapS> hallyn_: there's a script that does it automatically
[16:57] <hallyn_> so everyone says
[16:58] <SpamapS> lp:~clint-fewbar/+junk/ubuntuserver-minutes/
[16:58] <SpamapS> Used to be mentioned in the "how to write the minutes" page in the serverteam KB
[16:59] <hallyn_> SpamapS: I'll try it next week, thx
[16:59] <smoser> https://code.launchpad.net/~clint-fewbar/+junk/ubuntuserver-minutes/
[16:59] <SpamapS> utlemming: endmeeting?
[16:59] <utlemming> Tuesday 2011-12-20 at 1600 UTC - #ubuntu-meeting
[16:59] <utlemming> #endmeeting
[16:59] <meetingology> Meeting ended Tue Dec 13 16:59:38 2011 UTC.
[16:59] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-13-16.04.moin.txt
[16:59] <smoser> that is documented at https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <kamal> o/
[17:00] <ppisati> o/
[17:00] <cking> o/
[17:00] <smb> \o
[17:00] <sforshee> o/
[17:00] <bjf> sigh
[17:00] <arges> o/
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <meetingology> Meeting started Tue Dec 13 17:00:36 2011 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> P/omap4: a new kernel (3.2.0-1402.2) based off 3.2 (Ubuntu-3.2.0-3.9) has been released, while a new TI BSP + 3.2-rc5 is in the pipe.
[17:01] <ppisati> SRU kernels: nothing to report.
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> Just adding link this week, instead of posting all data.
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-team-precise-alpha-2.html
[17:01] <ogasawara> || apw        || hardware-p-kernel-boot                || 1 work item  ||
[17:01] <ogasawara> ||            || hardware-p-kernel-config-review       || 4 work items ||
[17:01] <ogasawara> ||            || hardware-p-kernel-delta-review        || 4 work items ||
[17:02] <ogasawara> ||            || foundations-p-ipv6                    || 1 work item  ||
[17:02] <ogasawara> || cking      || hardware-p-kernel-delta-review        || 1 work item  ||
[17:02] <ogasawara> || jsalisbury || other-p-bug-workflows                 || 1 work item  ||
[17:02] <ogasawara> || ogasawara  || hardware-p-kernel-version-and-flavors || 1 work item  ||
[17:02] <ogasawara> ||            || hardware-p-kernel-config-review       || 21 work items||
[17:02] <ogasawara> || tgardner   || hardware-p-kernel-version-and-flavors || 1 work item  ||
[17:02] <ogasawara> ||            || hardware-p-kernel-delta-review        || 1 work item  ||
[17:02] <ogasawara> If your name is in the above table, please review your Alpha-2 work items.  Note that Alpha-2 is Thurs Feb 2.
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Blueprint: hardware-p-kernel-power-management (cking)
[17:02] <cking> Power Management:
[17:02] <cking>  * Re-run power.d readahead and journal-commit tests on non-idle
[17:02] <cking>    user application scenerios.
[17:02] <cking>  * Measure mouse power consumption, different rates + devices:
[17:02] <cking>       http://zinc.canonical.com/~cking/power-benchmarking/mouse-movement
[17:02] <cking>  * Complete PowerTop good/bad results:
[17:02] <cking>       http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad-recommendations
[17:02] <cking>  * Measure backlight levels power traits:
[17:02] <cking>       http://zinc.canonical.com/~cking/power-benchmarking/backlight-non-linearity
[17:02] <cking>  * More extensive 32 vs 64 bit power comparisons (in progress)
[17:02] <cking>  * Compare UEFI vs BIOS firmware (in progress)
[17:02] <cking>  * Complete pm-utils measurements:
[17:02] <cking>       http://zinc.canonical.com/~cking/power-benchmarking/pm-utils-results
[17:02] <cking>  * Crowd-sourcing pm-utils extra tweaks, CALL FOR TESTING:
[17:02] <cking>       https://wiki.ubuntu.com/Kernel/PowerManagementPMUtils
[17:02] <cking> ..
[17:03] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:03] <ogasawara> We have uploaded the 3.2.0-4.10 Ubuntu kernel which is based on latest upstream v3.2-rc5 kernel.  Additionally, after yesterday's Tech Board discussion around the i386 non-pae flavor, it was decided to continue carrying this flavor for 12.04 and then drop it in 12.10.  The installer will also be switched to default to the pae flavor for i386.
[17:03] <ogasawara> Important Upcoming Dates:
[17:03] <ogasawara>  * Thurs Feb 2 - Alpha 2 (~7 weeks)
[17:03] <ogasawara> ..
[17:04] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:04] <apw> CVE-2010-4251 CVE-2010-4805 CVE-2011-1082 CVE-2011-1083: epoll DOS --  fix incomplete, referred back to Security for review
[17:04] <apw> CVE-2011-1747: agp ioctl memory DOS -- no upstream fix as yet
[17:04] <apw> CVE-2011-3347: be2net non-member vlan DOS -- cannot identify upstream fix
[17:04] <apw> CVE-2011-3638: ext4 extent split -- upstream fix identified, pending application
[17:04] <apw> CVE-2011-4112: pktgen bridge panic -- redhat is withdrawing the CVE
[17:04] <apw> CVE-2011-4131: nfs4 ACL oops -- fix is still iterating upstream, pending
[17:04] <apw> CVE-2011-4347: kvm kvm_vm_ioctl_assign_device crashes -- no upsteam fix as yet
[17:04] <apw>  
[17:04] <apw> [17:04] <apw>  
[17:04] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:04] <apw>  
[17:04] <apw> Currently open CVEs for each supported branch:
[17:04] <apw>  
[17:04] <apw> || Package                                  || Open      ||
[17:04] <apw> ||                                          ||           ||
[17:04] <apw> || linux Hardy                              ||   10 (-1) ||
[17:04] <apw> || linux Lucid                              ||    7 (-1) ||
[17:04] <apw> || linux Maverick                           ||    7 (-1) ||
[17:04] <apw> || linux Natty                              ||    7 (-1) ||
[17:04] <apw> || linux Oneiric                            ||    5      ||
[17:04] <apw> || linux Precise                            ||    5      ||
[17:04] <apw> || linux-ec2 Lucid                          ||    7 (-1) ||
[17:04] <apw> || linux-fsl-imx51 Lucid                    ||    7 (-1) ||
[17:04] <apw> || linux-mvl-dove Lucid                     ||    7 (-1) ||
[17:04] <apw> || linux-mvl-dove Maverick                  ||    7 (-1) ||
[17:05] <apw> || linux-ti-omap4 Maverick                  ||    7 (-1) ||
[17:05] <apw> || linux-ti-omap4 Natty                     ||    7 (-1) ||
[17:05] <apw> || linux-ti-omap4 Oneiric                   ||    5      ||
[17:05] <apw> || linux-ti-omap4 Precise                   ||    5      ||
[17:05] <apw> || linux-lts-backport-maverick Lucid        ||    7 (-1) ||
[17:05] <apw> || linux-lts-backport-natty Lucid           ||    7 (-1) ||
[17:05] <apw> || linux-lts-backport-oneiric Lucid         ||    5      ||
[17:05] <apw>  
[17:05] <apw> We only have one open CVE with an upstream fix currently.  The remainder await fixes from upstream.
[17:05] <apw>  
[17:05] <apw> ..
[17:05] <apw> (bah, will drop the CVE- prefix for future updates.) ..
[17:05] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:05] <bjf> Many of the kernels in -proposed were quickly verified and went into
[17:05] <bjf> regression testing early. This week is mostly about finishing up the
[17:05] <bjf> stragglers. A new Oneiric has been prep'd and uploaded. We'll just have
[17:05] <bjf> to see if we can get it verified and regression tested before the
[17:06] <bjf> dead week of Christmas.
[17:06] <bjf>  
[17:06] <bjf> Here is the status for the main kernels, until today (13/12):
[17:06] <bjf>  
[17:06] <bjf>  * Hardy - 2.6.24-30.97
[17:06] <bjf>   * On holiday
[17:06] <bjf>  
[17:06] <bjf>  * Lucid - 2.6.32-36.79
[17:06] <bjf>   * Regression testing in progress.
[17:06] <bjf>  
[17:06] <bjf>  * Maverick - 2.6.35-31.63
[17:06] <bjf>   * On holiday
[17:06] <bjf>  
[17:06] <bjf>  * Natty - 2.6.38-13.53
[17:06] <bjf>   * Regression testing in progress.
[17:06] <bjf>  
[17:06] <bjf>  * Oneiric - 3.0.0-14.23
[17:06] <bjf>   * Prep'd and trying to reach -proposed
[17:06] <bjf>  
[17:06] <bjf> Current opened tracking bugs details:
[17:06] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:06] <bjf>  
[17:06] <bjf> For SRUs, SRU report is a good source of information:
[17:06] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:06] <bjf>  
[17:06] <bjf> Future stable cadence cycles:
[17:06] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:06] <bjf> ..
[17:07] <jsalisbury> [TOPIC] Hardware Certification - Testing Pools (brendand)
[17:07] <brendand> hi
[17:07] <brendand> let me do this gradually
[17:07] <brendand> As part of the SRU workflow the hardware certification team tests the -proposed kernel on as many certified systems as possible.
[17:07] <brendand> As the number of certified systems for each release has grown, getting full coverage has become more and more difficult.
[17:07] <brendand> To allow us to reduce the number of systems tested we have devised a system of 'testing pools'.
[17:07] <brendand> This takes advantage of a system which stores details of the certified hardware including it constituent components to provide as broad a component coverage as possible.
[17:08] <brendand> Initially the system ensured that at least one instance of each piece of hardware (as identified by PCI Id's) was present in the testing pool.
[17:08] <brendand> This turned out not to fulfill the goal of the system since we still ended up with needing almost all the systems we had to provide full coverage (e.g. 165 systems certified for Natty gave a testing pool of 158)
[17:08] <brendand> We made a first effort at reducing the size of the pools by considering only components of particular categories to be 'important'. A list of these was sent to the kernel-team mailing list.
[17:08] <brendand> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AphFraZYTghddElqTHl3NmZsWXVDYkMxcE5zX3EtR0E&hl=en_US#gid=0
[17:09] <brendand> These give us testing pools of ~50 systems. However we are not happy yet with the coverage. We need feedback on which components need to be added in.
[17:09] <brendand> The criteria used should be: how likely is it that a bug could occur in just a subset of the components of this category? A good example is the category 'Display Controller/VGA Compatible Controller' which we do cover already. We know for a fact that bugs will be specific to particular makes of graphics card. Same for CPUs ('Processor' category)
[17:10] <brendand> We really need feedback on this
[17:10] <brendand> ...
[17:11] <jsalisbury> brendand, This will all be documented in the meeting minutes.  It would be good if you could also follow up with an email to the kernel-team mailing list.
[17:12] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:12] <ogasawara> brendand: Do you have a revised list which has all the possible components you want us to review to consider adding back in?  Also, what # are you looking for to satify coverage?
[17:12] <brendand> ogasawara - if you can access that link then all the ones marked 'x' are not considered at the moment
[17:13] <brendand> we have no fixed number to reach
[17:13] <tgardner> brendand, what is the max number of machines that you can cover ?
[17:14] <brendand> tgardner - it seems to be about 90, realistically speaking. something like that.
[17:14] <tgardner> ack
[17:14] <brendand> i would prefer for now to take each component category on it's own merits'
[17:15] <brendand> rather than considering how many extra systems it adds. we (the hwcert team) can worry about managing that
[17:15] <brendand> i had a question to pose, as a bit of a thought experiment
[17:16] <brendand> Could a bug affect only a subset of device of the category 'Bridge/PCI bridge'?
[17:16] <tgardner> brendand, likely, but its more likely to be BIOS specific
[17:17] <apw> if there is more than one different piece of h/w in any category it is possible to get different results from each
[17:17] <tgardner> however, we have way fewer problems with PCI bridges.
[17:17] <brendand> apw - yes, definitely *possible*.
[17:18] <brendand> actually the point of that question was to illustrate the line of thinking that needs to be taken to evaluate this list of component categories
[17:18] <brendand> between tgardner and apw that's the kind of critique of the list i'm looking for
[17:19] <brendand> thanks
[17:19] <jsalisbury> Any Open Discussion comments?
[17:19] <brendand> one last thing. i'm not sure is that link public. anyone who can't get access please let me know and i'll sort something out
[17:20] <jsalisbury> If no other comments, then going once
[17:20] <ogasawara> brendand: how do you want feedback, maybe a "feedback" column, and we'll add X's to categories we think should be added back?
[17:21] <brendand> ogasawara - i'm arranging for everyone to have edit rights and i'll add a feedback column
[17:22] <ogasawara> brendand: let us know when it's ready for editing.  I'm sure a few of us can just a quick pass off and tick the ones we want.
[17:22] <ogasawara> ..
[17:22] <jsalisbury> brendand, any other comments?
[17:23] <brendand> yeah, if any of the categories don't make sense to you, contact me about it
[17:23] <brendand> i'll send the link to the kernel-team list
[17:24] <jsalisbury> brendand, dot dot then ?
[17:24] <brendand> ..
[17:24] <jsalisbury> Any other open discussions or questions?
[17:25] <jsalisbury> Last call
[17:25] <jsalisbury> #endmeeting
[17:25] <meetingology> Meeting ended Tue Dec 13 17:25:39 2011 UTC.
[17:25] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-13-17.00.moin.txt
[17:25] <cking> thanks jsalisbury
[17:25] <kamal> thanks jsalisbury
[17:25] <jsalisbury> Thanks, everyone
[23:54] <IAmNotThatGuy> 6 minutes