On 02/15/09 10:48, John-Paul Drawneek wrote: > Just wondering what the gain you would get from using ldoms instead of zones > in the examples and blueprints docs that sun provides. > >>From the look they would be better suited to using zones, as same OS, >>software etc... > > But they use ldoms and don't say why? > > One I am mainly looking at is the tomcat setup.
There are a number of blueprints and other documents regarding the use of zones. Not knowing which one you are specifically looking at, it is hard to guess at why the author(s) chose the specific virtualization tool they did. Keep in mind that Solaris Containters or zones can be run in any instance of Solaris 10, whether already in a virtualized environment or not. This includes on bare metal, in a Dynamic System Domain, in an LDom, in a Xen domain, in an xVM server domain, in a VirtualBox instance, in a Parallels, in a VMware guest, and so on. Below is *my* list of features I give to customers to help decide whether to use Containers or LDoms (excluding the case of running a Container within an LDom or other virtualized environment). Steffen Solaris Containers ------------------ No special hardware required Single OS image Sub-CPU resource granularity Shared kernel, memory, file systems (configuration, resources and management) Solaris only (excluding Linux branded zone on x86) CPUs can be shared Works on all systems Virtually unlimited partitioning (max is 8191 non-global zones) Single system patch level Most admin operations can be applied to all containers in a single operation Very little performance overhead for zone infrastructure LDoms ----- Sun4v systems only Multiple OS images Multiples of CPU granularity Dedicated kernel, memory, file systems Can support other OSes CPUs can not be shared (CPUs here refers to a strand/thread) Currently available on Tx000, T5xy0 only Partitioning limited to number of CPUs Multiple and different patch and release levels possible Each LDom must be fully managed separately
