cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chris snow <chsnow...@gmail.com>
Subject Re: Devcloud 2 - veewee/Vagrant projects
Date Wed, 29 Jan 2014 18:57:19 GMT
I have started thinking about some options:

1)  use packer to convert the devcloud2 veewee definition as a starting point
2) create devcloud3 from scratch
3) start with an existing packer definition (e.g. [1])

Do you have a view on which option may be most suitable?

If we go with option 2 or 3, do you think debian 7.0 should be used as
a starting point, or another version such as 7.2 or 7.3?  Or even
another distro?

Are these goals still valid for devcloud3?

- Two network interfaces, host-only adapter so that the VM is
reachable from host os and a NAT so VMs can access Internet.
- Can be used both as an all in one box solution like the original
DevCloud but the mgmt server and other services can run elsewhere (on
host os).
- Reduce resource requirements, so one could run it in 1G limit.
- Allow multiple DevCloud VMs hosts.
- x86 dom0 and xen-i386 so it runs on all host os.
- Reduce exported appliance (ova) file size.
- It should be seamless, it should work out of the box.

Are there any new requirements in addition to the ones discussed in
this email chain, e.g.

- vagrant support (in addition to the ova/ovf image)
- packer and vagrant build environment


Many thanks,

Chris


[1] https://github.com/opscode/bento/tree/master/packer

On Wed, Jan 29, 2014 at 2:25 PM, Sebastien Goasguen <runseb@gmail.com> wrote:
>
> On Jan 29, 2014, at 8:49 AM, Rohit Yadav <bhaisaab@apache.org> wrote:
>
>> Thanks for stepping in. That is much needed, in fact I think we should
>> use something like packer alongwith vagrant/veewee for both devcloud
>> and systemvmtemplate. Veewee can build vms, packer can export them to
>> various platforms/formats and a developer could use vagrant for local
>> devcloud/host automation.
>>
>
> I looked into it the other day and I agree we need to revamp this.
>
> veewee development and maintenance is going to stop. So we need to prep a packer version
>
> So yes we should create a packer definition for devcloud3 :) and be able to post-process
it to vagrant.
>
>
>
>> Regards.
>>
>> On Wed, Jan 29, 2014 at 1:30 AM, chris snow <chsnow123@gmail.com> wrote:
>>> I would like to build the devcloud2 image [1] from scratch using
>>> veewee (or packer) and turn it into a vagrant box.
>>>
>>> There seems to be several versions of Vagrant files and veewee
>>> definitions in the code base, making it difficult to know which one to
>>> start from, or whether they are still valid.
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>> [1] http://bhaisaab.org/logs/devcloud/
>



-- 
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69

Mime
View raw message