Index: doku/uvmm/uvmm.tex =================================================================== --- doku/uvmm/uvmm.tex (Revision 7432) +++ doku/uvmm/uvmm.tex (Arbeitskopie) @@ -66,12 +66,12 @@ unterschiedliche Vor- und Nachteile. KVM beispielsweise benötigt zwingend CPU-Virtualisierungunterstützung während Xen auch (eingeschränkt) Systeme ohne Unterstützung durch die Hardware virtualisieren kann. Zu -Details können die Webseiten der beiden Projekte konsultiert werden -(\ucsURL{http://www.linux-kvm.org/} und \ucsURL{http://www.xen.org/}). +Details können die Webseiten der beiden Projekte konsultiert werden: +\ucsURL{http://www.linux-kvm.org/} und \ucsURL{http://www.xen.org/}. Zusätzlich sollte bei der Installation der Virtualisierungsserver die Architektur beachtet werden. Nur auf UCS-Systemen, die mit der -amd64-Architektur installiert sind, können auch 64Bit-Systeme +amd64-Architektur installiert sind, können auch 64 Bit-Systeme virtualisiert werden. \section{UMC-Modul} @@ -171,8 +171,9 @@ Verzeichnis} zur Verfügung. Dieser liegt auf den Virtualisierungs-Servern unterhalb des Verzeichnisses \ucsURL{/var/lib/libvirt/images/} (weitere Informationen zur Verwaltung von Speicherbereichen sind im \href{http://wiki.univention.de/index.php?title=UVMM_Quickstart}{Wiki} zu -finden). Zur Einbindung von ISO-Images für CDROM-Laufwerke können -diese ebenfalls in das Verzeichnis kopiert werden. Anschließend stehen sie sofort zur +finden). +Zum Einbinden als CDROM-Laufwerke können ISO-Images ebenfalls in diese Verzeichnis kopiert werden. +Anschließend stehen sie sofort zur Verfügung und können mit neuen Laufwerken verknüpft werden. Werden Laufwerke für eine neu zu installierende Instanz definiert, @@ -186,7 +187,7 @@ Ist eine virtuelle Instanz mit dem Assistenten erfolgreich angelegt worden, zeigt das UMC-Modul sofort die Übersicht zu der neuen Instanz -an. Die Einstellungen einer Instanz sind in drei Bereiche aufgeteilt +an. Die Einstellungen einer Instanz sind in mehrere Bereiche aufgeteilt (Abbildung \ref{pic:uvmm-domain-settings}): \begin{itemize} @@ -213,7 +214,7 @@ Die Grundeinstellungen einer virtuellen Instanz sind unter \ucsMenuEntry{Einstellungen} zu finden. Dort gibt es folgende Felder, die nur verändert -werden können, wenn die virtuelle Instanz ausgeschaltet ist: +werden können, wenn die virtuelle Instanz ausgeschaltet ist und keine Sicherungspunkte angelegt sind: \begin{description} \item[Name] definiert den Namen der virtuellen Instanz. Dieser muss @@ -222,7 +223,7 @@ installierten Betriebssystems genutzt werden \item[Architektur] legt die Architektur der emulierten Hardware fest. Dabei ist zu beachten, dass nur auf Virtualisierungs-Servern - der Architektur amd64 virtuelle 64-Bit-Instanzen angelegt werden + der Architektur amd64 virtuelle 64 Bit-Instanzen angelegt werden können. Dies wird vom UMC-Modul auf i386-Systemen auch unterbunden. \item[Anzahl der CPUs] definiert wieviele virtuelle CPUs der virtuellen Instanz zugeteilt werden. Index: doku/uvmm/uvmm_en.tex =================================================================== --- doku/uvmm/uvmm_en.tex (Revision 7432) +++ doku/uvmm/uvmm_en.tex (Arbeitskopie) @@ -112,11 +112,13 @@ following section on the description of the functions. \subsection{Creating a virtual instance} +\label{uvmm:instanz:erstellen} + The \ucsUMC{} module has a wizard for creating virtual instances, which can be used to create a virtual machine in just a few steps. In the first step a profile is selected which specifies some of the basic -settings for the virtual machine (e.g., a name prefix, no. of CPUs, -RAM and whether the access per VNC should be activated). As can be +settings for the virtual machine (e.g., a name prefix, number of CPUs, +RAM and whether the direct access per VNC should be activated). As can be seen in Figure \ref{pic:uvmm-instance-wizard}, there are profiles for different operating systems. Depending on the operating system, some parameters for the virtualisation are defined in the UVMM profile. For @@ -125,58 +127,57 @@ \ucsGraphicsRef[0.95]{Assistant for creating a virtual machine}{../doku/uvmm/abbildungen/uvmm-instance-wizard_en.png}{uvmm-instance-wizard} -The existing UVMM profiles are read out of the LDAP directory and can +The existing UVMM profiles are stored in the LDAP directory and can also be edited there. The profiles can be found in the \ucsMenuEntry{Navigation} section of \ucsUDM{} in the -container \emph{cn=Profiles,cn=Virtual Machine Manager}. Additional -ones can also be added here that have been adapted to suit the -respective environment. +container \emph{cn=Profiles,cn=Virtual Machine Manager}. +Additional profiles which have been adapted to suit the respective environment can also be added there. -Once the basic configuration of the virtual machine is complete, the drives -are defined. These can also be adapted subsequently just like the -configuration of the machine. When adding drives, image files are +Once basic configuration of the virtual machine is complete, the drives +are defined. +Subsequently existing drives can be removed and new drives can be created. +When adding drives, image files are created for virtual hard drives or existing files are linked to the hard drives or CDROM drives. Hard drive images can be administrated in two ways on KVM systems; by -default images are saved in the \ucsName{Qemu copy-on-write 2} -format. Copy-on-write means that a change in a file system does not -directly change the actual file, but rather stores a new version in a -different place. The internal references of the file administration -are then updated. This allows you to create snapshots of the file -systems of virtual machines. +default images are saved in the \ucsName{Extended format (qcow2)} +format. +This format supports Copy-on-write which means that changes do not overwrite the original version, but store new versions in different locations. +The internal references are updated to allow both access to the original and the new version. +This technique is a prerequisite for efficiently managing snapshots of virtual machines. Alternatively, you can also access a hard drive image -in \ucsName{Raw format}. Snapshots can only be created when using -hard drive images in \ucsName{Qemu copy-on-write 2} format. +in \ucsName{Simple format (raw)}. Snapshots can only be created when using +hard drive images in the \ucsName{Extended format}. -Only the \ucsName{Raw format} is available on Xen systems. +For Xen systems only the \ucsName{Simple format} is available. These image files are stored in so-called -storage pools. Each virtualisation server already provides a storage -pool with the name \emph{Local directory} in the default -setting. This can be found on the virtualisation servers in -the \ucsName{/var/lib/libvirt/images} directory (further information -on the management of storage pools can be found in Wiki). ISO images -can also be copied into this directory for mounting with CDROM -drives. They are then immediately available and can be linked with new +storage pools. +By default each virtualisation server already provides a storage pool with the name \emph{Local directory}. +This can be found on the virtualisation servers in +the \ucsURL{/var/lib/libvirt/images/} directory (further information +on the management of storage pools can be found in the \href{http://wiki.univention.de/index.php?title=UVMM_Quickstart}{Wiki}). +For mounting CDROM drives ISO images can also be copied into this directory. +They are then immediately available and can be linked with new drives. -If drives are defined for an virtual machine to be installed from new, it -must be ensured that it is possible to boot from the CDROM drive. The -UVMM profile specifies the boot order for the fully-virtualised -instances in advance. For the paravirtualised instances, it is defined -by the order on the definition of the drives and can be adapted -subsequently in the settings. +For new virtual machines the order of creating new drives is important. +It must be ensured that it is possible to boot from the CDROM drive. +The UVMM profile specifies the boot order for fully-virtualised instances in advance. +For paravirtualised instances, the first device listed is always used as the boot device. +This can be changed subsequently in the settings section. \subsection{Modifying virtual machines} \label{uvmm-instance-edit} When a virtual instance is successfully created with the wizard, the UMC module displays an overview of the new instance immediately. The -settings of a virtual machine are divided into three areas +settings of a virtual machine are divided into multiple sections (Figure \ref{pic:uvmm-domain-settings}): \begin{itemize} +\item Snapshots \item Drives \item Settings \item Extended settings @@ -184,7 +185,7 @@ \ucsGraphicsRef[0.95]{Settings of a virtual machine}{../doku/uvmm/abbildungen/uvmm-domain-settings_en.png}{uvmm-domain-settings} -The \ucsMenuEntry{Drives} menu contains a list of the defined drives +The \ucsMenuEntry{Drives} section contains a list of the defined drives with the type, image file and size as well as the assigned storage pool. At the end of each line there is a \ucsMenuEntry{Delete} button, which can be used to remove the drive (the image file can @@ -195,31 +196,32 @@ images can also be created for hard drives. These are created as sparse files with the specified size, i.e., these files only grow when they are used and then up to the maximally specified size and thus -initially require only minimal memory space. +initially require only minimal disk space. -The basic settings of a virtual instance can be found -in \ucsMenuEntry{Settings}. This includes the following fields -which can only be changed if the virtual instance is turned off. +The basic settings of a virtual instance can be found in the \ucsMenuEntry{Settings} section. +This includes the following fields +which can only be changed if the virtual instance is turned off and no snapshots are used. \begin{description} \item[Name] defines the name of the virtual machine. This does not have to be the same as the name of the host in the LDAP directory. +\item[Operating System] can contain a description of the virtual instance or of the operating system used. \item[Architecture] specifies the architecture of the emulated -hardware. It must be noted that virtual 64-bit machines can only be -created on virtualisation servers with an amd64 architecture. This is -also suppressed on i386 systems by the UMC module. +hardware. It must be noted that virtual 64 bit machines can only be +created on virtualisation servers using the amd64 architecture. +This setting is not shown on i386 systems. \item[Number of CPUs] defines how many virtual CPUs are assigned to the virtual instance. \item[MAC address] specifies the hardware address of the network -interface. If this field is not completed, a random value is -automatically entered. +interface. If this field is left empty, a random value is +automatically generated. \item[Memory] specifies the size of the system memory. \item[Interface] defines the interface used for the bridge on the physical server. This is usually \emph{eth0}, which is also the default setting. \end{description} -In the third area \emph{Extended settings}, you can find the following +In the last section \emph{Extended settings}, you can find the following attributes: \begin{description} @@ -230,13 +232,13 @@ the virtual machine searches the drives for bootable media. This setting is only available for fully-virtualised instances. For paravirtualised instances it is defined by the order of the drives. -\item[VNC remote access] defines whether VNC access to the virtual +\item[Direct access] defines whether VNC access to the virtual machine is available. If the option is activated, the UMC module can be used to start a VNC program directly. The VNC URL is displayed in a tool tip. -A Java VNC program is used for this in the default setting. \ucsUCRV{uvmm/umc/vnc} can be -used to define the \emph{external} value, which means that an external -program should be used. This must be installed on the workplace -computer and linked with the URI scheme vnc://. +A Java VNC program is used for this in the default setting. +By switching the \ucsUCRV{uvmm/umc/vnc} to the value of \emph{external}, an external +program can be used instead. +This requires the web browser on the workstation computer to be configured properly to handle the URI scheme \ucsURL{vnc://}. \item[Available globally] defines whether the VNC remote access is also possible from remote systems. If the option is not activated, the VNC session can only be accessed from the virtualisation server. @@ -248,22 +250,23 @@ \subsection{Removing virtual machines} Virtual instances no longer required can be deleted along with all their hard drives and ISO images. The images to be deleted can be -selected in a list. It must be noted that ISO images and sometimes -also hard drive images may still be being used by other instances. +selected from a list. It must be noted that ISO images and sometimes +also hard drive images may be used by multiple instances. +They only should be deleted when the are no longer used by any instance. \subsection{Starting/stopping/suspending virtual machines} Instances created via UVMM are turned off in the initial status. This status can changed in the overview of the respective virtualisation server in the respective list entry or in the overview of the virtual machine itself. In the latter case, there is -an \ucsMenuEntry{Operations} option, in which the status can be +an \ucsMenuEntry{Operations} section, in which the status can be set. The following possibilities exist: \begin{description} \item[Start] starts the virtual machine. \item[Stop] turns the virtual machine off. It must be noted that the operating system is not turned off first, i.e., it should be -compared with the turning off of a computer. +compared with turning off a computer by pulling the power plug. \item[Pause] assigns the instance no further CPU time. This still uses the working memory on the physical host, but the instance itself is paused. @@ -278,39 +281,37 @@ \end{description} \subsection{Migrating virtual machines} -A further function which can be found in the \emph{Operations} area +A further function which can be found in the \emph{Operations} section of the overview is the possibility of a migrating a virtual machine to another virtualisation server. This works with both paused and running instances (live migration). -During the migration it must be noted that the images of the mounted -hard drives and CDROM drive must be in the same directory on both -physical servers. This can be done, for example, by storing the images +For migration to work it must be noted that the images of the mounted +hard drives and CDROM drive must be available in the same location on both +physical servers. This can be archived, for example, by storing the images in a central storage system. \subsection{Managing snapshots} UVMM offers the possibility to save the contents of the main and -hard drive memory of a virtual machine in the \ucsName{Snapshots} -menu. This allows the administator to revert to these snapshots -at a later point in time, which makes them a useful ``safety net'' +hard drive memory of a virtual machine in \ucsName{Snapshots}. +This allows the administrator to revert the virtual instance back to these snapshots +at a later point in time, which makes them useful as a ``safety net'' when installing software updates. -Snapshots can only be used in KVM instances which access their hard +Snapshots can only be used with KVM instances which access all their hard drive images in Qcow2 format. All snapshots are stored using copy-on-write (see \ref{uvmm:instanz:erstellen}) directly in the hard drive image file. -The administration is performed via \ucsMenuEntry{Snapshots} in the +The administration is performed in the \ucsMenuEntry{Snapshots} section in the settings of a virtual machine. \ucsMenuEntry{Create new snapshot} can be used to create a snapshot with the name of your choice, e.g., \emph{DC Master before -update to UCS 2.4-2}. This is then listed with its time of -creation. \ucsMenuEntry{Revert} can be used to return the machine to +update to UCS 2.4-2}. +In addition to the description the time is saved when the snapshot is created. +The following list shows all available snapshots ordered reverse-chronologically. +\ucsMenuEntry{Revert} can be used to return the machine to an earlier snapshot and \ucsMenuEntry{Delete} can be used to remove a snapshot. - - - -