=== emma is now known as em [13:01] stgraber, barry: Hey [13:01] lool: hi [13:01] ogra_: hallo [13:01] hey ho [13:02] * stgraber waves [13:02] I think we have two things for this week [13:03] switch to new numbers + announcement on one side, and blueprint / starting work for stuff we've discussed at vUDS [13:03] stgraber, barry: So I read stgraber had tested updating to new version numbers [13:03] I did too [13:03] I had to manually trigger the update once [13:04] then it picked up the update from 17 to 18 in daily-barry [13:04] but first, do you folks have other agenda items? :-) [13:04] * ogra_ doesnt [13:04] nope [13:05] nope, first thing on my todo is to drop daily-barry, archive daily and daily-proposed, re-import both of them with the new numbering and write+send the announcement [13:05] sounds great [13:05] i haven't tried upgrading since friday, but good to hear it worked for lool and stgraber [13:05] then start updating the wiki and file bugs for the next bits on my list (channel aliases being pretty high up on it) [13:06] when do you think we can drop support in the client for the old version numbers? [13:06] barry: I had to use the cmdline to trigger the update with -b0 though, but I think that was expected? [13:06] lool: yes, expected [13:06] barry: give it 10 days or so? [13:06] lool: sounds good to me [13:06] (tbh, it's more tech debt than anything else) [13:07] ok; there's a hangout with QA team later today where we should get latest status on them testing the new images [13:07] I think that's all [13:07] asac: what were your questions WRT the switch? [13:07] barry: well, in theory you can do that tomorrow since we won't be publishing updates with the new format [13:08] stgraber: ack [13:08] hmm right, perhaps we want to keep the option of a roll back for a couple of days [13:08] but that's it I guess [13:08] lool: wanted an ETA when you guys feel we are in a state that we should start focussing on the touch_ro dashboard [13:08] yeah, I guess it doesn't hurt to keep it as a rollback option for a few days [13:08] asac: last week? :-) [13:08] lool: so all the technologyu parts have landed etc.? [13:09] yes [13:09] we switch numbering scheme Friday, so we delayed until today to announce [13:09] e.g. we can go into stabilization/testing and later, switch default mode [13:09] ok [13:09] so what will be announced today? [13:09] today we want to announce that the new images are ready for wide consumption [13:09] lool: doesn't matter really. i won't even start on that until after the d/l service integration (unless i find it's a blocker, but i doubt it) [13:10] I don't think we'll have a phablet-flash default, but we should switch the QA tests to use these now [13:10] lool: whats the diff on the dashboard? [13:10] lool: can we get the dashboard first into shape? [13:10] LP: #1220238 [13:10] http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/ [13:10] Launchpad bug 1220238 in Ubuntu system image "Remove support for old version numbers" [Low,Triaged] https://launchpad.net/bugs/1220238 [13:10] asac: apparently QA team was still converting some tests to run on the host as they were too big to apt-get install [13:10] those should have more or less the same results [13:10] asac: but we have a hangout later today with QA team that might be better suited to bring this up [13:10] (nobody from QA here0 [13:10] so right now we cannot promote images to /current [13:11] which means its not very good if we ask folks to move over [13:11] lets first get our dashboard in shape [13:11] barry: might want to check with mandel when the updated download service is landing [13:11] barry: he seemed to be changing the API a bit; not much, but still [13:11] lool: yep, on my plate :) [13:11] lool: do we have a tool to promote images? [13:12] is that one ready? [13:12] asac: it's hooked to the promotion of current [13:12] ok [13:12] well not so ok :) [13:12] but ok [13:12] :) [13:12] well, you could switch it manually if needed I guess [13:12] stgraber: ^ [13:12] so lets not announce them until we have valid results [13:12] but we should avoid this [13:12] asac: I'm not in favor of delaying the announcement [13:12] we want more people testing these [13:13] only if we decouple promotion [13:13] i dont want to promote stuff like this [13:13] lool: you can announce that people should try, but dont announce that they should use it as their default [13:13] so you would like separate promotion of pending -> current and daily-proposed -> daily [13:13] because they are tested separately [13:13] right [13:14] I can see how this makes sense, but it's bad if latest daily and latest current are different [13:14] we have different results as well [13:14] and we want to stop testing pending -> current altogether [13:14] not so sure about that one... for me its two different channels [13:14] so i dont have a problem if they are out of sync [13:14] we want to move over to touch_ro and kill the other [13:14] yes [13:14] right. so decouple so we can fix touch_ro [13:14] so I think it's a bit overzealous to maintain two systems [13:14] and not stop promoting the old image [13:15] asac, we cant stop promoting it === psivaa is now known as psivaa-lunch [13:15] it is used by ports ... we have no option for them to use system image [13:15] ogra_: right. i dont want to stop promoting cdimage-touch [13:15] which would happen if i know that i promoote touch_ro at same time [13:16] we will stop testing the cdimage ones [13:16] yeah, we only can do that in case we figure out how community can provide self signed images [13:16] ports can test their own images in situ [13:16] can we move that part offline :) [13:16] well, we test the same content in system imagess [13:16] all i sam saying is: if /pending -> /current automatically promotes touch_ro, then i cant promote cdimage-touch [13:16] ok [13:16] so as long as they work there it is likelz they also work in cdimage images [13:16] if touch_ro is red [13:17] cdimage touch should jprobably ust drop current and pending ... and grow a /latest :) [13:17] asac: *we* have a single set of images that we care about; we just keep the option of using cdimage images available for ports, or for engineers that want to test this intermediate step, but it's not considered a product / baseline [13:17] lets discuss that _after_ we have moved over to touch_ro [13:18] lool: right, but right now its soo bloody red [13:18] the only thing _we_ will be testing are the system-image images [13:18] if you would have come to me at a day where its 92% [13:18] i would have had more faith that coupling both is fine for the transition period [13:18] asac, you came to us ! [13:18] asac: but nobody retries stuff on touch_ro [13:18] buyt seems that our infrastructure is just not ready for the touch_ro [13:18] right [13:18] so lets do that this week [13:18] :) [13:18] focus on getting touch_ro also working [13:19] on infrastructrure [13:19] stgraber: would you mind attending the QA hangout later today? [13:19] i would prefer if the system-image team would drive that part [13:19] I'd like to get a final date agreed to announce this [13:19] lool: sure, I can do that [13:19] e.g. until you reach like 90% [13:19] then i am happy to take it over [13:19] stgraber: I think we should do the renumbering today and announce it though [13:19] stgraber: perhaps just on ubuntu-phone ML [13:19] +1 on renumbering announcement [13:20] asac: who will track the switch of QA to RO images? [13:20] we can discuss in the hangout I guess [13:20] asac: I'll chat with you about this [13:20] yeah, I'll do the renumbering as scheduled [13:20] ok, the other thing is updating the bps post-vUDS [13:20] stgraber, barry: I didn't copy workitems over from the session [13:21] lool: this team would drive the part [13:21] until its good [13:21] like 80% [13:21] again [13:21] asac: like us? [13:21] asac: or QA team? [13:21] no you guys should drive [13:21] its your landing [13:21] and you are seeing red in the dashboard [13:21] :) [13:21] this doesn't make sense, we don't have any control over this [13:21] well, but you are the drivers [13:21] lool: i'll double check, though tbh i find the bug tracker a *much* better way to track work than blueprints :/ [13:21] not saying you have to do all the work [13:22] just drive it [13:22] asac: we can't fix QA infrastructure or QA scripts; we can only advice on how ot implement -- which we did [13:22] lool: i asked psivaa-lunch now to give it love like we do on touch [13:22] lool: you can notify them abvout that [13:22] and ask for retries etc. [13:22] or ask for help [13:23] asac: but we want a single contact in QA team; so psivaa you say? [13:23] ok [13:24] lool: psivaa-lunch and plars are your entry points [13:24] to get stuff retried [13:24] etc. [13:24] stgraber: gah, can't find the bp from 13.08 vuds again [13:24] ah it was upate on OS updates [13:24] and it was just for summit [13:25] stgraber, barry: Well, bugs are fine for tracking, but to bubble them up to the workitem tracker we need to link them to some blueprint [13:25] I just wanted us to agree on teh blueprint we'll use going forward [13:25] do we update the 1305 one, or use the 1308 from vUDS, or yet another one? [13:26] lool: everything on the old one should be marked as done or postponed [13:26] lool: and we should use https://blueprints.launchpad.net/ubuntu/+spec/foundations-1308-os-updates until next vUDS [13:26] ok [13:27] i'm fine with using the new one. i'll do some housekeeping on the 1305 one [13:27] I can copy over stuff from 1305 to 1308 [13:27] can you two update it with new stuff? [13:27] lool: sure [13:27] yeah, I don't think I've looked at the old blueprint since the last vUDS so I suspect my work items are pretty out of date [13:27] https://blueprints.launchpad.net/ubuntu/+spec/foundations-1305-image-based-updates [13:27] barry: just link the bugs there [13:27] lool: +1 [13:28] hmm when using bugs we can't postpone them [13:28] anyway [13:28] ok; that's all I had [13:28] anything else from you folks? [13:28] nope [13:28] I wanted to make this meeting biweekly with the announcement of new images [13:29] stgraber, ogra_, barry, asac: Ok; thanks all! [13:29] thanks [13:29] nothing else here. I'll switch to the new version numbers in a bit, it'll take a few hours to re-import everything [13:29] cheers [13:30] then will nag QA to re-run the tests and see how things behave. I expect they'll have to go through several run of fixing the tests before things start looking good (I don't expect changes to the image to be required) [13:30] oh and I have no idea how the QA website will handle a new image replacing a broken one in daily-proposed [13:31] since it'll have the same version number === kyleN is now known as kyleN-afk === psivaa-lunch is now known as psivaa === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [15:58] o/ [15:58] evening folks [15:59] o/ [15:59] \o [16:00] \o [16:01] o/ [16:01] hiho [16:01] #startmeeting [16:01] Meeting started Tue Sep 3 16:02:22 2013 UTC. The chair is hallyn_. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:01] 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 [16:02] #topic Review ACTION points from previous meeting === meetingology changed the topic of #ubuntu-meeting to: Review ACTION points from previous meeting [16:02] arosales to update Juju blueprints [16:02] hallyn_, got some good updates during the sprint last week. [16:02] and bp is updated? [16:03] will assume yes :) [16:03] hallyn_ to coordinate with zul and smb on testing xen 4.3 on nova [16:03] done - tested fine [16:03] zul to follow up on mariadb/percona making it into Saucy [16:04] zul: done? [16:04] we have a catchup in +2 hrs about that with percona [16:04] mariadb is still in review in Debian [16:04] cool, i'll count that as up-followed [16:04] thx [16:04] and percona expect to work on it next month [16:04] saucy looking unlikely [16:04] ok [16:04] #topic Saucy Development === meetingology changed the topic of #ubuntu-meeting to: Saucy Development [16:05] #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server [16:06] looking through the high prio ones, not sure those pertain to us [16:06] oh there we go [16:06] hallyn_, yes sorry for the delay. Yes got some good BP updates [16:06] bug 1208455 - we can talk about during smb's section [16:06] bug 1208455 in linux (Ubuntu Saucy) "general protection fault running apt-get inside double nested kvm VM" [High,In progress] https://launchpad.net/bugs/1208455 [16:07] arosales: great, thanks [16:07] bug 1213915 [16:07] bug 1213915 in ceph (Ubuntu Saucy) "Please demote ceph-mds and ceph-fs-common to universe" [High,New] https://launchpad.net/bugs/1213915 [16:07] jamespage: ? [16:07] with archive admins [16:07] no further action on our part required [16:07] thx [16:07] bug 1206872 [16:07] bug 1206872 in samba (Ubuntu Saucy) "samba fails to unpack (behavior change in patch) and ftbfs on aarch64" [High,Incomplete] https://launchpad.net/bugs/1206872 [16:07] zul: ^ ? [16:07] also bug 1156932 [16:08] bug 1156932 in python-novaclient (Ubuntu Saucy) "User can't modify security-group-rule via nova-api if there are duplicated security group name" [High,Confirmed] https://launchpad.net/bugs/1156932 [16:08] thats fixed [16:08] will look at it this week [16:08] and bug 1199791 [16:08] bug 1199791 in nova (Ubuntu Saucy) "nova-compute-xcp misses nova-compute.conf" [High,Triaged] https://launchpad.net/bugs/1199791 [16:08] jamespage: the samba one/ [16:08] yeah [16:08] nova security groups thing is not and probably won't be I guess [16:08] jamespage: i was hoping for the nova security one ;) [16:08] nah [16:08] jamespage: sorry, won't be what? [16:08] its not that of a biggy [16:08] won't be fixed [16:08] ok [16:09] last high prio one is bug 1214615 [16:09] bug 1214615 in juju-core (Ubuntu Saucy) "package juju-core 1.13.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2" [High,Fix released] https://launchpad.net/bugs/1214615 [16:09] I just closed that [16:09] I realized my mistake just after uploading but someone raised a bug Idid not spot [16:09] i see that :) thx [16:09] ok, so moving on to blueprints [16:09] that horizon r/w on /usr/share is a pig as well [16:09] * jamespage bumps the priority [16:10] jamespage: oh? [16:10] I hit is yesterday when testing a few updates for horizon [16:10] bug 1216019 [16:10] I'll have a look [16:10] bug 1216019 in horizon (Ubuntu Saucy) "Horizon default config assumes www-data has R/w on /usr/share... directory" [High,Confirmed] https://launchpad.net/bugs/1216019 [16:10] jamespage: thx [16:10] yeah - horizon tries to store/retrieve a secret [16:10] is horrid [16:11] ok, so moving on - [16:11] [LINK] http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html [16:11] arosales: jamespage: ^ [16:11] * hallyn_ defers [16:11] good oh [16:11] smoser, jamespage did vUDS allow for some good BP updates? [16:11] looks like everything might have had a good catchup after uds last week [16:12] ah ok [16:12] roaksoax, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2 [16:12] any updates? [16:12] bah - we are stuck on the hard stuff - active/active rabbitmq and active/active mysql [16:12] jamespage: nope, I'll start this week to work on the charms (cause got distracted last week with toher stuff) right now in training [16:13] I started to look at charming percona/cluster using upstream repositories [16:13] it feel fragile still [16:13] anyway.. [16:13] arosales, i did a far amount of bp updates. if nothing else, vuds did give a reasonable time slot for that. [16:13] smoser, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams [16:13] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init [16:14] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa got a bit of a replan post vUDS [16:14] so s'ok [16:15] jamespage, simplestreams is in correct state. [16:15] zul, please can you update and re-plan https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana against remaining milestones [16:15] cloud-init i'm updating now. [16:15] ack [16:15] jamespage: will do so this afternoon [16:15] I don't think mongodb will make main this cycle - https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb [16:16] but hopefully we can figure out something with upstream for 14.04 [16:16] arrgh [16:16] that said we are now ship-shape on OpenSSL + AGPL linking exceptions [16:16] * jamespage thanks MongoDB for doing that [16:16] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms [16:17] adam_g, I think that needs an update post UDS session please; with milestones etc... [16:17] jamespage, ack [16:17] https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive [16:17] replanned and OK [16:18] zul, smb, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor has some immediate work items that need attention [16:18] specifcally FFe's for openstack stuff [16:18] FFE filed for xen [16:18] https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1218817 [16:18] Launchpad bug 1218817 in xen (Ubuntu) "[FFE] Update to Xen-4.3 in Saucy" [High,New] [16:18] zul, please update the blueprint then [16:18] FFE filed for openstack-lxc coming today [16:18] thanks [16:19] jamespage, thought I did update the bp [16:19] smb; so you did - my mistake [16:19] arosales, want to touch on the juju blueprints? [16:19] I'm not so close to those... [16:20] nope -OK [16:20] looks like not to many issues anyway [16:20] hallyn_, back to you [16:21] jamespage, I think we are good for this week [16:21] jamespage: thanks, moving on, [16:21] plus looks like I lost my chance :-) [16:21] arosales, lol [16:21] blink and you miss it [16:21] :) [16:21] * arosales too slow [16:21] #topic Ubuntu Server Team Events === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Server Team Events [16:21] plumber's is comgin up with several mini-confs (lxc, virt, security...) [16:22] * smb will be there [16:22] any more coming up? [16:22] charm school this friday [16:22] https://juju.ubuntu.com/events/ [16:22] How to use Charm Helpers [16:22] 1700 UTC (1pm EDT) 6 September [16:22] #juju on Freenode [16:22] and maybe what charm helpers are? :) /me should consider listening in [16:22] ok, moving on, [16:22] #topic Weekly Updates & Questions for the QA Team (plars) === meetingology changed the topic of #ubuntu-meeting to: Weekly Updates & Questions for the QA Team (plars) [16:23] yes if you don't know what charms are please join us and find out :-) [16:23] charm helpers help you write charms in less code +10000 [16:23] lol [16:23] plars: psivaa: \o [16:23] we can come back if need be, [16:23] #topic Weekly Updates & Questions for the Kernel Team (smb) === meetingology changed the topic of #ubuntu-meeting to: Weekly Updates & Questions for the Kernel Team (smb) [16:24] hello [16:24] too late ? :) [16:24] no updaes from us btw :) [16:24] psivaa: ok thanks :) [16:24] So just for that kvm bug mentioned before... [16:24] I cannot say more than that is seems to be some regression with 3.11 (maybe 3.10 already). I just managed to write a lengthy email to the kvm mailing list this morning as I am not sure how to drill down further. Basing on 64bit Precise and 64bit Saucy on level 1 for a level 2 should be mostly working but adding more saucy to deeper nesting is likely prone to fail. [16:24] smb: so 3.9-under-3.9 wouldn't have had this problem? [16:25] (I thought jodh was having trouble iwth earlier kernels, but maybe i mis-remember) [16:25] hallyn_, I think only 32bit user-space in level 1 seems to have been broken a bit longer [16:25] oh. right. we have multiple bugs? [16:25] Likely === kyleN-afk is now known as kyleN [16:25] lovely [16:26] ok so, we're waiting on community to jump in. this can be rperoduced with fedora or some other distros i assume? [16:26] I hope but I have not tried [16:26] ok. (mahbe i'll try later this week) any other questions for smb [16:27] if not, we can move on to... [16:27] #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) === meetingology changed the topic of #ubuntu-meeting to: Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) [16:27] Nothing new from me. Any questions? [16:27] (waiting 30 secs for responses) [16:28] great, let's move on to [16:28] #topic Open Discussion === meetingology changed the topic of #ubuntu-meeting to: Open Discussion [16:28] anything? [16:28] In case anyone is unaware, http://status.qa.ubuntu.com/reports/ubuntu-server/triage-report.html needs some love. [16:29] oh yeah - can we do any automated cleanup of the likewise-open bugs? [16:29] jamespage: ^ that looks like yoru ba [16:29] bag [16:30] golly [16:30] yes [16:30] I'll take a look [16:30] but if the rest of the team can have a dirge on bug triage this week/next that would be helpful [16:30] * jamespage holds up his hand for being a little neglegent on triage duty recently [16:30] jamespage: ok, thanks :) i looked at some by hand, and actually they looked like not all the same causes - but it's hard to tell bc i don't know the package that well [16:31] i'd also like to consider taking all < 1000000 numbered likewise-open bugs and marking them all dups or something [16:31] but ok, let's say [16:31] [ACTION] everyone spend extra time triaging bugs this week [16:31] ACTION: everyone spend extra time triaging bugs this week [16:32] so we can move on to [16:32] #topic Announce next meeting date, time and chair === meetingology changed the topic of #ubuntu-meeting to: Announce next meeting date, time and chair [16:32] Should be Tuesday Sep 10 at 16:00 UTC, with the magnificent roaksoax chairing [16:32] thanks everyone \o [16:32] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [16:32] Meeting ended Tue Sep 3 16:33:04 2013 UTC. [16:32] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-16.02.moin.txt [16:32] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-16.02.html [16:32] thanks hallyn_ [17:00] #startmeeting [17:00] ## [17:00] ## This is the Ubuntu Kernel Team weekly status meeting. [17:00] ## [17:00] Meeting started Tue Sep 3 17:00:36 2013 UTC. The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:00] 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] [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting [17:00] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy [17:00] # Meeting Etiquette [17:00] # [17:00] # NOTE: '..' indicates that you are finished with your input. [17:00] # 'o/' indicates you have something to add (please wait until you are recognized) [17:00] Roll Call for Ubuntu Kernel Weekly Status Meeting [17:00] o/ [17:00] o/ [17:00] o/ [17:00] o/ [17:00] o/ [17:00] \o [17:00] o/ [17:01] o/ [17:01] o/ [17:01] [TOPIC] ARM Status (ppisati) === meetingology changed the topic of #ubuntu-meeting to: ARM Status (ppisati) [17:01] Latest bits for Calxeda Midway and LPAE support were pulled in S/master-next. [17:01] Work continues on making the S/master generic kernel use a concatenated [17:01] DTB: S/master-next tip has all the necessary config changes, while flash-kernel [17:01] still needs some work. [17:01] .. [17:01] [TOPIC] Release Metrics and Incoming Bugs (jsalisbury) === meetingology changed the topic of #ubuntu-meeting to: Release Metrics and Incoming Bugs (jsalisbury) [17:01]