GaOrtiga opened a new pull request, #7954:
URL: https://github.com/apache/cloudstack/pull/7954

   ### Description
   
   While creating a VM using VMware, if the template does not have a nic 
adapter configured, CloudStack will default to `E1000`. There is a global 
configuration called `VmwareSystemVmNicDeviceType` that allows the operator to 
choose the default nic adapter for system VMs, however, no such configuration 
exists for user VMs.
   
   A new global configuration was created to allow the operator to choose the 
default nic adapter for user VMs.
   
   <!--- 
*********************************************************************************
 -->
   <!--- NOTE: AUTOMATATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
*********************************************************************************
 -->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [X] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [X] Minor
   
   ### How Has This Been Tested?
   I changed the value of the config to `PCNet32` and verified that the VMs 
deployed after this change had the right nic adapter.
   
   After that I used a template that had a nic adapter configured and verified 
that the value set in the template was respected.
   
   The steps mentioned above were repeated for all the options of the 
configuration.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to