[00:32] <menn0> wallyworld: review done
[00:32] <wallyworld> thanks menno, will look soon
[01:02] <axw> wallyworld: I was planning to do a small fix for cinder in goose today, but won't be able to if we can't use the version changes in juju
[01:03] <axw> wallyworld: you think it's too close to be doing that?
[01:21] <natefinch> rick_h_: thanks for all the feedback
[01:39] <thumper> wallyworld: ffs
[01:39] <thumper> wallyworld: I'm trying to get controller details for a non-responsive controller
[01:39] <thumper> but show-controller makes an api call
[01:39] <thumper> so doesn't return
[01:49] <natefinch> <sad trombone>
[01:49] <natefinch> ..aww, I miss Dave
[01:55] <menn0> axw: prometheus review done. good stuff.
[01:56] <axw> menn0: thanks!
[01:56] <axw> menn0: develop seems buggered, I got a test failure to do with SCP commands which I went nowhere near
[01:57] <menn0> axw: yep, that's failing each run in CI too
[01:57] <axw> I'll dig a bit later
[01:57] <menn0> axw: I worked in that area a few months ago so I can try and take a look too.
[01:58] <menn0> axw: i'm bringing up the issue of develop being permanently cursed in the tech board meeting
[01:58] <axw> menn0: dimiter made some changes last week to do with connecting to multiple addresses, most likely introduced then
[01:59] <menn0> axw: ah right. that seems likely.
[01:59] <axw> menn0: ok, sounds good. it's been a week since it merged :/
[02:00] <menn0> axw: actually, I'll take a look now unless you really want it
[02:00] <axw> menn0: nope, knock yourself out
[02:02]  * thumper sighs
[02:02] <thumper> menn0: got things to panic
[02:02] <thumper> not sure if this is moving in the right direction
[02:03] <menn0> thumper: this is the cloud credentials handling?
[02:03] <thumper> yeah
[02:04] <thumper> oh ffs
[02:05]  * thumper wants to slap whoever did the core/description part of cloud-credentials
[02:05] <thumper> menn0: the cloud credentials are never set on the outgoing model
[02:05] <thumper> now that I'm passing them in
[02:05] <thumper> it panics with "" not valid
[02:30] <wallyworld> thumper: show-controller does make an api call as it needs that info. list-controller doesn't. juju controllers --format yaml is what you want
[02:30] <thumper> thanks
[02:35] <natefinch> that is uh... not very intuitive
[04:11] <axw> wallyworld: just want to check I understand your email to heather. are we not updating dependencies.tsv now, because we're too close to 2.0.1?
[04:12] <axw> wallyworld: I was hoping to get https://github.com/go-goose/goose/pull/26 in and updated in juju, but can't do it without the api version changes
[04:13] <wallyworld> axw: i was refering to pull 25 which is the base work to support multi version endpoints. i didn't see the point in landing that just before 2.0.1 if there was no functional change
[04:13] <wallyworld> but if you have a 26 which actually fixes something....
[04:13] <axw> wallyworld: yes, this will fix https://bugs.launchpad.net/juju/+bug/1636648
[04:13] <mup> Bug #1636648: cinder fails with badRequest... "Invalid input for field/attribute device" <openstack-provider> <storage> <juju:In Progress by axwalk> <https://launchpad.net/bugs/1636648>
[04:13] <wallyworld> then that changes my thnking
[04:13] <wallyworld> do you see where i was coming from?
[04:14] <axw> wallyworld: yes
[04:14] <axw> wallyworld: but I thought this was meant to go through OIL before we cut 2.0.1
[04:14] <axw> so not sure on the timing
[04:14] <wallyworld> yeah, we will need to ensure that
[04:14] <axw> ok
[04:14] <wallyworld> let's land yours and we can track progress through OIL
[04:15] <axw> wallyworld: ok, sounds good. if you have a momen to review that, please do - it's pretty trivial
[04:15]  * axw lunches
[04:15] <wallyworld> looking now in fact :-)
[04:46] <axw> wallyworld: thanks
[04:46] <wallyworld> np
[05:04] <wallyworld> axw: oops (one liner) https://github.com/juju/juju/pull/6500
[05:06] <axw> wallyworld: LGTM
[05:06] <wallyworld> ta
[05:07] <axw> wallyworld: OK for me to land https://github.com/juju/juju/pull/6428 now then?
[05:07] <axw> then I'll base my update on top
[05:07] <wallyworld> yep
[05:08] <wallyworld> if you are happy with it
[05:08] <axw> looked fine, I'll take another look over
[05:11] <axw> wallyworld: actually hrm, looks like we're never assigning s.Openstack, so we'll leak HTTP servers
[05:11] <axw> wallyworld: I'll cherry-pick and fix that, and include in my PR
[05:11] <wallyworld> sgtm, ta
[05:47] <axw> wallyworld: bugger, seems there's an issue with keystone metadata source not working on heather's branch
[05:48] <wallyworld> oh, for the simple streams data
[05:48] <wallyworld> hmmm
[05:48] <wallyworld> yo think the issue is on the goose side?
[05:49] <wallyworld> or in that juju pr
[05:49] <axw> wallyworld: dunno, looking into it now
[05:49] <wallyworld> ok
[05:55] <axw> wallyworld: it looks like the object-store check is not quite sufficient for product-streams
[05:55] <axw> wallyworld: what do you think about disabling the API version check if the user passes in "" for the version?
[05:56] <axw> (and just use whatever's in the service URL)
[05:56] <axw> service catalogue
[05:56] <wallyworld> i *think* that's ok testing notwithstanding
[06:06] <axw> wallyworld: https://github.com/go-goose/goose/pull/27 please
[06:06] <axw> running a test in Juju now, so far so good
[06:07] <axw> it found the image metadata
[06:26] <wallyworld> axw: sorry, quassel has stopped beeping at me, missed ping
[06:29] <wallyworld> axw: lgtm with a suggestion. glad it was a simple fix
[06:44] <axw> wallyworld: last one I promise: https://github.com/juju/juju/pull/6501
[06:44] <wallyworld> no worries
[06:45] <axw> wallyworld: first commit is heather's, unchanged
[06:45] <wallyworld> ok
[06:47] <wallyworld> axw: lgtm, suggested a test for the no device case
[07:09] <menn0> wallyworld or axw: here's the fix for the issue that's causing lots of failures in develop: https://github.com/juju/juju/pull/6502
[07:10] <axw> menn0: looking
[07:10] <axw> and thank you
[07:10] <menn0> just writing up QA steps
[07:10] <wallyworld> yay
[07:15] <axw> menn0: LGTM, thanks
[07:15] <menn0> axw: cheers
[07:16] <menn0> wallyworld, axw: there's still other tests that are failing intermittently and need attention, but this gives us a better chance of a bless
[07:16] <wallyworld> yes, ty menno
[07:16]  * wallyworld off to soccer, bbiab
[07:52] <dimitern> macgreagoir: hey there
[07:52] <macgreagoir> dimitern: \o
[07:52] <dimitern> macgreagoir: rick_h_ suggested we should pair on the ipv6 setup / stuff
[07:52] <dimitern> :)
[07:53] <dimitern> macgreagoir: unless you are busy otherwise atm, ofc :)
[07:53] <macgreagoir> dimitern: Can I get back you about that? I'm just trying to finish part of it now.
[10:58] <Mmike> hi, lads. Where do I find wishlist for juju2 on launchpad?
[10:58] <Mmike> And ladies, hello!
[11:01] <mgz> hm, you mean as in features?
[11:07] <deanman> Is ftp used as a protocol in any operation of juju ?
[11:07] <mgz> nope
[11:09] <deanman> I have enabled TRACE logging to see why controller running inside LXD fails to download image to deploy a charm on a seperate LXD. I get the following http://paste.ubuntu.com/23382970/. Information there doesn't help. What could i further look into? pcap?
[11:22] <mgz> deanman: do you actually have routing to streams.canonical.com from that machine?
[11:26] <deanman> The key differentiator is proxy, if not using proxy my setup works just fine, if using proxy the guest Xenial machine is able to download image and boot LXD container but not when deploying a charm.
[11:27] <deanman> mgz: You mean whether this URL is resolvable?
[11:27] <mgz> yeah, in this case with the same proxy settings I guess
[11:28] <mgz> you probably do need some lower level inspection to see whether the correct requests are being sent out
[11:28] <deanman> mgz: I can manually curl that address and see content returned, i guess juju would have nagged anyway if it couldn't reach that URL, could it be that somehow proxy messes with content returned?
[11:31] <mgz> it's possible, but that log does look like juju nagging (at info level only)
[11:38] <deanman> I can deduce from https://github.com/juju/juju/blob/juju-2.0.0/tools/lxdclient/client_image.go that it should have failed earlier if it was a network problem.
[12:56] <perrito666> hey I suddenly have to run to the bank, bbl
[13:00] <mgz> voidspace: do you have a mo to help me work out if the bug I have is in juju or maas?
[13:15] <voidspace> mgz: yes
[13:15] <voidspace> mgz: hangout or PM?
[13:25] <mgz> voidspace: hangout?
[13:25] <voidspace> mgz: cool - I have 5 mins before 1:1 with rick_h_ though.
[13:25] <mgz> lets be fast
[13:25] <voidspace> kk
[13:25] <voidspace> mgz: see you in core
[13:46] <voidspace> mgz: right, 15 minutes until hangout - I'm digging out the maas docs
[13:47]  * mgz hopes back in core
[13:47] <mgz> hops
[13:47] <mgz> not hopes
[13:47] <voidspace> mgz: hopes is better
[13:52] <natefinch> odd, somehow my calendar got set to tuesday as the first day of the week
[13:53] <natefinch> oh, no, it was on 7 days.. wacky
[14:00] <rick_h_> katco: voidspace dimitern dooferlad ping for standup
[14:02] <dimitern> omw
[14:02] <dimitern> mgz: it will be useful to dump the NIC params here e.g.: 2016-10-26 11:31:50 INFO Changed existing interface: node-71f20964-71e9-11e5-8007-525400c43ce5 eth0
[14:02] <dimitern>  
[14:03] <mgz> dimitern: yeah, that could do with some more details
[14:13] <dimitern> mgz: I'm not sure maas can satisfy *both* a placement with --to and bootstrap spaces constraints
[14:14] <dimitern> mgz: if it happens some times but not others, the issue is probably hidden behind the log I pasted above
[14:15] <mgz> I expect --to overrides
[14:15] <mgz> anyway, the --to on bootstrap is fine
[14:15] <mgz> it's the bundle deploy which just uses constraints where things get interesting
[14:58]  * rick_h_ heads home from coffee shop
[15:04] <katco> rick_h_: are you in the 2.0 retro?
[16:00] <katco> balloons: hey i can't chat in bluejeans, but please don't hold back!
[16:05] <balloons> katco, I think the feedback is most useful in the context of how to make it work at Canonical. I am +1 for doing it -- have been for some time
[16:09] <katco> dooferlad: +1 to all of that
[16:09] <dooferlad> katco: thanks
[16:17] <katco> balloons: yes, i agree: it's paramount to confine the discussion to how it should work at canonical. that's a very agile concept anyhow :)
[18:30] <alexisb> rick_h_, ping
[18:35] <rick_h_> alexisb: pong
[18:35] <alexisb> heya rick_h_redir has a request
[18:41] <katco> rick_h_: re. your request: what priority is this? should i stop working on everything else?
[18:41] <rick_h_> katco: yes please to unblock release
[18:41] <katco> rick_h_: ok, starting on this
[18:43] <perrito666> k, new isp about to connect me expect me to be unresponsive, apologies
[18:49] <katco> rick_h_: so wait... we want develop -> 2.0? we're skipping staging?
[18:52] <rick_h_> katco: yes, staging is a subset of develop at the moment. We need the updates in develop.
[18:52] <katco> rick_h_: can you hangout rq?
[18:53] <rick_h_> katco: sure thing, meet you in ?core
[19:20] <thumper> rogpeppe, katco: morning, I've been thinking more about the retry thing, and I'm starting to get your viewpoint around the error handling. As my wife knows, I can be very stubborn but hopefully teachable
[19:21] <rogpeppe> thumper: hiya
[19:21] <katco> thumper: lol "strongly held beliefs loosely held" (thanks fwereade) is not a fault in my book
[19:21] <thumper> I just wanted to say so "in person"
[19:21] <rogpeppe> thumper: thanks for continuing to think it through :)
[19:22] <thumper> rather than just email
[19:22] <rogpeppe> thumper: that's appreciated
[19:22] <thumper> there is a wonderful saying
[19:22] <katco> thumper: rogpeppe: and thank you to both of you for putting so much effort into getting this right
[19:22] <thumper> you shouldn't hold on to a wrong idea just because you spent a long time making it
[19:22] <katco> thumper: yeah i immediately stole that one. not sure where he got it from
[19:23]  * katco has a moment of silence to miss fwereade's contribution here
[19:23] <rogpeppe> thumper: i like that - that is a good motto. apposite on many occasions i think.
[19:23]  * thumper nods
[19:24] <rogpeppe> thumper: shall we just go with gopkg.in/retry.v1 then? ISTM that it's something that deserves a larger scope than juju/
[19:25] <rogpeppe> thumper: (i removed the dependency on utils/clock, so it should be usable by external projects that want to keep their dependencies tight)
[19:26] <thumper> I'd like to bring things together first, then think about where
[19:26] <thumper> I also think that we shouldn't depend on utils/clock
[19:27] <thumper> we have always said that github.com/juju libraries aren't just for juju
[19:28] <rogpeppe> thumper: i agree that those libraries aren't just for juju, but i think the name does imply some juju relatedness to people.
[19:28] <thumper> yeah...
[19:28] <thumper> there is some squatter on the canonical name
[19:29] <rogpeppe> thumper: and some parts are definitely juju-centric - the way that an import of juju/utils mucks with gobal variables in net/http means I'd never recommend that to anyone external, for example.
[19:29] <thumper> what in juju/utils mucks?
[19:29] <rogpeppe> thumper: FWIW i think that snappy is already using the above import.
[19:30] <rogpeppe> thumper: http.go:20
[19:30] <thumper> ugh
[19:31] <thumper> that seems like a wrong place
[19:31] <rogpeppe> thumper: yes
[19:31] <thumper> libraries that modify globabls of other packages is very antisocial
[19:31] <rogpeppe> thumper: at least it doesn't make all HTTP connections drop after a single request like it did for years
[19:31] <thumper> pfft
[19:32] <rogpeppe> thumper: https://bugs.launchpad.net/juju/+bug/1491608
[19:32] <mup> Bug #1491608: importing juju/utils should not side-effect http.DefaultTransport <tech-debt> <juju:Triaged> <juju-core:Won't Fix> <https://launchpad.net/bugs/1491608>
[19:32] <mup> Bug #1636960 opened: Manual provider that spawns LXD containers <juju-core:New> <https://launchpad.net/bugs/1636960>
[19:39] <natefinch> rogpeppe: wow, that's bad
[19:52] <katco> balloons: ping, can you sanity check? https://github.com/juju/juju/pull/6504
[20:13] <natefinch> It is surprisingly hard to get url.parse to actually reject things
[20:26] <katco> so i'm on a new machine and having trouble building gh.com/lxc/lxd
[20:27] <katco> i can't remember if i ever had to set anything up... it looks from the README.md that a go get github.com/lxc/lxd isn't expected to work?
[20:27] <katco> there's additional libs required? can anyone confirm?
[20:29] <natefinch> katco: from the makefile:
[20:29] <natefinch> 	# Must a few times due to go get race
[20:29] <natefinch> 	-go get -t -v -d ./...
[20:29] <natefinch> 	-go get -t -v -d ./...
[20:29] <natefinch> 	-go get -t -v -d ./...
[20:30] <katco> natefinch: i'm getting errors on includes of .h files
[20:30] <katco> natefinch: i highly suspect my setup, but i wanted some confirmation
[20:30] <katco> natefinch: you're able to just do a go get?
[20:31] <natefinch> katco: I think I've built it before... possibly did some work to get there, I don't remember.  I presume you followed the steps in the readme?
[20:31] <katco> natefinch: nope, trying to avoid it
[20:32] <natefinch> ha
[20:32] <katco> natefinch: i don't want bleeding-edge lxd on my system, and the ppa doesn't seem to separate out that from the build-deps?
[20:33] <natefinch> I dunno.... tych0?
[20:35] <tych0> i htink the ppa bundles everything, and the archive version uses the archive's deps
[20:35] <tych0> what's the problem, exactly?
[20:35] <katco> tych0: is it possible to use the ppa for building but not for installing a binary?
[20:36] <tych0> katco: sure, just build the binary but don't copy it to /usr/bin
[20:36] <tych0> or did i misunderstand?
[20:36] <katco> tych0: if i add the ppa, and do apt install lxc, won't it install the binary from the ppa?
[20:36] <katco> tych0: or upgrade for that matter
[20:36] <tych0> the `lxc` binary comes from lxd-client
[20:36] <katco> tych0: ah ok different ppa? ppa:ubuntu-lxc/lxd-git-master is safe for building?
[20:37] <tych0> katco: i don't even think you need the PPA to build
[20:37] <tych0> i think the archive versions of golang should be okay for every release
[20:46] <katco> tych0: you are correct, it was indeed the way i had things set up. thanks for confirmation! and ty natefinch
[20:46] <tych0> katco: sure, np
[20:47] <katco> balloons: ping? ut?
[20:47] <balloons> katco, yes
[20:47] <balloons> katco, sure let me take a quick look
[20:48] <katco> balloons: ta
[20:48] <balloons> katco, the buildbot is going to ignore this -- personally I think if we're happy we can just merge it
[20:48] <balloons> it's been tested once, and we'll give it a full run once it's merged
[20:49] <balloons> (it ignores pr's not going into develop)
[20:49] <katco> balloons: ah ok
[20:49] <katco> balloons: so i'll just merge and we can start a test run?
[20:49] <balloons> yea
[20:50] <balloons> looks like you have the proper commit
[20:50] <katco> balloons: cool, merged.
[21:43] <wallyworld> katco: sent you an email about 2.0.1
[21:43] <katco> wallyworld: ok tal
[21:43] <wallyworld> thanks in advance :-)
[21:43] <katco> wallyworld: hth, shouldn't take long (WITH THE POWER OF EMACS!)
[21:43] <wallyworld> lol
[21:44] <wallyworld> katco: emacs, making development great again
[21:44] <katco> wallyworld: lol
[21:45]  * wallyworld prefers vi :-)
[21:45] <katco> wallyworld: no one is perfect
[21:45] <wallyworld> funny, funny
[21:45] <katco> wallyworld: i thought you liked ides?
[21:45] <wallyworld> yeah i do, but when i need to do quick editing, vi is it
[21:45] <katco> wallyworld: for me it's emacs -nw -q
[21:46] <wallyworld> of course it is :-)
[21:46] <katco> which i have aliased to qmacs for "quick emacs" ;p
[21:52] <katco> wallyworld: so you can't cherry-pick merge-commits, so i'll have to try and CP all the commits for that merge
[21:53] <wallyworld> katco: oh joy. i had a thought - just after that PR was another (test only fixes) to solve bad intermittent juju scp test fixes. might be worth taking that one so we get a good/better CI run
[21:53] <katco> wallyworld: was that the PR from menn0?
[21:54] <wallyworld> yeah
[21:54] <wallyworld> next commited PR after the goose one
[21:55] <katco> wallyworld: the next commit i see is bebd627 which is from dooferlad
[21:55] <katco> wallyworld: i don't see anything from menn0
[21:56] <menn0> katco: https://github.com/juju/juju/pull/6502
[21:56] <katco> menn0: ta... weird wonder why my local log is displaying something different
[21:57] <katco> menn0: dang it, last fetch didn't go through
[21:57] <katco> menn0: i see it now, ty
[22:02] <menn0> katco: cool. sorry was on a call.
[22:03] <katco> wallyworld: i lied earlier, i can cherry merge commits
[22:04] <wallyworld> awesome, i'm sure i have done it before so i was a bit confused but in a meeting so didn't really think too hard
[22:04] <wallyworld> katco: so think you are cherry pick 2 commits right?
[22:05] <katco> wallyworld: cherry-pick -m 1 <commit>
[22:05] <wallyworld> yep
[22:05] <wallyworld> that's what i use
[22:05] <wallyworld> so you are taking the goose commit and menno's
[22:07] <katco> wallyworld: correcy
[22:08] <katco> wallyworld: correct
[22:08] <wallyworld> tyvm
[22:16] <katco> wallyworld: menn0: sanity check please: https://github.com/juju/juju/pull/6505
[22:16] <wallyworld> looking
[22:16] <menn0> katco: looking
[22:17] <alexisb> anastasiamac, https://hangouts.google.com/hangouts/_/canonical.com/alexis-bruemmer
[22:17] <wallyworld> katco: looks good ty
[22:17] <alexisb> when you ar eready
[22:17] <katco> menn0: hit merge conflicts on yours
[22:17] <katco> menn0: i think i did the correct thing
[22:18] <menn0> katco: LGTM
[22:18] <katco> balloons: are you up on all this?
[22:18] <katco> wallyworld: menn0: tyvm
[22:18] <wallyworld> yes he is :-)
[22:19] <wallyworld> i raised it inthe release call
[22:19] <wallyworld> so it's my fault you needed to do this :-D
[22:19] <katco> wallyworld: ok :) will need a new test run balloons
[22:19] <katco> just merged
[22:19] <wallyworld> will will let the current run finish
[22:19] <wallyworld> and then look to the new one
[22:20] <katco> wallyworld: it was a hooge deal. terrible. and some commits i assume were good. but i make the best commits, everyone says so.
[22:20] <wallyworld> indeed :-)
[22:20] <katco> that was my attempt at trump-speak if that wasn't evident =|
[22:43] <perrito666> axw: already up? I have a vsphere thing to ping pong with you
[23:08] <axw> perrito666: I'm here now
[23:11] <perrito666> axw: are you on bluejeans?
[23:12] <mup> Bug #1636960 changed: Manual provider that spawns LXD containers <juju:Triaged> <https://launchpad.net/bugs/1636960>
[23:12] <axw> perrito666: I am now
[23:16] <alexisb> thumper, menn0, wallyworld ping
[23:21] <mup> Bug #1636960 opened: Manual provider that spawns LXD containers <juju:Triaged> <https://launchpad.net/bugs/1636960>
[23:30] <mup> Bug #1636960 changed: Manual provider that spawns LXD containers <juju:Triaged> <https://launchpad.net/bugs/1636960>
[23:44] <wallyworld> axw: ping after your breakfast etc and we can talk to thumper about cred migrations?
[23:44] <thumper> I'm looking to head up the road to a cafe for a bit
[23:45] <thumper> which isn't good for calls or irc
[23:45] <wallyworld> ok, can do it later
[23:45] <thumper> or now?
[23:45] <thumper> I really don't think there is a huge amount to talk about
[23:45] <wallyworld> i think axw needs to do school drop off etc
[23:45] <axw> thumper: now's fine for me. I just resent an email from june if you want to read that first
[23:45] <axw> nah, michelle's on leave so she'll take charlotte to school
[23:46] <thumper> what menn0 and I talked about yesterday was pack up the creds with the model, and error out if there are some that are on the controller already but differ
[23:47] <wallyworld> should we join the standup hangout again?
[23:47] <thumper> ok