ci(qualification): test DEB and RPM installation profiles
@elezar ya está trabajando en esto.
Desde el 18/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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
devartifacts. - 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
- Lenguaje dominante
- Rust
- Estrellas
- 8.7k
- Forks
- 1.3k
- Merge medio
- 2 d 6 h
- PR fusionados (30 d)
- 301
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NVIDIA/OpenShell
-
area:docs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
state:triage-needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
area:cli state:validated
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
state:triage-needed
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
area:build spike state:review-ready state:stale
Dificultad 2/5 Medio día Aptitud para principiantes 68/100
Todos los issues de NVIDIA/OpenShell
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
TheLarkInn/aipm#2413 ·
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
todo:ticket
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
taikoxyz/taiko-mono#22168 · 1 comentario ·