[opensuse-factory] A report about Tumbleweed
Anyone else seen this? http://news.softpedia.com/news/opensuse-tumbleweed-is-in-need-of-workers-no-... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello. Could any OpenQA guru please suggest the easiest way for a conventional desktop to join the openqa.opensuse.org as a worker, without having to read through the entire openqa documentation? Much appreciated. Kind regards, Howard On Fri, 19 Feb 2016, ianseeks wrote:
Anyone else seen this?
http://news.softpedia.com/news/opensuse-tumbleweed-is-in-need-of-workers-no-... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Howard! On 19 February 2016 at 08:30, Howard Guo <hguo@suse.com> wrote:
Could any OpenQA guru please suggest the easiest way for a conventional desktop to join the openqa.opensuse.org as a worker, without having to read through the entire openqa documentation?
You can't (yet? I do really like the idea) The blocker to that suggestion is that the current openQA architecture has an NFS share on the 'master' server (Scheduler/WebUI) which all the workers need to be able to see in order to get the media they are testing, and to save files required for the results back to As this can require quite a lot of data being transferred quite often (installation media and entire copies of repositories are not small), a fast network is preferred - we currently benefit from openqa.o.o being physically and network-wise quite close to build.o.o :) It would be nice to see features added to openQA to be able to work in a more distributed way, but I don't see it as an easy enough problem that we can fix it quickly for this immediate issue However, I have good news Several weeks ago, long before there was any hint of any problems with the existing openQA hardware, SUSE agreed to sponsor TWO new openQA worker servers These are intended to replace the current two machines (well currently 1 I guess..) that collectively can provide 10 slow worker instances, with two new machines that can each provide at least 16 medium/fast workers (eg. at least 32 workers for openqa.opensuse.org, possibly more) They're very nice beefy machines.. 16 cores/32 threads, 256GB RAM, 400GB NVMe SSDs..the same kind of hardware we use for the internal SLE openQA instance. The hardware was ordered weeks ago and we're expecting delivery imminently - I wonder if our old hardware figured this out and decided to blow up in protest? ;) As the current problem is dragging on, I'm working with the SUSE infra team to relocate one of the internal SLE openQA servers to the openSUSE infrastructure This'll mean we'll both be running at 'half strength' compared to our target capacity, but for openSUSE that will still be several times faster than anything we've ever seen on openqa.opensuse.org But all this network work isn't trivial, no promises as to when, if the new hardware turns up today then that'll change the plans, just please be assured that we're working on it as fast as we can to get everything back up and running as it should and we already made steps to avoid this happening again, the kit just didn't arrive before it happened ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 19 February 2016 at 09:41, Richard Brown <RBrownCCB@opensuse.org> wrote:
As the current problem is dragging on, I'm working with the SUSE infra team to relocate one of the internal SLE openQA servers to the openSUSE infrastructure
This'll mean we'll both be running at 'half strength' compared to our target capacity, but for openSUSE that will still be several times faster than anything we've ever seen on openqa.opensuse.org
But all this network work isn't trivial, no promises as to when, if the new hardware turns up today then that'll change the plans, just please be assured that we're working on it as fast as we can to get everything back up and running as it should and we already made steps to avoid this happening again, the kit just didn't arrive before it happened ;)
The promised migration of SLE openQA hardware to openSUSE is now complete Thanks to the SUSE Infra Team and Ludwig for their help making that happen openqa.opensuse.org is running faster than ever through it's backlog We're still looking forward to the other new hardware arriving soon :) Enjoy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2016-02-19 08:30, Howard Guo wrote:
Hello.
Could any OpenQA guru please suggest the easiest way for a conventional desktop to join the openqa.opensuse.org as a worker, without having to read through the entire openqa documentation?
And just like build.opensuse.org, the project would maybe say no anyway because of security concerns (uploading false and misleading results). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt píše v Pá 19. 02. 2016 v 10:22 +0100:
On Friday 2016-02-19 08:30, Howard Guo wrote:
Hello.
Could any OpenQA guru please suggest the easiest way for a conventional desktop to join the openqa.opensuse.org as a worker, without having to read through the entire openqa documentation?
And just like build.opensuse.org, the project would maybe say no anyway because of security concerns (uploading false and misleading results).
Compared to OBS where we sign the builds and ensure atomicity and clean enviroment... If your openQA tester sents fake results we can at worst approve broken release or block correct release from being released for a bit. That is way lower on threat scale compared to malcious RPMs installable by everybody. Cheers Tom
participants (5)
-
Howard Guo
-
ianseeks
-
Jan Engelhardt
-
Richard Brown
-
Tomas Chvatal