[15:25] <josepht> is any hook triggered when a service is exposed?
[15:26] <jose> josepht: nope, the only thing that happens is that the ports are opened for the external world to connect to
[15:27] <josepht> jose: thanks
[16:12] <mrjazzcat> Is there a way to turn off the juju engine for a while, to leave the environment in a certain state?
[16:15] <lazyPower> mrjazzcat: when you say turn off the juju engine - i'm assuming you mean halt the state-server so no agents receive any further events for the duration of teh state-server outage?
[16:16] <mrjazzcat> lazyPower:  That's it exactly
[16:16] <lazyPower> that would be my recommendation then - just halt the state-server machine for the duration of the desired "locked config"
[16:16] <lazyPower> er
[16:16] <lazyPower> "locked state"
[16:17] <mrjazzcat> lazyPower:  Is there a method to halt it?  kill <pid>  ??  Better?
[16:17] <lazyPower> mrjazzcat: well i was referring to actually halting the VM
[16:17] <mrjazzcat> lazyPower:  Ah, OK.  Thank you!
[16:17] <lazyPower> it does have an upstart job - let me see what i can fish up
[16:19] <lazyPower> mrjazzcat: if you want to just halt the services, look like juju-db and jujud-machine-0 are the jobs to stop
[16:19] <lazyPower> so, service jujud-machine-0 stop should be sufficient. as thats the state-server api process
[16:19] <mrjazzcat> lazyPower:  awesome.  I'll try that.  Thanks again
[17:50] <appelgriebsch> hello, I tried to use JuJu on a dedicated Ubuntu Server 14.04 LTS installation in our office network (http proxy enabled) with the local (LXC) adapter
[17:51] <appelgriebsch> everything bootstraps fine and juju status shows the agent running on local machine
[17:51] <appelgriebsch> but doing a juju deploy juju-gui failed when trying to access the web repo
[17:52] <appelgriebsch> have set the environment variables for the proxy (juju set-env http-proxy=...) but did not solve the issue
[17:52] <appelgriebsch> does someone has an hint how to proceed?
[17:54] <appelgriebsch> btw: doing a curl with the URL (something like https://charm...) works fine on the server
[17:59] <lazyPower> appelgriebsch: From the parent that worked - have you tried in the lxc-container the local provider allocated?
[18:02] <appelgriebsch> lazyPower: sorry, I don't understand your proposal. Everything was executed on one machine. Accessing the web repo via juju doesnt work. Doing a curl request (manually) from the same machine to the URL listed in the juju error message works fine
[18:05] <lazyPower> appelgriebsch: ah sorry for the confusion. The local provider spins up light weight containers to emulate a cloud to deploy services - if the networking on your host is fine doesn't necessarily mean your containers aren't inheriting the same config. What iw as asking is if you have tried to ssh into that machine:  juju ssh juju-gui/0 , and then try executing the command
[18:05] <lazyPower> since you mentioned a proxy is being set - i imagine the error here is the proxy isn't being inhereted by your juju env - and your communication isn't being routed properly through that proxy
[18:05] <lazyPower> i've got limited experience witht his and will tap someone else to see if they can help you - 1 moment while i put out a request for help
[18:07] <lazyPower> natefinch: when you juju-set http-proxy on the local provider, are all your lxc-containers expected to inheret that config as well? or have I missed something in the docs.
[18:40] <jose> beisner: hey, mind a quick PM?
[18:41] <beisner> o/ jose
[18:41] <jose> o/
[19:32] <natefinch> lazyPower: it's an environment-level property, so it really should be respected by everything
[19:33] <lazyPower> natefinch: ack. a user joined up experiencing the issue and has susequently left - but I thought that was the case.
[19:33] <lazyPower> ty for clarification
[19:33] <natefinch> lazyPower: though what I hear is "blah blah local provider"
[19:33] <natefinch> lazyPower: and the answer is almost always "that's not what local provider is for"
[19:34] <natefinch> unfortunately, I think way too many people misunderstand how juju works, and try to use local provider instead of just deploying to a machine and adding LXC containers to it.
[19:35] <lazyPower> natefinch: understood and agreed
[19:35] <lazyPower> natefinch: When I wrap up this weeks video overview of the rudder/lxc stuff - would you mind giving it a proof watch before i publish - i bet you've got some insight into this topic I may miss.
[19:36] <natefinch> lazyPower: sure, though lxc is not my forte... but I can give it a once-over
[19:37] <lazyPower> the more eyes the better quality the output will be is my thought :) Thanks for the pledge natefinch
[19:37] <lazyPower> this one has taken me longer than I care to admit circling back to