Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

ci(qualification): test DEB and RPM installation profiles

Aperta
#3,454 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@elezar ci sta già lavorando.

Dal 18/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

os:linux topic:testing

Description

Define the qualification policy for OpenShell installation profiles and add package-manager profiles for DEB and RPM candidate artifacts.

The policy keeps responsibilities explicit:

  • scenarios configure the machine and runtime environment;
  • installation profiles install and verify OpenShell;
  • testsuites verify post-install behavior and stateful transitions.

The DEB and RPM profiles must install the exact candidate packages through the guest's native package manager and compose with the same scenarios and testsuites used by native installation.

Context

  • Parent release pipeline: #2860
  • Native-install proof-of-concept pipeline: #2976
  • Completed reusable clean-install work: #2974
  • Installation profile model: #3419
  • N-to-N+1 upgrade testsuite: #2975
  • Release policy: RFC-0014

The native profile establishes the proof-of-concept pipeline. Package installation is separate qualification work and is a prerequisite for package-based upgrade testing.

Definition of Done

  • The installation-profile policy documents ownership, inputs, outputs, lifecycle, verification, diagnostics, and cleanup boundaries.
  • A DEB profile installs candidate packages on Ubuntu 24.04 through the native package manager.
  • An RPM profile installs candidate packages on Fedora through the native package manager.
  • Both profiles consume immutable candidate artifacts without rebuilding or using floating dev artifacts.
  • Both profiles verify installed package versions, candidate identity, expected services, and gateway health before a testsuite runs.
  • Native, DEB, and RPM installations can run the same independently selected testsuite without scenario-specific forks.
  • Failures retain package-manager, systemd, gateway, and scenario diagnostics without secrets.
  • Documentation explains how to add another installation profile under the same policy.
  • N-to-N+1 upgrade behavior remains in #2975 rather than being embedded in an installation profile.

Out of Scope

  • N-to-N+1 upgrade behavior
  • Helm, Homebrew, Snap, MSI, and WinGet installation profiles
Lingua principale
Rust
Stelle
8.7k
Fork
1.3k
Merge medio
2g 8h
PR unite (30g)
271

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/OpenShell

Tutte le issue di NVIDIA/OpenShell

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.