cml-lab-lifecycle

Cisco CML lab lifecycle management is automated by handling lab provisioning, state changes, and teardown through CLI and Slack-driven workflows. This covers creating, starting, stopping, wiping, deleting, and cloning labs deterministically.

Supported Cisco CML lab import and export operations include importing labs, exporting labs, cloning labs, and downloading lab configurations. These functions enable building labs from scratch and modifying existing topologies.

Yes, managing CML labs requires specific environment variables: CML_URL, CML_USERNAME, CML_PASSWORD, and CML_VERIFY_SSL. Setting these enables deterministic and auditable lab operations.

Yes, Slack-driven workflows support starting and stopping CML labs. The lifecycle management tasks cover lab CRUD operations and state management through both CLI and Slack integrations.

The best way to clone an existing Cisco CML lab topology is using the clone_lab operation. It duplicates the lab configuration, allowing you to modify existing topologies without affecting the original environment.

Wiping a CML lab resets the lab state by stopping nodes and clearing runtime data, while deleting a lab removes the topology entirely. Both are distinct lifecycle teardown steps for managing lab environments.