You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn about Commit Workflow v2 process in Azure Operator Nexus – Network Fabric
4
4
author: sushantjrao
5
5
ms.author: sushrao
@@ -19,9 +19,9 @@ With this update, users can lock configuration states, preview device-level chan
19
19
20
20
Commit Workflow v2 is built around a structured change management flow. The following core features are available:
21
21
22
-
-**Explicit configuration locking:** Users must explicitly lock the configuration of a Network Fabric resource after making changes. This ensures updates are applied in a predictable and controlled manner.
22
+
-**Explicit configuration locking:** Users must explicitly lock the configuration of a Network Fabric resource after making changes. This process ensures updates are applied in a predictable and controlled manner.
23
23
24
-
-**Full device configuration preview:** Enables visibility into the exact configuration that will be applied to each device before the commit. This helps validate intent and catch issues early.
24
+
-**Full device configuration preview:** Enables visibility into the exact configuration that is applied to each device before the commit. This helps validate intent and catch issues early.
25
25
26
26
-**Commit configuration to devices**
27
27
Once validated, changes can be committed to the devices. This final step applies the locked configuration updates across the fabric.
@@ -54,52 +54,70 @@ Commit Workflow v2 introduces new operational expectations and constraints to en
54
54
55
55
-**Availability & Irreversibility**
56
56
57
-
Commit Workflow v2 is only available after upgrading to Runtime Version 5.0.1. Once upgraded, reverting to Commit Workflow v1 is not supported.
57
+
Commit Workflow v2 is only available after upgrading to Runtime Version 5.0.1. Once upgraded, reverting to Commit Workflow v1 is n't supported.
58
58
59
59
-**Configuration lock requirements**
60
60
61
61
Locking is only possible when:
62
62
63
-
- There is no ongoing commit operation.
63
+
- There is no ongoing commit operation.
64
64
65
-
- The fabric is not in maintenance or upgrade mode.
65
+
- The fabric is not in maintenance or upgrade mode.
66
66
67
-
- The fabric is in an administrative enabled state.
67
+
- The fabric is in an administrative enabled state.
68
68
69
69
-**Unsupported during maintenance or upgrade**
70
70
71
-
Configuration Lock and View Device Configuration are not allowed during maintenance or upgrade windows.
71
+
Configuration Lock and View Device Configuration aren't allowed during maintenance or upgrade windows.
72
72
73
73
-**Commit is final**
74
74
75
-
Once a configuration is committed, it cannot be rolled back. Future changes must go through another lock-commit cycle.
75
+
Once a configuration is committed, it can't be rolled back. Future changes must go through another lock-commit cycle.
76
76
77
77
### Supported resource actions via Commit workflow v2 (when parent resources are in administrative state – Enabled)
| - Updates to Isolation Domains (L2 and L3) | - Creation and updates to Network TAP rules, Network TAP, Neighbor groups |
85
+
| - Creation and updates to Internal and External Networks of enabled L3 ISD | - Creation of new Route Policy and connected resources (IP Prefix, IP Community, IP Extended Community) |
86
+
| - Addition/updates/removal of Route Policy in Internal, External, ISD, and NNI resources | - Update of Route Policy and connected resources when **not attached** to ISD/Internal/External/NNI |
87
+
| - Addition/updates/removal of IP Prefixes, IP Community, and Extended IP Community when **attached** to Route Policy or Fabric | - Creation/update of new ACL which is **not attached**|
88
+
| - Addition/updates/removal of ACLs to Internal, External, ISD, and NNI resources ||
89
+
| - Addition/updates/removal of Network Fabric resource in Network Monitor resource ||
90
+
| - Additional description updates to Network Device properties ||
91
+
| - Creation of multiple NNI ||
92
+
||**ARM resources updates only:**|
93
+
|| - Tag updates for all supported resources |
94
+
||**Other administrative actions and post actions:**|
95
+
|| - Enabling/Disabling ISD, RMA, Upgrade, and all administrative actions (enable/disable), serial number update <br> - Deletion of all NNF resources |
| Lock Fabric, View Device Config, Commit Config, Check commit status | Other post-actions must be performed before locking |
101
+
Here's a clear, structured table showing **Supported actions post configuration lock is enabled on the fabric**, categorized by type of action and support status:
102
+
103
+
---
104
+
105
+
### **Supported and unsupported actions Post configuration lock**
106
+
107
+
|**Actions**|**Supported resource actions when fabric is under configuration lock**|**Unsupported resource actions when fabric is under configuration lock**|
|**Resource Actions (CUD)**| - **NFC** (Only *Update*)<br>- **Network TAP rules**, **Network TAP**, **Neighbor Group***(Create, Update, Delete)* <br>- **ACL***(Create/Update)* when **not attached** to parent resource<br>- **Network Monitor** created **without Fabric ID**<br>- **Creation/Update** of **IPPrefix**, **IPCommunity List**, **IPExtendedCommunity** when **not attached** to Route Policy<br>- **Read** of all NNF resources<br>- **Delete** of **disabled** resources and **not attached** to any parent resources | - No CUD operations allowed on:<br> • **Network-to-Network Interconnect (NNI)**<br> • **Isolation Domains (L2 & L3)**<br> • **Internal/External Networks** (Additions/Updates)<br> • **Route Policy**, **IPPrefix**, **IPCommunity List**, **IPExtendedCommunity**<br> • **ACLs** when **attached to parent resources** (e.g., NNI, External Network)<br> • **Network Monitor** when **attached to Fabric**<br> • **Deletion** of all **enabled** resources |
110
+
|**Post Actions**| - **Lock Fabric** (administrative state)<br>- **View Device Configuration**<br>- **Commit Configuration**<br>- **ARMConfig Diff** <br>- **Commit batch status**| - All other post actions are **blocked** and must be done **prior to enabling configuration lock**|
111
+
|**Service Actions / Geneva Actions**| - N/A | - **All service actions are blocked**|
112
+
113
+
114
+
### Supported and unsupported actions under administrative lock
0 commit comments