|
Red Hat and Platform Computing Partner for Supercomputing
Published: November 27, 2007
by Timothy Prickett Morgan
Platform Computing, one of the pioneers of grid computing for supercomputing environments, and Red Hat, a pioneer in commercially supported Linux distributions and the revenue and market share leader for commercial Linux for a decade, have teamed up to bundle and promote their respective products among the high performance computing centers of the world. Red Hat and Platform Computing have been working together since the latter company rolled together a bunch of open source tools into an integrated stack back in July 2006, called the Open Cluster Stack.
Back then, Platform's OCS product was launched on Dell servers and certified to run on Red Hat Enterprise Linux or its CentOS clone on X86 and X64 servers. The stack included development tools and utilities, file systems, system management, workload management, and resource management tools for both the server and cluster layers of supercomputer clusters. The heart of the OCS product is an open source cluster management project called Rocks, which was created by the San Diego Supercomputing Center and owned and administered by the University of California at San Diego. Platform has also created an open source cluster workload management tool called Lava, which is central to the OCS product and which provides some of the functionality of Load Service Facility, Platform's original (and closed source) grid computing product. LSF can plug into the OCS framework, as can popular open source tools such as Ganglia (which monitors workloads on nodes and clusters), CluMon (which is a system admin dashboard for monitoring grids), MatTool (for managing disks and DNS servers), the Nagios server management tool, and about a dozen other snap-ins, including the IBRIX parallel file system, the MySQL datasebase, the Volcano Web portal, and Intel's compilers.
The Platform stack is also going to be enhanced--either directly or indirectly--by the company's recent acquisition of Scali, another pioneer in the grid computing area that has created a sophisticated set of system management tools called Scali Manage for Linux clusters. Scali Manage is a souped-up version of the open source Beowulf clustering that put Linux on the map a decade ago in the supercomputer centers of the world. Platform announced its intent to acquire key assets of Scali at the end of October for an undisclosed amount; the company bought the key software assets behind the Scali Manage product and retained the key development and support personnel as well. Platform says that it expects to integrate Scali Manage with its LSF product by the second quarter of 2008, and it is possible that Scali Manage could be taken open source (but not probable). It seems far more likely that the OCS product will integrate with Scali Manage, much as LSF does. Ethernet, Gigabit Ethernet, InfiniBand, and Myrinet interconnects are supported by OCS.
In any event, the resulting bundle of the two companies' products will be called the Red Hat HPC Solution, integrating OCS with Enterprise Linux 5. Red Hat will be providing 24x7 technical support for the HPC variant, and is presumably kicking some of the money it receives from support contracts to Platform. Red Hat and Platform say that the HPC stack has been certified on a range of hardware platforms and will be available by the end of this year.
Commercial Linux distributor Novell has been a partner of Platform's since 2005, and has a pretty good foothold in the HPC space compared to Red Hat. Both Cray and Silicon Graphics have modified versions of SUSE Linux Enterprise Server 10 on their monster cluster machines, and do not offer Red Hat Enterprise Linux. Platform has chosen Red Hat, and vice versa, to try to take on Novell and its partners in the HPC space. It will be interesting to see if there is a SLES HPC stack in the works. Hard to imagine there isn't, and ditto for Ubuntu and maybe Mandriva Linux as well.
Platform is charging $150 per node per year for supporting OCS, which does not include Linux support. Red Hat has not talked about pricing for the HPC bundle, but considering the price sensitivity and stinginess of the world's supercomputer centers--which generally have nerds who know as much about Linux as the commercial distributors--there is no way that Red Hat can charge as much for RHEL 5 for these customers as it can for general commercial customers. Historically, those supercomputer centers that wanted to pay for commercial support bought workstation licenses and put the software on their server nodes, and then turned off all but the most necessary services to boost the efficiency of the Linux running on the nodes. Red Hat is charging $299 for a standard subscription to RHEL Desktop 5, which offers 12x5 business support; a standard subscription for RHEL 5 on a two-socket server costs $799. Microsoft is charging $469 per node for a license to Windows Compute Cluster Server 2003 license. It is a fair bet that Red Hat HPC Solution will cost $449, which is just the cost of RHEL 5 support on a workstation plus the cost of Platform's support.
RELATED STORIES
Red Hat Puts Out Fedora 8 Rev of Development Linux
The Low-Down on Red Hat Enterprise Linux 5.1 Enhancements
Red Hat to Use Automation, Virtualization to Eat the Server Space
Red Hat Puts Out Fedora 7 Community Release
Red Hat, IBM Commit to Better Mainframe Linux
RHEL 5: How's It Going?
Red Hat to Push Desktop Linux with Intel Partnership
Red Hat Integrates and Simplifies with RHEL 5
Platform Computing's OCS Extends Clustering with Open Source Tools
Platform Gets EAL Security Certification for Grid Products
Server Makers Push Linux As Linux Pulls Them
Post this story to del.icio.us
Post this story to Digg
Post this story to Slashdot
|
|
Why File-based System Backup is your Best Bet
File-based, Full System Backups Create Advantages Over Image-based Backups
File-based backups used for system recovery have been around for years. And, until recently, file-based meant a long, painstaking, manual process capable of turning off even the most meticulous system administrator. Image-based backups, then, seemed to solve this problem by eliminating the need to deal with recreating partitions, filesystems, volume groups or other details related to the system's storage configuration. In an image-based restore, the storage configuration and data from the original system are restored as a whole to the new system. While this method produced fast recovery times, Linux administrators began to realize disk image backup was more of an alternative method with its own set of problems and limitations than an answer to the challenges of manual, file-based backup.
Limitations to Disk Image Backup
Since disk image backups make no distinction between files and instead backup the hard drive as a group of sectors, bare-metal recovery can be quick and easy by simply rewriting a duplicate image onto a new, identical disk drive. A fine solution, as long as the old system and new system are indeed identical in types, sizes, locations- basically the exact same hardware. Any differences in hardware, however, could render an image backup unusable.
Many system administrators know first-hand the frustration caused by the inflexibility of image-based backup. "What I hear time and time again from clients is that they switched from image-based backup to file-based because of the limitations they encountered when trying to restore a backup onto different hardware." said Manuel Altamirano, Storix Software Director of Sales and Marketing. "Administrators assume they will have access to identical hardware after a disaster or for migration when the time comes. Unfortunately, so often this is not the case. Companies are left with unplanned, excessive downtime."
Even more advanced disk image backup products, that offer alterations to disk partition tables, still fail to understand more advanced and increasingly common storage configuration tools such as the Logical Volume Manager (LVM) or Software RAID (meta-disks) that also must be altered to match new hard disk configuration before data can be restored. In these cases, users must manually alter and build the configuration, usually through command-line utilities and manual editing of configuration files. This also requires users to have knowledge on how to make a system bootable. Rebuilding a system using a disk image backup requires experienced Linux administrators and could take days, weeks or longer resulting in crippling downtime for an organization.
Advances in File-based Backup
File-based backup tools today can automate the process of recording every aspect of a system separately such as disk, filesystem and boot loader configuration while supporting all popular Linux storage configuration tools (i.e. LVM and Software RAID). This detailed backup information is used to greatly simplify the recovery of a failed system from scratch, even if hardware differences are detected on the new system. Furthermore, systems rebuilt from the ground up using file-based backups often times operate better than the original because there is virtually no fragmentation when the restore is completed.
Flexible recovery based on file-based backup
File-based backup products have the ability to reconfigure disks, partitions, filesystems and other storage solutions to fit onto new hardware. This ability to adapt a backup to fit new hardware or alter the system's storage configuration is called "Adaptable System Recovery" or ASR. Only backup solutions that gather details about the original system have enough information and flexibility to make the ASR process of altering configuration so simple even novice Linux administrators can quickly perform the recovery. Once new configuration is completed, data files from the backup are easily restored onto the new hardware. Finally, the system is made bootable based on the new hardware.
The revolutionary adaptability of ASR found in file-based backup tools creates further added value for system administrators because these products can now be used for far more than just reactive tasks such as disaster recovery.
Applications for ASR:
Reactive
- Disaster Recovery- restore systems in minutes after a crash, even if hardware is not the same as the original
Proactive
- Provisioning/cloning- a single backup "golden image" can be used to provision different systems, even if disks, adapters or other elements are not the same.
- Storage software migration- change configuration on the same system for improved performance and availability
- Hardware migration- install the same system onto newer or virtual systems
New system backup management features
Products using file-based system backup have not neglected to consider a system administrator's daily backup responsibilities. These products now incorporate functionality for backup management as well as some of the most advanced features seen in backup and recovery solutions for Linux and AIX. Some advanced features designed to simplify daily backup management for system administrators include:
- Graphical, Web and Command line interfaces
- Local and remote backups to disk or tape devices
- Sequential and random tape autoloader support
- Support for SAN storage solutions
- Tivoli Storage Manager integration
- Oracle database backup support
- Backup data encryption
- Multiple compression levels
File-based Backup Solutions Provide Most Bang for the Buck
Inexpensive products exist that combine both file-based backup management and ASR in one program. Look for a file-based system backup product with advanced features like those mentioned above. In turn, regular backup responsibilities such as automatically verifying backups and encrypting backup data will become much easier. Additionally, combined ASR capabilities greatly reduce downtime and required expertise for both reactive (even bare metal) and proactive recovery projects. File-based system backup and recovery solutions are an economical and more comprehensive option than their image-based counterparts.
About the Author
Anne Stobaugh is an independent contractor working with Storix Software to educate Linux and AIX users on the advantages of file-based backup and recovery solutions.
www.storix.com
www.stobaughmarketing.com
|
Editor: Timothy Prickett Morgan
Contributing Editors: Dan Burger, Joe Hertvik, Kevin Vandever,
Shannon O'Donnell, Victor Rozek, Hesh Wiener, Alex Woodie
Publisher and Advertising Director: Jenny Thomas
Advertising Sales Representative: Kim Reed
|
IT Jungle Store Top Book Picks
The System i Pocket RPG & RPG IV Guide: List Price, $69.95
The iSeries Pocket Database Guide: List Price, $59.00
The iSeries Pocket Developers' Guide: List Price, $59.00
The iSeries Pocket SQL Guide: List Price, $59.00
The iSeries Pocket Query Guide: List Price, $49.00
The iSeries Pocket WebFacing Primer: List Price, $39.00
Migrating to WebSphere Express for iSeries: List Price, $49.00
iSeries Express Web Implementer's Guide: List Price, $59.00
Getting Started with WebSphere Development Studio for iSeries: List Price, $79.95
Getting Started With WebSphere Development Studio Client for iSeries: List Price, $89.00
Getting Started with WebSphere Express for iSeries: List Price, $49.00
WebFacing Application Design and Development Guide: List Price, $55.00
Can the AS/400 Survive IBM?: List Price, $49.00
The All-Everything Machine: List Price, $29.95
Chip Wars: List Price, $29.95
|
|
November 24, 2007: Volume 9, Number 46
November 17, 2007: Volume 9, Number 45
November 10, 2007: Volume 9, Number 45
November 3, 2007: Volume 9, Number 44
October 27, 2007: Volume 9, Number 43
October 20, 2007: Volume 9, Number 42
|
|
|
|