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
Copy file name to clipboardExpand all lines: articles/operator-nexus/concepts-commit-workflow-v2.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,19 +62,19 @@ Commit Workflow v2 introduces new operational expectations and constraints to en
62
62
63
63
### Availability & locking rules
64
64
65
-
- Available only on Runtime Version 5.0.1+. Downgrade to v1 is not supported.
65
+
- Available only on Runtime Version 5.0.1+. Downgrade to v1 isn't supported.
66
66
67
67
- Locking is allowed only when:
68
68
69
69
- No commit is in progress.
70
70
71
-
- Fabric is not under maintenance or upgrade.
71
+
- Fabric isn't under maintenance or upgrade.
72
72
73
73
- Fabric is in an administrative enabled state.
74
74
75
75
### Unsupported during maintenance or upgrade
76
76
77
-
`Lock`, `ViewDeviceConfiguration`, and `related post-actions`are not allowed during maintenance or upgrade windows.
77
+
`Lock`, `ViewDeviceConfiguration`, and `related post-actions`aren't allowed during maintenance or upgrade windows.
78
78
79
79
### Commit Finality
80
80
@@ -86,31 +86,31 @@ Once committed, changes **can't be rolled back**. Any further edits require a ne
86
86
87
87
- Reverts all ARM resource changes to their last known good state.
88
88
89
-
- Updates admin/config states (e.g., external/internal networks become disabled and rejected).
89
+
- Updates admin/config states (for example, external/internal networks become disabled and rejected).
90
90
91
-
-Does not delete resources; users must delete them manually if desired.
91
+
-Doesn't delete resources; users must delete them manually if desired.
92
92
93
93
- Enables further patching to reapply changes.
94
94
95
95
- When the discard batch action is performed:
96
96
97
-
- The administrative state of internal/external network resources moves to disabled and their configuration state to rejected; however, the resources are not deleted automatically. A separate delete operation is required for removal.
97
+
- The administrative state of internal/external network resources moves to disabled and their configuration state to rejected; however, the resources aren't deleted automatically. A separate delete operation is required for removal.
98
98
99
-
- Enabled Network Monitor resources attached to a fabric cannot be attached to another fabric unless first detached and committed.
99
+
- Enabled Network Monitor resources attached to a fabric can't be attached to another fabric unless first detached and committed.
100
100
101
-
- For Network Monitor resources in administrative state disabled (in commit queue), discard batch moves the config state to rejected. Users can re-apply updates (PUT/patch) and commit again to enable.
101
+
- For Network Monitor resources in administrative state disabled (in commit queue), discard batch moves the config state to rejected. Users can reapply updates (PUT/patch) and commit again to enable.
102
102
103
103
### Resource update restrictions
104
104
105
-
**Post-lock**, only a limited set of `Create`/`Update`/`Delete` (CUD) actions are supported (e.g., unattached ACLs, TAP rules).
105
+
**Post-lock**, only a limited set of `Create`/`Update`/`Delete` (CUD) actions are supported (for example, unattached ACLs, TAP rules).
106
106
107
107
Device-impacting resources (like Network-to-Network Interconnect (NNI), Isolation Domain (ISD), Route Policy, or ACLs attached to parent resources) are blocked during configuration lock.
108
108
109
109
### Supported resource actions via Commit workflow v2 (when parent resources are in administrative state – Enabled)
110
110
111
111
| **Supported resource actions which require commit workflow** | **Unsupported resource actions which doesn’t require commit workflow** |
| **All resource updates impacting device configuration:**<br>• Updates to Network Fabric resource<br>• Updates to Network-to-Network Interconnect (NNI)<br>• Updates to ISD (L2 and L3)<br>• Creation and updates to Internal and External Networks of enabled L3 ISD<br>• Addition/updates/removal of Route Policy in Internal, External, ISD, and NNI resources<br>• Addition/updates/removal of IP Prefixes, IP Community, and Extended IP Community when attached to Route Policy or Fabric<br>• Addition/updates/removal of ACLs to Internal, External, ISD, and NNI resources<br>• Addition/updates/removal of Network Fabric resource in Network Monitor resource<br>• Additional description updates to Network Device properties<br>• Creation of multiple NNI | **Creation/updating of resources not impacting device configuration:**<br>• Creation of Isolation Domain (ISD) (L3 and L2)<br>• Network Fabric Controller (NFC) creation/updates<br>• Creation and updates to Network TAP rules, Network TAP, Neighbor groups<br>• Creation and updates to Network TAP rules, Network TAP, Neighbor groups<br>• Creation of new Route Policy and connected resources (IP Prefix, IP Community, IP Extended Community)<br>• Update of Route Policy and connected resources when not attached to ISD/Internal/External/NNI<br>• Creation/update of new Access Control List (ACL) which is not attached<br><br>**ARM resources updates only:**<br>• Tag updates for all supported resources<br><br>**Other administrative actions and post actions which manage lifecycle events:**<br>• Enabling/Disabling Isolation Domain (ISD), Return Material Authorization (RMA), Upgrade, and all administrative actions (enable/disable), serial number update<br>• Deletion of all Nexus Network Fabric (NNF) resources |
113
+
| **All resource updates impacting device configuration:**<br>• Updates to Network Fabric resource<br>• Updates to Network-to-Network Interconnect (NNI)<br>• Updates to ISD (L2 and L3)<br>• Creation and updates to Internal and External Networks of enabled L3 ISD<br>• Addition/updates/removal of Route Policy in Internal, External, ISD, and NNI resources<br>• Addition/updates/removal of IP Prefixes, IP Community, and Extended IP Community when attached to Route Policy or Fabric<br>• Addition/updates/removal of ACLs to Internal, External, ISD, and NNI resources<br>• Addition/updates/removal of Network Fabric resource in Network Monitor resource<br>• Additional description updates to Network Device properties<br>• Creation of multiple NNI | **Creation/updating of resources not impacting device configuration:**<br>• Creation of Isolation Domain (ISD) (L3 and L2)<br>• Network Fabric Controller (NFC) creation/updates<br>• Creation and updates to Network TAP rules, Network TAP, Neighbor groups<br>• Creation and updates to Network TAP rules, Network TAP, Neighbor groups<br>• Creation of new Route Policy and connected resources (IP Prefix, IP Community, IP Extended Community)<br>• Update of Route Policy and connected resources when not attached to ISD/Internal/External/NNI<br>• Creation/update of new Access Control List (ACL) which isn't attached<br><br>**ARM resources updates only:**<br>• Tag updates for all supported resources<br><br>**Other administrative actions and post actions which manage lifecycle events:**<br>• Enabling/Disabling Isolation Domain (ISD), Return Material Authorization (RMA), Upgrade, and all administrative actions (enable/disable), serial number update<br>• Deletion of all Nexus Network Fabric (NNF) resources |
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-use-commit-workflow-v2.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Any `patch` operation on parent resources or `Create`/`Update`/`Delete` (CUD) op
32
32
### Step 1: Update resources
33
33
34
34
Make patch or CUD operations via Azure CLI, Portal, or ARM template.
35
-
Once these changes are made, the fabric's configuration state will change to `Accepted (Pending Commit)`.
35
+
Once these changes are made, the fabric's configuration state changes to `Accepted (Pending Commit)`.
36
36
37
37
#### Example scenarios
38
38
@@ -84,7 +84,7 @@ az networkfabric fabric view-device-configuration \
84
84
85
85
### Step 3a: Discard commit batch (Optional)
86
86
87
-
After validating with ViewDeviceConfiguration, users may discard pending configuration updates if issues are found. This restores the ARM resource state to its last known good configuration and resets the fabric state from Accepted & Locked to Succeeded.
87
+
After validating with ViewDeviceConfiguration, users may choose to discard pending configuration updates if issues are found. This operation restores the ARM resource state to its last known good configuration and resets the fabric state from Accepted & Locked to Succeeded.
88
88
89
89
90
90
```Azure CLI
@@ -95,7 +95,7 @@ az networkfabric fabric discard-commit-batch \
95
95
96
96
> [!Note]
97
97
> Internal/External network resources move to Admin State: Disabled and Config State: Rejected.<br>
98
-
> Resources are not deleted — user must delete them manually if required.<br>
98
+
> Resources are not deleted, user must delete them manually if required.<br>
99
99
> Network Monitor handling includes additional constraints (disabled monitors revert to rejected state).<br>
0 commit comments