[00:39] <veebers> If I deploy a charm and 'juju expose' it, I should be able to access that from my host, right? (local environment, charm is elastic search)
[00:40] <veebers> The test curl query works if I'm on the machine itself, but not from the host
[01:22] <thumper> veebers: if you are using the local provider, it is all exposed anyway
[01:22] <thumper> veebers: how are you doing the query?
[01:38] <veebers> thumper: it's all good, I've worked around it (using 'juju run') Its not important as im just tinkering at this point and it's not essential for the end resulting product
[05:17] <frenda> - HI there, Is there any working service currently using juju gui?
[05:17] <frenda> - Is juju-gui translatable?
[11:34] <ddellav> morning arosales
[13:12] <apuimedo> lazyPower: Hi
[14:18] <apuimedo> jamespage: ping
[14:57] <arosales> ddellav, morning
[15:01] <jamespage> hey arosales, ddellav
[15:06] <ddellav> hey guys
[16:51] <beisner> jamespage, can you land this?  coreycb has reviewed.  https://code.launchpad.net/~1chb1n/charm-helpers/amulet-ceph-cinder-updates/+merge/262013
[16:53] <beisner> coreycb, added functional test coverage to cinder-ceph, cinder-next, ceph-radosgw, ceph-osd and ceph;  can you review these?  http://paste.ubuntu.com/11794072/
[17:03] <coreycb> beisner, yep, will do
[23:27] <ennoble> Is there a way to kill a juju action that is in the running state, but isn't running any longer? juju debug-log is also repeating: ERROR juju.rpc server.go:573 error writing response: EOF & ERROR juju.worker.uniter.filter filter.go:137 tomb: dying
[23:50] <thumper> ennoble: interesting
[23:51] <thumper> ennoble: can I get you to file a bug and attach the relevant log parts that show the start of the uniter errors?