Anyway, the link will forward you to a form where you need to fill up some personal information (it’s from Sun, so there will be no selling of email or spamming there). Once you’re done with that, go read and study Solaris Virturalization!

Enjoy!

» Download your free copy of Virtualization for Dummies.

This How-To Guide instructs users, system administrators, and developers unfamiliar with Solaris 10 OS on consolidating applications onto a single server using Solaris Containers technology. The guide starts with a brief overview of Solaris Containers and follows with an example of using Solaris Containers to consolidate two Web server applications and an email server application onto a single server. Users are guided step-by-step through the consolidation process, with code examples and illustrations.

After using this guide, a user should be able to create Solaris Containers by:

* Creating a resource pool
* Defining Solaris Zones
* Assigning CPU usage with the Fair Share Scheduler (FSS)
* Installing and booting a zone
* Configuring access to raw devices from the zone

I wont be able to post every info from the PDF file here.. But I can however maybe put a part so that it will entice you more to download the paper:

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

Dynamic Resource Pools
In this 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

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.

And many more! Excited yet? here’s the link for download:

https://www.sun.com/offers/details/solaris_containers.xml?cid=927534