/srv/irclogs.ubuntu.com/2015/08/25/#ubuntu-meeting.txt

=== Guest37794 is now known as Zic
=== ghostcube_ is now known as ghostcube
=== kitterma is now known as ScottK
=== ghostcube__ is now known as ghostcube
rharper\o16:03
caribouo/16:03
matsubarao/16:03
jgrimmo/16:03
argeso/16:03
thedaco/16:03
smbo/16:04
beisnero/16:05
smosero/16:06
smoserheyt.16:06
smoseri guess its me.16:06
smoserwhoops16:06
smoser#startmeeting ubuntu-server-team16:06
meetingologyMeeting started Tue Aug 25 16:06:49 2015 UTC.  The chair is smoser. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:06
meetingologyAvailable commands: action commands idea info link nick16:06
=== 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:
smoser#topic Review ACTION points from previous meeting16:06
=== 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
smoserseems like agenda did not get updated i think...16:07
smoseras my caction item bug 1461242  there is fixe16:07
ubottubug 1461242 in cloud-init (Ubuntu Vivid) "cloud-init does not generate ed25519 keys" [Medium,Confirmed] https://launchpad.net/bugs/146124216:07
smoseri'll remvoe that16:07
smoserother item listed there is :16:07
smoser Thoughts about numad16:07
smoseranyone know of more content on that ?16:08
rharperI've not poked the team16:08
smoserok, well please add that to TODO list / bump its priority16:08
rharpersmoser: it's a background action item for me to collect team thoughts on whether we should have something like numad and other NUMA related placement stuff16:08
smoser#action rharper collect team thoughts on whether we should have something like numad and other NUMA related placement stuff16:09
meetingologyACTION: rharper collect team thoughts on whether we should have something like numad and other NUMA related placement stuff16:09
smoser#topic Wily Development16: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: Wily Development
smoser#link https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule16:09
smoserbeta1 freeze is thursday.16:09
smoserand we're past feature freeze now.16:09
smoserso ffe will have to be opened for any new features uyou want.16:09
smoseranything else ?16:10
smoser#subtopic Release Bugs16:10
caribouyes,16:10
smoserok... go caribou16:10
caribounm, I'll bring that up at my turn16:10
cariboucarry on16:10
smoserk16:11
smoser#subtopic Release Bugs16:11
smoser#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server16:11
smoserloading...16:11
smoseri have one there for keepalived , bu have been out for thelast two weeks.16:13
smoseri'll try to get proress on that by next week.16:13
smoseranyone interesated in others ?16:13
smoserseems like wesley may hav made progress on https://launchpadlibrarian.net/214863711/wily-debdiff16:13
smosererr.. on https://launchpadlibrarian.net/214863711/wily-debdiff16:13
smosersomeone want to shepard that through ?16:13
smoserok. well, that one at very least seems like we shoudl do some mocvement on it.16:14
magicalChickensmoser: Yeah, I got a fix uploaded for that one16:14
magicalChickensmoser: I need someone to sponsor it though16:15
smoseroh. ok. magicalChicken i can see if i can do that for you.16:15
magicalChickensmoser: Awesome, thanks16:15
rbasakI'm behind on sponsoring team bugfixes. Shall I gather a list maybe of who in the team is waiting on sponsorship and try and work through them?16:15
rbasakThough if smoser wants to work on this one feel free :)16:15
smoserthanks. for those playing along at home, magicalChicken == wesley16:16
rbasakmagicalChicken, smoser: note: on my very quick glance you need to s/Closes/LP: #/ in the changelog entry. Closes refers to Debian bugs so it won't autoclose the LP one otherwise.16:16
smoseri'm way behind on other things too as a week out did.16:16
smoserso i'll leave that to rbasak or smoser16:16
smoserand we'll move on, but yeah, you want to reference the ubuntu bug with:16:16
rbasakI'll happily take an action to sponsor all outstanding sponsorship requests before the next meeting.16:16
magicalChickenrbasak: Aah, i didn't know that. I'll fix that16:17
smoser LP: #147814916:17
ubottuLaunchpad bug 1478149 in python-tornado (Ubuntu Wily) "python-tornado tests fail against python3.5" [High,Triaged] https://launchpad.net/bugs/147814916:17
rbasakmagno problem!16:17
smosermoving on.16:17
smoserk ?16:17
smoser#topic Server & Cloud Bugs (caribou)16:17
=== 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)
cariboumy request for sponsorship of the rsyslog merge didn't get picked up16:17
caribou& we're passed FF16:17
rbasakSorry :-/16:17
caribouI'dl like the audience opinion on going for FFE on this one16:17
caribouso it gets its bits shaken before LTS16:18
rbasakI was swamped around feature freeze and didn't manage to get through all requests.16:18
rbasakI still have a pile of FFEs to do.16:18
caribourbasak: no worry, I pinged a few others who were swamped as well :)16:18
smosercaribou, your rsyslog ?16:18
caribouI have a potential sponsor now if I get the FFE through16:18
smoseroh. merge.16:18
rbasakI'm not sure it makes sense to FFE everything we missed. It just means that we have less time to fix bugs.16:19
caribousmoser: yes, current is 7.4.4 and debian has 8.9.016:19
smoseri'd personlly feel ok to push a ffe for rsyslog.16:19
smoseras we would like to have that newer version for x16:19
rbasakOTOH I have no objection to individuals driving their own FFEs.16:19
smoserand having it cook longer would be good16:19
caribouI'm fine with preparing it & let the server team drive it16:19
rbasakI don't want to take on driving more FFEs - I have a number I'm taking care of already16:20
rbasakAnd if I take on more, then they're only going to slip anyway.16:20
caribourbasak: true; ok I'll lead this one & may ask for help  on my way16:20
smoserok. well, then . seems like unless someone steps up that will drop16:20
smoser:-(16:20
caribousmoser: it won't, I'll do it16:21
rbasakI'm fine with that caribou - thanks.16:21
smoserah. ok. good.16:21
smoser#topic Weekly Updates & Questions for the QA Team (matsubara)16:21
=== 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)
smosercaribou, above, if you do have questions, please feel free to ask.16:21
matsubaranothing new to report smoser16:21
caribousmoser: k16:21
smoser#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)16:21
=== 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 here that I can think of right now. Are there questions?16:21
smoserk16:23
smoser#topic Upcoming Call For Papers16:23
=== 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
smoseranything here ?16:23
smoseri dont have anything.16:24
smoser#topic Ubuntu Server Team Events16:24
=== 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
smoseranyone speaking or attending soon and want to mention ?16:24
smoser#topic Open Discussion16:24
=== 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
rharpersmoser: on the bcache-tools sru to trusty16:24
smoserah. yeah.16:25
rharpersmoser: you were saying that we probably don't need the TB exception since we wouldn't be regressing things vs. upstream ?16:25
smoserunles we put it into an image, then we're virtually guaranteed to not regress aything16:26
rharperwouldn't it go into either cloud image or ephemeral? or just rely on them to pull it down from archive as needed ?16:26
rbasakI don't think the SRU team will accept it under current SRU policy without a TB-approved exception, but we can see.16:26
rharperupdated curtin for example, will auto pull in lvm2, mdadm and bcache-tools16:26
smosersru team would probasbly accept it.16:26
smoserother than putting it into an image.16:27
smoserif its not in an image, then it wont regress anything.16:27
smoserits generally ok to put new things ito old releases for important feature / hardware enablement./16:27
rbasakI agree that it probably won't regress anything. I'm sure the SRU team won't object on that basis either.16:27
smoserbut putting it into a maas ephemeral image means it becomes part of the default install of a maas from ubuntu16:27
smoserwhich i can see as possible potential for regression16:28
rbasakBut AFAIK no "important feature" has ever been SRU'd as new package that wasn't hardware enablement without a TB exception.16:28
rharperin either case (as I have a write up for the TB); the bigger issue IMO is the edge testing on bcache-tools16:29
rbasakAnyway, it doesn't really matter. It won't create extra or duplicate work whichever way we decide to approach this, so I don't mind either way.16:29
rharperwhile both server and maas teams have been using the bcache-tools package and bcache feature16:29
rbasakIf the SRU team want an exception from the TB then we can ask for one - there won't be any harm done.16:29
smoserrharper, well, putting buggy bcache-tools into trusty isnt necessarily bad on its own.16:30
rharperI don't feel those have been edge tested, ie, what happens when we drop the cache device, changing cache modes, recovery, twiddling the sysfs writable values on bcache;16:30
rharpersmoser: it's an LTS16:30
rharperso it can hurt for longer16:30
smoserexcept for when it is annoyingly buggy16:30
smoserand bcache-utils *is* annoyingly buggy16:30
rharperwell16:30
rharpersorta16:30
rharperthe main function doesn't appear that way16:30
rharperbut it's quite awkward to deal with16:31
smoserright.16:31
smoserwhich could happen unintentionally16:31
rharperwhich is why I started on that bcache-release script to help folks "cleanup" the mess16:31
rharperyes16:31
smoserthats the point i think is important really.16:31
smoseris that you're essentially suggesting it become part of a default install16:32
smoserand thus it requires significantly more thought16:32
rharperas per maas request16:32
smoserthan just adding a package to the archive that will not be used by someone unless they "opt in"16:32
rharperto make trusty  ~= vivid ~= wily w.r.t storage config features16:32
rharperok16:32
smoserso.. i'd say go to TB i guess.16:33
rharperand include some bits on in archive, vs. in image16:33
smoserand be clear that your intent is to add it to a "default install". as i think thats the intent.16:33
rharperand a follow up with maas, can they get by with 'in archive' vs. 'in image'16:33
smoserif instead curtin will install it into the ephemeral image and then into the target only when it is needed, then it requires much less scrutiny in my opintion16:34
smoserbecase even then, its essentially "opt in" by a user of maas.16:34
rharperthat's how it is today16:34
rharperand unless maas complains about the extra hit to archive to pull in deps16:34
rharperlikely not since we're not going to put lvm2 nor mdadm into default install, no ?16:34
rharpersmoser: it didn't seem likely given your discussion re: mdadm + mail dep in #ubuntu-devel the other week16:35
rbasakThat's going to slow down the install though, no?16:35
rharperso I don't think bcache-tools not in default install is a significant burden since it still has lvm2 and mdadm to install16:35
rharperrbasak: indeed16:35
rbasakWe don't really want curtin to have to install packages locally in the long term.16:35
rharperbut we'd need all 3 deps to be in16:35
smosershoot. i had to follow up on that... i thought the discussion ended with 'lets add it'.16:35
rbasakIt might be acceptable for Trusty though.16:35
rharpersmoser: maybe it did; I only saw the initial discussion w.r.t the mail deps16:35
smoseri'm on same page with rbasak.16:36
rharperfolks saying, no if I have a raid I really would like to have it send an email if something is wrong (w.r.t the madm dep on postfix)16:36
smoserwe want the default install to have those things, so we should work to get them into wily and then X16:36
smoserbut if we can live with trusty being less than perfect than that is good.16:36
rharperso trusty and vivid need runtime deps installed via curtin16:36
rharperwily could be fixed and in=place for x16:37
rbasakYeah. X is only round the corner now anyway.16:37
rharpertrusty and vivid16:37
rharperbut, yes16:37
rharperunless you rebuild those images IIUC16:37
smoserwell the images are re-built, but we'd have to add those packages.16:37
rharpersure16:37
rbasakThat's a good point. If you implement in curtin with a test, it'll always be possible to get a local speed up by hacking your local ephemeral image if it matters to you.16:38
smoserok. so i think this is beaten.  i guess you should go ahead to TB.16:38
smoserrharper, and we should get those packages into wily cloud and maas images.16:38
rharpersmoser: ok, can you add the action items then ?16:38
rharperare we OK with the level of edge testing then ?16:38
smoser#action rharper send email to TB about bcache-utils into trusty16:39
meetingologyACTION: rharper send email to TB about bcache-utils into trusty16:39
rharperthat was the only thing holding me back before sending to TB16:39
cariboubcache-utils == bcache-tools ?16:39
rharperyes16:39
smoserright16:39
smoser#action smoser, rharper get other packages into cloud-image necessary for storage features.16:40
meetingologyACTION: smoser, rharper get other packages into cloud-image necessary for storage features.16:40
rharpersmoser: ok, I'm good16:40
smoser#topic Announce next meeting date, time and chair16:41
=== 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
smosernext meeting will be Tuesday, September 1 at 16:00 UTC16:41
smoserchair will be gnuoy16:41
smoser#endmeeting16:41
=== 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 Aug 25 16:41:54 2015 UTC.16:41
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-08-25-16.06.moin.txt16:41
caribousmoser: thanks!16:42
jsalisbury#startmeeting17:00
meetingologyMeeting started Tue Aug 25 17:00:28 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##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
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Wily17:00
smbo/17:00
jsalisbury# Meeting Etiquette17:00
ckingo/17:00
henrixo/17:00
ppisatio/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[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://kernel.ubuntu.com/reports/kt-meeting.txt17:01
jsalisbury..17: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:02
jsalisbury[LINK] http://kernel.ubuntu.com/reports/kernel-cves.html17:02
jsalisbury..17:02
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Trusty/Utopic/Vivid (bjf)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Precise/Trusty/Utopic/Vivid (bjf)
bjfStatus for the main kernels, until today:17:02
bjf  *     Precise - Verification & Testing17:02
bjf  *      Trusty - Verification & Testing17:02
bjf  *  lts-Utopic - Verification & Testing17:02
bjf  *      Vivid  - Verification & Testing17:02
bjf 17:02
bjfCurrent opened tracking bugs details:17:02
bjf  * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html17:02
bjfFor SRUs, SRU report is a good source of information:17:02
bjf  * http://kernel.ubuntu.com/sru/sru-report.html17:02
bjf 17:02
bjf 17:02
bjfSchedule:17:02
bjf 17:02
bjfcycle: 16-Aug through 05-Sep17:02
bjf====================================================================17:02
bjf         14-Aug   Last day for kernel commits for this cycle17:02
bjf15-Aug - 22-Aug   Kernel prep week.17:02
bjf23-Aug - 29-Aug   Bug verification & Regression testing.17:03
bjf30-Aug - 05-Sep   Regression testing & Release to -updates.17:03
bjf..17:03
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:03
=== 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: 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 Aug 25 17:04:19 2015 UTC.17:04
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-08-25-17.00.moin.txt17:04
kamalthanks jsalisbury17:05

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