Cluster on Demand (COD) is a command-line tool for provisioning and managing NVIDIA Base Command Manager (BCM) clusters on major cloud providers. BCM is a cluster management platform that handles node provisioning, workload scheduling, and software stack deployment across HPC and AI environments.
COD supports managing clusters in AWS, Azure, GCP, and OCI.
Installation
Install COD with the extra for your cloud provider:
pip install cm-cluster-on-demand[aws]
pip install cm-cluster-on-demand[azure]
pip install cm-cluster-on-demand[gcp]
pip install cm-cluster-on-demand[oci]
To install support for multiple providers at once:
pip install cm-cluster-on-demand[aws,azure,gcp,oci]
Usage
Each provider has its own CLI entry point. Use --help to explore all available options:
cm-cod-aws --help
cm-cod-aws cluster create --help
Each provider CLI supports the following commands:
| Command | Description |
|---|---|
cluster create |
Create a new BCM cluster |
cluster list |
List existing clusters |
cluster delete |
Delete a cluster and its cloud resources |
cluster start |
Start head node instances of a stopped cluster |
cluster stop |
Stop all instances of a cluster |
image list |
List available BCM head node images |
The following examples each create a cluster with 5 compute nodes and 1 head node.
AWS
cm-cod-aws cluster create \
--on-error 'cleanup' \
--aws-region 'us-east-1' \
--wlm 'slurm' \
--nodes '5' \
--aws-access-key-id <AWS_ACCESS_KEY_ID> \
--aws-secret-key <AWS_SECRET_KEY> \
--cluster-password <CLUSTER_PASSWORD> \
--license-product-key <LICENSE_PRODUCT_KEY> \
--name mycluster
Azure
cm-cod-azure cluster create \
--on-error 'cleanup' \
--wlm 'slurm' \
--nodes '5' \
--cluster-password <CLUSTER_PASSWORD> \
--license-product-key <LICENSE_PRODUCT_KEY> \
--name mycluster
GCP
cm-cod-gcp cluster create \
--on-error 'cleanup' \
--head-node-zone 'europe-west4-c' \
--wlm 'slurm' \
--nodes '5' \
--project-id <PROJECT_ID> \
--cluster-password <CLUSTER_PASSWORD> \
--license-product-key <LICENSE_PRODUCT_KEY> \
--name mycluster
OCI
cm-cod-oci cluster create \
--on-error 'cleanup' \
--oci-region 'eu-amsterdam-1' \
--wlm 'slurm' \
--nodes '5' \
--oci-tenancy <OCI_TENANCY> \
--oci-user <OCI_USER> \
--oci-fingerprint <OCI_FINGERPRINT> \
--oci-key-file <OCI_KEY_FILE> \
--cluster-password <CLUSTER_PASSWORD> \
--license-product-key <LICENSE_PRODUCT_KEY> \
--name mycluster
Documentation
For full setup and usage documentation, see the Cloudbursting Manual.
Metadata
Release files for cm-cluster-on-demand 11.34.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cm_cluster_on_demand-11.34.0.tar.gz | 409.3 kB | Without provenance | Details for cm_cluster_on_demand-11.34.0.tar.gz |
Release files / cm_cluster_on_demand-11.34.0.tar.gz
| Download URL | cm_cluster_on_demand-11.34.0.tar.gz |
|---|---|
| Size | 409.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49e2e3b66184ce5ca21d9caef41a61d5b4b1f9d96f0bffbc4625cc6a0d538b90
|
|
BLAKE2b-256 checksum How to use checksums |
7ca35cd868ac3c17d0a45f2c6fdbac2a85a2f357dc7643dd02f5961a46f8310d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for cm-cluster-on-demand 11.34.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.