[05:20] <viswesn> Hi all,  I getting error on running 'juju bootstrap lxd-test localhost' in Ubuntu 16.04
[05:21] <viswesn> Error msg is "Unable to get LXD image for ubuntu-xenial: The requested image couldn't be found"
[05:21] <viswesn> I am followed the doc link
[05:22] <viswesn> https://jujucharms.com/docs/stable/getting-started
[05:25] <viswesn> Is there any one to help me on juju bootstrap issue?
[05:30] <viswesn> #juju :  Need help on juju bootstarp
[05:37] <viswesn> @all: Is there any one who can help me on juju bootstrap
[05:38] <thumper> hey
[05:39] <thumper> which version of juju?
[05:39] <thumper> also, are you on a closed network?
[05:39] <viswesn> juju version 2.0
[05:39] <viswesn> No
[05:41] <viswesn> cannot start bootstrap instance: unable to get LXD image for ubuntu-xenial: The requested image couldn't be found.
[05:41] <thumper> what do you get if you just go "lxc launch ubuntu:x"
[05:42] <viswesn> It is retrieving the image now
[05:43] <viswesn> $> lxc launch ubuntu:xenial
[05:49] <thumper> no idea why it didn't work before
[05:49] <thumper> juju should be able to use it now
[05:49]  * thumper done for the day
[05:49] <thumper> good luck
[05:58] <viswesn> @all  me getting different error now on running juju bootstrap
[05:58] <viswesn> ERROR cmd supercommand.go:458 failed to bootstrap model: Juju cannot bootstrap because no tools are available for your model. You may want to use the 'agent-metadata-url' configuration setting to specify the tools location.
[05:58] <viswesn> How to resolve this issue
[06:03] <viswesn> @all Can I get help on Juju bootstrap issue
[06:03] <viswesn> juju version 2.0-beta15-xenial-amd64
[06:13] <viswesn> @all any one here to help me on juju bootstrap issue?
[06:17] <viswesn> @all any one here to help me on juju bootstrap issue?
[06:46] <viswesn> @all any one here to help me on juju bootstrap issue?
[06:46] <viswesn> I am seeing error during juju bootstrap
[14:03] <elspru> can I deploy an openCL program on juju?
[15:13] <geetha> Hi, when I run `juju attach` command to upload resource, it's giving me the error: http://paste.ubuntu.com/23181757/. Can anyone please help me o this?
[15:39] <geetha> Hi, when I run `juju attach` command to upload resource, it's giving me an error: http://paste.ubuntu.com/23181757/. Can anyone please help me on this?
[15:40] <lazyPower1> geetha: whats the output of `juju version` ?
[15:44] <geetha> lazyPower1: output of `juju version`: 2.0-beta15-xenial-s390x
[15:45] <lazyPower1> geetha:  there have been a lot of improvements to resources in the later 2.0 betas. Can you try upgrading to juju 2.0-beta18 and giving it another go?
[15:47] <geetha> lazyPower1: ok, I'll try with juju 2.0-beta18
[15:47] <geetha> lazyPower1: thank you
[15:47] <lazyPower1> no problem
[17:15] <geetha> Hi, I'm getting this error: http://paste.ubuntu.com/23182940/
[17:17] <lazyPower1> geetha: - is that still on beta-15?
[17:17] <lazyPower1> geetha: that was bugged and fixed in the later betas according to this bug: https://bugs.launchpad.net/juju/+bug/1591387
[17:17] <mup> Bug #1591387: juju controller stuck in infinite loop during teardown - "lease manager stopped" errors <2.0> <destroy-controller> <juju:Fix Released by fwereade> <https://launchpad.net/bugs/1591387>
[17:21] <geetha> no on beta -18?
[17:21] <geetha> beta-18.
[17:23] <geetha> It's displaying juju status message as: resolver loop error
[18:22] <Siva_> I am using Juju 2.0 beta version 18
[18:23] <Siva_> I am trying to juju bootstrap and I am seeing the following error
[18:24] <Siva_> root@juju-api-client:~# juju bootstrap juniper-juju-controller junipermaas --to juju-controller.maas --show-log 11:10:25 INFO  juju.cmd supercommand.go:63 running juju [2.0-beta18 gc go1.6.2] 11:10:25 INFO  cmd cmd.go:141 Adding contents of "/root/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys 11:10:25 INFO  cmd cmd.go:141 Adding contents of "/root/.ssh/id_rsa.pub" to authorized-keys 11:10:30 ERROR cmd supercommand.go:458 Get 
[18:24] <Siva_> Any idea what does this mean?
[18:24] <Siva_> I am able to ping 192.168.1.2
[18:24] <Siva_> I am able to ping 192.168.1.2 which is the MAAS container
[18:40] <madhu> Hello all, we are using juju 2.0-beta18-xenial-amd64 version
[18:41] <madhu> When we are trying to use the juju bootstrap command to connect to the MAAs container, its giving us the below error
[18:41] <madhu> root@juju-api-client:~# juju bootstrap juniper-juju-controller junipermaas --to juju-controller.maas --show-log 11:10:25 INFO  juju.cmd supercommand.go:63 running juju [2.0-beta18 gc go1.6.2] 11:10:25 INFO  cmd cmd.go:141 Adding contents of "/root/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys 11:10:25 INFO  cmd cmd.go:141 Adding contents of "/root/.ssh/id_rsa.pub" to authorized-keys 11:10:30 ERROR cmd supercommand.go:458 Get 
[18:42] <Siva_> any help is much appreciated
[18:43] <madhu> 11:10:30 ERROR cmd supercommand.go:458 Get http://192.168.1.2/MAAS/api/1.0/version/: invalid proxy address "http://[fe80::1%eth0]:13128": parse http://[fe80::1%eth0]:13128: invalid URL escape "%et"
[20:24] <cclarke> I have MAAS/juju installed on a physical server and I am able to use juju to bootstrap and deploy charms to different nodes. Issue is all docus for Ubuntu 14 say to use quantum-gateway, but that is end of life and says to use neutron-gateway. But it stays blocked and the error is: (config-changed) Missing relations: messaging
[20:24] <cclarke>  Is this the correct channel to look for assistance deploying openstack with MAAS/juju and does anyone have any ideas or has seen this before?
[20:45] <cmars> is there an example working charm that uses layer:docker I can look at?
[21:42] <lazyPower1> stokachu: thanks for the turnaround on layer-nginx :)  It cleaned up nicely
[21:43] <lazyPower1> cmars: our kubernetes charms, i wrote a nice tutoral over on insights
[21:43] <cmars> lazyPower1, link?
[21:43] <lazyPower1> cmars: http://dasroot.net/posts/2016-08-03-layer-docker-deep-dive/
[21:43] <lazyPower1> or
[21:44] <lazyPower1> https://github.com/kubernetes/kubernetes/tree/master/cluster/juju/layers/kubernetes
[21:44] <cmars> lazyPower1, thanks
[21:45] <lazyPower1> cmars: I was giving this some thought during the summit, there are probably some very straight forward use cases that we could condense that code down quite a bit as well. feedback/bugs welcome.
[21:46] <lazyPower1> eg: framework it so you generate a lot of that boilerplate from a compose.yaml if thats your end goal is just to spin up the container formation defined there and not relate to anything, but i  dont know that we want to encourage that behavior in our ecosystem... as relations are a good chunk of the reason juju rocks our socks
[21:49] <jhobbs> did set-model-config go away in beta18?
[21:52] <lazyPower1> jhobbs: is just model-config now
[21:53] <lazyPower1> jhobbs: they dropped the set- infront of it.  so juju model-config enable-os-upgrades=true  would be the current syntax
[21:53] <jhobbs> ok thanks lazyPower1
[21:53] <jhobbs> i guess i missed the memo on that one
[21:53] <lazyPower1> i did too, dont feel bad :)
[22:26] <magicaltrout> afternoon
[22:27]  * magicaltrout has checked into a hotel 1 block away... what a  waste of time
[22:43] <smgoller-> what's the best bundle off jujucharms for deploying openstack mitaka on maas-2.0? I'm currently trying out this one: https://jujucharms.com/u/openstack-charmers-next/openstack-base-xenial-mitaka
[22:43] <smgoller-> oh yeah, and xenial. :)