DokuWiki

User Tools

Site Tools

Trace:
cluster:216

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
cluster:216 [2022/04/29 14:51]
hmeij07 		cluster:216 [2022/04/29 15:08]
hmeij07 [golden image]
Line 191: Line 191:
 tmpfs                          3.2G     0  3.2G   0% /run/user/0 tmpfs                          3.2G     0  3.2G   0% /run/user/0
  
-[root@n59 ~]# free -g +[root@n59 ~]# fdisk -l 
-              total        used        free      shared  buff/cache   available +Device       Start      End  Sectors  Size Type 
-Mem:             31           0          29           0           1          30 +/dev/sda1     2048     6143     4096    2M BIOS boot 
-Swap:             6           0           6+/dev/sda2     6144  1050623  1044480  510M EFI System 
 +/dev/sda3  1050624  2099199  1048576  512M Linux swap 
 +/dev/sda4  2099200 31277055 29177856 13.9G Linux filesystem 
  
 [root@n59 ~]# cat /etc/redhat-release  [root@n59 ~]# cat /etc/redhat-release 
Line 209: Line 212:
 ==== golden image ==== ==== golden image ====
  
-After stateful imaging we touch another file on imaged server then build a golden image. The touching of this new file represents customixing and testing the node. So for complex designs we might put the node temporarily on the internet and install nvidia drivers and toolkit. And perhaps install software that will optimize itself based on resources found (like gromacs/lammps probing gpu models for proper architecture). Then we build a golden image.+After stateful imaging we touch another file on imaged server then build a golden image. The touching of this new file represents customizing and testing the node prior to creating golden image. So for complex designs we might put the node temporarily on the internet and install nvidia drivers and toolkit for example. And perhaps install software that will optimize itself based on resources found (like gromacs/lammps probing gpu models for proper architecture). Then we build a golden image when everything works as expected. Hard to do in a CHROOT environment.
  
 <code> <code>
Line 273: Line 276:
 </code> </code>
  
 +Awesome. You also have a backup now. Image away. And no need for a dhcp server to always be at the ready. Linux will fix journal file system errors 99% of the time if rebooted from say a utility power loss.\\ Thank you Warewulf team.
 +
 +I also see there are EFI and EFI + NVME filesystem examples in ''/etc/warewulf/filesystem/examples''
  
  
cluster/216.txt · Last modified: 2022/06/07 20:07 by hmeij07

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki