=== brandon is now known as Guest49817 === kadams54 is now known as kadams54-away [11:16] stub: ping - you around today? === lp|away is now known as lazyPower === scuttle|afk is now known as scuttlemonkey === tris- is now known as tris === tris is now known as 7F1AALP94 [14:11] ARG google marked some juju emails as spam [14:11] lazyPower: it marked some of your posts as spam. GRAR === ericsnow is now known as ericsnow_afk [14:12] I missed a nice post about Docker === ericsnow_afk is now known as ericsnow [15:00] If I have a local install of "juju-quickstart bundle:~landscape/landscape-dense-maas...", can I add my maas target to it so I can deploy on maas controlled hardware? If so, where do I find how? === cmagina_ is now known as cmagina [15:29] drbidwell: so I think the trick is you have to use maas tags to target the deployment to those using contraints. [15:29] drbidwell: see https://jujucharms.com/docs/1.20/charms-constraints#maas-constraints would need to be updated in the bundle, so you'd have to edit the bundle file to add those constraints in === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey === jog_ is now known as jog === natefinch is now known as natefinch-afk === natefinch-afk is now known as natefinch === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey [19:15] what is the right way to replace a block-storage-broker (it is not a subordinate) in an environment? [19:15] I don't want to tear everything down [19:16] what is the common practice? I'm going to go read the postgresql carm to see what it does when the relation is removed [19:17] before I go through and remove the unit and then add a new one and then relate it === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [19:53] In order to use juju/juju-gui on a local machine I need to set up lxc networking as a better bridge so it is not using 10.* and 192.* ??? [19:56] BradyForM: you're deploying it to an lxc juju environment? [19:57] BradyForM: not following all the way what you're heading towards is what I'm getting at [19:57] rick_h_, I ran juju-quickstart [19:57] BradyForM: with a lxc juju environment? [19:57] and it says that everything is in a container for local [19:58] so if you do juju status you should see your gui deployed to an environment on a machine there with an IP address you can use to access it. [19:58] with a 10.X.X.X for the juju gui. when I run juju status [19:58] BradyForM: and quickstart should auto open the gui for you once it's up and running [19:58] But I can not acess it if it is out side my local ? [19:59] BradyForM: oh, outside of your machine elsewhere on the network? [19:59] example I am on 192.X.X.X and the lxc contianer is on 10.X.X.X [19:59] for the Gui ^^ [19:59] BradyForM: no, you'll have to configure lxc to pull from your outside network for IP addresses [19:59] BradyForM: you can, but it takes some doing and i wouldn't say its "officially supported" - http://blog.dasroot.net/making-juju-visible-on-your-lan.html [19:59] BradyForM: or you'll have to proxy or ssh tunnel the gui out [19:59] ahh [19:59] well check that out, lazyPower with even written docs on it woot :) [19:59] BradyForM: the better solution would be to use sshuttle for a quick and dirty VPN [19:59] is there a example of running juju on a VM ? [20:00] on the local [20:00] VM is bridged to my local [20:00] you can, we have a vagrant image for it actually [20:00] lazyPower: do you know the latest on juju and that virutalbox tool folks were working on? [20:00] vagrant, that's it [20:00] https://jujucharms.com/docs/1.20/config-vagrant [20:00] you know for testing purposes [20:00] Oo [20:01] BradyForM: if/when you graduate from local usage and still want to isolate you environment, we haev a docker container that has all the tools for you [20:01] thanks for all your help ! looking at that link and seeing what I can do that that. [20:01] lazyPower, that sounds great [20:02] BradyForM: https://github.com/whitmo/jujubox - due to app armor profile restrictions this will *not* work with the local provider. [20:02] but its worth a bookmark and checking out later in your ventures when paired with a cloud provider like AWS or digital ocean. [20:02] lazyPower, we are thinking about using ec2 thoughts ? [20:03] Its a solid choice. I use EC2 quite a bit myself when testing [20:03] cool [20:26] lazyPower, rick_h_ that worked like a charm ;) [20:26] Happy its working for you BradyForM o/ [20:27] \o [20:27] BradyForM: woot === _thumper_ is now known as thumper [20:29] I’m trying to find a guide on how to recover a juju cluster when one of the state servers ip’s have changed. AWS rebooted one of our three and juju refuses to connect to anything. [20:29] Is there a template to get started writing my own bundles or charms ? [20:30] BradyForM: if you have the 'charm tools' package installed there is a generator [20:30] charm create -h [20:31] lazyPower, do you know if there is ports for debian jessie ? for the charm tools that is [20:32] or should I add a ppa and just see if it works [20:32] host is debian jessie [20:33] I would think the ppa would work... but i haven't tested it tbh [20:33] lets give it a shot ! :) === scuttlemonkey is now known as scuttle|afk === axw_ is now known as axw === kadams54 is now known as kadams54-away