By design, Juju operates a very secure environment for deploying your
applications. Even if you have deployed applications, they won't be publicly
available unless you explicitly make them so. To allow public access to
applications, the appropriate changes must be made to the cloud provider
firewall settings. As the procedure for doing this varies depending on your
cloud, Juju helpfully abstracts this into a single command,
For example, you may have deployed a WordPress application using the relevant charm. Once deployed, the application still cannot be accessed by the public, so you would run:
juju expose wordpress
Juju will then take the steps necessary to adjust firewall rules and any other settings to expose the application via its given address. This process may take anything from a few moments to several minutes. You can check on the current status of your applications by running:
This will return a status report like this:
Model Controller Cloud/Region Version default mycloud google/us-east1 2.0.0 App Version Status Scale Charm Store Rev OS Notes mariadb 10.1.18 active 1 mariadb jujucharms 6 ubuntu wordpress unknown 1 wordpress jujucharms 4 ubuntu exposed Unit Workload Agent Machine Public address Ports Message mariadb/0* active idle 1 18.104.22.168 ready wordpress/0* unknown idle 0 22.214.171.124 80/tcp Machine State DNS Inst id Series AZ 0 started 126.96.36.199 juju-e41c31-0 trusty us-east1-b 1 started 188.8.131.52 juju-e41c31-1 trusty us-east1-c Relation Provides Consumes Type cluster mariadb mariadb peer db mariadb wordpress regular loadbalancer wordpress wordpress peer
As you can see in the above example, the
wordpress app is marked as 'exposed'
in the Notes column, meaning that the application is running and available to
users via its public address of 184.108.40.206.
Note: Exposing the application does not change any DNS or other settings which may be necessary to get your application running as you expect.
To return the firewall settings and make an application non-public again, you
simply need to run the
unexpose command. For example:
juju unexpose wordpress