Saltboot ability to deploy OEM images
an idea by oholecek
Updated 11 months ago. 2 hacker ♥️. 1 follower. Has no hacker: grab it!

Description

Saltboot is a system deployment part of Uyuni. It is the mechanism behind deploying Kiwi built system images from central Uyuni server location.

System image is when the image is only of one partition and does not contain whole disk image and deployment system has to take care of partitioning, fstab on top of integrity validation.

However systems like Aeon, SUSE Linux Enterprise Micro and similar are distributed as disk images (also so called OEM images). Saltboot currently cannot deploy these systems.

The main problem to saltboot is however that currently saltboot support is built into the image itself. This step is not desired when using OEM images.

Goals

Saltboot needs to be standalone and be able to deploy OEM images. Responsibility of saltboot would then shrink to selecting correct image, image integrity validation, deployment and boot to deployed system.

Resources

  • Saltboot - https://github.com/uyuni-project/retail/tree/master
  • Uyuni - https://github.com/uyuni-project/uyuni

No Hackers yet

Join this project

Looking for hackers with the skills:

saltboot uyuni imagedeployment

This project is part of:

Hack Week 24

Activity

  • 10 months ago: juliogonzalezgil liked this project.
  • 11 months ago: vizhestkov liked this project.
  • 11 months ago: oholecek added keyword "saltboot" to this project.
  • 11 months ago: oholecek added keyword "uyuni" to this project.
  • 11 months ago: oholecek added keyword "imagedeployment" to this project.
  • 11 months ago: oholecek originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Move Uyuni Test Framework from Selenium to Playwright + AI by oscar-barrios

    Description

    This project aims to migrate the existing Uyuni Test Framework from Selenium to Playwright. The move will improve the stability, speed, and maintainability of our end-to-end tests by leveraging Playwright's modern features. We'll be rewriting the current Selenium code in Ruby to Playwright code in TypeScript, which includes updating the test framework runner, step definitions, and configurations. This is also necessary because we're moving from Cucumber Ruby to CucumberJS.

    If you're still curious about the AI in the title, it was just a way to grab your attention. Thanks for your understanding.

    Goals

    • Migrate Core tests including Onboarding of clients
    • Improve test reliabillity: Measure and confirm a significant reduction of flakynes.
    • Implement a robust framework: Establish a well-structured and reusable Playwright test framework using the CucumberJS

    Resources