Consolidating Applications With Solaris Containers
- 1. Title : Consolidating Applications with Solaris Containers Author : Vaishal Gariwala Email : vaishal.gariwala@sos.sungard.com Environment : Solaris 10 Operating Environment Keywords : Virtualization and Consolidation Level : Intermediate Description : This article explains the basics about virtualization on Solaris 10 and how Solaris Containers work. Solaris Containers: Overview Solaris Containers Sun's operating system virtualization technique consists of several technologies that work together to foster improved resource management and isolate the environment from the underlying OS. With Solaris Containers, organizations can determine how to allocate resources among applications and services, and ensure they do not interfere with one another. In other words a Solaris Container is a complete runtime environment for applications. Solaris 10 Resource Manager and Solaris Zones software partitioning technology are both parts of the container. These components address different qualities the container can deliver and work together to create a complete container. The zones portion of the container provides a virtual mapping from the application to the platform resources. Zones allow application components to be isolated from one another even though the zones share a single instance of the Solaris Operating System. Resource management features permit you to allocate the quantity of resources that a workload receives. The container establishes boundaries for resource consumption, such as CPU. These boundaries can be expanded to adapt to changing processing requirements of the application running in the container.
- 2. Solaris Zones As part of the consolidation effort, it is important to evaluate the needs of the applications that will share the consolidated system. In this example, the email server and Web server applications need to run in isolated environments that make it appear as if they are running on physically separate machines. This is made possible by a Solaris Container technology called Solaris Zones, which provides separate environments on a machine and logically isolates applications from one another. Each application receives a dedicated namespace in which to run, and cannot see, monitor, or affect applications running in another zone. See the figure below: In the figure above all the three applications have there own Solaris Zone. Dynamic Resource Pools In the above mentioned example there are two types of applications, one that needs a fully dedicated CPU an email server, and another that is more flexible and can share CPUs the two Web servers. To accomplish these different levels of isolation we use a Solaris Container technology called Dynamic Resource Pools that enables CPU resources to be dedicated to specific applications. In this example, the email server needs a separate resource pool, while the Web servers can share another. As can be seen in figure below, we give one CPU to resource pool 1 and three CPUs to resource pool 2. In the figure email server has resource pool 1 and the Web Servers are sharing resource pool 2.
- 3. Fair Share Scheduler While the two Web servers are capable of sharing the remaining CPUs on the system, they each need a minimum guarantee of CPU resources that will be available to them. This is made possible by another Solaris Container technology called the Fair Share Scheduler (FSS). This software enables CPU resources to be allocated proportionally to applications. That is, each application gets assigned a number of the available shares of the total CPU. Of the five available shares, Web server 1 gets three, and Web server 2 gets two. Using all these Solaris Container technologies on the new server creates an environment like that shown in figure below. Now the system includes three Containers: one with dedicated CPU resources and two others shares CPU resources. Figure above shows a Container with a zone on a dedicated resource pool, and two Containers each with a zone on a shared pool with shares.
- 4. 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. Figure above shows the full example with all the resource pools and zones. Advantages: · Multiple isolated pools o Security o Resource Management · Comprehensive consolidation facility integrated as a core component of a mainstream OS o Portability to multiple platforms · Lower Administration o Manageable, observable o Reduces administration work o Delegation of container management · Low computational overhead · No additional hardware, licensing or support fees · Support multiple, isolated application environments in one OS instance o Achieves isolation, manageability, reduces cost · Software based solution o Achieves portability and simplicity · Do not require application changes or recompilation
- 5. Disadvantages: · No file system sharing o A Non-global Solaris Zone cannot be an NFS server, though they can establish NFS client connections to already running NFS servers.