[04:30] is there a way to list a local charm in a bundle file? [05:10] answering my own q, just need to specify the path === bbaqar is now known as bbaqar_ === bbaqar_ is now known as bbaqar__ === bbaqar__ is now known as bilalbaqar === bilalbaqar is now known as bilalbaqar_ === bilalbaqar_ is now known as bilalbaqar__ [12:32] #juju [13:49] hi all [13:49] I have installed JUJU on my PC alongside with some charms [13:49] no problems there [13:49] I use the LXD option and everything is running localy [13:51] 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] holocron: maybe an idea? [14:02] juju expose does nothing on lxd PCdude [14:03] all i do it iptables routing [14:03] sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 81 -j DNAT --to 10.106.143.112:80 [14:06] magicalt1out: uhm ok, I was looking at this link: http://askubuntu.com/questions/749063/reach-lxd-container-from-local-network [14:06] 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] ? [14:07] It feels like removing an extra layer of complexity where it is not needed imho [14:08] 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 ;) === magicalt1out is now known as magicaltrout [14:09] but I agree its called lxd local for a reason [14:12] 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] yeah good point haha, well it is in a test environment [14:13] jrwren: I see ur point there [14:13] if you do that, beware the solution in that askubuntu answer won't quite work. [14:13] juju uses its own lxd profile. it doesn't inherit from default. [14:14] yo'll need to lxc profile edit juju-default [14:14] jrwren: which was exactly my next question :) [14:14] is that an easy task? [14:14] it isvery easy [14:15] you just need to know that you need to do it. [14:15] ah ok check, will keep that in mind [14:16] so another thing is the way ipv4 and ipv6. I am not sure if this is a LXD or JUU thing [14:17] 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] 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] and where can I see the address where the "automatic" gui is located? [14:18] 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] `juju gui` will tell you the gui address [14:21] 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] 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] it depends on the address. if it starts with fe80 its a local address [14:24] it sounds like the DHCP for LXD isn't working, or something. [14:24] Did you setup that bridge to LAN already? [14:24] starts with fddc so should be accessible, but it is not.. [14:25] https://jujucharms.com/docs/stable/getting-started [14:25] that is what I followed to install JUJU [14:25] there is an bridge in "ifconfig", I am 95% sure there is [14:25] if you run `lxc list` what ip addresses does it show? [14:26] both v4 and v6 [14:26] those names are the same as in juju status [14:26] let me check real quick [14:28] so... if you correlate the v6 address to the v4 address you should be able to use that to view the gui. [14:29] jrwren: yeah, was trying exactly that with the command of magicaltrout earlier, but does not seem to work [14:36] ok, it took me some time, but I got the problem [14:36] I was mapping with iptables to eth0, but of course that is not the case anymore in 16.04 [14:37] mapped it to ens33 (or any port for that matter) and it worked [14:37] thanks anyway!! [14:47] so I see this login screen for the first time :) [14:47] what is the different between login and login with usso [14:48] and what credentials should I use? [14:48] the normal credentials for login to the machine does not work [14:50] PCdude: juju gui --show-credentials will tell you the password [14:53] awesome and what is USSO? [14:54] Ubuntu Single Sign On. [14:55] I don't think that works yet. We probably should not show that button if it won't work. [14:56] 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] SSO can be run by ANYTHING. Your google account is SSO to many google related services. [15:33] hi, it there somewhere an example how to use install-keys in a juju bundle, somehow my yaml is not valid === redir is now known as redir_afk [17:41] todin: I'm not sure about bundle, but if you want you set install-keys config, you can do that by $ juju config install-keys='$(cat ' [17:42] junaidali: thanks for your help, I found my solution here https://bugs.launchpad.net/charm-helpers/+bug/1515699 [17:42] Bug #1515699: configure_sources fails badly with misformatted configuration. [17:45] thanks todin and mup: I didn't know about that === zerick_ is now known as zerick