Set up Redis VM, upgrade all cookbooks for Chef 18, major cleanup #496
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/488-redis_server"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This replaces the deprecated redis cookbook. Compiles the latest version of Redis, currently 7.0.11. Running on redis-1. (The database is empty right now, there's no dump to check the backup functionality. It's more convenient to check that after we have data.)
The new redisio cookbook required upgrading to Chef client 16+, so we did a general upgrade of all code to be compatible with 18.x (latest stable). #500 will be a follow-up to complete the Chef 18 upgrades on the actual hosts.
Done in this PR:
Refs #488, #500
I forgot to add the firewall rule to only allow connections to Redis from Zerotier, doing that in a bit. Marking as WIP
Set up Redis using the latest version of redisioto WIP: Set up Redis using the latest version of redisioWIP: Set up Redis using the latest version of redisioto Set up Redis using the latest version of redisio@ -8,4 +8,0 @@
cookbook 'redis',
git: 'https://github.com/phlipper/chef-redis.git',
ref: 'v0.5.6'
cookbook 'redisio', '= 5.0.0' # TODO upgrade to 6.x when we use Chef 16
Are we actually using Chef 16 now on all machines that need Redis? If not, this would break Chef runs...
I just checked the node files. We do need to update Chef on the following machines, they're on Chef 15 and used an older version of the redisio cookbook
I'll take care of that
tomorrowon FridaySet up Redis using the latest version of redisioto Set up Redis using the latest version of redisio & general cookbooks update and cleanupSet up Redis using the latest version of redisio & general cookbooks update and cleanupto Set up Redis VM, upgrade all cookbooks for Chef 18, major cleanup