/srv/irclogs.ubuntu.com/2015/09/29/#ubuntu-meeting.txt

=== JanC_ is now known as JanC
=== hikiko-lpt is now known as hikiko
=== hikiko is now known as hikiko|ln
=== davidcalle_ is now known as davidcalle
coreycbo/16:00
gaughenit's me!!!16:00
smoserhoray!16:00
caribou\o16:00
rharper\o16:00
beisnero/16:01
thedac\o16:01
gaughen#startmeeting ubuntu-server-team16:01
meetingologyMeeting started Tue Sep 29 16:01:36 2015 UTC.  The chair is gaughen. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:01
meetingologyAvailable commands: action commands idea info link nick16:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic:
gaughen#topic Review ACTION points from previous meeting16:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | 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
gaughenI don't see any action points from last time.16:02
rharperyay, we finally moved on from asking rharper about numad16:02
gaughen#topic Wily Development16:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Wily Development
gaughen#link https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule16:02
gaughenha16:02
gaughenis thedac on the list to run this meeting?16:02
coreycbgaughen, no but he probably should be16:03
thedacso far I have hidden away16:03
gaughenfinal beta has passed16:03
gaughenthedac, I'm putting you on the list. I'm kind that way.16:03
gaughenI'll put you on the end... but before me ;-)16:03
thedacI am reconsidering our friendship :p16:03
gaughenfinal release is in less than a month - AAAAH!16:03
gaughenfinal freeze is Oct 1516:04
gaughen#subtopic Release Bugs16:04
gaughen#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server16:04
gaughendon't think there's anything worth mentioning  on the list16:05
gaughen#topic Server & Cloud Bugs (caribou)16:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Server & Cloud Bugs (caribou)
gaughencaribou, you have anything to say?16:05
gaughenbeuller16:05
caribouhi ?16:05
gaughenhello16:05
gaughenany bugs you want to mention16:05
caribouyes, bug #1496317 is up for review16:05
ubottubug 1496317 in kexec-tools (Ubuntu) "kexec fails with OOM killer with the current crashkernel=128 value" [High,In progress] https://launchpad.net/bugs/149631716:05
smoseroh nice.16:05
caribouapw is supposed to look at it soon16:05
cariboutl;dr create smaller initrd.img in /boot/kdump16:06
argescaribou: if it gets uploaded before tomorrow, I'll sru-review it : )16:06
caribouarges: then go & harrass apw about it :)16:06
caribouarges: I'd like a few eyes on it. Adding stuff to /boot can be seen as invasive16:06
argesyea16:07
caribougaughen: other than that I'm good16:07
gaughencaribou, cool! thank you!16:07
gaughen#topic Weekly Updates & Questions for the QA Team (matsubara)16:07
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | 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 (matsubara)
gaughenmatsubara, any QA topics?16:07
matsubaragaughen, hi, nothing new from me16:07
caribousmoser: debdiff is in the case if you want to have a look at it16:07
gaughen#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)16:08
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | 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)
smbNothing to see here, move along... Please...16:08
gaughen#topic Upcoming Call For Papers16:09
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Upcoming Call For Papers
gaughenany papers?16:09
gaughentopics?16:09
gaughenmoving on16:09
gaughen#topic Ubuntu Server Team Events16:09
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Ubuntu Server Team Events
gaughenOpenstack Summit in Tokyo is coming up16:10
gaughenthere is also Linux Con EU next week16:10
gaughenseveral folks are presenting  on LXD and cloud-init16:10
gaughenanything else?16:10
gaughen#topic Open Discussion16:10
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Open Discussion
gaughenanything?16:11
rharpercrickets16:11
gaughen#topic Announce next meeting date, time and chair16:11
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Announce next meeting date, time and chair
gaughennext week, same time, same place16:11
smoseroh.16:11
gaughenchair will be16:11
smoserhold on.16:11
smoserlets go back to open discussion16:11
gaughenarosales16:12
smoseri want to float one thing16:12
gaughenokay, go back16:12
gaughengo for it16:12
smoserhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd-vs-ifupdown16:12
gaughendo I need to switch topics officially?16:12
smosernah16:12
smoserserver has been asked what we think of a switch to networkd in 15.1016:12
smoser"by default"16:12
rharperhow can we do that now ?16:12
smoseri wish rbasak was here, but interested in anyone's thoughts.16:12
smoser:)16:13
gaughenrcj, does this impact cloud-images?16:13
smoserthat is the expected response.16:13
rharpermaybe at the start of a cycle16:13
gaughensmoser, isn't it a wee bit late16:13
smoserwell, the argument for it goes like this: i'd rather fail horribly now16:13
gaughenrcj, I expect the answer is yes16:13
smoserit does affect cloud images, yes.16:13
smosernot a *ton*, but it it would.16:14
gaughensmoser, would we have enough time to recover if we failed horribly now?16:14
rharpersmoser: hopefully the argument is: networkd fixes the following issues we have with ifupdown16:14
smoserthe bigger thing is anythign that writes (or reads) files in /etc/network/interfaces16:14
rharperif the size of that list is not large, it's hard to argue that it's worth the trouble in the first place16:14
rcjWe have cloud image specifics around the interfaces files so we'll break clouds16:14
smosera 1x1 static change is easy enough.16:15
rcjwe have things that generate interfaces on the fly16:15
smoserhonestly, i wouldnt expect the cloud images to be terribly effected.16:15
smoseroh?16:15
smoserrcj, where do you have such things ?16:15
rcjfor cloud providers that have dynamic networking and multiple devices16:15
rcjJoyent is one16:16
smoserok. so i'm very interested in that... can you give examples ?16:16
gaughenprobably not here16:16
smoser(to be clear, i'm not advocating for this, but rather playing devils advocate).16:16
rcjBut I don't know what tools like walinuxagent and gce tools are doing for certain either.16:16
gaughenwhat does non-devils advocate smoser think is the right thing to do here?16:16
smoserrcj, can you give a link to code that does "dynamic config" ?16:17
rcjsmoser, I don't know that I'll find it quickly with Ben out16:17
smosergaughen, the non-devils advocate thinks this is very late in a cycle.  and also even possibly very late in an LTS cycle (ie, as in now is late for *16.04*)16:18
rharpersmoser: the most damning discussion I've seen is that networkd hasn't been (in the past at least) focused on server configuration, so things like parallel interface bringup or even ordered interface bring up (think bonds) have been addressed16:18
rharperthe ifupdown + bonding threads brought up the issue and networkd folks, no we don't do that, lemme see if I can find the link16:18
smoserwell, this would be a server install (and cloud image) config.16:18
gaughensmoser, can we do a test build with it and see what falls out?16:18
rharperbut if we don't get equivalent function, and bug fixing, it's hard to argue that we should switch (and certainly harder late in the cycle)16:18
smoserrharper, i think that you're mistaken. in that networkd *is* server centric.16:19
smoserhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd-vs-ifupdown is the blueprint, and /usr/share/doc/systemd/README.Debian.gz on your wily system describes how to change16:20
smoserpitti has done a good job of documenting that.16:20
rharperI'll track down the emails I read;16:20
smoserfor easier reference, that README.Debian.gz is http://paste.ubuntu.com/12613789/16:21
smoseri agree, rharper that lack of bond is certainly a stop ship issue.16:21
smosergaughen, so yeah, you could reasonably easily "see what falls out".16:21
smoserso the big fallout is in anything that is reading or writing /etc/network/interfaces{,.d/*}16:22
smoserwhich is curtin for one16:22
smoserand also juju16:22
smoseri'm interested i knowing anything else that people are aware of.16:22
smoserlargely this is a fact finding expedition16:22
smoseralso relevant is resolvconf -> systemd-resolvconf would be probably done16:22
gaughensmoser, if we're still in fact finding mode that means to me we're not ready to pull the trigger16:23
gaughenand thus too damn late for wily16:23
gaughenmy 2 cents16:23
smoserthe general reason for the interest in networkd is the same as that of systemd16:23
smoserits not something you generally *chose*16:23
smoserbut something that is chosen for you. and you have to justify the cost of maintaining the other option (ifupdown-/etc/network/interfaces) indefinitely.16:24
* caribou likes the fact that this discussion is under Announce next meeting date :)16:25
gaughen:-)16:25
gaughenso anything else to talk about on this topic. smoser what's the next step?16:25
smoserthus, if it is inevitable, then dropping ENI/ifupdown (which people love to hate also) by 16.04 , means we get to drop support for ifupdown 2 years sooner.16:26
smoserdoes anyone have other examples of readers or writers of /etc/network/interfaces ?16:26
smoserthe other one that I know of is cloud-initramfs-dyn-netconf (which writes /etc/network/interfaces style file based on 'ip=' arguments on the cmdline).  And also open-iscsi is probably somehow affected (as it has to not bounce network interface of the root iscsi device).16:27
smoseranyone have anything else?16:27
gaughensmoser, should this one be emailed about on ubuntu-server?16:27
gaughen*crickets*16:28
gaughenokay I'm declaring this mtg done16:28
smoserdone16:28
smoserthanks.16:28
gaughenuntil next week, same time, same place.16:28
gaughenthank you smoser for your little topic16:29
caribouthanks gaughen16:29
gaughen#endmeeting16:29
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Sep 29 16:29:12 2015 UTC.16:29
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-29-16.01.moin.txt16:29
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 Sep 29 17:00:02 2015 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable commands: action commands idea info link nick17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Wily17: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
ckingo/17:00
smbo/17:00
henrixo/17:00
jsalisbury[TOPIC] Release Metrics and Incoming Bugs (jsalisbury)17:00
=== 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://kernel.ubuntu.com/reports/kt-meeting.txt17:01
jsalisbury..17:01
jsalisbury[TOPIC] Status: Wily Development Kernel (ogasawara)17:01
=== meetingology changed the topic of #ubuntu-meeting to: Status: Wily Development Kernel (ogasawara)
ogasawaraOur Wily kernel remains based on stable v4.2.1 and we will continue to17:01
ogasawaratrack 4.2 for the remainder of the 15.10 cycle.  As a reminder, we are17:01
ogasawaraapproaching Wily Kernel Freeze on Oct 8, ~1 week away.  If there are any patches which need to land for 15.10, please get them submitted soon.17:01
ogasawaraFollowing the Kernel Freeze deadline, all patches are subject to our SRU policy.17:01
ogasawara-----17:01
ogasawaraImportant upcoming dates:17:01
ogasawara[LINK] https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule17:01
ogasawaraThurs Oct  8 - Kernel Freeze (~1 weeks away)17:01
ogasawaraThurs Oct 15 - Final Freeze (~2 weeks away)17:01
ogasawaraThurs Oct 22 - 15.10 Release (~3 weeks away)17:01
ogasawara..17:01
chiluko/17:01
chiluk<-late17:01
jsalisbury[TOPIC] Status: CVE's17:01
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's
jsalisburyThe current CVE status can be reviewed at the following link:17:01
jsalisbury[LINK] http://kernel.ubuntu.com/reports/kernel-cves.html17:01
jsalisbury..17:01
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Trusty/lts-utopic/Vivid17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Precise/Trusty/lts-utopic/Vivid
jsalisburyStatus for the main kernels, until today:17:02
jsalisbury  *     Precise - Kernel Prep17:02
jsalisbury  *      Trusty - Kernel Prep17:02
jsalisbury  *  lts-Utopic - Kernel Prep17:02
jsalisbury  *      Vivid  - Kernel Prep17:02
jsalisburyCurrent opened tracking bugs details:17:02
jsalisbury  * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html17:02
jsalisburyFor SRUs, SRU report is a good source of information:17:02
jsalisbury  * http://kernel.ubuntu.com/sru/sru-report.html17:02
jsalisburySchedule:17:02
jsalisburycycle: 27-Sep through 17-Oct17:02
jsalisbury====================================================================17:02
jsalisbury         25-Sep   Last day for kernel commits for this cycle17:02
jsalisbury27-Sep - 03-Oct   Kernel prep week.17:02
jsalisbury04-Oct - 10-Oct   Bug verification & Regression testing.17:02
jsalisbury11-Oct - 17-Oct   Regression testing & Release to -updates.17:02
jsalisbury..17:02
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:03
jsalisbury#endmeeting17:03
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Sep 29 17:03:05 2015 UTC.17:03
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-29-17.00.moin.txt17:03
Macbook_OliverHi Team. Can anyone take a look at this: https://bugzilla.kernel.org/show_bug.cgi?id=9989117:06
ubottubugzilla.kernel.org bug 99891 in USB "Macbook8,1 12-inch (Early 2015) keyboard and trackpad don't work" [High,New]17:06
Macbook_OliverBasically the new macbook 12" is completely useless:(17:06

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