I would really like to see the system vm be built on the management server 
after it's deployed.  There's several reasons for this.

- As contribution grows, the number of items to be put on the system vm will 
likely grow.  CloudStack is built on the principle that it is a software 
collection that can be configured by a software distributor where software 
components can be enabled/disabled so it doesn't make sense that system vms 
come prepackaged with everyone's software.

- Generating the same iso on windows, linux, mac, and also generating agent 
rpms needs a lot of different effort.  When all that's really need is for 
buildsystemvm.sh to be a dynamic package of components as Chiradeep pointed out 
and mkisofs.  Why put all that effort into getting working on all these other 
systems? 

--Alex

> -----Original Message-----
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Wednesday, December 19, 2012 11:06 AM
> To: CloudStack DeveloperList
> Subject: Re: proper way to fetch system vms
> 
> 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" <t...@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
> >>
> >> So I've noticed there are at least 2 documented ways to get the
> >> console proxy and ssvm.
> >>
> >> 1)
> >>
> >> As document in the original devcloud creation build scripts ( and done
> >> in the current puppet scripts)
> >>
> >>         wget
> >>http://download.cloud.com/templates/devcloud//defaulttemplates/1/dc
> 68eb4c
> >>-228c-4a78-84fa-b80ae178fbfd.vhd
> >> -P /opt/storage/secondary/template/tmpl/1/1/
> >>         wget
> >>http://download.cloud.com/templates/devcloud//defaulttemplates/1/te
> mplate
> >>.properties
> >> -P /opt/storage/secondary/template/tmpl/1/1/
> >>         wget
> >>http://download.cloud.com/templates/devcloud/defaulttemplates/5/ce5
> b212e-
> >>215a-3461-94fb-814a635b2215.vhd
> >> -P /opt/storage/secondary/template/tmpl/1/5/
> >>         wget
> >>http://download.cloud.com/templates/devcloud//defaulttemplates/5/te
> mplate
> >>.properties
> >> -P /opt/storage/secondary/template/tmpl/1/5/
> >>
> >>
> >> 2) As documented in:
> >>
> >> http://rohityadav.in/logs/devcloud/ :
> >>
> >> "Preseed the SystemVM templates in /opt/storage/secondary, follow
> >> directions from here. Configure NFS server and local storage."
> >>
> >> here points to this link:
> >>
> >>
> >>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
> >>
> >> Which says to use:
> >>
> >>  For XenServer:
> >>
> >>
> >>/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-
> tmplt
> >> -m /mnt/secondary -u
> >>
> >>http://download.cloud.com/templates/acton/acton-systemvm-
> 02062012.vhd.bz2
> >> -h xenserver -s <optional-management-server-secret-key> -F
> >>
> >>
> >> 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?
> >>
> >> 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?
> >>
> >
> >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?
> >
> >--
> >Prasanna.,

Reply via email to