zulip/puppet/kandra/templates/supervisor/conf.d/redis_tunnel.conf.template.erb

[program:redis-tunnel]
command=autossh -M 0 -N -L 127.0.0.1:6379:127.0.0.1:6379 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 <%= @redis_hostname %>
priority=50
user=redistunnel
autostart=true
autorestart=true
redirect_stderr=true
stdout_logfile=/var/log/zulip/redis_tunnel.log
[manual] Use dedicated Redis server for staging Before we deploy this commit, we must migrate the data from the staging redis server to the new, dedicated redis server. The steps for doing so are the following: * Remove the zulip::redis puppet class from staging's zulip.conf * ssh once from staging to redis-staging.zulip.net so that the host key is known * Create a tunnel from redis0.zulip.net to staging.zulip.net * zulip@redis0:~$ ssh -N -L 127.0.0.1:6380:127.0.0.1:6379 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 staging.zulip.net * Set the redis instance on redis0.zulip.net to replicate the one on staging.zulip.net * redis 127.0.0.1:6379> slaveof 127.0.0.1 6380 * Stop the app on staging * Stop redis-server on staging * Promote the redis server on redis0.zulip.net to a master * redis 127.0.0.1:6379> slaveof no one * Do a puppet apply at this commit on staging (this will bring up the tunnel to redis0) * Deploy this commit to staging (start the app on staging) * Kill the tunnel from redis0.zulip.net to staging.zulip.net * Uninstall redis-server on staging The steps for migrating prod will be the same modulo s/staging/prod0/. (imported from commit 546d258883ac299d65e896710edd0974b6bd60f8) 2014-02-05 01:05:27 +01:00			`[program:redis-tunnel]`
puppet: Switch to more explicit variable rather than reuse a nagios one. Redis is not nagios, and this only leads to confusion as to why there is a nagios domain setting on frontend servers; it also leaves the `redis0` part of the name buried in the template. Switch to an explicit variable for the redis hostname. 2021-03-10 00:35:32 +01:00			`command=autossh -M 0 -N -L 127.0.0.1:6379:127.0.0.1:6379 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 <%= @redis_hostname %>`
[manual] Use dedicated Redis server for staging Before we deploy this commit, we must migrate the data from the staging redis server to the new, dedicated redis server. The steps for doing so are the following: * Remove the zulip::redis puppet class from staging's zulip.conf * ssh once from staging to redis-staging.zulip.net so that the host key is known * Create a tunnel from redis0.zulip.net to staging.zulip.net * zulip@redis0:~$ ssh -N -L 127.0.0.1:6380:127.0.0.1:6379 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 staging.zulip.net * Set the redis instance on redis0.zulip.net to replicate the one on staging.zulip.net * redis 127.0.0.1:6379> slaveof 127.0.0.1 6380 * Stop the app on staging * Stop redis-server on staging * Promote the redis server on redis0.zulip.net to a master * redis 127.0.0.1:6379> slaveof no one * Do a puppet apply at this commit on staging (this will bring up the tunnel to redis0) * Deploy this commit to staging (start the app on staging) * Kill the tunnel from redis0.zulip.net to staging.zulip.net * Uninstall redis-server on staging The steps for migrating prod will be the same modulo s/staging/prod0/. (imported from commit 546d258883ac299d65e896710edd0974b6bd60f8) 2014-02-05 01:05:27 +01:00			`priority=50`
puppet: Use a dedicated user for redis tunneling. 2024-01-31 18:07:08 +01:00			`user=redistunnel`
[manual] Use dedicated Redis server for staging Before we deploy this commit, we must migrate the data from the staging redis server to the new, dedicated redis server. The steps for doing so are the following: * Remove the zulip::redis puppet class from staging's zulip.conf * ssh once from staging to redis-staging.zulip.net so that the host key is known * Create a tunnel from redis0.zulip.net to staging.zulip.net * zulip@redis0:~$ ssh -N -L 127.0.0.1:6380:127.0.0.1:6379 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 staging.zulip.net * Set the redis instance on redis0.zulip.net to replicate the one on staging.zulip.net * redis 127.0.0.1:6379> slaveof 127.0.0.1 6380 * Stop the app on staging * Stop redis-server on staging * Promote the redis server on redis0.zulip.net to a master * redis 127.0.0.1:6379> slaveof no one * Do a puppet apply at this commit on staging (this will bring up the tunnel to redis0) * Deploy this commit to staging (start the app on staging) * Kill the tunnel from redis0.zulip.net to staging.zulip.net * Uninstall redis-server on staging The steps for migrating prod will be the same modulo s/staging/prod0/. (imported from commit 546d258883ac299d65e896710edd0974b6bd60f8) 2014-02-05 01:05:27 +01:00			`autostart=true`
			`autorestart=true`
			`redirect_stderr=true`
			`stdout_logfile=/var/log/zulip/redis_tunnel.log`