EXHIBIT FFF 

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 1 of 9 PageID #: 4758
Sun Microsystems, Inc.

4150 Network Circle

Santa Clara, CA 95054 U.S.A.

650 960-1300

http://www.sun.com/blueprints

Solaris Containers — What They Are 

and How to Use Them

Menno Lageman, Sun Client Solutions

Sun BluePrintsTM OnLine—May 2005

Part No.819-2679-10

Revision 1.0, 4/28/05

Edition: May 2005

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 2 of 9 PageID #: 4759 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 2 of 9
Please

Recycle

Copyright 2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, California 95054 U.S.A. All rights reserved. 

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document.

In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at

http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this 

product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, 

including font technology, is copyrighted and licensed from Sun suppliers. 

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark 

in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, Java, Sun BluePrints, SunSolve, SunSolve Online, docs.sun.com, JumpStart, N1, and Solaris are trademarks or 

registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered 

trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun 

Microsystems, Inc.

The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering 

efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. 

Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK 

GUIs and otherwise comply with Sun’s written license agreements.

U.S. Government Rights—Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions 

of the FAR and its supplements.

DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, 

INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE 

DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, California 95054 Etats-Unis. Tous droits réservés. 

Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En 

particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plus des brevets américains listés à l’adresse http://

www.sun.com/patents et un ou les brevets supplémentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. 

Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de 

Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par 

un copyright et licencié par des fournisseurs de Sun.

Certaines parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque enregistree 

aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd. 

Sun, Sun Microsystems, le logo Sun, Java, Sun BluePrints, SunSolve, SunSolve Online, docs.sun.com, JumpStart, N1, et Solaris sont des marques de fabrique 

ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des 

marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC 

sont basés sur une architecture développée par Sun Microsystems, Inc.

L’interface d’utilisation graphique OPEN LOOK et SunTM a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les 

efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de 

l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de 

Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

CETTE PUBLICATION EST FOURNIE “EN L’ETAT” ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y COMPRIS DES 

GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATION 

PARTICULIERE, OU LE FAIT QU’ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NE 

S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU.

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 3 of 9 PageID #: 4760 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 3 of 9
1

1

Executive Overview

Over the years businesses have been building large-scale information systems to solve 

business problems, with a focus on building scalable and highly available IT infrastructures 

that can adapt change. Providing sufficient availability and performance for business 

applications was the primary driver for these efforts. Today, the need to protect technology 

investments and provide the same service levels at a lower price point is shifting the focus to 

reducing IT infrastructure cost and improving end user service level management. Sun 

believes businesses can accomplish this goal by utilizing the facilities available in Solaris 

Containers.

End user application services are frequently comprised of components that are distributed 

across multiple servers. To reduce costs, businesses are eager to consolidate these 

applications onto fewer servers, but they must be careful to maintain isolation between 

applications. Hardware and software advances have led to the concept of server 

virtualization, the partitioning of network servers into several independent execution 

environments. Server virtualization allows a data center to be viewed and managed as a set of 

compute resources rather than a room of individual systems. 

Solaris Containers

Sun’s next advance in server virtualization is a concept called Solaris Containers. Solaris 

Containers provide isolation between software applications or services using flexible, 

software-defined boundaries. Applications can be managed independently of each other, even 

while running in the same instance of the SolarisTM Operating System (Solaris OS). Solaris 

Containers create an execution environment within a single instance of the Solaris OS and 

provide:

 Full resource containment and control for more predictable service levels

 Software fault isolation to minimize fault propagation and unplanned downtime

 Security isolation to prevent unauthorized access as well as unintentional intrusions

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 4 of 9 PageID #: 4761 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 4 of 9
2 Executive Overview • May 2005

The primary benefits of Solaris Containers are:

 Reduced management costs through server consolidation, and a reduced number of 

operating system instances

 Increased resource utilization with dynamic resource reallocation between Containers

 Increased service availability by minimizing fault propagation and security violations 

between applications

 Increased flexibility because software based Containers can be dynamically reconfigured

 Increased accuracy and flexibility of accounting, based on workloads rather than systems 

or processes

How This Article is Organized

 Chapter 2, “Introduction,” provides an overview of the features of Solaris Containers.

 Chapter 3, “Workload Management,” describes the nature of workloads today and how 

resource management techniques can be used to gives those workloads the resources they 

need.

 Chapter 4, “Managing Workloads — An Example,” provides an example of how to use 

projects to manage workloads effectively.

 Chapter 5, “Dynamic Resource Pools,” describes how dynamic resource pools can be used 

to automatically allocate resources.

 Chapter 6, “Resource Pools — An Example,” provides an example of how to use resource 

pools to partition the CPU resources on a system.

 Chapter 7, “Solaris Zones,” describes the new Zones features in the Solaris 10 Operating 

System.

 Chapter 8, “Using Zones — An Example,” illustrates how to use Zones to create virtual 

environments on a system.

 Chapter 9, “Containers — An Example,” describes how to create Containers that can be 

used to consolidate multiple copies of applications onto a system.

 Chapter 10, “Summary,” provides links to more information.

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 5 of 9 PageID #: 4762 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 5 of 9
 Typographic Conventions 3

Typographic Conventions

TABLE 1-1 describes the typographic conventions used in this article. 

TABLE 1-1 Typographic Conventions

Typeface Meaning Examples

