Populate network mapping from ovf envelope #546
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
On OVF import bind network adapters to the networks specified in the OVF envelope if they exist on the target.
|
thanks @egorovv |
dougm
added a commit
to dougm/govmomi
that referenced
this pull request
May 28, 2020
vCenter doesn't allow duplicate port group names within the network folder when creating via the UI or the AddDVPortgroupTask() API. However, NSXt 3.0 can do so via other (unknown) means. With this condition, govc would fail to map the given network name to its managed object reference. To workaround this, a raw MO ref can now be used in the NetworkMapping, instead of the Network name or inventory path. Related history: 223168f * Add NetworkMapping section to importx options. e3c3cd0 * Populate network mapping from ovf envelope (vmware#546) Fixes vmware#1996
dougm
added a commit
to dougm/govmomi
that referenced
this pull request
May 28, 2020
vCenter doesn't allow duplicate port group names within the network folder when creating via the UI or the AddDVPortgroupTask() API. However, NSXt 3.0 can do so via other (unknown) means. With this condition, govc would fail to map the given network name to its managed object reference. To workaround this, a raw MO ref can now be used in the NetworkMapping, instead of the Network name or inventory path. Related history: 223168f * Add NetworkMapping section to importx options. e3c3cd0 * Populate network mapping from ovf envelope (vmware#546) Fixes vmware#1996
dougm
added a commit
to dougm/govmomi
that referenced
this pull request
May 29, 2020
vCenter doesn't allow duplicate port group names within the network folder when creating via the UI or the AddDVPortgroupTask() API. However, NSXt 3.0 can do so via other (unknown) means. With this condition, govc would fail to map the given network name to its managed object reference. To workaround this, a raw MO ref can now be used in the NetworkMapping, instead of the Network name or inventory path. Related history: 223168f * Add NetworkMapping section to importx options. e3c3cd0 * Populate network mapping from ovf envelope (vmware#546) Fixes vmware#1996
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.
On OVF import bind network adapters to the networks specified in the
OVF envelope if they exist on the target.