7.4 What is logical partitioning?

Once VM was generally available in 1972, some companies used it to partition machines in order to run different workloads in different partitions. It turned out that for some companies, a simpler partitioning scheme would be just as useful. As a result, some fundamental virtualization concepts were included into the architecture. These concepts became the hardware hypervisor Processor Resource/Systems Manager (PR/SM) and the logical partitions (LPARs) into which PR/SM could divide a machine. A zSeries 900 or 800 mainframe can run in one of two modes: basic mode or LPAR mode. In basic mode, the entire machine is under the control of a single operating system. In LPAR mode, you can logically divide the machine into partitions so that multiple operating systems can run concurrently.

LPAR partitioning helps companies to exploit the resources of the machine better than if there were no partitioning. LPAR allows companies to have a single machine support both production and test requirements. Initially, companies would bring up the test partition only at off-peak times.

The PR/SM hypervisor of the zSeries 900 can manage up to 15 LPAR "guests." The CPU and channel paths are the two resources that can be logically shared. Central storage must be physically partitioned and assigned to each active partition.

Although the virtualization technology that is best known in the context of Linux on the mainframe is z/VM, there are some occasions where you might consider using an LPAR:

  • You might want to take advantage of the cost savings available with Integrated Facility for Linux (IFL). The IFL feature CPUs can be assigned only within an LPAR that is dedicated to Linux, or Linux running on z/VM (see 21.4, "Integrated Facility for Linux (IFL)").

  • You might want to have just a few Linux images. Then you might not require the ability of z/VM to handle hundreds of images.

  • You might require the certified security offered by LPAR. Typically, you might want to run a few Linux images each in their own LPAR (Figure 7-2). An independent authority has certified LPAR to confirm that LPARs are isolated from one another (see 23.1.1, "LPAR certification"). Depending on your corporate audit policy, a firewall might be an instance where you want an individual Linux in its own LPAR.

    Figure 7-2. Two LPARs, one running z/OS, the other running Linux


Companies can utilize their mainframe with more flexibility using LPARs than using native mode. However, LPAR provides far less flexibility and function than what is available with z/VM.

Linux on the Mainframe
Linux on the Mainframe
ISBN: 0131014153
EAN: 2147483647
Year: 2005
Pages: 199

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net