test.

Author: sivakami

.pipelines/swiftv2-long-running/README.md

@@ -34,30 +34,37 @@ This pipeline tests SwiftV2 pod networking in a persistent environment with sche
 **Trigger**: Manual run with parameter change  
 **Purpose**: Create new infrastructure or rebuild existing  
 **Setup Stages**: Enabled via `runSetupStages: true`  
-**Resource Group**: Configurable via parameter
+**Resource Group**: Auto-generated or custom
 
 **To create new infrastructure**:
 1. Go to Pipeline → Run pipeline
-2. **IMPORTANT**: Change `resourceGroupName` to a unique value (e.g., `sv2-long-run-eastus-test2`)
-   - Default uses location: `sv2-long-run-<location>`
-   - To avoid collisions, always use a unique name for new setups
-3. Set `runSetupStages` = `true`
-4. Optionally change `location` if deploying to different region
+2. Set `runSetupStages` = `true`
+3. **Optional**: Leave `resourceGroupName` empty to auto-generate `sv2-long-run-<location>`
+   - Or provide custom name for parallel setups (e.g., `sv2-long-run-eastus-dev`)
+4. Optionally adjust `location`, `vmSkuDefault`, `vmSkuHighNIC`
 5. Run pipeline
 
-**⚠️ Warning**: If you don't change the resource group name when creating a new setup, it will overwrite/conflict with the existing default setup used by scheduled runs!
-
 ## Pipeline Parameters
 
+Parameters are organized by usage:
+
+### Common Parameters (Always Relevant)
+| Parameter | Default | Description |
+|-----------|---------|-------------|
+| `location` | `centraluseuap` | Azure region for resources. Auto-generates RG name: `sv2-long-run-<location>`. |
+| `runSetupStages` | `false` | Set to `true` to create new infrastructure. `false` for scheduled test runs. |
+| `subscriptionId` | `37deca37-...` | Azure subscription ID. |
+| `serviceConnection` | `Azure Container Networking...` | Azure DevOps service connection. |
+
+### Setup-Only Parameters (Only Used When runSetupStages=true)
+
 | Parameter | Default | Description |
 |-----------|---------|-------------|
-| `subscriptionId` | `37deca37-c375-4a14-b90a-043849bd2bf1` | Azure subscription for deployment. |
-| `location` | `centraluseuap` | Azure region for resources. |
-| `resourceGroupName` | `sv2-long-run-<location>` | Static RG name for tests. Dynamically includes region (e.g., `sv2-long-run-centraluseuap`). **MUST be changed to unique value when creating new setup!** |
-| `runSetupStages` | `false` | Set to `true` to create/recreate AKS clusters and networking. **WARNING: Always set unique `resourceGroupName` when true!** |
+| `resourceGroupName` | `""` (empty) | **Leave empty** to auto-generate `sv2-long-run-<location>`. Provide custom name only for parallel setups (e.g., `sv2-long-run-eastus-dev`). |
 | `vmSkuDefault` | `Standard_D4s_v3` | VM SKU for low-NIC node pool (1 NIC). |
 | `vmSkuHighNIC` | `Standard_D16s_v3` | VM SKU for high-NIC node pool (7 NICs). |
-| `serviceConnection` | `Azure Container Networking - Standalone Test Service Connection` | Azure DevOps service connection. |
+
+**Note**: Setup-only parameters are ignored when `runSetupStages=false` (scheduled runs).
 
 ## How It Works
 
@@ -115,22 +122,21 @@ Alternatively, manually trigger with the new location or override `resourceGroup
 
 **Steps**:
 1. Go to Pipeline → Run pipeline
-2. **Change `resourceGroupName`** to a unique value:
+2. Set `runSetupStages` = `true`
+3. **Set `resourceGroupName`** to a unique value:
    - For different region: `sv2-long-run-eastus`
-   - For parallel test: `sv2-long-run-centraluseuap-v2`
-   - For experimental: `sv2-long-run-centraluseuap-experimental`
-3. Set `runSetupStages` = `true`
-4. Optionally change `location` parameter
+   - For parallel test: `sv2-long-run-centraluseuap-dev`
+   - For experimental: `sv2-long-run-centraluseuap-v2`
+   - Or leave empty to use auto-generated `sv2-long-run-<location>`
+4. Optionally adjust `location`, `vmSkuDefault`, `vmSkuHighNIC`
 5. Run pipeline
 
 **After setup completes**:
 - The new infrastructure will be tagged with `SkipAutoDeleteTill=2032-12-31`
-- To run tests against this new setup, either:
-  - **Option A**: Update the pipeline default `resourceGroupName` parameter
-  - **Option B**: Manually trigger test runs with the new `resourceGroupName`
+- Resources are isolated by the unique resource group name
+- To run tests against the new setup, the scheduled pipeline would need to be updated with the new RG name
 
 **Example Scenarios**:
-
 | Scenario | Resource Group Name | Purpose |
 |----------|-------------------|---------|
 | Default production | `sv2-long-run-centraluseuap` | Daily scheduled tests |

.pipelines/swiftv2-long-running/pipeline.yaml

@@ -21,23 +21,24 @@ parameters:
     type: string
     default: "centraluseuap"
 
-  - name: resourceGroupName
-    displayName: "Resource Group Name (Leave empty to auto-generate: sv2-long-run-<location>. Or provide custom name for parallel setups)"
-    type: string
-    default: ""
-
   - name: runSetupStages
-    displayName: "Create new setup(AKS + Network) - WARNING: Use unique resourceGroupName for parallel setups!"
+    displayName: "Create New Infrastructure Setup"
     type: boolean
     default: false
 
+  # Setup-only parameters (only used when runSetupStages=true)
+  - name: resourceGroupName
+    displayName: "[SETUP ONLY] Resource Group Name (empty = auto-generate sv2-long-run-<location>)"
+    type: string
+    default: ""
+
   - name: vmSkuDefault
-    displayName: "VM SKU for Default Node Pool"
+    displayName: "[SETUP ONLY] VM SKU for Default Node Pool"
     type: string
     default: "Standard_D4s_v3"
 
   - name: vmSkuHighNIC
-    displayName: "VM SKU for High NIC Node Pool"
+    displayName: "[SETUP ONLY] VM SKU for High NIC Node Pool"
     type: string
     default: "Standard_D16s_v3"