ReleaseAllResources

  1. TMC MCCS Leaf Node provides API for the ReleaseAllResources workflow.

  2. The TMC MCCS Leaf Node accepts the command if:

    1. Operational state of the TMC MCCS Leaf Node is ON, OFF, INIT, STANDBY, or ALARM.

    2. MCCS master is responsive.(TMC MCCS Leaf Nodes Availability)

  3. The TMC MCCS Leaf Node rejects the command if:

    1. Operational state of the TMC MCCS Leaf Node is FAULT or UNKNOWN.

    2. MCCS master is not responsive.

  4. The command execution involves the following key operations:

    1. Interface schema version is added to the input JSON.

    2. Deprecated flags (e.g., release_all) are removed.

    3. The Release command is invoked on the MCCS Master controller:

      1. If MCCS Master rejects the Release command, failure is reported as ‘RESULT_CODE - FAILED’ on the Long Running Command Result attribute of the MCCS master leaf node.

      2. If MCCS Master accepts the command, the TMC MCCS Leaf Node waits for command completion.

  5. The TMC MCCS Leaf Node monitors the progress of the command via Long Running Command Result:

    1. Command is successful when MCCS Master sends ‘RESULT_CODE - OK’ on the Long Running Command Result attribute. This is reported as ‘RESULT_CODE - OK’ on the same attribute of the MCCS master leaf node.

    2. Command failure is reported in any of the following cases as ‘RESULT_CODE - FAILED’:

      1. MCCS Master sends ‘RESULT_CODE - FAILED’.

      2. The command times out if MCCS Master does not send ‘RESULT_CODE - OK’ within the timeout period specified by the CommandTimeOutDefault property in the Helm chart of the MCCS master leaf node.

  6. Input JSON to the MCCS Master must conform to the schema detailed at:

    https://developer.skao.int/projects/ska-telmodel/en/latest/schemas/mccs/ska-low-mccs-releaseres.html