Interface DatabaseConfigurationMetadata.Builder

  • Method Details

    • rollbackStatus

      DatabaseConfigurationMetadata.Builder rollbackStatus(String rollbackStatus)

      Whether HyperPod restored the previous accounting database configuration after the change failed. Valid values:

      • NotApplicable: The change failed before HyperPod modified the cluster, for example because the database could not be reached or rejected the credentials, so there was nothing to restore.

      • Reverted: The change failed after it was applied, and HyperPod restored the previous configuration. The cluster continues to use the previous accounting database.

      • RevertFailed: The change failed and HyperPod could not restore the previous configuration, so Slurm accounting on the cluster might not be working.

      This field is omitted when the change succeeds.

      Parameters:
      rollbackStatus - Whether HyperPod restored the previous accounting database configuration after the change failed. Valid values:

      • NotApplicable: The change failed before HyperPod modified the cluster, for example because the database could not be reached or rejected the credentials, so there was nothing to restore.

      • Reverted: The change failed after it was applied, and HyperPod restored the previous configuration. The cluster continues to use the previous accounting database.

      • RevertFailed: The change failed and HyperPod could not restore the previous configuration, so Slurm accounting on the cluster might not be working.

      This field is omitted when the change succeeds.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • rollbackStatus

      Whether HyperPod restored the previous accounting database configuration after the change failed. Valid values:

      • NotApplicable: The change failed before HyperPod modified the cluster, for example because the database could not be reached or rejected the credentials, so there was nothing to restore.

      • Reverted: The change failed after it was applied, and HyperPod restored the previous configuration. The cluster continues to use the previous accounting database.

      • RevertFailed: The change failed and HyperPod could not restore the previous configuration, so Slurm accounting on the cluster might not be working.

      This field is omitted when the change succeeds.

      Parameters:
      rollbackStatus - Whether HyperPod restored the previous accounting database configuration after the change failed. Valid values:

      • NotApplicable: The change failed before HyperPod modified the cluster, for example because the database could not be reached or rejected the credentials, so there was nothing to restore.

      • Reverted: The change failed after it was applied, and HyperPod restored the previous configuration. The cluster continues to use the previous accounting database.

      • RevertFailed: The change failed and HyperPod could not restore the previous configuration, so Slurm accounting on the cluster might not be working.

      This field is omitted when the change succeeds.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • advisory

      Additional information about a change that succeeded, such as an action to take on the cluster.

      Parameters:
      advisory - Additional information about a change that succeeded, such as an action to take on the cluster.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • failureMessage

      DatabaseConfigurationMetadata.Builder failureMessage(String failureMessage)

      An error message describing why the accounting database change failed, and how to resolve it.

      Parameters:
      failureMessage - An error message describing why the accounting database change failed, and how to resolve it.
      Returns:
      Returns a reference to this object so that method calls can be chained together.