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
{{ message }}
Repository navigation
Commit ce38906
Browse filesBrowse the repository at this point in the historyBrowse files
NSX: support segment discovery and security profiles
Allow NSX network offerings to reference existing IP discovery, MAC
discovery, and segment security profiles, and bind them when creating a
segment.
Validate configured profiles and create segment bindings in the same
Policy API request. Remove bindings with their segment while preserving
shared profile definitions, attached-port checks, and retry behavior.
Keep cloned optional details editable, including clearing the last
profile. Reject offering updates and migrations that would change
profiles on an existing network, and correct NSX routed provider maps.
Cover offering creation, clone request handling, migration safeguards,
and segment creation and deletion with API, UI, and SDK regression tests.
@@ -167,7 +166,9 @@ public abstract class NetworkOfferingBaseCmd extends BaseCmd {
167
166
168
167
@Parameter(name = ApiConstants.DETAILS, type = CommandType.MAP, since = "4.2.0", description = "Network offering details in key/value pairs."
169
168
+ " Supported keys are internallbprovider/publiclbprovider with service provider as a value, and"
170
-
+ " promiscuousmode/macaddresschanges/forgedtransmits with true/false as value to accept/reject the security settings if available for a nic/portgroup")
169
+
+ " promiscuousmode/macaddresschanges/forgedtransmits with true/false as value to accept/reject the security settings if available for a nic/portgroup."
170
+
+ " NSX offerings also support nsxipdiscoveryprofileid, nsxmacdiscoveryprofileid, and nsxsegmentsecurityprofileid."
171
+
+ " Values are IDs of existing operator-managed NSX profiles to bind to segments created from the offering.")
0 commit comments