[opensuse-buildservice] Use docker, GCE or amazon for build workers?
Good day to all, Does anyone have an experience of package build in open build system in docker environment? Or using the infrastructure of google compute engine(gce)\amazon? ________________________________________ best regards Konstantin Rudenkov -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 23. Oktober 2014, 19:33:22 wrote Руденков Константин:
Good day to all, Does anyone have an experience of package build in open build system in docker environment? Or using the infrastructure of google compute engine(gce)\amazon?
In short, when you use * chroot: it works of course everywhere, but is unsecure and unclean. * kvm nesting: it works everywhere where you can start kvm guests inside of kvm guests. * direct cloud support: Support for EC2 and openstack is in general in build script, but reality showed so far that it is not much usefull yet. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Adrian, Thank you. I understand perl code very badly. Where can I find documentation of api bs_worker, how it starts/stops VM, how it gets the result back. I couldn't find the solution in the official documentation, or probably couldn't find the way. ________________________________________ best regards Konstantin Rudenkov On Thu, Oct 23, 2014 at 7:37 PM, Adrian Schröter <adrian@suse.de> wrote:
On Donnerstag, 23. Oktober 2014, 19:33:22 wrote Руденков Константин:
Good day to all, Does anyone have an experience of package build in open build system in docker environment? Or using the infrastructure of google compute engine(gce)\amazon?
In short, when you use
* chroot: it works of course everywhere, but is unsecure and unclean. * kvm nesting: it works everywhere where you can start kvm guests inside of kvm guests. * direct cloud support: Support for EC2 and openstack is in general in build script, but reality showed so far that it is not much usefull yet.
--
Adrian Schroeter email: adrian@suse.de
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 23. Oktober 2014, 22:50:14 wrote Konstantin Rudenkov:
Adrian, Thank you. I understand perl code very badly. Where can I find documentation of api bs_worker, how it starts/stops VM, how it gets the result back.
It is bash code mostly in https://github.com/openSUSE/obs-build check the build-vm-ec2 and -openstack files in first place.
I couldn't find the solution in the official documentation, or probably couldn't find the way.
right, it works not good enough to my opinion that it is worth to be documented right now. The EC2 approach most likely will never work good engough, because amazon is putting you a penalty time on starting/stopping VMs quite fast. And that one makes building way too slow. The openstack approach is 90% finished, but at that point of time, when I wrote it (1-2 years ago) the openstack cloud was to unstable and did even destroy itself when using it. I am sure openstack is in a much better state today, but I have not touch the code since then yet. You need still to set some environment variables (check the vm_verify_options_openstack() in build-vm-openstack) to get it working. However, all pieces of that code worked once at least. But it did bring the entire cloud down at that point of time :)
________________________________________ best regards Konstantin Rudenkov
On Thu, Oct 23, 2014 at 7:37 PM, Adrian Schröter <adrian@suse.de> wrote:
On Donnerstag, 23. Oktober 2014, 19:33:22 wrote Руденков Константин:
Good day to all, Does anyone have an experience of package build in open build system in docker environment? Or using the infrastructure of google compute engine(gce)\amazon?
In short, when you use
* chroot: it works of course everywhere, but is unsecure and unclean. * kvm nesting: it works everywhere where you can start kvm guests inside of kvm guests. * direct cloud support: Support for EC2 and openstack is in general in build script, but reality showed so far that it is not much usefull yet.
--
Adrian Schroeter email: adrian@suse.de
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany
-- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
24.10.2014 10:07, Adrian Schröter пишет:
On Donnerstag, 23. Oktober 2014, 22:50:14 wrote Konstantin Rudenkov:
Adrian, Thank you. I understand perl code very badly. Where can I find documentation of api bs_worker, how it starts/stops VM, how it gets the result back.
It is bash code mostly in
https://github.com/openSUSE/obs-build
check the build-vm-ec2 and -openstack files in first place.
Hi, Would be great to have howto write own build-vm-SOMETHING, there are much more cloud solutions. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter -
Konstantin Rudenkov -
Matwey V. Kornilov -
Руденков Константин