Return-Path: 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 E246BD7DB for ; Wed, 11 Jul 2012 18:06:04 +0000 (UTC) Received: (qmail 81360 invoked by uid 500); 11 Jul 2012 18:06:04 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 81331 invoked by uid 500); 11 Jul 2012 18:06:04 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 81323 invoked by uid 99); 11 Jul 2012 18:06:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2012 18:06:04 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Edison.su@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2012 18:05:58 +0000 X-IronPort-AV: E=Sophos;i="4.77,569,1336363200"; d="scan'208";a="31160825" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Jul 2012 14:05:37 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Wed, 11 Jul 2012 11:05:36 -0700 From: Edison Su To: "cloudstack-dev@incubator.apache.org" Date: Wed, 11 Jul 2012 11:05:36 -0700 Subject: RE: [RFC] DevCloud, an all-in-one-box CloudStack development environment Thread-Topic: [RFC] DevCloud, an all-in-one-box CloudStack development environment Thread-Index: Ac1fhRkcj4yAJEwpRWaY2iRoMzdLjQABpM9A Message-ID: References: <1FD6DA34-02AA-4BE3-9FF5-FBB20C9CC7E6@citrix.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > -----Original Message----- > From: Chip Childers [mailto:chip.childers@sungard.com] > Sent: Wednesday, July 11, 2012 9:49 AM > To: cloudstack-dev@incubator.apache.org > Cc: David Nalley > Subject: Re: [RFC] DevCloud, an all-in-one-box CloudStack development > environment >=20 > On Tue, Jul 10, 2012 at 6:36 PM, Edison Su wrote: > > The base image is easy to be created: > > 1. Ubuntu 12.04 server, fresh installation, few things need to take > into consideration: > > 1) Devcloud vm disk size, is about 20G > > 2) During installation, disk partition should be look like this: > > Root partition: need a separate /opt partition on LVM, which > is used as primary storage and secondary storage. Created on LVM, so > the partition can be extended easily if needed. > > 3) The default installed packages: select SSH server. >=20 > Done, including the VirtualBox Guest Additions kernel modules (so that > vagrant can work). >=20 > > The Vagrant can not act as > https://help.ubuntu.com/12.04/serverguide/jeos-and-vmbuilder.html ? If > it can automate Ubuntu OS installation itself, that will be great... >=20 > I haven't really thought about how to build the "base box" yet, but > that's an infrequent event really. At least we'd have a document about how to setup the "base box", or people = can't reproduce the image. >=20 > > 2. After Server installed, execute: "devcloudsetup.sh -p", will > install xen+xcp, then reboot. >=20 > So a couple of points here: >=20 > 1 - I had initially thought about having "devcloudstetup.sh -p" as > part of the Vagrant provisioning process. Now that I've gone through > it, I don't think that's the right place in the workflow. Unless > anyone objects, I'll do this step as part of the "base box" > preparation. Yes, it should be in the "base box" installation procedure, as it installs = the OS/Hypervisor stuff. >=20 > 2 - The xcp-networking install requires console interaction (AFAIK). > Do you know how to avoid the "bridged vs. ovs" prompt during the > install process? >=20 > 3 - I'm assuming that you used "bridged" for the xcp network config. > Correct? Yes. >=20 > >> 2) steps you took to hack together the CloudStack build / install? > >> > >> For point 2, are you perhaps already looking at fixing the master > >> branch build within Ubuntu 12.04? If not, but you know the steps > you > >> generally took, I can start to look at this after the initial > Vagrant > >> work. > > > > Not yet. I think it's better let me do it, as it takes me a while to > figure it out, what's wrong with the build. Don't waste your time on it. > > I'll work on it tomorrow. >=20 > OK. Let me know if you want any support. >=20 > > 4. Need to document or automate the VirtualBox image or ova > > creating process, such as what's the hardware configuration for the > VM, > > what's the Port Forwarding rules we are using, etc. >=20 > I've got notes for the "base image" creation process, that I can start > to put into a clean location. There are several steps that can be > added around your existing "-p" setup phase. I'm thinking that there > should be an option to specifically configure the OS as a Vagrant base > image, allowing someone that uses VMware or Parallels (or other) to > get to the same point in the process. Agree. If need to install VirtualBox addon in the setupscript, then better = to have an option to enable/disable it. >=20 > Here is the config that I have in the Vagrantfile now: >=20 > Vagrant::Config.run do |config| > config.vm.box =3D "devcloudbase-ubuntu-12-04-64bit" > # TODO: get a place to host the base image > # config.vm.box_url =3D "http://domain.com/path/to/above.box" >=20 > # Uncomment this line to enable the console for debugging the > # build process. > # config.vm.boot_mode =3D :gui >=20 > config.vm.forward_port 22, 2222 > config.vm.forward_port 8080, 8080 > config.vm.forward_port 8443, 8443 > config.vm.forward_port 5901, 5901 > config.vm.forward_port 8787, 8787 > config.vm.forward_port 8250, 8250 > end