svc-adm01: split IXP deployment units #91
No reviewers
Labels
No labels
auth
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
management
network
question
services
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dd-ix/nix-config!91
Loading…
Reference in a new issue
No description provided.
Delete branch "ixp-split-deployment"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Split IXP deployment into independent units:
systemctl disabledoesn't work in our setup) @lisketouch /var/lib/arouteserver/kill/$NAME) @liske/var/lib/arouteserver/kill/@MarcelCodingShould the deployment automatically be disabled if the other one (routeserver or switch) failed? Maybe also with some sanity checks? (e.g. verify that the bird rc unit is running?)
Configuring switches is almost independent from the routers (see below) in this context. The deployment services will not run if the
ddix-ixp-build.serviceshas failed or was not run, yet.(Yes some more sanity check should be added inside the ansible deployment like the use of BGP session culling before disabling interfaces. But that is out of scope for the
nix-config.)@ -88,0 +69,4 @@User = "ddix-ix-failed-notification";DynamicUser = true;};script = ''Maybe move that into a variable and reuse it.
I mean that the rs02 should only be deployed if rs01 successes the deployment.
It doesn't matter if the deployment did succeed of the other RS. We must not stop deploying if one of them failed due to hardware failures etc. The deployment won't fail if there are semantic issues in the peering LAN.