Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
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: Chip Childers <chip.childers@sungard.com>,
	"cloudstack-dev@incubator.apache.org" <cloudstack-dev@incubator.apache.org>
CC: Rohit Yadav <bhaisaab@apache.org>, Sheng Yang <Sheng.Yang@citrix.com>
Date: Tue, 5 Feb 2013 15:54:35 -0800
Subject: Re: Building SystemVM template appliance
Thread-Topic: Building SystemVM template appliance
Thread-Index: Ac4D/CaiTGushFVxSHeiZSByT1CXDA==
Message-ID: <CD36DAF8.6A47%chiradeep.vittal@citrix.com>
In-Reply-To: 
 <CA+96GG5rc_+dWu-r4=Da5j5AYR=2AD1WGOZ5mfx629=7pkH9NQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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" <chip.childers@sungard.com> wrote:

>On Tue, Feb 5, 2013 at 2:34 PM, Chiradeep Vittal
><Chiradeep.Vittal@citrix.com> wrote:
>> Rohit,
>> I see that you have followed the code from
>>=20
>>https://github.com/jedi4ever/veewee/tree/master/templates/Debian-7.0-b4-i
>>38
>> 6-netboot
>>
>>
>> Since that code is under MIT license:
>> https://github.com/jedi4ever/veewee/blob/master/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" <bhaisaab@apache.org> wrote:
>>
>>>Just wanted to share some wip, based on the way we can build devcloud
>>>and basebox appliance, I've added a template systemvm appliance which
>>>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 appliance
>>>building code which is in tools/devcloud/src to tools/appliance? Pl.
>>>feel free to hack on it, update the README and scripts.
>>>
>>>We now just need to port the patches/systemvm/debian/buildsystemvm.sh
>>>to tools/appliance/definitions/systemvmtemplate/base.sh and add
>>>cleanup code.
>>>
>>> - Install [RVM](https://rvm.io/rvm/install)
>>> - Setup paths:  export PATH=3D~/.rvm/bin:$PATH
>>> - Install Ruby 1.9.3, if it installed some other version: rvm install
>>>1.9.3
>>>
>>>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
>>>
>>>Regards.
>>
>>