[00:49] <thumper> wallyworld_: morning, got time to catch up with a hangout?
[00:49] <thumper> wallyworld_: it seems we have some critical work to do
[00:49] <wallyworld_> ok, can i have a few minutes, just finishing something
[00:50] <thumper> ack
[00:57] <thumper> axw: morning
[00:57] <axw> thumper: heya
[00:57] <axw> have a nice weekend?
[00:58] <thumper> too short...
[00:58] <thumper> I forwarded you an email
[00:58] <thumper> and what I expected has come to pass
[00:58] <axw> mmkay
[00:58] <thumper> so we need to catch up on a hangout with wallyworld_
[00:58] <axw> sounds ominous
[00:58] <thumper> :-)
[00:58] <thumper> not as bad as it sounds
[00:58] <thumper> but more organising work
[00:59] <axw> ok
[00:59]  * wallyworld_ almost ready
[00:59] <axw> can it wait 30 mins or so?
[00:59] <thumper> considered "critical, drop what you're doing" type work
[00:59] <axw> aha
[00:59] <thumper> um... sure
[00:59] <thumper> I could catch up with wallyworld_ about some other work
[00:59] <thumper> a hangout we didn't get around to last week
[00:59] <thumper> but it would make sense for me not to repeat myself regards this other work
[01:00] <thumper> damn english
[01:00] <axw> never mind, just give me a couple of minutes
[01:01] <thumper> ok
[01:01] <axw> ok ready when you are
[01:02] <thumper> wallyworld_: ?
[01:03] <wallyworld_> okaaay
[01:04] <thumper> axw: wallyworld_, https://plus.google.com/hangouts/_/76cpj05oqcceb2k1t0qdjatpr8?hl=en
[03:10] <axw> thumper: the way I'm doing the plugin at the moment will have the machine started up with a juju-db. is that okay? IIANM, the restoration requires it to be there already
[03:11] <thumper> axw: that seems ok...
[03:12] <axw> thumper: cool. just need to find a not completely horrible way of getting StartInstance to go half way
[03:12] <thumper> :)
[04:30]  * thumper waits for jam to wake up
[04:30]  * thumper looks at the world clock
[04:30] <thumper> hmm 8:30am local
[04:59] <axw> fuck it. short term hack time
[04:59] <axw> such a mess
[05:07] <jam> thumper: /wave
[05:07] <jam> I'm not officially started, but since you poked
[05:07] <thumper> jam: when do you normally officially start?
[05:08] <jam> about now, but I have to go pick up my car from the repair shop
[05:08] <thumper> jam: ah, I'd like to have a hand-off call
[05:08] <thumper> for the critical work status
[05:09] <jam> thumper: I've got time for a handoff call
[05:09] <thumper> ok
[05:09]  * thumper kicks a hangout
[05:10] <thumper> jam: https://plus.google.com/hangouts/_/72cpik63e8i2q1m4eu10q73qh4?hl=en
[05:25] <jam> axw: wallyworld_: before you stop today, can you give updates on where you got to with the various backup plugins? In case we need to hand it off to someone
[05:25] <axw> jam: certainly
[05:25] <wallyworld_> yep, was going to :-)
[05:57] <axw> wallyworld_: do you know a James Price from when you were at Caterpillar?
[05:57] <wallyworld_> not offhand
[05:57] <wallyworld_> what section was he in?
[05:57] <axw> not sure actually
[05:58] <axw> he's my cousin, used to work there
[05:58] <wallyworld_> caterpillar has almost 100000 employees :-)
[05:58] <axw> heh :) he's in Perth, just thought you may have known him since you did some owrk over here
[06:07] <jam> wallyworld_: I'm around if you want to chat
[06:07] <wallyworld_> jam: ok, for 10 minutes then i have to go
[06:07] <jam> np
[06:48] <jam> davecheney: so why do you need the 4.9 snapshot for gccgo? I guess the default gcc for T is 4.8.? Is there just not support for golang there, or its just broken, or ?
[06:49] <davecheney> jam: 4.8 does not support the architctures we need
[06:49] <jam> davecheney: isn't that going to be true for the platform as a whole ?
[06:49] <jam> so if we want any Ubuntu on those platforms for T then we need the compiler
[06:50] <davecheney> jam: to your first question: not necessarily
[06:50] <davecheney> to your second: I have no idea
[06:50] <davecheney> arm64, no, that works with 4.82
[06:50] <davecheney> for the other platform, i have no idea
[06:51] <davecheney> but I would place a small wager that 4.8.2 as shipped my us in T will not suffice
[06:52] <jam> davecheney: anyway, my point is that if 4.8.2 isn't going to compile for the platforms we want to support for golang, isn't that going to be true if we want to support C/C++ packages on that platform? In which case, there needs to be some sort of exception that needs to be made which isn't specific to us
[06:54] <davecheney> jam: https://docs.google.com/a/canonical.com/document/d/1ip_WmLusPBRqtxZG2rjANbnaiig68hkZENKj1DEOmKg/edit
[06:56] <davecheney> jam: hopefully this explains, at least in part, why gccgo != gcc
[06:56] <jam> davecheney: yeah it does
[06:56] <jam> davecheney: I'm not sure that the compiler you build a tool with needs to be in main, are you sure on that?
[06:56] <jam> I know we have a bug where backports are a problem
[06:57] <davecheney> jam: mathias and james page both tell me this is true
[06:58] <jam> davecheney: https://wiki.ubuntu.com/UbuntuMainInclusionRequirements section 6
[06:58] <davecheney> > Could you clarify for me, if we want to use gccgo to build juju into
[06:58] <davecheney> > main, does that gccgo compiler also have to be in main ?
[06:58] <davecheney> yes. build dependencies of packages have to be in the same pocket.
[06:58] <jam> "All build and binary dependencies must be satisfyable in main"
[06:58] <davecheney> ^ from the man
[07:01] <jam> davecheney: yeah, I found it on the official "What do you need for a Main Inclusion Request" page.
[07:04] <davecheney> jam: this is quite a quandry
[08:15] <fwereade> jam, morning
[08:16] <jam> fwereade: morning. I'm in a hangout with Dimiter right now, but I know Tim really prefered the Juju process than the MaaS hackery. Partially because it works on any provider
[08:17] <fwereade> jam, and it's fully achievable... today?
[08:17] <jam> fwereade: well Juju-backup and juju-provision have been written
[08:17] <jam> whether "they all work" yet
[08:17] <jam> I'm not sure
[08:19] <jam> fwereade: but we need them tested anyway
[08:24] <jam> fwereade: I'm chatting with dimitern about having him pick up bug #1254577
[08:25] <fwereade> jam, I'm really worried that this is bad craziness and way too many moving parts, when what was asked for was "a procedure to back up and restore the bootstrap node", and we know they already have file-level backups of everything
[08:26] <jam> fwereade: but are they file-level backups that are consistent mongo snapshots?
[08:26] <jam> fwereade: hangout?
[08:26] <fwereade> jam, yeah, sgtm
[08:26] <jam> fwereade: https://plus.google.com/hangouts/_/calendar/am9obi5tZWluZWxAY2Fub25pY2FsLmNvbQ.6dasi8b7b79tgd1ij533qo0ma8
[08:28] <wallyworld_> jam: fwereade : let me know what you decide
[08:29] <jam> wallyworld_: you can join the conversation if you want
[08:29] <wallyworld_> ok
[08:34] <axw> wallyworld_: you made some changes to stop the lxc provisioner from starting unnecessarily, right?
[08:34] <wallyworld_> axw: yeah
[08:34] <wallyworld_> only starts when first lxc machine is asked for
[08:35] <wallyworld_> s/machine/container
[08:35] <axw> cool. someone on #juju just reported a problem with manual provisioning, it was barfing because lxc-ls couldn't be found
[08:36] <wallyworld_> right. so cloud init no longer apt-get installs lxc by default
[08:37] <jam> axw: so I think you need "juju-local" vs just "juju" if you are doing things like manual work
[08:38] <axw> jam: for the local provider, but not for manual
[08:38] <axw> ah
[08:38] <axw> well, until wallyworld_'s change I suppose it should have installed it, yeah
[08:38] <axw> oh well, FIXED_UPSTREAM
[08:39] <wallyworld_> axw: did i break something?
[08:39] <axw> wallyworld_: no, you fixed it
[08:39] <wallyworld_> \o/
[08:56] <rogpeppe> mornin' all
[08:59] <axw> morning rogpeppe
[08:59] <rogpeppe> axw: hiya
[08:59] <jam> morning rogpeppe, currently on a hangout talking about how we're going to deal with the NEC stuff
[09:00] <jam> https://plus.google.com/hangouts/_/calendar/am9obi5tZWluZWxAY2Fub25pY2FsLmNvbQ.6dasi8b7b79tgd1ij533qo0ma8 if you want to join
[09:00] <rogpeppe> jam: joining
[09:59] <mramm> morning all.
[10:00] <jam> morning mramm
[10:00] <jam> morning mgz
[10:00] <axw> morning
[10:00] <mgz> how are you jam?
[10:01] <jam> a bit talked out, as we've been in "we need to fix the backup process" discussion overload
[10:02] <mgz> I saw Ian's branch
[11:38] <jamespage> jam: hey - who's the best person to talk to about what juju needs in this stripped down mongodb package I'm about to hack out?
[11:39] <jam> jamespage: we're a bit on critical response today
[11:51] <wallyworld_> jam: natefinch: i've pushed the latest changes to the backup script. https://codereview.appspot.com/31960043 it still doesn't include the jenv info eg uuid. nate suggested mongo --eval but i don't know how far i'll sensibly get with that tonight. i *could* use juju get-env from the client side part of the backup script and include the resulting json output in the tarball. but if we can generate on the server side that would be better
[11:52] <natefinch>          /join #maas
[12:07] <TheMue> wallyworld_: already looking too
[12:18] <dimitern> rogpeppe, you're using 1.16 branch for the ec2 tests, right?
[12:18] <rogpeppe> dimitern: yeah
[12:18] <rogpeppe> dimitern: but the latest 1.16 branch, probably not the one that they're using
[12:18] <rogpeppe> dimitern: i don't think it matters *too* much for these tests though
[12:19] <dimitern> rogpeppe, ok, I'm pulling 1.16 now and starting
[12:19] <rogpeppe> dimitern: i've written down the set of steps to take; now i'm deploying an environment, following the steps
[12:19] <rogpeppe> dimitern: wanna join the hangout?
[12:19] <dimitern> rogpeppe, i'm about to yeah
[13:04] <mattyw_> rogpeppe, hope you had a good weekend? would you be able to spare me 10-15 mins this afternoon (probably after 4pm) to talk about the api
[13:05] <rogpeppe> mattyw_: had an excellent weekend thanks
[13:05] <rogpeppe> mattyw_: hopefully, yes
[13:05] <rogpeppe> mattyw_: ping me
[14:07] <sinzui> abentley, CI is ill I failed to fix it on Friday. I have not seen 1.17 pass in days and we need to do a release. I removed azure from testing, and that revealed the disk space. I suspect the space issue is why I saw 3 instances running for 19 hours when we expected no more than 30 minutes
[14:07] <sinzui> abentley, I did update the assemble script to download less
[14:07] <abentley> sinzui: Okay, I'll get on it.
[14:10] <sinzui> abentley, I hope to work with utlemming in a few hours to deploy the real set of tools and mirrors to streams.canonical.com. I think it is realistic to say by our mid-afternoon, we will see production and code ready for the release.
[14:18] <abentley> sinzui: tests running.
[14:18] <sinzui> with my new script?
[14:21] <sinzui> jam, hazmat, I have an agreement/plan to fix Lp's listing of releases on +downloads. I will propose a fix later this week.
[14:21] <hazmat> sinzui, cool
[14:26] <abentley> sinzui: I didn't update the script.
[14:33] <hazmat> sinzui, is manual provisioning on the automated tests?
[14:33] <sinzui> no, net yet hazmat
[14:33] <hazmat> sinzui, there was a regression on trunk for it recently.
[14:33] <sinzui> hazmat, bug that I can track?
[14:33] <hazmat> sinzui, https://bugs.launchpad.net/juju-core/+bug/1254642
[14:33] <_mup_> Bug #1254642: manual provider configures API Info with state server addresses <juju-core:Triaged by axwalk> <https://launchpad.net/bugs/1254642>
[15:05] <mgz> I'm going to be variably around for the next while, working on ug 1254579
[15:10] <mramm> hey all, can at least one of you join the new P1 conf call I am creating
[15:10] <mramm> sending out the details to everybody in email.
[15:19] <rogpeppe> mgz: ping
[15:23] <rogpeppe> rebooting
[15:23] <sinzui> rogpeppe, mgz, fwereade can one of you give an opinion about Bug #1253576? As I do see relation errors all the time, I think the reporter didn't wait long enough to see the problem reported
[15:23] <_mup_> Bug #1253576: Juju does not show relation status <add-relation> <juju-core:New> <https://launchpad.net/bugs/1253576>
[15:39] <rogpeppe> sinzui: if the hook is hung, then there is no problem, as we currently conceive things anyway
[15:39] <rogpeppe> sinzui: hooks are allowed to take as long as they like
[15:40] <sinzui> rogpeppe,  thank you. In this case then, the charm needs to verify its hooks respond properly
[15:41] <rogpeppe> sinzui: you mean that it's a charm testing issue?
[15:41] <sinzui> yes
[15:41] <sinzui> rogpeppe, I don't think this is a juju issue
[15:41] <rogpeppe> sinzui: agreed
[15:41]  * sinzui moves bug
[15:42]  * rogpeppe goes to grab a bite to eat
[15:42] <fwereade> sinzui, sorry, just commented, should have replied here, go distracted looking for another bug
[16:02] <jam> yay sinzui
[16:05] <jam> mgz: how goes?
[16:39] <mattyw> rogpeppe, would you be free in 15 minutes?
[16:39] <rogpeppe> mattyw: i could probably spare a little time, sure
[16:39] <mattyw> rogpeppe, I'll try to not take up too much of your time :)
[18:01] <mgz> rogpeppe: how goes with landing your bits?
[18:01] <rogpeppe> mgz: i might have been duplicating your work, i'm afraid
[18:01] <rogpeppe> mgz: i couldn't contact you
[18:02] <rogpeppe> mgz: so i went ahead and did the stuff to edit the config files etc
[18:02] <mgz> in a plugin command, right?
[18:02] <rogpeppe> mgz: no, just as a standalone, but it could be a plugin
[18:03] <mgz> oh, okay, so not completely the same then
[18:03] <rogpeppe> mgz: if i'd thought to do it as a plugin, i probably would have
[18:04] <mgz> I was assuming you'd be working on getting the machine listing working after putting a state server back online, so just have a lookup then ssh/sed replace/hup thing
[18:04] <rogpeppe> mgz: this is what i've got currently: http://paste.ubuntu.com/6475020/
[18:05] <rogpeppe> mgz: there's not an enormous amount more in terms of easily scripted stuff
[18:05] <mgz> okay, that's too bad
[18:06] <rogpeppe> mgz: sorry, i tried to ping you, 'cos i thought we could pair on it
[18:06] <mgz> yeah, I had to leave internet-world unfortunately
[18:06] <rogpeppe> mgz: i should get your mobile number :-)
[18:07] <mgz> the other thing I wondered if it should be part of this command, or assumed to be done already, is the updating of provider-state
[18:08] <rogpeppe> mgz: i'm not sure
[18:09] <rogpeppe> mgz: in my mind that part of things isn't quite so fixed as to how we're going to do things
[18:09] <jam> sinzui: ping
[18:10] <mgz> rogpeppe: have you got anything up for actually correcting the address of the state server in state yet?
[18:10] <rogpeppe> mgz: the addresser should do that automatically, shouldn't it
[18:11] <mgz> hm, yes, though leaving it to that I find a bit scary, because presumably everything will start up with the wrong details till the update happens... may not matter
[18:13] <rogpeppe> mgz: it seemed to work when i tried it
[18:16] <natefinch> jam, fwereade: I have garage maas all set up, not sure if there's anything else I should be doing to help out?
[18:16] <jam> natefinch: I think rogpeppe has set up some instructions, we should probably have you try them out
[18:17] <natefinch> jam: sure thing
[18:17] <rogpeppe> jam: my instructions are somewhat different to the ones that dimiter was putting together
[18:17] <rogpeppe> jam: but are less ec2-specific so maybe useful anyway
[18:18] <natefinch> jam, rogpeppe:  let's start this way - what version of juju should I be installing?
[18:18] <rogpeppe> natefinch: i used the latest 1.16
[18:18] <rogpeppe> natefinch: and a version with a patch to worker/provisioner
[18:18] <jam> rogpeppe, natefinch: certainly a 1.16 version. The question from ehw was about using 1.16.1
[18:19] <ehw> jam: think I figured it out; 1.16.0.1 shows up in the logs; not sure which jujud returns that version
[18:19] <rogpeppe> natefinch: i bootstrapped with the current 1.16... or whatever bootstrap found, anyway
[18:19] <jam> ehw: no official version. the .0.1 means it wasn't an official release
[18:19] <rogpeppe> ehw: that means you've used --upload-tools
[18:20] <jam> rogpeppe: which isn't *that* uncommon because of MaaS, people tend to do that instead of sync-tools, I think
[18:20] <rogpeppe> jam: hmm
[18:20] <mgz> jam: they really shouldn't thoough
[18:20] <jam> rogpeppe: mgz: well, I agree, but lack of egress means we exposed a way through (a jujud right here, use it)
[18:20] <mgz> at the least, it's probably an old local copy, instead of our latest 1.16 relase
[18:21] <ehw> jam, rogpeppe looks like it was deployed with ` juju bootstrap -v --upload-tools `
[18:22] <ehw> although right before that, they did `juju sync-tools`, not sure why
[18:23] <jam> ehw: did they try sync-tools but it failed because of lack of outbound network access?
[18:24] <ehw> jam: no error reported in the deployment doc; I'm going to add a comment to it and see
[18:42] <sinzui> hi jam
[18:46] <sinzui> mgz, ehw, rogpeppe: We never published a good document about collecting the tools and running sync-tools. I wrote a doc explaining how QA does it. We might use that doc as a base for official docs
[18:46] <mgz> sinzui: that sounds like a good idea
[18:48] <rogpeppe> i'm going to have to leave soon
[18:49] <rogpeppe> mgz: here's what i've got now FWIW - it does work, but feel free to discard http://paste.ubuntu.com/6475222/
[18:49] <mgz> rogpeppe: thatnks
[18:50] <sinzui> We haven't seen hp-cloud do a successful upgrade-juju since r2071. We might no care about this case since we will advise users not to upgrade envs and note that cli is incompatible with existing envs
[18:51] <rogpeppe> g'night all
[19:11] <jam> I'm off to bed myself, have a good night
[19:12] <jam> sinzui: I was just pinging you to help get an answer for e-hw and tools
[20:32] <natefinch> mgz: you around?
[20:54] <mgz> natefinch: yeah
[20:57] <natefinch> mgz: are the backup & restore steps in here ready to be tested, do you know? https://docs.google.com/a/canonical.com/document/d/17Ougx-wbiUP8xsGskESyUX_bEbZApvXHHYibMBzDD0Q/edit
[20:59] <mgz> dimiter said he tested them, yeah
[20:59] <mgz> I'm not sure it covers *everything*
[21:02] <rick_h_> sinzui: you guys have any experience with https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin or something like it?
[21:02] <sinzui> ^ abentley
[21:04] <abentley> rick_h_: No, but it might be something we'd use as we start to support per-environment testing.
[21:04] <rick_h_> abentley: k, thanks
[21:29] <fwereade> natefinch, they should be -- the part that's not addressed is getting a backup of the full machine
[21:29] <fwereade> natefinch, I'm afraid that part is down to whatever hackery matches your best guess
[21:30] <fwereade> natefinch, "tar everything up and splat it over the new system" is inelegant but I think matches the reality pretty well
[21:31] <natefinch> fwereade: cool.  I'm waiting for garage maas to download all the ubuntu images.... it is distinctly slow.  something on the order of 20 minutes so far.
[21:31] <natefinch> fwereade: my previous virtual maas never completed setup somehow.  Not sure why, and red squad is all european based, so I had no one to ask.
[21:31] <natefinch> fwereade: so I started over