- Jan 24, 2025
-
-
Antoine R. Dumont authored
Refs. sysadm-environment#5543
-
Antoine R. Dumont authored
Support bullseye and bookworm (maybe more, only checked those). Refs. sysadm-environment#5543
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
Refs. sysadm-environment#5543
-
Antoine R. Dumont authored
Refs. sysadm-environment#5543
-
- Jan 17, 2025
-
-
Antoine R. Dumont authored
Refs. sysadm-environment#5530
-
Antoine R. Dumont authored
Refs. sysadm-environment#5532
-
Antoine R. Dumont authored
Refs. sysadm-environment#5530
-
Antoine R. Dumont authored
Refs. sysadm-environment#5532
-
- Jan 10, 2025
-
-
Antoine R. Dumont authored
Refs. sysadm-environment#5532
-
- Jan 06, 2025
-
-
Antoine R. Dumont authored
It's now the stable distribution. Refs. sysadm-environment#5519
-
Antoine R. Dumont authored
Refs. sysadm-environment#5519
-
Antoine R. Dumont authored
Based on esnode8's first installation tryout failure. Refs. sysadm-environment#5519
-
Antoine R. Dumont authored
Refs. sysadm-environment#5519
-
- Dec 19, 2024
-
-
Antoine R. Dumont authored
Refs. sysadm-environment#5519
-
Antoine R. Dumont authored
Earlier this year, we had to adapt the routine to be able to define the net devices and the interfaces diffently than the default names (net0, ...). It worked at the time because we declared those in the $(hostname).yaml configuration file. But now, trying to use the default values (without specifying those new entries), the routine does not work. The cli j2 is not happy about non declared template values (IPXE_NET, ...) [1] This fixes it by using temporary templates which gets adapted through sed to fill-in the holes. Once done, the temporary templates are cleaned up. [1] ``` jinja2.exceptions.UndefinedError: 'IPXE_NET' is undefined ``` Refs. sysadm-environment#5519
-
- Dec 18, 2024
-
-
Antoine R. Dumont authored
Refs. sysadm-environment#5519
-
- Aug 22, 2024
-
-
Vincent Sellier authored
(it was manually updated on the server) Related to sysadm-environment#5386
-
- Aug 21, 2024
-
-
Vincent Sellier authored
Related to sysadm-environment#5386
-
- Jul 18, 2024
-
-
Antoine R. Dumont (@ardumont) authored
Refs. sysadm-environment#5367
-
- Jul 17, 2024
-
-
Vincent Sellier authored
-
Antoine R. Dumont (@ardumont) authored
This fails the postinstallation step altogether (during the install phase). Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Fix formatting and some typos Refs. sysadm-environment#5367
-
Antoine R. Dumont (@ardumont) authored
Fix formatting and some typos
-
Vincent Sellier authored
-
Vincent Sellier authored
-
Vincent Sellier authored
-
- Jul 16, 2024
-
-
Vincent Sellier authored
Only tested for the HP servers bought at the end of 2023 Related to sysadm-environment#5312
-
- Mar 22, 2024
-
-
Guillaume Samson authored
Related to sysadm-environment#5288
-
- Feb 26, 2024
-
-
Antoine R. Dumont authored
It was not working for the old beaubourg machine whose interfaces named differed. Refs. sysadm-environment#5250
-
Antoine R. Dumont authored
Refs. sysadm-environment#5250
-
- Feb 23, 2024
-
-
Antoine R. Dumont authored
And fallback generation to the default hard-coded name otherwise. Refs. sysadm-environment#5250
-
Antoine R. Dumont authored
Previously known as beaubourg. Refs. sysadm-environment#5251
-
- Nov 16, 2023
-
-
Nicolas Dandrimont authored
Ref. sysadm-environment#5069
-
- Sep 25, 2023
-
-
Guillaume Samson authored
Related to sysadm-environment#5042
-