How to open port with juju when no application is instlaled?

John Meinel john at arbash-meinel.com
Thu Nov 23 18:09:39 UTC 2017


I believe there is an nginx charm, which you could have installed with
"juju deploy nginx --to X"  (where X is the machine id of the postgres
charm), and then used "juju expose nginx".
Is there a reason you prefer to install it manually?
One other option would be to co-locate the "ubuntu" charm and than use open
port from there, if you really don't want any other applications installed.
Generally we model ports-to-be-opened as part of an application, rather
than on a machine. So there's likely to be friction there without an
application to expose.

John
=:->

On Thu, Nov 23, 2017 at 9:54 PM, Akshat Jiwan Sharma <akshatjiwan at gmail.com>
wrote:

> Hi,
>
> I've used juju to deploy postgres on aws. On the same machine I've
> installed an nginx server manually (i.e without juju) that listens on ports
> 80 and 443. I want both of these ports to be open but juju command
> open-port only works when an application is exposed.
>
>
>
> *open-portopen-port registers a port or range to open on the
> public-interface. On public clouds the port will only be open while the
> application is exposed.*
>
> Now according to juju I only have one application (postgres) on my
> machine, that I don't want exposed anyway. However I do want ports 80 and
> 443 to be accessible  publicly. Is adding a policy to aws manually my only
> option here?
>
>
> Thanks,
>
> Akshat
>
>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20171123/e2c5ece7/attachment.html>


More information about the Juju mailing list