[02:42] <pjdc> r
[09:50] <gnuoy> anyone got a sec to help with a network spaces issue? I have a neutron-api charm on 10.60.0.0/24 and 10.70.0.0/24 and a mysql instance on 10.70.0.0/24 and on the neutron-api charm I see:
[09:50] <gnuoy> network-get --primary-address shared-db
[09:50] <gnuoy> 10.60.0.5
[09:50] <gnuoy> Why is juju deciding to return the 10.60 address?
[10:38] <wpk>   
[10:39] <wpk> what network-get shared-db shows (without --primary-address)?
[10:39] <boolman> how do I change sysctl settings inside lxd containers on deploy?
[10:41] <boolman> I'm using maas as provider
[12:29] <gnuoy> wpk, sorry, I redeployed my setup. This what I'm seeing: http://paste.ubuntu.com/25707092/
[12:41] <gnuoy> wpk, fwiw these are the other bindings on the neutron-api unit http://paste.ubuntu.com/25707152/
[12:45] <junaidali> Hi guys, have anyone faced autocompletion issue with juju commands?
[12:46] <junaidali> I'm getting this error when I press tab to autocomplete  a command
[12:46] <junaidali> _juju_complete_2_0: command not found
[13:40] <gnuoy> wpk, I redeployed with shared-db=internal bind for the neutron-api charm and that fixed it.
[14:06] <zeestrat> junaidali: Which version of Juju are you running and how is installed (deb, snap)? Did this crop up after upgrading something or a new install?
[15:48] <ybaumy> pmatulis: please ask. thank you
[16:57] <junaidali> Hi zeestrat: It's 2.0.2-0ubuntu0.16.04.2 installed via apt
[16:59] <junaidali> a new install
[17:23] <zeestrat> junaidali: Some of the devs here might know a solution, but just FYI that 2.0.2 release in the main repositories is a quite old and it's recommend that you use the juju/stable PPA (https://launchpad.net/~juju/+archive/ubuntu/stable) if possible.
[17:23] <junaidali> sure zeestrat, I will try that. Thanks
[17:31] <zeestrat> junaidali: No problem. Also, in case you're interested and your environment allows it, the juju team recommends installing juju as a snap (see https://jujucharms.com/docs/stable/reference-install#ubuntu) which can be real nice.
[17:34] <junaidali> zeestrat: do you think would there be any compatibility issues if I upgrade juju from 2.0.2 to the latest stable one (2.2.4)? I have a deployment with 2.0.2
[17:35] <magicaltrout> you can snap install and have the apt installed version
[17:35] <magicaltrout> I believe
[17:36] <magicaltrout> rick_h: ping
[17:37] <junaidali> magicaltrout: is the juju data directory (.local/share/juju) different for snap installed juju.
[17:37] <junaidali> I think I'm a bit confused here, I will try it out and will see what happens
[17:39] <zeestrat> junaidali: Assuming this is a production deployment, I'd recommended testing these things in dev first. You can run different versions of Juju on your machine (client) and on controllers (server), then upgrade the controller/models if you want. See also https://jujucharms.com/docs/stable/models-upgrade
[17:44] <junaidali> Thanks, I did have a look at controller upgrade. I will stick to client update atm.
[18:05] <hallyn> kirkland: seriously, i urge you to find a clever way to address the problem that googling something like 'juju proxy' gives you outdated results (i.e. for 1.22)
[18:05] <hallyn> i predict it will cut down on adoption
[20:40] <hallyn> So if juju bootstrap for a vsphere controller behind a http proxy keeps giving me 'No packaged binary found, preparing local Juju agent binary' does that mean i didn't specify the proxy in the right place?
[20:41] <hallyn> I've set it in ~/.local/share/juju/clouds.yaml , but juju show-clouds doesn't show the updated info
[20:41] <hallyn> juju set-env no longer exists ...  (couldn't tell it by google, see above :)
[20:41] <hallyn> axw: \o