The idea is simple. Dice is a light weight build service for KIWI images with full control over the build power by the user.
At SUSE we have the buildservice which is the full professional version of a build service for packages, images and also products. As a normal user I can provide input and I get some output but I have no control what happens with my data, when it's being processed and where it's being processed. That's by design and works great, thus not meant negatively. I'm a 100% fan of the buildservice
If people have the need for build power on demand or they need a trust model which does not allow to hand over information to other people they are mostly down at the ground level of the basic tools we provide to them. At that level a customer has to deal with several hurdles and I'd like to close this gap a little bit with this project
From a technical perspective my idea includes to provide a public worker machine as an image in one ore more public clouds. I think I will use Amazon EC2 as a start because that's also the biggest player in the field. Users can then run as many instances as they need and can control how much and when they need build power. For those who need privacy the worker machine will also be build as a vagrant box and is offered for download.
A nice little tool called dice makes use of this workers and can control and fire up the jobs whenever it is needed. The project is live on github for further details.
Looking for mad skills in:
ruby rspec ec2 gce kiwi vagrant
This project is part of:
Hack Week 11
Differentiate Microsoft virtualization types (WSL1/WSL2/Azure/Hyper-V) in SUSEConnect by wstephenson
People are interested in Linux on Windows via W...
We are running the geekos app at [geekos.prv.su...
I just recently started a new project which is ...