Page MenuHomeSoftware Heritage

pergamon: Add route to staging network to be able to check nodes
ClosedPublic

Authored by ardumont on Sat, Aug 3, 10:39 PM.

Details

Summary

Pergamon being the monitoring server (icinga).

Note:
Implementation wise, this unfolds the current default routes in the yaml.
This also adds one route to the staging network.

This one route was not added as default route since the staging network should
stay separated from the production network.

Related T1785

Test Plan
  1. bin/octocatalog pergamon

diff: adds the one new route to the staging network on pergamon

  1. bin/octocatalog <another-node> (for example worker01)

diff: nothing

Diff Detail

Repository
rSPSITE puppet-swh-site
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

ardumont created this revision.Sat, Aug 3, 10:39 PM
ardumont added inline comments.Mon, Aug 5, 12:14 PM
data/hostname/pergamon.softwareheritage.org.yaml
26

as @ftigeot noticed, this should pass by the staging gateway directly.

I think i made it pass through louvre to avoid duplicating the gateway's production ip twice (one in louvre and one in pergamon)...
But that makes the paquets bounce one more node so i'll skip that and fix it.

Thanks.

ardumont updated this revision to Diff 6114.Mon, Aug 5, 12:25 PM

Pass directly through the gateway node for the staging network paquets

ftigeot accepted this revision.Mon, Aug 5, 12:27 PM
This revision is now accepted and ready to land.Mon, Aug 5, 12:27 PM
ardumont updated this revision to Diff 6116.Mon, Aug 5, 1:45 PM

Plug to production branch

This revision was automatically updated to reflect the committed changes.