%% This is file `a4-de-en-xen.tex'.
%% Written in its current form by Jörg Pernfuß for the ongoing
%% efforts of the german allBSD.de BSD advocacy project.
%% It is intentionally based on the work done by Stefan Schumacher, to
%% achieve a consistent identity for all used NetBSD advocacy flyers.
%% The german text was initially written by Rainer Brinkmöller and the
%% english translation was provided by Lars %NACHNAME%.
%% Suggestions from various others have been incorporated, see the
%% allbsd-misc@ archive for detailed information.
%%
%% All registered trademarks belong to their owner.
%% The BSD daemon is copyright Marshall Kirk McKusick and
%% free to use in non-commercial bsd-positive advocacy.
%% The NetBSD logo is copyright The NetBSD Foundation and
%% free to use in non-commercial bsd-positive advocacy.
%%
%% The file this was based on had the following copyright remarks:
%
% $Id: netbsd-a4-flyer-de+en-xen.tex,v 1.1 2006/03/12 14:35:52 hubertf Exp $
% written by Stefan Schumacher, <stefan [at] net-tex.de>, 2006-01-08
% Die Urheberrechtshinweise dürfen nicht entfernt werden.
%\rcsInfo $Id: netbsd-a4-flyer-de+en-xen.tex,v 1.1 2006/03/12 14:35:52 hubertf Exp $
%{\scriptsize Version \rcsInfoRevision\ as of
%\rcsInfoYear-\rcsInfoMonth-\rcsInfoDay. See \texttt{http://www.net-tex.de/netbsd/advocacy} All rights reserved. Created by Stefan Schumacher
%(\texttt{http://www.net-tex.de})}
% Do not remove my copyright notice!
%
%% If you find this document, or the allBSD.de efforts in general, useful,
%% come visit us at a BSD booth. Bring beer.

%% Definitions
\def\filedate{2006/03/10}
\def\fileversion{1.0.4}

%% Basic declarations, package includes
\documentclass[9pt,a4paper]{article}
\usepackage[pdftex]{graphicx}
\usepackage{multicol}
\usepackage[latin1]{inputenc}
\usepackage[ngerman]{babel}
\usepackage[margin=10mm,nohead,nofoot]{geometry}
\setlength{\parindent}{0pt}
%%
%% Establish new command: mySection  
%% 
\newcommand{\mySection}[1]{\begin{center}\large{\sffamily\bfseries #1}\end{center}}

\newcommand{\reg}{\textsuperscript{\textregistered~}}
\newcommand{\trade}{\textsuperscript{\texttrademark~}}

%%
%%
%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% PAGE 1
%%
%%
\begin{document}
\pagestyle{empty}
%%
%% Header
%%
\begin{center}
\includegraphics[scale=0.8]{head.jpg}
\rule{\textwidth}{0.5pt}
\end{center}
%%
%% Body
%% 
\begin{multicols}{2}\setlength{\columnseprule}{0.3pt}
%%
%% Page 1 - German
%%
\mySection{Virtualisierung mit Xen}
Xen ist ein, ursprünglich an der Universität von Cambridge entwickelter,
Open Source Virtual-Machine-Monitor für x86-Hardware.
Die Entwickler haben mit XenSource ein Unternehmen gegründet, das
Xen als Industriestandard etablieren möchte. Xen verwendet die GPL als
Lizenzmodell.
%%
\mySection{Architektur}
Xen bildet mittels eines eigenen Kernels eine Schnittstelle 
zwischen der Hardware und dem Hostsystem. Das Hostsystem wird
innerhalb des Xen-Umfelds auch priviligierte Domain (Dom0) genannt.
Die Konfiguration und Steuerung der da\-rauf aufsetzenden,
unpriviligierten Gastsysteme (DomU) wird durch diese Domain
übernommen. Den Gastsystemen werden hier Ressourcen, wie
zum Beispiel Anteile am verfügbaren Arbeitsspeicher, Festplattenplatz
sowie Schnittstellen zu Geräten wie Netzwerkkarten, zugewiesen.
Die Anzahl der Gastbetriebssysteme wird lediglich durch die
verfügbaren Ressourcen und deren Verteilung begrenzt.
Xen selbst benötigt hierbei je Gast-Domain weniger als 32 KiByte
Arbeitsspeicher.
%%
\mySection{Unterstützte Betriebssysteme}
Die Xen-Architektur bietet nicht nur gute Performance sondern führt
insgesamt zu einer hohen Stabilität und Unabhängigkeit der
Betriebssystem-Umgebungen. Neben NetBSD\reg und FreeBSD wird Xen
auch von weiteren Open-Source-Betriebssystemen, wie zum Beispiel
Linux und Plan9, unterstützt.
%%

Sowohl NetBSD\reg als auch FreeBSD können derzeit mit Xen in der
Version 2.0.x eingesetzt werden. An den notwendigen Anpassungen für die
Nutzung der Version 3 wird bei beiden BSDs gearbeitet. Xen 3 bietet im Gegensatz
zur Version 2 unter anderem Unterstützung für SMP und 64Bit-Architekturen.
%%
\mySection{Einsatzmöglichkeiten}
Mögliche Einsatzgebiete sind z.~B. sicherheitsrelevante
n-Tier-Umgebungen. BSD/Xen-Umgebungen ermöglichen zudem
die Senkung der Betriebskosten bei hoher Stabilität und
bestmöglicher Performance. Dies gilt sowohl für verteilte
Applikations- als auch Datenbank-, Mail-  und/oder Webserver.
Hier können Hardwarekosten gesenkt und die Ressourcennutzung optimiert
werden. Auch langfristige Skalierbarkeit ist ein weiterer
Grund, der für den Einsatz von BSD/Xen im produktiven Umfeld spricht.
%%
\mySection{Hardware-Support}
Die für 2006 angekündigten neuen Prozessoren von Intel\trade und AMD\trade
ermöglichen es, durch die Technologien \glqq{}Vanderpool\grqq{} bzw. \glqq{}Pacifica\grqq{},
Gastsysteme unter Xen 3 zu verwenden, ohne dass eine Anpassung der
Betriebssyteme notwendig ist.
Auf Computern, in welchen diese Prozessoren verwendet werden, soll
nahezu jedes Betriebssystem für x86 oder IA64 als Xen3-Gastsystem
eingesetzt werden können.
%%
\mySection{Weiterführende Informationen}
\begin{itemize}\itemsep-1ex
\item http://www.NetBSD.org/de/Ports/xen/
\item http://de.wikipedia.org/wiki/Xen
\item http://www.cl.cam.ac.uk/Research/SRG/netos/xen/
\item http://www.xensource.com/
\end{itemize}
\end{multicols}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\mySection{Ein Fallbeispiel:}
\begin{minipage}[c][85mm][t]{0.5\textwidth}%
\begin{center}%
\includegraphics[scale=0.96]{../../in-Action/brinkmoeller-xen.png}\\%
{\small Eine n-Tier-Architektur, die durch unterschiedliche Xen-Domains Datenbank- und Applikationsserver abgrenzt.}%
\end{center}%
\end{minipage}% linke MP mit Bild
%
\begin{minipage}[c][85mm][t]{0.5\textwidth}%
Die Abbildung zeigt einen KDE-Screenshot der Xen-Dom0.
Oben links sehen Sie im KDE-Konqueror die Webapplikation ,,JPetstore`` dargestellt.
Einen VNC-Bildschirm einer dedizierten DomU und des darin laufenden
,,Tomcat Application Managers``, sehen Sie oben rechts.
Als Backend für diese Installation dient eine, ebenfalls in einer
dedizierten DomU betriebene, PostgreSQL-Datenbank. Einen VNC-Bildschirm dieser DomU mit pgsql-Konsole sehen Sie
unten rechts.
Unten links ist die in der Dom0 laufende xenconsole abgebildet, die der
Überwachung der DomUs dient. Neben den beiden im Beispiel verwendeten
DomUs, zeigt diese noch zwei weitere an.
Sowohl in der Dom0 als auch in allen DomU läuft NetBSD\reg 3.0.~\\


\textbf{Weiterführende Informationen:}
\begin{itemize}\itemsep-1ex%
\item http://ibatis.apache.org/
\item http://tomcat.apache.org/
\item http://www.postgresql.org/
\item http://ucck.sourceforge.net/xenConsole/
\end{itemize}%
\end{minipage}%
%
\vfill
%%
%% Footer
%%
\begin{center}
\rule{\textwidth}{0.5pt}
\texttt{\begin{tiny}v\fileversion{} - \filedate{} | \copyright\ allBSD.de - Text by Rainer Brinkmöller | BSD Daemon \copyright\ Kirk McKusick | NetBSD Logo \copyright\ The NetBSD Foundation | All Trademarks belong to their owners\end{tiny}}
\end{center}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%  ___           _ _        _    
%% | __|_ _  __ _| (_)___ __| |_  
%% | _|| ' \/ _` | | (_-</ _| ' \ 
%% |___|_||_\__, |_|_/__/\__|_||_|
%%          |___/                 
%% 
%%
%%
\clearpage
\pagestyle{empty}
%%
%% Header
%%
\begin{center}
\includegraphics[scale=0.8]{head.jpg}
\rule{\textwidth}{0.5pt}
\end{center}
%%
%% Body
%% 
\begin{multicols}{2}\setlength{\columnseprule}{0.5pt}
%%
%% Page 2 -> English
%%
\mySection{Virtualisation with Xen}
Xen is an open source virtual machine monitor for x86 hardware
initially developed at the University of Cambridge.
The developers have formed a company, XenSource, which aims to establish Xen
as an industry standard. Xen is released under the terms of the GPL.
%%
\mySection{Architecture}
Xen uses its own kernel to act as an interface between the hardware
and the host operating system. Within the Xen context the host system is also called 
the privileged domain (Dom0), which handles control and configuration 
of the unprivileged guest systems (DomU) running on top of it. It allocates 
resources, such as memory ranges, disk space and provides interfaces for
the DomU guest systems to physical hardware devices.
The number of guest systems is limited only by the available resources
and their allocation. Xen itself requires less than 32 KiByte of RAM per 
guest system.
%%
\mySection{Supported operating systems}
The Xen architecture is not only a high-performance virtualisation 
technology, but also increases service availability and operating system 
independence. Aside from NetBSD\reg and FreeBSD, Xen also suppports
other open source operating systems such as Linux and Plan9. Both
BSDs currently support Xen version 2.0.x, with support for Xen 3 being
actively developed. Xen 3 offers, among other improvements, support
for SMP and 64bit architectures.
%%
\mySection{Deployment}
Possible deployment scenarios include not only security-relevant n-tier
environments. BSD/Xen enables you to lower operational costs
while still maintaining high availability and performance for
distributed applications, databases, mail and web services.
Here the cost of hardware can be lowered and the use of resources optimised.
Long term scalability is another reason to consider BSD/Xen in
production environments.
%%
\mySection{Hardware-Support}
New processors announced for 2006 will include the new technologies
``Vanderpool'' (Intel\trade) or ``Pacifica'' (AMD\trade), enabling Xen 3
to run unmodified guest operating systems.
This means that practically any operating system that runs on x86 or 
IA64 will run on Xen as a guest operating system.
%%
\mySection{See also:}
\begin{itemize}
\item http://www.NetBSD.org/Ports/xen/
\item http://en.wikipedia.org/wiki/Xen
\item http://www.cl.cam.ac.uk/Research/SRG/netos/xen/
\item http://www.xensource.com/
\item http://www.intel.com/technology/computing/vptech/
\item http://www.amd.com/us-en/Weblets/~\\0,,7832\_8366\_7595\textasciitilde 94608,00.html
\end{itemize}
\end{multicols}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\mySection{A Case study:}
\begin{minipage}[c][85mm][t]{0.5\textwidth}%
\begin{center}%
\includegraphics[scale=0.96]{../../in-Action/brinkmoeller-xen.png}\\%
{\small A n-tier architecture that segregates the application server and the database server
by placing them in different Xen domains.}%
\end{center}%
\end{minipage}% linke MP mit Bild
%
\begin{minipage}[c][85mm][t]{0.5\textwidth}%
The figure shows a KDE screenshot from the Dom0.
In the upper left, one can see a Konqueror, showing the web\-application JPetstore.
This application was deployed with Tomcat 5 in a dedicated DomU. A VNC
screen of this DomU and the Tomcat application manager is found in the upper right.
As backend of this installation serves a, again running in its own dedicated DomU, PostgreSQL data\-base.
A VNC screen of this DomU depicting a pgSQL console is in the lower right.
Lastly, in the lower left corner is a terminal running the xenconsole, which provides convenient means to
monitor the DomU. Aside from the DomUs used in this example, as we can see, there are two more
DomU running on this machine. The Dom0 as well as all DomU run on NetBSD\reg 3.0.\\

\textbf{See also:}
\begin{itemize}
\item http://ibatis.apache.org/
\item http://tomcat.apache.org/
\item http://www.postgresql.org/
\item http://ucck.sourceforge.net/xenConsole/
\end{itemize}%
\end{minipage}%
%
\vfill
%%
%% Footer
%%
\begin{center}
\rule{\textwidth}{0.5pt}
\texttt{\begin{tiny}v\fileversion{} - \filedate{} | \copyright\ allBSD.de - Text by Rainer Brinkmöller | BSD Daemon \copyright\ Kirk McKusick | NetBSD Logo \copyright\ The NetBSD Foundation | All Trademarks belong to their owners\end{tiny}}
\end{center}
%%
%%
%%
\end{document}