cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-6454) Service Offering, cores per socket setting
Date Wed, 08 Feb 2017 09:23:55 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daan Hoogland closed CLOUDSTACK-6454.
-------------------------------------
    Resolution: Won't Fix

> Service Offering, cores per socket setting
> ------------------------------------------
>
>                 Key: CLOUDSTACK-6454
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6454
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1, 4.3.0
>            Reporter: Michael Phillips
>
> When creating a service offering in cloudstack(CS) using multiple "cores" CS, actually
creates the VM in the background with multiple sockets.
>  Example a 6 "core" offering actually translates into a 6 socket offering. This is a
problem on certain OS's and applications like SQL 2012. SQL 2012 has a 4 socket maximum. 
> I propose to fix this by allowing the admin to specify how to arrive at the core count
when creating the service offering. Specifically, the service offering could have a 'cores
per socket' setting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message