"salt-toaster" allows you to test multiple Salt package flavors across different operating systems via Docker containers. This project is heavily used on the SUSE Manager team to hardening the Salt package that is shipped on the openSUSE/SLE distributions. Link to GitHub repository
The "salt-toaster" execution is divided on different steps (image building, container spinning, salt key acceptance, tests execution, etc) but currently we only get the global results for the entire testsuite execution.
This hackweek projects wants to gather the timing profile of each execution step of the "salt-toaster" in order to export them to Prometheus (node_exporter) and vizualise them on Grafana.
Steps to follow:
- Evaluate implementation alternatives. (accumulated value like CPU)
- Implement timing profile inside "salt-toaster". The profile is saved in a json file collected by Prometheus "node_exporter".
- Visualize the data, rate, trends, on Grafana.
UPDATE July 11. 2018:
Goal achieved! 
Exporting profile and metrics from salt-toaster to Prometheus: https://github.com/openSUSE/salt-toaster/pull/59
This project is part of:
Hack Week 17
Activity
Comments
-
over 6 years ago by dmaiocchi | Reply
@PSuarezHernandez i would like to help
.We could create a separate github repo called "salt-toaster-metrics", and starting from there we can cordinate.
I will do also my hackweek on elixir but i would like to help on this also. If we have github Repo we can create issue and dashboards for cordination.
If we want at the end to push it back to salt-toaster this can be easy.
What do you think?
Reply to dmaiocchi
@PSuarezHernandez i would like to help .
We could create a separate github repo called "salt-toaster-metrics", and starting from there we can cordinate.
I will do also my hackweek on elixir but i would like to help on this also. If we have github Repo we can create issue and dashboards for cordination.
If we want at the end to push it back to salt-toaster this can be easy.
What do you think?
# A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image  This is a user link @hans This is a project link hw#some-cool-title
Similar Projects
Run local LLMs with Ollama and explore possible integrations with Uyuni by PSuarezHernandez
Description
Using Ollama you can easily run...
Team Hedgehogs' Data Observability Dashboard by gsamardzhiev
Description
This project aims to develop a ...
Saline (state deployment control and monitoring tool for SUSE Manager/Uyuni) by vizhestkov
[comment]: # (Please use the project descriptio...
ClusterOps - Easily install and manage your personal kubernetes cluster by andreabenini
Description
ClusterOps is a Kubernetes ...
Ansible for add-on management by lmanfredi
Description
Machines can contains various...
Saline (state deployment control and monitoring tool for SUSE Manager/Uyuni) by vizhestkov
[comment]: # (Please use the project descriptio...
Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil
Join the Gitter channel! [https://gitter.im/uy...
Automated Test Report reviewer by oscar-barrios
Description
In SUMA/Uyuni team we spend a...
Hack on isotest-ng - a rust port of isotovideo (os-autoinst aka testrunner of openQA) by szarate
Description
Some time ago, I managed to c...
Yearly Quality Engineering Ask me Anything - AMA for not-engineering by szarate
Goal
Get a closer look at how developers wo...
Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil
Join the Gitter channel! [https://gitter.im/uy...
Make more sense of openQA test results using AI by livdywan
Description
AI has the potential to help wi...