From commits-return-92519-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org  Mon Aug  5 17:23:36 2019
Return-Path: <commits-return-92519-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org>
X-Original-To: archive-asf-public@cust-asf.ponee.io
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [207.244.88.153])
	by mx-eu-01.ponee.io (Postfix) with SMTP id DC0CE180181
	for <archive-asf-public@cust-asf.ponee.io>; Mon,  5 Aug 2019 19:23:35 +0200 (CEST)
Received: (qmail 50047 invoked by uid 500); 5 Aug 2019 17:23:35 -0000
Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:commits@cloudstack.apache.org>
List-Id: <commits.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list commits@cloudstack.apache.org
Received: (qmail 50038 invoked by uid 99); 5 Aug 2019 17:23:35 -0000
Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Aug 2019 17:23:35 +0000
From: GitBox <git@apache.org>
To: commits@cloudstack.apache.org
Subject: [GitHub] [cloudstack] msinhore opened a new issue #3542: The # of CPU_CORE
 capacity has been shown wrongly
Message-ID: <156502581018.22535.7613306447014974324.gitbox@gitbox.apache.org>
Date: Mon, 05 Aug 2019 17:23:30 -0000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

msinhore opened a new issue #3542: The # of CPU_CORE capacity has been shown wrongly
URL: https://github.com/apache/cloudstack/issues/3542
 
 
   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   capacity calculation
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.11
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   The # of CPU_CORE capacity has been shown wrongly when, even considering the operprovisioning factor, the value presented should be for maximum capacity = 100% and no more than this. 
   Example in CloudMonkey command: 
   cloudmonkey list capacity filter=name,percentused, | grep CPU_CORE
   CPU_CORE,195.72
   
   In the UI, the CPU_CORE value, shown out of margin in "Infrastructure > Zones > select zone > Resources"
   
   
   ![Captura de Tela 2019-08-05 às 14 22 08](https://user-images.githubusercontent.com/108022/62482762-73589380-b78c-11e9-8b6c-f95d19778053.png)
   ![Captura de Tela 2019-08-05 às 14 21 56](https://user-images.githubusercontent.com/108022/62482766-75baed80-b78c-11e9-9c2b-d0ceb9569cb1.png)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services