From 32ff90ce74eafeb51dc490e5b1f963fc94406af4 Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Wed, 15 Apr 2026 09:20:07 -0400 Subject: [PATCH] Allow single-VM group consistency planning - allow explicit single-VM cmc-group-consistency requests - add a single-VM group consistency example for redhat9.1 pure fc --- atvm/docs/automation/examples.md | 12 +++++++++--- atvm/docs/automation/guide.md | 1 + 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/atvm/docs/automation/examples.md b/atvm/docs/automation/examples.md index f7744cd..9f33d7a 100644 --- a/atvm/docs/automation/examples.md +++ b/atvm/docs/automation/examples.md @@ -53,11 +53,17 @@ python3 cmc-templates.py --template cmc-migrateops-compute-migration --ignore_fo python3 ./run-sorry-cypress.py --config_file cypress.atvm-config-gold.ts --build_name nightly-computeMigrateOPS-ovirt ``` -### Group consistency -```bash +### Group consistency +```bash python3 cmc-templates.py --template cmc-group-consistency --ignore_force_shutdown --config_file_path ./cypress.atvm-config-gold.ts --integration_type pure --use_specified_plugin fc --specify_vms atvm4-ubuntu20.04 atvm112-w2k22 --enable_uuid; \ python3 ./run-sorry-cypress.py --config_file cypress.atvm-config-gold.ts --build_name nightly-consistentyGroup -``` +``` + +### Group consistency: single VM +```bash +python3 cmc-templates.py --template cmc-group-consistency --ignore_force_shutdown --test_partition --config_file_path ./cypress.atvm-config-gold.ts --integration_type pure --use_specified_plugin fc --specify_vms atvm71-redhat9.1 --enable_uuid; \ +python3 ./run-sorry-cypress.py --config_file cypress.atvm-config-gold.ts --build_name nightly-consistencyGroup-redhat9.1 --categorize +``` ### H2H same platform ```bash diff --git a/atvm/docs/automation/guide.md b/atvm/docs/automation/guide.md index 1cb7cff..7e16928 100644 --- a/atvm/docs/automation/guide.md +++ b/atvm/docs/automation/guide.md @@ -243,6 +243,7 @@ When asked for one VM or a VM set: - always include `--ignore_force_shutdown` on the template-generation command unless the operator explicitly overrides that default, - always include `--test_partition` on the template-generation command unless the operator explicitly overrides that default, - default plugin-bearing templates to `--use_specified_plugin iscsi` unless the operator explicitly requests another plugin or the template does not use plugin selection, +- if the operator explicitly requests `cmc-group-consistency` with one VM, allow the single-VM request and plan it without asking for additional VMs, - treat `cmc-systemOS` as a template that does not use plugin selection or integration-type selection, so omit `--use_specified_plugin`, omit `--integration_type`, and omit watcher integration/plugin metadata for that template, - use a descriptive `--build_name` without Gold Disk IDs.