HP-UX Virtual Partitions
Marty Poniatowski, William F. Evans · CERN Document Server (European Organization for Nuclear Research) · 2002
From the Book: PREFACE About Virtual Partitions With Virtual Partitions (vPars) you can take almost any HP 9000 server and turn it into many computers. These virtual computers can each be running their own instance of HP-UX and associated applications. The virtual computers are isolated from one another at the software level. Software running on one Virtual Partition will not affect software running in any other Virtual Partition. In the Virtual Partitions you can run different revisions of HP-UX, different patch levels of HP-UX, different applications, or any software you want and not affect other par-titions. There are some base requirements that must be met in order to run vPars on your system. At the time of this writing, the following requirements minimum requirements must be met for each vPar on your system: Minimum of one CPU. Sufficient memory to run HP-UX and any other software that will be present in the vPar. A boot disk off of which HP-UX can be booted. At the time of this writing it is not possible to share bus adapters between vPars. Therefore, a separate bus adapter is required for each of the vPars. This requirement may have been removed by the time you read this book. A console for managing the system. The console can be either physical or virtual. We'll cover the console in detail in the book. An HP 9000 system supported by HP-UX 11i. At the time of this writing only HP-UX 11i is supported in vPars. With systems based on Itanium Processor Family (IPF) processors, there are plans to support numerous operating systems in vPars in the future. The system we'll use in most of the exampthroughout this book is an L-Class system that meets all of the requirements in the previous list. You may also want to have additional disks and a separate LAN card in each of your vPars. I strongly recommend the LAN card so that you can establish TELNET, or other, sessions to your vPars rather than connect to them only from the console. The LAN card is also required to perform backup and Ignite-UX related work. If you have Instant Capacity on Demand (iCOD) employed on your server, all CPUs must be activated in order for vPars to work. When employing Processor Sets (psets) in a vPar, use only bound CPUs. There is a vPars product bundled with HP-UX 11i as well as a full, or add-on product. There are very few limitations with the add-on product. The bundled product has a limitation of a maximum of two vPars and one of the vPars can have only one CPU. This book was written with Virtual Partitions software that had not yet been released. There have been many enhancements to Virtual Partitions since the writing of this book. There is a Graphical User Interface being considered for vPars that I haven't covered in this book. There is something to be said for working with a product when it is new. You really get a good understanding of the functionality of the product by using the command line only and performing a lot of manual procedures. In addition, Superdome vPars software in covered in Appendix A had just become available as early access software. The vPars software for Superdome operates identically to that on the L-Class and N-Class systems covered in the earlier examples in the book. Although the Virtual Partitions product has been streamlined since the writing of this book you'll gain a good understanding of Virtual Partitions by the procedures I cover herein. I hope you enjoy reading the book and learning the material as much as I did writing it. Marty Poniatowski [email protected] Virtual Partitions (vPars) Background HP-UX Virtual Partitions (vPars) allow you to run multiple instances of HP-UX on the same HP 9000 server. From a hardware perspective a vPar consists of CPU, memory, and I/O that is a subset of the overall hardware on the computer. From a software perspective a vPar consists of the HP-UX 11i Operating Environment and all application-related software to successfully run your workload. Figure P-1 shows a conceptual diagram of the way in which HP 9000 computer system resources can be allocated to support multiple vPars. The components of which your HP 9000 is comprised can be allocated in a variety of ways. You can see that the eight-way system shown has a different number of processors, different amount of memory, and different number of I/O cards allocated to each vPar. The unused components can be added to any of the vPars or be the basis for yet another vPar. In addition, components can be moved from one vPar to another (with some restrictions described later in the book). Uses of Virtual Partitions I have worked on many vPars installations that have a variety of uses for vPars. The following are a sampling of the reasons to use vPars: Increased System Utilization - Many servers are underutilized. With vPars you can devote a subset of system resources to each vPar. With each vPar running its own instance of HP-UX 11i and ass applications, you'll get higher overall system utilization. Flexibility - Many applications have resource needs that change. With vPars you can devote fewer system components when application needs are low and additional resources when an application needs them. An increased end-of-the-month workload, for instance, can be given more system resources to complete faster. Server Consolidation - Running multiple instances of HP-UX 11i and their associated applications on one HP server reduces the overall number of servers required. Web servers that had run on different servers can now be run in different vPars on the same computer. Application Isolation - HP vPars are fully software-isolated from one another. A software failure in one vPar does not affect other vPars. Mixed Production, Test, and Development - Production and testing can take place on the same server with vPars. When testing is complete, the test vPar can become the production vPar. Similarly, development usually takes place on a separate system. With the software isolation of vPars, however; development can take place on the same sys-tem with other applications. These are just a sampling of the uses I've seen for vPars. Many others will emerge as vPars become widely used and systems experts implement them in more computing environments. Organization of the Book I did not restrict this book to covering only Virtual Partitions (vPars) related material. I cover many HP-UX 11i system administration topics and the way in which they are affected by vPars. This is, however, not a complet 11i System Administration Handbook and Toolkit is a complete system administration guide that you may want to consider as a companion to this book. It also contains a UNIX section as well as an HP-UX and Windows interoperability section. Each chapter starts with partition-specific information and later in the chapter contains background information on the topic. In the chapter covering booting partitions, for instance, I first cover topics specifically related to booting partitions. Later in the chapter I cover booting in general. Covering both the partition-specific information related to a topic and then background information on the same topic gives you most of what you need to know to successfully deal with partitions. Relevant URLs There are many Web sites that can assist you in your Virtual Partition-related work and HP-UX system administration in general. The following are some of the more prominent HP-UX-related Web sites as they existed at the time of this writing: IT Resource Center (This is essential for every HP-UX administrator): http://www.itrc.com Technical documentation, including most HP-UX documents: http://www.docs.hp.com Software depot home page: http://www.software.hp.com vPar product information: http://www.hp.com/go/servicecontrol vPar Systems Administrator's Guide: http://docs.hp.com/hpux Instant Capacity on Demand (iCOD): http://www Professionals: http://www.interex.org Configurable kernel parameters: http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html Index of HP-UX online documents: http://docs.hp.com/hpux/onlinedocs/os Information on HP's new architecture Itanium processor family: http://www.IA64.hp.com Register name servers at: http://www.icann.org/registrars/accredited-list.html. Excellent unsupported system administration scripts at: ftp://contrib:[email protected]/sysadmin/ Software used for UNIX and Windows interoperability at: http://www.hummingbird.com/products/evals/index.html Information on Perl, including sites to download Perl: http://www.perl.com The Perl Journal: http://www.tpj.com Information about the GNOME desktop environment: http://www.gnome.org Public-domain software that has been ported to HP-UX: http://hpux.connect.org.uk Site devoted to managing and promoting open source: http://www.opensource.org Linux documentation site: http://www.linuxdoc.org Information on Java running on HP: include vPars manual pages and a few other select manual pages in this book. I have received a great deal of positive feedback on the inclusion of manual pages in my previous books. Many readers find it helpful to have the manual pages in the book to refer to when reading it when there is no system available to check on a command (apparently, a lot of people are reading my books while not at the office).