Linux on POWER (LoP) was introduced in 2005 with the introduction of Advanced Power Virtualization (APV) and IBM System p5®. Its introduction allowed users of the IBM System p® architecture to install Linux natively on top of IBM's logical partitioning (LPAR) technology. In doing so, it provided the ability to use virtualization features on System p, similar to IBM's brand of UNIX®: AIX®. These features included micro-partitioning, Virtual IO Servers (VIOS) and supported advanced-level features, such as Capacity on Demand (CoD). It even is supported by newer innovations on the Power6, such as Live Partition Mobility, which allows workloads to be dynamically moved from one System p server to another with no downtime; and shared dedicated capacity, which optimizes the use of spare processor cycles.
Users of LoP should be aware of an innovation brought in by PowerVM™. Formerly referred to as System p AVE, it has since been renamed PowerVM Lx86. PowerVM Lx86 supports the installation and running of most 32-bit x86 Linux applications on any System p or BladeCenter® model with POWER6™, POWER5+™, or POWER5™ processors, without a native installation of the application. It works by creating an x86 Linux application environment running on POWER™ processor-based systems by dynamically translating x86 instructions to Power Architecture® instructions and caching them to enhance performance. It also maps x86 Linux system calls to LoP system calls. What is unique about this solution is that no native porting or application upgrade is required for running most x86 Linux applications. This is supported by both SLES and RHEL.
But aren't both Red Hat's and Novell's distributions supported on IBM System p? The short answer is yes. But there are some fundamental differences you should be aware of. As a project manager involved in a multimillion-dollar project moving from one Linux distribution to another, I can attest to the importance of this decision. Some of these factors include how important a GUI is to you, what kind of support you can expect to receive from your distribution vendors, and the respective market share of each. To assist with your decision, you'll see what's involved in managing volume groups and allocating physical volumes to your logical environments.
SUSE was founded in 1992 as a UNIX Consulting Group. The first real Linux distribution was released in 1996. SLES is based on SUSE's Linux and was released in October 2000. Interestingly enough, it was first released as a version for the IBM mainframe. The x86 version of SLES was released in April 2001. Novell acquired SUSE in January 2004, SLES V9 was released in August 2004, and SLES V10 was released in February 2006.
What is it about SUSE that sets it apart? In my view, it starts with Yet another Setup
Tool (YaST or YaST2) . YaST is similar to AIX, and it can pretty much perform
any systems administration task. Let's work with logical volumes, which will allow you
to work with physical devices and file systems, as well. First, we'll call up the GUI using the
# yast. This calls up
the YaST Control Center shown below.
Figure 1. YaST Control Center
Next, you need to choose LVM. You can add a volume group or add logical volumes. In this case, you will add a volume group since we don't have one defined at the moment.
Figure 2. LVM configuration
The volume group you are adding is oravg. You'll also allocate physical device /dev/sdb to this volume group.
Figure 3. Allocating physical device /dev/sddb to the volume group
When that is completed, you'll see the physical volume size increase; in our case, it increases to 19.9 GB. Now we're ready to add the logical volume. Choose Add.
Figure 4. Adding the logical volume
In Figure 5, you'll input the name of the logical volume, oralv, and request a size of 4.9 GB. You'll also add the mount point, /ora01, which also creates the file system.
Figure 5. Inputting the name of the logical volume
Figure 6 shows that the volume was created successfully.
Figure 6. The volume was created successfully
The command line verifies that the volume was created successfully.
Figure 7. Command-line verification
In this section, we'll discuss Red Hat's distribution on IBM System p. Red Hat offers support on IBM System p, starting with RHEL4, but RHEL5 is also supported. So without IBM support of the version, functionality, such as PowerVM, IBM's virtualization engine will just not work.
Red Hat V1 was released in November 1994 and was actually the first Linux to use the RPM Package Manager. RHEL was introduced in 2003, with the last of the Red Hat Linux versions, V9, released in April 2004. Unquestionably, Red Hat has been the Linux market leader through the years, particularly for big business.
What you won't find with RHEL is an integrated GUI-like YaST2, from which you can
launch any command your heart desires. With Red Hat, you have GUIs, but you need to
remember the names of the commands that launch them; there is not one command from
which it all flows as there is with SLES. To add logical volumes, you'll use the
system-config-lvm command. The first thing you need to do prior to setting up our
volume group is initialize your unpartitioned space (see Figure 8), which, here, is 20 GB:
Figure 8. Initializing your unpartitioned space
After you initialize, choose Create new Volume Group to create a new volume group.
Figure 9. Create new Volume Group
In this case, you'll call the volume group
oraclevg and allocate 256 4-MG extents. Click OK when the action is completed.
Figure 10. Naming the volume group
At this point, click on Logical view to create a logical volume.
Figure 11. Clicking on Logical view
Now let's create the LVM. Click on Create New Logical Volume.
Figure 12. Create New Logical Volume
We'll call our LV
oralv and allocate 1,000 extents. We'll also call the file system
/ora01 and make it an ext3 file system.
Figure 13. Naming the logical volume
Figure 14 shows the logical volume, physical volume, file system, and volume group.
Figure 14. Logical volume, physical volume, file system, and volume group
Before we compare and contrast the two distributions, make sure you download the required software that will enable you to access the full capabilities of your operating system, including the ability to enable dynamic logical partitioning on your Linux partition. See Resources for a complete list of SLES packages you should download for System p servers that are not managed by a Hardware Management Console (HMC). These packages are provided from IBM in RPM format. After installing these, the dynamic reconfiguration of CPU and hot-pluggable PCI adapters can also be performed without having to reboot Linux.
One important innovation exclusive to Novell is its integrated stack for SUSE Linux Enterprise, first made available on IBM System p5® and BladeCenter JS21. This consists of the IBM WebSphere® Application Aerver, IBM DB2®, SLES10, and Centeris Likewise Management. This management tool allows you to manage a network of Linux and Windows servers. The stack is bundled on one DVD and available from all Novell business partners. This product is an end-to-end Web-enabled environment, which is as powerful as it is integrated. This is intended for clients with custom Web-based or Java applications who are looking to modernize their infrastructures with a mix of supported and open source applications. It is also fully supported by IBM's midrange virtualization product: IBM's PowerVM. On the RHEL side, Red Hat has its own application stack. This stack is an integrated version of RHEL4 that includes JBoss and Apache. The RHEL stack, however, does not have the same level of System p support the SLES stack does.
Additionally, Novell's market share climbed from approximately 13 percent in last year's survey to roughly 17 percent in the current poll (see Resources). SLES also boasts some impressive benchmarks. Recent SPECfp_2006 benchmarks on one of its most popular high-end midrange servers, the IBM System p570, powered by the new POWER6™ chip (4.7 GHz) and running SUSE Linux, scored 22.4. This is the highest result in the industry — approximately 23 percent better than an HP Integrity rx6600 running HP-UX.
What about RHEL? Red Hat owns the market share for Linux and has for many years, which is something to consider. I have a preference for some of the RHEL GUI tools over YaST — in particular, the one we looked at in this article — to configure logical volumes. The GUI is easy on the eyes and intuitive.
As someone who has used both SLES and RHEL, I'm not prepared to say I prefer one over the other on IBM System p. They both have great support and are top performers. It's important to note that both Red Hat and Novell service and support the LoP configurations. Make sure you visit IBM's LoP Service and Productivity Tools Support Forum (see Resources), where you can collaborate with others using these systems.
In this article, we looked at the top Linux distributions on IBM System p: RHEL and SLES. The history of Linux on POWER (LoP) and the histories of the leading distributions were also detailed. You've seen firsthand how to set up the logical volumes on each distribution. In doing so, you used the GUI of each distribution to perform some configurations.
RHEL or SLES? The bottom line is you can't go wrong with either.
Read the 2008 Server OS
Reliability Survey from the Institute of Advanced Professional Studies.
with coLinux": Read an article that introduces virtualization and then looks at the approach taken by Cooperative Linux (coLinux).
New to AIX and
UNIX?: Visit "New to AIX and UNIX" to learn more.
AIX Wiki: A
collaborative environment for technical information related to AIX.
AIX 5L performance: Tuning network performance, Part 1": Read Part 1 of a three-part
series on AIX networking, which focuses on the challenges of optimizing network performance.
For a three-part series on memory tuning on AIX, see "Optimizing
AIX 5L performance: Tuning your memory settings , Part 1."
Read the IBM whitepaper "Improving
Database Performance with AIX concurrent I/O."
Learn about AIX
memory affinity support from the IBM System p and AIX InfoCenter.
Learn about IBM's Power
Architecture: High-Performance Architecture with a History.
Read "Power to the
People: A history of chip making at IBM" for coverage of IBM's Power Architecture.
Monitoring and Tuning" to learn how standard AIX tools can help you determine CPU bottlenecks.
For a comprehensive guide about the performance monitoring and tuning tools that are
provided with AIX 5L V5.3, see the IBM Redbooks titled "AIX 5L
Practical Performance Tools and Tuning Guide."
Learn what features you can benefit from in AIX 5L V5.3 in "AIX 5L Version 5.3:
What's in it for you?"
System and Device Management provides users and systems administrators with complete
information that can affect your selection of options when performing such tasks as
backing up and restoring the system, managing physical and logical storage, and sizing appropriate paging space.
"The AIX 5L Differences
Guide Version 5.3 Edition" focuses on the differences introduced in AIX 5L V5.3 when
compared to AIX 5L V5.2.
The AIX and UNIX developerWorks zone
provides a wealth of information relating to all aspects of AIX systems administration.
Visit the developerWorks Open source zone for extensive
how-to information, tools, and project updates to help you develop with open source technologies and use them with IBM products.
Stay current with developerWorks
technical events and webcasts.
Podcasts: Tune in and catch up with IBM technical experts.
Get products and technologies
- Participate in the discussion forum.
- Participate in the discussion forums:
- Linux on Power Service and Productivity Tools Support Forum
- AIX Forum
- AIX Forum for developers
- Cluster Systems Management
- IBM Support Assistant Forum
- Performance Tools Forum
- Virtualization Forum
- More AIX and UNIX Forums
- AIX Networking
Ken Milberg is a technology writer and site expert for Techtarget.com and provides Linux technical information and support at Searchopensource.com. He is also a writer and technical editor for IBM Systems Magazine, Power Systems edition, and a frequent contributor of content for IBM developerWorks. He holds a bachelor's degree in computer and information science, as well as a master's degree in technology management from the University of Maryland University College. He is the founder and group leader of the N.Y. Metro POWER-AIX/Linux Users Group. Through the years, he has worked for both large and small organizations and has held diverse positions from CIO to senior AIX engineer. He is currently president and managing consultant for UNIX-Linux Solutions, is a PMI-certified Project Management Professional (PMP), an IBM Certified Advanced Technical Expert (CATE), and is also IBM SCon certified.