Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates
 74.125.82.48 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Devcloud 2 - veewee/Vagrant projects
From: Sebastien Goasguen <runseb@gmail.com>
In-Reply-To: 
 <CANLSSBWMWd0x=0ZzOO-5SriuCFzqCNCJGdoe4+asa0R=7GJMXQ@mail.gmail.com>
Date: Wed, 29 Jan 2014 09:25:43 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <924534D3-8832-4679-9AE3-E7CEC1568D9B@gmail.com>
References: 
 <CAGWifGJBuAQTmeughq5L8jA-UzPah7HVAVpFZmWeCu9qnyFRmg@mail.gmail.com>
 <CANLSSBWMWd0x=0ZzOO-5SriuCFzqCNCJGdoe4+asa0R=7GJMXQ@mail.gmail.com>
To: dev@cloudstack.apache.org


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.
>=20

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.
>=20
> 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.
>>=20
>> 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.
>>=20
>> Many thanks,
>>=20
>> Chris
>>=20
>> [1] http://bhaisaab.org/logs/devcloud/