[chef] Re: [announcemnet] GoatOS:: Fully automated CI to build and test chef infrastructure

[Torben Knerr < >]

Nice work Ranjib!

I'm looking into a solution that lets us fully test cookbooks using
kitchenci and LXC containers, and this looks quite promising
(especially since I found out go ci/cd is free now, right?). I would
love to see something like that being available as a SaaS offering
(like travis-ci or cirlceci).

For open source cookbooks circleci got me quite far (you can run lxc
containers inside docker containers there), but I never got it to work
with vagrant-lxc though (see [0] if anyone with some lxc background
wants to chime in)

Hats off!
Torben

[0] https://github.com/fgrehm/vagrant-lxc/issues/339



On Sun, Mar 8, 2015 at 6:38 AM, Ranjib Dey 
<
 >
 wrote:
> Hi all,
> I am happy to announce an opensource project GoatOS. It provides fully
> automated CI/CD setup[1], with agents capable of running unprivileged LXC
> containers. These are full blown system containers (running init, cron etc),
> unlike docker's app container (which requires process supervision, runs as
> privileged mode etc), running  as normal, nono-root user. It also uses
> blender, a modular orchestration framework to run tasks against a set of
> container or agents.
>
> Together, these technologies allows creating arbitrary artifact (like debs,
> rpms. container images) and publishing them. I have setup a full blown build
> pipeline that tests chef, builds omnibus installers, and then use it to test
> community couple of community cookbooks.
>
> I'll be more than happy to get some feedback on this. Currently the whole
> stack is tested against ubuntu 14.04 servers.
>
> regards
> ranjib
>
> [2]https://github.com/GoatOS/Spec
> [1]https://github.com/GoatOS/GoatOS
> [3]https://github.com/GoatOS/go_cd
> [4]https://github.com/GoatOS/container
> [5]https://github.com/PagerDuty/blender
>