juju-gui

Bug #1149410
Comment #18

Comment 18 for bug 1149410

Revision history for this message

brian mullan (bmullan) wrote on 2014-05-01:

#18

I have the same problem as reported in the original post of this bug ... except ... my use case is different.

I created an OpenStack "instance" of ubuntu 14.04.
I installed juju on that "instance" and configured it for Local Provider (re lxc).
I then bootstrapped and deployed Juju-GUI which successfully installed into its own LXC container.

If I install a desktop on that Openstack Ubuntu instance and log into it via a remote desktop capability I can start Firefox and point it to the 10.0.30.x address of the juju-gui container and login to juju-gui.

While logged into the OpenStack Ubuntu "instance" I can obviously ping to/from the juju-gui container and the Ubuntu Host.

But because my OpenStack Ubuntu instance is a 173.39.x.x address and the juju-gui container is a non-routable 10.x.x.x address I obviously cannot use Firefox from my Laptop and connect to the juju-gui.

However, I thought I could solve that by installing a Reverse Proxy on the OpenStack Ubuntu Host and point it to the 10.0.3.x address of Juju-gui container.

I used NGINX and it almost seems to work.

From my laptop I point Firefox to the 173.39.x.x address of the Ubuntu Host and the NGINX Proxy starts to redirect to the juju-gui. I see the Juju-Gui login screen start to appear but it just keeps spinning its circle and is stuck on "Trying to connect to the Juju environment" message.

So I am piggy backing on this Bug report since the resulting message is the same. I had thought that a Reverse Proxy like this would enable this access.

My use-case is to have people that from their desktop at work use their browser to connect to Juju-Gui then deploy "services" to LXC containers on the OpenStack ubuntu "instance". Its our own Openstack on our own hardware so I can install this on a very large compute & network resource machine.

note: yes I understand I could deploy juju-gui to a cloud server but then ... that server & the juju-gui would not be utilizing LXC afterwards for deployment of charm services.

I have the same problem as reported in the original post of this bug ... except ... my use case is different.

I created an OpenStack "instance" of ubuntu 14.04.    
I installed juju on that "instance" and configured it for Local Provider (re lxc).
I then bootstrapped and deployed Juju-GUI which successfully installed into its own LXC container.

While logged into the OpenStack Ubuntu "instance" I can obviously ping to/from the juju-gui container and the Ubuntu Host.

However, I thought I could solve that by installing a Reverse Proxy on the OpenStack Ubuntu Host and point it to the 10.0.3.x address of Juju-gui container.

I used NGINX and it almost seems to work.

From my laptop I point Firefox to the 173.39.x.x address  of the Ubuntu Host and the NGINX Proxy starts to redirect to the juju-gui.    I see the Juju-Gui login screen start to appear but it just keeps spinning its circle and is stuck on "Trying to connect to the Juju environment" message.

So I am piggy backing on this Bug report since the resulting message is the same.    I had thought that a Reverse Proxy like this would enable this access.

My use-case is to have people that from their desktop at work use their browser to connect to Juju-Gui then deploy "services" to LXC containers on the OpenStack ubuntu "instance".    Its our own Openstack on our own hardware so I can install this on a very large compute & network resource machine.

note:  yes I understand I could deploy juju-gui to a cloud server but then ... that server & the juju-gui would not be utilizing LXC afterwards for deployment of charm services.