Table of contents

Infrastructure

Update Pingdom IP ranges

Note

This process only applies to Carrenza environments.

The “Check_Pingdom_IP_Ranges” Jenkins job runs every Monday and checks whether the IP addresses we have stored for Pingdom match the ones they are actually using.

If this task fails, it is an indicator that our IPs are not consistent with the ones they are using and we need to update our rules.

Edit the carrenza_mirror_vars.yaml file in the govuk_mirror-deployment. There is a command in the comments of that file that will generate a new list of IP addresses in YAML format.

To check the IP addresses from your own machine, clone the govuk_mirror-deployment and run ruby tools/pingdom_ips.rb.

Once done, run the “Mirror_Network_Config” Jenkins job, setting the environment to “Carrenza” and the component to “Firewall”. You can use the --dry-run extra argument to test what changes the job will make before omitting the argument to actually make the changes.

This page was last reviewed on 2 May 2019. It needs to be reviewed again on 2 November 2019 by the page owner #govuk-2ndline .
This page was set to be reviewed before 2 November 2019 by the page owner #govuk-2ndline. This might mean the content is out of date.