[13:01] <lool> heyo
[13:01]  * stgraber waves
[13:01] <lool> stgraber, barry, ogra_: Around?
[13:01]  * barry waves
[13:01]  * ogra_ moos
[13:02] <lool> so let's perhaps start with a quick status?
[13:03] <lool> good news is that the system-images are now formally official  :-)
[13:03] <barry> \o/
[13:03] <lool> and the recommended images, except if you run into SDK bugs
[13:03] <lool> stgraber blogged this, mailed ubuntu-phone and this got decently G+-ed, so I think the news is out
[13:04] <lool> I had some back and forth with community team to try to get the words passed to larger circles, but I guess we're covered for now
[13:04] <lool> stgraber: you want to update us on the channel aliases work and importer work you have been doing?
[13:04] <stgraber> sure
[13:05] <stgraber> so over the past couple of work days I've implemented the new channels.json format to allow the flexiblity needed for channel aliases and hidden channels
[13:05] <stgraber> barry implemented the client side of that in 1.5 which landed on Friday
[13:05] <stgraber> (I still need to update the wiki, will do that today)
[13:05] <stgraber> then after that, I've been working on adding the code needed for the channel aliasing
[13:06] <barry> (technically sunday with 1.5.1 which fixed a test failure on 32 bit ;)
[13:06] <stgraber> I finished that yesterday with all the tests passing and 100% code coverage
[13:06] <stgraber> next up is moving the existing cleanup script to the python module and have tests for that
[13:06] <stgraber> and once I'm done with that, implement the new channel management tool (not so much a cdimage importer anymore)
[13:07] <stgraber> that last one will probably take me at least a couple of days because of how complex it can get and how long test runs take
[13:07] <lool> ok; thanks
[13:07] <stgraber> but I'm hopeful that we'll be able to transition to it by end of week (that's assuming we can get an image with 1.5.1 promoted today, otherwise we'll need to wait a bit longer for people to get the new client)
[13:07] <lool> barry: so you've worked on client updates; what are the latest news?
[13:09] <barry> the new version numbering support landed.  re-started work on d/l service integration, but that was put on hold to get the new channels.json format supported.  both of those features have landed.  i'll be getting back to d/l service integration today
[13:09] <barry> eot
[13:10] <lool> cool
[13:10] <lool> looking at https://blueprints.launchpad.net/ubuntu/+spec/foundations-1308-os-updates
[13:11] <lool> repartitioning is still WIP/future
[13:11] <lool> the rest should be targeted at 13.10, channel aliases, upgrade boot scripts, download service
[13:11] <lool> switching to android.deb to get android bits
[13:11] <lool> there are a couple of issues with the current images
[13:12] <lool> we fixed some over Friday / the week end
[13:12] <lool> but there might be more
[13:12] <lool> there are two bad cases of people currently disable system-image that we need to help resolve
[13:12] <lool> one is QA tests that are currently switching to rw to run the tests
[13:13] <lool> the other is SDK team (apt-get install openssh and qdeclarative packages and g++)
[13:13] <ogra_> FYI, here at the QA sprint people are working on fixing the fact that we dont actually do ro testing
[13:13] <lool> ogra_: cool
[13:13] <ogra_> i hope that is fixed by end of the week
[13:13] <lool> stgraber: I guess you might get queries from QA team / SDK team as they discover things in the image that ought to be rw
[13:13] <ogra_> right
[13:13] <ogra_> thats also one big topic here this week
[13:14] <ogra_> inpescting the image and finding all missing rw dirs
[13:14] <lool> I know there is sadly noone with time to work on fixing the SDK use cases right now
[13:14] <ogra_> *inspecting
[13:14] <lool> higher priority projects underway
[13:14] <lool> ogra_: ok
[13:14] <ogra_> lool, my task for today is getting sshd to work for the SDK
[13:14] <stgraber> lool: yep, that's fine, updating lxc-android-config is pretty quick so long as it's either a single file that usually doesn't change outside of user's control or an empty directory.
[13:14] <lool> ogra_: if folks there don't know how to fix it, let stgraber or me know
[13:14] <ogra_> that should get us a step forward
[13:14] <ogra_> yeah
[13:14] <lool> ogra_: cool
[13:14] <stgraber> if it's something else, it usually requires some more thinking (which is why I like being the gate keeper for that :))
[13:14] <lool> ogra_: so you will likely need a new rw path
[13:15] <lool> ogra_: I'm expecting we will ship a openssh-server.override upstart job which disables it on startup and some sudo script will reenable it if people enable developer mode
[13:15] <lool> ogra_: you'll need this openssh-server.override file to be rw
[13:15] <stgraber> ogra_: my guess for sshd is that we want it installed by default, with a .override saying manual and the override file and all the host keys marked writable with migration enabled
[13:15] <ogra_> well, lets see :)
[13:16] <lool> stgraber: migration?
[13:16] <ogra_> i dont really want us to re-write conffiles
[13:16] <lool> ogra_: wouldn't be a conffile?
[13:16] <ogra_> its in /etc/init/
[13:16] <lool> yes?
[13:16] <ogra_> i'll rather make it read some variable from somewhere else in the override job
[13:17] <lool> ogra_: I think this is similar to e.g. changing your timezone
[13:17] <stgraber> sure, that works too
[13:17] <barry> i guess we can't just make sshd start on boot for everyone eh? ;)
[13:17] <lool> I think this is too slow
[13:17] <lool> notably key generation on first start
[13:17] <lool> /!\ make sure we don't ship the same host keys to everyone   :-)
[13:17] <stgraber> the trick will be to get ssh to agree to generate new keys to empty files instead of missing fils
[13:17] <stgraber> *files
[13:17] <ogra_> lool, indeed
[13:18] <stgraber> because we can't mark all of /etc/ssh writable due to the other config files in there, so we need to mark the individual key files as writable
[13:19] <lool> right; not easy to trick sshd in installing the keys properly once generated
[13:19] <lool> (similar to sed -i issue in qa-regression-testing)
[13:19] <lool> ok
[13:19] <lool> ogra_: did you have updates on images that you wanted to share?
[13:20] <lool> otherwise, I am happy to open the floor to AOB
[13:20] <ogra_> lool, nothing special, nope
[13:20] <ogra_> (apart from the ro tests and ssh)
[13:20] <lool> were there specific things that you folks want to discuss today outside of things we covered above?
[13:20] <lool> I'd like to make this meeting biweekly
[13:20] <stgraber> I think we'll need the rootfs build to create empty key files in /etc/ssh/, then have code doing the ssh-keygen to the writable target (/userdata/system-data/etc/ssh/) on the device after removing the empty files in there. Once done, reboot and it should be all good.
[13:21] <lool> stgraber: sounds good
[13:21] <barry> biweekly sounds good
[13:21] <stgraber> ogra_: anyway, let me know what you come up with so I can quickly confirm there shouldn't be problems with that in the future
[13:21] <stgraber> I'm fine with biweekly too
[13:21] <stgraber> I won't be there next week anyway (Plumbers)
[13:22] <lool> ogra_: I'd like us to get updates on the QA efforts in some way; what's the best way?
[13:22] <lool> would folks at the sprint grab us on #ubuntu-touch?>
[13:22] <lool> there was a weekly hangout, but it got cancelled
[13:22] <ogra_> well, i'm mainly sitting with my team in a separate room, i guess asac participates a lot more in the cross team meetings
[13:23] <lool> ogra_: who should we ask?  paul larson and doanac?
[13:23] <lool> I guess we can ping them in a couple of days
[13:23] <lool> if we dont hear any queries  :-)
[13:23] <lool> ok; I guess that's it for today then!
[13:23] <lool> have a good end of day everyone
[13:24]  * lool waves
[13:24] <ogra_> you too :)
[13:24] <barry> cheers!
[13:27] <ogra_> lool, heh ... i just noticed your claendar invitation says "Bieekly upgrader ...."
[13:53] <lool> ogra_: fixed thanks
[16:03] <smoser> roaksoax, ping
[16:03] <hallyn_> i think arosales will be stepping up today
[16:04] <arosales> roaksoax, isn't able to chair this seek
[16:04] <arosales> sorry smoser ^
[16:04] <arosales> hallyn_, were you interested in chairing
[16:04] <smoser> i can do it.
[16:04] <smoser> #startmeeting
[16:04] <hallyn_> arosales: i just did last week :)  don't have stuff ready, but can in 2 mins if it's not convenient for you
[16:04] <hallyn_> k
[16:05] <smoser> #startmeeting ubuntu-server-team
[16:05] <arosales> I can cover
[16:05] <hallyn_> hm?  not working?
[16:05] <arosales> or it looks like smoser
[16:05] <smoser> well, no bot i think
[16:06] <smoser> meetingology seems gone.
[16:07] <arosales> smoser, should we just proceed with out it?
[16:07] <smoser> give 3 minutes.
[16:08] <smoser> 12:10. then go on without.
[16:08] <smoser> trying to find it.
[16:10] <smoser> k.
[16:10] <smoser> 12:10. i'll start
[16:10] <smoser> #startmeeting ubuntu-server-team
[16:10] <smoser> #topic Review ACTION points from previous meeting
[16:10] <smoser>  * everyone spend extra time triaging bugs this week
[16:10] <smoser> i think i saw hallyn do that, but i'm not sure of anyone else, and I know i was delinquent.
[16:11] <hallyn_> wellt he list is still long enough that we could use another week of it
[16:11] <smoser> reguarding Meetingology, i pinged AlanBell just now as the contact per
[16:11] <hallyn_> i may dedicate tomorrow to it
[16:11] <smoser> https://wiki.ubuntu.com/IRC/Bots
[16:11] <smoser> ok. so we'll push that again.
[16:11] <smoser> #action  everyone spend extra time triaging bugs this week
[16:11] <smoser> topic Saucy Development
[16:11] <smoser> #topic Saucy Development
[16:11] <smoser> https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[16:12] <smoser> We just passed Beta 1.  So we're moving towards a release some time.
[16:12] <smoser> utlemming cut beta-1 cloud images for us.  and we have daily images of those of course.
[16:12] <smoser> #topic ReleaseBugs
[16:13] <smoser> bug 1221906 seems like adam_g is on it.
[16:13] <smoser> bug 1208455.
[16:13] <smoser> smb did you make any progress there ?
[16:13] <smb> A bit
[16:14] <AlanBell> hi smoser
[16:14] <smb> Got a rough bisection done. Which leads to some rework of nested VMX code
[16:14] <smoser> hey, AlanBell . we're missing your bot. :)
[16:14] <smb> But I think I need some upstream help to dig deeper
[16:14] <smoser> smb, ok. thanks.
[16:14] <smoser> bug 1213915
[16:15] <smoser> hm.. i'll leave that on jamespage. to push on a archive admin.
[16:15] <smoser> bug 1206872
[16:17] <smoser> that looks like incomplete at the moment... that should probably get off this list.
[16:17] <smoser> bug 1156932
[16:18] <smoser> hm.. that seems languishing. wonder if still relevant.
[16:18] <smoser> bug 1199791
[16:18] <smoser> bug 1170393 and bug 1222180 show fix-committed
[16:20] <smoser> bug 1188069, mdeslaur should we not have fixed that in saucy?
[16:20] <smoser> ok. so i think we should probably do something to some of those bugs so that they're not on this list.
[16:21] <smoser> bug 1206872 and bug 1156932 seem not really relevant.
[16:21] <smoser> so moving on.
[16:21] <smoser> #topic blueprints
[16:21] <smoser> http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html
[16:22] <smoser> well, that clearly shows we have a lot of work to do :)
[16:22] <smoser> please just take some time and get your pblueprints into order.
[16:23] <smoser> i still have plenty of work to do. i fthere are things that you're not going to get to, consider postpone.
[16:23] <smoser> topic Weekly Updates & Questions for the QA Team (plars)
[16:23] <smoser> #topic Weekly Updates & Questions for the QA Team (plars)
[16:23] <smoser> plars,  ?
[16:23] <plars> smoser: you still have my name on this? :) but nothing this week, psivaa and I are both at a sprint
[16:24] <smoser> should your name not be here ?
[16:24] <psivaa> it would help to change it to mine
[16:24] <smoser> ok.
[16:24] <smoser> can-do
[16:24] <psivaa> thanks
[16:24] <smoser> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:24] <smb> Xen-4.3 has been uploaded (but needs to be NEWed), thanks zul. Otherwise nothing to report. Any questions?
[16:24] <plars> smoser: I moved this to psivaa a while back, but we might ought to check if it should go to someone on the qa team or to him still
[16:25] <smoser> plars, updated https://wiki.ubuntu.com/ServerTeam/Meeting
[16:25] <smoser> smb i dont have anything.
[16:25] <smoser> probably noteworth to many here.. bug 1206961 is now 'fix-released'
[16:25] <smoser> everywhere.
[16:26] <smoser> which means if nested virt is available, you'll get it in a cloud image without having to reach for linux-image-extra-virtual.
[16:26] <smoser> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:26] <hallyn_> (which means more ppl will hit the other bug)
[16:26] <rbasak> Nothing new to report. Any questions for me?
[16:27] <smoser> hallyn_, whats the other bug ?
[16:27] <hallyn_> nested kvm on intel failing in saucy
[16:27] <smoser> ah. yeah.
[16:27] <hallyn_> (more ppl hitting it => good thing)
[16:27] <smoser> #topic Ubuntu Server Team Events
[16:27] <smoser> I think LinuxCon and CloudOpen are both next week.
[16:28] <smoser> ttx told me he was going.
[16:28] <smoser> anyone have anythign else?
[16:28] <smoser> #topic Open Discussion
[16:28] <smoser> i dont hae much here. just that we're really in crunch time in the cycle.
[16:28] <smoser> pleae file bugs and subscribe or assign people for work you know needs to be done.
[16:29] <smoser> #topic Announce next meeting date and time
[16:30] <smoser> next meeting will be Tuesday Sep 17 at 16:00 UTC
[16:30] <smoser> #endmeeting
[16:30] <hallyn_> thx smoser
[16:38] <arosales> smoser, thanks for chairing ubuntu server meeting
[16:39] <mdeslaur> smoser: re: 1188069: saucy isn't affected. Updated bug. Thanks.
[17:00] <jsalisbury> #startmeeting
[17: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/Meeting
[17:00] <meetingology> Meeting started Tue Sep 10 17:00:16 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available 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 #votesrequired
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[17:00] <jsalisbury> # Meeting Etiquette
[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> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <rtg> o/
[17:00] <sconklin> o/
[17:00] <bjf> o/
[17:00] <henrix> o/
[17:00] <smb> o/
[17:00] <cking> \o
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> Fixes for Calxeda's NIC and Omap4 mmc landed in S/master-next, and patches
[17:01] <ppisati> to handle the DTB concatenation and the generic-lpae kernel flavour were
[17:01] <ppisati> submitted to the flash-kernel mantainer.
[17:01] <ppisati> In the mean time, while testing the Calxeda kernel a new panic crop up and
[17:01] <ppisati> investigation is ongoingi (no LP bug was filled yet since we are still ruling out
[17:01] <ppisati> the hardware).
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <jsalisbury> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <jsalisbury> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:02] <jsalisbury> || apw       || foundations-1305-arm64-bringup     || 2 work items ||
[17:02] <jsalisbury> || bjf       || foundations-1308-kernel            || 1 work item  ||
[17:02] <jsalisbury> || cking     || foundations-1308-power-measurement || 1 work item  ||
[17:02] <jsalisbury> || ogasawara || foundations-1308-kernel            || 1 work item  ||
[17:02] <jsalisbury> || ppisati   || foundations-1305-kernel            || 1 work item  ||
[17:02] <jsalisbury> || smb       || servercloud-s-virtstack            || 1 work item  ||
[17:02] <jsalisbury> ||           || servercloud-s-openstack-hypervisor || 1 work item  ||
[17:02] <jsalisbury> Note: Some of the WI's listed in the table above don't show up in any of
[17:02] <jsalisbury> the tracking pages due to the BP's needing to get properly assigned to a
[17:02] <jsalisbury> series (ie Saucy).  I'll try to get this sorted with the BP owners.
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:03] <jsalisbury> As noted last week, v3.11 final has been released and we have already
[17:03] <jsalisbury> rebased.  We have uploaded this to the Saucy archive and it should be
[17:03] <jsalisbury> available for testing.  Please let us know your results.  We will
[17:03] <jsalisbury> continue to track the upstream stable v3.11.x releases as we move
[17:03] <jsalisbury> forward.
[17:03] <jsalisbury> -----
[17:03] <jsalisbury> Important upcoming dates:
[17:03] <jsalisbury> [LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[17:03] <jsalisbury> Thurs Sep 19 - Final Beta Freeze (~1 week away)
[17:03] <jsalisbury> Thurs Sep 26 - Final Beta (~2 weeks away)
[17:03] <jsalisbury> Thurs Oct 03 - Kernel Freeze (~3 weeks away)
[17:03] <jsalisbury> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's
[17:03] <jsalisbury> == 2013-09-10 ==
[17:03] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:03] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <jsalisbury> ..
[17:04] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:04] <bjf> Status for the main kernels, until today (Sept. 10):
[17:04] <bjf>   *   Lucid - Skipping this cycle
[17:04] <bjf>   * Precise - Prep'ing Packages
[17:04] <bjf>   * Quantal - Prep'ing Packages
[17:04] <bjf>   * Raring  - Prep'ing Packages
[17:04] <bjf> Current opened tracking bugs details:
[17:04] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <bjf> For SRUs, SRU report is a good source of information:
[17:04] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Sep 10 17:04:59 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-10-17.00.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-10-17.00.html