Introduction

-Additionally, you will need to specify the attrs option in -/etc/fstab for your vserver partition: -

@@ -143,7 +139,7 @@ # make (Installing) # make modules_install -# cp arch/i386/boot/bzImage /boot/kernel-<KERNELVERSION>-vserver-<VSERVERVERSION> +# cp arch/<arch>/boot/bzImage /boot/kernel-<KERNELVERSION>-vserver-<VSERVERVERSION> (Edit bootloader config file as required and) # reboot @@ -156,23 +152,26 @@

To maintain your virtual servers you need the util-vserver package which -contains all necessary programs and many usefull features. +contains all necessary programs and many useful features. Be aware that there +is also a package called vserver-utils. It is a new incarnation of the +user-space implementation of the VServer kernel API, but not yet usable for +production use.

@@ -247,7 +251,7 @@

 # cd /vservers/gentoo-template
-# tar cjvpf ../gentoo-template.tar.bz2 ./
+# tar cjvpf ../gentoo-template-<arch>-<date>.tar.bz2 ./

@@ -260,12 +264,12 @@ --hostname myguest \ --context 1252 \ --interface eth0:192.168.1.252/24 \ - template ./gentoo-template.tar.bz2 + template ./gentoo-template-<arch>-<date>.tar.bz2 <arch> -You should use a shared portage tree for your guests to keep guests small in -size. Edit /etc/vservers/myguest/fstab and uncomment the entries +You should use a shared portage tree to keep guests small in size. Edit +/etc/vservers/myguest/fstab and uncomment the entries for /usr/portage and /usr/portage/distfiles. Guests will have read-only access to /usr/portage and read-write access to /usr/portage/distfiles. @@ -302,13 +306,140 @@ + + + +Maintenance made easy +

+Start guests on boot + + +

+You can start certain guests during boot. Each guest can be assigned a MARK. +Now everything you have to do is configure these MARKs in the guests +configuration and tell the init script to run all MARKed guests. +

+ +

+(Do this for every guest you want to start)
+# mkdir -p /etc/vservers/myguest/apps/init
+# echo "default" > /etc/vservers/myguest/apps/init/mark
+

+ + +Since all guests marked with "default" are started by default, nothing more has +to be done. If you have different marks you should also update +/etc/conf.d/vservers. + + + +

+Gentoo goodies + + +

+The util-vserver ebuild has installed some goodies for Gentoo guests. You know +vserver-new from the previous chapter. In this chapter, you will learn +how to use vesync and vemerge to keep portage in sync as well as +vupdateworld and vdispatch-conf to update guests. +

+ + +

+Keep portage in sync + + +

+The script vesync will help you to keep the metadata cache and overlays +in sync. vemerge is a simple wrapper for emerge in guests. +

+ +

+(Sync metadata for 'myguest')
+# vesync myguest
+(Sync metadata for all guests)
+# vesync -a
+(Sync metadata for all guests except 'myguest')
+# vesync -a -e myguest
+(Sync 'myoverlay' for all guests)
+# vesync -a \
+  --overlay /usr/local/overlays/myoverlay \
+  --overlay-host rsync://rsync.myhost.com/myoverlay \
+  --overlay-only
+(emerge app-editors/vim in 'myguest')
+# vemerge myguest app-editors/vim -va
+

+ + +This script requires you to have a shared portage tree. + + + +

+Update guests + + +

+Gentoo guests can share packages to save compilation time. In order to use +shared packages, you have to create a central directory for packages on the +host. We will use /var/cache/vpackages on the host and mount it +to /usr/portage/packages in every guest. +

+ +

+# mkdir -p /var/cache/vpackages
+# $EDITOR /etc/vservers/myguest/fstab
+(Add this line at the end)
+/var/cache/vpackages /usr/portage/packages none bind,rw 0 0
+

+ +

+Now you can use vupdateworld to update every guest. The command is +equivalent to something like emerge --deep --update --newuse world +depending on command line options. +

+ +

+(Pretend update for 'myguest')
+# vupdateworld -p myguest
+(Update 'myguest' using binary packages)
+# vupdateworld -k myguest
+(Update all guests using binary packages)
+# vupdateworld -ka
+

+ + +In order to get binary packages you can either use PORTAGE_BINHOST (see man +make.conf) or set FEATURES="buildpkg" in one or more guests. + + +

+After a successful update you can easily update all configuration files with +vdispatch-conf. It is a simple wrapper for dispatch-conf and +behaves exactly the same. +

+ +

+(Update configuration files for 'myguest')
+# vdispatch-conf myguest
+(Update configuration files for all guests)
+# vdispatch-conf -a
+

+ + +

Contact

-Please feel free to contact the author or file a bug on Bugzilla in case of any problems. +Please feel free to contact the author or +file a bug on Bugzilla in case of any +problems.

-- gentoo-doc-cvs@gentoo.org mailing list