Warning: Can't synchronize with the repository (/nfs/projects/capforge.org/trac/cap does not appear to be a Subversion repository.). Look in the Trac log for more information.

Comparisons

xcat compared to cap

CAP 4.0

current OS/Distribution support Cap 4.0 is distrubited by a RPM for RHEL4
current OS/Distribution support Cap 4.0 can be utilzied by a tar ball for any Linux type system
future OS/Distribution support Cap 4.0 will be distrubited via a debian package
current Hardware Control Remote Power control (on/off/status) via iLO or IPMI
current Hardware Control Remote OS console via iLO, IPMI or various terminal servers
current Boot Control pxe network, diskless, or local
current Automated installation Parallel install via scripted RedHat? kickstart on ia32 and ia64
current Automated installation Network installation with supported PXE NICs or via etherboot on supported NICs without PXE
current Administration Utilities Parallel distrubibted remote shell, rsync, and scp
current Configuration Administrator Speconf, intelligently synchronize a speconf directory
current Usability Command line utilities for all cluster management functions
current Usability Single operations can be applied in parallel to multiple nodes with a very flexible and customizable group/range functionality
current Flexibility Support for various user defined node types

2.3 Understanding xCAT's Features

Status Feature Type Feature
current OS/Distribution support RedHat? 6.2, 7.0, 7.1, 7.2, 7.3, and 8.0-beta on management and compute / storage / interactive | head nodes
current OS/Distribution support RedHat? for ia64 on management and compute / storage / interactive | head nodes
current OS/Distribution support Any OS on compute nodes via OS agnostic imaging support
current Hardware Control Remote Power control (on/off/state) via IBM Management Processor Network and/or APC Master Switch
current Hardware Control Remote software reset (Ctrl+Alt+Del)
current Hardware Control Remote Network BIOS/firmware update and configuration on a lot of IBM hardware
current Hardware Control Remote OS console via pluggable support for a number of different terminal servers
current Hardware Control Remote POST/BIOS console via IBM Management Processor Network and via terminal servers in upcoming IBM BIOS releases.
current Boot Control Ability to remotely change boot type (network or local disk) with syslinux
current Automated installation Parallel install via scripted RedHat? kickstart on ia32 and ia64
current Automated installation Parallel install via imaging with other Linux distributions, Widows, or other OSes
current Automated installation Network installation with supported PXE NICs or via etherboot on supported NICs without PXE
current Monitoring Hardware alerts and email notification with IBM's Management Processor Network and SNMP alerts
current Monitoring Remote vitals (fan speed/temp/etc...) with IBM's Management Processor Network
future Monitoring Configurable and extensible monitoring support via mon
future Monitoring Graphical look at cluster status via ganglia.
current Monitoring Remote hardware event logs with IBM's Management Processor Network
current Administration Utilities Parallel remote shell, ping, rsync, and copy
current Administration Utilities Remote hardware inventory with IBM's Management Processor Network
current Software Stack PBS and Maui schedulers - Build scripts, documentation, automated setup, extra related utilities, and deep integration
current Software Stack Myrinet - automated setup and installation
current Software Stack MPI - Build scripts, documentation, automated setup for MPICH, MPICH-GM, and LAM
future Software Stack SGridEngine scheduler supprt
current Usability Command line utilities for all cluster management functions
current Usability Single operations can be applied in parallel to multiple nodes with a very flexible and customizable group/range functionality
current Flexibility Support for various user defined node types