From users-return-25893-apmail-cloudstack-users-archive=cloudstack.apache.org@cloudstack.apache.org Tue Jun 14 23:10:46 2016 Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D2C68195AB for ; Tue, 14 Jun 2016 23:10:46 +0000 (UTC) Received: (qmail 51717 invoked by uid 500); 14 Jun 2016 23:09:02 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 51690 invoked by uid 500); 14 Jun 2016 23:09:02 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 50993 invoked by uid 99); 14 Jun 2016 23:08:35 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2016 23:08:35 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 02167C1302 for ; Tue, 14 Jun 2016 23:05:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.821 X-Spam-Level: X-Spam-Status: No, score=-0.821 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id qHwaPcOcWHaS for ; Tue, 14 Jun 2016 23:05:38 +0000 (UTC) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id CC17D5FBC5 for ; Tue, 14 Jun 2016 23:05:37 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id hl6so974274pac.2 for ; Tue, 14 Jun 2016 16:05:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-transfer-encoding; bh=OU9Q515J401ZN7zI4hwRprFacyTfZA4OIaosPqG72A8=; b=XOfiKIId98lwb8GaaTHffPS3H/86jK5nJ7pDd8p/gZ4TRUVIlhOap7ianlkYKNZBNr KV+v4E4axfGRUyhJ34hIlZoYHjVqXn7aJjmW9QZw2Ol7jiKXEyVPEuAagw5SS6VRjmUm jhsDWJlViv5AKPbDQU8yfzDVj4umYFP8FEbFZFS4/BH7COCnEpa5lq1nD8qjRqbV3+uB 4tbDvrGGk26z15r64b6URmVgMuJ1IjixWQclGPLaxnKKEUf1z5FFIC42PtR7YZljsjPH VRUKWkbAtUoKR0uYiLM0xiS05mPpO12OrhZz9OqDepPZQZi/ve1Nlpu+9MBtrbOqEC2Y VAaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-transfer-encoding; bh=OU9Q515J401ZN7zI4hwRprFacyTfZA4OIaosPqG72A8=; b=Ij9mGENdOGvUhl0DAXwttzrgkj0oec3IEd7cF1qhNOQSUPjwwmRCsyx+fJ8KsFR7KU FY0nWEDHLRodkQzZMS+5v+azE2JG3OfAX7sCEvdFCCDTW4O+nDhR0Eu0VzWxOqCES62U 1/wVocSNdYW8hCvUnGSTO5/i4Kykra1lo/Qj/bYa5yg1zjfZbYov/dPvw+XGdpoaesBc 2K28oYX34lmGnTgxHhBKTaivQEfy6kFmL+vBSp054PYXBwFoCYut8pyKiNyzVbtgVj0H +gur4ane5doERnIZMpNto0NRutdPfd5kebvpN1IQkWSMeqyRswp93kEabVPI+XZJ4EMR Xrmg== X-Gm-Message-State: ALyK8tLRaZ1mpPS8XcLwS8iKw8TE0Z9ZBh+mai5rKsl22yrWdawVLTw817X2AQ1ao16f6A== X-Received: by 10.66.1.134 with SMTP id 6mr115168pam.15.1465945530928; Tue, 14 Jun 2016 16:05:30 -0700 (PDT) Received: from [0.0.0.0] (dev1.cloudsand.com. [162.243.147.22]) by smtp.gmail.com with ESMTPSA id w194sm39293558pfd.58.2016.06.14.16.05.30 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 14 Jun 2016 16:05:30 -0700 (PDT) Message-ID: <57608DB8.2090502@gmail.com> Date: Tue, 14 Jun 2016 16:05:28 -0700 From: ilya User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: users@cloudstack.apache.org Subject: Re: ACS 4.3 & VMware CPU Allocation References: <001001d1c61b$2c537a60$84fa6f20$@gmail.com> In-Reply-To: <001001d1c61b$2c537a60$84fa6f20$@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit You can pass arbitrary vmware specifc configs for each template that will be exposed in VMX. This is done when you import your template - for example - in cloudmonkey register template format=ova hypervisor=vmware url=http://mywebserver/ovas/ol-5.8-52.ova ispublic=true isfeatured=true passwordenabled=false details[0].rootDiskController=scsi details[0].nicAdapter=Vmxnet3 details[0].keyboard=us details[0].keyboard.typematicMindelay=2000000 ostypeid=146 zoneid=-1 displaytext=OL58-52 name=OL58-52 The "details[0]" argument can be used to feed custom vmware metadata that would enforce the usage of cores vs sockets. Reference: https://issues.apache.org/jira/browse/CLOUDSTACK-5891 Attribute: cpu.corespersocket=X On 6/14/16 2:00 AM, Timothy Lothering wrote: > Hello Community, > > > > We have found a very interesting issue with CPU allocation in ACS 4.3 and > VMware. When a Service Offering is configured, you can choose the number of > Cores and clock speed, which is simple enough. The problem comes in on HOW > the cores are assigned. > > > > In VMware at least, each core is assigned as a vSocket, with 1 vCore. As an > example: > > > > 1. Service Offering defined is 8 Cores @ 2.5GHz, > > 2. Instance is provisioned as 8 vSockets with 1vCore per Socket > > 3. OS displays all 8 "CPUs" > > 4. Happiness! > > > > But, when you are using Core based licensing with products such as Microsoft > SQL 2014 Standard, there is a limit on the number of supported "physical" > sockets, in this case, 4. > > > > So when you run a SQL query/command, only 4 of the 8 cores are used, the > only way around this is to change the VMware settings to 4x vSockets with 2x > vCores per socket. There is a performance hit as described here: > http://blogs.vmware.com/vsphere/2013/10/does-corespersocket-affect-performan > ce.html, but the main issue is that Customers are trying to use all > available resources. > > > > My questions from the info above: > > > > 1. Will there be future support to define vSockets and vCores per > vSocket in a future release of ACS? > > 2. What is the impact on ACS Usage and Management reporting if we change > the vSockets manually? (on VMware itself) > > > > Your insights would be appreciated. > > > > Regards > > > > Tim > > > >