Transport node realization data source #949
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ksamoray
force-pushed
the
xportnode_realization
branch
6 times, most recently
from
cb728ac to
a0e91f7
Compare
annakhm
reviewed
Aug 29, 2023
|
|
||
| In addition to arguments listed above, the following attributes are exported: | ||
|
|
||
| * `state` - The realization state of the resource: "pending", "in_progress", "success", "failed", "partial_success", "orphaned", "unknown", "error", "in_sync", "NOT_AVAILABLE", "VM_DEPLOYMENT_QUEUED", "VM_DEPLOYMENT_IN_PROGRESS", "VM_DEPLOYMENT_FAILED", "VM_POWER_ON_IN_PROGRESS", "VM_POWER_ON_FAILED", "REGISTRATION_PENDING", "NODE_NOT_READY", "NODE_READY", "VM_POWER_OFF_IN_PROGRESS", "VM_POWER_OFF_FAILED", "VM_UNDEPLOY_IN_PROGRESS", "VM_UNDEPLOY_FAILED", "VM_UNDEPLOY_SUCCESSFUL", "EDGE_CONFIG_ERROR", "VM_DEPLOYMENT_RESTARTED", "REGISTRATION_FAILED", "TRANSPORT_NODE_SYNC_PENDING", "TRANSPORT_NODE_CONFIGURATION_MISSING", "EDGE_HARDWARE_NOT_SUPPORTED", "MULTIPLE_OVERLAY_TZS_NOT_SUPPORTED", "TN_OVERLAY_TZ_IN_USE_BY_EDGE_CLUSTER", "TZ_ENDPOINTS_NOT_SPECIFIED", "NO_PNIC_PREPARED_IN_EDGE", "APPLIANCE_INTERNAL_ERROR", "VTEP_DHCP_NOT_SUPPORTED", "UNSUPPORTED_HOST_SWITCH_PROFILE", "UPLINK_HOST_SWITCH_PROFILE_NOT_SPECIFIED", "HOSTSWITCH_PROFILE_NOT_FOUND", "LLDP_SEND_ENABLED_NOT_SUPPORTED", "UNSUPPORTED_NAMED_TEAMING_POLICY", "LBSRCID_NOT_SUPPORTED_FOR_EDGE_VM", "LACP_NOT_SUPPORTED_FOR_EDGE_VM", "STANDBY_UPLINKS_NOT_SUPPORTED_FOR_EDGE_VM", "MULTIPLE_ACTIVE_UPLINKS_NOT_SUPPORTED_FOR_EDGE", "UNSUPPORTED_LACP_LB_ALGO_FOR_NODE", "EDGE_NODE_VERSION_NOT_SUPPORTED", "NO_PNIC_SPECIFIED_IN_TN", "INVALID_PNIC_DEVICE_NAME", "TRANSPORT_NODE_READY", "VM_NETWORK_EDIT_PENDING", "UNSUPPORTED_DEFAULT_TEAMING_POLICY", "MPA_DISCONNECTED", "VM_RENAME_PENDING", "VM_CONFIG_EDIT_PENDING", "VM_NETWORK_EDIT_FAILED", "VM_RENAME_FAILED", "VM_CONFIG_EDIT_FAILED", "VM_CONFIG_DISCREPANCY", "VM_NODE_REFRESH_FAILED", "VM_PLACEMENT_REFRESH_FAILED", "REGISTRATION_TIMEDOUT", "REPLACE_FAILED", "UPLINK_FROM_TEAMING_POLICY_NOT_MAPPED", "LOGICAL_SWITCH_NAMED_TEAMING_HAS_NO_PNIC_BACKING", "DELETE_VM_IN_REDEPLOY_FAILED", "DEPLOY_VM_IN_REDEPLOY_FAILED", "INSUFFICIENT_RESOURCES_IN_EDGE_NODE_FOR_SERVICE", "VM_RESOURCE_RESERVATION_FAILED", "DUPLICATE_PNICS_IN_TEAMINGS_WITH_MULTIPLE_UPLINKS_AND_FAILOVER_ORDER", "DUPLICATE_VLANS_SHARING_SAME_PNICMULTIPLE_UPLINKS_IN_NAMED_TEAMING_NOT_SUPPORTED_IF_UPLINK_IN_DEFAULT_TEAMING", "EDGE_NODE_SETTINGS_MISMATCH_RESOLVE", "EDGE_VM_VSPHERE_SETTINGS_MISMATCH_RESOLVE", "EDGE_NODE_SETTINGS_AND_VSPHERE_SETTINGS_ARE_CHANGED_RESOLVE", "EDGE_VSPHERE_LOCATION_MISMATCH_RESOLVE", "COMPUTE_MANAGER_NOT_FOUND", "DELETE_IN_PROGRESS", "ADVANCED_CONFIG_EDIT_FAILED", "UPT_MODE_REALIZATION_POLL_TIMED_OUT", "DATAPATH_CONFIGURATION_EDIT_FAILED", "MAINTENANCE_MODE_ENABLED", "ERROR_IN_ENABLE_MAINTENANCE_MODE", "ERROR_IN_DISABLE_MAINTENANCE_MODE", "CONFIGURE_UPT_ON_VM_FAILED", "VM_VERSION_IS_UPT_INCOMPATIBLE", "DELETE_FAILED_FOR_DIFFERENT_MOREF_ID", "DELETE_FAILED_ON_VM_NOT_FOUND", "DELETE_FAILED_FOR_NON_LCM_EDGE", "ADVANCED_CONFIG_EDIT_PENDING", "DUPLICATE_VLANS_SHARING_SAME_PNIC", "MULTIPLE_UPLINKS_IN_NAMED_TEAMING_NOT_SUPPORTED_IF_UPLINK_IN_DEFAULT_TEAMING", "REDEPLOY_ACTIVITY_FAILED", "REDEPLOY_ACTIVITY_IN_PROGRESS", "REDEPLOY_ACTIVITY_SCHEDULED", "REDEPLOY_ACTIVITY_SUCCESSFUL", "REPLACE_ACTIVITY_FAILED", "REPLACE_ACTIVITY_IN_PROGRESS", "REPLACE_ACTIVITY_SCHEDULED", "REPLACE_ACTIVITY_SUCCESSFUL", "REPLACED_RPC_CLIENT_OF_TN", "RETRYING_REPLACE", "UNABLE_TO_DELETE_EDGE_NODE_VM_INTERNAL_ERROR", "VM_REDEPLOY_FAILED", "VM_RESOURCE_RESERVATION_EDIT_PENDING", "REDEPLOYED_VM_REGISTRATION_PENDING". |
There was a problem hiding this comment.
I suggest to remove the huge list, but mention which states are considered final (triggering data source resolution)
ksamoray
force-pushed
the
xportnode_realization
branch
from
a0e91f7 to
0888478
Compare
annakhm
reviewed
Aug 31, 2023
|
|
||
| In addition to arguments listed above, the following attributes are exported: | ||
|
|
||
| * `state` - The realization state of the resource: "pending", "in_progress", "success", "failed", "partial_success", "orphaned", "unknown", "error", "in_sync". |
There was a problem hiding this comment.
Lets mention which ones of those are target states
ksamoray
force-pushed
the
xportnode_realization
branch
from
0888478 to
63074c9
Compare
Realization data source for nsxt_transport_node resource. Signed-off-by: Kobi Samoray <[email protected]>
ksamoray
force-pushed
the
xportnode_realization
branch
from
63074c9 to
06a1d44
Compare
annakhm
approved these changes
Sep 11, 2023
|
/test-all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Realization data source for nsxt_transport_node resource.