[04:30] <holocron> is there a way to list a local charm in a bundle file?
[05:10] <holocron> answering my own q, just need to specify the path
[12:32] <junaidali> #juju
[13:49] <PCdude> hi all
[13:49] <PCdude> I have installed JUJU on my PC alongside with some charms
[13:49] <PCdude> no problems there
[13:49] <PCdude> I use the LXD option and everything is running localy
[13:51] <PCdude> when I type "juju expose application" that seems to work, but the address is an LXD container address and thus not accessible without modification. Now, I can go in LXD and make some firewall changes and stuff, but what is the recommended way to deal with this, maybe I am overlooking some command from JUJU to do this
[13:59] <PCdude> holocron: maybe an idea?
[14:02] <magicalt1out> juju expose does nothing on lxd PCdude
[14:03] <magicalt1out> all i do it iptables routing
[14:03] <magicalt1out> sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 81 -j DNAT --to 10.106.143.112:80
[14:06] <PCdude> magicalt1out: uhm ok, I was looking at this link: http://askubuntu.com/questions/749063/reach-lxd-container-from-local-network
[14:06] <PCdude> which basically gives the same option as u said. Are there any downsides by bringing the LXD containers directly to the LAN. IP addresses on the LAN would not be an problem here
[14:06] <PCdude> ?
[14:07] <PCdude> It feels like removing an extra layer of complexity where it is not needed imho
[14:08] <jrwren> PCdude: the recommended way is to use lxd only for dev/test of charms and bundles. It isn't meant to be used for production in this way.
[14:08]  * magicalt1out uses it in production in that way ;)
[14:09] <magicaltrout> but I agree its called lxd local for a reason
[14:12] <jrwren> not much downside to bridging LXD to lan, other than you now depend on LAN DHCP. if you are on laptop and move, your containers won't be accessible.
[14:12] <PCdude>  yeah good point haha, well it is in a test environment
[14:13] <PCdude> jrwren: I see ur point there
[14:13] <jrwren> if you do that, beware the solution in that askubuntu answer won't quite work.
[14:13] <jrwren> juju uses its own lxd profile. it doesn't inherit from default.
[14:14] <jrwren> yo'll need to lxc profile edit  juju-default
[14:14] <PCdude> jrwren: which was exactly my next question :)
[14:14] <PCdude> is that an easy task?
[14:14] <jrwren> it isvery easy
[14:15] <jrwren> you just need to know that you need to do it.
[14:15] <PCdude> ah ok check, will keep that in mind
[14:16] <PCdude> so another thing is the way ipv4 and ipv6. I am not sure if this is a LXD or JUU thing
[14:17] <PCdude> I was not aware that JUJU 2.0 installed the web GUI automatically, so I installed it the old way with a charm
[14:17] <PCdude> now, I have 2 questions. Why is the charm I installed been given an ipv6 address and how can I change this to a ipv4 address?
[14:18] <PCdude> and where can I see the address where the "automatic" gui is located?
[14:18] <jrwren> charms don't get ip addresses, machines/containers do. it is normal for it to have an ipv6 address. are you saying it does not have an ipv4 address also?
[14:19] <jrwren> `juju gui` will tell you the gui address
[14:21] <PCdude> juju gui gives me an ipv6 address, should that address be availabe from the network or is that also an container. (not talking about the charm I installed myself, but the automatic one)
[14:22] <PCdude> the one I installed myself is only having an ipv6 address, but not sure. How can I check? I looked with juju status and juju status juju-gui and both only give me an ipv6 address for the juju-gui
[14:23] <jrwren> it depends on the address. if it starts with fe80 its a local address
[14:24] <jrwren> it sounds like the DHCP for LXD isn't working, or something.
[14:24] <jrwren> Did you setup that bridge to LAN already?
[14:24] <PCdude> starts with fddc so should be accessible, but it is not..
[14:25] <PCdude> https://jujucharms.com/docs/stable/getting-started
[14:25] <PCdude> that is what I followed to install JUJU
[14:25] <PCdude> there is an bridge in "ifconfig", I am 95% sure there is
[14:25] <jrwren> if you run `lxc list` what ip addresses does it show?
[14:26] <PCdude> both v4 and v6
[14:26] <PCdude> those names are the same as in juju status
[14:26] <PCdude> let me check real quick
[14:28] <jrwren> so... if you correlate the v6 address to the v4 address you should be able to use that to view the gui.
[14:29] <PCdude> jrwren: yeah, was trying exactly that with the command of magicaltrout earlier, but does not seem to work
[14:36] <PCdude> ok, it took me some time, but I got the problem
[14:36] <PCdude> I was mapping with iptables to eth0, but of course that is not the case anymore in 16.04
[14:37] <PCdude> mapped it to ens33 (or any port for that matter) and it worked
[14:37] <PCdude> thanks anyway!!
[14:47] <PCdude> so I see this login screen for the first time :)
[14:47] <PCdude> what is the different between login and login with usso
[14:48] <PCdude> and what credentials should I use?
[14:48] <PCdude> the normal credentials for login to the machine does not work
[14:50] <jrwren> PCdude: juju gui --show-credentials will tell you the password
[14:53] <PCdude> awesome and what is USSO?
[14:54] <jrwren> Ubuntu Single Sign On.
[14:55] <jrwren> I don't think that works yet. We probably should not show that button if it won't work.
[14:56] <PCdude> strange, I thought that was simply called SSO, but it seems like some sort of LDAP service to seperate JUJU and the user accounts?
[15:05] <jrwren> SSO can be run by ANYTHING. Your google account is SSO to many google related services.
[15:33] <todin> hi, it there somewhere an example how to use install-keys in a juju bundle, somehow my yaml is not valid
[17:41] <junaidali> todin: I'm not sure about bundle, but if you want you set install-keys config, you can do that by $ juju config <charm-name> install-keys='$(cat <install_Key>'
[17:42] <todin> junaidali: thanks for your help, I found my solution here https://bugs.launchpad.net/charm-helpers/+bug/1515699
[17:42] <mup> Bug #1515699: configure_sources fails badly with misformatted configuration. <Charm Helpers:Triaged> <https://launchpad.net/bugs/1515699>
[17:45] <junaidali> thanks todin and mup: I didn't know about that