/srv/irclogs.ubuntu.com/2015/01/13/#ubuntu-meeting.txt

=== freeflyi_ is now known as freeflying_
=== dholbach_ is now known as dholbach
=== kickinz1 is now known as kickinz1|afk
=== kickinz1|afk is now known as kickinz1
gnuoyThings seem to be in a bit of a muddle, since I'm in the chair but I was scribe in the last but one meeting. Either way, I thought I'd destributed minutes etc from my meeting last year but I evidently didn't so as penance I'll pick up today and sort out the minutes I missed.16:00
gnuoy#startmeeting ubuntu-server-team16:00
meetingologyMeeting started Tue Jan 13 16:00:22 2015 UTC.  The chair is gnuoy. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:00
meetingologyAvailable commands: action commands idea info link nick16:00
=== 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:
gnuoy#topic Review ACTION points from previous meeting16:00
=== 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
gnuoyAll I have is:16:00
gnuoybeisner: establish new qa-team point of contact for server team16:00
gnuoydid that happen ?16:00
coreycbo/16:00
beisnero/16:01
beisnerhi16:01
beisnergnuoy, gaughen has initiated that16:01
argeso/16:01
kickinz1p/16:01
smbo/16:01
kickinz1sorry gnouy, I'm the responsible for that :(16:01
gnuoygaughen, does it require a meeting Aaction?16:01
gnuoy* action16:01
gnuoykickinz1, not just you, my fail too16:01
gnuoyACTION: gaughen  establish new qa-team point of contact for server team16:02
gnuoy#action  gaughen  establish new qa-team point of contact for server team16:02
meetingologyACTION: gaughen  establish new qa-team point of contact for server team16:02
gnuoy#topic Vivid 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: Vivid Development
gnuoy#link https://wiki.ubuntu.com/VividVervet/ReleaseSchedule16:02
gnuoyNot much in Jan by the looks of it16:03
gnuoy#subtopic Release Bugs16:03
gnuoy#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server16:03
matsubarao/16:03
hallyn~month to feature freeze...16:03
gnuoyok, we have 516:03
gnuoyhallyn, ta16:04
gnuoysmoser, does Bug #1387340 need anython special for vivid ? looks like fix to cloud-init is there16:05
ubottubug 1387340 in cloud-init (Ubuntu Vivid) "'output' directive not honored (/var/log/cloud-init-output.log missing)" [High,Confirmed] https://launchpad.net/bugs/138734016:05
gnuoySame question for Bug#140431116:06
gnuoyBug #140431116:06
ubottubug 1404311 in cloud-init (Ubuntu Vivid) "gce metadata api doesn't properly stream binary data" [High,Confirmed] https://launchpad.net/bugs/140431116:06
gnuoyBug #1409639 looks to be one you raised jamespage16:06
ubottubug 1409639 in juju-core (Ubuntu Vivid) "juju needs to support systemd for >= vivid" [High,Triaged] https://launchpad.net/bugs/140963916:06
smosergnuoy, they'll need to get uploaded to vivid, yes.16:06
jamespageo/16:07
jamespageindeed I did16:07
gnuoysmoser, do you know if that's likely to happen soonish ?16:07
jamespagethere is a bit of a focus on the switch to systemd this month16:07
rharper\o16:07
smoserprobably should. :)16:07
jamespagegnuoy, that work is inflight with juju-core - we've asked it get backport to 1.2216:07
gnuoyok16:08
gnuoyjamespage, and Bug #1388077 seems to be one of yours also16:08
ubottubug 1388077 in nova (Ubuntu Vivid) "Parallel periodic instance power state reporting from compute nodes has high impact on conductors and message broker" [Undecided,In progress] https://launchpad.net/bugs/138807716:08
gaugheno/16:09
gnuoyjamespage, coreycb, will we automagically get the fix to  Bug #1388077 when we next do a juno pkg update ?16:09
ubottubug 1388077 in nova (Ubuntu Vivid) "Parallel periodic instance power state reporting from compute nodes has high impact on conductors and message broker" [Undecided,In progress] https://launchpad.net/bugs/138807716:09
jamespagegnuoy, its fixed in juno and patched in in kilo as well16:10
gnuoyok16:10
coreycbgnuoy, I think yes then16:10
* jamespage does bug housekeeping16:10
gnuoyThat leaves us with Bug #1385851 then16:11
ubottubug 1385851 in openvpn (Ubuntu Vivid) "OpenVPN only supports TLS v1.0" [Medium,Confirmed] https://launchpad.net/bugs/138585116:11
gnuoy#subtopic Blueprints16:12
gnuoy"Everybody review and update blueprints"16:12
gnuoywith that taken as read, anything else?16:12
gnuoy#link http://status.ubuntu.com/ubuntu-v/group/topic-v-server.html16:12
gnuoy#link https://blueprints.launchpad.net/ubuntu/+spec/topic-v-server16:12
gnuoy#topic Server & Cloud Bugs (caribou)16:13
=== 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)
gnuoyAnything for/from caribou16:13
gnuoy?16:14
jamespagegnuoy, you might want to update the openstack charms blueprint (hint)16:14
gnuoyjamespage, with what in particular?16:14
jamespagegnuoy, any updates on work items16:14
jamespageright now have we done any charm work this cycle?16:14
gnuoywell, yes.16:14
jamespage0/51 tasks completed16:14
jamespage:-)16:15
gnuoyI know, the blueprint haven't done an upstanding job of reflecting work to date16:15
gnuoybut I agree, updates to reflect reality would be good16:16
gnuoy#topic Weekly Updates & Questions for the QA Team (not psivaa)16:16
=== 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 (not psivaa)
gnuoywe should probably skip this until we have a rep16:17
gnuoy#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)16:17
=== 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, sforshee, arges)
smbOn our side we had talked about dkms modules and reviewing stuff with 3.19. For openvswitch I was wondering whether there still will be something with Vivid. I mean there isn't anything in the archive, yet. But I am not sure this is intentional or not. Though I think from the openstack use case the in-kernel module was good enough. jamespage what would you say? Also, just looking at testing it seems it is/was fail16:17
smbing somehow for Utopic too. Which we may or may not care to care.16:17
jamespagesmb, it was intentional - its really not required for >= 3.1316:18
jamespageI do have an in-tree ovs bug tho16:18
* jamespage looks16:18
jamespagebug 140897216:18
ubottubug 1408972 in linux (Ubuntu) "openvswitch: failed to flow_del (No such file or directory)" [Medium,Confirmed] https://launchpad.net/bugs/140897216:18
smbjamespage, Yeah I just got pinged by jsalisbury to help him review his dependencies16:19
jamespagesmb, awesome16:19
smbApart from that anybody has something he want to refresh my memory with16:19
gnuoy... doesn't look like it16:20
gnuoy#topic Ubuntu Server Team Events16:20
=== 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
gnuoyOpenstack charm feature freeze on Thursday16:20
jamespage\o/16:21
jamespage15.01 here we come!16:21
gnuoy#topic Open Discussion16:21
=== 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
gnuoyAnything to openly discuss?16:22
gaughengnuoy, and there's the systemd virtual sprint16:22
gaughenthis Thurs/Friday16:22
gaughensorry missed the events topic16:22
gnuoyit whizzzzzzed past16:22
gaughenthat is all I have to gnuoy16:23
gaughensome good discussion today16:23
gnuoy#topic Announce next meeting date and time16:23
=== 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
gnuoy2015-01-20 16:00 UTC16:23
jamespageooo my birthday!16:23
gnuoyLooks like coreycb is next weeks winner16:23
gnuoy#endmeeting16:23
=== 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 Jan 13 16:23:56 2015 UTC.16:23
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-01-13-16.00.moin.txt16:23
coreycbtime to sing to james!16:23
coreycbgnuoy, thanks, for some reason I haven't chaired in forever16:24
gnuoycoreycb, you must be champing at the bit16:24
coreycbgnuoy, oh yes, yes I am :)16:25
ppisatio/17:00
chiluko/17:00
bjfo/17:01
ppisati\o/17:01
ogasawarao/17:01
* cking \o17:01
smbo/ (did id start?)17:01
chilukI think someone needs to start the meeting ..17:01
kamalo/ o/ o/17:01
kamal\o \o \o17:01
smbkamal volunteered to chair17:01
* kamal hides17:01
ppisati=^..^=17:02
argeso/17:02
ppisati(that was supposed to be a cat)17:02
ppisati(ok so, my audio/pulse thing is broken - can't talk but i can hear you)17:02
jsalisbury#startmeeting17:03
jsalisbury##17:03
jsalisbury## This is the Ubuntu Kernel Team weekly status meeting.17:03
jsalisbury##17:03
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:03
meetingologyMeeting started Tue Jan 13 17:03:14 2015 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:03
meetingologyAvailable commands: action commands idea info link nick17:03
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Vivid17:03
jsalisbury# Meeting Etiquette17:03
jsalisbury#17:03
jsalisbury# NOTE: '..' indicates that you are finished with your input.17:03
jsalisbury#       'o/' indicates you have something to add (please wait until you are recognized)17:03
jsalisbury[TOPIC] Release Metrics and Incoming Bugs (jsalisbury)17:03
=== 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:03
jsalisbury[LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt17:03
jsalisbury..17:03
jsalisbury[TOPIC] Status: Vivid Development Kernel (ogasawara)17:04
=== meetingology changed the topic of #ubuntu-meeting to: Status: Vivid Development Kernel (ogasawara)
ogasawaraBoth the master and master-next branches of our Vivid kernel have been17:04
ogasawararebased to the v3.18.2 upstream stable kernel.  This has also be17:04
ogasawarauploaded to the archive, ie. 3.18.0-9.10.  Please test and let us17:04
ogasawaraknow your results.  We are also starting to track the v3.19 kernel on17:04
ogasawaraour unstable branch and have pushed preliminary packages to our ppa.17:04
ogasawara-----17:04
ogasawaraImportant upcoming dates:17:04
ogasawara[LINK] https://wiki.ubuntu.com/VividVervet/ReleaseSchedule17:04
ogasawaraThurs Jan 22 - Vivid Alpha 2 (~1 week away)17:04
ogasawaraThurs Feb 5 - 14.04.2 Point Release (~3 weeks away)17:04
ogasawaraThurs Feb 26 - Beta 1 Freeze (~6 weeks away)17:04
ogasawara..17:04
chiluko/17:04
jsalisbury[TOPIC] Status: CVE's17:05
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's
chilukso are which kernel are we targetting for use in vivid?17:05
ogasawarachiluk: likely 3.19, possibly 3.20 but only if schedules align17:05
ogasawara..17:05
chiluk..17:05
jsalisburyThe current CVE status can be reviewed at the following link:17:06
jsalisburyhttp://people.canonical.com/~kernel/cve/pkg/ALL-linux.html17:06
jsalisbury..17:06
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Utopic/Trusty/Precise/Lucid (bjf/henrix/kamal/arges)17:06
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Utopic/Trusty/Precise/Lucid (bjf/henrix/kamal/arges)
bjfStatus for the main kernels, until today:17:06
bjf  *   Lucid - Verification & Testing17:06
bjf  * Precise - Verification & Testing17:06
bjf  *  Trusty - Verification & Testing17:06
bjf  *  Utopic - Verification & Testing17:06
bjf 17:06
bjfCurrent opened tracking bugs details:17:06
bjf  * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html17:06
bjfFor SRUs, SRU report is a good source of information:17:06
bjf  * http://kernel.ubuntu.com/sru/sru-report.html17:06
bjf 17:06
bjf 17:06
bjfSchedule:17:06
bjf 17:06
bjfcycle: 09-Jan through 31-Jan17:06
bjf====================================================================17:06
bjf         09-Jan   Last day for kernel commits for this cycle17:06
bjf11-Jan - 17-Jan   Kernel prep week.17:06
bjf18-Jan - 31-Jan   Bug verification; Regression testing; Release17:06
bjf..17:06
bjfoops ... all those should be kernel prep ...17:07
bjf..17:07
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:07
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:08
jsalisbury#endmeeting17:08
=== 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 Jan 13 17:08:34 2015 UTC.17:08
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-01-13-17.03.moin.txt17:08
kamalthanks jsalisbury17:08
=== kickinz1 is now known as kickinz1|afk
=== kickinz1|afk is now known as kickinz1
=== kickinz1 is now known as kickinz1|afk
=== jpds is now known as Guest41488
=== popey_ is now known as popey

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