-
Notifications
You must be signed in to change notification settings - Fork 17
First versions of Ansible playbooks that seem to work #1
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
Conversation
… the Galaxy repository
zilverberg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
boegel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Critical review, but I'm fairly clueless about CVMFS, so don't let it block you...
…_* variable names) to our (default) EESSI values
|
@boegel I made some changes, and things still seem to work (except for some weird stuff, for which I created two issues). I think I'm done for now first, so please have another look. |
|
This looks good to me know, but I didn't test it myself... Should we let someone else test it before we merge? Maybe @zilverberg or @mvsurf/@casparvl? |
Surf or another party would be preffered, as I would run it on the same hardware/environment as Bob. |
|
It looks like @trz42 (Thomas) is up for it too (based on his reply in Slack). |
rename to compatibility-layer
prepare cfg for NESSI
Move README.eessi and add its info to appropriate role
Initial commit with some configuration and playbooks that seem to work for setting up the stratum 0 and 1, the local proxies, and clients.