Page MenuHomeSoftware Heritage

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

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



Pergamon being the monitoring server (icinga).

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

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

Event Timeline


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.


Pass directly through the gateway node for the staging network paquets

This revision is now accepted and ready to land.Aug 5 2019, 12:27 PM

Plug to production branch

This revision was automatically updated to reflect the committed changes.