TransportNodeCollectionRequestParameters (schema)

Parameters that dictate how operations are processed

Name Description Type Notes

apply_profile Indicates if the Transport Node Profile (TNP) configuration should be applied during creation

This flag should be used when the configuration specified by the
transport_node_profile_id should not be applied to existing hosts
referred to by the compute_collection_id during transport node collection
creation. If this flag is set to false, the TNP configuration will not be
applied to any of the hosts in the cluster during creation. Any transport
node that exists in the cluster that has a different configuration than the
TNP configuration will have the is_overridden flag set to true. This will
result in the transport node collection creation completing with a status
of PROFILE_MISMATCH.

If this flag is set to true, the default value, the TNP configuration will
be applied to all hosts in the cluster during transport node collection
creation.
boolean Default: "True"

override_nsx_ownership Override NSX Ownership

Flag indicating whether the NSX ownership constraints (on Managed Objects like Host/Cluster/DVS) should be
overridden/bypassed.
Note:
Overriding/bypassing NSX ownership constraints is not recommended at all. This indicates, you want to use/configure/own
certain Managed Objects (like Cluster, Host or DVS) which seem to be already in use/configured/owned by some other NSX instance.
This option should be used with caution. It should only be used to come out of situations where:
a. The other NSX instance no longer intends to use the Managed Objects (and has already unconfigured NSX
configurations) but the ownership still lies with it (incorrectly) and you want those Managed Objects to be
used/configured/owned by this NSX instance.
b. The other NSX instance has crashed or decommisioned but the ownership still lies with it and you want those
Managed Objects to be used/configured/owned by this NSX instance.
Enabling this option, while the Managed Objects affected by this operation are actively used by other NSX, can
lead to problematic states on both the NSX instances. For example, if a TN is forcefully reconfigured by this NSX instance
(using override_nsx_ownership=true), while it was already configured and in use by the other NSX instance, it could
corrupt the HostSwitch configurations pushed down by the other NSX instance.
boolean Default: "False"

Name	Description	Type	Notes
apply_profile	Indicates if the Transport Node Profile (TNP) configuration should be applied during creation This flag should be used when the configuration specified by the transport_node_profile_id should not be applied to existing hosts referred to by the compute_collection_id during transport node collection creation. If this flag is set to false, the TNP configuration will not be applied to any of the hosts in the cluster during creation. Any transport node that exists in the cluster that has a different configuration than the TNP configuration will have the is_overridden flag set to true. This will result in the transport node collection creation completing with a status of PROFILE_MISMATCH. If this flag is set to true, the default value, the TNP configuration will be applied to all hosts in the cluster during transport node collection creation.	boolean	Default: "True"
override_nsx_ownership	Override NSX Ownership Flag indicating whether the NSX ownership constraints (on Managed Objects like Host/Cluster/DVS) should be overridden/bypassed. Note: Overriding/bypassing NSX ownership constraints is not recommended at all. This indicates, you want to use/configure/own certain Managed Objects (like Cluster, Host or DVS) which seem to be already in use/configured/owned by some other NSX instance. This option should be used with caution. It should only be used to come out of situations where: a. The other NSX instance no longer intends to use the Managed Objects (and has already unconfigured NSX configurations) but the ownership still lies with it (incorrectly) and you want those Managed Objects to be used/configured/owned by this NSX instance. b. The other NSX instance has crashed or decommisioned but the ownership still lies with it and you want those Managed Objects to be used/configured/owned by this NSX instance. Enabling this option, while the Managed Objects affected by this operation are actively used by other NSX, can lead to problematic states on both the NSX instances. For example, if a TN is forcefully reconfigured by this NSX instance (using override_nsx_ownership=true), while it was already configured and in use by the other NSX instance, it could corrupt the HostSwitch configurations pushed down by the other NSX instance.	boolean	Default: "False"