Tungsten Fabric Controller maintenance API¶
The Tungsten Fabric (TF) Controller creates and uses both types of
workloadlocks that include ClusterWorkloadLock and NodeWorkloadLock.
When the ClusterMaintenanceRequest object is created, the TF Controller
verifies the TF cluster health status and proceeds as follows:
If the cluster is
Ready, the TF Controller moves theClusterWorkloadLockobject to the inactive state.Otherwise, the TF Controller keeps the
ClusterWorkloadLockobject in the active state.
When the NodeMaintenanceRequest object is created, the TF Controller
verifies the vRouter pod state on the corresponding node and proceeds as
follows:
If all containers are
Ready, the TF Controller moves theNodeWorkloadLockobject to the inactive state.Otherwise, the TF Controller keeps the
NodeWorkloadLockin the active state.
Note
If there is a NodeWorkloadLock object in the inactive state
present in the cluster, the TF Controller does not process the
NodeMaintenanceRequest object for other nodes until this inactive
NodeWorkloadLock object becomes active.
When the cluster LCM removes the MaintenanceRequest object, the TF
Controller waits for the vRouter pods to become ready and proceeds as follows:
If all containers are in the
Readystate, the TF Controller moves theNodeWorkloadLockobject to the active state.Otherwise, the TF Controller keeps the
NodeWorkloadLockobject in the inactive state.