[16:01] <arosales> Hello
[16:01] <arosales> I'll be chairing today's Server team meeting
[16:01] <smoser> o./
[16:01] <adam_g> o/
[16:01]  * arosales grabs the commands
[16:01] <roaksoax> o/
[16:01] <arosales> #startmeeting ubuntu-server-team
[16:01] <meetingology> Meeting started Tue Nov 26 16:02:08 2013 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <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:02] <arosales> #topic Review ACTION points from previous meeting
[16:02] <arosales> No actions from previous meeting
[16:02] <arosales> #topic Trusty Development
[16:03] <arosales> #link https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[16:04] <arosales> we have an alpha coming up I think . . .
[16:04] <arosales> Dec 19th
[16:04] <arosales> opt in for flavors
[16:04] <arosales> smoser, jamespage is server opting in?
[16:04]  * arosales doesn't see utlemming for cloud image confirmation
[16:05] <jamespage> as a core flavor we don't normally opt in - I'm happy to stick with that for alpha1
[16:05] <arosales> jamespage, ack
[16:05] <arosales> #subtopic Release Bugs
[16:05] <arosales> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server
[16:05] <smoser> jamespage, well, i like to create cloud images.
[16:06] <arosales> smoser, I think cloud images has done an alpha in the past .  . .
[16:06] <smoser> i'd like for us to opt in for alpha1 cloud images, with some actual targets.
[16:06] <jamespage> sure
[16:06] <smoser> the seed-review and gpt
[16:06] <smoser> jamespage, have you done a seed-review email ?
[16:06] <jamespage> smoser, urgh - not yet
[16:06] <arosales> #action smoser sync with utlemming on building cloud images for alpha 1, targets = seed-review, gpt
[16:06] <meetingology> ACTION: smoser sync with utlemming on building cloud images for alpha 1, targets = seed-review, gpt
[16:07] <jamespage> arosales, please action me todo that asap
[16:07] <arosales> will do
[16:07] <arosales> #action jamespage do seed-review email
[16:07] <meetingology> ACTION: jamespage do seed-review email
[16:07] <arosales> onto bugs :-)
[16:07] <arosales> got two high @ http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server
[16:08] <arosales> no critical
[16:08] <arosales> http://launchpad.net/bugs/1243762
[16:08] <jamespage> that will stick on the report until either we decide not to or it gets in main
[16:08] <arosales> jamespage, ok, thanks
[16:08] <arosales> bug 1062336
[16:09] <arosales> zul ^
[16:09] <rbasak> We should perhaps track bug 1248283, since at the moment it seems to affect all MAAS/juju on Saucy, and presumably Trusty too. I don't know how much this needs to be tracked by us as opposed to juju upstream, though.
[16:09] <arosales> nevermind jamespage looks like your marked won't fix
[16:09] <jamespage> zul, that will get fixed up under the kvm packaging review
[16:09] <zul> rbasak:  its been removed in trusty
[16:10] <rbasak> zul: what's been removed exactly?
[16:10] <zul> arosales: the xcp stuff has been removed in nova
[16:10] <zul> rbasak:  sorry not you :)
[16:10] <arosales> zul, thanks
[16:10] <arosales> rbasak, you are referring to https://bugs.launchpad.net/maas/+bug/1248283
[16:11] <rbasak> Yes
[16:11] <arosales> good one to track
[16:12] <arosales> jamespage, which team to we add to get in on the bug tracking list?
[16:13] <arosales> ~ubuntu-server ?
[16:13] <arosales> smoser, ^
[16:13] <jamespage> no - dbus should not be on the server list
[16:14] <jamespage> raise a task for juju-core - I think that will do it
[16:14] <smoser> there is a task for juju-core thre.
[16:14] <arosales> juju-core has a task
[16:15] <arosales> while we work on that is there any other bugs we want to cover?
[16:15] <jamespage> juju-core in Ubuntu
[16:15] <arosales> there are a few other mediums and lows
[16:15] <jamespage> not upstream
[16:15] <rbasak> I think you might need a packaging task against a package that ~ubuntu-server subscribes to that also has a Trusty task.
[16:15] <rbasak> I'm not sure this is a good way to do it, mind.
[16:15] <arosales> jamespage, ah ok
[16:15] <jamespage> rbasak, is the bug in dbus?
[16:15] <rbasak> Debatable. I'd say the primary bug is in juju-core.
[16:16] <rbasak> (or perhaps the MAAS provider in juju if that's separate)
[16:16] <arosales> rbasak, could you add a task for juju-core in Ubuntu?
[16:16] <rbasak> dbus would ideally not fail, and ideally log a message explaining what happens when it does.
[16:17] <rbasak> But juju should not try to restart networking. It doesn't need to do that anyway.
[16:17] <jamespage> rbasak, raise a distro bug task for Ubuntu and target to trusty
[16:17] <jamespage> so we can track it
[16:17] <rbasak> ack
[16:17] <arosales> rbasak, thanks
[16:17] <arosales> any other bugs we should cover
[16:17] <rbasak> Done. Importance?
[16:18] <arosales> got the highs and critical ones done @ http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server
[16:18] <rbasak> I'll say Triaged/High.
[16:18] <arosales> rbasak, thanks for brining in one we needed to track too
[16:18] <arosales> ok we covered those
[16:18] <arosales> not the others on the list are openstack
[16:18] <arosales> less websockify
[16:18] <arosales> moving on
[16:19] <arosales> #subtopic Blueprints
[16:19] <arosales> jamespage, to my failing did you create a topic bp?
[16:19] <jamespage> yes
[16:19] <arosales> #link http://status.ubuntu.com/ubuntu-s/group/topic-t-servercloud-overview.html
[16:19] <arosales> ah and you must have updated the notes
[16:19] <arosales> well done -- thank you
[16:19] <arosales> :-)
[16:20] <arosales> http://status.ubuntu.com/ubuntu-s/group/topic-t-servercloud-overview.html
[16:20] <arosales> hmm not loading for me atm
[16:20] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/topic-t-servercloud-overview
[16:20] <arosales> working for others?
[16:21] <arosales> hmm http://status.ubuntu.com/ubuntu-t/ looks to may need a kick
[16:21] <jamespage> arosales, no
[16:21]  * arosales doesn't see any topic BPs there
[16:21] <jamespage> arosales, gaughen: we need to go through all blueprints and priortize and accept for trusty
[16:21] <jamespage> so as its only UDS + 2 days really
[16:21] <arosales> #action jamespage, gaughen review blueprints and accept for trusty
[16:21] <meetingology> ACTION: jamespage, gaughen review blueprints and accept for trusty
[16:22] <gaughen> okay
[16:22] <smoser> yeah.
[16:22] <jamespage> can respectfully suggest that everyone write up their blueprints from last week by thursday
[16:22] <jamespage> using the blueprint spec
[16:22] <jamespage> and mark 'Pending Approval'
[16:22] <arosales> #action gaughen file bug with status.u.c to get ubuntu server topic tracking in there
[16:22] <meetingology> ACTION: gaughen file bug with status.u.c to get ubuntu server topic tracking in there
[16:22] <arosales> gaughen, I hope you don't mind that action
[16:22] <jamespage> then smoser, gaughen and I will know which ones to review
[16:23] <arosales> gaughen, https://bugs.launchpad.net/launchpad-work-items-tracker/+filebug
[16:23] <arosales> gaughen, ping me if you have any questions
[16:23] <jamespage> so I guess for folks in the US that means be end of wednesday
[16:23] <jamespage> ....
[16:23] <jamespage> sorry
[16:23] <gaughen> nope don't mind but i will have questions :-)
[16:23] <jamespage> actually - this makes no sense
[16:23] <arosales> #action all: write up blueprints, and have them ready for review by November 28
[16:23] <meetingology> ACTION: all: write up blueprints, and have them ready for review by November 28
[16:23] <jamespage> end of week - then we can review early next week
[16:23] <smoser> end of week.
[16:24] <smoser> (which may be in a few hours for some US folk)
[16:24] <arosales> # all write up bluerprints, using blueprint spec, mark 'pending approval', and have complete by November 29
[16:25] <arosales> any other BP topics?
[16:25] <arosales> #topic Server & Cloud Bugs (caribou)
[16:25] <arosales> caribou any bugs to bring up here that we didn't already cover?
[16:26]  * arosales doesn't see caribou online atm
[16:26] <arosales> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:26] <psivaa> No updates from us,
[16:26] <arosales> psivaa, ok thanks
[16:26] <arosales> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:28] <arosales> smb any updates?
[16:28]  * arosales doesn't seem smb here atm
[16:28] <arosales> any folks from kernel
[16:29] <arosales> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:29] <rbasak> No updates from me. Any questions?
[16:29] <arosales> any questions for rbasak ?
[16:29] <arosales> #topic Ubuntu Server Team Events
[16:29] <arosales> we had a lot of events we just came back from
[16:30] <arosales> ODS, uVDS, RubyConf, AWS re:Invent
[16:30] <arosales> I don't know of any upcoming in the next week
[16:30] <arosales> any other folks have any events to bring up here?
[16:30] <arosales> #topic Open Discussion
[16:31] <arosales> any other agenda items?
[16:31] <arosales> going once
[16:31] <arosales> twice
[16:31] <arosales> thrice
[16:32] <arosales> #topic Announce next meeting date and time
[16:32] <arosales> NEXT MEETING: Tuesday 2013-12-03 at 1600 UTC
[16:32] <arosales> Thanks for joining the ubuntu server team meeting!
[16:32] <arosales> #endmeeting
[16:32] <meetingology> Meeting ended Tue Nov 26 16:32:50 2013 UTC.
[16:32] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-16.02.moin.txt
[16:32] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-16.02.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] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <meetingology> Meeting started Tue Nov 26 17:00:29 2013 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/Trusty
[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] <rtg> o/
[17:00] <kamal> o/
[17:00] <henrix> o/
[17:00] <cking> o/
[17:00] <sforshee> o/
[17:00] <bjf> o/
[17:01] <ppisati> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing new 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:01] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> 2 secs
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-t/canonical-kernel-distro-team.html
[17:02] <ogasawara> While marginally useful for tracking work items in the past, the above
[17:02] <ogasawara> links are completely useless at the moment.  I have manually reviewed
[17:02] <ogasawara> work items from the core-1311-kernel and core-1311-hwe-plans blueprints.
[17:02] <ogasawara> However, beyond those two, I'm oblivious to what other work our team or
[17:02] <ogasawara> individuals were signed up for.
[17:02] <ogasawara> || apw   || core-1311-kernel    || 1 work ite ||
[17:02] <ogasawara> || cking || core-1311-kernel    || 2 work item ||
[17:02] <ogasawara> || rtg   || core-1311-hwe-plans || 1 work item ||
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Trusty Development Kernel (ogasawara)
[17:02] <ogasawara> For those unaware, the ubuntu-trusty git repo is open and available at:
[17:02] <ogasawara> git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git .  The master branch is
[17:03] <ogasawara> currently tracking the latest 3.12.1 upstream stable kernel while the
[17:03] <ogasawara> unstable branch has most recently been rebased to v3.13-rc1.  We shall
[17:03] <ogasawara> move our master branch to track v3.13 after some baking.  We will also
[17:03] <ogasawara> upload to the archive when it's ready.
[17:03] <ogasawara> -----
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara> [LINK] https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[17:03] <ogasawara> Thurs Dec 12 - 12.04.4 Kernel Freeze (~2 weeks away)
[17:03] <ogasawara> Thurs Dec 23 - 12.04.4 Final Release (~8 weeks away)
[17:03] <ogasawara> [LINK] https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[17:03] <ogasawara> Thurs Dec 19 - Alpha 1 (~3 weeks away)
[17:03] <ogasawara> Thurs Jan 23 - Alpha 2 (~ 8 weeks away)
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's
[17:03] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:03] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <jsalisbury> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Saucy/Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:03] <bjf> Status for the main kernels, until today (Nov. 26):
[17:03] <bjf>   *   Lucid - Regression Testing
[17:03] <bjf>   * Precise - Regression Testing
[17:03] <bjf>   * Quantal - Regression Testing
[17:03] <bjf>   *  Raring - Regression Testing
[17:03] <bjf>   *   Saucy - Regression Testing
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Nov 26 17:04:58 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-17.00.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-17.00.html