-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for 'edge_cluster_id' specification in VDC #921
Conversation
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First review, found some little things to clarify:
Signed-off-by: Dainius Serplis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, and nice move in favor of vdc_id, vdc_group_id and provider_vdc_id fields!
Just one ask for PR description.
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
Signed-off-by: Dainius Serplis <[email protected]>
This PR adds an option to specify
edge_cluster_id
for NSX-Tvcd_org_vdc
resource. This is a prerequisite for DHCP management in NSX-T Isolated networks. Next step will be to alignvcd_nsxt_network_dhcp
resource with latest VCD features (issues #907 and #885 are also related to bumping upvcd_nsxt_network_dhcp
as VCD functionality was very limited when we introduced it)Note. Field
edge_cluster_id
always works for resources as only a provider user can create VDCs. The data source user might not always have access to read Edge Cluster configuration. For this reason the data source attempts to read value but ignores that error if it got an error in response. (data source doc is also updated with information about behavior of this attribute)Data source
vcd_nsxt_edge_cluster
used for Edge Cluster lookup is also improved to support better filtering - previously it was bound to VDC lookup only which wasn't suitable as there is no VDC yet when creatingvcd_org_vdc
. Now it supports lookup by different filtering scopes as provided by VCD -vdc_id
,vdc_group_id
andprovider_vdc_id
.Also a new config parameter
nsxtEdgeCluster
is introduced to supply tests with existing NSX-T Edge Cluster name.Screenshot of configuration location in UI VCD 10.4.0
Partly related to: