summaryrefslogtreecommitdiff
path: root/2005/flow-accounting-ols2005/OLS2005/vasilevsky
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2015-10-25 21:00:20 +0100
committerHarald Welte <laforge@gnumonks.org>2015-10-25 21:00:20 +0100
commitfca59bea770346cf1c1f9b0e00cb48a61b44a8f3 (patch)
treea2011270df48d3501892ac1a56015c8be57e8a7d /2005/flow-accounting-ols2005/OLS2005/vasilevsky
import of old now defunct presentation slides svn repo
Diffstat (limited to '2005/flow-accounting-ols2005/OLS2005/vasilevsky')
-rw-r--r--2005/flow-accounting-ols2005/OLS2005/vasilevsky/Makefile.inc7
-rw-r--r--2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky-abstract.tex53
-rw-r--r--2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky.tex100
3 files changed, 160 insertions, 0 deletions
diff --git a/2005/flow-accounting-ols2005/OLS2005/vasilevsky/Makefile.inc b/2005/flow-accounting-ols2005/OLS2005/vasilevsky/Makefile.inc
new file mode 100644
index 0000000..7253bab
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/vasilevsky/Makefile.inc
@@ -0,0 +1,7 @@
+PAPERS += vasilevsky/vasilevsky.dvi
+
+## Add any additional .tex or .eps files below:
+vasilevsky/vasilevsky.dvi vasilevsky/vasilevsky-proc.dvi: \
+ vasilevsky/vasilevsky.tex \
+ vasilevsky/vasilevsky-abstract.tex
+
diff --git a/2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky-abstract.tex b/2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky-abstract.tex
new file mode 100644
index 0000000..7e8fe69
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky-abstract.tex
@@ -0,0 +1,53 @@
+
+% Registration Linux Virtualization on Virtual Iron VFe
+% [2]Register/Submit Proposal Alex Vasilevsky (alex@virtualiron.com)
+
+After many years of research and development,
+the concept of cluster-based computing
+seamlessly integrating a set of computing
+resources into a cohesive whole has gone
+largely unfulfilled. The barrier to adoption
+of cluster-based computing has been that
+applications must be made cluster-aware. The
+best technology that is currently available is
+a set of middleware tools, such as the Globus
+toolkit, which is used to rework applications
+to run on a cluster. Because it is difficult
+to make applications run in parallel on a
+cluster, only a handful of highly specialized
+applications sometimes referred to as
+``embarrassingly parallel'' applications, have
+been made cluster-aware. Of the very few
+commercial cluster-aware applications, the
+best known is Oracle Database Real Application
+Clustering. Virtual Iron(R) Software has
+solved these problems by creating Virtual Iron
+VFe, which allows any applications to
+transparently run on a tightly-coupled
+cluster of computers without any
+modifications. This software elegantly
+abstracts the underlying cluster of servers
+with a Distributed Virtual Machine Monitor.
+Like many other Virtual Machines Monitors,
+this software layer takes complete control of
+the underlying hardware and creates virtual
+machines, each of which behaves like a
+complete physical machine running its own
+operating system in full isolation. In
+contrast to other existing Virtual Machines
+Monitors, the Distributed Virtual Machine
+Monitor creates a virtual multi-processor on a
+collection of tightly coupled servers. The
+system gives guest operating systems the
+illusion that it is running on a single
+multi-processor machine with \textit{N} CPUs on top
+of \textit{M} physical servers interconnected by
+networks. In this paper we'll describe Linux
+Virtualization on Virtual Iron VFe, the
+virtualization capabilities of the Virtual
+Iron(R) Distributed VMM technology, as well as
+the changed made to the Linux kernel to take
+advantage of this new distributed
+virtualization technology.
+
+
diff --git a/2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky.tex b/2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky.tex
new file mode 100644
index 0000000..70e87f3
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/vasilevsky/vasilevsky.tex
@@ -0,0 +1,100 @@
+% The file must begin with this \documentclass declaration. You can
+% give one of three different options which control how picky LaTeX
+% is when typesetting:
+%
+% galley - All ``this doesn't fit'' warnings are suppressed, and
+% references are disabled (the key will be printed as a
+% reminder). Use this mode while writing.
+%
+% proof - All ``this doesn't fit'' warnings are active, as are
+% references. Overfull hboxes make ugly black blobs in
+% the margin. Use this mode to tidy up formatting after
+% you're done writing. (Same as article's ``draft'' mode.)
+%
+% final - As proof, but the ugly black blobs are turned off. Use
+% this to render PDFs or PostScript to give to other people,
+% when you're completely done. (As with article, this is the
+% default.)
+%
+% You can also use the leqno, fleqn, or openbib options to article.cls
+% if you wish. None of article's other options will work.
+
+%%%
+%%% PLEASE CHANGE 'galley' to 'final' BEFORE SUBMITTING. THANKS!
+%%% (to submit: "make clean" in the toplevel directory; tar and gzip *only* your directory;
+%%% email the gzipped tarball to papers@linuxsymposium.org.)
+%%%
+\documentclass[galley]{ols}
+
+% These two packages allow easy handling of urls and identifiers per the example paper.
+\usepackage{url}
+\usepackage{zrl}
+
+% The following package is not required, but is a handy way to put PDF and EPS graphics
+% into your paper using the \includegraphics command.
+\ifpdf
+\usepackage[pdftex]{graphicx}
+\else
+\usepackage{graphicx}
+\fi
+
+
+% Here in the preamble, you may load additional packages, or
+% define whatever macros you like, with the following exceptions:
+%
+% - Do not mess with the page layout, either by hand or with packages
+% (e.g., typearea, geometry).
+% - Do not change the principal fonts, either by hand or with packages.
+% - Do not use \pagestyle, or load any page header-related packages.
+% - Do not redefine any commands having to do with article titles.
+% - If you are using something that is not part of the standard
+% tetex-2 distribution, please make a note of whether it's on CTAN,
+% or include a copy with your submission.
+%
+
+\begin{document}
+
+% Mandatory: article title specification.
+% Do not put line breaks or other clever formatting in \title or
+% \shortauthor; these are moving arguments.
+
+\title{Linux Virtualization on Virtual Iron VFe}
+\subtitle{ } % Subtitle is optional.
+\date{} % You can put a fixed date in if you wish,
+ % allow LaTeX to use the date of typesetting,
+ % or use \date{} to have no date at all.
+ % Whatever you do, there will not be a date
+ % shown in the proceedings.
+
+\shortauthor{Alex Vasilevsky} % Just you and your coauthors' names.
+% for example, \shortauthor{A.N.\ Author and A.\ Nother}
+% or perchance \shortauthor{Smith, Jones, Black, White, Gray, \& Greene}
+
+\author{% Authors, affiliations, and email addresses go here, like this:
+Alex Vasilevsky \\
+{\itshape Your affiliation}\\
+{\ttfamily\normalsize your-address@example.com}\\
+% \and
+% Bob \\
+% {\itshape Bob's affiliation.}\\
+% {\ttfamily\normalsize bob@example.com}\\
+} % end author section
+
+\maketitle
+
+\begin{abstract}
+% Article abstract goes here.
+\input{vasilevsky-abstract.tex}
+\end{abstract}
+
+% Body of your article goes here. You are mostly unrestricted in what
+% LaTeX features you can use; however, the following will not work:
+% \thispagestyle
+% \marginpar
+% table of contents
+% list of figures / tables
+% glossaries
+% indices
+
+\end{document}
+
personal git repositories of Harald Welte. Your mileage may vary