Q. How is Uyuni pronounced?
A. As /uju:ˈni/
Q. Why the name Uyuni?
A. As announced at the press release, Uyuni is using Salt for configuration management, thereby inheriting its name: Uyuni refers to the world’s largest Salt flat, Salar de Uyuni in Southwest Bolivia.
Q. Where I can find Uyuni source code?
A. At the Git repository.
Q. Is Uyuni based on SUSE Manager?
A. Only the initial release 4.0.0, was based on SUSE Manager 3.2. Uyuni 4.0.1 and subsequent versions are the base for next on SUSE Manager version 4.0, and all future versions.
Uyuni and SUSE Manager are based on the Spacewalk project, but as our code diverged more and more, we decided to fork for the reasons explained at the Press Release.
A. Uyuni is since July 2018 the upstream for SUSE Manager, so the two first digits are the next SUSE Manager version (4.0) and the third one the Uyuni release.
As soon as next SUSE Manager version is out, the two first digits will change. Meanwhile only the last one will be increased and will be used for the rolling release model.
Q. What are the main differences between Uyuni and Spacewalk right now?
A. While most of the bugfixes and enhancements from SUSE Manager were contributed back to Spacewalk, some features did not make their way back. To highlight some:
- The server is a full Salt master and can manage systems running the Salt minion, with full configuration management support.
- Building of image containers based on frozen channels.
- Auditing of container images and Kubernetes clusters.
- Initial configuration and setup based on YaST.
- Infrastructure changes to keep the codebase modern (Java 8, Hibernate 5, React.js, Spark, ...).