This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 189
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix: vApp instantiation fails if template has more than one VM (#713)
There is a bug where vApp instantiation fails if the template has multiple VMs and any of VMs has more than one NICs. And, any of NIC is connected to a vDC network. It works fine if VMs are only connected to vApp networks. Existing API was designed on an assumption that there will be only one VM having one NIC. Restructured the code to handle multiple VMs. Behavior will remain same for a single VM template. In case of multiple VMs, customization parameters will be ignored. Testing Done: Ran vapp_tests.py, related tests are passing. Also did manual testing of following scenarions: - Single VM template with one NIC and no customization - Single VM template with one NIC and network customization - Two VMs template with two NICs, one conntected to a vDC network and other to a vApp network
- Loading branch information
Showing
1 changed file
with
181 additions
and
154 deletions.
There are no files selected for viewing
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