[00:00] Bug # changed: 1530957, 1532167, 1536446, 1536728, 1542127 [01:30] Bug #1547741 opened: Cannot build on armhf with go1.2

[09:16] Bug #1547806 opened: open-port does not work on EC2 [15:20] Bug #1547887 opened: Wrong endpoints for Joyent us-east-1 and us-east-2

[15:20] Bug #1547891 opened: Juju searches for index2.sjson in image streams

[15:44] Bug #1547898 opened: create-model confusing, does not just work

[15:47] Bug #1547898 changed: create-model confusing, does not just work

[15:50] Bug #1547898 opened: create-model confusing, does not just work

[21:57] did I miss something obvious? `juju init` doesn't work in 2.0beta1 [22:00] jcastro: there is no more init [22:00] jcastro: you use list-clouds, list-credentials, etc [22:00] jcastro: try add-credentials [22:00] * rick_h_ hasn't upgraded on here yet [22:01] jcastro: in beta1 there is no more environments.yaml [22:01] oh, well init still exists when I just type `juju` [22:01] jcastro: hmm, have to look at why it exists. [22:01] ok I see the clouds [22:01] how do I do lxd then? [22:02] jcastro: "it just works" [22:02] jcastro: so juju bootstrap lxd $nameofcontroller [22:02] jcastro: and lxd should be the name of the cloud in list-clouds [22:02] no lxd in clouds [22:05] jcastro: can you bootstrap it with lxd? [22:05] juju bootstrap mycontroller lxd [22:05] * rick_h_ wonders if it's there but not visible in list-clouds in this release then [22:05] ERROR cloud "lxd" not found [22:06] axw: wallyworld around on the weekend at all? ^ [22:06] jcastro: probably have to manually edit the clouds.yaml file for now then if it's not there due to a bug/oversight on the release [22:06] trying that now [22:07] jcastro: should be able to add a stanza that's just named lxd with the type value of lxd in it [22:07] * rick_h_ needs to get my laptop out and update to the beta on there [22:08] any idea where I can find a cloud.yaml example? [22:08] should be in the .local/share/juju directory where things lived in alpha2 [22:08] it's plural [22:08] clouds.yaml (if you're searching with mlocate/etc) [22:09] brand new install though [22:09] and init won't generate a skeleton for me since it doesn't exist [22:09] it has to have stuck the file somewhere [22:09] right, but the package install needs to stick that file somewhere [22:09] and that should be in the xdg path [22:09] along with credentials file location, etc [22:10] * rick_h_ goes to get laptop, brb [22:10] the package doesn't have that file [22:11] do you think it's as simple as [22:11] lxd: [22:11] type:lxd [22:11] I'll try that [22:13] also [22:13] Development releases use the "devel" simple-streams. You must configure [22:13] the `agent-stream` option in your environments.yaml to use the matching [22:13] juju agents. [22:13] in the release notes [22:13] So is environments.yaml gone or not? [22:13] yes, but should say to use upload-tools perhaps? [22:14] I think there's a bootstrapping problem here [22:14] not like, bootstrapping in a juju context [22:14] but like, without init I don't have any information for juju to know about [22:14] and I can't add it because there are no example files [22:15] AHA! [22:15] dude [22:15] juju help add-clouds [22:15] * rick_h_ is upgrading hoping this isn't a brown paper bag release [22:15] jcastro: ah right [22:15] jcastro: but there shuold still be a file that feeds the current list-clousd [22:16] nope [22:16] heh running xenial means there's a lot more to upgrade than just juju [22:16] just an ssh directory and some keys in there [22:16] I am on trusty [22:16] try juju update-clouds [22:17] oh, I wonder if we blacklist there since lxd is wily+ [22:17] * rick_h_ is just guessing out the $#@$ [22:18] ok, added [22:18] that wasn't so bad [22:19] looks like update-clouds didn't make it [22:19] ok, wasn't sure on that one [22:20] yeah, it has to be because I am trusty [22:20] that's the only thing that makes sense [22:21] bah, under dist-ugprade vs upgrade /me tries again [22:22] ok, will investigate tomorrow, for now it's chimichanga time [22:22] woot [22:22] thanks for the heads up, will check out here on xenial [22:22] once the upgrade finishes [22:22] I'll ask on the list [22:36] Bug #1547966 opened: juju beta 1 does not include lxd in clouds [23:28] rick_h_: hi [23:29] just reading backscroll, lxd works out of the box, but not on trusty [23:30] rick_h_: update-clouds not in this release, hopefully beta2 [23:31] rick_h_: and yeah, no lxd provider on trusty until lxd and golang1.5 added to backports [23:34] wallyworld: k, I think he manually added lxd for his trusty [23:34] wallyworld: so that makes sense, it should show in list-clouds. I know it's not 'public' but that's the list folks will look at how to try things [23:34] wallyworld: so it needs to be a listed option [23:34] wallyworld: ty for the heads up on that it should be working ootb for non-trusty [23:39] rick_h_: yeah, we were following the spec for list-clouds output. easily added [23:39] wallyworld: cool ty [23:40] rick_h_: maybe release notes aren't explicit enough about lxd and trusty [23:40] wallyworld: yea, I think there's a general assumption since we keep saying lxd >= wily [23:40] but if folks manually go at it, they can get trusty/lxd [23:41] i'm not sure of the status of the backports effortd