Skip to content

Note about 'become' functionality in Ansible #18

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.

Sign up for GitHub

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

Merged
boegel merged 2 commits into from
Jun 25, 2020
Merged

Note about 'become' functionality in Ansible #18

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19ff89f
Note about 'become' functionality in Ansible
bedroge Jun 22, 2020
2051315
Update README.md
bedroge Jun 25, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,8 @@ The CVMFS layer of the EESSI project consists of the usual CVMFS infrastructure:
The main prerequisite is Ansible (https://github.com/ansible/ansible),
which can be easily installed via the package manager of most Linux distributions or via `pip install`.
For more details, see the Ansible installation guide: https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html.
Note that Ansible needs to be able to log in to the remote machines where you want to install some CVMFS component,
and needs to be able to use privilege escalation (e.g. `sudo`) on those machines to execute tasks with root permission.

For the installation of all components we make use of two Ansible roles: the CVMFS installation role provided by the Galaxy project (see
https://github.com/galaxyproject/ansible-cvmfs), and a role for adding the EPEL repository (https://github.com/geerlingguy/ansible-role-repo-epel).
Expand Down