Redundancy public API questions

Questions related to our redundancy API

  1. Do any of your modules import any Ignition classes under com.inductiveautomation.ignition.gateway.redundancy.*
  2. If yes, what are you using?

Hello from Sepasoft,
We have imports for the following redundancy classes:

com.inductiveautomation.ignition.gateway.redundancy.RedundancyManager;
com.inductiveautomation.ignition.gateway.redundancy.types.ActivityLevel;
com.inductiveautomation.ignition.gateway.redundancy.types.ClusterPeerConnectionStatus;
com.inductiveautomation.ignition.gateway.redundancy.types.NodeRole;
com.inductiveautomation.ignition.gateway.redundancy.types.PeerStatus;
com.inductiveautomation.ignition.gateway.redundancy.types.RedundancyState;
com.inductiveautomation.ignition.gateway.redundancy.types.RedundancyStateListener;
com.inductiveautomation.ignition.gateway.redundancy.types.RuntimeStateProvider;
com.inductiveautomation.ignition.gateway.redundancy.util.ActiveInactiveFilter;

Can you let us know what your use case is for com.inductiveautomation.ignition.gateway.redundancy.types.RuntimeStateProvider ? We need to make sure that your use case can be covered by the redundancy overhaul for 8.3. I am guessing that the other classes you listed are used to react to a change in the redundancy system (going active/inactive, etc).

You're correct the other classes are for monitoring redundancy state change.
We may be able to remove our use of com.inductiveautomation.ignition.gateway.redundancy.types.RuntimeStateProvider it seems to be in code that is no longer in use, it was used to synchronize state that was not stored in the database, however, we've moved nearly all state into the database.

These are the imports in the Cirrus Link modules:

com.inductiveautomation.ignition.gateway.redundancy.RedundancyManager;
com.inductiveautomation.ignition.gateway.redundancy.types.ActivityLevel;
com.inductiveautomation.ignition.gateway.redundancy.types.ClusterPeerConnectionStatus;
com.inductiveautomation.ignition.gateway.redundancy.types.RedundancyState;
com.inductiveautomation.ignition.gateway.redundancy.types.RedundancyStateListener;
com.inductiveautomation.ignition.gateway.redundancy.util.ActiveInactiveFilter;
com.inductiveautomation.ignition.gateway.redundancy.types.NodeRole;

Ok. Let us know if you can't remove that class for some reason. We are planning to remove the class on our end. If you can't remove the class completely, we need to look at providing 8.3-equivalent functionality.

Ok, sounds like you are also using the redundancy classes to monitor and react to activity level. That functionality is still the same for 8.3.