As an initial implementation, instead of immediately creating a new Salt execution module, I will temporarily use cmd.run to configure CARP.

This approach allows us to configure easily the CARP configuration (rc.conf entries).

This is intended as a short-term solution to validate the configuration and integration with Vault.
A future refactoring may introduce a dedicated a carp execution module for better maintainability and abstraction.

Steps:

• Create the role folder "router"

• Create the required init.sls file

• Create the new state carp.sls inside a folder carp created

• Add a new function (get_carp_entries()) in the file /_modules/node.py to retrive the carp configurations from nodes.sls and test the function (D3979)

• Configure the file carp.sls
  
  --> requires to retrieve the shared secrets from VALT, steps :
  • Add a policy for role router

• Deploy the network configuration to router-002 and router-003 via Salt, and validate CARP is correctly applied.

And then :

We can return to to T2203, and finish the step "Deploy the updated file nodes.sls and apply the configuration via Salt on every machine"