Technical brief — HexaOS Portal
This localized note explains the scope and checks associated with HexaOS Portal.
Read →EDITORIAL CONTENT
Blog
Project news, architecture decisions and technical evidence published without exposing sensitive data.
Maintenance and non-regression — Understand the role — Grafana and version dashboards
Analysis HexaOS 3.0.0-rc1. Subject : Grafana and version dashboards. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Prometheus collection and target health
Analysis HexaOS 3.0.0-rc1. Subject : Prometheus collection and target health. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Prometheus collection and target health
Analysis HexaOS 3.0.0-rc1. Subject : Prometheus collection and target health. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Prometheus collection and target health
Analysis HexaOS 3.0.0-rc1. Subject : Prometheus collection and target health. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Prometheus collection and target health
Analysis HexaOS 3.0.0-rc1. Subject : Prometheus collection and target health. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Prometheus collection and target health
Analysis HexaOS 3.0.0-rc1. Subject : Prometheus collection and target health. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Multinode physical qualification
Analysis HexaOS 3.0.0-rc1. Subject : Multinode physical qualification. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Multinode physical qualification
Analysis HexaOS 3.0.0-rc1. Subject : Multinode physical qualification. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Multinode physical qualification
Analysis HexaOS 3.0.0-rc1. Subject : Multinode physical qualification. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Multinode physical qualification
Analysis HexaOS 3.0.0-rc1. Subject : Multinode physical qualification. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Multinode physical qualification
Analysis HexaOS 3.0.0-rc1. Subject : Multinode physical qualification. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — MPI, Modules and Containers Apptainer
Analysis HexaOS 3.0.0-rc1. Subject : MPI, Modules and Containers Apptainer. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — MPI, Modules and Containers Apptainer
Analysis HexaOS 3.0.0-rc1. Subject : MPI, Modules and Containers Apptainer. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — MPI, Modules and Containers Apptainer
Analysis HexaOS 3.0.0-rc1. Subject : MPI, Modules and Containers Apptainer. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — MPI, Modules and Containers Apptainer
Analysis HexaOS 3.0.0-rc1. Subject : MPI, Modules and Containers Apptainer. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — MPI, Modules and Containers Apptainer
Analysis HexaOS 3.0.0-rc1. Subject : MPI, Modules and Containers Apptainer. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Munge and temporal consistency
Analysis HexaOS 3.0.0-rc1. Subject : Munge and temporal consistency. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Munge and temporal consistency
Analysis HexaOS 3.0.0-rc1. Subject : Munge and temporal consistency. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Munge and temporal consistency
Analysis HexaOS 3.0.0-rc1. Subject : Munge and temporal consistency. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Munge and temporal consistency
Analysis HexaOS 3.0.0-rc1. Subject : Munge and temporal consistency. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Munge and temporal consistency
Analysis HexaOS 3.0.0-rc1. Subject : Munge and temporal consistency. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Jobs, allowances and cgroup v2
Analysis HexaOS 3.0.0-rc1. Subject : Jobs, allowances and cgroup v2. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Jobs, allowances and cgroup v2
Analysis HexaOS 3.0.0-rc1. Subject : Jobs, allowances and cgroup v2. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Jobs, allowances and cgroup v2
Analysis HexaOS 3.0.0-rc1. Subject : Jobs, allowances and cgroup v2. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →