Difference between revisions of "Diskless netboot"

 
(65 intermediate revisions by the same user not shown)
Line 1: Line 1:
Diskless server / workstation using netboot
+
[[Category:Linux]]
  
  
NFS is a technology that allow you to share some files and folders over the network. So:
+
==Target folder tree (server side)==
* All the clients will share the installation, configuration files and so on.
 
* Each client will run a dedicated instance of the operating system
 
* Logs will be centralized on the common NFS server - so we don't loose data on each reboot.
 
  
You must have a working DHCP server + NetBoot before starting this part.
+
This is how we'll setup our files and folders:
  
 
Requirements:
 
* [[DHCP server]]
 
* [[NetBoot server]]
 
 
 
 
=Installation=
 
 
 
'''NFS support'''
 
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
apt-get install nfs-kernel-server nfs-common
+
# TFTP root
</syntaxhighlight>
+
/tftpboot/                                  
 
 
'''Debootstrap (manage netboot image)'''
 
<syntaxhighlight lang="bash">
 
apt-get install debootstrap
 
</syntaxhighlight>
 
 
 
  
 +
###############
 +
# Network bootable image(s) using NFS technology
 +
################     
  
=NFS server setup=
+
#### Boot file           
 +
/tftpboot/pxelinux.0                  # Initial boot file - only use to load the PXE NetBoot manager
 +
/tftpboot/{menu.c32 || vesamenu.c32}  # PXE interactive menu managers (text or graphical)
 +
/tftpboot/pxelinux.cfg/                # PXE configuration(s)
 +
/tftpboot/pxelinux.cfg/default        # default PXE configuration
  
 +
#### Kernel file
  
==Preparation==
+
/tftpboot/images/    
 
 
You have to create a dedicated folder on your server where you will host the client image.
 
 
 
<syntaxhighlight lang="bash">
 
mkdir -p /srv/nfsroot
 
chmod -R 777 /srv/nfsroot
 
</syntaxhighlight>
 
 
 
  
==Configuration==
+
# Debian 7.x [Wheezy]
 +
/tftpboot/images/wheezy/ 
 +
/tftpboot/images/wheezy/vmlinuz
 +
/tftpboot/images/wheezy/initrd.img
  
The NFS configuration is done in the '''/etc/exports''' file
+
# [X]Ubuntu 14.04 [Trusty]
 +
/tftpboot/images/trusty/ 
 +
/tftpboot/images/trusty/vmlinuz
 +
/tftpboot/images/trusty/initrd.img
  
<syntaxhighlight lang="bash">
 
vim /etc/exports
 
</syntaxhighlight>
 
  
 +
#### NFS
 +
# This is where the runnable will be. Each image will be in a dedicated folder.
 +
/nfs/                   
  
Add something like that:
+
# Debian 7.x [Wheezy]
 +
/nfs/wheezy/ 
  
<syntaxhighlight lang="bash">
+
# Ubuntu 14.04 [Trusty]
  /srv/nfsroot      192.168.2.0/24(ro,no_root_squash,async,insecure,no_subtree_check)
+
/nfs/trusty/
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
Adjust "192.168.2.0/24" to your own network address
 
 
* rw : Allow clients to read as well as write access
 
* ro : Read only access
 
* insecure : Tells the NFS server to use unpriveledged ports (ports > 1024).
 
* no_subtree_check : If the entire volume (/users) is exported, disabling this check will speed up transfers.
 
* async : async will speed up transfers.
 
* no_root_squash: This phrase allows root to connect to the designated directory.
 
 
 
- NOTE -
 
 
It's always a good idea to use Read-Only if you plan to share this disk.
 
 
That will avoid user to mess with your image!
 
  
  
 +
==Client overview==
  
==Security==
+
Each client must have, at least, 4 Go of RAM.
  
Like TFTP, this part is insecure !
 
  
You must restrict the access to your NFS server by a firewall script and filtering BEFORE reaching the LAN !
+
===4 GO RAM configuration===
  
 +
This is how we're gonna populate the client:
  
 +
[[File:Client_composition.png|480px|NetBoot client RAM overview - 4Go]]
  
