Skip to content

ClusterSummary

Source code in docs_src/capo_pcs/types/cluster_summary.py 
15
16
17
18
19
20
21
22
23
24
25
26
27
class ClusterSummary(TypedDict, closed=True):
    name: "str"
    """<p>The name that identifies the cluster.</p>"""
    id: "str"
    """<p>The generated unique ID of the cluster.</p>"""
    arn: "str"
    """<p>The unique Amazon Resource Name (ARN) of the cluster.</p>"""
    created_at: "datetime.datetime"
    """<p>The date and time the resource was created.</p>"""
    modified_at: "datetime.datetime"
    """<p>The date and time the resource was modified.</p>"""
    status: "capo_pcs.types.cluster_status.ClusterStatus"
    """<p>The provisioning status of the cluster.</p> <note> <p>The provisioning status doesn't indicate the overall health of the cluster.</p> </note> <important> <p>The resource enters the <code>SUSPENDING</code> and <code>SUSPENDED</code> states when the scheduler is beyond end of life and we have suspended the cluster. When in these states, you can't use the cluster. The cluster controller is down and all compute instances are terminated. The resources still count toward your service quotas. You can delete a resource if its status is <code>SUSPENDED</code>. For more information, see <a href="https://docs.aws.amazon.com/pcs/latest/userguide/slurm-versions_faq.html">Frequently asked questions about Slurm versions in PCS</a> in the <i>PCS User Guide</i>.</p> </important>"""

arn instance-attribute 

arn: str

The unique Amazon Resource Name (ARN) of the cluster.

created_at instance-attribute 

created_at: datetime

The date and time the resource was created.

id instance-attribute 

id: str

The generated unique ID of the cluster.

modified_at instance-attribute 

modified_at: datetime

The date and time the resource was modified.

name instance-attribute 

name: str

The name that identifies the cluster.

status instance-attribute 

status: ClusterStatus

The provisioning status of the cluster.

The provisioning status doesn't indicate the overall health of the cluster.

The resource enters the SUSPENDING and SUSPENDED states when the scheduler is beyond end of life and we have suspended the cluster. When in these states, you can't use the cluster. The cluster controller is down and all compute instances are terminated. The resources still count toward your service quotas. You can delete a resource if its status is SUSPENDED. For more information, see Frequently asked questions about Slurm versions in PCS in the PCS User Guide.