You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been doing daily backups our redis deployments for a long time. We recently performed a 'restore test' to validate that we'd been backing up everything correctly and discovered that we have an issue around redis service. During the test we did 'bosh delete-deployment cf-redis', then redeployed it and restored the data. When BOSH deployed the new VM it did not have the same IP address as the destroyed one. Therefore, even after restoring all of the data redis clients were unable to connect as their service_instances all referenced the old IP address from the deleted deployment.
A simple solution would be to use a DNS name instead of IP address when issuing the service credentials. Setting up a suitable DNS name in bosh-dns is trivial, but it appears that currently there isn't the ability to pass a manifest property for the hostname into the job.
In jobs/cf-redis-broker/templates/broker.yml.erb we can see that the 'host' parameter is using spec.ip
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
The shared-redis broker issues connection details which use the IP address of the redis-broker VM.
We've been doing daily backups our redis deployments for a long time. We recently performed a 'restore test' to validate that we'd been backing up everything correctly and discovered that we have an issue around redis service. During the test we did 'bosh delete-deployment cf-redis', then redeployed it and restored the data. When BOSH deployed the new VM it did not have the same IP address as the destroyed one. Therefore, even after restoring all of the data redis clients were unable to connect as their service_instances all referenced the old IP address from the deleted deployment.
A simple solution would be to use a DNS name instead of IP address when issuing the service credentials. Setting up a suitable DNS name in bosh-dns is trivial, but it appears that currently there isn't the ability to pass a manifest property for the hostname into the job.
In
jobs/cf-redis-broker/templates/broker.yml.erb
we can see that the 'host' parameter is usingspec.ip
I'd like to request the ability to use a DNS name as an alternative to the current 'spec.ip' - This will make backup/restore operations simpler.
The text was updated successfully, but these errors were encountered: