利用Solaris容器整合服务器应用实战指南

需积分: 5 14 浏览量更新于2024-08-02 收藏 436KB PDF 举报

"Solaris 容器使用指南旨在帮助用户、系统管理员和开发者了解如何利用 Solaris 容器技术在单个服务器上整合应用程序。该指南涵盖了 Solaris 容器的概述、Solaris 区域、动态资源池、公平份额调度器等内容，以及创建和管理容器的具体步骤。" 在 Solaris 操作系统中，Solaris 容器是一种虚拟化技术，它允许在一个单一的 Solaris 实例内创建多个独立的执行环境，这些环境被称为“区域”（Zones）。这使得不同应用程序和服务可以在一个物理服务器上隔离运行，而不会相互干扰，从而提高资源利用率并简化管理。 Solaris 区域是容器技术的核心，有两种主要类型：全局区（Global Zone）和非全局区（Non-Global Zone）。全局区是系统默认启动的区域，拥有操作系统的所有功能，可以创建和管理其他所有区域。非全局区则是在全局区内部创建的，它们是独立的执行环境，具有自己的进程空间和文件系统，但依赖全局区提供服务和资源。动态资源池（Dynamic Resource Pools）是 Solaris 容器管理的重要组成部分，它允许管理员根据需要动态调整资源分配，如 CPU、内存和磁盘空间。这可以通过创建自定义资源池，将特定的硬件资源分配给不同的区域，确保应用程序和服务得到预期的性能。公平份额调度器（Fair Share Scheduler, FSS）是一种 CPU 资源调度策略，它确保了系统中的所有用户和进程都能获得公平的 CPU 时间。通过 FSS，管理员可以为每个区域设定权重，根据权重分配 CPU 使用率，确保高优先级的服务得到足够的处理能力。在创建 Solaris 容器的过程中，首先需要创建一个新的资源池，然后定义区域的配置，包括分配的资源和安全策略。接下来，安装区域的操作系统镜像并设置启动参数。虚拟平台管理允许管理员控制区域对物理设备的访问，例如，让某个区域能够直接访问网络接口或磁盘。最后，容器创建完成后，可以登录到区域进行进一步的配置和应用部署。例如，指南中提到创建两个 Web 服务器容器，通过启用 FSS 并设定权重，确保两个容器在共享资源时能按比例分配 CPU 功率。此 Solaris HowTo 指南提供了详细的步骤指导，不仅适用于初次接触 Solaris 容器的用户，也对有经验的管理员在实践中提供实用帮助，以实现高效且可靠的服务器和应用程序整合。

Using all these Solaris Container technologies on this new

server creates an environment like that shown in Figure 5.

Now the system includes three Containers: one with

dedicated CPU resources, and two others sharing CPU

esources.

Figure 5—A Container with a zone on a dedicated resource

pool, and two Containers each with a zone on a shared

pool with shares.

Two Types of Zones

All systems that run Solaris 10 contain a master zone,

called the

global zone

. The global zone is the original

Solaris OS instance. It has access to the physical hardware

and can control all processes. It also has the authority to

create and control new zones, called non-global zones, in

which applications run. Non-global zones do not run

inside the global zone—they run along side it—yet the

global zone can look inside non-global zones to see how

they are configured, monitor, and control them.

Like the other zones, this global zone is also associated

with a resource pool. In our example this is resource pool

2. In this case, it shares CPU resources with the Web

servers. When the Fair Share Scheduler is enabled, the

global zone defaults to one share. So Figure 5 needs to be

amended to include the global zone as shown in Figure 6.

Figure 6—The full example with all the resource pools and

zones.

Solaris™ Containers: An Example

his section is a step-by-step guide that shows how to

create the email and Web server example described above.

It does this by going through the following steps:

• Creating a new resource pool

•

Creating the email zone on the new resource pool

• Enabling the Fair Share Scheduling on the Web server

resource pool

• Creating the first Web server Container

• Creating the second Web server Container

When creating the last two Containers we will also show

some extra configuration options available to Solaris

Zones.

As the starting point, Figure 7 shows how the system looks

before any of these steps are taken. The only existing

objects are the global zone, and one resource pool. The

global zone is associated with this one resource pool. This

first resource pool is also called the

default pool

, and

before any action is taken, it has all the CPUs in the

system.

Figure 7—Every system has a default processor set.

Creating a New Resource Pool

In the Solaris OS, a

resource pool

is a logical entity that

owns a subset of the system resources, like CPU and

Memory. These subsets are known as

resource sets

Currently the Solaris OS only has one type of resource

set—a processor set. Every resource pool is associated

with a processor set—so if you want to give this pool its

own unique CPUs, you will need to define the processor

set, the number of processors it contains, and associate it

with a pool.

Every additional resource pool created is taken out of the

default pool. So, the email server's CPU comes out of the

four CPUs initially assigned to the default pool (leaving

three). Resource pools can be dynamically created and

removed on a running system, but you must leave one

CPU for the default pool.

Resource Pool 1

(1 CPUs)

Default Resource Pool

(3 CPUs)

Global

Zone

Zone 2

Zone 3

Zone 1

Container 2 Container 1

Number

of Shares

Number

of Shares

Container 4 Container 3

Resource Pool 1

(1 CPU)

Resou rce Pool 2

(3 CPUs and Fair Share Scheduler)

Zone 2

eb Server 1

Zone 3

eb Server 2

Zone 1

mail Application

Container 2 Container 3 Container 1

Number

of Shares

Number

of Shares

Default Resource Pool

(4 CPUs)

Global

Zone

Solaris 10 Operating System sun.com/solaris

剩余16页未读，继续阅读

zhangsc

粉丝: 26
资源: 15

利用Solaris容器整合服务器应用实战指南

Solaris管理员指南

Oracle Solaris 10 System Administration Guide: Oracle Solaris Co

在Solaris容器中优化Oracle数据库部署实践

Solaris ZONE 基本操作指南：容器化技术应用

Oracle Solaris 9系统管理指南：容器技术详解

Solaris 10到Solaris 11迁移指南：ISV实战

Oracle Solaris 11.3 资源管理与 Solaris Zones 开发指南

Oracle Solaris 8系统管理指南：容器与区域资源管理

Oracle Solaris 10 系统管理指南：资源管理和容器技术

Solaris Zone操作指南：创建与删除

最新资源