Automate CARP activation and parameter preemption
Needs ReviewPublic
Actions

Authored by yousra on Sun, Mar 15, 17:15.

Details

Reviewers

dereckson
Duranzed

Summary

Automate CARP configuration on router nodes. Preemption is also enabled (net.inet.carp.preempt=1) so that the router with the highest priority CARP regains
the MASTER role after recovery or after being start late.

Test Plan

1.Apply the state on router nodes.

2.Verify CARP states (MASTER/BACKUP).

3.Simulate failover and recovery.

4.Verify CARP states (MASTER/BACKUP).

Diff Detail

Repository

rOPS Nasqueron Operations

Lint

Lint Skipped

Unit

No Test Coverage

Branch

role-router

Build Status

Buildable 6476
Build 6760: arc lint + arc unit

Event Timeline

yousra requested review of this revision.Sun, Mar 15, 17:15

yousra created this revision.

Harbormaster completed remote builds in B6473: Diff 10440.Sun, Mar 15, 17:15

dereckson requested changes to this revision.Sun, Mar 15, 20:09

dereckson added inline comments.

roles/core/sysctl/files/sysctl.conf
46	By convention, we call those functions in the .sls, and pass the result here context: is_router: {{ salt["node.has_role"]("router") }}
roles/router/carp/init.sls
19	Not a Jinja template. We can omit that line.

This revision now requires changes to proceed.Sun, Mar 15, 20:09

Changes :

roles/router/carp/files/carp-loader.conf rename on roles/router/carp/files/carp.conf
roles/router/carp/files/carp.conf is not a Jinja template
The Salt function is now called in the state and its result is passed to the template through the context, it is a convention.

Harbormaster completed remote builds in B6476: Diff 10443.Sun, Mar 15, 21:07

dereckson added inline comments.Sun, Mar 15, 21:26