incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <>
Subject Re: Building SystemVM template appliance
Date Fri, 08 Feb 2013 03:16:07 GMT
I undid your fix :) to leave it modular.
It still builds with the hostname as 'ahha' -- I can't figure out why.

What is left:
 Openswan requires interactive input to install. Previously we had a
pre-baked config.dat that fed into pkg-configure to supply canned
responses. Somehow this needs to be copied into the root directory
(postinstall_files in definition.rb will try to execute it).
One idea is to serve it from the http server that veewee runs to serve the
pressed.cfg file
Another idea is to make it a self-extracting shell file using [1]

Also all the custom config files in patches/systemvm/debian/config needs
to be copied into the vm. Again one can make a self-extracting shell file
or use the http server

Finally, I suspect netinst makes the base system far more bulky than it
needs to be. Some packages need to be trimmed after everything is
installed, apt-get clean needs to run and perhaps some locale data and man
pages need to be nuked.

On 2/7/13 4:22 AM, "Rohit Yadav" <> wrote:

>Okay so I did few fixes, now there is only one script
>which needs to be configured and one can simply port methods from the
>old script and it would run. One only required veewee and no other
>tool to build it, nor it packages any other dependency.
>Now, someone with more experience with systemvm template needs to
>finish the script with up-to-date packages. I'm done
>with basic definitions and code; building may take a lot of time, make
>sure you're good internet connection, it uses NAT to install stuff
>while running on vbox.
>On Thu, Feb 7, 2013 at 8:17 AM, Chiradeep Vittal
><> wrote:
>> It is confusing -- gaah.
>> I could be persuaded that it could be licensed as Apache. But IANAL and
>> went through the legal wringer already on this in Aug/Sep.
>> To build the actual systemvm, I would call another helper script in post
>> install: which replicates the packages() function in
>> To perform the overrides of default config files, it seems we would need
>> the puppet provisioner in vagrant?
>> On 2/5/13 6:49 PM, "Rohit Yadav" <> wrote:
>>>I'm not sure it applies, I did not copy them, veewee generates the
>>>definitions for you which are like stubs and you modify the
>>>definitions as per your needs. MIT should be compatible with APL?
>>>Besides, we're not including veewee in our codebase, they are just
>>>config files for veewee.
>>>This is not something new, we've veewee definitions in
>>>tools/devcloud/src/deps/boxes for devcloud etc. If this is an issue,
>>>we need to fix it there as well.
>>>On Wed, Feb 6, 2013 at 5:24 AM, Chiradeep Vittal
>>><> wrote:
>>>> What I meant was to
>>>>  - retain the MIT license and not change the license
>>>>  - maintain in our repo.
>>>>  - optionally recognize the provenance (either in NOTICE or in the
>>>> directory)
>>>> On 2/5/13 1:44 PM, "Chip Childers" <> wrote:
>>>>>On Tue, Feb 5, 2013 at 2:34 PM, Chiradeep Vittal
>>>>><> wrote:
>>>>>> Rohit,
>>>>>> I see that you have followed the code from
>>>>>> 6-netboot
>>>>>> Since that code is under MIT license:
>>>>>> I think we should not check it in or reproduce the MIT license.
>>>>>Just to be clear, by "reproduce", are you suggesting that we include
>>>>>the legal docs for this?  (assuming that we want to keep it in the
>>>>>repo, which I'm personally a +1 on)
>>>>>> On 2/5/13 4:24 AM, "Rohit Yadav" <> wrote:
>>>>>>>Just wanted to share some wip, based on the way we can build
>>>>>>>and basebox appliance, I've added a template systemvm appliance
>>>>>>>can be built using veewee and currently has VMDK disk image format.
>>>>>>>It's based on Debian b4-i386, has 256MB ram and 2GB HDD. The built
>>>>>>>vbox disk can be exported as ova, raw disk image, qcow2 etc.
>>>>>>>I've put it under tools/appliance. Maybe we should move our
>>>>>>>building code which is in tools/devcloud/src to tools/appliance?
>>>>>>>feel free to hack on it, update the README and scripts.
>>>>>>>We now just need to port the
>>>>>>>to tools/appliance/definitions/systemvmtemplate/ and add
>>>>>>>cleanup code.
>>>>>>> - Install [RVM](
>>>>>>> - Setup paths:  export PATH=~/.rvm/bin:$PATH
>>>>>>> - Install Ruby 1.9.3, if it installed some other version: rvm
>>>>>>>cd tools/appliance
>>>>>>>veewee vbox list
>>>>>>>(Modify scripts in definitions/systemvmtemplate/ as per needs)
>>>>>>>veewee vbox build 'systemvmtemplate'
>>>>>>>veewee vbox up 'systemvmtemplate'  # start the box

View raw message