GabrielBrascher commented on a change in pull request #4722:
URL: https://github.com/apache/cloudstack/pull/4722#discussion_r581497547
##########
File path: server/src/main/java/com/cloud/hypervisor/HypervisorGuruBase.java
##########
@@ -85,6 +89,14 @@
private ServiceOfferingDao _serviceOfferingDao;
@Inject
private NetworkDetailsDao networkDetailsDao;
+ @Inject
+ private HostDao hostDao;
+
+ static final ConfigKey<Boolean>
VmMinMemoryEqualsMemoryDividedByMemOverprovisioningFactor = new
ConfigKey<Boolean>("Advanced", Boolean.class,
"vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor", "true",
+ "If we set this to 'true', a minimum memory (memory/
mem.overprovisioning.factor) will be setted to the VM, independent of using a
scalable service offering or not.", true, ConfigKey.Scope.Cluster);
Review comment:
Please, change from **setted** to **set**
##########
File path: server/src/main/java/com/cloud/hypervisor/HypervisorGuruBase.java
##########
@@ -85,6 +89,14 @@
private ServiceOfferingDao _serviceOfferingDao;
@Inject
private NetworkDetailsDao networkDetailsDao;
+ @Inject
+ private HostDao hostDao;
+
+ static final ConfigKey<Boolean>
VmMinMemoryEqualsMemoryDividedByMemOverprovisioningFactor = new
ConfigKey<Boolean>("Advanced", Boolean.class,
"vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor", "true",
+ "If we set this to 'true', a minimum memory (memory/
mem.overprovisioning.factor) will be setted to the VM, independent of using a
scalable service offering or not.", true, ConfigKey.Scope.Cluster);
+
+ static final ConfigKey<Boolean>
VmMinCpuSpeedEqualsCpuSpeedDividedByCpuOverprovisioningFactor = new
ConfigKey<Boolean>("Advanced", Boolean.class,
"vm.min.cpu.speed.equals.cpu.speed.divided.by.cpu.overprovisioning.factor",
"true",
+ "If we set this to 'true', a minimum cpu speed (cpu speed/
cpu.overprovisioning.factor) will be setted to the VM, independent of using a
scalable service offering or not.", true, ConfigKey.Scope.Cluster);
Review comment:
Same here.
Additionally, what do you think of using **CPU** instead of **cpu** in the
configuration description? (quite a cosmetic change, but IMHO it fits better as
CPU is an acronyms)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
