Sun Microsystems 10 用户手册
Version 3.1-en
Solaris 10 Container Guide - 3.1 1. Introduction
Effective: 30/11/2009
1. Introduction
[dd/ug] This guide is about Solaris Containers, how they work and how to use them. Although the
original guide was developed in german [
original guide was developed in german [
], starting with version 3.1 we begin to deliver a version in
english.
By making Solaris 10 available on 31
st
January 2005, an operating system with groundbreaking
innovations has been provided by Sun Microsystems. Among these innovations are Solaris
Containers that can be used - among other things - to consolidate and virtualize OS environments, to
isolate applications, and for resource management. Solaris Containers can contribute considerably to
the advanced reconfiguration of IT processes and environments, as well as to cost savings in IT
operations.
Containers that can be used - among other things - to consolidate and virtualize OS environments, to
isolate applications, and for resource management. Solaris Containers can contribute considerably to
the advanced reconfiguration of IT processes and environments, as well as to cost savings in IT
operations.
Using these new possibilities requires know-how, decision guidance and examples which we have
summarized in this guide. It is directed at decision makers, data center managers, IT groups and
system administrators. The document is subdivided into the following chapters: Introduction,
Functionality, Use Cases, Best Practices, Cookbooks, and a list of references.
summarized in this guide. It is directed at decision makers, data center managers, IT groups and
system administrators. The document is subdivided into the following chapters: Introduction,
Functionality, Use Cases, Best Practices, Cookbooks, and a list of references.
A brief introduction is followed by the functionality part, which contains a description of today's typical
data center requirements in terms of virtualization and consolidation, as well as a description and
comparison of Solaris Container technology. This is followed by a discussion of the fields of
application for Solaris Containers in a variety of use cases. Their conceptual implementation is
demonstrated by means of Best Practices. In the chapter on Cookbooks, the commands used to
implement Best Practices are demonstrated using concrete examples. All cookbooks were tested and
verified by the authors themselves. The supplement discusses the specifics of Solaris Containers in
OpenSolaris.
data center requirements in terms of virtualization and consolidation, as well as a description and
comparison of Solaris Container technology. This is followed by a discussion of the fields of
application for Solaris Containers in a variety of use cases. Their conceptual implementation is
demonstrated by means of Best Practices. In the chapter on Cookbooks, the commands used to
implement Best Practices are demonstrated using concrete examples. All cookbooks were tested and
verified by the authors themselves. The supplement discusses the specifics of Solaris Containers in
OpenSolaris.
The document itself is designed to be a reference document. Although it is possible to read the
manual from beginning to end, this is not mandatory. The manager of a data center gets an overview
of the Solaris Container technology or have a look at the use cases. An IT architect goes over the
Best Practices in order to build solutions. Meanwhile, a system administrator tests the commands
listed in the cookbooks in order to gain experience. That is why the document offers something for
everyone and in addition provides references to look into other areas.
manual from beginning to end, this is not mandatory. The manager of a data center gets an overview
of the Solaris Container technology or have a look at the use cases. An IT architect goes over the
Best Practices in order to build solutions. Meanwhile, a system administrator tests the commands
listed in the cookbooks in order to gain experience. That is why the document offers something for
everyone and in addition provides references to look into other areas.
Many thanks to all who have contributed to this document through comments, examples and
additions. Special thanks goes to the colleagues (in alphabetical order): Dirk Augustin[da], Bernd
Finger[bf], Constantin Gonzalez, Uwe Furchheim, Thorsten Früauf[tf], Franz Haberhauer, Claudia
Hildebrandt, Kristan Klett, Joachim Knoke, Matthias Pfützner, Roland Rambau, Oliver Schlicker[os],
Franz Stadler, Heiko Stein[hes], Hartmut Streppel[hs], Detlef Ulherr[du], Thomas Wagner and Holger
Weihe.
additions. Special thanks goes to the colleagues (in alphabetical order): Dirk Augustin[da], Bernd
Finger[bf], Constantin Gonzalez, Uwe Furchheim, Thorsten Früauf[tf], Franz Haberhauer, Claudia
Hildebrandt, Kristan Klett, Joachim Knoke, Matthias Pfützner, Roland Rambau, Oliver Schlicker[os],
Franz Stadler, Heiko Stein[hes], Hartmut Streppel[hs], Detlef Ulherr[du], Thomas Wagner and Holger
Weihe.
Please do not hesitate to contact the authors with feedback and suggestions.
Berlin and Langen, November 2009
Detlef Drewanz (
Detlef.Drewanz@sun.com
), Ulrich Gräf (
Ulrich.Graef@sun.com
)
1