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

Set up Stratum 1 in AWS #76

Open
bedroge opened this issue Feb 19, 2021 · 3 comments
Open

Set up Stratum 1 in AWS #76

bedroge opened this issue Feb 19, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@bedroge
Copy link
Collaborator

bedroge commented Feb 19, 2021

No description provided.

@bedroge bedroge added the enhancement New feature or request label Feb 19, 2021
@sassy-crick
Copy link

Some suggestions from trying out the Setup of Stratum-1 in AWS:
GeoIP key request:
It would be good to specify whether we need a license key for geoipupdate version 3.1.1 or newer, or the older version. Without having the software installed it is difficult to know.

In inventory/local_site_specific_vars.yml.example it might be good to comment about whether or not local_cvmfs_http_proxies_allowed_clients: and ocal_cvmfs_http_proxies: need to be commented out or not if you are not using them.

Similarly, in inventory/hosts.example I would do it like that:

[cvmfsstratum1servers]
your-stratum1.org ansible_ssh_user=YOUR-USERNAME

This might be a bit clearer when you look at the example file.

In inventory/host_vars/stratum0host.example :
It might be worth while to put a note in the stratum0host.example to explain that if the cvmfs_srv_device is mounted already, it is not needed and a symlink between the mount point and /srv is all what is required. In my case I added:

# we are not using this here but we are using a symlink which was done
# manually. This was needes as /etc/fstab is using a Label instead of 
# a block device name
# cvmfs_srv_device: /dev/nvme1n1 

One mistake I made is I was running the Ansible command on the machine I wanted to install the stratum1 server. This is probably now what I would do in production. Maybe a comment here might be useful?

Overall, given I got very little experiences with Ansible and with AWS, I think addressing these minor issues should clarify things for the not-so experienced user.

@boegel
Copy link
Contributor

boegel commented Nov 18, 2021

@bedroge This can be closed, no?

@bedroge
Copy link
Collaborator Author

bedroge commented Nov 18, 2021

I think Jörg's feedback still has to be addressed in the docs. I'll try to do that this/next week when updating the docs (there's also that similar issue from Jurij, can do that at the same time).

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

No branches or pull requests

3 participants