In preparation for the region migration of beta cluster, we need to ensure that there are no IP addresses for beta hard-coded anywhere in puppet and instead that we switch to using DNS lookups.
|Open||None||T53494 Use Beta cluster as a true canary for code deployments (epic)|
|Open||None||T87220 Minimize differences between beta and production (Tracking)|
|Open||None||T196662 Set up LVS in beta like prod|
|Resolved||bd808||T166396 Program 1 Outcome 4: VPS hosting|
|Resolved||None||T167293 Nova-network to Neutron migration|
|Resolved||Krenair||T208101 Migrate deployment-prep to eqiad1|
|Resolved||mmodell||T208262 Ensure there are no hard-coded IPs in use for beta|
A git grep for 10.68 yields a good amount of stuff related to beta-cluster.
hieradata/labs/deployment-prep/common.yaml 191: - 10.68.23.25:11211:1 # deployment-memc04 192: - 10.68.23.49:11211:1 # deployment-memc05 197: host: 10.68.23.25 # deployment-memc04 200: host: 10.68.23.49 # deployment-memc05 245:"role::url_downloader::url_downloader_ip": 10.68.19.117 # deployment-urldownloader02 329: host: 10.68.19.242 # deployment-redis06 332: host: 10.68.20.16 # deployment-redis06
There is stuff in network::constants as well.
All of the 10.* references in hieradata/labs/deployment-prep/common.yaml are gone now, but a few 172.16.* ones have crept in there as well as in the hiera data managed in Horizon. It turns out that there are at least a few Puppet modules (for example ::profile::mediawiki::nutcracker) that only work with IP addresses.