Summary of the content on the page No. 1
Solaris 10 Container Guide
- Functionality status up to Solaris 10 10/09 and OpenSolaris 2009.06 -
Detlef Drewanz, Ulrich Gräf, et al.
Sun Microsystems GmbH
Effective: 30/11/2009
Functionalities
Use Cases
Best Practices
Cookbooks
Summary of the content on the page No. 2
Version 3.1-en Solaris 10 Container Guide - 3.1 Effective: 30/11/2009 Table of contents Disclaimer....................................................................................................................................................VI Revision control............................................................................................................................................VI 1. Introduction.........................................................................
Summary of the content on the page No. 3
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...................................................................36 4.1.5.3. Software installation by the global zone – usage in the global zone..............................................................
Summary of the content on the page No. 4
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............................................................................................55 4.5.2. Consolidating log information of zones.................................................................................56 4.5.3. Monitoring zone wo
Summary of the content on the page No. 5
Version 3.1-en Solaris 10 Container Guide - 3.1 Effective: 30/11/2009 5.2. Network............................................................................................................................................81 5.2.1. Change network configuration for shared IP instances........................................................81 5.2.2. Set default router for shared IP instance..............................................................................81 5.2.3. Network interface
Summary of the content on the page No. 6
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 Detlef Drewanz Adjustment with content of „Solaris Container Leitfaden 3.1“ Ulrich Gräf Table of Content with HTML for better navigating through the document Correction „Patching of systems with loca
Summary of the content on the page No. 7
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 Detlef Drewanz, Ulrich Gräf Additional network examples 27/10/2006 Revision control table reorganized 1.1 (the latest at the top) Detlef Drewanz References amended Hardening of zones amended 1.0 24/10/2006 Feedback incorporated, corrections Detlef Drewanz Use cases and network Zones added in the
Summary of the content on the page No. 8
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 in english. st By making Solaris 10 available on 31 January 2005, an operating system with groundbreaking innovations has been provided by Sun Microsystems. Among these innovations are Solaris C
Summary of the content on the page No. 9
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 virtualization). Solaris Containers are Solaris Zones with Resource Management. The term is frequently used (in this document as well) as a synonym for Solaris Zones. Resource Management has alr
Summary of the content on the page No. 10
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 causes little additional runtime expenditure. Local zones execute the same Solaris version as the global zone. Alternatively, virtual execution environments for older Solaris versions (SPARC: S
Summary of the content on the page No. 11
Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.1.2. Zones and software installation [dd] The respective requirements on local zones determine the manner in which software is installed in zones. There are two ways of supplying software in zones: 1. Software is usually supplied in pkg format. If this software is installed in the global zone with pkgadd, it will be automatically available to all other local zones as well. This considerably simplifies
Summary of the content on the page No. 12
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. The following resources can be managed: • CPU resources (processor sets, CPU capping and fair share scheduler) • Memory use (real memory, virtual memory, shared segments) • Monitoring network traff
Summary of the content on the page No. 13
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-called resource capping daemon (rcapd). A limit for physical memory consumption is defined for the respective objects. If consumption of one of the projects exceeds the defined limit, the rcapd cau
Summary of the content on the page No. 14
Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.1.7. Zones and high availability [tf/du/hs] In the presence of all RAS capabilities, a zone has only the availability of a computer and it decreases with the number of components of the machine (MTBF). If this availability is not sufficient, so-called failover zones can be implemented using the HA Solaris Container Agent, allowing zones to be panned among cluster nodes (from Sun Cluster 3.1 08/05). Thi
Summary of the content on the page No. 15
Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.1.9. Solaris container cluster (aka "zone cluster") [hs] In autumn 2008, within the scope of the Open HA Cluster Project, zone clusters were announced. The latter has also been available since Sun Cluster 3.2 1/09 in a commercial product as Solaris Container Cluster. A Solaris Container Cluster is the further development of the Solaris zone technology up to a virtual cluster, also called "zone cluster
Summary of the content on the page No. 16
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 computers This also includes multi-tier architectures with firewall, load balancing, web and application servers and databases. • Applications on a network of computers This includes distributed applications and job systems. • Many applications on a large computer The separation of appli
Summary of the content on the page No. 17
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 turned off. Shared parts are either very failsafe (cabinet) or redundantly structured (service processor, power supplies). Advantages: • Separation: Applications are well separated from each other
Summary of the content on the page No. 18
Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.2.2. Logical partitions [ug] A minimal operating system called the hypervisor, that virtualizes the interface between the hardware and the OS of a computer, runs on the computer's hardware. A separate operating system (guest operating system) can be installed on the arising so-called virtual machines. In some implementations, the hypervisor runs as a normal application program; this involves increased
Summary of the content on the page No. 19
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 multitenant enabled: it exists only once but appears in each zone as though it was assigned exclusively. Separation is implemented by restricting access to resources, such as e.g. the visibility of proce
Summary of the content on the page No. 20
Version 3.1-en Solaris 10 Container Guide - 3.1 2. Functionality Effective: 30/11/2009 2.2.4. Consolidation in one computer [ug] The applications are installed on a computer and used under different userid. This is the type of consolidation feasible with modern operating systems. Advantages: • Application: All applications are executable as long as they are executable in the basic operating system and do not use their own OS drivers. However, there are restrictions if different versions o
