[05:47] <pitti> arges: thanks
[07:12] <caribou> pitti: yes ?
[07:14] <pitti> caribou: I meant I had a question for you in bug 1532789
[08:15] <cking> hi there, stress-ng 0.6.04-1 has been stuck in autopkgtest testing for ppc64el for ~4+ days in  the "Test in progress" state (looking at the update_excuses page). I think it needs some kicking
[09:37] <jamespage> pitti, I think its important that we maintain interim Ubuntu release until the end of their life - one reason being that they are actually the primary source for Ubuntu Cloud Archive pockets, so if we stop maintaining Ubuntu two months prior to eol, then I have to start maintain the same packages directly in the UCA for 2 months extra :-)
[09:38] <jamespage> pitti, crmsh is a bit of exception to that rule as its not in the UCA, however ovs and ceph both are...
[09:38] <jamespage> pitti, for UCA updates, we push through the associated ubuntu release first (on the assumption its still supported)
[09:38] <jamespage> so for OpenStack Liberty UCA, Wily is still the point for entry for updates...
[09:39] <pitti> jamespage: wow, we have production stuff running on wily?
[09:39] <jamespage> pitti, that's not quite what I said
[09:39] <jamespage> pitti, we have production stuff running on trusty based on the packages that are in wily
[09:40] <jamespage> pitti, UCA is just one huge backport
[09:40] <jamespage> :-)
[09:41] <pitti> jamespage: ok, fair enough; I just wanted to ask if all that effort was actually useful, and it does seem to be a major risk for users on actual wily
[09:41] <jamespage> pitti, well for crmsh wily users are completely broken atm
[09:41] <pitti> jamespage: right, so for the crmsh case: who will actually care
[09:42] <jamespage> pitti, I was all up for the 'no one is going to actually use wily for production' but then a load of people commented on that bug...
[09:42] <pitti> jamespage: i. e. who will start using wily for crmsh now that xenial is out
[09:42] <jamespage> thats true now, but was not the case two months ago when I did the updates, testing and upload...
[09:46] <jamespage> pitti, tbh i think people where testing on wily in preparation for xenial
[09:47] <pitti> yeah, that seems plausible
[09:47] <jamespage> pitti, from my perspective, most of the work is already done in terms of time, so I'd rather see it through...
[09:47] <pitti> jamespage: so you want ceph, curtin, maas, openvswitch
[09:47] <jamespage> and be happy stating that we did support wily for 9 months
[09:47] <jamespage> pitti, can't comment on maas and curtin, but yes please to ceph and openvswitch
[09:47] <pitti> jamespage: the verification work of this is going to be substantial too, I suppose
[09:48] <pitti> jamespage: ok, and I guess we bury  crmsh?
[09:48] <jamespage> pitti, for crmsh? no the testing is automated - we know its broken (wily-liberty is currently disabled...)
[09:48] <jamespage> infact the testing is automated for ceph and ovs as well
[09:48] <pitti> jamespage: I mean for ceph, curtin, etc.
[09:48] <jamespage> curtin/maas - defer to server team on that front...
[09:48] <pitti> jamespage: we have automated tests that check that an upgrade from a current wily deployment still works?
[09:49] <pitti> as that's what actually matters
[09:49] <pitti> we know that the new versions by themselves are fine (presumably)
[09:49] <pitti> but we are throwing that at existing users of the wily version
[09:49] <jamespage> pitti, yes
[09:49] <jamespage> deploy/test/upgrade/test
[09:49] <jamespage> basically
[09:51] <jamespage> pitti, I stand corrected - that's not fully automated, but is a cycle we go through for SRU's
[09:51] <jamespage> but its still not resource intensive
[11:27] <arges> pitti: i'm trying to understand your comment on the wily SRU review queue. isn't wily supported until july?
[11:28] <pitti> arges: it is, yes
[11:28] <pitti> arges: and we shuold certainly continue to supply major bug fixes
[11:28] <pitti> arges: but I wonder if "update a server package to a major new release" makes sense at this point
[11:28] <pitti> the testing and risk by far outweigh the benefit IMHO
[11:29] <pitti> arges: that said, see backscroll from jamespage a few lines up
[11:29] <arges> pitti: fwiw some of the server packages go into wily then into cloud archive
[11:29] <pitti> yes, he pointed that out
[11:29] <pitti> so accepting these is fine
[11:29] <pitti> arges: but I think we should bury crmsh
[11:29] <arges> oh ok : ) yea i need to increase scrollback on weechat
[11:30] <arges> yea that seems like a bit jump anyway
[13:48] <Odd_Bloke> infinity: I see you've commented again on https://code.launchpad.net/~daniel-thewatkins/livecd-rootfs/enable-backports/+merge/295059; have you had a chance to re-review it fully?
[13:49] <Odd_Bloke> infinity: Oh, I see you're not working; don't worry about it!
[13:49] <infinity> Odd_Bloke: Nah, I'm still off work until tomorrow, that was just a side comment to ogra's comment.
[13:49] <infinity> Odd_Bloke: I'll get you all reviewed and merged tomorrow (or later today if this whole laying around on drugs thing threatens my sanity).
[13:49] <Odd_Bloke> infinity: Cool, thanks!
[13:50] <Odd_Bloke> infinity: Enjoy your stupor!
[13:50] <infinity> Odd_Bloke: Once this is tested and proven, is the intent to backport to xenial for 16.04.1?
[13:50] <infinity> (and maybe trusty too, though meh...)
[13:50] <ogra_> lol
[13:50] <Odd_Bloke> infinity: Yeah, definitely for xenial.
[13:50] <ogra_> 2011 ?
[13:50] <ogra_> woah
[13:51] <infinity> ogra_: Yeah, it's okay, I was as surprised as you.  Old people don't deal well with change.
[13:51] <ogra_> lol, yeah
[13:52] <infinity> Odd_Bloke: Kay.  Let's make sure that ball gets rolling as soon as this is landed in yakkety and a few builds appear to produce sane results.
[13:53] <infinity> Odd_Bloke: For now, I'm high on Oxy and going to movie myself to sleep.
[14:03] <ogra_> "oxi brings movies to your sleep" :)