loyment and running vm, network/router life cycles
should be enough for starters.
Regards.
>
> Thank you,
> Chandan.
>
> -Original Message-
> From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of
> Rohit Yadav
> Sent: Tuesday, February 19, 2013
edure and what needs to be
>tested as a QA effort?
>
>Thank you,
>Chandan.
>
>-Original Message-
>From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of
>Rohit Yadav
>Sent: Tuesday, February 19, 2013 2:31 AM
>To: cloudstack-dev@incubator.apache
Rohit
Yadav
Sent: Tuesday, February 19, 2013 2:31 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Building SystemVM template appliance
On Tue, Feb 19, 2013 at 8:23 AM, Chiradeep Vittal
wrote:
> Hi Rohit
>
>>>
>>> Are the format conversions automated?
>>
>
On Tue, Feb 19, 2013 at 8:23 AM, Chiradeep Vittal
wrote:
> Hi Rohit
>
>>>
>>> Are the format conversions automated?
>>
>>They are now! The file name format is:
>>$appliance-$build_date-$branch-hyperv.$format
>>Format conversion and archiving is automated on a large instance with
>>export formats:
Hi Rohit
>>
>> Are the format conversions automated?
>
>They are now! The file name format is:
>$appliance-$build_date-$branch-hyperv.$format
>Format conversion and archiving is automated on a large instance with
>export formats:
>ova -> vmware
>vhd -> xen
>qcow2 -> kvm
>vhd -> hyperv
>
>Build job
On Fri, Feb 15, 2013 at 12:40 AM, Chiradeep Vittal
wrote:
>
>>
>>To update, I'm able to build a systemvm appliance with vbox and able
>>to convert the disk image to vmdk, hyper-v vhd, qcow2 and ova
>>(vmware), but I've not tested them. Next week, I'll take help from
>>Prasanna to setup a jenkins j
>
>To update, I'm able to build a systemvm appliance with vbox and able
>to convert the disk image to vmdk, hyper-v vhd, qcow2 and ova
>(vmware), but I've not tested them. Next week, I'll take help from
>Prasanna to setup a jenkins job on j.c.o. I cannot do it on b.a.o, as
>I need to test it first
Hi Chiradeep,
>>Okay this is the issue :) I'll fix in preseed.cfg so we'll have only
>>one root partition (and maybe a small swap but not required I think?)
>>like the present systemvm which too has only one / partition, unless
>>you want a different scheme.
>
> Actually prefer different partition
Chiradeep Vittal
>> Cc: Chip Childers; cloudstack-dev@incubator.apache.org; Sheng Yang
>> Subject: Re: Building SystemVM template appliance
>>
>> >>
>> >>> It still builds with the hostname as 'ahha' -- I can't figure out why.
>> >>We can
>> Figured it out: the dhcp server in vbox hands out the dns server of the
>> host (in my case my corporate dns server). Dhclient reverse looks up
>> 10.0.2.15 (the address of the vm) and gets a valid response from the
>> corporate dns server. Annoyingly this is used to name the volume group
>> du
>>
>>> It still builds with the hostname as 'ahha' -- I can't figure out why.
>>We can enforce hostname in one of the postinstall scripts, I found
>>some reference of ahha in config.dat
>
> Figured it out: the dhcp server in vbox hands out the dns server of the
> host (in my case my corporate dns s
>
> Mind reviewing ebe738e (on master) to make sure I interpreted what came
> from Veewee (and what did not) correctly?
Thanks Chip!
>
> -chip
LGTM. Thanks!
On 2/11/13 6:49 PM, "Chip Childers" wrote:
>On Fri, Feb 08, 2013 at 10:19:43AM -0500, Chip Childers wrote:
>> On Thu, Feb 07, 2013 at 07:10:48PM -0800, Chiradeep Vittal wrote:
>> > Thanks Chip. I added some shell scripts in the systemvmtemplate
>>directory
>> > -- not sure if you w
On Fri, Feb 08, 2013 at 10:19:43AM -0500, Chip Childers wrote:
> On Thu, Feb 07, 2013 at 07:10:48PM -0800, Chiradeep Vittal wrote:
> > Thanks Chip. I added some shell scripts in the systemvmtemplate directory
> > -- not sure if you want to add the header to each or leave it to the
> > LICENSE file
On 2/7/13 7:27 PM, "Rohit Yadav" wrote:
>On Fri, Feb 8, 2013 at 8:46 AM, Chiradeep Vittal
> wrote:
>> I undid your fix :) to leave it modular.
>
>:) I made it thinking would be easier to hack only one postinstall.sh
>script. Pl. also backport to 4.1 (CLOUDSTACK-1066's fix version is
>4.1, thoug
On Thu, Feb 07, 2013 at 07:10:48PM -0800, Chiradeep Vittal wrote:
> Thanks Chip. I added some shell scripts in the systemvmtemplate directory
> -- not sure if you want to add the header to each or leave it to the
> LICENSE file
Yeah, all of that needs to be sorted out. We don't want LICENSE files
On Fri, Feb 8, 2013 at 8:46 AM, Chiradeep Vittal
wrote:
> I undid your fix :) to leave it modular.
:) I made it thinking would be easier to hack only one postinstall.sh
script. Pl. also backport to 4.1 (CLOUDSTACK-1066's fix version is
4.1, though in cfg files we use version 4.2?) so we are in sy
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 c
Thanks Chip. I added some shell scripts in the systemvmtemplate directory
-- not sure if you want to add the header to each or leave it to the
LICENSE file
On 2/7/13 12:58 PM, "Chip Childers" wrote:
>On Wed, Feb 06, 2013 at 06:47:28PM -0800, Chiradeep Vittal wrote:
>> It is confusing -- gaah.
>>
On Wed, Feb 06, 2013 at 06:47:28PM -0800, Chiradeep Vittal wrote:
> It is confusing -- gaah.
> I could be persuaded that it could be licensed as Apache. But IANAL and we
> went through the legal wringer already on this in Aug/Sep.
>
IMO, the best thing to do is to reference them as MIT licensed.
Okay so I did few fixes, now there is only one postinstall.sh 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.
Commit:
https://git-wip-us.apache.o
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 we
> went through the legal wringer already on this in Aug/Sep.
>
> To build the actual systemvm, I would call another helper script in post
It is confusing -- gaah.
I could be persuaded that it could be licensed as Apache. But IANAL and we
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: cloudstack.sh which replicates the packages() function in
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 s
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
On Tue, Feb 5, 2013 at 2:34 PM, Chiradeep Vittal
wrote:
> Rohit,
> I see that you have followed the code from
> https://github.com/jedi4ever/veewee/tree/master/templates/Debian-7.0-b4-i38
> 6-netboot
>
>
> Since that code is under MIT license:
> https://github.com/jedi4ever/veewee/blob/master/Lice
Rohit,
I see that you have followed the code from
https://github.com/jedi4ever/veewee/tree/master/templates/Debian-7.0-b4-i38
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 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 exporte
28 matches
Mail list logo
