16:02 <arosales> #startmeeting ubuntu-server-team 16:02 <meetingology> Meeting started Tue Aug 18 16:02:42 2015 UTC. The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:02 <meetingology> 16:02 <meetingology> Available commands: action commands idea info link nick 16:02 <arosales> #topic Review ACTION points from previous meeting 16:03 <arosales> smoser to check with Odd_Bloke on status of high priority bug 1461242 16:03 <ubottu> bug 1461242 in cloud-init (Ubuntu Vivid) "cloud-init does not generate ed25519 keys" [Medium,Confirmed] https://launchpad.net/bugs/1461242 16:03 <arosales> fix released now so we should be ok on that bug 16:03 <arosales> rharper, I think you were going to review numad 16:04 <arosales> any actions or follow up we should document? 16:04 <arosales> I'll take it that numad was reviewed properly there, if there are any comments around numad please ping here 16:04 <arosales> #topic Wily Development 16:04 <arosales> #link https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule 16:05 <rbasak> So feature freeze is on Thursday. 16:05 <rbasak> I've been busy working on things with that deadline and so haven't reviewed anyone's bug fix submissions yet, sorry. 16:05 <arosales> I know coreycb and folks are working hard on the OpenStack pacakges 16:05 <arosales> busy week with feature freeze 16:05 <arosales> #subtopic Release Bugs 16:06 <arosales> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server 16:06 <arosales> I think we said here that bugs are behind feature freeze atm 16:06 <arosales> only 1 high bug atm 16:06 <rbasak> Does anyone have anything that needs sponsoring that is an item that cannot be uploaded after feature freeze? 16:06 <arosales> https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149 16:06 <ubottu> Launchpad bug 1478149 in python-tornado (Ubuntu Wily) "python-tornado tests fail against python3.5" [High,Triaged] 16:07 <arosales> slangasek marked that one as high so looks like it needs a review 16:08 <arosales> volunteers? 16:08 <arosales> ok ping if any folks can take a look at 1478149 16:08 <arosales> #topic Server & Cloud Bugs (caribou) 16:09 <arosales> caribou any updates for server and cloud bugs? 16:09 <arosales> . 16:09 <arosales> . 16:09 <arosales> . 16:09 <arosales> #topic Weekly Updates & Questions for the QA Team (matsubara) 16:09 <arosales> matsubara, any bits for QA? 16:09 <arosales> . 16:09 <arosales> . 16:09 <arosales> . 16:09 <matsubara> Completed SRU verification for bug 1336742 16:09 <arosales> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges) 16:09 <ubottu> bug 1336742 in squid3 (Ubuntu Trusty) "Caching responses with "Vary" header" [Medium,Fix committed] https://launchpad.net/bugs/1336742 16:10 <matsubara> other than that, nothing else to report arosales 16:10 <arosales> thanks matsubara 16:10 <arosales> good to hear SRU verified for 1336742 16:10 <arosales> smb, sforshee, arges: any bits from kernel? 16:10 <arosales> . 16:10 <arosales> . 16:10 <arosales> . 16:10 <rharper> arosales: just missed you earlier on numad, no progress on that front at this time, I'll carry the action for a bit till we get some time 16:11 <arosales> # action rharper review numad 16:11 <arosales> trhanks rharper 16:11 <arosales> #topic Upcoming Call For Papers 16:11 <arosales> I don't know of any upcoming events for CFP deadlines, any ones folks would like to bring up? 16:11 <arosales> . 16:11 <arosales> . 16:12 <arosales> . 16:12 <arosales> #topic Ubuntu Server Team Events 16:12 <arosales> Any upcoming event folks would like to call out? 16:12 <arosales> #link http://insights.ubuntu.com/event/juju-charmer-summit-2015/ 16:12 <arosales> if folks are interested in Juju and Charm authoring 16:12 <arosales> #topic Open Discussion 16:12 <arosales> Any other topics? 16:12 <arosales> . 16:12 <arosales> . 16:12 <arosales> . 16:12 <rharper> rbasak I wanted to chat about the bcache-tools sru 16:13 <rbasak> Sure 16:13 <rharper> what all do we need to bring that into trusty ? 16:13 <rbasak> It will probably need a tech board exception. Technically the SRU team could choose to accept it I think, but historically they never do. So best to send to the TB in the first instance to save time IMHO. 16:14 <rharper> right, ok 16:14 <rbasak> Once that's done, a backport needs to be prepared and tested, sponsored and then the SRU team will be able to accept it in the usual way. 16:14 <rharper> is there a general template, or do we fill out the SRU info in the bug and forward that ? 16:14 <rharper> ok, I suggest we do some of the work in parallel 16:14 <rharper> I know we've tested the vivid version in trusty 16:14 <rharper> not clear about what's currently in wily 16:14 <rbasak> We don't really have a template as it's pretty exceptional. An email to the tech board mailing list with a request and justification should do. 16:14 <rharper> which I suppose is what we'd bring in? instead of vivid version ? 16:15 <rharper> rbasak: ok 16:15 <rbasak> We'd want to backport something that's already in the archive ideally. 16:15 <rharper> ok 16:15 <rbasak> If the Vivid version is tested and the Wily version is at increased risk of introducing regression (as opposed to fixing bugs that we want in the backport) then I don't see any reason why we can't backport the Vivid version. 16:16 <rharper> sure 16:16 <rharper> I'll have a look at the delta 16:16 <rbasak> Thanks! 16:16 <arosales> #topic Announce next meeting date, time and chair 16:16 <arosales> #info NEXT MEETING: Tuesday 2015-08-25 at 1600 UTC - #ubuntu-meeting 16:17 <arosales> next chair = gnuoy 16:17 <arosales> thanks! 16:17 <kickinz1> Thanks arosales 16:17 <arosales> #endmeeting