[00:00] <sebas538_> somebody used juju-nat ?
[00:00] <sebas538_> cmars: ping
[00:03] <sebas5384> cmars: juju-nat can be used to expose ports from a service through the host machine? let's say a virtualbox(host machine)
[00:14] <cmars> sebas5384, yes
[00:14] <cmars> sebas5384, how do you have virtualbox set up as a host? manual provider?
[00:15] <cmars> or are you using the local provider inside vbox?
[00:17] <sebas5384> cmars: juju-local
[00:17] <sebas5384> im using lxc on the host
[00:19] <cmars> sebas5384, i'm not sure if juju-nat will work in that setting, though I've not tested juju-nat with local (I typically deploy into lxc containers with the manual provider or cloud providers)
[00:20] <sebas5384> cmars: hmmm gotcha
[00:20] <sebas5384> well i teste with a juju-local, and tried to expose the ports of a service through the host machine(vbox)
[00:21] <sebas5384> but didn't work :P
[00:21] <sebas5384> would it be cool to have a tool like that
[00:22] <sebas5384> do you think that your plugin can be extended to meet that feature?
[00:22] <cmars> sebas5384, indeed. the iptables commands would be similar. the tricky part is the way vbox networking is usually set up
[00:22] <sebas5384> yeah
[00:23] <cmars> bridging or the host-only interfaces would have to be used
[00:23] <sebas5384> but i'm already exposing 80 and 443 in using vagrant :)
[00:23] <cmars> ah, they've certainly figured that out... good point. there should be a way then
[00:24] <cmars> sebas5384, i'll have to play with vbox
[00:24] <sebas5384> yeah, i was using something like "iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to 10.0.3.170:80"
[00:24] <sebas5384> but that rule was breaking some things hehe
[00:27] <cmars> juju-nat specifies -d DEST and the interface, see https://github.com/cmars/juju-nat/blob/master/cmd/common.go#L104
[00:28] <sebas5384> i was there, trying to understand hehe
[00:28] <sebas5384> hmmm
[00:28] <sebas5384> so you specify the interface, never tried that
[00:29] <cmars> pretty sure it shouldn't be the default vbox NAT one
[00:31] <sebas5384> yes
[00:31] <sebas5384> eth2
[00:31] <sebas5384> so an interface parameter in the juju-nat
[00:31] <sebas5384> maybe would fix that problem
[00:32] <sebas5384> :)
[00:32] <sebas5384> cmars: juju nat-expose drupal/0 --interface eth2
[00:33] <sebas5384> just saying hehe
[00:33] <cmars> sebas5384, i might be able to do a bit better. detect if we're using the local provider, and then require an interface (if I can't figure out a way to autodetect one)
[00:33] <sebas5384> cmars: what you think?
[00:34] <sebas5384> hmmm
[00:34] <sebas5384> nice
[00:34] <sebas5384> liket that
[00:34] <sebas5384> *liked
[00:35] <sebas5384> cmars: i'm cloning here the project from git :P
[00:35] <sebas5384> just for playing, btw thank you for this tool!
[00:36] <cmars> sebas5384, https://github.com/cmars/juju-nat/issues/5
[00:36] <cmars> sebas5384, thanks :)
[00:36] <sebas5384> nice!!
[00:37] <sebas5384> cmars: i don't know go lang, but, do you think i can do it?
[00:37] <sebas5384> or its toooo easy for you
[00:37] <sebas5384> hehe
[00:38] <cmars> sebas5384, golang is pretty easy to pick up, though it might become contagious to write
[00:39] <sebas5384> cmars: hehe contagius? what you mean?
[00:39] <cmars> sebas5384, some developers can't stop writing in it once they start
[00:40] <sebas5384> hahahhaa
[00:40] <cmars> habit-forming, i should say
[00:40] <sebas5384> nice, like that kind of lang
[00:41] <sebas5384> cmars: well I will try to make that happen
[00:41] <sebas5384> if i cant do it, can i ping you?
[00:41] <cmars> sebas5384, certainly
[00:42] <sebas5384> great! thanks cmars!
[04:01] <sebas5384> cmars: ping
[14:26] <AskUbuntu> Running Openstack on 3 nodes | http://askubuntu.com/q/474911
[17:49] <s3an2> Hi, is there a reason when deploying the ubuntu juju charm using the MAAS provider br0 is added instead of just using eth0?