[00:00] <wallyworld> rick_h__: something weird is going on; the ec2 config schema for master is identical to 1.25, so control bucket support should also be the same. so a bug would be good
[00:00] <wallyworld> oh wait, you said rax?
[00:01] <wallyworld> how is control-bucket getting into rackspace config
[00:01] <wallyworld> huh
[00:01] <wallyworld> and there it is
[00:02] <wallyworld> looks like someone cut and paste some ec2 code into rackspace provider
[00:02] <wallyworld> rick_h__: ^^^^ so yeah, that's a bug sadly
[00:04] <rick_h__> wallyworld: ok, will file and go back to previous alpha for demo hopefully
[00:05] <rick_h__> wallyworld: is there anything I can pass it to make it less cranky in alpha2?
[00:05] <wallyworld> yeah, sorry, it's a one line fix by the looks, just a cut and paste error
[00:05] <wallyworld> rick_h__: sadly no, i don't think so
[00:06] <rick_h__> wallyworld: k, ty for checking for me
[00:06] <wallyworld> rick_h__: np, i'll follow up with QA to see how our tests can improve
[00:07] <wallyworld> rick_h__: if you need a build for demo, i can do that for you
[00:20] <rick_h__> wallyworld:
[00:20]  * wallyworld waits in anticipation
[00:20] <rick_h__> wallyworld: ty for the QA follow up.
[00:21] <wallyworld> haven't done it yet, but will do tomorrow when we meet :-)
[00:21] <rick_h__> wallyworld: guessing we're not trying to create-model on each provider
[00:21] <wallyworld> guess not :-(
[00:21] <rick_h__> wallyworld: yea, just got me thinking about how that slipped by
[00:22] <wallyworld> rick_h__: i have a feeling a lot of the QA scripts are pre-JES
[00:59] <axw> anastasiamac: would you please review this small one? https://github.com/juju/juju/pull/4417
[01:00] <anastasiamac> axw: of course \o/
[01:03] <anastasiamac> axw: looks gr8! tyvm
[01:03] <axw> anastasiamac: ta
[01:20] <anastasiamac> axw: quartz could b multi-coloured too... and does not imply location (best opals are from Oz \o/) and does not start with "O" like some other teams already...
[01:20] <anastasiamac> :D
[01:23] <axw> anastasiamac: good points
[01:28] <anastasiamac> wallyworld: axw: show-contorller cleaned up http://reviews.vapour.ws/r/3814/
[01:28] <wallyworld> yay
[01:30] <axw> anastasiamac: will look shortly
[01:30] <axw> oh, I already did shipit
[01:31] <anastasiamac> axw: u did but I've added some output that u might want to agree to...
[01:31] <axw> anastasiamac: ok
[01:31] <anastasiamac> axw: no rush, whenever u get a chance \o/
[01:33] <axw> anastasiamac: why change to using file-based store?
[01:34] <axw> anastasiamac: in the tests
[01:36] <axw> wallyworld: a thought just occurred to me, we could change the "restore-bootstrap -b" on its head, and add a "--restore" flag to bootstrap
[01:36] <axw> wallyworld: not for now, maybe later
[01:36] <axw> wallyworld: I think that would make intent a bit clearer
[01:37] <wallyworld> hmm, not a bad idea, i'm asking anastasiamac to do a one pager on this, so she can consider it
[01:37] <anastasiamac> axw: easier to load in tests...
[01:37] <anastasiamac> and actually clearer what m loading too...
[01:38] <axw> anastasiamac: I'd rather we stop messing with the filesystem if possible. I suspect my change to jujuclienttesting (merging now) would make it clearer/easier for the in-mem case
[01:39] <axw> anastasiamac: I won't block it for now, but next time could you please look at the new MemStore, see if it's easier with the new struct?
[01:39] <axw> anastasiamac: ... and if not, try and make it easier, so we don't have to touch the filesystem
[01:40] <anastasiamac> axw: k, m happy to wait for ur changes, rebase and updte the tests.
[01:41] <wallyworld> axw: one liner http://reviews.vapour.ws/r/3858/
[01:41] <axw> wallyworld: LGTM
[01:41] <wallyworld> ta
[01:42] <anastasiamac> axw: altho, considering list-controller tests depend ont he same stuff.. i'd rather land this and then fix both command testsonce in memory store lands
[01:42] <axw> anastasiamac: fine by me
[01:42] <anastasiamac> axw: awesome \o/
[01:43] <anastasiamac> axw: so if u r happy with smaple output (in current tests probably esier to see), then m going to respect ur original ship-it and land
[01:43] <axw> anastasiamac: just a moment please, still looking
[01:44] <anastasiamac> axw: nps
[01:46] <axw> anastasiamac: couple of small things, and one biggish one -- I think we shouldn't be showing passwords by default
[01:46] <axw> wallyworld: ^^
[01:46] <axw> agree?
[01:46] <wallyworld> of course
[01:47] <anastasiamac> axw: when u say "by default" do u mean not at all?
[01:47] <anastasiamac> or do u mean have a flag?
[01:47] <axw> cherylj: thanks for letting aaron know -- I've been emailing him about this. Aaron says it's a trivial change
[01:47] <cherylj> axw: ah, ok
[01:48] <axw> anastasiamac: I mean, clear out the password flag unless the user provides "--include-passwords" or something
[01:48] <anastasiamac> also isnt this command only displays to users their own accounts?... we are not going out..
[01:48] <axw> anastasiamac: someone might want to get the addresses for their controller, and inadvertantly show a conference room their password
[01:49] <anastasiamac> axw: ha. i'll add a flag
[01:49] <anastasiamac> cherylj: pm-ed u
[01:52] <axw> wallyworld: I've created a "backup/restore 2.0" card under Juju 2.0
[01:53] <wallyworld> great ty
[01:53] <axw> the board is getting out of hand :p
[01:59] <wallyworld> yes, too much work :-(
[02:43] <axw> wallyworld: do you have time to review another one? https://github.com/juju/juju/pull/4419  -- ignoring the first commit, and the jenv.go stuff in the second one
[02:43] <axw> (covered by other PRs)
[02:43] <wallyworld> axw: just heading out, will get to it as soon as i can
[02:43] <axw> wallyworld: ok, nps
[02:54] <axw> argggggghhhhhhhh. have the state tests gotten worse, or were they always this shit
[02:54] <anastasiamac> axw: probably always
[02:56] <axw> seems like every 2nd test run fails because "no reachable servers" or similar
[02:57] <anastasiamac> :(
[03:15] <bradm> anyone know what generating /etc/rsyslog.d/25-juju.conf ?  its got a dodgy IP in it that I need to remove, from virbr0 as well as all the juju state nodes.  it only appears to be in the state nodes
[03:26] <menn0> thumper or waigani: this will be used to replace most of what the current statestarter worker does: http://reviews.vapour.ws/r/3860/
[03:27]  * thumper leaves for waigani
[03:32] <mup> Bug #1544846 changed: restore fails with could not exit restoring status <nil> <backup-restore> <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1544846>
[03:34] <waigani> menn0: sorry just saw your PR looking now
[03:35] <mup> Bug #1544846 opened: restore fails with could not exit restoring status <nil> <backup-restore> <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1544846>
[03:35] <menn0> waigani: np
[03:37] <waigani> thumper: btw didn't spot anything weird in the diff. Though I release I merged in tip, not latest blessed master. But still, they're not seeing it at all in master.
[03:38] <waigani> *realize
[03:38] <thumper> waigani: weird
[03:38] <mup> Bug #1544846 changed: restore fails with could not exit restoring status <nil> <backup-restore> <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1544846>
[03:38] <thumper> waigani: I have to head out shortly, so either check in with menn0 or we could go through it tomorrow
[03:39] <waigani> thumper: will do. cheers.
[03:53] <mup> Bug #1545562 opened: Restore assumes systemd present on machines <backup-restore> <juju-core:Triaged> <https://launchpad.net/bugs/1545562>
[03:53] <mup> Bug #1545563 opened: Cannot deploy service after restoring <backup-restore> <juju-core:Triaged> <https://launchpad.net/bugs/1545563>
[03:53] <mup> Bug #1545568 opened: api/backups/restore.go has no unit tests <backup-restore> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1545568>
[03:59] <mup> Bug #1545562 changed: Restore assumes systemd present on machines <backup-restore> <juju-core:Triaged> <https://launchpad.net/bugs/1545562>
[03:59] <mup> Bug #1545563 changed: Cannot deploy service after restoring <backup-restore> <juju-core:Triaged> <https://launchpad.net/bugs/1545563>
[03:59] <mup> Bug #1545568 changed: api/backups/restore.go has no unit tests <backup-restore> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1545568>
[04:02] <mup> Bug #1545562 opened: Restore assumes systemd present on machines <backup-restore> <juju-core:Triaged> <https://launchpad.net/bugs/1545562>
[04:02] <mup> Bug #1545563 opened: Cannot deploy service after restoring <backup-restore> <juju-core:Triaged> <https://launchpad.net/bugs/1545563>
[04:02] <mup> Bug #1545568 opened: api/backups/restore.go has no unit tests <backup-restore> <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1545568>
[05:35] <mup> Bug #1545589 opened: Destroying a model leaves stale current-model file <destroy-environment> <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1545589>
[05:49] <cherylj> wallyworld, axw, could you guys take a look at http://reviews.vapour.ws/r/3861/ ?
[05:58] <axw> cherylj: I don't understand this comment: This is necessary as
[05:58] <axw> / the error type returned from a facade call is rpc.RequestError
[05:58] <axw> / and we cannot use params.IsCodeUpgradeInProgress
[05:58] <axw> cherylj: RequestError is an rpc.ErrorCoder, so should be usable in params.ErrCode
[05:59] <axw> (which is what IsCode... functions use under the hood)
[06:00] <davecheney> an the "code" is just a string
[06:02] <cherylj> ah, I may have mixed up my comments.  We can't use params.IsCodeUpgradeInProgress, because the code returned from the rpc call *isn't* apiserver.CodeUpgradeInProgress
[06:03] <wallyworld> cherylj: sure, looking
[06:03] <cherylj> it's the inUpgradeError returned from the upgrading_root
[06:03] <cherylj> it was hard to keep track of all the type mismatches
[06:04] <cherylj> I'll update the comment
[06:06] <cherylj> actually, maybe I'll go back to what it was before, and add in a new function into upgrading_root.go to check IsInUpgradeError
[06:06] <cherylj> axw: how does that sound? ^^
[06:06] <cherylj> (and I mean, what I had it as before I committed)
[06:06] <axw> cherylj: as in do the check on the servert, and translate to the code that the client was expecting?
[06:06] <axw> server*
[06:08] <cherylj> axw: that's not quite what I was thinking, although I could do that.
[06:09] <axw> cherylj: can you explain more? sorry, slow. I'm not keen to have snowflakes that don't use the IsCode... functions
[06:09] <cherylj> Yeah, I'm sorry, I'm super tired
[06:09] <cherylj> I was going to add a func IsCodeInUpgrade()....
[06:10] <cherylj> or I could have the existing in Upgrade check see if it matches CodeUpgradeInProgress or the upgrade_root.go inUpgradeErr
[06:11] <cherylj> am I still not making sense?  It is after midnight here.  Maybe I should go to sleep and continue this tomorrow
[06:12] <axw> cherylj: you may be, but I still don't understand :p
[06:12] <cherylj> heh, ok, let me push up a proposed change
[06:13] <axw> cherylj: sounds good, I comprehend code better than english
[06:35] <wallyworld> axw: sorry for delay, reviewed your earlier pr, see what you think of suggestions
[06:35] <cherylj> axw: did you have any other concerns with the PR?
[06:41] <axw> cherylj: nothing else jumped out
[06:42] <axw> wallyworld: thanks, looking in a sec
[06:42] <cherylj> ok, I'm just retesting with my change.  This takes forever...
[06:44] <wallyworld> axw: later when you are free http://reviews.vapour.ws/r/3862/
[07:00] <cherylj> omfg why is it taking 20 minutes to do apt-get update on an AWS instance?!
[07:10] <axw> wallyworld: PTAL. looking at yours now
[07:14] <anastasiamac> axw: wallyworld: we don't write to models or accounts files yet, riite?..
[07:14] <axw> anastasiamac: I'm working on it
[07:14] <anastasiamac> axw: \o/
[07:14] <anastasiamac> axw: so m not going crazy a little here.. :D
[07:18] <axw> wallyworld: just one main concern, about the rpc change
[07:18] <wallyworld> ok
[07:20] <wallyworld> axw: with the remaining ClientStore() comment, i was really trying to look for a way not to have that method
[07:20] <wallyworld> the store is really internal to the command
[07:21] <wallyworld> if the method is merely used to see what's been set is nil, can we cater for that another way
[07:24] <axw> wallyworld: each controller or model command will need to call ClientStore()
[07:24] <axw> wallyworld: well maybe not all of them, but some of them do
[07:24] <wallyworld> ok
[07:24] <axw> wallyworld: e.g. list-controllers will call ClientStore() to get the store and then call AllControllers()
[07:25] <wallyworld> fair enough lgtm
[07:28] <wallyworld> axw: the version != 0 thing. that appeared fundamentally broken. it totally rejected rpc calls where the version was not 0, and with all the old code removed, tests failed
[07:28] <wallyworld> i don't know a reason why we'd not allow rpc calls with version != 0
[07:32] <axw> wallyworld: version isn't used in that code below there, so I'm a bit concerned that something is passing in a version wrongly
[07:32] <wallyworld> axw: yeah, it was only used in that bogus (IMO) check
[07:33] <wallyworld> why would we return an error if version != 0 ?
[07:33] <wallyworld> I've tested the branch live with lxd, everythign seems fine
[07:34] <wallyworld> i'd have to check again, i think the test failure was on the Admin facade
[07:44] <axw> wallyworld: sorry, it just doesn't look right. if an object doesn't support versioned methods, then the client shouldn't be requesting them. can you find the object & method that's being requested?
[07:45] <wallyworld> i'll check soon, just diggin into some python client stuff
[07:48] <mup> Bug #1545126 changed: juju/maas do not create ptr reccords for bare metal servers with multiple networks <MAAS:New> <https://launchpad.net/bugs/1545126>
[08:11] <cherylj> ugh, this upgrade in progress error is funky - the error string is put into the Message and not the Code
[08:12] <anastasiamac> cherylj: omg, i hate being the clock but is it not 2am for u?
[08:12] <cherylj> anastasiamac: it is
[08:13] <anastasiamac> cherylj: wow
[08:13] <dimitern> cherylj, that's because it's not a coded error - just like all generic errors it has no code and just message
[08:14] <cherylj> dimitern: yeah, but I can't inspect it using errors.Cause() == upgradeErr because it's an rpc.ResultError so the types are different
[08:14] <cherylj> so I need to use the check I have
[08:14] <cherylj> bleh
[08:15] <dimitern> cherylj, yeah, that's a result of not using concrete errors, unfortunately - and need to resort to strings.HasSuffix(err.Error(), ...) :.
[08:15] <dimitern> :/
[08:15] <cherylj> just got a ship it from thumper, so fuck it.  I'm merging and trying to get some sleep
[08:16] <dimitern> cherylj, you should +1
[08:16] <cherylj> heh
[08:16] <cherylj> thanks for taking  a look at that bug, dimitern
[08:16] <dimitern> no worries
[08:17] <dimitern> cherylj, I hope some of my friday rant on that blocker bug helped a bit :)
[08:17] <axw> cherylj: it appears that the IsCodeUpgradeInProgress only works if the original error is state.UpgradeInProgressError
[08:18] <axw> cherylj: and not the one in apiserver
[08:18] <cherylj> axw: yeah, I found that out the hard way yesterday
[08:18] <axw> cherylj: ok. well, anyway, sleep :)
[08:23] <wallyworld> axw: that rpc FindMethod() call is being asked to find the "Login" method on the "Admin" facade with version = 3. That's when we fail the test. That code comes from api/state.go Login() which tried v2 then fell back to v1 and then v0.So the only reason it was all working is due to some obsolete fallback code in that client Login() method which I removed
[08:24] <axw> wallyworld: so the other versions never worked? :/
[08:24] <wallyworld> master always fell bacl to v0
[08:24] <wallyworld> or so the code seems to suggest
[08:25] <wallyworld> there were 2 lots is params.IsCodeNotImplemented()
[08:25] <wallyworld> in that api state Login()
[08:25] <axw> SERVERS Y U NO REACHABLE
[08:25] <wallyworld> i hate that error
[08:25] <axw> wallyworld: sorry, I still need to convince myself
[08:25] <wallyworld> axw: open up api/state.go
[08:26] <wallyworld> see the Login() method at the top
[08:26] <wallyworld> i removed the fallbacks
[08:26] <axw> wallyworld: I'm *fairly* sure I don't see three Login RPC calls each time I connect though...
[08:27] <wallyworld> need to check i guess, maybe it's the tests only affected. but the code path to the error makes sense. we are passing a version 3 and it complains when it has no right to
[08:28] <wallyworld> the method is there on the facade
[08:29] <axw> wallyworld: I'm going to pull your branch and dig a bit. if I can convince myself it's ok, I'll merge it (unless you're still around)
[08:29] <wallyworld> i'll be here. i'll see what master does also
[08:36] <axw> wallyworld: I think it must be tests only, because live test without that code removed works
[08:36] <axw> wallyworld: at the top level we should have apiserver.anonRoot, which has its own FindMethod. I suspect some test is constructing a login facade and serving that directly
[08:38] <wallyworld> axw: but live, we should still be passing the login call to anonroot i would have thought
[08:38] <axw> wallyworld: yes... testing live works. it goes to anonRoot, but anonRoot is not one of those rpcreflect things that you changed
[08:39] <wallyworld> ok, i'll dig into tests later fater dinner. but i still can see why we'd just blanket reject calls with non 0 version
[08:39] <wallyworld> can't
[08:42] <dimitern> wallyworld, axw, fwiw apiserver/doLogin calls maintenanceInProgress which fakes up a login request with a user tag
[08:42] <dimitern> might be related, as I discovered while looking into why upgrade/restore didn't work as expected
[08:55] <axw> wallyworld: the problem is the errRoot
[08:56] <axw> wallyworld: changing that to have a FindMethod which ignores the version, and using ServeFinder does the trick
[08:57] <axw> wallyworld: the reason for not accepting a non-zero version is strictness: objects of that type don't understand versions, ergo the client shouldn't request versions. if they do, they're probably doing something wrong
[08:57] <axw> safer to ignore versions on a case-by-case basis
[09:00] <frobware> jam: just rebooting to locate my headset...
[09:01] <jam> frobware: k
[09:32] <voidspace> dimitern: frobware: dooferlad: if you get a chance http://reviews.vapour.ws/r/3848/
[09:33] <dimitern> voidspace, sure, looking
[09:39] <dimitern> voidspace, reviewed
[09:43] <voidspace> dimitern: you think the local machine will never attempt to login (your comment about that code path never being taken)?
[09:43] <voidspace> dimitern: won't agents that use the api login as the local machine
[09:44] <dimitern> voidspace, they'll try, but have a look in maintenanceInProgress and follow what happens when the validator return an unknown error (i.e. not UpgradeInProgress or one of the others)
[09:45] <dimitern> voidspace, actually doLogin is the place
[09:46] <voidspace> dimitern: hmmm...
[09:47] <voidspace> dimitern: I see the code, however that returns a concrete error - and we see the "space discovery in progress" error
[09:47] <dimitern> voidspace, that's why I suggested (not now, but soon) to add a concrete error for discovery in progress and check it early in doLogin
[09:47] <voidspace> dimitern: which indicates to me that code path isn't being hit
[09:48] <voidspace> dimitern: we hit the code path earlier which just fails - we bail out before maintenanceInProgress is called
[09:48] <voidspace> the switch on concrete error types
[09:48] <voidspace> dimitern: but those cases all return a restricted api - we either return full api or no api
[09:49] <voidspace> mind you, not if the login succeeds
[09:49] <dimitern> voidspace, yeah
[09:49] <voidspace> ah, so for the local machine doLogin still fails
[09:49] <voidspace> so why bother allowing local machine at all
[09:49] <dimitern> voidspace, it fails for any machine
[09:49] <voidspace> it will attempt to login, succeed, then double check to see if arbitrary logins work
[09:49] <voidspace> when they don't it will bail
[09:50] <dimitern> voidspace, if we get as far down as doCheckCreds and maintenanceInProgress
[09:50] <voidspace> well, only if there's an error
[09:50] <voidspace> if they logged in with local machine (e.g. the discover spaces worker which needs access to the api)
[09:50] <voidspace> they should get that far and doCheckCreds should succeed
[09:51] <voidspace> so it will never hit maintenanceInProgress
[09:51] <dimitern> voidspace, nope, because of line 68 above
[09:51] <jam> frobware: did I miss you somehow?
[09:51] <voidspace> dimitern: if the login is from the local machine they will get "case nil"
[09:51] <voidspace> dimitern: no error at all
[09:51] <frobware> jam: nope was still there, saw you come back and thought you disconnected
[09:52] <voidspace> dimitern: and if the login isn't local machine it will fail completely on line 68
[09:52] <voidspace> dimitern: and that's all desired behaviour I think
[09:52] <jam> frobware: yeah, I had to restart the connection, but now I don't seem to see you anymore
[09:53] <frobware> jam: I got disconnected
[09:53] <frobware> jam: live migration. :)
[09:53] <jam> frobware: k. I'm back in the hangout
[09:54] <frobware> jam: trying..
[09:54] <dimitern> on error from checkCreds the s.validator is called again with a user tag.. what a mess :/
[09:55] <voidspace> dimitern: right, but checkCreds shouldn't fail should it?
[09:56] <wallyworld> axw: changes pushed
[09:57] <dimitern> voidspace, I'd expect so
[09:58] <dimitern> voidspace, but maybe it's deeper than that - e.g. something around empty uuid (for backwards compatibility), the MA trying v2 then v1 / v0 ?
[09:58] <dooferlad> dimitern, voidspace, frobware: may be a tiny bit late for standup - just off to get coffee.
[09:58] <dimitern> dooferlad, np
[09:59] <axw> wallyworld: reviewed
[09:59] <wallyworld> ta
[09:59] <axw> gotta go take care of the kids for a while, bbl
[10:06] <menn0> fwereade: would you mind having a look at http://reviews.vapour.ws/r/3860/ pls?
[10:06] <menn0> fwereade: a bit of infrastructure for converting the state worker to work under the dependency engine
[10:08] <dimitern> voidspace, standup?
[10:09] <voidspace> dimitern: oops, sorry - omw
[10:11] <voidspace> dimitern: frobware: uhm, I can't login
[10:11] <voidspace> dimitern: frobware: I lost my phone over the weekend - I thought I had some saved codes for two factor auth in my gmail account
[10:11] <voidspace> dimitern: frobware: but I don't - I'll have to contact IS to get them to turn off two factor temporarily
[10:12] <voidspace> dimitern: frobware: sorry :-(
[10:12] <voidspace> dimitern: frobware: dooferlad: my standup report - test fixes and discovery reliability landing now
[10:13] <dimitern> voidspace, ok, np
[10:13] <voidspace> dimitern: frobware: dooferlad: I've been working on having the maas provider (maasInstance) Addresses method add provider id
[10:14] <voidspace> dimitern: frobware: dooferlad: that's complete but needs gomaasapi support for the spaces endpoint in the test server
[10:14] <voidspace> dimitern: frobware: dooferlad: which is partly implemented but not usable (or tested) - so I've been working on that
[10:14] <voidspace> when that is done I can test my branch for provider ids and land that
[10:14] <voidspace> dimitern: frobware: dooferlad: caveat is that we need both the provider id *and* the space name
[10:15] <voidspace> dimitern: frobware: dooferlad: so addresses out of the provider will have space name and id set - but this will be a *maas name* not a juju name for the space
[10:15] <voidspace> dimitern: frobware: dooferlad: so we have to ensure it is converted before ever storing it in state or we will confuse ourselves a great deal
[10:16] <voidspace> dimitern: frobware: dooferlad: *or* we add SpaceProviderName *as well*, which is annoying but might be better
[10:17] <voidspace> or we just use provider id and don't set the provider space name, this might actually be better
[10:17] <voidspace> but we have code that currently relies on having the name set I think
[10:17] <dimitern> voidspace, let's sync up on this after standup
[10:18] <voidspace> dimitern: ok
[11:02] <perrito666> morning all
[11:27] <perrito666> mm, odd for some operations lxd provider seems to be unregistered
[12:03] <mup> Bug #1545686 opened: Multi-series not backwards compatible <juju-core:New> <https://launchpad.net/bugs/1545686>
[12:06] <mup> Bug #1545686 changed: Multi-series not backwards compatible <juju-core:New> <https://launchpad.net/bugs/1545686>
[12:12] <mup> Bug #1545686 opened: Multi-series not backwards compatible <juju-core:New> <https://launchpad.net/bugs/1545686>
[12:18] <mup> Bug #1545686 changed: Multi-series not backwards compatible <juju-core:New> <https://launchpad.net/bugs/1545686>
[12:24] <mup> Bug #1545686 opened: Multi-series not backwards compatible <juju-core:New> <https://launchpad.net/bugs/1545686>
[12:51] <axw> wallyworld: there are assumptions in the code that the initial controller name == initial model name
[12:51] <axw> wallyworld: so I've had to revert the model name back to controller name, from "admin"
[12:51] <wallyworld> damn, i thought we could work around those
[12:51] <axw> wallyworld: possibly in a follow up, but it wasn't working right
[12:52] <wallyworld> sure np
[12:52] <wallyworld> i wasn't fully across how deeply ingrained the assumption was
[12:53] <rick_h___> :(
[12:53] <rick_h___> thanks for trying!
[12:53] <wallyworld> rick_h__: temporary setback, it will be fixed :-)
[12:53] <axw> wallyworld: sorry about the rambling PR, the tendrils keep spreading
[12:53] <wallyworld> understood
[12:53] <rick_h___> wallyworld: is there anyone that can hand hold an outside commit? Looks like OCR is out today (domas)
[12:54] <rick_h___> wallyworld: https://github.com/juju/juju/pull/4426 is from an outsider through the mailing list trying to get the m4 types to work
[12:54] <rick_h___> wallyworld: so needs some kid gloves and "yay outside commits" love and such
[12:54] <wallyworld> rick_h__: perrito666 would love to :-)
[12:54] <rick_h___> ty :)
[12:54] <wallyworld> he's at SOD
[12:54] <rick_h___> k
[12:55] <wallyworld> rick_h__: longer term, we want to query those instance types using the new aws api
[12:55] <wallyworld> maybe for 2.1
[12:55] <rick_h___> wallyworld: completely understand and agree
[12:55] <rick_h___> yep
[12:56] <rick_h___> marcoceppi: ^ fyi
[12:56] <axw> wallyworld: at the very least, we should probably stop caring about the region and assume theyre the same relative costs across all
[12:56] <rick_h___> marcoceppi: faster to reply than me :P
[12:57] <wallyworld> axw: that is sensible, the costs are just approximate anyway
[12:57] <wallyworld> used in sorting
[12:57] <wallyworld> to select the cheapest by default
[12:58] <marcoceppi> interesting.
[12:59] <axw> I'm off, bonne nuit
[13:06] <mup> Bug #1545704 opened: no-auto-upgrade not respected in environments.yaml <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1545704>
[13:08] <rick_h___> marcoceppi: ?
[13:08] <rick_h___> marcoceppi: also fyi email on the way I need help on asap please so I can help the team out
[13:08] <marcoceppi> rick_h___: I like the idea of moving aws queries out of the codebase
[13:09] <rick_h___> marcoceppi: oic, yea. I more meant that we have a reviewer nominated so we don't both bug folks on it.
[13:09] <rick_h___> marcoceppi: but yea, moving the instance types out is a long standing wishlist thing for the team heh
[13:09] <marcoceppi> rick_h___: oh, cool. I just say I'm going to bug someone but never actually do it ;)
[13:09] <rick_h___> marcoceppi: :P
[13:12] <wallyworld> rick_h__: marcoceppi: until recently we haven't had the option for aws. was built into openstack from day one
[13:12] <mup> Bug #1545712 opened: WARNING juju.network address.go:268 no hostPorts found in space "default" <network> <juju-core:New> <https://launchpad.net/bugs/1545712>
[13:22] <rick_h___> wallyworld: yea, the new api for that data is good stuff from aws
[13:22] <wallyworld> and not a day too soon
[13:42] <mup> Bug #1545704 changed: no-auto-upgrade not respected in environments.yaml <kanban-cross-team> <landscape> <juju-core:Invalid> <https://launchpad.net/bugs/1545704>
[13:43] <mup> Bug #1545713 opened: Lost Unit when specifying constraints incorrectly <juju-core:New> <https://launchpad.net/bugs/1545713>
[13:57] <tvansteenburgh> wallyworld: you and dpb1 proceed w/o me on the python-jujuclient stuff - i can't make the meeting. if i need to be in the loop (to help with the actual work), please take notes or something.
[14:01] <voidspace> frobware: dooferlad: dimitern: in sapphire room?
[14:02] <voidspace> frobware: dooferlad: dimitern: our normal retrospective room, or our normal standup room?
[14:02] <voidspace> I'm in sapphire alone...
[14:03] <dooferlad> voidspace: https://plus.google.com/hangouts/_/canonical.com/juju-sapphire
[14:03] <frobware> voidspace, normal standup
[14:03] <dooferlad> voidspace: that is where andrew and I are
[14:03] <voidspace> I guessed wrong...
[14:04] <dimitern> frobware, voidspace, dooferlad, sorry guys just got back in, omw
[14:15] <marcoceppi> wallyworld: I'll be filling in for tvansteenburgh tomorrow
[14:21] <wwitzel3> the ol' bait and switch
[14:22] <rick_h__> hah
[14:41] <perrito666> ohh, today is a holiday in the US, that explains the silence
[14:41] <rick_h__> ssshhhh
[14:42] <rick_h__> we're paying respects to our presidents today
[14:42] <perrito666> you clearly have better presidens than we do :p
[16:06] <bogdanteleaga> do charms need to be changed in any way for 2.0? I've got one charm I've been using for a while now for testing, but it doesn't even get downloaded to the machine
[16:08] <voidspace> frobware: dimitern: dooferlad: PR for gomaasapi spaces support https://github.com/juju/gomaasapi/pull/4
[16:13] <dimitern> voidspace, looking
[16:30] <dimitern> voidspace, what's the significance of the *Space used in server.spaces ?
[16:30] <dimitern> voidspace, it is an optimization to not fetch subnets again?
[16:32] <voidspace> dimitern: no, it's so that any changes persist rather than them being copied
[16:32] <voidspace> dimitern: it makes them mutable
[16:32] <dimitern> voidspace, right
[16:33] <dimitern> voidspace, LGTM
[16:34] <voidspace> dimitern: thanks
[16:34] <dimitern> we should really sort out the growing code duplication in gomaasapi soon btw
[16:35] <voidspace> dimitern: fair point about goroutine safety - but this is a test server
[16:36] <voidspace> dimitern: and incrementing id rather than dict iteration preserves order of result by id
[16:37] <dimitern> voidspace, yeah
[16:37] <voidspace> dimitern: not my code but I assume that is the intent
[16:37] <dimitern> voidspace, exactly :)
[16:37] <dimitern> voidspace, that's the point - if the reason is not obvious, the code needs refactoring
[16:38] <voidspace> dimitern: well, a comment would do
[16:38] <dimitern> voidspace, +1
[16:38] <dimitern> just because it's test code doesn't mean we shouldn't try to make it clean
[16:39] <voidspace> dimitern: I've added a comment
[16:39] <voidspace> dimitern: does $$merge$$ work here?
[16:39] <voidspace> doesn't look like it
[16:39] <dimitern> voidspace, cheers
[16:39] <dimitern> voidspace, yes, it should
[16:39] <voidspace> ah well, I'll wait a bit and see then
[16:40] <voidspace> ah yes, merge request accepted
[16:40] <voidspace> aaand merged
[16:40] <dimitern> voidspace, sweet :)
[16:41] <voidspace> back to juju then
[23:06] <perrito666> wallyworld: be warned, it is starting to rain here so power might go off (just in case I dont show at the standup)
[23:06] <wallyworld> yay
[23:08] <axw> wallyworld: I might have to look at fixing the "juju status" code this morning, it takes 10 minutes every time I do a full test run...
[23:08] <axw> killing me
[23:08] <wallyworld> ouch
[23:09] <axw> just the cmd/juju/status package
[23:48] <davecheney> uh, why does the apiserver import the api client during testing ?!?!