Sun Microsystems 10 - Manuals

Page 2 - Table of contents; II

Version 3.1-en Solaris 10 Container Guide - 3.1 Effective: 30/11/2009 Table of contents Disclaimer ....................................................................................................................................................VI Revision control ....................................

Page 3 - III

Version 3.1-en Solaris 10 Container Guide - 3.1 Effective: 30/11/2009 4.1.5.1. Software installation by the global zone – usage in all zones .......................................................................36 4.1.5.2. Software installation by the global zone – usage in a local zone ..............

Page 4 - IV

Version 3.1-en Solaris 10 Container Guide - 3.1 Effective: 30/11/2009 4.5. Management and monitoring ............................................................................................................55 4.5.1. Using boot arguments in zones ......................................................

Page 6 - Disclaimer

Version 3.1-en Solaris 10 Container Guide - 3.1 Disclaimer Effective: 30/11/2009 Disclaimer Sun Microsystems GmbH does not offer any guarantee regarding the completeness and accuracy of the information and examples contained in this document. Revision control Version Contents Who 3.1 30/11/2009 Adju...

Page 7 - VII

Version 3.1-en Solaris 10 Container Guide - 3.1 Disclaimer Effective: 30/11/2009 Version Contents Who Drawings 1 - 6 as an image Detlef Drewanz 1.2 06/11/2006 General chapter virtualization Additional network examples Detlef Drewanz, Ulrich Gräf 1.1 27/10/2006 Revision control table reorganized (the...

Page 8 - January 2005, an operating system with groundbreaking

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 [ 25 ], starting with version 3.1 we begin to deliver a version...

Page 9 - Solaris Containers and Solaris Zones; a virtualization at the operating; Server

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2. Functionality 2.1. Solaris Containers and Solaris Zones 2.1.1. Overview [ug] Solaris Zones is the term for a virtualized execution environment – a virtualization at the operating system level (in contrast to HW...

Page 10 - Additional details are summarized in the following table:

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 Thus, a local zone is a Solaris environment that is separated from other zones and can be used independently. At the same time, many hardware and operating system resources are shared with other local zones, which...

Page 12 - Processor sets in a resource pool; z o n e c f g : a d d d e d i c a t e d - c p u; Fair share scheduler in a resource pool; defined share; CPU resource management within a zone

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.1.5. Zones and resource management [ug] In Solaris 9, resource management was introduced on the basis of projects, tasks and resource pools. In Solaris 10, resource management can be applied to zones as well. Th...

Page 13 - locked

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.1.5.2. Memory resource management [ug] In Solaris 10 (in an update of Solaris 9 as well), main memory consumption can be limited at the level of zones, projects and processes. This is implemented with the so-cal...

Page 16 - Virtualization technologies compared

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.2. Virtualization technologies compared [ug] Conventional data center technologies include • Applications on separate computersThis also includes multi-tier architectures with firewall, load balancing, web and a...

Page 17 - Overhead: Each machine has a separate operating system overhead.

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.2.1. Domains/physical partitions [ug] A computer can be partitioned by configuration into sub-computers (domain, partition). Domains are almost completely physically separated since electrical connections are tu...

Page 19 - BrandZ

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.2.3. Containers (Solaris zones) in an OS [ug] In an operating system installation, execution environments for applications and services are created that are independent of each other. The kernel becomes multiten...

Page 21 - compared to installation on a separate computer.; Logical; Key for the meaning of the symbols:

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.2.5. Summary of virtualization technologies [ug] The virtualization technologies discussed above can be summarized in the following table – compared to installation on a separate computer. Separate computer Doma...

Page 22 - HW error containment

Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 15 Figure 6: [dd] Comparison of virtualization technologies HW OS App Logical virtualisation (logical partitions) OS virtualisation (Container - Solaris zones - Physical virtualisation (Domains/ physical partition...

Page 23 - Sparse-root zones; Assessment; Grid; Grid network

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3. Use Cases The following chapter discusses a variety of use cases for Solaris Containers and evaluates them. 3.1. Grid computing with isolation Requirement [ug] There is a need within a company to use free cycles on...

Page 24 - s y s i d c f g; Global Zone; Webserver

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.2. Small web servers Requirement [ug] One of the following situations exists: • An Internet Service Provider (ISP) would like to have the option to set up web servers automatically, without additional costs. Based o...

Page 25 - Zones as runtime environments for one application each.; The number of required systems is reduced.; App A1 App A2 App B; Network A; App C App C App C; Network B

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.3. Multi-network consolidation Requirement [dd] A company uses several different networks that are separated either by firewalls or by routers. Applications are run in the individual networks. The company would like...

Page 27 - A device is provided from the global zone to a local zone.; The operating division's expenses for creating the zones are low.; Network C

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.5. Multi-network backup Requirement [dd] A company has several different networks that are separated in different stages either by firewalls or by routers. Different computers are installed in the individual network...

Page 28 - Requirement; Development systems; Solution; Option: Application administrator with root access.; ment

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.6. Consolidation development/test/integration/production Requirement [ug] Usually, further systems supporting the same application exist while an application is in production: • Development systems • Test systems • ...

Page 29 - File system decisions analogous to the production system.; Test

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.7. Consolidation of test systems Requirement [ug] To test software and applications, there are many test systems in the data center environment that are only ever used for tests. They are mostly used only for qualit...

Page 31 - App

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.9. Server consolidation Requirement [ug] In a data center, several applications run whose workload is too low (often much less than 50%). The computers themselves usually require a lot of electricity, cooling and sp...

Page 32 - Confidentiality of data and processes; Applications are installed in local zones only .; The operators/customers retain confidentiality.

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.10. Confidentiality of data and processes Requirement [ug] In the data center, applications are running on different computers because • Certain departments want to be certain that data and processes are not seen by...

Page 33 - Data are stored locally.; Developer

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.11. Test systems for developers Requirement [ug] Developers need test systems to test their application. Frequently, the interaction of several computers must be tested as well. Resources for the installation of tes...

Page 34 - Solaris 8 and Solaris 9 containers for development; Installation of an archived legacy system.; Current hardware based on Solaris 10 can be used.

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.12. Solaris 8 and Solaris 9 containers for development Requirement [ug] There are still systems running in companies under Solaris 8 or Solaris 9 with self-developed software, and it must be possible for these syste...

Page 35 - Solaris 8 and Solaris 9 containers as revision systems; Old hardware perhaps has not a maintenance contract.

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.13. Solaris 8 and Solaris 9 containers as revision systems Requirement [ug] For legal reasons or due to revision requests, it is necessary to have certain systems available for years under Solaris 8 or Solaris 9. • ...

Page 36 - Hosting for several companies on one computer; Company; NAT

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.14. Hosting for several companies on one computer Requirement [ug] An application service provider operates systems for a variety of companies. The systems are underutilized. Solution [ug] The applications are conso...

Page 38 - Minimal downtime required through live upgrade and ZFS

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.16. Upgrade- and Patch-management in a virtual environment Requirement [da] Virtualization by means of Solaris Containers allows the application to be disengaged from the hardware. An application can thus be run ver...

Page 39 - Service-oriented Solaris server infrastructure; Staging

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009 3.17. "Flying zones" – Service-oriented Solaris server infrastructure Requirement [os] A highly available virtualization platform to run business-critical applications should meet the following requirements: •...

Page 43 - usage in all zones; p k g a d d

Version 3.1-en Solaris 10 Container Guide - 3.1 4. Best Practices Effective: 30/11/2009 4.1.5. Software installations in Solaris and zones [dd] The zones' directory structure is determined mainly from the need to install software with special needs in this area. Prior to creating the zones, this que...

Page 44 - d i r

Version 3.1-en Solaris 10 Container Guide - 3.1 4. Best Practices Effective: 30/11/2009 4.1.5.3. Software installation by the global zone – usage in the global zone • non-pkg software − Software A is installed by the global zone e.g. in /software/A − /software/A is available to the global zone as a ...

Page 52 - hosts; sysidcfg

Version 3.1-en Solaris 10 Container Guide - 3.1 4. Best Practices Effective: 30/11/2009 4.1.9. Separate name services in zones [ug] Name services include among other things the hosts database and the userids ( p a s s w d , s h a d o w ) and are configured with the file / e t c / n s s w i t c h . c...

Page 54 - is considered sufficient.

Version 3.1-en Solaris 10 Container Guide - 3.1 4. Best Practices Effective: 30/11/2009 4.2.3. One application per zone [ug] Another paradigm is to always install one application per zone.A zone has very little overhead; basically, only the application processes are separated from the rest of the sy...

Page 55 - DWDM; Sun Cluster Geographic

Version 3.1-en Solaris 10 Container Guide - 3.1 4. Best Practices Effective: 30/11/2009 administrator. With the software products described here, the requirements with respect to visualization and flexibilization of containers right up to disaster recovery concepts can be covered completely. The har...

Page 87 - Accelerated automatic creation of zones on a ZFS file system

Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009 5.1.15. Accelerated automatic creation of zones on a ZFS file system [bf/ug] If a zone is configured on a ZFS file system, it can be duplicated very quickly by using ZFS snapshots. This procedure is described below by...

Page 92 - Implementation; b g e 1

Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009 5.2.7.3. Zones in separate network segments using exclusive IP instances [dd/ug] Two local zones, zone1 and zone2, are located in separated network segments and provide services for these network segments. • Each loca...

Page 111 - Using live upgrade to patch a system with local zones; Patching a system with local zones

Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009 5.3.10. Shutting down a zone [dd] Zones can be shut down from the local zone itself or from the global zone. Depending on which option is used, running services are either completed or simply stopped. • z o n e a d m ...

Page 112 - i n i t 6; under no circumstances the command; r e b o o t

Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009 The BE is now available e.g. under /.alt.s10-807+1. Next, the boot archive of this BE is updated and the BE is unmounted again. bootadm update-archive -R /.alt.s10-807+1luumount s10-807+1 Finally, the new BE can be ac...

Page 116 - Dynamic resource pools

Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009 created with p o o l c f g and p o o l a d m . 5.5.9. Dynamic resource pools for zones [dd] As already described in 4.6.2.5 Dynamic resource pools , dynamic resource pools can very easily be used for zones since Solar...

Page 117 - Limiting the physical main memory consumption of a project; Limiting memory resources

Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009 5.5.10. Limiting the physical main memory consumption of a project [dd] To limit the physical main memory of a project, the resource capping daemon r c a p d ( 1 M ) can be used. If the resident set size (RSS) of a pr...

Page 119 - Supplement; A. Solaris Container in OpenSolaris; z o n e a d m - z k e e t o n g a i n s t a l l - a

Version 3.1-en Solaris 10 Container Guide - 3.1 Supplement Effective: 30/11/2009 Supplement A. Solaris Container in OpenSolaris A.1. OpenSolaris – general [dd] In 2005, Sun Microsystems started OpenSolaris as an OpenSource project in order to support and advance the developer community around Solari...

Page 120 - The configuration of the zone is done as usual with

Version 3.1-en Solaris 10 Container Guide - 3.1 A. Solaris Container in OpenSolaris Effective: 30/11/2009 A.1. Cookbook: Configuring an ipkg zone The configuration of the zone is done as usual with z o n e c f g ( 1 M ) . root@cantaloup:~# zonecfg -z keetonga keetonga: No such zone configured Use 'c...