Skip to content

DatabaseConfigurationMetadata

Source code in docs_src/capo_sagemaker/types/database_configuration_metadata.py 
11
12
13
14
15
16
17
18
19
class DatabaseConfigurationMetadata(TypedDict, closed=True):
    rollback_status: NotRequired[
        "capo_sagemaker.types.database_configuration_rollback_status.DatabaseConfigurationRollbackStatus"
    ]
    """<p>Whether HyperPod restored the previous accounting database configuration after the change failed. Valid values:</p> <ul> <li> <p> <code>NotApplicable</code>: 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.</p> </li> <li> <p> <code>Reverted</code>: The change failed after it was applied, and HyperPod restored the previous configuration. The cluster continues to use the previous accounting database.</p> </li> <li> <p> <code>RevertFailed</code>: The change failed and HyperPod could not restore the previous configuration, so Slurm accounting on the cluster might not be working.</p> </li> </ul> <p>This field is omitted when the change succeeds.</p>"""
    advisory: NotRequired["str"]
    """<p>Additional information about a change that succeeded, such as an action to take on the cluster.</p>"""
    failure_message: NotRequired["str"]
    """<p>An error message describing why the accounting database change failed, and how to resolve it.</p>"""

advisory instance-attribute 

advisory: NotRequired[str]

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

failure_message instance-attribute 

failure_message: NotRequired[str]

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

rollback_status instance-attribute 

rollback_status: NotRequired[DatabaseConfigurationRollbackStatus]

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.