Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose #36

Open
ethernyEonian opened this issue Jul 10, 2015 · 1 comment
Open

Expose #36

ethernyEonian opened this issue Jul 10, 2015 · 1 comment

Comments

@ethernyEonian
Copy link

Hi, it look like when i deploy a charm, it's always exposed, this is normal ?
I want to expose only my choosen services.
If i do :
juju deploy wordpress
juju deploy mysql
and link wordpress to mysql, wordpress is by default exposed.
I try to :
juju unexpose wordpress, but it don't close the 80 http port.

Thank you for your help.

@lazypower
Copy link

The expose command in juju interfaces with intermediary networking routers/firewall implementations. The following providers ship with this by default:

  • Azure
  • OpenStack based clouds
  • AWS

Digital Ocean by default does not have a Zone level firewall that requires 'exposing' - and therefore the command really no-ops other than declaring to the juju state server that these ports should be / are open.

Any further security on the services deployed to DigitalOcean should be done via a subordinate firewall configuration, or by ssh'ing into the machine and setting up your own firewalling scripts.

This is a side-effect of the current state of Juju, and the fact we dont ship with a default firewall in place on the unit/service level.

I'll get a PR for the provider plugin README as a caveat to help shore this up. Thanks for reporting this @ethernyEonian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants