Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Mon, 3 Feb 2014 20:52:47 +0530
From: Prasanna Santhanam <tsp@apache.org>
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] Introduce API returning you an answer from CloudStack
 storage/host allocators whethere there is enough resources for vm deployment
Message-ID: <20140203152247.GA1442@cloud-2.local>
Mail-Followup-To: dev@cloudstack.apache.org
References: <CF117F6D.3F008%alena.prokharchyk@citrix.com>
 <CAKprHVYkFKWa6Y6V9x9YCqHwS7bhC-Dd8A_x81Yh4D6-7PbV4g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAKprHVYkFKWa6Y6V9x9YCqHwS7bhC-Dd8A_x81Yh4D6-7PbV4g@mail.gmail.com>
User-Agent: Mutt/1.5.22 (2013-10-16)

On Mon, Feb 03, 2014 at 09:09:44AM -0500, David Nalley wrote:
> 3. Most importantly deploying a single machine isn't interesting, and
> why would I bother checking. (And this also brings up one of the
> things I find lacking in the deployVM API call.) What I'd be
> interested in knowing is whether I could deploy 5, 50, or 500
> machines. Perhaps adding a count parameter to the deployVirtualMachine
> would help (and the corresponding API call to check that resources are
> available.)

+1 - incredibly useful for large hadoop clusters.

-- 
Prasanna.,

------------------------
Powered by BigRock.com