[00:18] <davechen1y> bdx: no
[00:18] <davechen1y> bdx: why do you ask ?
[00:21] <mwhudson> davechen1y: rebuild testing suggests that making 'real go' the default  on ppc64 would lead to unhappiness
[00:21] <mwhudson> mostly because of the limited cgo
[01:23] <moqq> alexisb: FYI after wrestling around with a failed upgrade-juju its working and the cpu is behaving. will hit up that bug report if anything goes sideways again
[01:31] <davechen1y> mwhudson: why do we need cgo ?
[01:31] <mwhudson> davechen1y: "we" as in juju don'
[01:31] <mwhudson> t but lots of things in the archive do
[01:32] <davechen1y> when you say lots
[01:32] <davechen1y> can you quantify ?
[01:32] <davechen1y> 10,000 packages ?
[01:32] <davechen1y> 10 packages ?
[01:32] <davechen1y> i find it hard to believe that gccgo's cgo support is better ?
[01:32] <mwhudson> in between those
[01:32] <mwhudson> cgo on ppc64el is internal linking only
[01:33] <mwhudson> so it's pretty easy to step outside the bounds of what that can handle
[01:33] <mwhudson> i'll be able to quantify better tomorrow, still lots of builds going
[01:33] <mwhudson> some of these indeed don't build on ppc64el with gccgo either
[01:33] <davechen1y> http://paste.ubuntu.com/11997181/
[01:34] <davechen1y> oh come on
[01:34] <davechen1y> mwhudson: i'm annoyed by this
[01:34] <davechen1y> this is a problem canonical has done to itself
[01:34] <mwhudson> davechen1y: i am also annoyed
[01:34] <davechen1y> and if that means we don't get go 1.5 everywhere
[01:34] <davechen1y> i will be more than just annoyed
[01:35] <mwhudson> a recent go 1.5 change breaks docker and my go tools packages are insane for reasons i don't understand
[01:35] <davechen1y> mwhudson: more practically
[01:35] <davechen1y> is now the time to suggest taht go versions be versioned in ubuntu in the same way gcc is ?
[01:36] <davechen1y> ie, go-1.4, go 1.5
[01:36] <davechen1y> like we have gcc-4.8
[01:36] <mwhudson> i think there is certainly merit in that idea
[01:36] <davechen1y> how do we make that a reality ?
[01:36] <davechen1y> it needs to happen immediately
[01:36] <davechen1y> ie, before the 20th
[01:37] <davechen1y> hmm that means they also need to be co installable
[01:37] <mwhudson> yeah
[01:37] <davechen1y> and it's going to widen the set of alternatives for who owns /usr/bin/go
[01:37] <mwhudson> it wouldn't be trivial
[01:37] <davechen1y> co installable is doable
[01:38] <davechen1y> who owns /usr/bin/go will be more complicated
[01:38] <mwhudson> yeah not super hard, just a bunch of pain
[01:38] <mwhudson> well that's managed by alternatives now
[01:38] <mwhudson> (which is not how gcc does /usr/bin/gcc)
[01:38] <davechen1y> yeah
[01:39] <mwhudson> mm
[01:39] <mwhudson> maybe i should retract my opening statement
[01:39] <mwhudson> so long as go 1.5 builds juju and lxd on ppc64el
[01:40] <mwhudson> i don't know how much of this other stuff we care about
[01:45] <mwhudson> oh
[01:45] <mwhudson> lxd fails to build :(
[01:45] <mwhudson> https://launchpadlibrarian.net/213514232/buildlog_ubuntu-wily-ppc64el.lxd_0.14-0ubuntu3_BUILDING.txt.gz
[01:45] <mwhudson> still if it's just that, we can build it with gccgo
[01:45] <mwhudson> (which does work)
[01:47] <davechen1y> it doesn't build because go-sqlite3 does not support ppc
[01:47] <davechen1y> oh
[01:47] <davechen1y> crap
[01:47] <davechen1y> fucking cgo
[01:47] <davechen1y> why does that encode a database ?
[01:47] <davechen1y> why does every fucking project have to have a database
[01:48] <davechen1y> how is that helping us, as a species ?
[01:56] <davechen1y> https://bugs.launchpad.net/juju-core/+bug/1481133
[01:56] <mup> Bug #1481133: version: tests fail on arm64 14.04 <juju-core:New> <https://launchpad.net/bugs/1481133>
[01:57] <davechen1y> if this is a test isolation problem I'm going to throw a shoe
[01:58] <mwhudson> davechen1y: i guess there was never a precise for arm64?
[01:59] <mwhudson> if that is the cause, i think shoe-throwing would still be appropriate
[01:59] <davechen1y> i'm going to throw both
[02:02] <davechen1y> https://bugs.launchpad.net/juju-core/+bug/1481133/comments/1
[02:02] <davechen1y> FML
[02:02] <mup> Bug #1481133: version: tests fail on arm64 14.04 <juju-core:New> <https://launchpad.net/bugs/1481133>
[02:10] <mup> Bug #1481133 opened: version: tests fail on arm64 14.04 <juju-core:New> <https://launchpad.net/bugs/1481133>
[02:13] <mup> Bug #1481133 changed: version: tests fail on arm64 14.04 <juju-core:New> <https://launchpad.net/bugs/1481133>
[02:21] <mwhudson> davechen1y: is the proto-plan to try juju on ppc64 next?
[02:21] <davechen1y> mwhudson: i guess
[02:22] <davechen1y> actually, yes
[02:22] <davechen1y> now I have the script
[02:25] <mup> Bug #1481133 opened: version: tests fail on arm64 14.04 <juju-core:New> <https://launchpad.net/bugs/1481133>
[06:41] <axw> wallyworld: I'm wanting to add status to volumes and filesystems. what's the appropriate way to marshal that over the API? existing stuff is using api.AgentStatus, which doesn't seem quite right for a non-agent entity... but it is being used for workload and service status too
[06:44] <wallyworld> axw: from memory, that struct grew to accomodate the extra workload status info, somewhat avoiding api churn. it's messy because there's stuff from 1.18, different stuff added in 1.19 which is supposed to be removed, the legacy info for backwards compat, and the new stuff
[06:44] <wallyworld> maybe it's time to bite the bullet and add a new api
[06:44] <axw> wallyworld: okey dokey. I'll look into that, thanks
[06:45] <axw> kinda what I figured, was hoping I'd overlooked something
[06:45] <wallyworld> nah :-(
[06:45] <wallyworld> all a bit messy
[07:05] <dimitern> we're using ErrorResults.Combine() now instead of OneError() ?!
[07:06] <dimitern> ok, only in a few cases it seems, otherwise it would've been *insane*
[07:13] <dimitern> fwereade just texted me they have a power cut and he'll come online when he can
[07:20] <voidspace> dimitern: is it correct that in EC2 you can have multiple NICs, but only one subnet per machine (even if you have multiple NICs)?
[07:23] <dimitern> voidspace, subnets in ec2 map 1:1 with AZs, so you definitely *can't* run an instance with multiple NICs attached to subnets in different AZs
[07:23] <dimitern> voidspace, it's unclear though if you can run an instance with multiple NICs bound to separate subnets in the same VPC and AZ
[07:24] <dimitern> voidspace, probably not, but it can be verified easily
[07:27] <voidspace> dimitern: ok - the network model document states that machines and subnets map 1:1 and you *can't* have multiple NICs bound to different subnets
[07:31] <dimitern> voidspace, we don't intend to allow this initially, yes
[07:31] <dimitern> voidspace, to simplify the implementation, but effectively a machine can end up in multiple spaces and subnets
[07:32] <dimitern> voidspace, so which subnet a machine is in is not the right question to ask, as NICs are bound to subnets, not machines directly
[07:32] <jam> dimitern: there was a recent bug that made me think https://bugs.launchpad.net/juju-core/+bug/1478660
[07:32] <mup> Bug #1478660: juju uses proxy to access bootstrap node <juju-core:Fix Committed by cherylj> <juju-core 1.24:In Progress by cherylj> <https://launchpad.net/bugs/1478660>
[07:32] <jam> we should probably be adding the space to the no-proxy list
[07:32] <jam> dimitern: ^ what do you think?
[07:33] <voidspace> dimitern: right, it's fine to say we don't support it - the doc implies it's an EC2 restriction and that machines map to subnets 1:1
[07:33] <voidspace> dimitern: I'll add a comment
[07:33] <dimitern> jam, is that what we want to do always?
[07:34] <dimitern> voidspace, cheers
[07:34] <jam> dimitern: I don't think you want to proxy for things that you consider on your local LAN do you ?
[07:34] <dimitern> jam, is this for MAAS or in general?
[07:34] <jam> dimitern: in general I'm thinking
[07:34] <dimitern> jam, trying to think of scenarios - AWS is different from MAAS for example
[07:34] <jam> dimitern: they mentioned working around wget, but ISTM that just fixing our wget is shortsighted
[07:35] <jam> dimitern: still, if you're in a space, it seems to define that you have direct access to other things in that space
[07:35] <jam> voidspace: I think the idea right now is that service endpoints map 1:1 to a space, not machines
[07:35] <dimitern> jam, that's right, yes it seems we should do what you suggest
[07:35] <dimitern> jam, I got confused by client-side proxies for a moment
[07:36] <jam> dimitern: so in general, I think we should avoid proxies for things that want to talk to the state server (consider debug-log, or any future file downloads, etc). It may be that we explicitly ignore proxy settings in our code
[07:36] <dimitern> jam, and that relates to voidspace's comment yesterday - *thou shalt always be able to connect to any state servers*
[07:36] <voidspace> jam: the network model docs state that for EC2 machines map to subnets 1:1 - so a service can only be on one space
[07:36] <voidspace> *in one space
[07:37] <voidspace> jam: as a machine can only be on one subnet (even with multiple NICs)
[07:38] <jam> voidspace: I do see that text, I haven't expiremented personally to know if it is true, though it might complicate (or maybe simplify) things.
[07:39] <dimitern> voidspace, you mean a machine, not service, right?
[07:39] <dimitern> voidspace, a service spans multiple units (machines in different subnets of the space)
[07:39] <voidspace> dimitern: well, you deploy services not machines (well you do both)
[07:40] <voidspace> dimitern: so the deploy command can only take one positive space for EC2
[07:40] <jam> dimitern: page 9 of Network Model Phase 1.1 says machines map to subnets 1:1 verbatim
[07:40] <voidspace> dimitern: a service can only be in one space *because* machines can only be on one subnet (i.e. one space)
[07:41] <jam> voidspace: dimitern: it should probably take as long as this discussion to bring up a machine, create 2 subnets in the same AZ, and see if you can attach 2 network interfaces from each subnet to it
[07:41] <voidspace> :-)
[07:41] <voidspace> probably longer for me, but it would be time well spent I think
[07:41]  * dimitern gets increasingly confused
[07:41] <jam> voidspace: I do think that if that constraint is true, we need to think carefully about the ramifications to the network model
[07:41] <dimitern> we need to chat about this at standup
[07:42] <dimitern> I'm trying to review a bunch of things and am distracted right now
[07:42] <jam> specifically, if you ever want to separate the ADMIN endpoint for MYSQL onto a separate space from the DB endpoint, then we need to know if that is actually possible.
[07:42] <voidspace> jam: the space model seems to only be *really* useful when you can have some of your services on multiple spaces
[07:42] <voidspace> jam: and you have firewalling between the spaces
[07:43] <jam> voidspace: well, it can be useful between services (postgres is only in the DB space, and WebApp is in a different space) with custom routing/firewalling
[07:43] <voidspace> right
[07:43] <voidspace> we need to do the custom routing
[07:43] <voidspace> fair enough
[07:43] <voidspace> and we also need to do custom routing for the state server
[07:44] <jam> so I thought for P1 we still had the flat space for Juju traffic.
[07:44] <voidspace> jam: you mean no firewalling?
[07:44] <jam> voidspace: we aren't directly controlling the firewall yet (relations != connections in all cases)
[07:45] <jam> voidspace: but I mean that being in *a* space means you are actually in 2 (the Juju meta space and the explicit one for the service)
[07:46] <voidspace> jam: "the Juju meta space" isn't something mentioned in the network doc
[07:46] <voidspace> jam: can all machines in every space route to each other through the meta space?
[07:47] <voidspace> as spaces are described as being "a security subdivision of a network" it seems that they only have any reason to exist if traffic between them is restricted / controlled (or am I wrong)?
[07:48] <voidspace> is the "meta space" just a consequence of having no routing restrictions - or is it (or will it be) something else (a specific set of routing rules)?
[07:50] <jam> voidspace: so I think it was a pragmatic decision in first phase to make sure everything can talk to the state server without requiring the server to have an address in every space.
[07:50] <jam> but it may have been in conversations and not captured in the doc
[07:50] <voidspace> right
[07:51] <jam> it certainly does get us away from strong security if we don't have binding
[07:51] <jam> (if your service always binds to all available interfaces, then having an interface on a globally routable space means you lost the security aspect)
[07:52] <voidspace> which is the raison d'etre for spaces to exist at all :-)
[07:55] <voidspace> jam: when I login to the AWS console and then navigate to EC2 I get a "Your service sign-up is almost complete!" message
[07:55] <voidspace> I've tried us-east-1 and us-west-2
[07:55] <voidspace> jam: could you verify it works for you? (sorry to be a pain)
[07:56] <voidspace> I can try from go-amz instead
[07:56] <jam> voidspace: trying to go in
[07:57] <voidspace> seems like I get the same response from all the AZs
[07:57] <jam> voidspace: I see a juju-env machine running in us-east-1
[07:57] <jam> m1.small
[07:57] <voidspace> ok, must be a problem with my account
[07:57] <jam> though that is via the master account, if you are using an IAM role
[07:57] <jam> voidspace: is it a personal account?
[07:57] <jam> or shared?
[07:57] <voidspace> I logged in with the wrong account first (and then signed out) - it maybe a cookie issue
[07:58] <voidspace> jam: it's my canonical account
[07:58] <jam> voidspace: interesting, your mfoord user in the shared account has password last used of 2014-11
[08:00] <voidspace> jam: odd, I get the same result from another browser too
[08:01] <voidspace> jam: gah, user error
[08:02] <voidspace> jam: I have a personal account with my canonical email address
[08:02] <voidspace> jam: I wasn't using the shared account
[08:11] <voidspace> jam: when launching an instance I can create multiple nics bound to different subnets (in the same AZ)
[08:11] <voidspace> dimitern: ^^^
[08:18] <dimitern> voidspace, I can't say off hand, but should be easy to verify by using the AWS CLI commands
[08:18] <dimitern> voidspace, or even the web UI
[08:18] <dimitern> TheMue, I've responded on your review, but I'm afraid I found even more issues missed earlier, ping me if anything is unclear
[08:19] <TheMue> dimitern: ah, great, thank you. just wanted to ping you that I added some questions/remarks. but the I found your mail about the sprint and currently answering it.
[08:20] <dimitern> TheMue, cheers
[08:22] <dimitern> axw, are you still around?
[08:22] <dimitern> wallyworld, or you?
[08:32] <axw> dimitern: I'm here, what's up?
[08:33] <dimitern> axw, I'm reviewing your RB2295 and found out we're now using things like storage.XXXResults similarly to apiserver/params.XXXResults with Error fields
[08:33] <dimitern> axw, but that's in the providers; wasn't clear at first, but I figured it out, sorry for the noise :)
[08:34] <axw> dimitern: well, this is the first place it's done AFAIK. I'm trying to enable bulk provider API calls, even though the current ones mostly don't support it
[08:34] <axw> dimitern: some do (DestroyVolumes for some), some don't (all CreateVolumes)
[08:35] <axw> dimitern: cool, no worries
[08:35] <dimitern> axw, we need this for sure - we can use it for ReleaseAddresses as well for example
[08:36] <axw> dimitern: you might be interested in the next branch I put up, which does retries for failed operations. the storage provisioner will include a scheduler for operations, with failed ones being put back on the schedule to retry at a later date
[08:36] <dimitern> axw, think about a few common cases there: retrying transient errors (how to make that easier to convey) as well as a few helpers on the results types that have errors to verify e.g. the number of results == number of args
[08:37] <dimitern> axw, nice! I'll definitely be interested in looking at that
[08:37] <axw> hm yes I suppose it should check those things
[08:37] <axw> I'm currently relying on the fact that it's all in the same process, so we *should* be able to rely on them doing the right thing
[08:38] <axw> but I could make it more pedantic
[08:39] <dimitern> might be worth it in the face of future extensions to the behavior/implementation
[08:40] <dimitern> axw, it seems a bit unwieldy how ([]error, error) returns are handled - a some common Combine() helper might be useful
[08:41] <axw> dimitern: that's a stop-gap. in a follow-up, the individual errors will be used to decide whether or not to reschedule, and they won't surface. a further follow-up will propagate the errors to status
[08:41] <axw> so you can see the provisioning error from the CLI
[08:41] <axw> I had it as one big branch, but it was >1200 LOC :)
[08:42] <dimitern> wow :)
[08:42] <dimitern> axw, ok, I'll follow the follow-ups then
[08:52] <axw> dimitern: thanks for the review
[08:53] <dimitern> axw, thanks for starting to solve the retrying in general for providers :)
[08:57] <voidspace> dimitern: I have verified it!
[08:57] <voidspace> dimitern: I was saying I *can* create an instance with multiple nics on different subnets
[08:59] <dimitern> voidspace, ah, I see
[09:00] <dimitern> voidspace, well that's AWS, in other clouds we'll have different constraints like this, OpenStack being an example of almost "all is allowed" sort of cloud
[09:02] <voidspace> TheMue: dooferlad: stdup?
[09:02] <TheMue> voidspace: omw, fetch a coffee
[09:02] <TheMue> fetched
[11:02] <perrito666> morning all
[11:06] <TheMue> heya perrito666
[11:09] <dimitern> perrito666, hey, my fellow OCR :)
[11:10]  * perrito666 feels something coming his way
[11:10] <dimitern> perrito666, I've left you the best review of all - william's final leadership one
[11:10]  * dimitern ducks
[11:10] <dimitern> :)
[11:11] <perrito666> dimitern: aren t you a sweetie
[11:11] <dimitern> perrito666, I'll buy you a beer on the next sprint hehe
[11:11] <perrito666> ill make some coffee before this
[11:19] <wwitzel3> ericsnow: ping
[11:56] <dimitern> dooferlad, I think the build errors you're getting might be due to the "type SpaceDoc spaceDoc" definition in export_test.go (or something else like this when only happens while running tests)
[11:59] <perrito666> dimitern: well it was the second time around most of these changes
[11:59] <perrito666> which made them a bit easier
[12:00] <dimitern> perrito666, I've been on some of the previous ones as well, but there are new things there as well
[12:00] <perrito666> dimitern: yep, but still much better than the first time
[12:00] <perrito666> :)
[12:01]  * dimitern found out this background music makes it a *lot* easier to go through reviews :) https://www.youtube.com/watch?v=exWNztpgfIw
[12:03] <perrito666> dimitern: sounds like it would make you shoot at the review at some points
[12:04] <dimitern> perrito666, it occasionally does, yes :)
[12:22] <dooferlad> dimitern: the code builds fine here. Very strange
[12:22] <dooferlad> dimitern: in fact I have 100% tests passing, and I have rebased on upstream so I should have identical code.
[12:26] <dooferlad> dimitern: maybe a go version thing? I am on 1.4.2
[12:26] <dimitern> dooferlad, I'm on 1.2.1 which is the same CI uses IIRC, I'll pull your branch and try it here
[12:30] <dooferlad> dimitern: thanks. I thought we had moved to 1.4.2. Guess not. Are we waiting for 1.5?
[12:30] <dimitern> dooferlad, we are
[12:30] <dimitern> dooferlad, but it's useful to have a mix of versions until then, just for such issues
[12:31] <voidspace> dooferlad: ping
[12:31] <dooferlad> voidspace: hi
[12:31] <voidspace> dooferlad: hey, you available to hangout?
[12:32] <dooferlad> voidspace: yea, I can come back to this.
[12:32] <voidspace> dooferlad: cool, stdup hangout?
[12:33] <dooferlad> sure
[12:38] <dimitern> mgz, ping
[12:56] <dimitern> dooferlad, btw while looking at the changes your branch introduced - https://github.com/juju/juju/compare/net-cli...dooferlad:net-cli-state-add-space I noticed the last change - removing Assert: isAliveDoc from Subnet.EnsureDead() - why is that?
[12:56] <dooferlad> dimitern: odd.
[12:56] <voidspace> dimitern: must spaces list be a bulk call?
[12:57] <dimitern> voidspace, I don't think so, but it should take filters
[12:57] <voidspace> dimitern: what do you mean by filters?
[12:57] <voidspace> dimitern: filtering output by name or something?
[12:58] <voidspace> dimitern: the CLI doesn't have filters (like that)
[12:58] <dimitern> voidspace, let me double-check the model
[12:58]  * voidspace too
[12:58] <dimitern> I might be thinking of subnet list
[12:59] <voidspace> dooferlad: the juju command is actually "space" rather than "spaces"
[12:59] <voidspace> dooferlad: so "space" seems more correct
[13:00] <voidspace> subnet list hasn't been done yet
[13:00] <dimitern> voidspace, no filters for space list
[13:00] <voidspace> so I can't just copy it
[13:00] <voidspace> dimitern: yeah
[13:01] <dimitern> voidspace, the --short argument is purely a CLI thing - we still get all the details from the API
[13:01] <voidspace> dimitern: ok
[13:01] <voidspace> dimitern: and what about format?
[13:01] <voidspace> dimitern: do we do that on the server?
[13:01] <voidspace> I'll find another list cli command and look at that
[13:02] <dimitern> voidspace, how about this? http://reviews.vapour.ws/r/1390/
[13:02] <dimitern> voidspace, the format is also a CLI thing
[13:02] <voidspace> dimitern: yeah, I meant the apiserver bit
[13:02] <voidspace> dimitern: thanks though, worth looking at
[13:03] <dimitern> voidspace, ah, yeah - no apiserver support for listing spaces, but it should just call Backing.AllSpaces
[13:04] <voidspace> dimitern: so if format, output and short are all handled on the client - ListSpaces takes no arguments
[13:05] <dimitern> dooferlad, please reintroduce that assert
[13:05] <dooferlad> dimitern: will do. Did you have any problems with go 1.2?
[13:05] <dimitern> voidspace, yeah
[13:06] <dimitern> dooferlad, tests are still running - so far a few failures which look like flakyness
[13:18] <mgz> dimitern: hey
[13:18] <dimitern> dooferlad, passed the cmd package where the build issue happened on the CI machine - no issues
[13:18] <dooferlad> dimitern: I thought the problem was in state.
[13:18] <dimitern> mgz, hey, I'm trying to analyze why this merge fails with such an odd error: http://juju-ci.vapour.ws:8080/job/github-merge-juju/4188/consoleFull
[13:18] <dooferlad> dimitern: you could "cd state; go test -c" to check for a compile error
[13:19] <dimitern> mgz, it's happening a few times now and both I and dooferlad get no errors when running tests with the same branch locally, I'm on 1.2.1, he's on 1.4.2
[13:19] <mgz> dimitern: that's not one I've seen before
[13:19] <dimitern> dooferlad, I know, but just in case it's some weird issue which *only happens* under load or when running the full suite..
[13:20] <dimitern> mgz, can you force the instance to stay after the tests fail, so we can get in and inspect it?
[13:24] <mgz> hm, I should just attatch the tarball as an artifact
[13:26] <mgz> ugh, that branhc adds more ConnSuite derived tests?
[13:27] <mgz> dimitern: I bet the problem is the export_test
[13:28] <dimitern> mgz, that's what I suspected, but there's no redefinition of that type there
[13:29] <mgz> I am surpised it worsk for you on 1.21 but not on the clean instance for the bot
[13:29] <dimitern> mgz, and since #testmain is involved, I strongly suspect it's actually due to the way we're running CLI tests (another possibility is a dirty GOPATH on the CI instance)
[13:30] <mgz> dimitern: try running `make check` and see if you get it?
[13:30] <dimitern> mgz, I did, it's running for a while now
[13:31] <dimitern> mgz, and there it is! I've reproduced it (in a different package, but that's due to suites running in parallel I guess)
[13:31] <dimitern> dooferlad, I've got a repro
[13:31] <dooferlad> dimitern: sweet!
[13:32] <alexisb> katco, are you in today?
[13:34] <katco> alexisb: i am :)
[13:39] <dimitern> dooferlad, now running go test ./... in cmd/juju to see if that triggers it
[13:41] <dimitern> incredibly annoying :(
[13:42] <dimitern> it's not that then trying cmd/jujud/
[13:44] <dimitern> dooferlad, I managed with go test -c in state/
[13:47] <katco> dimitern: perrito666: more input needed on this: http://reviews.vapour.ws/r/2199/
[13:47] <dimitern> katco, ack, will look shortly
[13:48] <dimitern> dooferlad, found a workaround
[13:49] <perrito666> katco: will look
[13:50] <dimitern> dooferlad, if you change "func (s *Space) Doc() spaceDoc { return s.doc }" to "func SpaceDoc(s *Space) spaceDoc { return s.doc }" (and the tests from space.Doc().X to state.SpaceDoc(space).X) it builds ok here
[13:50] <dimitern> dooferlad, amazingly it doesn't complain about spaceDoc not being exported, which I expected
[13:51] <dimitern> oh boy PowerShell
[13:51] <dimitern> gsamfira, ping :)
[13:52] <dimitern> perrito666, I'm with you on that one re PS
[13:53] <perrito666> dimitern: ?
[13:54] <dimitern> perrito666, about http://reviews.vapour.ws/r/2199/
[13:56] <dimitern> katco, replied, if somewhat unhelpfully I guess
[14:01] <dooferlad> dimitern: thanks. Just setting up a container to let me test in a clean environment before I try and merge again, (trusty + default go)
[14:02] <dimitern> dooferlad, +1
[14:06] <mup> Bug #1481366 opened: leader-get may fail in -departed hooks <juju-core:New> <https://launchpad.net/bugs/1481366>
[14:08] <katco> alexisb: hey i'm out tomorrow
[14:09] <alexisb> katco, ok np
[14:09] <alexisb> I need to catch pat before she goes on vacation, so just decline the call
[14:10] <katco> alexisb: k will do
[14:10] <katco> alexisb: just lemme know what you need from me
[14:28] <perrito666> katco: that patch is still a hughe powershell blob, I have no idea what is going on inside
[14:30] <mup> Bug #1481368 opened: Deploy hangs: jujud-machine-0 upstart process running but juju status shows it down <canonical-bootstack> <deploy> <state-server> <juju-core:Triaged> <https://launchpad.net/bugs/1481368>
[16:03] <alexisb> perrito666, ping
[16:18] <perrito666> alexisb: pong
[16:18] <perrito666> sorry was having lunch
[16:18] <alexisb> perrito666, no worries
[16:18] <alexisb> I saw https://launchpad.net/bugs/1481368 come in on the proposed 1.24.4
[16:18] <mup> Bug #1481368: Deploy hangs: jujud-machine-0 upstart process running but juju status shows it down <canonical-bootstack> <deploy> <state-server> <juju-core:Triaged> <https://launchpad.net/bugs/1481368>
[16:18] <alexisb> looks to potentially be status related
[16:18]  * perrito666 checks
[16:19] <alexisb> was curious on your perspective
[16:22] <perrito666> alexisb: mm, I think it might be something else being masked by status
[16:30] <alexisb> perrito666, katco, cherylj, wwitzel3, ericsnow, natefinch if someone has free cycles https://launchpad.net/bugs/1481368 needs to be worked
[16:30] <mup> Bug #1481368: Deploy hangs: jujud-machine-0 upstart process running but juju status shows it down <canonical-bootstack> <deploy> <state-server> <juju-core:Triaged> <https://launchpad.net/bugs/1481368>
[16:30] <katco> alexisb: might be possible later. today is moonstone's catchup+planning day
[16:31] <katco> alexisb: since i was out on fri.
[16:31] <alexisb> katco, ack
[16:35] <cherylj> alexisb: I can take a look in a few
[16:38] <alexisb> cherylj, thank you as always
[19:23] <sinzui> cherylj: I am trying to force CI to retest your commit to master.
[19:24] <cherylj> sinzui: for bug 1480298?
[19:24] <mup> Bug #1480298: unknown object type "Charms" <blocker> <ci> <compatibility> <regression> <juju-core:Fix Committed by cherylj> <https://launchpad.net/bugs/1480298>
[19:26] <sinzui> cherylj: yes. the branch failed because of a logging test that may have been intermittent
[19:26] <cherylj> ah, ok
[20:31] <mbruzek> Hello core devs.  Someone is setting up a network for a conference and wants to know all the ports to open to get Juju to work.  I know about 22 and 37017 and 38017, are there any other ones that I am forgetting?
[20:31] <mbruzek> when I do a google search for juju ports I only get the open ports for charms.
[20:37] <katco> wwitzel3: ericsnow: we'll delay the remainder of planning until thurs. do you feel like you have a good idea of what to work on tomorrow?
[20:37] <ericsnow> katco: yep
[20:37] <ericsnow> katco: I also did my best to flesh out the cards we have
[20:37] <katco> ericsnow: awesome ty
[20:42] <mbruzek> The default port numbers for api-port, state-port, and storage-port are 17071, 37017, and 8040 respectively.
[20:56] <wwitzel3> katco: yep, sounds good
[20:56] <wwitzel3> ericsnow: thanks :)
[21:16] <perrito666> menn0: ping
[21:19] <menn0> perrito666: sorry, in standup
[21:42] <perrito666> menn0: np, just ping me when you have a moment plz
[22:06] <menn0> perrito666: ok i'm done. what's up/
[22:06] <perrito666> you dont seem happy to see me :p
[22:07] <perrito666> ill go priv so I have proper logs to read after
[22:16] <mup> Bug #1481500 opened: automatic devel streams selection for beta releases <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1481500>
[23:00] <perrito666> aghh my fix depends on fwereade patch
[23:14] <alexisb> perrito666, this one:   https://github.com/juju/juju/pull/2909
[23:14] <perrito666> yeah, I am trying to make a patch for it
[23:17] <perrito666> alexisb: mm, it seems he did not fwport all of it, ill propose a patch tailored to master