Virtual Servers

Virtual Server Creation, and Deployment

Introduction

• Gentoo Linux, kernel 2.6.17-vs2.0.2.1-gentoo on host server
• Gentoo Linux, kernel 2.6.17-vs2.0.2.1-gentoo on virtual nodes

There are two methods to create vserver nodes on the vs2.0.2.1-gentoo vserver. Each method begins differently, but the final setup is the same. The directions contained in this note may appear saturated by the words vserver, vsrvr, vservers, and vs0n. Due to the default vserver directory naming conventions, and the vserver node naming convention (i.e. vs00, vs01, etc.) this name-clutter is unavoidable. If setup does not follow spec, please examine your syntax carefully.

Create a Vserver Template

vsrvr / # vserver vs0n enter

vs0n / # shutdown -h now

vsrvr / # cd /vservers/vs0n

vsrvr vs0n # tar cvf vs.template*.tar bin boot etc fastboot home lib mnt root sbin sys tmp usr var

• DO NOT INCLUDE /DEV OR /PROC

vsrvr vs0n # cp /vservers/vs0n/vs.template*.tar /vserver.template/

• Be careful to examine the /vserver.template/ directory for pre-existing vs.template*.tar files before naming any new tar files. vs.template.tar is the stock template, so name new templates vs.template.00.tar, etc. Using non-stock templates will have an impact on the *.tar name used in point 4 in the next section of this note.

• GOTO "Use the Vserver Stock Template"

Use the Vserver Stock Template

vsrvr / # vserver vs0n build -m skeleton --hostname vs0n --context 563n --interface vs0n=eth0:209.87.56.3n/24

• Make sure to check /vservers directory for pre-existing vs0n nodes matching the desired vnode name
• Make sure to correct/match every vs0n reference in the vnode creation line; there are 3 references.
• Make sure to correct/match the IP statement eth0:209.87.56.3n/24 with the IP stated in the context.
• Make sure the context matches the values of the last two octets of the target vnode IP

vsrvr / # cd /vservers/vs0n

vsrvr vs0n # tar -xvf /vserver.template/vs.template*.tar

Post Vnode Creation Setup

• Several directories will need to be customized, post vnode creation, to make the vnode unique.
• Changes must be made in the /etc/vservers/vs0n and the /vservers/vs0n before the new vnode will be ready to start.

Changes to /etc/vservers/vs0n

• To allow vnode to boot, we need to copy over init instructions.

vsrvr / # cp /vserver.template/init/* /etc/vservers/vs0n/apps/init/

• To allow for proper service initialization, we need to add eth:lo and renumber interface 0 and 1.

vsrvr / # mv /etc/vservers/vs0n/interfaces/0 /etc/vservers/vs0n/interfaces/1

vsrvr / # cp -r /vserver.template/interfaces/0 /etc/vservers/vs0n/interfaces/

vsrvr / # cp -r /vserver.template/fstab /etc/vservers/vs0n
cp: overwrite `/etc/vservers/vs0n/fstab'? yes

Chnages to /vservers/vs0n

• To allow for proper service initialization, we need to change hostname and IP addresses in the following files.

vsrvr / # vi /vservers/vs0n/etc/ssh/sshd_config

vsrvr / # vi /vservers/vs0n/etc/conf.d/hostname

vsrvr / # vi /vservers/vs0n/etc/hosts

vsrvr / # vi /vservers/vs0n/etc/conf.d/net

vsrvr / # vi /vservers/vs0n/etc/conf.d/domainname

vsrvr / # vi /vservers/vs0n/etc/mysql/my.cnf

vsrvr / # vi /vservers/vs0n/etc/apache2/httpd.conf

vsrvr / # vi /vservers/vs0n/etc/apache2/modules.d/40_mod_ssl.conf

START YOUR VSERVER

vsrvr / # vserver vs0n start
vsrvr / # vserver vs0n enter

PASSWORD

• Don't forget to set a new root password.