Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Bigtop >> mail # dev >> Boxgrinder is not actively developed anymore

Copy link to this message
Re: Boxgrinder is not actively developed anymore
I haven't used VMBuilder or imgfac yet, but I will check them out so I can
have a more intelligent 2c to share. I agree with Bruno's requirements,
although I think I can help get us around these two:

* Make it easy to customize images and derive new ones
* No manual steps

I recently hacked my way around Boxgrinder to add a few features, tweaks
and fixes, and having done that, I'd be happy to apply the same ideas to
whatever tool we end up going with (see BIGTOP-871). I suspect that no tool
will be perfect but that the basic principles are similar enough that we
could define a configuration and have it interpreted by various "back-ends"
(which is essentially what I'm doing already, with boxgrinder being the
only "back-end" right now).
On Sat, Mar 16, 2013 at 7:26 PM, Konstantin Boudnik <[EMAIL PROTECTED]> wrote:

> I never been a fun of boxgrinder mostly because of its Ruby'ness and
> fedora/centos centism - distros that I use for pretty much nothing at all -
> and I am glad to see it go.
> That said: why jump on some colledge project with unknown outcome and not
> to
> use something mature? How about vmbuilder? It see to do the job almost
> perfectly, has been around for years and has a huge community.
> Cos
> On Sat, Mar 16, 2013 at 04:04PM, Bruno MahИ wrote:
> > Hi all,
> >
> > I was told that boxgrinder is not actively developed anymore. Given
> > the speed at which distributions and the ruby language evolve, it
> > may even break and not work anymore sooner than later.
> >
> > So I would like to start a conversation to establish a plan for
> > phasing out boxgrinder and to replace it with another solution.
> > From my understanding, people are directed to use imagefactory
> > (http://imgfac.org/).
> > imagefactory seems to have less features than boxgrinder and to use
> > xml files instead of yaml. It would fit the requirements, except
> > that for now, the documentation is pretty sparse and/or outdated. I
> > also cannot make it work after following the doc and poking around
> > for 15min. So until basic image creation works for me, I cannot
> > recommend it.
> > I will try to spend some more time on it though.
> >
> > Would anyone has any other tool they would recommend?
> >
> >
> > But regardless of the tool we pick, we don't have to stop using
> > boxgrinder right away and we don't even have to delete our
> > boxgrinder recipes either.
> > My goal would be to establish a consensus here so we can all put our
> > efforts in common.
> >
> > To me, the requirements for such tool are:
> > * Ability to build images for desktop virtualization
> > * Ability to push images to cloud providers
> > * Make it easy to customize images and derive new ones
> > * No manual steps
> > * Libre software
> >
> > Thanks,
> > Bruno