NAS-137503 / 26.04 / TNC support for HA

[sonicaj]

This PR adds changes to properly support TNC on HA systems ensuring heartbeat only runs on master node and relevant bits of TNC only execute where they should.

[bugclerk]

Jira URL: https://ixsystems.atlassian.net/browse/NAS-137503

[ZackaryWelch]

@yocalebo @sonicaj We could still have the heartbeat run on the secondary node. No stats are sent, but alerts are, with 'node' indicating the controller. I now have logic on the backend to parse that and tag the alert by controller, then we can query by 'active' or 'standby'.

[yocalebo]

@yocalebo @sonicaj We could still have the heartbeat run on the secondary node. No stats are sent, but alerts are, with 'node' indicating the controller. I now have logic on the backend to parse that and tag the alert by controller, then we can query by 'active' or 'standby'.

@ZackaryWelch after some more internal discussion, I don't believe sending the heartbeat from passive is necessary. Predominantly because that's not the normal paradigm of how we handle services on HA in general. I believe sending the heartbeat only from the active is sufficient. All data about the other controller can be gleaned from the active.

[ZackaryWelch]

Will we run into any issue with use_all_interfaces as on by default?

[sonicaj]

HA systems are meant to be used using VIP, @yocalebo do you think we should allow specific or all interfaces ?
Basically these attrs control what IPs we send to TNC based on what is configured on selected/all interfaces.

For public or special ip cases, we are allowing that right now separately

[ZackaryWelch]

I agree with disabling that setting for HA, just don't know if there also needs to be a change on registration since it does default to true.