AaBbCc123 The names of commands, files, 

and directories; on-screen 

computer output

Edit your .login file.

Use ls -a to list all files.

% You have mail.

AaBbCc123 What you type, when contrasted 

with on-screen computer output

% su

Password:

AaBbCc123 Book titles, new words or terms, 

words to be emphasized

Read Chapter 6 in the User’s Guide.

These are called class options.

You must be superuser to do this.

AaBbCc123 Command-line placeholder text; 

replace with a real name or value

To delete a file, type rm filename.

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 6 of 9 PageID #: 4763 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 6 of 9
4 Introduction • May 2005

2

Introduction

Today, businesses often design their systems with extra capacity to handle occasional peak 

loads to maximize revenue during periods of high demand. This extra system capacity 

remains unused during periods of normal demand. By allowing other applications to borrow 

this unused capacity a more cost-effective solution can be realized. During periods of high 

demand resources can be dynamically reallocated to important applications. Sharing 

resources in this way leads to higher resource utilization, reduces capital and system 

management costs by reducing the total number of systems required. For the consolidation of 

applications onto fewer systems to be effective, applications must be able to be managed 

independently. This requires the ability to control resource utilization, isolate faults, and 

manage security between multiple applications on the same server. In other words, it requires 

the establishment of virtual server boundaries within the server.

One of the first steps in this direction was the introduction of Dynamic System Domains on 

large Sun servers. With Dynamic System Domains, a server can be divided into several 

domains, each running its own copy of the Solaris OS. The domains provide hardware 

isolation between the applications so that faults in one domain do not propagate to 

applications in other domains. Domain boundaries can be dynamically partitioned to adapt to 

changing resource requirements. Resources can be moved from one domain to another 

without requiring a restart of the system. This adds flexibility to the data center while 

maintaining security and isolation from faults in other domains.

Starting with Solaris Resource Manager 1.x in the Solaris 2.6 OS, Sun has gradually 

enhanced the ability to control resource utilization and separate applications running in a 

single instance of the Solaris OS. Several technologies have been added to the Solaris OS 

over the years, providing additional capabilities and finer control over resource utilization. 

Examples of such technologies include the Solaris 9 Resource Manager and Resource Pools 

in the Solaris 9 OS. These technologies allow users to create a Solaris Container, an 

application or service that has one or more resource boundaries associated with it. These 

resource boundaries can limit CPU or memory consumption, network bandwidth, or even be 

a processor set. As a result, Solaris Containers are a prime enabler for server consolidation.

With the introduction of Solaris Zones in the Solaris 10 OS, Sun is taking Solaris Containers 

a step further by allowing servers to be partitioned in sub-CPU granularity. A Solaris Zone is 

a complete execution environment for a set of software services — a separate, virtual Solaris 

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 7 of 9 PageID #: 4764 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 7 of 9
 Workload Resource Management 5

environment within a Solaris instance. A Zone provides a virtual mapping from software 

services to platform resources, and allows application components to be isolated from each 

other even though they share a single Solaris OS instance. It establishes boundaries for 

resource consumption and provides isolation from other Zones on the same system. The 

boundaries can be changed dynamically to adapt to changing processing requirements of the 

applications running in the Zone.

Solaris Containers can be built using one or more the following technologies. These 

technologies can be combined to create Containers tailored for a specific server consolidation 

project.

 Solaris Resource Manager, for workload resource management

 Resource Pools, for partitioning

 Zones, for isolation, security and virtualization

It is important to note that a Solaris Container is not equivalent to a Solaris Zone. Zones 

technology can be used to create a Container with certain characteristics, such as the 

isolation provided by the virtual Solaris environment. But it is also possible to create another 

Solaris Container using Resource Pools technology if the required characterics of that 

Container can be met with the features Resource Pools provide. So while a Zone is a 

Container, a Container is not necessarily a Zone.

Workload Resource Management

One of the inhibitors for consolidating multiple applications onto a single server is the lack 

of control over the resources utilized by applications. Consider the example of a company 

that wants to consolidate two database servers onto one system to decrease the number of 

systems to manage, as well as the number of software licenses required. 

The first database is used by an on-line sales application while the second database is used 

by a marketing application. Because the sales application supports the core business of the 

company, it should be guaranteed a certain minimum amount of CPU when needed. The 

marketing application is a supporting application, and the CPU requirements of the database 

server are much less stringent. Without a mechanism to enforce these requirements, these two 

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 8 of 9 PageID #: 4765 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 8 of 9
6 Introduction • May 2005

applications cannot be consolidated successfully onto one system. With Solaris Containers, 

these business requirements can be implemented by establishing the appropriate CPU 

resource boundaries using the Fair Share Scheduler (Figure 2-1). 

FIGURE 2-1 Solaris Containers provide an environment that fosters the safe consolidation of 

applications onto a single server

The Fair Share Scheduler controls the allocation of available CPU resources among 

workloads based on their relative importance. See Chapter 3 for more information on 

workload management and Chapter 4 for a hands-on example of workload management.

Server

Server

Database 1

Database 2

Database 1

Database 2

DBA

Processes

Server

Case 2:24-cv-00093-JRG Document 95-18 Filed 10/23/24 Page 9 of 9 PageID #: 4766 Case 7:24-cv-00030-ADA-DTG Document 32-4 Filed 06/07/24 Page 9 of 9