Bug #4699
Vcenter does not honor vmm_exec_vcenter.conf
Status: | Closed | Start date: | 08/03/2016 | ||
---|---|---|---|---|---|
Priority: | High | Due date: | |||
Assignee: | Miguel Ángel Álvarez Cabrerizo | % Done: | 10% | ||
Category: | vCenter | ||||
Target version: | Release 5.4 | ||||
Resolution: | fixed | Pull request: | |||
Affected Versions: | OpenNebula 4.14, OpenNebula 5.0 |
Description
It seems that values set in vmm_exec_vcenter.conf are not read by the driver. In particular NIC model only uses that on the VM definition.
Moreover XML drivers should use XML syntax for the defaults.
Related issues
History
#1 Updated by Carlos Cesario over 4 years ago
Ruben S. Montero wrote:
It seems that values set in vmm_exec_vcenter.conf are not read by the driver. In particular NIC model only uses that on the VM definition.
Moreover XML drivers should use XML syntax for the defaults.
I reproduced it, using OpenNebula 5.1.80.
Changing the /etc/one/vmm_exec/vmm_exec_vcenter.conf file content from NIC=[MODEL="VirtualE1000"] to NIC=[MODEL="virtualvmxnet3"] does not causes effect.
The network driver continue as "VirtualE1000"
Regards,
-Carlos
#2 Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- Assignee set to Miguel Ángel Álvarez Cabrerizo
- % Done changed from 0 to 10
Defaults could be stored in a new file under /etc/one called vcenter_driver.default would be used in the same way for Azure and EC2. E.g to set a default NIC model like VMXNET3 the following file would be used:
<VM>
<TEMPLATE>
<NIC>
<MODEL>vmxnet3</MODEL>
</NIC>
</TEMPLATE>
</VM>
So far I've tested successfully this defaults on vCenter 6 configuring the NIC model if it's not already set on the VM template.
#3 Updated by Ruben S. Montero over 4 years ago
- Related to Bug #4872: vCenter :: Error when create Empty Disk Image added
#4 Updated by Tino Vázquez over 4 years ago
- Target version changed from Release 5.2 to Release 5.4
#5 Updated by Jaime Melis about 4 years ago
- Status changed from New to Closed
- Resolution set to fixed