Rudder

Hi Nicolas,

I think it works (although: what would happen with a rsync during a cfagent run?), but I'm not a fan of the introduced hierarchy between relays: the "master" relay becomes a SPOF.
AIUI, if the master dies, the whole infra is stuck (because the slaves are unknown to the policy server, I've no quick way to resume normal conditions, except a backup of the master ; but I don't want to backup relays, they are dispensable, they basically duplicate content from the policy server to share the load).

I'd like to simply put them behind a load balancer: when one relay goes down, I don't even care to restore it, only instanciate a new one from a template, accept it on the policy server & declare it as relay. After the next cf-agent run, it's ready to go. And this is invisible for all my nodes.

Thanks.

Thank you for your answer.
We'll check how to implement this approach, has you have NATed systems, and identify Relay by their Hostname

Hi Lionel,

We gave it some thought, and devised a more robust solution, by introducing "groups" of relays

• each relay will belong to a group with a specific uuid (group is generated by the relay configuration script)
• the relays will expose their group id rather than their own uuid to nodes connecting through them
• the promises generated for relays will be in
  /var/rudder/share/groupid/nodeid
• relays will fetch their promise sbased on the gorup id rather than their own uuid
• ACLs will be computed based on the group id rather than nodeid

1. write the group id to a specific file
2. update the apache config to expose the group id rather that the node id

What do you think of it?

As discussed on IRC yesterday, that looks fine, thanks (why not a checkbox "promises are global to all relays" though?).