Yast team has a great experience in automating tasks that can be done by machines in order to save time that can be used better. We usually use Jenkins for running these jobs.

Why to use automation?

Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA Topic 1:

OpenStack is, undoubtedly, a really huge ecosystem of cooperative services. Rally is a benchmarking tool that answers the question: “How does OpenStack work at scale?”. To make this possible, Rally automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a pluggable way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an OpenStack CI/CD system that would continuously improve its SLA, performance, and stability. <img src="https://wiki.openstack.org/w/images/thumb/e/ee/Rally-Actions.png/850px-Rally-Actions.png" width="700">

Alexa understands you. Jessy is the same, but you also understand her! :-)

Everyone loves to talk to the computer. Especially if it understands you. :-) So the Amazon Alexa is a hype right now. However, it requires your marriage to Amazon and signing contract to sell your soul in the afterlife: Alexa is nothing but a fancy microphone that sends everything you speak to ̶F̶B̶I̶ ̶a̶n̶d̶ ̶C̶I̶A̶ Amazon cloud so it will access your public API. Yes, and give them your access rights, of course...

Salt – The most intelligent, powerful and flexible open source software for remote execution, configuration automation, cloud control and event-driven orchestration The goal of the project is to bring its power into QAM, improving efficacy of work and possibly replacing other tools, where Salt could perform the task more naturally.