/srv/irclogs.ubuntu.com/2016/10/18/#ubuntu-meeting.txt

=== doko_ is now known as doko
=== Guest62846 is now known as med_
cpaelzero/15:59
powersjo/16:00
jgrimmo/16:01
powersjwait a min. or two?16:01
rharpero/16:01
cpaelzerdepends no how much showed up, you might highlight some you consider missing16:01
jgrimmyeah, i just poked internal channel16:02
nacco/16:02
braunero/16:02
naccsorry was messing with the importer16:02
powersjok let's see if I do this right :)16:03
jgrimm:)16:03
smosero/16:03
powersj#startmeeting ubuntu-server-team16:03
meetingologyMeeting started Tue Oct 18 16:03:10 2016 UTC.  The chair is powersj. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:03
meetingologyAvailable commands: action commands idea info link nick16: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 | ubuntu-server-team Meeting | Current topic:
powersj#topic Review ACTION points from previous meeting16: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 | ubuntu-server-team Meeting | Current topic: Review ACTION points from previous meeting
powersj(jamespage) checkin with old iscsitarget users on relevancy with new kernels16:03
powersjanything here?16:04
jgrimmpowersj, if we don't get an update in next irc meeting, i'll work via email16:04
powersjok, moving on16:05
powersj#topic Yakkety Development16: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: Yakkety Development
powersj#link https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule16:05
naccthat should be Zesty now, right?16:05
powersjdone with this topic now?16:05
powersj:)16:05
jgrimm:)16:05
cpaelzernacc: it is not there yet16:05
powersjany lingering or post-release yakkety issues?16:05
nacccpaelzer: which is not?16:06
jgrimmhttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-z-server-core16:06
jgrimmjust a reminder that the blueprint is open for business that we want to track ^^16:06
rharperjgrimm: we may want to add the /boot install outcome16:07
powersjgreat! anything else for yakkety or zesty dev?16:07
jgrimmrharper, agreed. i'll fix now16:07
naccjgrimm: would you be ok with adding putting the importer live to the blueprint? or should we keep it unofficial? :)16:07
rharperI think rbasak was going to take that to ubuntu-devel as well16:07
jgrimmrharper, yep16:08
jgrimmnacc, feel free to use blueprint for it (or create new separate and link)16:08
naccjgrimm: thanks16:08
jgrimmits not terribly formal.. however we feel it helps us be effective.16:08
naccabsolutely16:08
jgrimmrharper, added /boot to blueprit16:09
jgrimmblueprint even16:09
powersjok moving on16:09
powersj#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-y-tracking-bug-tasks.html#ubuntu-server16:09
powersjwwops16:09
powersj#subtopic Release Bugs16:09
powersjdo we have rbasak?16:10
nacci recollect seeing in my scrollback he might be out16:10
jgrimmah, new stuff in the report at least16:10
powersjah yes he is out today16:10
jgrimmpowersj, i just did a quick look at the y report.  all have owners or in progress that I don't see anything worth bringing up here.16:11
powersjjgrimm: thank you! moving on16:11
powersj#topic Server & Cloud Bugs (caribou)16: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: Server & Cloud Bugs (caribou)
powersj#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-x-tracking-bug-tasks.html#ubuntu-server16:11
jgrimmpowersj, caribou unable to make it today, sent status ahead of time that he had nothing to bring up today16:12
powersjmaking this easy on me ;)16:12
powersj#topic Weekly Updates & Questions for the QA Team (powersj)16:12
=== 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 (powersj)
powersj#link https://jenkins.ubuntu.com/server/16:12
powersjYakkety ISO testing last week, few issues with ppc64el and ppc16:12
powersjFocus is on cloud-init integration testing. Goal is still to have something working by Friday in our jenkins (linked above)16:13
powersjany questions for me?16:13
smoserpowersj, woot!16:13
jgrimmlooks good.  will be great to have cloud-init integration tests finally !16:13
powersj:)16:13
powersjok moving on then16:14
cpaelzerI still feel too red on the migration tests powersj16:14
cpaelzeris the ball currently with you or me ?16:14
powersjcpaelzer: I agree - let me remind myself of status later today and send you mail16:14
cpaelzerpowersj: I'll let you remind yourself :-P16:14
powersj:)16:14
powersj#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee)16:14
=== 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)
* cpaelzer stops stropping people reminding things16:14
cpaelzerstopping even16:15
smbNothing to report from here16:15
powersjok16:15
powersj#topic Upcoming Call For Papers16:15
=== 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
powersjanything here?16:16
jgrimmchecking16:16
jgrimmCFP for OSCON is Oct 25, FOSDEM is Oct 31.16:17
jgrimmpowersj, fwiw.. i usually rely upon the LWN CFP deadline page.16:18
powersjjgrimm: good to know, I will go read that after this16:18
powersjanything else from folks?16:19
rharperjgrimm: link ?16:19
rharperjust  #  link it here16:19
jgrimm#link http://lwn.net/Calendar/Monthly/cfp/16:19
powersjexcellent, thank you!16:20
jgrimmnp16:20
powersj#topic Ubuntu Server Team Events16:20
=== 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
smoseris zesty open for uploads ?16:20
jgrimmgood question16:20
cpaelzersmoser: not a few hours ago16:20
cpaelzersmoser: I saw xnox having extra work since not all things were ready16:20
cpaelzersmoser: so I wouldn't rush things today unless we hear a "go"16:21
nacci'm seeing stuff go into z-p on #ubuntu-release16:21
jgrimmooo > Unapproved: mistral (zesty-proposed/universe) [3.0.0-1 => 3.0.0-1ubuntu1] (no packageset16:21
naccbut that might be an artifact of the copy forward?16:21
naccnot sure16:21
naccthe /topic says its still closed16:21
cpaelzerwell then it was resolved in the last few hours16:21
cpaelzerbut copy?16:21
jgrimmso some bits getting close16:21
cpaelzeryeah ack16:21
powersjanyting for team events?16:22
powersjanything rather16:22
powersjok, moving on16:23
powersj#topic Open Discussion16: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: Open Discussion
cpaelzerI have two topics for this one16:23
cpaelzerOne would be a discussion on proactive stable updates for qemu16:24
cpaelzerI found that 2.5 got 2.5.1 and 2.5.1.1 upstream16:24
cpaelzerFYI - http://paste.ubuntu.com/23344536/16:24
cpaelzerthe CVEs are already in by the security Team16:24
cpaelzer2.5 is Xenial = LTS16:24
nacccpaelzer: would this be a MRE kind of thing?16:24
naccMicro Release Exception16:24
cpaelzerthat is kind of what I'm wondering about16:24
rharperI don't think so16:24
rharperthose are all bugs (just not filed against xenial)16:25
cpaelzerI'd think since it is only bug fixes not16:25
cpaelzerrharper: exactly16:25
naccrharper: ah ok16:25
cpaelzerI would suggest I open a bug and work against that over the next time, but wanted to ask for any objections16:25
cpaelzerlike "we usually don't because ..."16:25
rharperI think we should chat with the openstack team16:25
nacchttps://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases fwiw, MRE is for (aiui) bugfix microreleases upstream16:25
rharperthey possibly have a similar cadence of changes/fixes16:25
cpaelzerFYI - debian hasn't got to them since all releases are on 2.4.* or 2.6.* now16:25
naccthat's what i followed for php7.0, e.g.16:26
rharpernacc: ah, nice16:26
cpaelzernacc: interesting16:26
naccit just puts it on the SRU team radar to approve a 'new' upstream version (not normally allowed) in the SRU16:26
cpaelzerok, without objection I think I'll handle this as such microrelease16:26
rharpercpaelzer: won't that increase delta?16:26
rharperuntil sync?16:27
cpaelzerrharper: it will increase the delta to something that isn't maintained - that is what I tried to say above16:27
nacccpaelzer: fyi, LP: #1569609 is how i filed it16:27
cpaelzerDebian is either on <2.5 or >2.5 on all releases16:27
ubottuLaunchpad bug 1569609 in php7.0 (Ubuntu Xenial) "[SRU] microrelease exception for src:php7.0" [Wishlist,Fix released] https://launchpad.net/bugs/156960916:27
naccand y is already on 2.6.x right?16:27
naccrharper: so this would only be for x, aiui16:28
cpaelzeryes Y=2.616:28
cpaelzerexactly16:28
rharperwell, why not T or P ?16:28
cpaelzerit is only X for all of the Debian/Ubuntu world16:28
rharperI guess I don't get why we're doing it now and only for X ?16:28
cpaelzerrharper: I didn't check the same might apply for T (and update to 2.0)16:28
rharperit's a nice to have16:28
naccbecause somebody cares enough to do it? :)16:28
rharpernot a care16:28
rharpera _cost_16:28
rharperwhich we've not explored w.r.t impact on other choices16:29
nacci thought cpaelzer was saying the cost was we might get bugs for all of the bugfixes16:29
naccso we'd be backporting those individually to x16:29
rharperbut if we don't get those?16:29
nacci mean, they are known bugs in the upstream version x is based on16:29
rharperso, in the past, it's been a judgement call during the process16:29
cpaelzernacc: right, I thought those are known issues and fixing bugs in non emergency mode as a batch would be worth it16:29
naccrharper: yeah, i'm not sure what makes the most sense16:30
rharperlet's continue the discussion w.r.t trade-offs of time vs. benefit;  I think jgrimm and openstack folks should opine on the matter16:30
jgrimmcpaelzer, have you done any looking at the bugs fixed to see if any of that list seem critical?16:30
rharperwe could discuss this next week and return here with our findings16:31
cpaelzerjgrimm: just slightly, would need a bit more time to do so16:31
jgrimmi do think i can be swayed, as qemu is critical component to our stack16:31
naccsounds like an action item :)16:31
cpaelzerrharper: that is good, I'll analyze the severity and come back with it16:31
rharperright, and getting some input from other teams16:31
rharperwill it increase churn? help them out?16:31
cpaelzer#action cpaelzer investigating severity of issues covered by qemu 2.5. stable releases and ask other Teams on their input16:32
meetingologyACTION: cpaelzer investigating severity of issues covered by qemu 2.5. stable releases and ask other Teams on their input16:32
naccyeah, the testing impact is a good point, it's an integration point16:32
powersjcpaelzer: was that both of your topics?16:32
cpaelzerthat was one16:32
rharperone more =)16:32
jgrimmfwiw, the newton c-a, does _not_ include a y qemu.16:32
rharperjgrimm: it won't until Z16:33
rharperIIUC16:33
* cpaelzer is moving to second topic16:33
rharperthey pull from archive until it goes out of support16:33
jgrimmrharper, ack16:33
cpaelzerthat actually was brought up by rharper - which was TL;DR "We should follow-up on this:" in regard to VNIC offloads16:34
cpaelzerI think here is the right place to discuss, unless you prefer doing that via ML16:34
cpaelzer#link https://www.youtube.com/watch?v=NjlyutCppcU&list=PLrninrcyMo3IkTvpvM2LK6gn4NdbFhI0G&index=1016:35
rharpersure;  at netdev 1.2 there was a discussion on vnic performance and specifically offload features, in KVM and containers16:35
cpaelzerI checked Xenial and Yakkety and we were already at the recommended setting16:35
rharperexercised on top of 16.0416:35
rharperI wanted to see the paper/slides so I could get the data16:35
cpaelzerthe question is what else could/should we (not?) do based on that16:35
cpaelzerrharper: getting data would be nice - just to see if there are any outliers that we want to care for16:36
rharperyeah16:36
rharperexactly16:36
rharperspecifically  VM to VM and container to container (LXD)  vs. say docker (libnetwork )16:36
rharperbridge mode vs. something else16:36
cpaelzerwhat is good is that the most common "huge" case for us will be openstack and that is optimized a lot for east/west traffic in VM/VM16:36
rharperright16:37
cpaelzerabout 4 times faster than what they had, but getting access to the data would allow to get from "I assume" to "we know"16:37
cpaelzerand for the container east/west I'm interested to know about16:37
cpaelzerrharper: will you kindly inquire that data?16:37
rharperyeah, I need to look around for more details16:37
rharperthe other performance (which I don't know if the video covered)16:38
rharperis small-packet-performance, latency16:38
cpaelzerrharper: the video did not cover the others16:38
cpaelzerrharper: I had it running in background16:38
cpaelzerrharper: didn't come back to it16:38
rharperI ran across an interesting KVM paper on that;16:38
cpaelzerrharper: wait that was Stephen Hemminger right?16:38
rharperyes16:38
cpaelzerI'll likely meet him on Thursday on DPDK Userspace16:39
cpaelzerwhile I feel buried I tihnk I'll define another action for me16:39
cpaelzerat least to kindly ask for more there16:39
rharpersure16:39
cpaelzer#action cpaelzer will try to ask Stephen Hemminger for more data on the netdev presentation16:39
meetingologyACTION: cpaelzer will try to ask Stephen Hemminger for more data on the netdev presentation16:39
powersjany other actions?16:39
cpaelzerI stalled you long enough - I'm done16:40
powersjany other topics?16:40
jgrimmnacc, .. import status?16:40
powersjyes - shall I update the agenda to say "zesty" instead of "yakkety"?16:40
jgrimmpowersj, yes please!16:40
braunerhave we agreed on zesty as the new release name?16:40
powersj#ACTION powersj to update agenda to remove yakkety add in zesty16:41
meetingologyACTION: powersj to update agenda to remove yakkety add in zesty16:41
rharper#link http://www.linux-kvm.org/images/d/df/02x11-AspenMario_Smarduch-Migrating_NFV_applicatoins_to_KVM_Guest.pdf16:41
jgrimmbrauner: Zesty Zapus16:41
naccjgrimm: i need to sync with rbasak on tagging and we should be ready for 1.016:41
powersjbrauner: http://www.markshuttleworth.com/16:41
naccjgrimm: importer seemed to run fine last night on the packages we care about, i wanted to confirm with rbasak that all the MRs we did last cycle are tagged16:41
jgrimmcool.. we can start assigning out some merges once done and zesty open for business!16:42
naccjgrimm: my plan is to update all the lpusip trees by EOW and then we will look to flip over to lpusdp16:42
jgrimmgreat!16:42
naccworking on documentation today16:42
powersjlast call!16:43
powersj#topic Assigned merges/bugwork (rbasak)16:43
=== 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: Assigned merges/bugwork (rbasak)
powersjsince he is out, just a friendly reminder to update the sheet!16:44
* jgrimm thought he killed that from agenda16:44
powersjlol it is in the copy and paste page16:44
jgrimmahhh16:44
powersjI'll remove it16:44
jgrimmthanks16:44
powersj#topic Announce next meeting date, time and chair16:44
=== 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
powersjSame time, same place16:44
powersjbeisner will be our host16:44
powersjthat's all folks!16:45
powersj#endmeeting16:45
=== 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 Oct 18 16:45:06 2016 UTC.16:45
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-10-18-16.03.moin.txt16:45
rharperpowersj: thanks !16:45
naccpowersj: thanks!16:45
jgrimmthanks powersj16:45
powersjo/16:45
jgrimmpowersj, http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-10-18-16.03.moin.txt17:19
powersjjgrimm: brilliant thank you17:19
jgrimmnp, you'll see that above ^^ when you did your endmeeting17:20
powersjoh look at that :)17:20
xnoxcpaelzer, yeah adam will send archive open for development email, when it's open.22:03
xnoxif you upload things now they will just be stuck in unapproved queue for zesty22:03

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