[09:17]  * bokjhv is away: /me requires JuanValdez. BRBack...
[16:00] <jamespage> o/
[16:01] <m_3> \o
[16:03] <arosales> Hello :-)
[16:03] <zul> hi hi hi hi hi hi
[16:03] <m_3> zul: supposed to be "ho ho ho"
[16:04] <smoser> o/
[16:04]  * m_3 can't get holiday songs out of the head
[16:04] <arosales> so we ready to get started :-)
[16:04] <hggdh> ~ô~
[16:04] <zul> m_3:  uh uh...en francais "ho ho ho"
[16:04] <jamespage> arosales, +1
[16:04] <arosales> #startmeeting ubuntu-server-team
[16:04] <meetingology> Meeting started Tue Dec  4 16:04:23 2012 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[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:04] <arosales> #topic Review ACTION points from previous meeting
[16:05] <arosales> hmm, where the action points updated from the previous meeting . . . ?
[16:05] <arosales> Daviey to fix the release bugs report
[16:05] <jamespage> thats the one
[16:05] <arosales> everyone look through http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:05]  * jamespage proposes we scrap that report
[16:05] <jamespage> its actually working aside from the fact it says 'Quantal'
[16:06] <jamespage> but we are not using the subscribe ubuntu-server-release method any more
[16:06] <arosales> hmm is the release team using that report still?
[16:06] <jamespage> use this report instead: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:06] <jamespage> arosales, thats not the report Daviey is mean't to be fixing
[16:06] <jamespage> arosales, thats this one -http://reqorts.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:07] <arosales> jamespage: to confirm what report were you suggesting to scrap?
[16:07] <jamespage> http://reqorts.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:07] <arosales> and that was the one Daviey was going to review, correct?
[16:08] <jamespage> he was going to fix yes
[16:08] <arosales> #action move to http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server for release bug tracking
[16:08] <meetingology> ACTION: move to http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server for release bug tracking
[16:08] <zul> i like that one less nova/openstack bugs
[16:08] <arosales> #action deprecate http://reqorts.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:08] <meetingology> ACTION: deprecate http://reqorts.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:09] <arosales> jamespage: is that the correct actions?
[16:09] <Daviey> +1, i agree with that
[16:09] <jamespage> +!
[16:09] <jamespage> +1 even
[16:09] <arosales> ok, got those logged as actoins
[16:09] <arosales> *actions :-)
[16:09] <arosales> #topic Raring Development
[16:09] <arosales> #link https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule
[16:10] <arosales> Alpha one coming up
[16:10] <arosales> Daviey: do we need to notify the release team of server participating in A1, or is that just for flavors?
[16:10] <jamespage> which server is not opting in to right?
[16:10] <arosales> December 6th
[16:10] <arosales> Alpha 1 (for opt-in flavors)
[16:11] <arosales> sounds like we need to opt in too then .. .
[16:11] <arosales> jamespage: to confirm server is _not_ going to opt into A1, correct?
[16:12] <jamespage> correct AFAIK
[16:12] <arosales> any other comments on A1?
[16:12] <smoser> i dont think we've had this discussion. i dont see a strong reason for a fire drill.
[16:12] <jamespage> +1
[16:12] <smoser> but my general feeling is that milestones are useful targets. but not if they're 2 days from now.
[16:12] <arosales> thats reasonable
[16:13] <arosales> smoser: so we should plan on A2 then?
[16:13] <arosales> February 7th
[16:13] <arosales> Alpha 2 (for opt-in flavors)
[16:13] <smoser> i would say we should definitely opt in to a feb 7 date.
[16:13] <arosales> utlemming: not cloud images will also not opt in for A1, but lets plan on A2 to be in-line with server
[16:13] <arosales> s/not/note/
[16:14] <jamespage> sounds sane to me
[16:14] <arosales> onto bugs
[16:14] <smoser> worthy note, next set of cloud images should reliably boot. thakns to mountall fix.
[16:14] <arosales> #subtopic Release Bugs
[16:14] <jamespage> smoser, \o/
[16:14] <utlemming> arosales: ack
[16:14] <arosales> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server 
[16:14] <arosales> since we are deprecating http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:15] <arosales> #action arosales update https://wiki.ubuntu.com/ServerTeam/Meeting/IRCCommands with new release bug link of  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server 
[16:15] <meetingology> ACTION: arosales update https://wiki.ubuntu.com/ServerTeam/Meeting/IRCCommands with new release bug link of  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server 
[16:15] <arosales> jamespage: smoser: should we at least step through the critical and maybe high bugs?
[16:16] <arosales> bug http://launchpad.net/bugs/1081212
[16:17] <arosales> looks to be fixed in trunk and 1.2 mass, but uncertain of Ubuntu
[16:17] <arosales> Daviey: ^
[16:17] <smoser> arosales, i'd say that the maas bugs are probalby not worth going through here.
[16:17] <jamespage> arosales, I'd ask roaksoax for general comment on the maas bugs; most of then are in hand upstream
[16:17] <jamespage> and will land in the stablization release
[16:18] <arosales> #action roaksoax to review MAAS bugs, and sync with upstream
[16:18] <meetingology> ACTION: roaksoax to review MAAS bugs, and sync with upstream
[16:18] <arosales> 1064224 is maas
[16:18] <Daviey> arosales: hola
[16:18] <arosales> 1069734 is maas
[16:18] <arosales> sorry /me just noticed the package column . .
[16:19] <arosales> so all these bugs are mass on the server list except http://launchpad.net/bugs/671065
[16:19] <arosales> and http://launchpad.net/bugs/1066845
[16:20] <arosales> 671065 looks like it wasn't going to be fixed in Quantal, any ideas on Raring?
[16:20] <arosales> jamespage: It looks like you commented on it being to late for Quantal and bumping to Raring
[16:20] <jamespage> arosales, I'll take it
[16:21] <arosales> ivoks was also working on it.
[16:21] <arosales> zul any comments on 1066845
[16:21] <arosales> low priority . .  .
[16:22] <zul> arosales: should already be fixed in raring
[16:22] <arosales> zul: could you please update the bug with that info?
[16:22] <zul> yep
[16:22] <arosales> thanks
[16:22] <arosales> thats it for bugs.
[16:23] <arosales> unless anyone has any others.
[16:23] <arosales> ok moving on
[16:23] <arosales> #link http://status.ubuntu.com/ubuntu-raring/ubuntu-server.html
[16:24]  * arosales noticed http://status.ubuntu.com/ubuntu-raring/ wasn't picking up the servercloud area
[16:24] <arosales> #action arosales to investigate why status tracker is not picking up servercloud area
[16:24] <meetingology> ACTION: arosales to investigate why status tracker is not picking up servercloud area
[16:25] <arosales> the "todos" are currently staying below the trend line, which is nice
[16:26] <arosales> actually the topics at http://status.ubuntu.com/ubuntu-raring/ubuntu-server.html don't look correct
[16:26] <arosales> hmm status tracker doesn't look to be in a healthy state, I don't think we can trust the info atm.
[16:27] <arosales> https://blueprints.launchpad.net/~ubuntu-server?searchtext=servercloud+r
[16:27] <arosales> sorry
[16:27] <arosales> #link https://blueprints.launchpad.net/~ubuntu-server?searchtext=servercloud+r
[16:28] <arosales> and possibly https://blueprints.launchpad.net/~ubuntu-server/+upcomingwork
[16:28] <arosales> if the BPs are targetted correctly ;-)
[16:28] <arosales> assuming the BPs are targetted correctly
[16:28] <arosales> WI due for A1 (dec 6) look to be done
[16:29] <arosales> as there are none ;-)
[16:29] <arosales> juju-core as some upcoming for dec 13
[16:29] <arosales> any BPs folks want to bring up here?
[16:30] <arosales> btw: smoser, jamespage: Daviey: are you guys targetting BPs?
[16:30] <jamespage> arosales, yes
[16:30] <jamespage> but they need to be reviewed as the month ones did not exists when we did it first time
[16:30] <arosales> cool, so perhaps https://blueprints.launchpad.net/~ubuntu-server/+upcomingwork may be a good review of upcoming work that needs addressed . ..
[16:30] <arosales> thoughts?
[16:30] <jamespage> Daviey, smoser: we need to review/approve the final few for the release and then retarget
[16:31] <smoser> yeah.
[16:31] <arosales> who would like the action there?
[16:31] <smoser> me is fine
[16:31] <jamespage> yes please
[16:32] <arosales> #action jamespage, smoser: we need to review/approve the final few BPs for the release and then retarget
[16:32] <meetingology> ACTION: jamespage, smoser: we need to review/approve the final few BPs for the release and then retarget
[16:32] <arosales> ok, any BPs folks would like to bring up?
[16:32] <arosales> #action jamespage, arosales confirm if https://blueprints.launchpad.net/~ubuntu-server/+upcomingwork should be used in ubuntu-server team IRC meeting for BP status
[16:32] <meetingology> ACTION: jamespage, arosales confirm if https://blueprints.launchpad.net/~ubuntu-server/+upcomingwork should be used in ubuntu-server team IRC meeting for BP status
[16:33] <arosales> moving to next topic
[16:33] <arosales> #topic Ubuntu Server Team Events
[16:33] <jimbaker> scalex cfp deadline is next monday (dec 10)
[16:34] <arosales> negronjl: will be at Lisa Dec 9-14 doing a BOF (http://www.usenix.org/event/lisa12/cfp/)
[16:34] <m_3> ah, thanks for the reminder jim
[16:34] <arosales> m_3: and jcastro at scale it looks like from https://juju.ubuntu.com/Events/
[16:34] <arosales> any other events for server?
[16:35] <arosales> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:35] <hggdh> hi
[16:36] <hggdh> no real news, except that I want to look at the ec2 test automation to drive kernel tests. Will chat with jamespage later on
[16:36] <hggdh> ..
[16:36] <arosales> hggdh: is that via UTAH?
[16:36] <hggdh> arosales: no, it is outside UTAH
[16:36] <hggdh> arosales: move to UTAH will depend on the kernel team
[16:37] <arosales> hggdh: is cloud deployments on UTAH's road map?
[16:37] <hggdh> arosales: it is beneath the horizon right now, but it has been considered
[16:38] <arosales> hggdh: ok, thanks for the update. We'll also ask smb about kernel and utah in the next topic :-)
[16:38] <arosales> any questions/comments for hggdh?
[16:38] <hggdh> heh
[16:38] <arosales> thanks hggdh for the update
[16:38] <arosales> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:38] <smb> Hello. I wanted to bring up two things. First to clarify the slight confusion I was causing last time with respect to rolling kernel. So the ISOs for 12.04.2 will have the quantal kernel and quantal x stack but that is under the name of enablement stack, not the rolling kernel as I incorrectly brought up.
[16:39] <smb> The plan with rolling kernel updates really has been put back.
[16:39] <hggdh> smb: so default kernel keeps the same, correct?
[16:39] <smb> https://wiki.ubuntu.com/KernelTeam/Specs/QuantalLTSEnablementStack  (#9)
[16:39] <arosales> smb: so folks can keep on the precise kernel, and still get updates
[16:39] <smb> If they use the 12.04 or 12.04.1 cds for install and upgrade yes
[16:40] <smb> When using the 12.04.2 cds they get the newer kernel
[16:40] <arosales> smb: great, thanks for the clarification
[16:40]  * hggdh is quite confused now
[16:40] <arosales> #link https://wiki.ubuntu.com/KernelTeam/Specs/QuantalLTSEnablementStack
[16:40] <smb> Ok, the second thin, I am not sure it was already discussed
[16:40] <smb> (brain unfortunately has multitasking issues)
[16:40] <smb> So right now Xen-4.2 is in raring-proposed
[16:41] <smb> This causes xen-api (xcp-xapi) to have issues because the xl api is incompatible
[16:41] <smb> And this is probably also keeping nova back in proposed
[16:42] <smb> AFAIK this is known to the xcp guys but until resolved everything is kept back in proposed
[16:42] <smb> ..
[16:42] <arosales> hggdh: any clearer now?
[16:42] <hggdh> aye
[16:43] <arosales> I think the important piece for server is point 9 in https://wiki.ubuntu.com/KernelTeam/Specs/QuantalLTSEnablementStack
[16:43] <hggdh> but I do not see much difference from before -- new installs get the new kernel, updates from 12.04/12.04.1 get the old
[16:43] <arosales> in that folks can continue to use the precise kernel and get updates
[16:44] <smb> I think the big difference is what and how things get enforced. The rolling kernel plan would have moved people automatically
[16:44] <arosales> I think the main point is an LTS getting non-LTS stack option (ie rolling)
[16:44] <hggdh> yes, and the need to support both on all
[16:45] <arosales> smb: ya forcing folks to upgrade their LTS kernel would have been a bit scary, thanks for keeping the option to stay on the precise kernel.
[16:45] <arosales> smb: hggdh had a question regarding UTAH and kernel testing
[16:46] <smb> yep
[16:46] <arosales> smb: is kernel team going to be using UTAH in their testing?  (perhaps smb can provide some more context)
[16:46] <arosales> sorry perhaps hggdh can provide more context :-)
[16:46] <smb> arosales, I can forward that question to the people doing it
[16:46] <smb> :)
[16:46] <arosales> smb: ok thanks
[16:47] <arosales> any other questions for smb?
[16:47] <hggdh> I do not think the kernel team is looking at porting to UTAH right now
[16:47] <arosales> smb: thanks for the update
[16:47] <arosales> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:48] <rbasak> The highbank installer is broken in quantal and we should have a fix shortly (bug 1084106). Nothing else to report. Any questions for me?
[16:48] <arosales> rbasak: any news on the ARM front ?
[16:48] <arosales> I'll take it no further questions for rbasak.
[16:48] <arosales> rbasak: thanks for the update.
[16:48] <arosales> #topic Open Discussion
[16:49] <arosales> any topics folks would like to discuss
[16:49] <arosales> going 1 . .
[16:49] <arosales> 2 . .  .
[16:49] <arosales> 3. . .
[16:50] <arosales> #topic Announce next meeting date and time
[16:50] <TheLordOfTime> guess not :P
[16:50] <arosales> :-)
[16:50] <arosales> next meeting is: Tuesday 2012-12-11 at 1600 UTC
[16:50] <arosales> thanks for joining, and your time
[16:50] <arosales> #endmeeting
[16:50] <meetingology> Meeting ended Tue Dec  4 16:50:44 2012 UTC.
[16:50] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-12-04-16.04.moin.txt
[16:50] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-12-04-16.04.html
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Dec  4 17:00:33 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/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring
[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] <ppisati> o/
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <sforshee> o/
[17:00] <sconklin> o/
[17:01] <henrix> o/
[17:01] <cking> o/
[17:01] <herton> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing to report this week.
[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:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> jsalisbury: meep, 2secs
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> || apw         || hardware-r-kernel-config-review       || 12 work items ||
[17:02] <ogasawara> ||             || hardware-r-kernel-misc                ||  3 work items ||
[17:02] <ogasawara> ||             || foundations-r-secure-boot             ||  2 work items ||
[17:02] <ogasawara> ||             || desktop-r-clean-old-kernels           ||  1 work item  ||
[17:02] <ogasawara> || cking       || hardware-r-kernel-config-review       ||  1 work item  ||
[17:02] <ogasawara> || ogasawara   || hardware-r-kernel-config-review       ||  2 work items ||
[17:02] <ogasawara> ||             || hardware-r-arm-power-measurement      ||  1 work item  ||
[17:02] <ogasawara> || ppisati     || hardware-r-kernel-config-review       ||  1 work item  ||
[17:02] <ogasawara> ||             || hardware-r-kernel-version-and-flavors ||  2 work items ||
[17:03] <ogasawara> || sconklin    || hardware-r-arm-power-measurement      ||  3 work items ||
[17:03] <ogasawara> || smb         || hardware-r-kernel-delta-review        ||  1 work item  ||
[17:03] <ogasawara> || rtg         || foundations-r-secure-boot             ||  1 work item  ||
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: Raring Development Kernel (ogasawara)
[17:03] <ogasawara> We have recently rebased the raring kernel to upstream v3.7-rc8.  We
[17:03] <ogasawara> plan to upload today.
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara>  * Tues Dec 18 - 13.04 Month 2 Milestone - (~2 weeks)
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's (henrix)
[17:04] <henrix> Currently we have 29 CVEs on our radar, with 1 CVE added and 0 CVEs retired this week.
[17:04] <henrix> See the CVE matrix for the current list:
[17:04] <henrix> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:04] <henrix> Overall the backlog has decreased slightly this week:
[17:04] <henrix> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:04] <henrix> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:04] <henrix> ..
[17:04] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)
[17:04] <henrix> Here is the status for the main kernels, until today (December 04):
[17:04] <henrix>  * Hardy - In Preparation; 1 CVEs; (1 commits)
[17:04] <henrix>  * Lucid - In Preparation; 1 CVEs; (1 commits)
[17:04] <henrix>  * Oneiric - In Preparation; 1 CVEs; 2 upstream stable release(s); (78 commits)
[17:04] <henrix>  * Precise - In Preparation; 1 CVEs; 1 upstream stable release(s); (87 commits)
[17:04] <henrix>  * Quantal - In Preparation; 1 CVEs; 1 upstream stable release(s); (308 commits)
[17:04] <henrix> Current opened tracking bugs details:
[17:04] <henrix>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <henrix> For SRUs, SRU report is a good source of information:
[17:04] <henrix>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <henrix> Future stable cadence cycles:
[17:04] <henrix>  * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:05] <henrix> ..
[17:05] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Dec  4 17:05:34 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-12-04-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-12-04-17.00.html
[18:59] <shPikachu> hi ppl
[19:00] <shPikachu> im trying to connect 7 FTDI rs232- usb adapters to my pc using a hub
[19:00] <shPikachu> each has a data stream
[19:01] <shPikachu> when i plug the 7th while the others 6 are plugged in, it doesnt xmit or receives
[19:01] <pleia2> shPikachu: this channel is for team meetings, you want #ubuntu for support
[19:01] <shPikachu> however, when i plug it alone, it works
[19:01] <shPikachu> ok thanks