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 — Choice of architecture — Jobs, allowances and cgroup v2
Analysis HexaOS 3.0.0-rc1. Subject : Jobs, allowances and cgroup v2. 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 — Jobs, allowances and cgroup v2
Analysis HexaOS 3.0.0-rc1. Subject : Jobs, allowances and cgroup v2. 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 — Slurmctld, slurmd and knot states
Analysis HexaOS 3.0.0-rc1. Subject : Slurmctld, slurmd and knot states. 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 — Slurmctld, slurmd and knot states
Analysis HexaOS 3.0.0-rc1. Subject : Slurmctld, slurmd and knot states. 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 — Slurmctld, slurmd and knot states
Analysis HexaOS 3.0.0-rc1. Subject : Slurmctld, slurmd and knot states. 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 — Slurmctld, slurmd and knot states
Analysis HexaOS 3.0.0-rc1. Subject : Slurmctld, slurmd and knot states. 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 — Slurmctld, slurmd and knot states
Analysis HexaOS 3.0.0-rc1. Subject : Slurmctld, slurmd and knot states. 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 — Local data, retention and mode without network
Analysis HexaOS 3.0.0-rc1. Subject : Local data, retention and mode without network. 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 — Local data, retention and mode without network
Analysis HexaOS 3.0.0-rc1. Subject : Local data, retention and mode without network. 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 — Local data, retention and mode without network
Analysis HexaOS 3.0.0-rc1. Subject : Local data, retention and mode without network. 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 — Local data, retention and mode without network
Analysis HexaOS 3.0.0-rc1. Subject : Local data, retention and mode without network. 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 — Local data, retention and mode without network
Analysis HexaOS 3.0.0-rc1. Subject : Local data, retention and mode without network. 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 — CPU, GPU and fallback visible
Analysis HexaOS 3.0.0-rc1. Subject : CPU, GPU and fallback visible. 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 — CPU, GPU and fallback visible
Analysis HexaOS 3.0.0-rc1. Subject : CPU, GPU and fallback visible. 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 — CPU, GPU and fallback visible
Analysis HexaOS 3.0.0-rc1. Subject : CPU, GPU and fallback visible. 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 — CPU, GPU and fallback visible
Analysis HexaOS 3.0.0-rc1. Subject : CPU, GPU and fallback visible. 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 — CPU, GPU and fallback visible
Analysis HexaOS 3.0.0-rc1. Subject : CPU, GPU and fallback visible. 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 — Local GAR and sources cited
Analysis HexaOS 3.0.0-rc1. Subject : Local GAR and sources cited. 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 — Local GAR and sources cited
Analysis HexaOS 3.0.0-rc1. Subject : Local GAR and sources cited. 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 — Local GAR and sources cited
Analysis HexaOS 3.0.0-rc1. Subject : Local GAR and sources cited. 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 — Local GAR and sources cited
Analysis HexaOS 3.0.0-rc1. Subject : Local GAR and sources cited. 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 — Local GAR and sources cited
Analysis HexaOS 3.0.0-rc1. Subject : Local GAR and sources cited. 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 — Licences and bundles of models
Analysis HexaOS 3.0.0-rc1. Subject : Licences and bundles of models. 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 — Licences and bundles of models
Analysis HexaOS 3.0.0-rc1. Subject : Licences and bundles of models. 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 →