|
|||||||
Part I Overall Planning of Any Solaris Installation or Upgrade 1. Where to Find Solaris Installation Planning Information 2. What's New in Solaris Installation 3. Solaris Installation and Upgrade (Roadmap) 4. System Requirements, Guidelines, and Upgrade (Planning) 5. Gathering Information Before Installation or Upgrade (Planning) Part II Understanding Installations That Relate to GRUB, Solaris Zones, and RAID-1 Volumes 6. x86: GRUB Based Booting for Solaris Installation 7. Upgrading When Solaris Zones Are Installed on a System (Planning) Upgrading With Non-Global Zones Disk Space Requirements for Non-Global Zones 8. Creating RAID-1 Volumes (Mirrors) During Installation (Overview) 9. Creating RAID-1 Volumes (Mirrors) During Installation (Planning) |
Solaris Zones (Overview)The Solaris Zones partitioning technology is used to virtualize operating system services and provide an isolated and secure environment for running applications. A non-global zone is a virtualized operating system environment created within a single instance of the Solaris OS. When you create a non-global zone, you produce an application execution environment in which processes are isolated from the rest of the system. This isolation prevents processes that are running in one non-global zone from monitoring or affecting processes that are running in other non-global zones. Even a process running with superuser credentials cannot view or affect activity in other zones. A non-global zone also provides an abstract layer that separates applications from the physical attributes of the machine on which they are deployed. Examples of these attributes include physical device paths. Every Solaris system contains a global zone. The global zone has a dual function. The global zone is both the default zone for the system and the zone used for system-wide administrative control. All processes run in the global zone if no non-global zones are created by the global administrator. The global zone is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled. Only the global zone is bootable from the system hardware. Administration of the system infrastructure, such as physical devices, routing, or dynamic reconfiguration (DR), is only possible in the global zone. Appropriately privileged processes running in the global zone can access objects associated with the non-global zones.
|
||||||
|