-
Notifications
You must be signed in to change notification settings - Fork 76
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 ipv6 support for vApp network configuration #550
Conversation
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[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.
Looks good - a few minor comments
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
Signed-off-by: Adam Jasinski <[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.
I am pretty much good to approve, but a few notes here:
- changelog should have a bugfix entry about issue Nil point dereference in govcd.(*VApp).UpdateNetworkAsync #554
- your description of this PR has "closes vcd_vapp_org_network does not work properly with IPv6 networks in NSX-T terraform-provider-vcd#999", but it this still needs to be validated that
vcd_vapp_network
andvcd_vapp_org_network
both work afterwards. (IMO better to close it with Terraform PR if we are sure it fixes it)
Signed-off-by: Adam Jasinski <[email protected]>
Sounds good, updated. |
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! Just a comment:
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Signed-off-by: Adam Jasinski <[email protected]>
Closes #554.
This PR adds support to creating vApp networks using ipv6, as before it would not work because
VAppNetworkConfiguration
didn't haveSubnetPrefixLength
field which is needed for ipv6 handling. https://developer.vmware.com/apis/1507/vmware-cloud-director/doc/doc//types/IpScopeType.htmlPrefixLength
toIPScope
andVappNetworkSettings
structsTest_AddAndRemoveIsolatedVappNetworkIpv6
which tests creation and removal of ipv6 vApp networksWorth noting, that the VCD API returns both
SubnetPrefixLength
andNetmask
on creation of ipv4 networks, but onlySubnetPrefixLength
on creation of ipv6 networks.Also fixes a bug in
UpdateNetworkAsync
, that happened while trying to change fields of un-initializednetworkToUpdate.Configuration.Features
field