changeset 2:2e15cb64202d

Cleanup, and basic structure
author Josef "Jeff" Sipek <>
date Fri, 26 Aug 2005 17:41:28 -0500
parents d7c6a14e17c8
children 7f424d95e939
files slideshow.tex
diffstat 1 files changed, 34 insertions(+), 188 deletions(-) [+]
line wrap: on
line diff
--- a/slideshow.tex	Fri Aug 26 17:18:37 2005 -0500
+++ b/slideshow.tex	Fri Aug 26 17:41:28 2005 -0500
@@ -2,213 +2,59 @@
-\title{Linux Clustering}
-  {\bf Q}: What is better than a PC running Linux?\\
-  {\bf A}: More than one PC running Linux, clustered together!}
+\title{Source Code Management /\\ 	Version Control Systems}
+\subtitle{Everything you would ever want to know}
 \author{Josef ``Jeff'' Sipek}
-% What the..?
-\begin{slide}{Wait a second...}
-% What is this "cluster"?
-What are you talking about?!
-% Collection of similar items
-% We are talking about computers
-Collection of computers
-% In a cluster, each computer is called a node
-Collection of nodes
-% We like Linux
-Collection of nodes running Linux
-% hence the subtitle
+% What is it?
+\begin{slide}{What's SCM/VCS?}
+	% like CVS, SVN, HG
-% Types
-\begin{slide}{Types of Clustering}
-There are several types of clusters...
-	\vspace{2em}
-% google's cluster is great example
-	{\bf High availability} - fail over situation
-	\vspace{2em}
-% grid computing, openmosix, etc.
-	{\bf High throughput} - implies high availability, loosly coupled
-	\vspace{2em}
-% beowulf
-%   - dedicated lan
-	{\bf High performance} - tightly coupled, very faaaaast
-	\hspace{3em}{\bf This is the cool stuff!}
+% What is it good for?
+\begin{slide}{What is it good for?}
-\begin{slide}{NonUniform Memory Access}
-% Altix 3000 uses special hardware to connect the nodes into one "computer." 
-If you have quite a bit of money to spend, you might want to consider one of these with:
-% yes, that's GigaBytes
-\item 6.4 GB/s interconnect
-% quite a bit of memory
-\item 4GB - 8TB of RAM
-% what good is hardware, when there is no software? 
-\item Linux
-% you need at least 4 zeros in the pricetag, more likely to have 5
-\item Damn expensive!
-% Beowulf
-% Are you too poor to spend quarter million on a computer? Don't worry!
-If you don't have that much money, try Beowulf cluster type.
-% you can use hardware you have already at home! (point out the NYC court computers)
-\item Use any old hardware
-% Ok, maybe you think that you should spend some money
-\item Use any new hardware
-% And here we go again, need software? Get Linux!
-\item Linux
+% What can it do?
+\begin{slide}{What can it do?}
-% MPI
-\begin{slide}{Message Passing Interface aka. MPI}
-% MPI is an standard
-\item A standard
-% MPI was designed for high performance on both massively parallel machines and on workstation clusters.
-\item Designed for high performance
-%  MPI is widely available, with both free available and vendor-supplied implementations. A number of MPI home pages are available.
-\item Widely available
-% for what it's worth, MPI has 130 functions
-\item 130 function
-% PVM
-\begin{slide}{Parallel Virtual Machine aka. PVM}
-% I won't have enough time to talk and demo PVM...oh well
-% PVM does a similar thing as MPI, but a little differently
-% I don't have much to say about it except that it has 38 functions, and works well for many people. RTFM
-\item 38 functions
-% OM
-% openMosix is a kernel extension for SSI clustering.
-\item Single System Image clustering
-% spawn a process anywhere, and it will migrate to the best node available => load balancing
-\item Automatic process migration
-\item Easy to set up
-% not in my opionion
+% There are different models
+\begin{slide}{More than one way to skin a cat}
+	\begin{itemstep}
+		\item Centalized
+		\item Distributed
+	\end{itemstep}
-% distcc
-% HW: uncluterring of cables
-\begin{slide}{What a mess!}
-% Now that you have spend thousands of dollars on computers and miles of cables, what can you do to make it neater?
-What am I supposed to do?
-% you won't like this, but it works
-\item Don't look
-% organize the cables, have networking cables run in "channels"
-\item Organize
-% you might want to write everything down, since a cluster can get large and you usually set it up and leave it alone for a looong time
-\item Document
+	\begin{itemstep}	
+		\item CVS and Subversion
+		\item Central server
+		\item Clients checking code in/out
+	\end{itemstep}
-There are MANY HowTos, and manuals about clustering...Read!
-% Let's get dirty
-\begin{slide}{Let's get dirty..}
-% Debian is a good choice, this is very simple
-\item Install Linux
-% really any DNS server will do, but bind is know to be good
-\item Install bind9
-% DHCP gives the disk-less-nodes IPs and info on how to boot
-\item Install dhcpd
-% tftp gives the nodes a way to get a copy of the kernel
-\item Install tftpd
-% mknbi (debian) allows you to create the etherboot kernel images
-\item Install mknbi
-% NFS for root on NFS
-\item Install NFS
-% you need to create a root structure for each node
-\item Make / for nodes
-% if you don't have a network bootable box, make an etherboot floppy/cd
-\item Make boot floppy (optional)
+\begin{slide}{Centralized (cont'd.)}
+	% FIXME: animation of what happens
+	%  - server, client
+	%  - client checks out a copy
+	%  - client modifies code
+	%  - client commits changes to server
-\begin{slide}{Installing Linux}
-\begin{slide}{Installing Bind9, dhcpd, etc...}
-This takes some effort, but is outside the scope of this talk, except...
-\item Set nfs-root in dhcpd.conf
-% FIXME: use "clusterfobia"