/srv/irclogs.ubuntu.com/2013/11/26/#ubuntu-meeting.txt

=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== philipballew is now known as philip
=== Logan_ is now known as Guest61371
=== Logan__ is now known as Logan_
=== doko_ is now known as doko
=== dholbach_ is now known as dholbach
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== Guest46324 is now known as med_
=== med_ is now known as medberry
=== Ursinha-afk is now known as Ursinha
arosalesHello16:01
arosalesI'll be chairing today's Server team meeting16:01
smosero./16:01
adam_go/16:01
* arosales grabs the commands16:01
roaksoaxo/16:01
arosales#startmeeting ubuntu-server-team16:01
meetingologyMeeting started Tue Nov 26 16:02:08 2013 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:01
meetingologyAvailable 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 #votesrequired16:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic:
arosales#topic Review ACTION points from previous meeting16:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Review ACTION points from previous meeting
arosalesNo actions from previous meeting16:02
arosales#topic Trusty Development16:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Trusty Development
arosales#link https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule16:03
arosaleswe have an alpha coming up I think . . .16:04
arosalesDec 19th16:04
arosalesopt in for flavors16:04
arosalessmoser, jamespage is server opting in?16:04
* arosales doesn't see utlemming for cloud image confirmation16:04
jamespageas a core flavor we don't normally opt in - I'm happy to stick with that for alpha116:05
arosalesjamespage, ack16:05
arosales#subtopic Release Bugs16:05
arosales#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server16:05
smoserjamespage, well, i like to create cloud images.16:05
arosalessmoser, I think cloud images has done an alpha in the past .  . .16:06
smoseri'd like for us to opt in for alpha1 cloud images, with some actual targets.16:06
jamespagesure16:06
smoserthe seed-review and gpt16:06
smoserjamespage, have you done a seed-review email ?16:06
jamespagesmoser, urgh - not yet16:06
arosales#action smoser sync with utlemming on building cloud images for alpha 1, targets = seed-review, gpt16:06
meetingologyACTION: smoser sync with utlemming on building cloud images for alpha 1, targets = seed-review, gpt16:06
jamespagearosales, please action me todo that asap16:07
arosaleswill do16:07
arosales#action jamespage do seed-review email16:07
meetingologyACTION: jamespage do seed-review email16:07
arosalesonto bugs :-)16:07
arosalesgot two high @ http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server16:07
arosalesno critical16:08
arosaleshttp://launchpad.net/bugs/124376216:08
ubottuUbuntu bug 1243762 in juju-core (Ubuntu Trusty) "[MIR] juju-core, golang" [High,Confirmed]16:08
jamespagethat will stick on the report until either we decide not to or it gets in main16:08
arosalesjamespage, ok, thanks16:08
arosalesbug 106233616:08
ubottubug 1062336 in nova (Ubuntu Trusty) "nova-compute expects libvirtd group" [High,Triaged] https://launchpad.net/bugs/106233616:09
arosaleszul ^16:09
rbasakWe 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
ubottubug 1248283 in juju-core "Juju deploy of Charm in MAAS fails because dbus fails" [High,Triaged] https://launchpad.net/bugs/124828316:09
arosalesnevermind jamespage looks like your marked won't fix16:09
jamespagezul, that will get fixed up under the kvm packaging review16:09
zulrbasak:  its been removed in trusty16:09
rbasakzul: what's been removed exactly?16:10
zularosales: the xcp stuff has been removed in nova16:10
zulrbasak:  sorry not you :)16:10
arosaleszul, thanks16:10
arosalesrbasak, you are referring to https://bugs.launchpad.net/maas/+bug/124828316:10
ubottuUbuntu bug 1248283 in juju-core "Juju deploy of Charm in MAAS fails because dbus fails" [High,Triaged]16:10
rbasakYes16:11
arosalesgood one to track16:11
arosalesjamespage, which team to we add to get in on the bug tracking list?16:12
arosales~ubuntu-server ?16:13
arosalessmoser, ^16:13
jamespageno - dbus should not be on the server list16:13
jamespageraise a task for juju-core - I think that will do it16:14
smoserthere is a task for juju-core thre.16:14
arosalesjuju-core has a task16:14
arosaleswhile we work on that is there any other bugs we want to cover?16:15
jamespagejuju-core in Ubuntu16:15
arosalesthere are a few other mediums and lows16:15
jamespagenot upstream16:15
rbasakI think you might need a packaging task against a package that ~ubuntu-server subscribes to that also has a Trusty task.16:15
rbasakI'm not sure this is a good way to do it, mind.16:15
arosalesjamespage, ah ok16:15
jamespagerbasak, is the bug in dbus?16:15
rbasakDebatable. I'd say the primary bug is in juju-core.16:15
rbasak(or perhaps the MAAS provider in juju if that's separate)16:16
arosalesrbasak, could you add a task for juju-core in Ubuntu?16:16
rbasakdbus would ideally not fail, and ideally log a message explaining what happens when it does.16:16
rbasakBut juju should not try to restart networking. It doesn't need to do that anyway.16:17
jamespagerbasak, raise a distro bug task for Ubuntu and target to trusty16:17
jamespageso we can track it16:17
rbasakack16:17
arosalesrbasak, thanks16:17
arosalesany other bugs we should cover16:17
rbasakDone. Importance?16:17
arosalesgot the highs and critical ones done @ http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server16:18
rbasakI'll say Triaged/High.16:18
arosalesrbasak, thanks for brining in one we needed to track too16:18
arosalesok we covered those16:18
arosalesnot the others on the list are openstack16:18
arosalesless websockify16:18
arosalesmoving on16:18
arosales#subtopic Blueprints16:19
arosalesjamespage, to my failing did you create a topic bp?16:19
jamespageyes16:19
arosales#link http://status.ubuntu.com/ubuntu-s/group/topic-t-servercloud-overview.html16:19
arosalesah and you must have updated the notes16:19
arosaleswell done -- thank you16:19
arosales:-)16:19
arosaleshttp://status.ubuntu.com/ubuntu-s/group/topic-t-servercloud-overview.html16:20
arosaleshmm not loading for me atm16:20
jamespagehttps://blueprints.launchpad.net/ubuntu/+spec/topic-t-servercloud-overview16:20
arosalesworking for others?16:20
arosaleshmm http://status.ubuntu.com/ubuntu-t/ looks to may need a kick16:21
jamespagearosales, no16:21
* arosales doesn't see any topic BPs there16:21
jamespagearosales, gaughen: we need to go through all blueprints and priortize and accept for trusty16:21
jamespageso as its only UDS + 2 days really16:21
arosales#action jamespage, gaughen review blueprints and accept for trusty16:21
meetingologyACTION: jamespage, gaughen review blueprints and accept for trusty16:21
gaughenokay16:22
smoseryeah.16:22
jamespagecan respectfully suggest that everyone write up their blueprints from last week by thursday16:22
jamespageusing the blueprint spec16:22
jamespageand mark 'Pending Approval'16:22
arosales#action gaughen file bug with status.u.c to get ubuntu server topic tracking in there16:22
meetingologyACTION: gaughen file bug with status.u.c to get ubuntu server topic tracking in there16:22
arosalesgaughen, I hope you don't mind that action16:22
jamespagethen smoser, gaughen and I will know which ones to review16:22
arosalesgaughen, https://bugs.launchpad.net/launchpad-work-items-tracker/+filebug16:23
arosalesgaughen, ping me if you have any questions16:23
jamespageso I guess for folks in the US that means be end of wednesday16:23
jamespage....16:23
jamespagesorry16:23
gaughennope don't mind but i will have questions :-)16:23
jamespageactually - this makes no sense16:23
arosales#action all: write up blueprints, and have them ready for review by November 2816:23
meetingologyACTION: all: write up blueprints, and have them ready for review by November 2816:23
jamespageend of week - then we can review early next week16:23
smoserend of week.16:23
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 2916:24
arosalesany other BP topics?16:25
arosales#topic Server & Cloud Bugs (caribou)16:25
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Server & Cloud Bugs (caribou)
arosalescaribou any bugs to bring up here that we didn't already cover?16:25
* arosales doesn't see caribou online atm16:26
arosales#topic Weekly Updates & Questions for the QA Team (psivaa)16:26
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the QA Team (psivaa)
psivaaNo updates from us,16:26
arosalespsivaa, ok thanks16:26
arosales#topic Weekly Updates & Questions for the Kernel Team (smb)16:26
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the Kernel Team (smb)
arosalessmb any updates?16:28
* arosales doesn't seem smb here atm16:28
arosalesany folks from kernel16:28
arosales#topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)16:29
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
rbasakNo updates from me. Any questions?16:29
arosalesany questions for rbasak ?16:29
arosales#topic Ubuntu Server Team Events16:29
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Ubuntu Server Team Events
arosaleswe had a lot of events we just came back from16:29
arosalesODS, uVDS, RubyConf, AWS re:Invent16:30
arosalesI don't know of any upcoming in the next week16:30
arosalesany other folks have any events to bring up here?16:30
arosales#topic Open Discussion16:30
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Open Discussion
arosalesany other agenda items?16:31
arosalesgoing once16:31
arosalestwice16:31
arosalesthrice16:31
arosales#topic Announce next meeting date and time16:32
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Announce next meeting date and time
arosalesNEXT MEETING: Tuesday 2013-12-03 at 1600 UTC16:32
arosalesThanks for joining the ubuntu server team meeting!16:32
arosales#endmeeting16:32
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Nov 26 16:32:50 2013 UTC.16:32
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-16.02.moin.txt16:32
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-16.02.html16:32
jsalisbury#startmeeting17: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/Meeting17:00
meetingologyMeeting started Tue Nov 26 17:00:29 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable 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 #votesrequired17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Trusty17:00
jsalisbury# Meeting Etiquette17: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
jsalisburyRoll Call for Ubuntu Kernel Weekly Status Meeting17:00
rtgo/17:00
kamalo/17:00
henrixo/17:00
ckingo/17:00
sforsheeo/17:00
bjfo/17:00
ppisatio/17:01
jsalisbury[TOPIC] ARM Status (ppisati)17:01
=== meetingology changed the topic of #ubuntu-meeting to: ARM Status (ppisati)
ppisatinothing new to report this week17:01
ppisati..17:01
jsalisbury[TOPIC] Release Metrics and Incoming Bugs (jsalisbury)17:01
=== meetingology changed the topic of #ubuntu-meeting to: Release Metrics and Incoming Bugs (jsalisbury)
jsalisburyRelease metrics and incoming bug data can be reviewed at the following link:17:01
jsalisbury[LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt17:01
jsalisbury..17:01
jsalisbury[TOPIC] Milestone Targeted Work Items (ogasawara)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Milestone Targeted Work Items (ogasawara)
ogasawara2 secs17:02
ogasawara[LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork17:02
ogasawara[LINK] http://status.ubuntu.com/ubuntu-t/canonical-kernel-distro-team.html17:02
ogasawaraWhile marginally useful for tracking work items in the past, the above17:02
ogasawaralinks are completely useless at the moment.  I have manually reviewed17:02
ogasawarawork items from the core-1311-kernel and core-1311-hwe-plans blueprints.17:02
ogasawaraHowever, beyond those two, I'm oblivious to what other work our team or17:02
ogasawaraindividuals 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
=== meetingology changed the topic of #ubuntu-meeting to: Status: Trusty Development Kernel (ogasawara)
ogasawaraFor those unaware, the ubuntu-trusty git repo is open and available at:17:02
ogasawaragit://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git .  The master branch is17:02
ogasawaracurrently tracking the latest 3.12.1 upstream stable kernel while the17:03
ogasawaraunstable branch has most recently been rebased to v3.13-rc1.  We shall17:03
ogasawaramove our master branch to track v3.13 after some baking.  We will also17:03
ogasawaraupload to the archive when it's ready.17:03
ogasawara-----17:03
ogasawaraImportant upcoming dates:17:03
ogasawara[LINK] https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule17:03
ogasawaraThurs Dec 12 - 12.04.4 Kernel Freeze (~2 weeks away)17:03
ogasawaraThurs Dec 23 - 12.04.4 Final Release (~8 weeks away)17:03
ogasawara[LINK] https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule17:03
ogasawaraThurs Dec 19 - Alpha 1 (~3 weeks away)17:03
ogasawaraThurs Jan 23 - Alpha 2 (~ 8 weeks away)17:03
ogasawara..17:03
jsalisbury[TOPIC] Status: CVE's17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's
jsalisburyThe current CVE status can be reviewed at the following link:17:03
jsalisburyhttp://people.canonical.com/~kernel/cve/pkg/ALL-linux.html17:03
jsalisbury..17:03
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Saucy/Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Saucy/Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
bjfStatus for the main kernels, until today (Nov. 26):17:03
bjf  *   Lucid - Regression Testing17:03
bjf  * Precise - Regression Testing17:03
bjf  * Quantal - Regression Testing17:03
bjf  *  Raring - Regression Testing17:03
bjf  *   Saucy - Regression Testing17:03
bjfCurrent opened tracking bugs details:17:03
bjf  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html17:03
bjfFor SRUs, SRU report is a good source of information:17:03
bjf  * http://people.canonical.com/~kernel/reports/sru-report.html17:03
bjf..17:03
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:04
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:04
jsalisbury#endmeeting17:04
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Nov 26 17:04:58 2013 UTC.17:04
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-17.00.moin.txt17:04
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-26-17.00.html17:04
=== G4MBY is now known as PaulW2U
=== greyback is now known as greyback|away
=== Logan_ is now known as Guest1674
=== Logan__ is now known as Logan_
=== medberry is now known as med_
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!