Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 93A32D1CF for ; Tue, 23 Oct 2012 02:29:57 +0000 (UTC) Received: (qmail 79541 invoked by uid 500); 23 Oct 2012 02:29:57 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 79520 invoked by uid 500); 23 Oct 2012 02:29:57 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 79512 invoked by uid 99); 23 Oct 2012 02:29:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2012 02:29:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of no1lucy@gmail.com designates 209.85.220.47 as permitted sender) Received: from [209.85.220.47] (HELO mail-pa0-f47.google.com) (209.85.220.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2012 02:29:49 +0000 Received: by mail-pa0-f47.google.com with SMTP id fa11so2095379pad.6 for ; Mon, 22 Oct 2012 19:29:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=bsnOuFCvg0+DwbyxTVzf0bZW/S30O5mdST7pCDNpyZY=; b=tXBoGJsOQgyqExcQ9cREtVkcuzVXBb7CKcV7edkbsp2Jt+Mf59AMTw/VATDyyz1sPc 8KPUqxJ38n/twxkFYLuqj3WW9i3Y3OKcSRTmmSXzzfO3C6f67mlBv7tpk7r950YalQX4 SxcxZrfAF+tjNrUODp+27R1xgNXb02nmyLP6L//2gmDY9lnZwm9V9KBXUXkRdB9+mti8 J+z5UKEet4wGU32RpyNdYT9cCsUOztdSWc5R5icDRmYtrXJ6tRtQNt+Bk6j/UPp8Fmus 1JjHBakMaIsQ4CKptQk+Ax7wLg0K054BWSm+sQ+AB8pDl7Ky67aALjg+aC9jgt6Ox9mw 4PXA== Received: by 10.68.136.229 with SMTP id qd5mr35338347pbb.154.1350959367687; Mon, 22 Oct 2012 19:29:27 -0700 (PDT) Received: from LucyPC ([124.42.13.230]) by mx.google.com with ESMTPS id a10sm6850738paz.35.2012.10.22.19.29.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 22 Oct 2012 19:29:26 -0700 (PDT) From: "Lucy" To: References: <7A92FF96DF135843B4B608FB576BFC3E012D9F95E820@SJCPMAILBOX01.citrite.net> In-Reply-To: <7A92FF96DF135843B4B608FB576BFC3E012D9F95E820@SJCPMAILBOX01.citrite.net> Subject: Re: About Allocator algorithm of creating VM on Host Date: Tue, 23 Oct 2012 10:29:10 +0800 Message-ID: <004401cdb0c6$361484e0$a23d8ea0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac2wP/NsVMGUAaJzT9Cvgt2WY5iqUAASF2ZgAA9EgLA= Content-Language: zh-cn X-Virus-Checked: Checked by ClamAV on apache.org Hi Prachi & Tamas , Thanks for the reply. =20 It's very helpful. Thanks, Lucy -----Original Message----- From: Prachi Damle [mailto:Prachi.Damle@citrix.com]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA10=D4=C223=C8=D5 3:09 =CA=D5=BC=FE=C8=CB: cloudstack-users@incubator.apache.org =D6=F7=CC=E2: RE: About Allocator algorithm of creating VM on Host Allocator choices are as described below and the global confg param to = use is 'vm.allocation.algorithm' and is set to randon by default. About detecting 80% CPU/RAM usage - there are various cluster level thresholds one can set through global configurations to track the = capacity usage per cluster. Upon crossing the thresholds, alerts are generated. Also new VM = deployments do not occur above the threshold limits. Thanks, Prachi -----Original Message----- From: Tamas Monos [mailto:tamasm@veber.co.uk]=20 Sent: Monday, October 22, 2012 3:29 AM To: cloudstack-users@incubator.apache.org Subject: RE: About Allocator algorithm of creating VM on Host Hi, The 3.0.2 support the following VM allocation algorithms: 'random', 'firstfit', 'userdispersing', 'userconcentratedpod_random', 'userconcentratedpod_firstfit' You can configure this in the global configuration options. The default = is random I guess. I don't think CloudStack will detect any of those you require however I think hypervisors should. Your hypervisor cluster (I use ESX) will detect issues and send alerts, = I'm sure there is something for xen/kvm as well. Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 = 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: Lucy [mailto:no1lucy@gmail.com] Sent: 22 October 2012 10:45 To: cloudstack-users@incubator.apache.org Subject: About Allocatoralgorithm of creating VM on Host Dear all, =20 =20 I have a question about allocator algorithm of creating VMs on Host. =20 What's the default allocator algorithm to allocate VM on Host in = Cloudstack? =20 And are there any other choice? =20 Can Cloudstack detect heavy loadbalance ,for example one host's = CPU/memory is greater than 80%? =20 Thanks, Lucy =20