When the Operations team add a new device the router.db file will need to be updated. Within the GitLab project, edit the files/rancid/router.db file in the test branch of the repository:
https://git.geant.net/gitlab/puppet-apps/rancid/blob/test/files/rancid/router.db
Add the router in the following format:
mx1.ath2.gr.geant.net:juniper:up
Commit your changes to the GIT repository add the JIRA SYS ticket reference
Raise an IT support ticket, asking the DevOps team to push the puppet configuration to through test, uat and production. As this is a standard change, it can be pushed straight to production.
In the meantime the Operations Centre need to add a special SSH user on the network device, to enable Rancid to connect to the device and retrieve the configuration information
To verify the change, check the router.db file on the production server:
https://prod-rancid.geant.net/cgi-bin/cvsweb.cgi/GEANT/router.db - Check the date time stamp of the file to ensure the change has been pushed by puppet
In addition a new row should exist in the directory list for the new router: https://prod-rancid.geant.net/cgi-bin/cvsweb.cgi/GEANT/configs/