Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Chiradeep.Vittal@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Chiradeep Vittal <Chiradeep.Vittal@citrix.com>
To: CloudStack DeveloperList <cloudstack-dev@incubator.apache.org>
Date: Wed, 19 Dec 2012 11:05:46 -0800
Subject: Re: proper way to fetch system vms
Thread-Topic: proper way to fetch system vms
Thread-Index: Ac3eG9q3kmZBUqWdRWSusmUa93Q1ZQ==
Message-ID: <CCF74F56.3C939%chiradeep.vittal@citrix.com>
In-Reply-To: <20121219184052.GA10182@cloud-2.local>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Certainly the buildsystemvm.sh script can be replaced by veewee automation
followed by qemu-img conversion to the desired hypervisor format.

buildsystemvm.sh originated in pre-vagrant/veewee history and can be
replaced by more modern tools.
The main takeaway from buildsystemvm.sh is the list of packages that are
needed for the systemvm.
That is documented in the packages() function.


On 12/19/12 10:40 AM, "Prasanna Santhanam" <tsp@apache.org> wrote:

>On Wed, Dec 19, 2012 at 01:30:16PM -0500, James Martin wrote:
>> The context of this document is building the devcloud vm that exists
>> in tools/devcloud
>>=20
>> So I've noticed there are at least 2 documented ways to get the
>> console proxy and ssvm.
>>=20
>> 1)
>>=20
>> As document in the original devcloud creation build scripts ( and done
>> in the current puppet scripts)
>>=20
>>         wget=20
>>http://download.cloud.com/templates/devcloud//defaulttemplates/1/dc68eb4c
>>-228c-4a78-84fa-b80ae178fbfd.vhd
>> -P /opt/storage/secondary/template/tmpl/1/1/
>>         wget=20
>>http://download.cloud.com/templates/devcloud//defaulttemplates/1/template
>>.properties
>> -P /opt/storage/secondary/template/tmpl/1/1/
>>         wget=20
>>http://download.cloud.com/templates/devcloud/defaulttemplates/5/ce5b212e-
>>215a-3461-94fb-814a635b2215.vhd
>> -P /opt/storage/secondary/template/tmpl/1/5/
>>         wget=20
>>http://download.cloud.com/templates/devcloud//defaulttemplates/5/template
>>.properties
>> -P /opt/storage/secondary/template/tmpl/1/5/
>>=20
>>=20
>> 2) As documented in:
>>=20
>> http://rohityadav.in/logs/devcloud/ :
>>=20
>> "Preseed the SystemVM templates in /opt/storage/secondary, follow
>> directions from here. Configure NFS server and local storage."
>>=20
>> here points to this link:
>>=20
>>=20
>>http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0
>>-incubating/html/Installation_Guide/management-server-install-flow.html#p
>>repare-system-vm-template
>>=20
>> Which says to use:
>>=20
>>  For XenServer:
>>=20
>>=20
>>/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt
>> -m /mnt/secondary -u
>>=20
>>http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2
>> -h xenserver -s <optional-management-server-secret-key> -F
>>=20
>>=20
>> I've also seen it mentioned that these VMs can be built with maven as
>> well, and it seems to me that should be the best process.  If you are
>> building devcloud from source, shouldn't you also be building the
>> console proxy and secondary storage vms?
>>=20
>> Can we get some consensus on the best way to retrieve these VMs?  Or
>> when is the best time to build them versus downloading pre-built ones?
>>=20
>
>Currently the systemVMs are pre-built and not made into a BYO recipe
>like devcloud. There has been discussion on working in this direction
>but don't think anyone has started work on it yet.
>
>The debian image is right now built using:
>./patches/systemvm/debian/buildsystemvm.sh
>
>Perhaps start from there?
>
>--=20
>Prasanna.,