Return-Path: 
 <cloudstack-dev-return-8002-apmail-incubator-cloudstack-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B6BFEDDC3
	for <apmail-incubator-cloudstack-dev-archive@minotaur.apache.org>;
 Tue,  2 Oct 2012 14:04:27 +0000 (UTC)
Received: (qmail 70907 invoked by uid 500); 2 Oct 2012 14:04:27 -0000
Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org
Received: (qmail 70629 invoked by uid 500); 2 Oct 2012 14:04:27 -0000
Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cloudstack-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cloudstack-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cloudstack-dev@incubator.apache.org>
List-Id: <cloudstack-dev.incubator.apache.org>
Reply-To: cloudstack-dev@incubator.apache.org
Delivered-To: mailing list cloudstack-dev@incubator.apache.org
Received: (qmail 70495 invoked by uid 99); 2 Oct 2012 14:04:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2012 14:04:27 +0000
X-ASF-Spam-Status: No, hits=1.7 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of cloudchen0620@gmail.com
 designates 209.85.223.175 as permitted sender)
Received: from [209.85.223.175] (HELO mail-ie0-f175.google.com)
 (209.85.223.175)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2012 14:04:19 +0000
Received: by iebc13 with SMTP id c13so15123551ieb.6
        for <multiple recipients>; Tue, 02 Oct 2012 07:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=yLgNnxsh2krIHdh6AMpolEw1P/Wc8HA3VWpAHNUQA50=;
        b=cEx0dtS35cdL/MV2ABKVdWH2wfPBmbrWVRheZtpjFrMyKykPTWeBDuVlJYEuknJOtY
         s+HjRXxZTQB3+VPuaytSRK/t5gf9j4eiG44H4kwl3OAIi5xuJuEJ2Yxhh+ejCSHsm946
         tB2XEfrY+OkGrOXHy9h7oBIGIcpmQMB5fNtEvt0gnEx0Shk1P3PLsYNQ/edXY8RoAf5i
         d2M07NXes+npCfXLeOmKIag4mz4nLijKxOSDP9VvXHHR4NeWcSBpDLlCeofCUGohdhhz
         24kHc68aRZH7X15ts7H3+BK5pl++ozMP8jrhVIxYGji+5D7eOjXKIiKnY6KYf9GoZTIc
         2Guw==
MIME-Version: 1.0
Received: by 10.50.195.161 with SMTP id if1mr8762502igc.66.1349186638161; Tue,
 02 Oct 2012 07:03:58 -0700 (PDT)
Received: by 10.50.209.8 with HTTP; Tue, 2 Oct 2012 07:03:58 -0700 (PDT)
Date: Tue, 2 Oct 2012 22:03:58 +0800
Message-ID: 
 <CANqHH3dwgf+3MRbK4B=bDABdUKbetLMFT5pvWEVkX+xnZAhbMQ@mail.gmail.com>
Subject: How can I specify the vCPU and ram manually?
From: sx chen <cloudchen0620@gmail.com>
To: cloudstack-users@incubator.apache.org, cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=14dae9340e1d4da6fd04cb13fe96

--14dae9340e1d4da6fd04cb13fe96
Content-Type: text/plain; charset=ISO-8859-1

  I can spcify the volume capacity when I deploy a vm using a disk offering
without spcifing disk volume.
How can I specify the vCPU and ram manually.If I have to change some source
code,how can I do?

--14dae9340e1d4da6fd04cb13fe96--