The open-source configuration and infrastructure management solution for software-defined infrastructure.

get_app Get new 2021.09!

What is Uyuni?

Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines.

Automated patch and package management

enables you to deploy patches and packages based on software channels and repositories you can assign, helping you to reduce costs.

any Linux server connected to the network, from IoT edge devices to your Kubernetes environment, no matter where it is located – in your data center, a 3rd party data center or in the public cloud.

of hardened OS templates (bare metal, VM or container) to tens of thousands of servers and IoT devices for faster, consistent and repeatable provisioning and configuration without compromising speed or security.

How does Uyuni work?

Uyuni leverages the Salt configuration management system to manage clients. The Uyuni Server is a full-fledged Salt Master node, allowing you to register and manage Salt clients. For more information about Salt, see the Salt documentation at Saltstack

and reporting with the ability to track all hardware and software changes made to your managed Linux infrastructure helps to ensure compliance with internal security policies

deployed in hybrid cloud and container infrastructures that are out of compliance to hardened profiles/templates based on your own internal security policies ensuring faster non-compliant remediation.

with graphical visualization of your Linux systems and their relationships along with the capability to organize them into logical groupings based on tags (e.g. location, rack, vendor, CPU architecture, RAM, etc.)

Latest news

28/19/2021

A security bugfix for CVE-2021-40348, for the Uyuni Server, was just released See how to apply the patch. We recommend you apply them as soon as possible.

24/09/2021

If zypper is reporting that it cannot update some packages on the server, check the workaround at the Uyuni issue 4244. We already filled a bug for openSUSE Leap 15.3 about it.