wallyworldaxw: anastasiamac: may be delayed for standup, will ping00:09
menn0thumper: another trivial PR, as discussed via email http://reviews.vapour.ws/r/380300:10
* thumper looks00:11
axwmenn0: what magic did you use to get RB to recognise you renamed a file, rather than delete/add?00:13
menn0axw: I did nothing00:14
menn0axw: I think if the file is exactly the same and only moved RB does the right thing00:15
menn0axw: if you move it and then change it, RB gets confused00:15
menn0axw: that's my guess anyway00:15
axwmenn0: yeah, sounds plausible00:15
menn0axw: this is the first time I've seen RB do that too00:15
menn0axw: that PR is just a single "git mv"00:16
* axw nods00:16
davecheneythumper: cherylj sooo, master and 1.25 are blocked00:32
davecheneyyet my JFDI is third in the queue, hmmmm00:32
thumperlanding bot does non master/12.5 branches too remember00:32
davecheneyfor review, https://github.com/juju/juju/pull/436100:42
wallyworldaxw: anastasiamac: free now if you are01:06
axwwallyworld: coming01:06
=== ses is now known as Guest22318
thumpercherylj: still around?02:39
cheryljthumper: yeah, what's up?02:40
thumpercherylj: davecheney suggested that we have a quick hangout to sync about client side api error retries02:40
davecheneymeet in the standup hangout ?02:41
cheryljthumper: sure, give me a minute02:41
thumperdavecheney: ack02:42
axwanastasiamac: FYI, I can bootstrap/destroy/bootstrap lxd on cloud-credentials without any problems02:55
anastasiamacaxw: i was afraid u'd say that...02:55
anastasiamaci'll dismiss it as "it's just me" :D02:56
axwwallyworld: did we discuss dropping the no-args variant of "juju switch"? currently "juju switch" will show the active model name, which feels like a weird command to have to use03:23
axwwallyworld: IMO we should have a more obvious command specifically for that purpose03:24
axwwallyworld: "juju current-model", or something like that03:24
axwmaybe just "juju current"03:25
wallyworldaxw: that has come up before, with external stakeholders, and it had traction at one stage. i do agree but had thought we had reverted to accepting juju switch with no args as showing what's current. i'll ask around03:31
anastasiamacwallyworld: axw: don't we show "current" in list- commands?03:32
anastasiamacspec says mark them with *03:32
axwanastasiamac: we do, but we shouldn't have to make an API call to show the current controller/model03:32
axwanastasiamac: which the list commands require03:32
wallyworldlist-controllers is not an api call03:32
axwwallyworld: list-models is though03:32
axwwallyworld: "juju current" would print the current model, not controller03:33
wallyworldjust being clear wrt controllers to avoid potential confusion03:33
axwok, sure03:33
anastasiamacwallyworld: axw: m putting the card for injecting store into command off in favour of list-controllers...03:37
anastasiamacwill get back to it when I (we/anyone) get a chance...03:37
axwanastasiamac: sure. I was thinking I *might* do that one while I'm working on switch03:37
wallyworldok. i think you'll need placeholders for some columns03:37
anastasiamacaxw: sounds awesome - it'll b a fun one to do \o/03:39
thumperaxw: +1 on removing no args juju switch03:45
natefinch-afknick natefinch03:46
=== natefinch-afk is now known as natefinch
natefinchso.... what's the command to see what controller my commands will be working against?03:47
axwnatefinch: undecided03:48
natefinchaxw: ok :)03:48
axwnatefinch: you'll be able to see with "juju list-controllers" which are available, and which is active03:48
axwnatefinch: what's undecided is whether there'll be another command to show the current controller/model03:48
axwone htat's not "juju switch"03:49
natefinchdefinitely juju switch was a terribly unintuitive way of seeing what environment you were on03:49
natefinchericsnow: thanks for the fixes to those bugs. I was just running into that04:03
ericsnownatefinch: yep :)04:03
natefinchericsnow: lemme see if I can review it real quick so we can get it in04:03
natefinchericsnow:  reviewed... a few things to think about, but I think it can land as-is (maybe remove one unneeded log statement)04:09
ericsnownatefinch: thanks04:09
natefinchericsnow: ship it!04:26
natefinchericsnow: nvm, I see it's already been shipped.04:27
ericsnownatefinch: :)04:27
axwwallyworld anastasiamac: just to confirm your changes don't involve adding models to ControllerStore, right?05:03
wallyworldaxw: no, i don't want to do that, i think controllers.yaml is judt for controllersd05:03
wallyworldaxw: but i'm having an issue where i now can't map from model->controller because the info is missing from cache.yaml05:04
axwwallyworld: right... but ControllerStore will have methods for accessing model info too. because they're related to controllers05:04
wallyworldi may need a temp solution05:04
axwwallyworld: what info is that?05:05
wallyworldaxw: given a model name, i need to know the controller name that hosts that model05:05
wallyworldwe used to get that from cache.yaml05:05
axwwallyworld: you should be using the UUIDs I think?05:07
axwwallyworld: is your branch on github yet? can I look?05:08
wallyworldaxw: yes, that's what used to happen under the covers. the cli knows the name of it's model; from there it looked up the model uuid, and then got the controller uuid, and from there the api info05:08
wallyworldbut now we don't store controller or model stuff in cache.yaml05:08
wallyworldwe only have controller by name from controller.yaml05:09
wallyworldmy branch is very much wip, lots of stuff commented out05:09
wallyworldi may have to go back to storing controller and model stuff in cache.yaml for now05:10
wallyworldbut removing that allowed the code to be  lot cleaner05:10
axwwallyworld: I think it's necessary until we have a model store05:11
wallyworldsadly so05:11
axwwallyworld: I'll work on that now, since it's needed for switching05:12
wallyworldthe code to persist controller stuff is much cleaner without having to cater for both cache.yaml and controller.yaml05:12
wallyworldaxw: at least i'll remove the bootstrap config stuff etc05:12
wallyworldor try to, until i hot the next roadblock05:13
axwanastasiamac wallyworld: any objections to the name jujuclient.ClientStore as an amalgamation of ControllerStore, ModelStore, etc.?05:13
axwwallyworld: SGTM05:13
wallyworldnope, sounds good05:13
wallyworldmy branch is all f*cked up, got to replace stuff back to how it was, sigh05:13
anastasiamacaxw: r we likely to have other stores in jujuclient?05:52
axwanastasiamac: accounts05:52
axwanastasiamac: not sure if there's anything else05:53
anastasiamacaxw: so ClientStore is for controllers and models; and AccountStore for accounts?05:53
axwanastasiamac: ClientStore will be for all of them05:53
axwanastasiamac: but you can still get specific ones05:54
axwanastasiamac: i.e. ClientStore is just the combination of all the others05:54
anastasiamacaxw: ClientStore sounds great then \o/05:55
axwwallyworld: also need accounts.yaml before we can get rid of cache.yaml, because that's where user/pass is06:07
axwI suppose I'll do that at the same time/directly after06:07
wallyworldaxw: exactly, so i'm adding todos around where we'd use accounts.yaml06:11
wallyworldit's all a bit of a mess atm06:11
wallyworldaxw: luckily api-info, api-endpoints commands are obsolete so that's a whole world of migration pain i can avoid \o/06:32
axwwallyworld: really? what are the alternatives?06:33
wallyworldaxw: i need to check the specs, i think we'll work it into the list-controllers cli or something like that06:34
axwwallyworld: that would make sense. probably just have it in the YAML for scripts to pull out06:34
wallyworldmore or less06:34
axwwallyworld: I suspect we're going to have a lot of overlap. when are you likely to propose?08:27
wallyworldaxw: i have a shittonne of tests to fix, just got it compiling. i have introduced a temporary ControllerModel struct to hold controller and model uuid stored in the existing cache.yaml file08:28
axwwallyworld: mmkay08:28
wallyworldthe ControllerModle struct is used in place of the old APIEndpoints struct which contained addresses etc as well as the model and controller uuid08:29
wallyworldso it's a way of retaining the current recording of association between controller and model using the existing files08:29
wallyworlddoes that make sense?08:30
axwwallyworld: that's just temporary tho? what's the long term plan?08:30
wallyworldto use the stuff you're working on08:30
axwwallyworld: I was planning to pass controller name, model name, and store08:30
axwwallyworld: to NewAPI... functions08:31
wallyworldsometimes we only have the uuid, but i think that will go away08:31
wallyworldaxw: quick chat in standup hangout?08:32
axwwallyworld: sorry was afk, one minute08:44
=== blahdeblah_ is now known as blahdeblah
voidspacedimitern: did you see the maas-spaces CI run(s)?09:26
voidspacedimitern: still a couple of errors " gomaasapi: got error back from server: 400 BAD REQUEST ({"distro_series": ["'trusty' is not a valid distro_series]"09:26
voidspacedimitern: a bunch of known issues that aren't our fault09:26
voidspacedimitern: plus another maas one, unrecognised architecture for the centos test09:27
dimiternvoidspace, yeah, it's getting close09:27
dimiternvoidspace, I've merged latest master and set it to land btw09:27
dimiternvoidspace, that should clear the know issues already fixed on master09:28
dimiternvoidspace, and .. oh joy :/ another discovery from yesterday: https://bugs.launchpad.net/maas/+bug/154396809:36
mupBug #1543968: MAAS 1.9.0 allows non-unique space names and shows no space id in a subnet <MAAS:New> <https://launchpad.net/bugs/1543968>09:36
dimiterndooferlad, you'd love that I'm sure ^^ :)09:39
dooferladdimitern: yea...09:40
voidspacedimitern: cool about master09:40
voidspacedimitern: to make it worse, when they reference spaces (for example on subnets) - they do it by *name* not by id09:41
dimiternmaas is making really hard for juju to accept its imposed spaces management09:41
voidspacedimitern: so if we want to use provider id we have to look them up by name to find the id09:41
voidspacedimitern: and if the names are duplicated that's then impossible :-)09:42
dooferladdimitern: I think we just have to say that we can't support spaces on the current MAAS.09:42
dimiternvoidspace, nope, that's not unambiguous - we need to list all spaces and get the ids from there09:42
dimiterndooferlad, only if ..09:42
voidspacedimitern: unless they have two spaces with the same name and a different id as your bug report says09:42
voidspacedimitern: so if it's space "foo", which "foo" is it?09:43
dimiternvoidspace, when you do discovery do you list the spaces or only subnets?09:43
voidspacedimitern: list spaces which have all subnets09:43
dimiternvoidspace, so you then have all ids and names - duplicates or not09:43
voidspacedimitern: but when we look up the links on an interface, the referenced subnet tells us the space *name*09:44
dooferladdimitern: what else can we do? It is broken. If they fix this and change the restriction on whitespace in a point release then we can just use a minimum MAAS version of 1.9.109:44
voidspacedimitern: and this is in provider code, so we can't just ask state09:44
dooferladdimitern: without fixing your bug we can't use names that match their names.09:44
voidspacedimitern: we could list all spaces and subnets and get the id from there09:44
dimiternvoidspace, that's unavoidable I'm afraid09:45
dimiternwe can only do damage control atm09:45
dooferladdimitern, voidspace: We can't work around this in a user friendly way. We haven't released yet. Isn't it reasonable to get MAAS fixed and require the fixed version?09:45
voidspacedooferlad: sounds reasonable to me09:46
dimiternvoidspace, dooferlad, I bet it will still land on us eventually09:46
voidspacedooferlad: their space naming model doesn't match what we need and I'm sure it's an oversight on their part09:46
dimiterni.e. "you are not talking - why did you discover this that late" ?09:46
dooferladdimitern: we are talking. It is a bug. We didn't notice it because it isn't our job to validate MAAS.09:47
dimiterndooferlad, I know, but that's what will come to - all I'm saying09:47
dimiterndooferlad, voidspace, which means our approach with renaming spaces on discovery was the only thing we can do now09:48
dooferladdimitern: if we take that attitude we are screwed anyway. We are better off being positive. We found the problem before any Juju + MAAS deployment suffered and it can be fixed before that point.09:48
voidspacedooferlad: yep, +1 to that09:49
dimiternlet's chat in 10m09:49
dooferladdimitern: +109:49
dooferlad(no, not 11 minutes)09:49
dimiternI think the issue stems from the attitude "we don't care how you set up your spaces or name them - you're the admin, you should know (no matter there's juju to care about)"09:51
dimiternvoidspace, dooferlad, I've rebased https://github.com/juju/juju/pull/4354 after the merge btw - still needs a review11:29
voidspacedimitern: ok12:11
dimiternvoidspace, dooferlad, I hate to be a pest, but did you had a chance to look at that PR?12:51
voidspacedimitern: I'm looking at it now12:52
dimiternvoidspace, tyvm!12:53
dimiternvoidspace, btw at least I found maas does not allow deleting a space a subnet is using: this: http://paste.ubuntu.com/15008282/12:55
voidspacedimitern: right, I thought that was the case12:56
voidspacedimitern: good12:56
dimiternvoidspace, haha! see the comment in bug 1543968: Critical for the lack of uniqueness on space names. That's close to unforgivable12:57
mupBug #1543968: MAAS 1.9.0 allows non-unique space names and shows no space id in a subnet <MAAS:Triaged> <https://launchpad.net/bugs/1543968>12:57
dimiterndooferlad, ^^12:57
voidspacedimitern: yeah, oops...12:58
voidspacedimitern: the basic changes all look sound13:07
voidspaceplus the tests13:07
dimiternvoidspace, awesome, thanks!13:07
voidspacedimitern: lots of "tinkering" with the code makes the diff harder to read (moving stuff around without semantic changes)13:07
voidspacedimitern: nearly at the end13:07
voidspacedimitern: alright, LGTM13:08
dimiternvoidspace, yeah, sorry about that churn, but at least makes the tests easier to follow I believe13:13
natefinchericsnow, katco: trivial patch for renaming comment to description - http://reviews.vapour.ws/r/3813/14:54
ericsnownatefinch: ship-it14:59
natefinchericsnow: thanks15:00
natefinchfwereade__: we have a card to fire the upgrade-charm hook when a new resource is uploaded... how do we do that?15:22
=== akhavr1 is now known as akhavr
perrito666omg unable to determine the series is like a bad dream that keeps returning15:47
alexisbwake up perrito666, wake up!15:48
perrito666honestly, how can we be panicking on the latest stable version of ubuntu, it is insane15:48
natefinchgah, we talked about that in oakland... we gotta get rid of that stupid line in the version stuff15:49
voidspacedimitern: ping15:57
dimiternvoidspace, pong15:57
voidspacedimitern: just to confirm with you - at the moment we are using MAAS space *name* as the provider id15:57
voidspacedimitern: (see maasEnviron.subnetFromJson)15:57
voidspacedimitern: in fact we never call the spaces api directly - we fetch all subnets and build the spaces information from the subnets (because we only care about spaces that actually have subnets)15:58
dimiternvoidspace, yeah, we need to fix this soon15:58
voidspacedimitern: and the subnets api doessn't give us a space id - only the name15:58
dimiternvoidspace, we're already using provider ids in acquireNode though15:58
dimiternvoidspace, yeah, we need to call spaces read in ListSpaces15:59
voidspacedimitern: where does that id come from?15:59
voidspacedimitern: for the endpoint bindings for acquireNode ?16:00
voidspacedimitern: if we take it from the provider id from space in *state* then you have a name16:00
dimiternvoidspace, yeah16:00
dimiternvoidspace, I know :)16:00
dimiternvoidspace, but at least we pass it correctly16:00
dimiternvoidspace, to acquireNode, so once we fix what we store in state, we'll be a step closer16:01
voidspacedimitern: you mean it's currently broken16:01
voidspacedimitern: so a maasInstance is a created with a maasObject representing the node16:06
voidspacedimitern: if the instance needs to call an api method not on the node that may not be possible16:07
voidspacedimitern: I may need to change the way the instance is created16:07
voidspacedimitern: just checking if I can get back to the client from the maasObject I have16:07
dimiternvoidspace, sorry, in a call - will get back to you soon16:07
mbruzekHas anyone here bootstrapped a xenial image?  I am getting a juju error on amazon about the nonce.txt file not being found, and it aborts my bootstrap: http://paste.ubuntu.com/15009092/16:09
natefinchdimitern: we're trying to look into how the upgrade-charm hook gets fired... we want to have that hook fired when we upload a new resource for a service... it looks like that means we should change the uniter's remotewatcher to watch for resources as well?16:11
natefinch(when you're done your call)16:12
mbruzeknatefinch: Have you ever seen this nonce.txt error ?16:16
natefinchmbruzek: hmm.... it definitely sounds familiar, though not something I've experienced personally16:18
natefinchmbruzek: that's supposed to be created by our cloudinit script16:19
katcombruzek: isn't that created when you do --upload-tools ?16:20
katcoor am i remembering something completely different...16:20
mbruzeknatefinch: katco: Yeah it probably is, the cpc team said this was a core issue, but I can ask them again16:21
dooferladdimitern, voidspace: one failure on the latest run: http://reports.vapour.ws/releases/3594/job/run-unit-tests-trusty-ppc64el/attempt/456316:22
dooferladallwatcher_internal_test.go:844: TestStateWatcherTwoModels.pN47_github_com_juju_juju_state.allWatcherStateSuite16:22
dimiterndooferlad, voidspace, yay!16:23
dimiternnatefinch, hey16:34
dimiternnatefinch, so there's definitely a need for a watcher for resources, like for config settings etc.16:35
katcoericsnow: ^^^16:36
dimiternnatefinch, depending on how the resources of a service are stored in state, it might be a simple notify watcher16:36
dimiternnatefinch, katco, ericsnow, however, it's been *some* time since I was around the uniter code, so where those changes need to go I'm not sure - fwereade__  should be a better source16:37
dimiterncherylj, ping16:37
* ericsnow girds himself to enter the labyrinth16:38
cheryljdimitern: pong.  in a standup so responses will be slow16:38
dimiterncherylj, np, I just had a chat with alexisb about the state of maas-spaces16:39
dimiterncherylj, and it looks like with the yesterday's changes we're down to 1 failure now (ppc64), and 2 CI issues causing container-networking and aws-deploy-xenial to fail16:40
dimiterncherylj, so I suggested to wait for another run with today's changes and if it's not worse off tomorrow - do the merge16:40
dimiterncherylj, since it looks like our best chance this week16:40
dimiternvoidspace, dooferlad ^^16:41
dimiterncherylj, if you think that's acceptable, we can do it tomorrow16:41
dimiternvoidspace, btw can you have a look at that TestLoginsDuringUpgrade failure btw16:42
voidspacedimitern: where?16:42
dimiternvoidspace, it's flaky and connected to spaces discovery16:42
voidspacedimitern: ah, ok16:42
dimiternvoidspace, in cmd/juju somewhere.. let me have a look16:42
cheryljdimitern: that's good news.  I know there's one fix I need to get into master16:42
voidspacedimitern: if it gets a login failure it probably needs to wait and retry16:42
cheryljdimitern: and I'll probably want your review on it :)16:42
voidspacedimitern: as if discovery hasn't yet completed it will block temporarily16:42
dimiterncherylj, awesome! sure - I'll have a look16:42
voidspacedimitern: either that, or the test can patch discovery to complete immediately16:43
dimiternvoidspace, I tried both of those suggestions, up to the point of patching the worker creation16:43
voidspacedimitern: well, it was worker creation I was suggesting patching16:44
voidspacedimitern: to return a dummy worker and a closed channel16:44
dimiternvoidspace, but the test itself is a bit poorly written - it assumes that if it patches the upgrade steps block, it should be able to login almost immediately16:44
voidspacedimitern: I don't understand that, I'd have to look at the test16:45
voidspacedimitern: I'll do it after this16:45
voidspacedimitern: so, another question - the maasInstance can't call the spaces api method because it only has a node maasObject16:45
voidspacedimitern: and you can't go back from a node object to the client16:45
voidspacedimitern: so a maasInstance will need either a reference to the maas client or to the environ itself16:46
voidspacedimitern: which do you prefer?16:46
voidspacedimitern: a maas instance having a reference to the environ (the provider substrate) seems reasonable16:46
dimiternvoidspace, it's there: ./featuretests/upgrade_test.go:86:func (s *upgradeSuite) TestLoginsDuringUpgrade(c *gc.C) {16:46
voidspacedimitern: thanks16:47
dimiternvoidspace, ah, let me think for a sec..16:47
dooferladdimitern, voidspace: have made progress but am going to call it a day. If I get the urge I will do more hacking later, but I think I have at least solved my current problems.16:48
dimiterndooferlad, sure, get some rest :)16:49
dooferladdimitern: thanks. Hope you get some too at some point!16:49
dimiternvoidspace, so if you have an instance of maasEnviron, you can get the client from there16:49
natefinchericsnow, katco: I think making a new watcher shouldn't be a big deal.  We can model it after the unitassigner, which works much the same way... just fires an event when there's a new item in a specific collection16:49
voidspacedimitern: right16:49
dimiterndooferlad, :) ta16:50
voidspacedimitern: the maasInstance doesn't have that - my suggestion is to add it16:50
cheryljdimitern: http://reviews.vapour.ws/r/3816/16:50
voidspacedooferlad: o/16:50
natefinchericsnow, katco: also, unitassigner is very easy to grep for.  The watcher created in state/watcher.go  WatchForUnitAssignment16:50
katconatefinch: that may be so. i think we should have a plan and then query wallyworld_, axw for validity16:51
natefinchkatco: sounds like a good idea'16:51
dimiternvoidspace, I've tried that before and I had to change quite a lot of code and tests16:51
dimiterncherylj, will have a look shortly16:51
katconatefinch: ericsnow: (or fwereade__ if he's available)16:51
cheryljthanks, dimitern!16:51
ericsnowkatco: agreed16:52
voidspacedimitern: it doesn't need to be set, it can be nil - so it shouldn't need to change any tests16:52
voidspacedimitern: except new tests that *use* it16:52
dimiternvoidspace, yeah I suppose - give it a try16:53
voidspacedimitern: ok, cool - thanks16:53
dimiternvoidspace, it will be easier to implement a helper taking *MAASObject and extracting the information from there16:53
voidspacedimitern: you can't get there from an arbitrary *MAASObject16:54
dimiternvoidspace, like I did for maasObjectNetworkInterfaces fwiw16:54
voidspacedimitern: oh, I see - to actually get the spaces16:54
dimiternvoidspace, yeah - the parsing16:54
voidspacedimitern: I was thinking of implementing it on the environ, because we'll need it there anyway - and then have the instance just call the environ method16:54
dimiternvoidspace, as for getting it - sure, with the client.GetSubObject("spaces") I guess16:54
dimiternvoidspace, also works, yeah - I'd leave you to it then :)16:55
voidspacedimitern: not if the MAASObject represents a node - which is how the instance is created16:55
dimiterncherylj, ah, fwiw we have a better solution in progress for selecting the correct controller addresses and mongo peers16:56
cheryljdimitern: does it happen at bootstrap?16:57
dimiterncherylj, but it will get improved in steps16:57
dimiterncherylj, right after the node boots as one of the first few things the MA will do16:57
cheryljdimitern: it's good to know, but we need something to fix CI failures we're seeing now :)16:58
dimiterncherylj, yeah, sure - just a heads up :)16:58
cheryljthanks :)16:58
dimiterncherylj, ship it16:59
cheryljthanks, dimitern!16:59
dimitern:) np16:59
dimiternok folks, eod of me17:00
mupBug #1544158 opened: add explicit unit tests for network.MergedAddresses <juju-core:Triaged by cherylj> <https://launchpad.net/bugs/1544158>17:10
cheryljehmagerd scp'ing to private fileshare is so slow17:21
perrito666cherylj: off course it is, for some reason compunting never tried to solve the issue of sharing files decently17:25
* perrito666 found a supplier that will deliver hardware replacement to him on the day... I have never felt more firstworldish17:26
tych0cherylj: do i need to have anyone's approval to merge https://github.com/juju/juju/pull/4355 ?17:48
cheryljericsnow, natefinch can one of you guys review tych0's PR?  ^^17:51
ericsnowcherylj: I'll take a look17:51
katcotych0: you know about the whole $$merge$$ thing right?17:53
ericsnowcherylj, tych0: this one? http://reviews.vapour.ws/r/380017:53
tych0katco: yeah, but i don't know about what the rules are about when i can merge and can't :)17:54
tych0ericsnow: yes, at least the numbers match up :)17:54
katcotych0: just need a +1 on the reviews.vapour.ws site, and then you can do a $$merge$$ :)17:54
tych0katco: right. i don't have a +1 yet :(17:54
cheryljtych0: have you tried building on a clean wily system?  That will let you know if there will be build failures in CI17:54
tych0cherylj: i have not17:55
tych0i just deleted gosexy and built17:55
tych0and it worked17:55
ericsnowtych0: LGTM with one thing to fix17:57
tych0ericsnow: ah, there isn't an implementation of it17:59
tych0ericsnow: there's a lot of those stubs that are unimplemented actually17:59
ericsnowtych0: oh, I bet we are embedding the interface (if so you can drop that review comment)18:00
tych0ericsnow: ok. i just clicked drop. safe to $$merge$$ now?18:00
ericsnowtych0: yep18:04
tych0cool, thanks18:04
bogdanteleagaanybody here using xenial?19:25
jcastroxenial here19:59
=== akhavr1 is now known as akhavr
katcoericsnow: whatcha working on?20:20
katconatefinch: how's your card coming? anything i can do to help?20:21
ericsnowkatco: oops, forgot to grab the card20:21
katcoericsnow: np, why i asked :)20:21
natefinchkatco: lotta busywork writing tests.... the functionality is all there, just writing out a million struct literals for tests is a pain (since this thing needs a list of resources for the service and then a list for each unit)20:29
natefinchkatco: getting close though20:29
katconatefinch: yeah, understand that is a pain =/20:30
katconatefinch: still think you'll have it done today? hopefully before demo walkthrough?20:30
natefinchkatco: definitely by EOD, but possibly not by demo walkthrough.  I can certainly demo it as-is, it's just the tests left to do20:31
katconatefinch: cool, i don't think that's a huge deal. still have till friday to clean up demo, so it's fine if that 1 aspect is working20:32
katconatefinch: thx for the update20:32
natefinchgah... I don't know what is up with list_charm_resource.go and it's test file... but git really doesn't like rebasing them20:48
katconatefinch: meeting time21:02
perrito666you know what is funnier? refactring those kind of tests :p21:16
tych0hi cherylj, do i need to do anything to trigger the CI here? http://reports.vapour.ws/releases#lxd-container-type21:20
tych0looks like it hasn't run after my last commit to lxd-container-type21:20
cheryljtych0: it may take several hours as branches are tested one at a time21:21
tych0ah, ok21:22
alexisbwallyworld_, non urgent ping when you are in21:36
=== akhavr1 is now known as akhavr
=== _thumper_ is now known as thumper
marcoceppiin alpha2, do I still need to use an environments.yaml?21:54
marcoceppiI ran init and it create .local/share/juju, etc21:55
marcoceppibut if I try to create-model after "bootstrapping" I get some odd errors21:55
=== natefinch is now known as natefinch-afk
perrito666marcoceppi: oh, can you pastebin it?21:59
marcoceppiperrito666: http://paste.ubuntu.com/15011429/22:01
rick_h___marcoceppi: create model requires passing a yaml -c option currently for the auth tokens and such to use22:02
rick_h___marcoceppi: the idea being you can change the credentials used for different models22:02
rick_h___marcoceppi: we've got a request in to wallyworld_ to have it default sanely to the ones used to bootstrap/etc22:02
rick_h___marcoceppi: but I don't know that's hit yet22:02
marcoceppirick_h___: so this goes away when credentials/clouds are the way to roll out instead of environments.yaml ?22:02
rick_h___marcoceppi: yes22:02
rick_h___marcoceppi: but it will turn into an option22:03
perrito666marcoceppi: checking22:03
marcoceppirick_h___: cool22:03
* marcoceppi tries22:03
rick_h___marcoceppi: so for now, create a 'aws.yaml' with the settings it's fussing about and pass iot into create-model with a -c flag22:03
* wallyworld_ in meeting, will read backscroll in a bit22:03
* marcoceppi tries22:03
perrito666marcoceppi: well those errors are incredibly unhelpful22:04
marcoceppirick_h___ perrito666 weee22:05
rick_h___marcoceppi: woot22:06
marcoceppirick_h___: I got tripped up22:06
marcoceppirick_h___: because I was doing -c /path/to/file22:06
marcoceppibut that was not the right thing22:06
marcoceppiand I was about to make :( at you all22:06
marcoceppibut then I checked myself22:06
marcoceppiprior to wrecking myself22:06
marcoceppiand I created a model22:06
marcoceppiit's glorious22:06
rick_h___marcoceppi: good to hear22:07
marcoceppirick_h___: will nu gui see these models?22:07
rick_h___marcoceppi: yes, juju deploy the gui into the admin/first model22:08
rick_h___marcoceppi: and it'll see them, list the models, and you can switch between them22:08
rick_h___marcoceppi: I've been using that for demos recently22:08
marcoceppiit was totally worth installing golang on this computer22:08
rick_h___marcoceppi: :)22:08
perrito666marcoceppi: it is always worth to install golang ;)22:08
=== blahdeblah_ is now known as blahdeblah
marcoceppiI really wanted to just get a new svg.juju.solutions out but I kind of got sidetracked22:09
marcoceppiMakyo: you around?22:22
rick_h___marcoceppi: they're just coming back from team dinner tonight at the sprint22:33
rick_h___marcoceppi: I'd not count on it, maybe email instead22:33
marcoceppirick_h___: no worries, I got it sorted22:33
marcoceppirick_h___: http://svg.juju.solutions/?bundle-file=https://raw.githubusercontent.com/whitmo/bundle-kubernetes/master/bundles.yaml22:33
rick_h___ah cool22:33
axwkatco: sorry I didn't respond to the invite, I was asleep: )22:51
rick_h___marcoceppi: sexy22:52
katcoaxw: no worries at all; you were optional22:54
perrito666thats a cruel thing to say to axw22:56
perrito666you are so optional mate22:57
axwheh :)22:57
axwjob title: superfluous22:57
axwanastasiamac: accounts.yaml marshal/unmarshal is assigned to you; ok if I assign to myself?23:01
anastasiamacaxw: yes but i was going tos tart on it today23:01
anastasiamacaxw: i have list- and show- proposed23:01
anastasiamacbut want to clean it a bit today too23:01
axwanastasiamac: only reason I was going to look at it was to complete what we were talking about in mini-meeting yesterday23:02
axwanastasiamac: so we have the correct final approach for opening API connections23:03
anastasiamacaxw: go ahead if it's buringin then \o/23:03
anastasiamacsounds good23:03
davecheneycherylj: what's the status of 1.25.4 ?23:03
davecheneyi'm building up a lot of chagnes on master that should be backported to 1.2523:04
anastasiamacaxw: but if u r lookiing for things to do, I'd love to see what u'd do with file locks :D23:04
axwanastasiamac: that's fairly low priority atm. important, but we can change it behind the scenes without impacting any other code23:05
perrito666ok seems that compiling the tests and running hangout might be a bit too much for the laptop23:14
davecheneywhee, just looked at the org chart, i have 6 manager above me23:16
davecheneyonly 4 more and we'll be microsoft class23:16
wallyworld_alexisb: standup if you are free23:16
perrito666davecheney: I wish, they have lovely cafeterias23:19
davecheney^ this is good news23:42

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!