[13:01]  * barry waves
[13:01] <lool> hey
[13:01] <lool> stgraber, ondra, ogra_: heyo
[13:01] <ogra_> moo
[13:02] <lool> barry: should we start with download service?
[13:02] <barry> lool: sure
[13:02] <barry> so, i uploaded a new version last night with dbus support
[13:03] <barry> stgraber: pointed to a problem with config file updates: https://bugs.launchpad.net/ubuntu-system-image/+bug/1204090
[13:03] <barry> so i'll be getting an 0.8 out this morning
[13:03] <barry> had a chat with seb yesterday.  his team was going to start work on the update ui.  i'll circle round to him today, though i am on patch pilot for at least half the day
[13:04] <lool> barry: so even after deleting client.ini today, I'll have to repeat every day until this is solved?
[13:04] <barry> we sketched out a very basic interaction pattern, so i think the minimal ui will be doable
[13:04] <ondra> lool: hey
[13:04] <barry> lool: yeah, but hopefully "every day" will be just "today"
[13:05] <barry> 0.8 will have only this fix and then you won't have to edit client.ini to set the device model any more
[13:05] <barry> anyway, i think that's about it for the client
[13:05] <lool> barry: so when do you think you would have a simple UI for an update?  (even if partial)
[13:05] <barry> d/l service. i have to circle back to mandel to see where/when/if that is landing
[13:06] <lool> barry: download service should be all landed now
[13:06] <barry> lool: ah, good.
[13:06] <barry> lool: i'm still aiming for tomorrow
[13:06] <barry> (on the ui
[13:06] <barry> )
[13:06] <lool> https://launchpad.net/ubuntu/+source/ubuntu-download-manager
[13:07] <lool> libubuntudownloadmanager1 and ubuntu-download-manager are in the images
[13:07] <lool> barry: ok
[13:07] <barry> excellent.  i'm still not going to integrate that until after the demo most likely
[13:07] <barry> done
[13:07] <lool> barry: yeah; we had noted the download service as an action on you last week, just wanted to close this topic
[13:07] <lool> since it's all landed now
[13:07] <barry> +1
[13:07] <lool> oh wow, we even have unity-scope-click in the image too !
[13:08] <sergiusens> lool: beuno was going to demo that afaik
[13:08] <lool> sergiusens: yeah
[13:08] <lool> so I think stgraber isn't around
[13:09] <lool> he was to land gpg in recovery
[13:09] <lool> but basically everything is landed, updater is announced for adventurous folks
[13:09] <ogra_> isnt that n since days
[13:09] <ogra_> ?
[13:09] <lool> and we had various issues at the time of launch and since the launch
[13:09] <lool> but getting resolved
[13:09] <ogra_> though we havent released images since 5 days due to the new policies
[13:10] <sergiusens> ogra_: stgraber pulls from pending to rebuild the images
[13:10] <lool> ogra_: yeah but update imgaes are generated from latest image rather than current, so it still works
[13:10] <barry> ogra_: new policies?
[13:10] <ogra_> (and i expect releases to not happen for a while until all bits ship full tests that utah can run)
[13:10] <ogra_> barry, 100% test coverage on the dashboard now
[13:10] <barry> ah
[13:10] <ogra_> lool, well, we will need a full test of the bits that got added to recovery ...
[13:10] <lool> barry: now that I read it more carefully, I don't understand how LP 1204090 is critical; is that in the case where the model detection would change over time?!?
[13:11] <ogra_> theoretically we couldnt release atm
[13:11] <ogra_> after asac's definition
[13:11] <lool> ogra_: not sure what you mean
[13:11] <lool> ogra_: you mean add new testsuites to cover the new bits?
[13:11] <ogra_> lool, we add ubuntu code to recvery that has zero tests
[13:11] <ogra_> by the new definition that isnt releasable
[13:12] <ogra_> so testing gpg and the ubuntu updater scripts would be needed
[13:12] <ogra_> and proper integration into utah
[13:12] <barry> lool: no.  if future changes are made to client.ini, they most likely won't get installed (at least easily) since conffile will see a local edit.  i think the point is to remove the need for almost everyone to edit their client.ini file.
[13:12] <lool> barry: oh ok
[13:12] <lool> barry: sorry, I get it now
[13:12] <lool> barry: I thought it was entirely generated
[13:12] <lool> but it's a conffile *and* gets updated after install, and wont get updated on upgrades anymore
[13:12] <lool> ok
[13:13] <barry> nope.  maybe i'll port gentoo's conffile update system to debian :)
[13:13] <lool> barry: there's ucf too
[13:13] <barry> yeah
[13:13] <lool> but this only concerns people who have renabled apt, right?>
[13:13] <barry> it's better to query the system for the device name anyway
[13:13] <lool> otherwise you get the new conffile overwritten by a system image update?
[13:14] <barry> i think that's right
[13:14] <lool> ogra_: so we do have tests in certain places, but not for everything
[13:14] <ogra_> lool, right
[13:14] <lool> ogra_: we also lack end-to-end integration tests
[13:14] <ogra_> and new features need to ship tests alongside
[13:14] <ogra_> yeah
[13:15] <ogra_> currently all we have are the app tests and default installability
[13:15] <ogra_> bit for the recovery changes we need tests too
[13:15] <lool> I'm not sure how practical it would be to have them run daily; I don't really see how that would reasonnably be done, but we could e.g. run update tests from the latest release or something like that
[13:15] <ogra_> and there should be a test that prevents stuff like above as well
[13:15] <ogra_> (broken configs etc)
[13:15] <sergiusens> lool: the end to end stuff we can discuss in our meeting with QA later today
[13:15] <lool> sergiusens: yeah
[13:16] <ogra_> http://reports.qa.ubuntu.com/smokeng/saucy/
[13:16] <ogra_> thats what we depend on now
[13:16] <ogra_> and the next daily will only go out if all is green
[13:16] <lool> ogra_: right; but we need a base image to smoke test an update
[13:16] <ogra_> (which i suspect might take until the weekend)
[13:17] <ogra_> lool, right
[13:17] <lool> I think we covered all actions from last week
[13:17] <asac> i feel that daily-release should always use last /current + the proposed changes
[13:17] <asac> in that way we foster a culture of delivering something that will work in one shot
[13:17] <ogra_> asac, that makes only sense if /current is actually daily
[13:17] <asac> rather than saying you can have multiple shots to get things right (e.g. we have an option to easily see results against /rpoposed)
[13:17] <asac> ogra_: sure. it only makes sense if we go strict
[13:18] <lool> so I guess the only remaining open topics are: a) barry adding UI (high) a') barry fixing LP 1204090 b) barry switching to download service (low) c) sergiusens / ogra_ / lool discussing integration tests
[13:18] <barry> lool: seems reasonable
[13:18] <asac> on /etc ... I think it makes sense to put a zero /etc in any touch image policy
[13:18] <ogra_> lool, sounds fine
[13:18] <asac> because its a half broken concept in the new world of system image updates
[13:18] <ogra_> zero /etc ?
[13:18] <ogra_> can you elaborate ?
[13:18] <asac> at best defaults are never shipped in /etc/ anyway, and we can provide other locations to change defaults through .DOT files
[13:19] <lool> asac: it's more of a template
[13:19] <asac> lool: those should go to /usr/share/docs :)
[13:19] <barry> asac: how does that work with convergence?
[13:19] <asac> right now in the linux world /etc is not cleanly designed
[13:19] <ogra_> barry, we'll find out in the 14.04 cycle :)
[13:19] <asac> its used as one place for a) defaults (that should usually go into the app) and b) admininstrative/system wide changes
[13:20] <barry> ogra_: :)
[13:20] <asac> i think we hsould go clean about those two approaches in touch :)
[13:20] <asac> thats all i am saying (now i am out again)
[13:20] <lool> asac: I don't see a big gain in pushing defaults out of /etc
[13:20] <lool> this is make-work
[13:21] <lool> (like merging /usr/bin and /bin or renaming /etc to /config or something)
[13:21] <lool> anyway
[13:21] <asac> its not consisten behaviour
[13:21]  * ogra_ thought /etc is readonly anyway 
[13:21] <barry> well, at least let's say an irc comment leaves it a bit underspecified :)
[13:21] <asac> if apt is there
[13:21] <lool> seems we're getting a bit out of the topic
[13:21] <ogra_> variable data needs to go into /data
[13:21] <asac> ogra_: not if apt is back i am sure
[13:21] <ogra_> asac, ah, no, then not indeed
[13:21] <lool> ogra_: exactly; except in convergence, or if you swithc to developer mode
[13:22] <ogra_> lool, i dont see why convergence would have to differ :)
[13:22] <ogra_> but thats 14,04 stuff
[13:22] <ogra_> not for now
[13:22] <lool> ogra_: because of the installer user bsae
[13:22] <lool> as in, today my /etc is r/w on my laptop
[13:22] <sergiusens> ogra_: if /etc is read only, where does network mananger setup it's configs?
[13:23] <lool> sergiusens: /dev/mmcblk0p9 on /var/lib/NetworkManager type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
[13:23] <ogra_> sergiusens, in a tmpfs overlay ? no idea
[13:23] <lool> sergiusens: bind mounts to writable space
[13:23]  * ogra_ needs to look into the setup this week 
[13:23]  * sergiusens needs to check
[13:23] <ogra_> i had planned to do an install this week
[13:23] <lool> sergiusens: sorry, I meant: /dev/mmcblk0p9 on /etc/NetworkManager/system-connections type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
[13:23] <ogra_> yeah
[13:23] <ogra_> thats /data
[13:23] <sergiusens> lool: and I thought you changed the location :-)
[13:24] <lool> the other is for more ephemeral stuff
[13:24] <lool> like dhcp leases and stuff
[13:24] <ogra_> they go into /run anyway, no ?
[13:24] <lool> sergiusens: so basically anything which used to write to /var or /etc needs to be diverted to /data
[13:24] <ogra_> yeah
[13:24] <asac> yeah :)
[13:25] <lool> ogra_: not that ephemeral
[13:25] <asac> and everything that is in /etc should rewally go to doc (template) or /usr/share/ (default settings)
[13:25] <lool> ogra_: you could remove it, but it's best to keep across reboots
[13:25] <asac> :()
[13:25] <lool> e.g. which ssids you've seen and such
[13:25] <ogra_> yeah
[13:25] <ogra_> asac, whats the benefit ?
[13:25]  * ogra_ doesnt see it 
[13:25] <lool> asac: I don't think we need to spend engineering cycles moving stuff around in gazillions of packages
[13:26] <ogra_> if /etc is readonly anyway, why would you want to have apps read from a non std place
[13:26] <ogra_> yeah, lool expressed that better
[13:26] <ogra_> seems like a waste
[13:26] <lool> it's kind of funny to have this argument in this direction with asac
[13:26] <asac> well, i will cover this topic elsewhere... short term its not on topic
[13:26] <ogra_> heh
[13:27] <lool> asac: you're supposed to be more pragmatic than me!  and I ought to advocate beauty of the file hierarchy  :-)
[13:27] <asac> i am pragmatic
[13:27] <lool> alright, almost out of time
[13:27]  * ogra_ sees no beauty in moving configs from /etc to /doc :)
[13:27] <lool> barry, ondra, ogra_, sergiusens: Anything else we want to cover?
[13:27]  * barry is good
[13:27] <lool> also, do we want to keep this meeting?
[13:27] <ogra_> lool, do we know who will write tests ?
[13:27] <lool> perhaps until it's used by everyone?
[13:27] <ogra_> (thats why i brought it up_
[13:28] <ogra_> i know stgraber will not be around (vacations, etc)
[13:28] <barry> lool: i think we're far enough along that it most likely won't be necessary for much longer
[13:28] <ogra_> and we need to switch at some point
[13:28] <ondra> lool: not much from me, I haven't done much, only recent activity was to help stgraber to resolve gpg problem, but that was 1 tas
[13:28] <ogra_> but we cant without having tests in place
[13:28] <lool> ogra_: I would think stgraber would write upgrade tests when he's back?
[13:29] <ogra_> dunno, i think i remember something about three weeks
[13:29] <lool> barry: I'm thinking we should cancel next week then have one more meeting to plan enabling for everyone
[13:29] <ogra_> with parts of that being on/off and parts of that being gone completely
[13:29] <lool> barry: or would you be interested in writing the upgrades tests in the next weeks?  since stgraber is on leave, you might be a good candidate since you know the upgrade logic inside out  :-)
[13:29] <lool> barry: would you want to join the call we have with QA folks later?
[13:30] <lool> ogra_: yeah; release sprint, debconf and other leaves
[13:30] <barry> lool: when's the call?
[13:30] <ogra_> lool, right
[13:30] <lool> barry: 4pm UTC
[13:30] <lool> barry: adding you
[13:30] <lool> barry: feel free either way
[13:31] <lool> alright, closing this meeting them; have a good day everyone!
[13:31] <barry> lool: sure, np
[13:31] <lool> *then
[13:31] <barry> cheers!
[13:31] <lool> bye all
[13:31] <ondra> bye
[13:31] <sergiusens> see you on the channel to the left (or right) (irssi)
[13:31] <ogra_> bye
[13:31] <ogra_> sergiusens, pfft ... below
[13:31] <ogra_> (xchat)
[13:32] <sergiusens> lol
[15:32] <Laney> o/
[15:34] <Laney> oops
[16:00] <l304> o
[16:00] <hallyn> o/
[16:00] <arosales> hello
[16:00] <jamespage> o/
[16:01] <smb> \o
[16:01] <adam_g> o/
[16:01] <jamespage> lets strt
[16:02] <jamespage> #startmeeting
[16:02] <meetingology> Meeting started Tue Jul 23 16:02:00 2013 UTC.  The chair is jamespage. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <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
[16:02] <jamespage> #topic review previous actions
[16:02] <jamespage> rbasak to land delta report to lp:ubuntu-reports, Daviey to deploy
[16:02] <jamespage> rbasak, Daviey- hows that going?
[16:03] <jamespage> zul:
[16:03] <jamespage> zul has willfully volunteered to review and document what is blocking server related saucy-proposed migration excuses, with joy.
[16:03] <jamespage> I think thats all sorted now right
[16:03] <jamespage> ?
[16:03] <zul> bah
[16:03] <zul> almost apache2 again i think
[16:03] <zul> rbasak:  ^^^
[16:04] <jamespage> anyone actually here?
[16:04] <jamespage> lol
[16:04] <jamespage> anyway
[16:04] <jamespage> #action rbasak to land delta report to lp:ubuntu-reports, Daviey to deploy
[16:04] <meetingology> ACTION: rbasak to land delta report to lp:ubuntu-reports, Daviey to deploy
[16:04] <hallyn> my bot is...
[16:04] <jamespage> carried forward in their absence
[16:04] <jamespage> #topic Saucy Development
[16:05] <jamespage> #link https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[16:05] <jamespage> Debian Import Freeze is on the 25th July - manual syncs after that point will be required
[16:05] <jamespage> alpha2 same week - we will be opting out again
[16:06] <jamespage> also worth noting that 12.04.3 is just under a month away
[16:06] <jamespage> the QA team now have some dkms auto-testing setup
[16:06] <jamespage> openvswitch and iscsitarget are going to need some attention in the next two weeks.
[16:06] <hallyn> ?
[16:06] <jamespage> (as are lots more I guess)
[16:07] <jamespage> hallyn, hardware enablement kernels
[16:07] <rbasak> Oops, sorry. ubuntu-reports is almost ready for an MP. apache2 is done. I'm preparing a merge with an upgrade path bug and SSL passphrase prompting fixed.
[16:07] <jamespage> 12.04.3 will get rarings 3.8 kernel
[16:07] <jamespage> rbasak, marvellous!
[16:07] <hallyn> jamespage: gotcha
[16:07] <jamespage> next
[16:07] <jamespage> #subtopic Release Bugs
[16:07] <jamespage> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:08] <jamespage> I still need to look at asm4 transitions
[16:08] <jamespage> and quantum service respawns
[16:09]  * jamespage berates himself again
[16:09] <yolanda> lua5.2 is pending from review
[16:09] <jamespage> ack
[16:09] <hallyn> there's a yucky memleak in libvirt i need to look into
[16:09] <yolanda> rrdtool and rubyluabridge
[16:09] <rbasak> bug 1202653 should be targetted for Saucy. It's in hand though - I just want to fix SSL certificate prompting at the same time, write a dep8 test for that, and in any case proposed migration will be blocked as it's seeded in alpha-2 opt-in flavours.
[16:09] <jamespage> zul: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1199791
[16:09] <jamespage> rbasak, done
[16:09] <zul> in progrress
[16:09] <rbasak> thanks
[16:09] <jamespage> zul, great - thanks
[16:10] <jamespage> looks like adam_g's cheetah fixup is almost done
[16:11] <adam_g> yup, should make its way out today
[16:12] <jamespage> rbasak, whats the latest on bug 1031680?
[16:13] <jamespage> and that covers release bugs....
[16:13] <jamespage> #subtopic Blueprints
[16:13] <rbasak> No progress.
[16:13] <jamespage> #link http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html
[16:13] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb
[16:13] <jamespage> use of libv8 in the mongodb shell is causing some security concerns re supportability
[16:13] <jamespage> which is understandable
[16:14] <jamespage> looking at a shell disabled variant of the package - but I suspect thats worse than useless
[16:14] <jamespage> so we might be inthe position where mongodb is not suitable for main inclusion
[16:14] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery
[16:14] <jamespage> juju2 release going much smoother now
[16:14] <jamespage> two in the last week
[16:15] <jamespage> (one for OSCON)
[16:15] <jamespage> local provider has also landed if no-one noticed - works well (thanks thumper)
[16:15] <jamespage> roaksoax, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2
[16:15] <jamespage> whats happening with HA stack for saucy? I know we have had a few conversations?
[16:16] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph reappears
[16:16] <jamespage> utlemming, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-webscale
[16:16] <jamespage> utlemming, are you likely to have capacity to work on this blueprint this release? its already a carry over from raring
[16:17] <jamespage> zul: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa
[16:17] <jamespage> needs some updates
[16:18] <zul> jamespage:  ack
[16:18] <jamespage> quite a few activities need to be worked on still this cycle there - might be work allocating out and postponing anything we know we won't get to this cycle
[16:18] <jamespage> adam_g, ^^
[16:19] <hallyn> s/work/worth/ ?
[16:19] <adam_g> agree
[16:19] <jamespage> hallyn, yes
[16:19] <roaksoax> jamespage: sorry i'm supper lagged
[16:19] <hallyn> k
[16:19] <jamespage> roaksoax, ack
[16:19] <jamespage> roaksoax, wanna update now?
[16:19]  * jamespage gives roaksoax a few to respond
[16:20] <jamespage> zul: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana
[16:20] <jamespage> lots of things actually done there I think
[16:20] <jamespage> good point to catchup now that havana2 is landing everywhere
[16:20] <zul> ill upate it today
[16:21] <jamespage> arosales, quite a few juju related ones with minimal progress - do you want to go through those now?
[16:21] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms
[16:21] <jamespage> adam_g, roaksoax and I have been working on the python redux of the openstack charms
[16:22] <jamespage> looking quite good now - hopefully we should have a full set of initial versions this week
[16:22] <adam_g> im hoping to have all of the bash -> python rewrites ready for testing this week
[16:22] <jamespage> \o/
[16:23] <jamespage> OK - anyone got any other BP related stuff they wanted to raise/query?
[16:23] <jamespage> ....
[16:23] <jamespage> ...
[16:23] <jamespage> ..
[16:23] <yolanda> mine of server banners is stuck, working on other issues
[16:23] <jamespage> .
[16:24] <jamespage> yolanda, is that just pending sponsorship or are you getting blocked?
[16:24] <arosales> jamespage, sorry I was in another window
[16:24] <yolanda> jamespage, i stopped working on that for a while, working on syncs and merges, and now in charms
[16:24] <jamespage> yolanda, OK
[16:25] <jamespage> arosales, juju blueprints?
[16:25] <yolanda> i got some of them uploaded, bind9 is pending on review
[16:25] <arosales> jamespage, a couple of the owners are at OSCON so I can take an action to review juju related ones this week
[16:25] <arosales> #action arosales to review Juju blueprints
[16:25] <meetingology> ACTION: arosales to review Juju blueprints
[16:25] <jamespage> #action arosales to review juju related blueprints with owners after OSCON
[16:25] <meetingology> ACTION: arosales to review juju related blueprints with owners after OSCON
[16:25] <jamespage> ooops
[16:25] <jamespage> oh well - we will remember twice now!
[16:25] <jamespage> lets move on
[16:25] <jamespage> #topic Ubuntu Server Team Events
[16:26] <jamespage> something called OSCON I think
[16:26] <jamespage> anyone going?
[16:26] <hallyn> i'm guessing if they are, they are there already
[16:26] <jamespage> lol
[16:26] <jamespage> yes
[16:26] <jamespage> any other events folk want to raise now?
[16:26] <arosales> m_3 and jcastro @ OSCON
[16:26] <arosales> giveing a Charm School talk as we chat here
[16:27] <jamespage> excellent - hope its packed....
[16:27] <jamespage> #topic Weekly Updates & Questions for the QA Team (plars)
[16:27] <jamespage> plars, floor is yours
[16:27] <plars> hi, a couple of bugs are affecting server testing at the moment
[16:27] <plars> both on the virtual host part
[16:27] <plars> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203694 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203211
[16:28] <smb> should be fixed by -5 in proposed
[16:28] <plars> bot seem to be well on their way though :)
[16:28] <plars> ack
[16:28] <rbasak> AIUI the release team are working on landing -5.
[16:28] <jamespage> excellent
[16:28] <plars> sounds good
[16:28] <plars> that's it from me
[16:28] <jamespage> thanks plars
[16:28] <jamespage> anyone got anything else qa related while we are here? matsubara maybe?
[16:29] <jamespage> ....
[16:29] <jamespage> ...
[16:29] <jamespage> ..
[16:29] <jamespage> .
[16:29] <matsubara> not really
[16:29] <jamespage> ack
[16:29] <jamespage> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:29] <smb> There seem also to be some problem with qemu and vmvga crashing the host which apw is working on.
[16:30] <smb> The bug number slipped my brain though
[16:30] <smb> ah
[16:30] <smb> bug 1204005
[16:31] <smb> Apart from that I cannot think of anything hot right now (exccept the weather)
[16:31] <smb> Are there questions?
[16:31] <jamespage> smb, thanks
[16:31] <jamespage> sound like a no for questions...
[16:31] <jamespage> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:32] <rbasak> Nothing new to report. Any questions for me?
[16:32] <jamespage> not from me
[16:32] <jamespage> anyone else?
[16:33] <jamespage> OK
[16:33] <jamespage> #topic Open Discussion
[16:33] <jamespage> anything anyone wants to raise?
[16:33] <arosales> UDS fastly approaching
[16:33] <jamespage> discuss or otherwise argue about?
[16:33] <arosales> http://uds.ubuntu.com/
[16:33] <zul> yeah i raised this
[16:33] <roaksoax> jamespage: basically, I'm currently updating the cluster stack, which means the removal of 'redhat-cluster' from the archives. All cluster will be based on pacemaker+corosync2.0, gfs2 + dlm (a new package that needs to be uploaded)
[16:33] <roaksoax> for distributed storage
[16:33] <roaksoax> /filesystem
[16:33] <jamespage> roaksoax, man - that is some lag - thanks for the update
[16:34] <zul> https://bugs.launchpad.net/ubuntu/+source/quantum/+bug/1203766
[16:34] <roaksoax> and all packages that used to depend on redhat-cluster related dependencies need to be update
[16:34] <arosales> ah sorry for the dup zul
[16:34] <jamespage> good point about UDS _ only a month away
[16:34] <jamespage> good point to recheck on progress for saucy so far
[16:34] <zul> that should be interesting
[16:35] <jamespage> just to be clear - quantum is now called neutron if anyone missed that
[16:35] <jamespage> its not another new core project in openstack
[16:35] <jamespage> :-)
[16:35] <jamespage> anyway
[16:35] <jamespage> #topic Announce next meeting date and time
[16:36] <jamespage> Tuesday 30th July - 1600 GMT
[16:36] <jamespage> see you then
[16:36] <jamespage> #endmeeting
[16:36] <meetingology> Meeting ended Tue Jul 23 16:36:25 2013 UTC.
[16:36] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-23-16.02.moin.txt
[16:36] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-23-16.02.html
[16:36] <jamespage> thanks folks!
[16:51] <arosales> jamespage, thanks for chairing
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Jul 23 17:00:37 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/Meeting
[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] <henrix> o/
[17:00] <smb> \o
[17:00] <kamal> o/
[17:01] <rtg> o/
[17:01] <cking> \o
[17:01] <ogasawara> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing new to report
[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:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:01] <ogasawara> || apw       || foundations-1305-arm64-bringup || 1 work item  ||
[17:01] <ogasawara> || ppisati   || foundations-1305-kernel        || 1 work item  ||
[17:01] <ogasawara> || smb       || servercloud-s-virtstack        || 3 work items ||
[17:01] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:02] <ogasawara> We have recently uploaded a new 3.10.0-5.14 Saucy kernel to the archive.
[17:02] <ogasawara> This includes the v3.10.2 upstream stable patch set, as well as a fix
[17:02] <ogasawara> for a regression which was causing graphics failures on boot.  We have
[17:02] <ogasawara> also rebased our unstable branch to begin tracking v3.11-rc2.
[17:02] <ogasawara> I also want to again point out that the 12.04.3 point release is
[17:02] <ogasawara> approaching on Thurs Aug 22.  Any kernel patches needing to land in the
[17:02] <ogasawara> 12.04.3 point release need to be applied to our Raring kernel tree on
[17:02] <ogasawara> or before Mon July 29 in order to hit the SRU cadence before the point
[17:02] <ogasawara> release.  Please get any patches submitted to the mailing list for
[17:02] <ogasawara> proper review as soon as possible.
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara> Thurs July 25 - Alpha 2 (opt in, 2 days)
[17:02] <ogasawara> Thurs Aug 22 - 12.04.3 (~4 weeks)
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's (bjf)
[17:02] <bjf> The current CVE status can be reviewed at the following link:
[17:02] <bjf>   * http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:03] <bjf> Status for the main kernels, until today (July 23):
[17:03] <bjf>   *   Lucid - Regression testing
[17:03] <bjf>   * Precise - Regression testing
[17:03] <bjf>   * Quantal - Regression testing
[17:03] <bjf>   * Raring  - Regression testing
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:03] <kamal> o/
[17:03] <jsalisbury> kamal, go
[17:03] <kamal> folks playing with 3.11-rc2 should be aware that acpi backlight is borked for many systems...  a revert of the offending commits is planned in advance of 3.11-rc3.
[17:03] <kamal> ..
[17:04] <jsalisbury> kamal, thanks for the heads up.
[17:04] <jsalisbury> ..
[17:04] <jsalisbury> The next two meetings will be canceled due to the kernel team sprint.  The next meeting will be August 13th, 2013.
[17:05] <jsalisbury> ..
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Jul 23 17:05:32 2013 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-23-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-23-17.00.html
[17:05] <kamal> thanks jsalisbury