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

Need playbook to install firewall #12

Open
sromkey opened this issue Dec 5, 2015 · 3 comments
Open

Need playbook to install firewall #12

sromkey opened this issue Dec 5, 2015 · 3 comments

Comments

@sromkey
Copy link

sromkey commented Dec 5, 2015

For using these in a non-Vagrant VM, need to be able to configure a firewall.

@sevein sevein added the P4 label May 13, 2017
@sevein
Copy link
Member

sevein commented Oct 10, 2017

I personally think that's beyond the scope of this repository.

@jhsimpson
Copy link
Member

I think this is well within the scope of the deploy-pub repository. This repo is used to deploy Archivematica projects such as Archivematica and AtoM. Including a firewall is a reasonable choice. Using http://docs.ansible.com/ansible/latest/firewalld_module.html for example, just another playbook in the list of possible playbooks to use?

If not in this repo, then where should a firewall be configured in an Archivematica deployment?

@sevein
Copy link
Member

sevein commented Oct 10, 2017

If not in this repo, then where should a firewall be configured in an Archivematica deployment?

If the user happens to be using Ansible I would assume they're using these playbooks only as a reference and they're part of a bigger setup with a complex directory layout where they manage many other concerns, say backups, load balancing, monitoring, security... where do we draw the line? I'd rather write some recommendations like the following: https://www.accesstomemory.org/en/docs/2.5/admin-manual/security/firewall/#security-firewall - which gives the user a general idea of what's needed to be protected. They should know what to do next as they're running in on an on-premise environment.

@sallain sallain removed the P4 label May 21, 2019
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

4 participants