You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by ilya musayev <il...@gmail.com> on 2014/05/27 21:46:06 UTC

[ACS4.3] Cherry pick commit 008b029a29460d883ac7d645877e6f4f2945b1e1 - CLOUDSTACK-5891

Not certain who RM is for minor 4.3.0.x release, please cherry pick this 
commit from 4.4 branch.

If no-one responds, and i hear no objections, i will do this later tonight.

Summary:
CloudStack 4.3.0 does not honor cpu.corespersocket=x template setting 
for vmware
CLOUDSTACK-5891.[VMware] If a template has been registered and 
"cpu.corespersocket...

Commit:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=008b029a29460d883ac7d645877e6f4f2945b1e1



The commit is a bug fix with 3 lines of code:

+             // Check for multi-cores per socket settings
+            String coresPerSocket = 
vmSpec.getDetails().get("cpu.corespersocket");
+            if (coresPerSocket != null) {
+ vmConfigSpec.setNumCoresPerSocket(NumbersUtil.parseInt(coresPerSocket, 
1));
+            }
+

Re: [ACS4.3] Cherry pick commit 008b029a29460d883ac7d645877e6f4f2945b1e1 - CLOUDSTACK-5891

Posted by sebgoa <ru...@gmail.com>.
On May 27, 2014, at 9:46 PM, ilya musayev <il...@gmail.com> wrote:

> Not certain who RM is for minor 4.3.0.x release, please cherry pick this commit from 4.4 branch.

go ahead there is no assign RM for 4.3 minor
> 
> If no-one responds, and i hear no objections, i will do this later tonight.
> 
> Summary:
> CloudStack 4.3.0 does not honor cpu.corespersocket=x template setting for vmware
> CLOUDSTACK-5891.[VMware] If a template has been registered and "cpu.corespersocket...
> 
> Commit:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=008b029a29460d883ac7d645877e6f4f2945b1e1
> 
> 
> 
> The commit is a bug fix with 3 lines of code:
> 
> +             // Check for multi-cores per socket settings
> +            String coresPerSocket = vmSpec.getDetails().get("cpu.corespersocket");
> +            if (coresPerSocket != null) {
> + vmConfigSpec.setNumCoresPerSocket(NumbersUtil.parseInt(coresPerSocket, 1));
> +            }
> +