NFS is using dynamic ports numbers because it runs over '''rpcbind'''. Making NFS using specifics port is a pain in the ass !! :(
 
  
So, instead of that you should allow your LAN communication.  
+
As you can see, each client will have some space dedicated for swap + some RAMdisk to allow writing in /var, /tmp and /proc.
  
  
<syntaxhighlight lang="bash">
+
Configuration of a '''4Go RAM''' disk:
    IPTABLES=`which iptables`
+
* No swap
    LAN_ADDRESS="192.168.2.0/24"
+
* Local TMPFS (read/write for /dev, /tmp, ...) : 1 Go
 +
** /tmp      = 512 M
 +
** /var/tmp  = 128 M
 +
** /var/log  = 128 M
 +
** /var/run  = 8 M
 +
** /var/lock = 8 M
 +
** /run/shm  = 256 M
 +
* O.S (NFS read only) : all the rest ~ 2.8 Go
 +
* Common share (NFS read write) : ''Remote disk''
  
    # Allow LAN communication
 
    $IPTABLES -A INPUT -s $LAN_ADDRESS -d $LAN_ADDRESS -m state ! --state INVALID -j ACCEPT
 
    $IPTABLES -A OUTPUT -s $LAN_ADDRESS -d $LAN_ADDRESS -m state ! --state INVALID -j ACCEPT
 
  
</syntaxhighlight>
 
  
 +
===2 Go===
  
==Management==
+
Due to budget restriction we might encounter some low memory machines with only 2 Go...
 
 
<syntaxhighlight lang="bash">
 
service nfs-kernel-server {status|start|stop|restart}
 
</syntaxhighlight>
 
 
 
  
==Test the server==
 
  
 +
This is how we're gonna populate the client:
  
Install the NFS v4 client:
+
[[File:Client_mount_points_2Go.png|480px|NetBoot client RAM overview - 2Go]]
<syntaxhighlight lang="bash">
 
apt-get install nfs-common
 
</syntaxhighlight>
 
  
  
To mount the default path:
+
In case of '''2Go RAM''' then you have to use some tricks:
<syntaxhighlight lang="bash">
+
* No swap
mount -t nfs nfs-server:/ /mnt
+
* O.S (NFS read only) : ~ 1.2 Go
</syntaxhighlight>
+
* Common share (NFS read write) : ''Remote disk''
 +
* Local TMPFS (read/write for /dev, /tmp, ...) : all the rest
 +
** /tmp      = 372 M
 +
** /var/tmp  = auto
 +
** /var/log  = 128 M
 +
** /var/run  = auto
 +
** /var/lock = auto
 +
** /run/shm  = auto
  
You'll see: "/mnt/srv/nfsroot"
 
  
  
It's better to do:
+
==How big is the client image ?==
<syntaxhighlight lang="bash">
 
mount -t nfs nfs-server:/srv/nfsroot /mnt
 
</syntaxhighlight>
 
  
 +
By default the ''deboostrap'' Ubuntu 14.04 LTS image is 239 Mo. With the applications we're gonna use that size will increase to about 1 or '''1.3 Go''' depending if you copy (or not) the kernel sources. It may even take 1.6 Go if you're using XFCE frontend.
  
  
Line 139: Line 112:
  
 
The main ones are:
 
The main ones are:
* debootstrap
 
* copying the install from your server
 
* Manual install on a client, then, when the system is ready, copy everything to the NFS share
 
  
 +
* Manually
 +
** debootstrap
 +
** copying the install from your server
 +
** Manual install on a client, then, when the system is ready, copy everything to the NFS share
  
 +
* Using script and software like "Puppet" or "Chef"
  
==Debootstrap: setup client distribution==
 
  
  
===Setup distribution folder===
+
==Setup client distribution==
  
 
You have to create one target for each distribution you want to serve:
 
You have to create one target for each distribution you want to serve:
  
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
mkdir -p /srv/nfsroot/trusty
+
mkdir -p /nfs/trusty
chmod -R 777 /srv/nfsroot/trusty
+
mkdir -p /nfs/wheezy
 +
mkdir -p /nfs/common
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
  
 
- NOTES -  
 
- NOTES -  
 +
 
* The folder name should match your NetBoot settings. Folder name = a LABEL in the NetBoot config.
 
* The folder name should match your NetBoot settings. Folder name = a LABEL in the NetBoot config.
 +
 
* The folder name should match a Linux (Debian like) distribution name
 
* The folder name should match a Linux (Debian like) distribution name
  
  
===Populate the content===
 
  
<syntaxhighlight lang="bash">
+
==Configure client distribution==
cd /srv/nfsroot/trusty
 
debootstrap trusty /srv/nfsroot/trusty
 
</syntaxhighlight>
 
  
 +
* Manual configuration: [[Diskless image configuration - manual setup]]
  
===Adjust default login/password===
+
* Automatic [Puppet || Chef] configuration: [[Diskless image configuration - script setup]]
 
 
You have to create / adjust the default user.
 
 
 
To do so, we must "mount" the new system and perform operations on it.
 
<syntaxhighlight lang="bash">
 
# "mount" the system
 
chroot /srv/nfsroot/trusty/
 
# Add new user
 
adduser <username>
 
# Add user to sudoers group
 
usermod -a -G sudo <username>
 
# Exit chroot
 
exit
 
</syntaxhighlight>
 
  
  
  
  
=Custom NetBoot configuration=
 
  
 +
==Backup distribution==
  
==Basic configuration==
+
You can create an archive of your current distribution for later restore / re-use.
  
You can setup your own netboot configuration.
 
  
To do so, you can re-use one of the syslinux templates:
+
===Compression===
  
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
# Create folders
+
cd /nfs
mkdir /var/lib/tftpboot/custom
+
tar cvpjf trusty.tar.bz2 ./trusty
mkdir /var/lib/tftpboot/custom/pxelinux.cfg
 
 
 
# Create configuration files
 
cp /usr/lib/syslinux/pxelinux.0 /var/lib/tftpboot/custom
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
The ''pxelinux.cfg'' folder is mandatory. Inside you can provide:
+
===Restoration===
* configuration for a specific IP @ or hostname
 
* configuration for a group
 
* default configuration (required)
 
  
 
Create the default configuration file:
 
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
vim /var/lib/tftpboot/custom/pxelinux.cfg/default
+
cd /nfs
 +
tar -xvjf trusty.tar.bz2
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 +
=PXE interactive menu=
  
Put the following:
+
You can create interactive NetBoot menus, see:
<syntaxhighlight lang="bash">
+
* [[PXE interactive menu - single level]]
# Ubuntu 14.04
+
* [[PXE interactive menu - multi level]]
LABEL TRUSTY
 
    kernel trusty/vmlinuz
 
    initrd trusty/initrd.img
 
    # Set NFS share as default root
 
    append root=/dev/nfs nfsroot=192.168.2.2:/srv/nfsroot/trusty
 
  
  
# Prompt user for selection
 
PROMPT 0
 
  
TIMEOUT 30
 
</syntaxhighlight>
 
  
* Each LABEL is a specific configuration that will displayed on the NetBoot menu.
+
=Local server monitoring=
* PROMPT 1 = enable user prompt so you can choose the configuration
 
* TIMEOUT 30 = timeout (in seconds) before the default option is choosen
 
  
 +
Install the following services:
 +
* [[SNMP client]]
 +
* [[Zabbix agent setup]]
  
Note that I used a reference to "trusty/", that's a folder I need to create later on.
 
  
  
  
==Create boot files==
+
=Other services=
  
<syntaxhighlight lang="bash">
 
mkdir /var/lib/tftpboot/custom/trusty
 
# Copy current boot files
 
cp /boot/vmlinuz-3.2.0-4-amd64 /var/lib/tftpboot/custom/trusty/
 
cp /boot/initrd.img-3.2.0-4-amd64 /var/lib/tftpboot/custom/trusty/
 
# Create symlinks
 
ln -s /var/lib/tftpboot/custom/trusty/vmlinuz-3.2.0-4-amd64 /var/lib/tftpboot/custom/trusty/vmlinuz
 
ln -s /var/lib/tftpboot/custom/trusty/initrd.img-3.2.0-4-amd64 /var/lib/tftpboot/custom/trusty/initrd.img
 
</syntaxhighlight>
 
  
 +
==File sharing==
  
- NOTES -
+
If you want to expose the NFS common folder as a file-share, you have to install and configure Samba. See: [[Samba server]]
* Adjust the ''3.2.0-4'' kernel number to the version you are using
 
* '''Do NOT use symlinks''' !! It won't work !!
 
* Don't forget to set all the rights ("chmod 777"). See the ''Security'' section below.
 
  
  
==Advanced menu==
+
''Note''
  
===Install menu manager===
+
Samba is actually better than NFS for the file-share. You should remove Common from /etc/exports and use a samba share instead.
  
Text menu:
 
  
<syntaxhighlight lang="bash">
 
cp /usr/lib/syslinux/menu.c32 /var/lib/tftpboot/custom/
 
</syntaxhighlight>
 
  
 +
==Management UI (webmin)==
  
Graphic menu:
+
Since there is a lot of services to manage, it's always convenient to use an UI for it. Check [[Webmin]]
  
<syntaxhighlight lang="bash">
 
cp /usr/lib/syslinux/vesamenu.c32 /var/lib/tftpboot/custom/
 
cp /mySuperPicture/logo.png /var/lib/tftpboot/custom/pxelinux.cfg/
 
</syntaxhighlight>
 
  
The associate picture must be a '''PNG 800x600''' picture and MUST be named '''logo.png'''.
 
  
 +
==VPN server==
  
===Configure boot options===
+
See [[VPN]]
  
Then edit the PXE boot file:
 
  
<syntaxhighlight lang="bash">
 
vim /var/lib/tftpboot/custom/pxelinux.cfg/default
 
</syntaxhighlight>
 
  
 +
==Apache2 server==
  
Put:
+
See [[Apache 2]]
  
<syntaxhighlight lang="bash">
 
#### GENERIC OPTIONS #####
 
# Enable text menu
 
#DEFAULT menu.c32
 
# Enable graphical menu
 
DEFAULT vesamenu.c32
 
# Prompt for user input? (0 = choose from menu, 1 = you can type anything)
 
PROMPT 0
 
# Allow or not the user to left the menu (1 = user is locked to the menu)
 
NOESCAPE 1
 
# Time before using default option
 
TIMEOUT 50
 
  
  
#### Menu settings #####
 
MENU TITLE my super netboot menu
 
MENU BACKGROUND pxelinux.cfg/logo.png
 
MENU WIDTH 80
 
MENU ROWS 14
 
MENU MARGIN 10
 
  
  
#### Distributions #####
+
=References=
# Ubuntu 14.04
 
LABEL trusty
 
    MENU LABEL Ubuntu 14.04 (trusty)
 
    MENU DEFAULT
 
    # Kernel and boot files
 
    KERNEL trusty/vmlinuz
 
    initrd trusty/initrd.img
 
    ### Boot options
 
    # Set NFS share as default root
 
    APPEND root=/dev/nfs nfsroot=192.168.2.2:/srv/nfsroot/trusty
 
  
# Installation disk
+
Ubuntu diskless how-to: https://help.ubuntu.com/community/DisklessUbuntuHowto
    MENU LABEL rescue disk
 
    # Kernel and boot files
 
    KERNEL trusty/vmlinuz
 
    initrd rescue/amd64/initrd.img
 
  
</syntaxhighlight>
 
  
 +
Mind reference: http://mindref.blogspot.se/2011/03/debian-diskless.html
  
Note all the "MENU" commands + PROMPT 0
 
  
 +
Super video tutorials:
 +
* https://www.youtube.com/watch?v=js9imsrqAMk
 +
* http://www.stepladder-it.com/bivblog/14/ to /16/
 +
* https://blog.dlasley.net/2013/01/pxe-server-ubuntu/
  
=Security notes=
 
  
in order to work you must adjust the rights of your "/var/lib/tftpboot/".
+
Nice explanation of PXE process: http://www.linux.com/learn/docs/ldp/497-Diskless-root-NFS-HOWTO
  
<syntaxhighlight lang="bash">
+
* How to improved /etc/fstab: http://www.askapache.com/optimize/super-speed-secrets.html
chmod -R 777 /var/lib/tftpboot
 
</syntaxhighlight>
 
 
 
 
 
 
 
 
 
 
 
=References=
 
 
 
Ubuntu diskless how-to: https://help.ubuntu.com/community/DisklessUbuntuHowto
 
Super video tutorials:  
 
* https://www.youtube.com/watch?v=js9imsrqAMk
 
* http://www.stepladder-it.com/bivblog/14/ to /16/
 

Latest revision as of 14:37, 21 August 2014


Target folder tree (server side)

This is how we'll setup our files and folders:

# TFTP root
/tftpboot/                                   

###############
# Network bootable image(s) using NFS technology
################       

#### Boot file            
/tftpboot/pxelinux.0                   # Initial boot file - only use to load the PXE NetBoot manager
/tftpboot/{menu.c32 || vesamenu.c32}   # PXE interactive menu managers (text or graphical)
/tftpboot/pxelinux.cfg/                # PXE configuration(s)
/tftpboot/pxelinux.cfg/default         # default PXE configuration

#### Kernel file

/tftpboot/images/      

# Debian 7.x [Wheezy] 
/tftpboot/images/wheezy/   
/tftpboot/images/wheezy/vmlinuz
/tftpboot/images/wheezy/initrd.img

# [X]Ubuntu 14.04 [Trusty] 
/tftpboot/images/trusty/  
/tftpboot/images/trusty/vmlinuz
/tftpboot/images/trusty/initrd.img


#### NFS 
# This is where the runnable will be. Each image will be in a dedicated folder.
/nfs/                    

# Debian 7.x [Wheezy] 
/nfs/wheezy/   

# Ubuntu 14.04 [Trusty] 
/nfs/trusty/


Client overview

Each client must have, at least, 4 Go of RAM.


4 GO RAM configuration

This is how we're gonna populate the client:

NetBoot client RAM overview - 4Go


As you can see, each client will have some space dedicated for swap + some RAMdisk to allow writing in /var, /tmp and /proc.


Configuration of a 4Go RAM disk:

  • No swap
  • Local TMPFS (read/write for /dev, /tmp, ...) : 1 Go
    • /tmp = 512 M
    • /var/tmp = 128 M
    • /var/log = 128 M
    • /var/run = 8 M
    • /var/lock = 8 M
    • /run/shm = 256 M
  • O.S (NFS read only) : all the rest ~ 2.8 Go
  • Common share (NFS read write) : Remote disk


2 Go

Due to budget restriction we might encounter some low memory machines with only 2 Go...


This is how we're gonna populate the client:

NetBoot client RAM overview - 2Go


In case of 2Go RAM then you have to use some tricks:

  • No swap
  • O.S (NFS read only) : ~ 1.2 Go
  • Common share (NFS read write) : Remote disk
  • Local TMPFS (read/write for /dev, /tmp, ...) : all the rest
    • /tmp = 372 M
    • /var/tmp = auto
    • /var/log = 128 M
    • /var/run = auto
    • /var/lock = auto
    • /run/shm = auto


How big is the client image ?

By default the deboostrap Ubuntu 14.04 LTS image is 239 Mo. With the applications we're gonna use that size will increase to about 1 or 1.3 Go depending if you copy (or not) the kernel sources. It may even take 1.6 Go if you're using XFCE frontend.


NFS client image

There are different way to setup a NFS client image.

The main ones are:

  • Manually
    • debootstrap
    • copying the install from your server
    • Manual install on a client, then, when the system is ready, copy everything to the NFS share
  • Using script and software like "Puppet" or "Chef"


Setup client distribution

You have to create one target for each distribution you want to serve:

mkdir -p /nfs/trusty
mkdir -p /nfs/wheezy
mkdir -p /nfs/common


- NOTES -

  • The folder name should match your NetBoot settings. Folder name = a LABEL in the NetBoot config.
  • The folder name should match a Linux (Debian like) distribution name


Configure client distribution



Backup distribution

You can create an archive of your current distribution for later restore / re-use.


Compression

cd /nfs
tar cvpjf trusty.tar.bz2 ./trusty


Restoration

cd /nfs
tar -xvjf trusty.tar.bz2

PXE interactive menu

You can create interactive NetBoot menus, see:



Local server monitoring

Install the following services:



Other services

File sharing

If you want to expose the NFS common folder as a file-share, you have to install and configure Samba. See: Samba server


Note

Samba is actually better than NFS for the file-share. You should remove Common from /etc/exports and use a samba share instead.


Management UI (webmin)

Since there is a lot of services to manage, it's always convenient to use an UI for it. Check Webmin


VPN server

See VPN


Apache2 server

See Apache 2



References

Ubuntu diskless how-to: https://help.ubuntu.com/community/DisklessUbuntuHowto


Mind reference: http://mindref.blogspot.se/2011/03/debian-diskless.html


Super video tutorials:


Nice explanation of PXE process: http://www.linux.com/learn/docs/ldp/497-Diskless-root-NFS-HOWTO