Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentes Révision précédente
Prochaine révision
Révision précédente
Prochaine révision Les deux révisions suivantes
en:developpement:productions:sidus [2013/10/23 11:09]
equemene [Startup sequence]
en:developpement:productions:sidus [2014/11/04 17:22]
equemene [Startup sequence]
Ligne 1: Ligne 1:
 ====== SIDUS : Single Instance Distributing Universal System ====== ====== SIDUS : Single Instance Distributing Universal System ======
  
-<note important>​This page is a //Google & I translation// of the french page [[developpement:​productions:​sidus|SIDUS]] : if you want to improve this page, send updates!</​note>​+<note important>​For proper English, please refer to this Linux Journal [[http://www.linuxjournal.com/content/november-2013-issue-linux-journal-system-administration|article]] published in November 2013. It was written by Marianne Corvellec based on Emmanuel Quemener'​s articles.</​note>​
  
 {{ :​developpement:​productions:​sidus.png?​200 |}} {{ :​developpement:​productions:​sidus.png?​200 |}}
Ligne 95: Ligne 95:
 Look in more detail the configuration of the different services we have include: Look in more detail the configuration of the different services we have include:
  
 +<note important>​In [[http://​www.linuxjournal.com/​content/​november-2013-issue-linux-journal-system-administration|Linux Journal]] article, next-server is defined as ''​172.16.20.13'',​ it's better to put it inside LAN: 10.13.20.13 is a better choice.</​note>​
 For the DHCP server in the configuration file ''/​etc/​dhcp/​dhcpd.conf''​ :<​code>​ For the DHCP server in the configuration file ''/​etc/​dhcp/​dhcpd.conf''​ :<​code>​
 next-server 10.13.20.13;​ next-server 10.13.20.13;​
Ligne 182: Ligne 183:
 ===== Purge ===== ===== Purge =====
  
-Unfortunately,​ this installation bulimia is not without effect. Packages still install some "​evil"​ and a purge of a few, including an installer Matlab, we ruffles hair!<​code>​+Unfortunately,​ this installation bulimia is not without effect. Packages still install some "​evil"​ and a purge of a few, including an installer Matlab!<​code>​
 time sidus apt-get purge -y -f --force-yes matlab-*</​code>​ time sidus apt-get purge -y -f --force-yes matlab-*</​code>​
  
Ligne 228: Ligne 229:
 This script, ''​rootaufs'',​ in located in ''​${SIDUS}/​etc/​initramfs-tools/​scripts/​init-bottom''​ This script, ''​rootaufs'',​ in located in ''​${SIDUS}/​etc/​initramfs-tools/​scripts/​init-bottom''​
  
-The original script was inspired by the project **rootaufs** from Nicholas A. Schembri (http://​code.google.com/​p/​rootaufs/​). He was deeply modified to adapt our infrastructure:​ a version is available on http://​www.cbp.ens-lyon.fr/​sidus/​rootaufs :<​code>​ +<note important>​In [[http://​www.linuxjournal.com/​content/​november-2013-issue-linux-journal-system-administration|Linux Journal]] article, ''​rootaufs''​ as destination file is missing.</​note>​ 
-wget -O ${SIDUS}/​etc/​initramfs-tools/​scripts/​init-bottom http://​www.cbp.ens-lyon.fr/​sidus/​rootaufs+The original script was inspired by the project **rootaufs** from Nicholas A. Schembri (http://​code.google.com/​p/​rootaufs/​). He was deeply modified to adapt our infrastructure:​ a version is available on http://​www.cbp.ens-lyon.fr/​sidus/​rootaufs : 
 +<​code>​ 
 +wget -O ${SIDUS}/​etc/​initramfs-tools/​scripts/​init-bottom/​rootaufs ​http://​www.cbp.ens-lyon.fr/​sidus/​rootaufs
 </​code>​ </​code>​
  
Ligne 238: Ligne 241:
 <​code>​sidus update-initramfs -k all -u</​code>​ <​code>​sidus update-initramfs -k all -u</​code>​
  
-Then just copy the kernel and boot loader in the definition :<​code>​ +<note important>​In [[http://​www.linuxjournal.com/​content/​november-2013-issue-linux-journal-system-administration|Linux Journal]] article, ''​vmlinux-Sidus''​ is written, not ''​vmlinuz-Sidus''​ as TFTP kernel file.</​note>​ 
-cp ${SIDUS}/​vmlinuz-3.2.0-4-amd64 /​srv/​tftp/​vmlinuz-Sidus +Then just copy the kernel and boot loader in the definition : 
-cp ${SIDUS}/​initrd.img-3.2.0-4-amd64 /​srv/​tftp/​initrd.img-Sidus+<​code>​ 
 +cp ${SIDUS}/boot/​vmlinuz-3.2.0-4-amd64 /​srv/​tftp/​vmlinuz-Sidus 
 +cp ${SIDUS}/boot/​initrd.img-3.2.0-4-amd64 /​srv/​tftp/​initrd.img-Sidus
 </​code>​ </​code>​
-Here, we are under AMD64 architecture with 3.2.0-4 kernel version. 
  
 Initially, we explored the possibility of offering a second NFS share as read/write persistence associated with a client reboots changes. This version, though functional, demanded the opening of an atomic NFS from each customer with what we imagine as a burden on their server! Initially, we explored the possibility of offering a second NFS share as read/write persistence associated with a client reboots changes. This version, though functional, demanded the opening of an atomic NFS from each customer with what we imagine as a burden on their server!