[15:58] <Ursinha> I will chair the meeting this time!
[15:59] <rbasak> \o/
[15:59]  * rbasak is safe for another week
[15:59] <m_3_> o/
[15:59] <mercsniper> o/
[15:59] <Ursinha> :)
[16:00] <Ursinha> sorry for being absent last weeks
[16:00] <Ursinha> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Oct  2 16:00:07 2012 UTC.  The chair is Ursinha. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16: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
[16:00] <Ursinha> hello all
[16:00] <Ursinha> are you all here?
[16:00] <SpamapS> no
[16:00] <SpamapS> but keep going
[16:00] <Ursinha> #topic Review ACTION points from previous meeting
[16:00] <Ursinha> * jamespage to look into aligning release team and server team trackign reports
[16:01] <jamespage> Ursinha, golly -is that still on the list....
[16:01] <Ursinha> jamespage, hehe... this one involves me, right?
[16:01] <jamespage> yep
[16:01] <jamespage> and as we are sooo bad at communicating with each other...
[16:01] <Ursinha> [action] jamespage and Ursinha to look into aligning release team and server team tracking reports
[16:01] <meetingology> ACTION: jamespage and Ursinha to look into aligning release team and server team tracking reports
[16:01] <Ursinha> it's mine too now :)
[16:02] <Ursinha> we can catch up tomorrow, will try to find a spot for us to talk
[16:02] <Ursinha> #topic Quantal Development
[16:02] <Ursinha> #link https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule
[16:02] <Ursinha> #subtopic Release Bugs
[16:03] <Ursinha> I don't think this works?
[16:03] <Ursinha> #link http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:03] <Ursinha> so, let's see
[16:04] <JoseeAntonioR> Ursinha: you won't get a reply for link, or for subtopic
[16:04] <Ursinha> that's different
[16:04] <Ursinha> thanks JoseeAntonioR
[16:04] <Ursinha> I'm looking at the bugs
[16:05] <Ursinha> so, there is bug 1017847
[16:06] <Ursinha> are we working on it for this cycle? it has the rls-q-incoming tag
[16:06] <Ursinha> serge isn't here
[16:06] <hallyn> sure i am
[16:06] <hallyn> last i tried i couldn't reproduce due to other failures - i should try again...
[16:06] <Ursinha> ah!
[16:06] <Ursinha> :)
[16:07] <Ursinha> hallyn, if we're not fixing, we might want to remove the tag or add another one to say we're not fixing this cycle
[16:07] <Ursinha> if is a valid issue, of course
[16:07] <hallyn> the issue definately was valid at one point
[16:08] <Ursinha> right..
[16:09] <hallyn> (added to my list)
[16:09] <Ursinha> we have two critical bugs, one is fix committed by smoser
[16:09] <Ursinha> other is critical, SpamapS set it to critical
[16:09] <Ursinha> bug 1047520
[16:09] <Ursinha> SpamapS, are you fixing that?
[16:10] <smoser> what is the one that is fix-committed by me ?
[16:10] <Ursinha> bug 1049177
[16:11] <Ursinha> the quantal task
[16:11] <Ursinha> for maas
[16:11] <smoser> roaksoax, should that be fix-released in maas ?
[16:12] <smoser> ie, do we have a maas package that uses its own dhcp server?
[16:12] <SpamapS> Ursinha: yes I'll take a look at that
[16:12] <roaksoax> smoser: i think we do, i haven't looked at the latest changes made to that package
[16:12] <roaksoax> (maas-dhcp(
[16:12] <Ursinha> thanks Sp4rKy
[16:12] <Ursinha> oops
[16:12] <Ursinha> SpamapS, even
[16:13] <Sp4rKy> :)
[16:13] <Ursinha> (sorry Sp4rKy)
[16:13] <smoser> Ursinha, well, either way, its under control
[16:13] <smoser> (it is fixed in daily ppa)
[16:13] <Ursinha> cool
[16:13] <Ursinha> do you have any issues you want to bring into attention?
[16:14] <SpamapS> bug 1047520 is actually already Fix Released
[16:14] <SpamapS> so, woot :)
[16:15] <Ursinha> cool :)
[16:15] <Ursinha> I found another critical bug: bug 1044632
[16:16] <Daviey> OT: /me chimes in that he is only partially here atm.
[16:16] <jimbaker> Ursinha, that's part of the 0.5.2 release of juju
[16:16] <Ursinha> jimbaker, I ask because it's targeted to the release, only wanted to know if that bug is going to make it or if it's going to be sru'd later
[16:17] <jimbaker> SpamapS is currently working on a micro release that will be in a sru
[16:17] <Ursinha> ah, right
[16:17] <jimbaker> actually bad phrased - 0.5.2 is that micro release, then to included in an upcoming sru
[16:18] <Ursinha> so we might want to target that to quantal-updates,right?
[16:18] <Daviey> SpamapS: any news on using ubuntu-cloud lxc template for local provider ?
[16:19] <jimbaker> Ursinha, that's a sru for precise. it should be part of the final for quantal
[16:19] <Ursinha> jimbaker, right, thanks for the info
[16:19] <Ursinha> I'll talk to people about bugs outside the meeting, otherwise this will take forever
[16:19] <Ursinha> will move on to blueprints
[16:19] <Ursinha> #subtopic Blueprints
[16:20] <Ursinha> #link http://status.ubuntu.com/ubuntu-quantal/ubuntu-server.html
[16:20] <Ursinha> the link that Daviey hates
[16:21] <Ursinha> that link is indeed not nice if you want to be objective :/
[16:22] <SpamapS> Daviey: yes, branch is proposed and in review today actually
[16:22] <SpamapS> jimbaker: format 2 does not exist in 0.5.x
[16:22] <SpamapS> jimbaker: that bug is only relevant in 0.6
[16:23] <SpamapS> Ursinha: we don't need to target that at quantal-updates. I have a final drop of Juju code planned for later this week.
[16:23] <Ursinha> SpamapS, awesome then
[16:23]  * SpamapS apologizes for lagging :-P
[16:23] <Ursinha> :)
[16:24] <Ursinha> that link is somehow impossible to follow up, the blueprints one, so please remember to update yours if haven't already
[16:24] <Ursinha> I'll move on
[16:24] <Ursinha> #topic Ubuntu Server Team Events
[16:25] <Ursinha> * CFP deadlines
[16:25] <Ursinha>  ** SoCal Linux Expo (Deadline: Dec. 10) http://www.socallinuxexpo.org/cfp
[16:26] <Ursinha> any other events?
[16:27] <Ursinha> I'll take that as a no :)
[16:27] <Ursinha> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:27] <hggdh> hi
[16:27] <Ursinha> hi hggdh, any updates for us?
[16:28] <hggdh> just a question from me -- the iSCSI and MAAS tests for the ISO -- it seems you want us to run it
[16:28] <hggdh> we need to have the details on how to do it, can you please pass them over?
[16:29] <hggdh> and, additionally, I found an easy way to have the ISO dns-server tests to actually execute, I will be proposing a merge soon for USIT
[16:29] <hggdh> ..
[16:29] <Ursinha> who asked you that, hggdh?
[16:29] <hggdh> Ursinha: nobody asked us that, but then the server team did not run them on the Beta 2 tests
[16:30] <Ursinha> ah, oops
[16:30] <Ursinha> Daviey, who could provide the info to hggdh to run these tests?
[16:31] <jamespage> hggdh, I can pass you info on the iscsi tests
[16:31] <hggdh> oh, an additional point on MAAS
[16:32] <Ursinha> [action] jamespage to provide info to hggdh about how to run iSCSI and MAAS tests for the ISO
[16:32] <meetingology> ACTION: jamespage to provide info to hggdh about how to run iSCSI and MAAS tests for the ISO
[16:32] <hggdh> it now seems to support virsh, but there is no docs on how to fill in the fields on the "Add Node" screen
[16:32] <hggdh> and the "Doc" button on the page does not even talk about virsh...
[16:34] <Ursinha> roaksoax or smoser, ^^
[16:35] <roaksoax> i think we would need to check that with iupstream I've only worked with IPMI
[16:35] <roaksoax> but should be pretty straight forward
[16:36] <smoser> i've not tested current maas with virsh
[16:36] <smoser> but it is on the list of things i'd like to know how to do
[16:37] <Daviey> Ursinha: hggdh should grab me out of meeting :)
[16:38] <Ursinha> cool :)
[16:38] <Ursinha> is that enough information for you, hggdh?
[16:38] <hggdh> yes it is :-)
[16:38] <Ursinha> great :)
[16:39] <Ursinha> moving on, then
[16:39]  * hggdh prepares the net to grab Daviey
[16:39] <Ursinha> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:39] <Ursinha> hello smb
[16:39] <smb> I don't have much to report right now... I hope I am finally homing in on bug 1021471. Just compiling a new test kernel for that right now. Should be on people by the time this meeting ends...
[16:39] <smb> ..
[16:39] <SpamapS> smb: thanks for fighting to get that going. Its quite important for juju. :)
[16:39] <SpamapS> and really for LXC users
[16:40] <Daviey> +1
[16:40] <Ursinha> great, thanks smb
[16:40] <Ursinha> any questions for smb?
[16:41] <Ursinha> okay, moving on
[16:41] <Ursinha> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:41] <rbasak> Quantal on ARM is looking good. MAAS on ARM is almost done too - all the critical pieces are written now, appear to be working and are in various stages in the pipeline for landing in the next week.
[16:41] <rbasak> Any questions for me?
[16:42] <Ursinha> maybe not :)
[16:42] <Ursinha> thanks rbasak
[16:42] <Ursinha> #topic Open Discussion
[16:42] <Ursinha> discuss!
[16:43] <Ursinha> you are making me sad today, people
[16:43] <Ursinha> :)
[16:43] <zul> gee thanks
[16:43] <Ursinha> lol
[16:43] <Ursinha> no one is into discussing today :)
[16:43] <Ursinha> #topic Announce next meeting date and time
[16:43] <Ursinha> sooo
[16:44] <SpamapS> Ursinha: thanks!!
[16:44] <SpamapS> oh damn I thought that was EOM
[16:44] <Ursinha> Next meeting will take place Oct 9th, same bat-channel
[16:44] <Ursinha> who's next in the line
[16:45] <Ursinha> if that is a line, so jimbaker is our next chair
[16:45] <Ursinha> jimbaker, is that ok for you?
[16:45] <Ursinha> that should do :P
[16:45] <Ursinha> #endmeeting
[16:45] <meetingology> Meeting ended Tue Oct  2 16:45:40 2012 UTC.
[16:45] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-02-16.00.moin.txt
[16:45] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-02-16.00.html
[16:45] <Ursinha> thanks people
[16:45] <SpamapS> FYI, jim did last week, so its from the other end
[16:46] <SpamapS> Ursinha: anyway, ^5 well done, thanks again
[16:46] <Ursinha> so next week is rbasak :)
[16:47] <rbasak> Ursinha: not jimbaker first?
[16:47]  * rbasak doesn't mind
[16:47] <rbasak> But knowing in advance is helpful
[16:47] <Ursinha> rbasak, SpamapS said he did it last week, so I have to fix that queue :/
[16:49] <jimbaker> Ursinha, rbasak, cool, yes, i chaired last week, so someone else is next :)
[16:49] <rbasak> ah yes
[16:49] <rbasak> OK, so me next week it is
[16:49] <zul> the more people who pile in front of me the better :)
[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 Oct  2 17:00:07 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[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/Quantal
[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> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <henrix> o/
[17:00] <dhillon-v10> o/
[17:00] <sconklin> o/
[17:00] <herton> o/
[17:00] <ogasawara> o/
[17:00] <rtg> o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> Nothing new to report this week.
[17:01]  * smb runs in
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team-ubuntu-12.10.html
[17:01] <ogasawara> || apw         || hardware-q-kernel-config-review || 3 work item  ||
[17:01] <ogasawara> ||             || hardware-q-kernel-delta-review  || 2 work items ||
[17:01] <ogasawara> ||             || hardware-q-kernel-misc          || 1 work item  ||
[17:01] <ogasawara> || ogasawara   || hardware-q-kernel-misc          || 2 work item  ||
[17:01] <ogasawara> ||             || hardware-q-kernel-version-and-flavors || 2 work items ||
[17:01] <ogasawara> ||             || desktop-q-xorg-lts-updates      || 1 work item  ||
[17:01] <ogasawara> apw and I will review and close our remaining work items as we approach
[17:01] <ogasawara> final release.
[17:01] <ogasawara> ..
[17:01] <jsalisbury> [TOPIC] Status: Quantal Development Kernel (ogasawara)
[17:02] <ogasawara> Last week we uploaded the 3.5.0-16.[24,25] kernels.  With Quantal kernel
[17:02] <ogasawara> freeze approaching in 2 days, we will upload one final kernel before
[17:02] <ogasawara> freeze by EOD tomorrow, Wed Oct 3.  Following kernel freeze all patches
[17:02] <ogasawara> are subject to the SRU policy and only critical bug fixes will warrent
[17:02] <ogasawara> an upload. Non critical bug fixes and changes will be targetted to the
[17:02] <ogasawara> first Quantal SRU kernel.
[17:02] <ogasawara> As usual, all kernels will also get uploaded to the q-lts-backport [1]
[17:02] <ogasawara> PPA to help facilitate testing of the 12.10 kernel in 12.04.  We welcome
[17:02] <ogasawara> anyone to please install, test, and let us know your feedback.
[17:02] <ogasawara> [1] https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara>  * Thurs Oct 4 - Kernel Freeze (2 days)
[17:02] <ogasawara>  * Thurs Oct 9 - Final Freeze (~1 week)
[17:02] <ogasawara>  * Thurs Oct 18 - 12.10 Final (~2 weeks)
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's (sconklin)
[17:02] <sconklin> == 2012-10-02 (weekly) ==
[17:02] <sconklin> Currently we have 41 CVEs on our radar, with no CVEs added or retired this week.
[17:02] <sconklin> See the CVE matrix for the current list:
[17:02] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <sconklin> Overall the backlog has decreased slightly this week:
[17:02] <sconklin> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:02] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:02] <sconklin> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Oneiric/Natty/Lucid/Hardy (bjf/herton/henrix)
[17:03] <henrix> Here is the status for the main kernels, until today (October 02):
[17:03] <henrix>  * Hardy - In Testing; 1 CVEs; (1 commits)
[17:03] <henrix>  * Lucid - In Testing; 3 CVEs; (12 commits)
[17:03] <henrix>  * Oneiric - In Testing; 2 CVEs; 1 upstream stable release(s); (54 commits)
[17:03] <henrix>  * Precise - In Verification; 1 CVEs; 2 upstream stable release(s); (234 commits)
[17:03] <henrix> Current opened tracking bugs details:
[17:03] <henrix>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <henrix> For SRUs, SRU report is a good source of information:
[17:03] <henrix>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <henrix> Future stable cadence cycles:
[17:03] <henrix>  * https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[17:03] <henrix> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:03] <dhillon-v10> o/
[17:04] <jsalisbury> dhillon-v10, go ahead
[17:04] <dhillon-v10> hi all, okay so recently at KS there was a lot of discussion about module signing and I've been working on an approach i'd like to present and maybe get some feedback?
[17:05] <rtg> dhillon-v10, how is your approach different then david howell's ?
[17:05] <dhillon-v10> the idea is a hybrid between what chrome os does (I saw some of Kees's work) and what David Howell posted
[17:05] <dhillon-v10> rtg: just getting to t hat
[17:05] <dhillon-v10> *that
[17:05] <dhillon-v10> so specifically, I'm referring to patch 19 that in his patchset, that allows signatures to be added in the build process
[17:06] <rtg> dhillon-v10, so, given the complexity of module signing you'd likely be better off posting your ideas on teh kteam mailing list
[17:06] <dhillon-v10> rtg: do you think it's better to post there? alright then in that case i suppose i'm done here
[17:07] <rtg> dhillon-v10, we _are_ considering module signing, but just haven't fully thought it all through
[17:07] <sconklin> Yes, that also preserves the discussion and gives people in different time zones an ability to review it
[17:07] <rtg> ..
[17:08] <jsalisbury> Any other open discussion or questions?
[17:08] <dhillon-v10> rtg: right, the idea here is not to include all of David's signing stuff because it's very complicated, and I think I may have a simpler approach similar to how in the UEFI stuff, we are getting signed bootloaders IIRC
[17:08] <dhillon-v10> ..
[17:09] <jsalisbury> Thanks everyone
[17:09] <jsalisbury> #endmeeting
[17:09] <meetingology> Meeting ended Tue Oct  2 17:09:02 2012 UTC.
[17:09] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-02-17.00.moin.txt
[17:09] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-02-17.00.html
[17:09] <sconklin> thanks jsalisbury