kitchen-ci dont have any native lxc based driver, i want get that addressed
first. Current LXC driver uses shell-out to do its magic, which is
Yeah, GoCD is now opensource . Thats why i am building things on top of
it, instead of jenkins.
I too would love to have a SaaS offering, which give vanilla linux kernel.
I dont know much about circle-ci. But i know for fact that travis uses
openvz, and they dont have any plan to move to mainline kernel anytime
soon, so we wont get containers from them. When i used to work at
ThoughtWorks (the company behind GoCD) we had built DevCloud, an internal
SaaS for GoCD farm. Currently they have Snap CI, but i doubt its anything
closer to GoCD (i.e the pipelines, fan-in, fan-out dependencies etc), but
you should definitely talk to them and check if they have any plans to do
Im pretty sure Docker inside LXC will force you to run lxc as root :-(.
It will be awesome if someone starts something like cloudbees, but backed
by GoCD, with multi-tenancy baked in
Till then, I’ll continue improving these tools, and their integration. i.e.
reduce the entry barrier for CI-CD adoption for infrastructure as code.
On Sun, Mar 8, 2015 at 1:20 AM, Torben Knerr firstname.lastname@example.org wrote:
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  if anyone with some lxc background
wants to chime in)
On Sun, Mar 8, 2015 at 6:38 AM, Ranjib Dey email@example.com wrote:
I am happy to announce an opensource project GoatOS. It provides fully
automated CI/CD setup, with agents capable of running unprivileged LXC
containers. These are full blown system containers (running init, cron
unlike docker’s app container (which requires process supervision, runs
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
rpms. container images) and publishing them. I have setup a full blown
pipeline that tests chef, builds omnibus installers, and then use it to
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.