You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
server: Fix issue with volume resize on VMWare (deploy as-is templates) (#4829)
This PR fixes the issue pertaining to volume resize on VMWare for deploy as-is templates. VMware deploy as-is templates are those that are deployed as per the specification in the imported OVF. Hence override root disk size will not be adhered to for such templates. Moreover, when we deploy VMs in stopped state and resize the volume, the root disk doesn't get resized but the volume size is merely updated in the DB.
This PR also includes the following (for deploy as-is templates):
- Disables overriding root disk size during VM deployment on the UI
- Disables selection of compute offerings with root disk size specified, at the time of deployment
- Provided users with the option to deploy VM is stopped state via UI (so as to give an option to users to resize the volumes before starting the VM)
Co-authored-by: Pearl Dsilva <pearl.dsilva@shapeblue.com>
Copy file name to clipboardExpand all lines: plugins/integrations/kubernetes-service/src/main/java/com/cloud/kubernetes/cluster/actionworkers/KubernetesClusterResourceModifierActionWorker.java
Copy file name to clipboardExpand all lines: plugins/integrations/kubernetes-service/src/main/java/com/cloud/kubernetes/cluster/actionworkers/KubernetesClusterStartWorker.java
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -277,6 +277,7 @@ private UserVm provisionKubernetesClusterMasterVm(final Network network, final S
thrownewInvalidParameterValueException("Failed to deploy Virtual Machine as a service offering with root disk size specified cannot be used with a deploy as-is template");
5278
+
}
5279
+
5280
+
if (cmd.getDetails().get("rootdisksize") != null) {
5281
+
thrownewInvalidParameterValueException("Overriding root disk size isn't supported for VMs deployed from defploy as-is templates");
5282
+
}
5283
+
5284
+
// Bootmode and boottype are not supported on VMWare dpeloy-as-is templates (since 4.15)
5285
+
if ((cmd.getBootMode() != null || cmd.getBootType() != null)) {
5286
+
thrownewInvalidParameterValueException("Boot type and boot mode are not supported on VMware, as we honour what is defined in the template.");
Copy file name to clipboardExpand all lines: ui/public/locales/en.json
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2682,6 +2682,7 @@
2682
2682
"message.delete.vpn.customer.gateway": "Please confirm that you want to delete this VPN Customer Gateway",
2683
2683
"message.delete.vpn.gateway": "Please confirm that you want to delete this VPN Gateway",
2684
2684
"message.deleting.vm": "Deleting VM",
2685
+
"message.deployasis": "Selected template is Deploy As-Is i.e., the VM is deployed by importing an OVA with vApps directly into vCenter. Root disk(s) resize is allowed only on stopped VMs for such templates.",
2685
2686
"message.desc.add.new.lb.sticky.rule": "Add new LB sticky rule",
2686
2687
"message.desc.advanced.zone": "For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support.",
2687
2688
"message.desc.basic.zone": "Provide a single network where each VM instance is assigned an IP directly from the network. Guest isolation can be provided through layer-3 means such as security groups (IP address source filtering).",
0 commit comments