Information Technology Reference
In-Depth Information
At this point, we have successfully cloned the original desktop. All of the cus-
tomizations have been preserved and do not need to be performed again. The
new guest machine has started automatically, and we can now connect to it from
another rdesktop session anywhere on the network.
# rdesktop 192.168.1.42
It is important to consider the effects of cloning a Container. The clone has
the same license keys and registration information as the original. If your license
agreement requires installation of a new activation key and subsequent registra-
tion, these tasks must be performed before the guest can be used.
8.5.8 Summary
This example highlights several facets of Oracle Solaris virtualization. Every virtu-
alization solution has strengths. This example leverages the ability of VirtualBox
to run Windows guests on the highly scalable Solaris OS. It also takes advantage
of the fine-grained resource controls of Solaris Containers. As you add virtual
desktops to this system, you can change the CPU cap of each one, even as they
continue running. Finally, this example demonstrates the ability to use two differ-
ent virtualization solutions to achieve goals that neither can achieve alone.
8.6 Consolidating with Oracle Solaris Containers
Solaris Containers are excellent environments for consolidating many kinds of
applications. For example, consolidating multiple Oracle Solaris web servers into
Containers on one system is a straightforward process, but you can also consoli-
date web servers from other operating systems. Consolidating into Containers
provides better isolation and manageability than simply collapsing the contents
into one web server. Benefits of using Containers in this situation include work-
load isolation, comprehensive resource controls, delegated administration, and
simple mobility, among others.
This section demonstrates the simplicity of migrating Apache web server en-
vironments from multiple Red Hat Enterprise Linux systems to one Solaris 10
system. This example is relatively simple because Apache's configuration files use
the same syntax, for any one version, on any UNIX or Linux system.
Nevertheless, slight differences in file system layout must be taken into account
during this consolidation. On most Linux distributions, the default location for
Apache's configuration file is /etc/httpd/conf/httpd.conf , while on Solaris it
is /etc/apache2/httpd.conf . Further, the default home of web pages is /var/
 
 
 
 
Search WWH ::




Custom Search