Single system image
In distributed computing, a single system image (SSI) cluster is a cluster of machines that appears to be one single system. The concept is often considered synonymous with that of a distributed operating system, but a single image may be presented for more limited purposes, just job scheduling for instance, which may be achieved by means of an additional layer of software over conventional operating system images running on each node. The interest in SSI clusters is based on the perception that they may be simpler to use and administer than more specialized clusters.
Different SSI systems may provide a more or less complete illusion of a single system.
Features of SSI clustering systems
Different SSI systems may, depending on their intended usage, provide some subset of these features.
Many SSI systems provide process migration. Processes may start on one node and be moved to another node, possibly for resource balancing or administrative reasons.[note 1] As processes are moved from one node to another, other associated resources (for example IPC resources) may be moved with them.
Some SSI systems allow checkpointing of running processes, allowing their current state to be saved and reloaded at a later date.[note 2] Checkpointing can be seen as related to migration, as migrating a process from one node to another can be implemented by first checkpointing the process, then restarting it on another node. Alternatively checkpointing can be considered as migration to disk.
Single process space
Some SSI systems provide the illusion that all processes are running on the same machine - the process management tools (e.g. "ps", "kill" on Unix like systems) operate on all processes in the cluster.
Most SSI systems provide a single view of the file system. This may be achieved by a simple NFS server, shared disk devices or even file replication.
The advantage of a single root view is that processes may be run on any available node and access needed files with no special precautions. If the cluster implements process migration a single root view enables direct accesses to the files from the node where the process is currently running.
Some SSI systems provide a way of "breaking the illusion", having some node-specific files even in a single root. HP TruCluster provides a "context dependent symbolic link" (CDSL) which points to different files depending on the node that accesses it. HP VMScluster provides a search list logical name with node specific files occluding cluster shared files where necessary. This capability may be necessary to deal with heterogeneous clusters, where not all nodes have the same configuration. In more complex configurations such as multiple nodes of multiple architectures over multiple sites, several local disks may combine to form the logical single root.
Single I/O space
Some SSI systems allow all nodes to access the I/O devices (e.g. tapes, disks, serial lines and so on) of other nodes. There may be some restrictions on the kinds of accesses allowed (For example, OpenSSI can't mount disk devices from one node on another node).
Single IPC space
Some SSI systems allow processes on different nodes to communicate using inter-process communications mechanisms as if they were running on the same machine. On some SSI systems this can even include shared memory (can be emulated with Software Distributed shared memory).
In most cases inter-node IPC will be slower than IPC on the same machine, possibly drastically slower for shared memory. Some SSI clusters include special hardware to reduce this slowdown.
Cluster IP address
Some SSI systems provide a "cluster address", a single address visible from outside the cluster that can be used to contact the cluster as if it were one machine. This can be used for load balancing inbound calls to the cluster, directing them to lightly loaded nodes, or for redundancy, moving the cluster address from one machine to another as nodes join or leave the cluster.[note 3]
Some example clustering systems
Examples here vary from commercial platforms with scaling capabilities, to packages/frameworks for creating distributed systems, as well as those that actually implement a single system image.
|Name||Process migration||Process checkpoint||Single process space||Single root||Single I/O space||Single IPC space||Cluster IP address[t 1]||Source Model||Latest release date[t 2]||Supported OS|
|Amoeba[t 3]||Yes||Yes||Yes||Yes||Unknown||Yes||Unknown||Open||July 30, 1996||Native|
|AIX TCF||Unknown||Unknown||Unknown||Yes||Unknown||Unknown||Unknown||Closed||March 30, 1990||AIX PS/2 1.2|
|Inferno||No||No||No||Yes||Yes||Yes||Unknown||Open||March 4, 2015||Native, Windows, Irix, Linux, OS X, FreeBSD, Solaris, Plan 9|
|Kerrighed||Yes||Yes||Yes||Yes||Unknown||Yes||Unknown||Open||June 14, 2010||Linux 2.6.30|
|LinuxPMI[t 4]||Yes||Yes||No||Yes||No||No||Unknown||Open||June 18, 2006||Linux 2.6.17|
|LOCUS[t 5]||Yes||Unknown||Yes||Yes||Yes||Yes[t 6]||Unknown||Closed||1988||Native|
|MOSIX||Yes||Yes||No||Yes||No||No||Unknown||Closed||May 16, 2016||Linux|
|openMosix[t 7]||Yes||Yes||No||Yes||No||No||Unknown||Open||December 10, 2004||Linux 2.4.26|
|Open-Sharedroot[t 8]||No||No||No||Yes||No||No||Yes||Open||September 1, 2011||Linux|
|OpenSSI||Yes||No||Yes||Yes||Yes||Yes||Yes||Open||February 18, 2010||Linux 2.6.10 (Debian, Fedora)|
|Plan 9||No||No||No||Yes||Yes||Yes||Yes||Open||January 9, 2015||Native|
|TruCluster||No||Unknown||No||Yes||No||No||Yes||Closed||October 1, 2010||Tru64|
|VMScluster||No||No||Yes||Yes||Yes||Yes||Yes||Closed||September 23, 2016||OpenVMS|
|z/VM||No||Yes||No||No||No||No||Unknown||Closed||February 16, 2016||Native|
|UnixWare NonStop Clusters[t 9]||Yes||No||Yes||Yes||Yes||Yes||Yes||Closed||June 2000||UnixWare|
- Many of the Linux based SSI clusters can use the Linux Virtual Server to implement a single cluster IP address
- Green means software is actively developed
- Amoeba development is carried forward by Dr. Stefan Bosse at BSS Lab
- LinuxPMI is a successor to openMosix
- LOCUS was used to create IBM AIX TCF
- LOCUS used named pipes for IPC
- openMosix was a fork of MOSIX
- Open-Sharedroot is a shared root Cluster from ATIX
- UnixWare NonStop Clusters was a base for OpenSSI
- Computer clusters
- Diskless Shared Root Cluster
- Distributed lock manager
- Distributed cache
- Parallel Virtual Machine - multiple system image alternative
- Message Passing Interface - multiple system image alternative
- ScaleMP - software implementation of cache only memory architecture
- for example it may be necessary to move long running processes off a node that is to be closed down for maintenance
- Checkpointing is particularly useful in clusters used for high-performance computing, avoiding lost work in case of a cluster or node restart.
- "leaving a cluster" is often a euphemism for crashing
- Pfister, Gregory F. (1998), In search of clusters, Upper Saddle River, NJ: Prentice Hall PTR, ISBN 978-0-13-899709-0, OCLC 38300954
- Buyya, Rajkumar; Cortes, Toni; Jin, Hai (2001), "Single System Image" (PDF), International Journal of High Performance Computing Applications, 15 (2): 124, doi:10.1177/109434200101500205
- Coulouris, George F; Dollimore, Jean; Kindberg, Tim (2005), Distributed systems: concepts and design, Addison Wesley, p. 223, ISBN 978-0-321-26354-4
- Bolosky, William J.; Draves, Richard P.; Fitzgerald, Robert P.; Fraser, Christopher W.; Jones, Michael B.; Knoblock, Todd B.; Rashid, Rick (1997-05-05), "Operating System Directions for the Next Millennium", 6th Workshop on Hot Topics in Operating Systems (HotOS-VI), Cape Cod, MA, p. 106, CiteSeerX , doi:10.1109/HOTOS.1997.595191
- Prabhu, C.S.R. (2009), Grid And Cluster Computing, Phi Learning, p. 256, ISBN 978-81-203-3428-1
- Smith, Jonathan M. (1988), "A survey of process migration mechanisms" (PDF), ACM SIGOPS Operating Systems Review, 22: 28, doi:10.1145/47671.47673
- "AIX PS/2 OS".
- "Open-Sharedroot GitHub repository".
- Pike, Rob; Presotto, Dave; Thompson, Ken; Trickey, Howard (1990), "Plan 9 from Bell Labs", In Proceedings of the Summer 1990 UKUUG Conference, p. 8,
Process migration is also deliberately absent from Plan 9.Missing or empty