Use rsync instead of wget for mirroring group_vars and host_vars #34
Conversation
With the help of the rsync --delete option, this gets rid of files that have been deleted at the source, which can otherwise cause problems. Also, by using rsync instead of wget we save some of our precious cluster insternal bandwidth, since in the vast majority of cases there are no changes.
|
We have this in use now, and it does work as advertised, although I haven't tried reinstalling a node yet. That being said, it should work, as git depends on rsync (repoquery --whatrequires rsync), and git is in the default kickstart packages list. |
|
And yes, just tested that kickstarting also works. |
|
Nice! If I can see clearly now there shouldn't be any issue á la #11 with this - nodes won't get ansible-pull-script.sh + rsync until an admin has run the fgci-install tag. And that tag/role also sets up the rsyncd. |
|
If one wants to be really paranoid one could move setting up rsyncd before generating the new ansible-pull-script.sh in service.yml.. And yes, the rsync daemon is read-only by default. There are ways to have some kind of user/password logins and write support, but it needs to be explicitly configured to be enabled. |
|
In fgci-ansible/devel since fgci-org/fgci-ansible@a1700c0 As I didn't have a host_vars directory then it give an error. Nothing critical though: Feb 1 09:15:03 io-install rsyncd[27614]: rsync: chroot /var/www/html/host_vars failed: No such file or directory (2) Creating that directory in 154bf9f |
With the help of the rsync --delete option, this gets rid of files
that have been deleted at the source, which can otherwise cause
problems.
Also, by using rsync instead of wget we save some of our precious
cluster internal bandwidth, since in the vast majority of cases there
are no changes.