jpdrawneek wrote: > Pallab Bhattacharya wrote: > >> jpdrawneek wrote: >> >>> Steffen Weiberle wrote: >>> >>>> 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. >>>> >>> http://wikis.sun.com/download/attachments/24543563/820-4995.pdf >>> >>> I don't see how ldoms can provide higher utilization than zones >> >> >> hmm.. is that what the document says ? that ldoms provide higher >> utilization than zones? > > Not quite - its about using ldoms to gain higher util over using nothing.
well, in that particular application case, we can get higher utilization and scale-up by replacing some of the components with some other components too :) (not changing the application itself) - pl. see below.. > > But it give no real reason for picking ldoms over zones - other than > you can > >> >>> - ie the over head >> >> >> other than over head there must be other reasons for using LDOMs? > > hence why i am asking on the ldom mailing list. Ok. at least one for you :) zones is somewhat like and better than some of the sw-hv-v12n technology as far as performance is concerned - but provide same availabilty with LDOMs - when dom0 equivalant is rebooted (for any reason) - nothing happens to other domains (domU equivalant). And Steffen cited this : > Multiple OS images -regards -pallab >> -regards >> -pallab >> >>> >>>> 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. >>> >>> >>> I know this - I am just reading your documentation and wondering why >>> the choose to do it that way. >>> >>> >>>> >>>> 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 >>> >>> >>> So from your list there is seems to be no reason for that pdf to be >>> produced - so why use ldom for these task. >>> >>> Theres also the sugar crm pdf - again it chooses ldom when zones >>> seems a much better fit. >>> >>> _______________________________________________ >>> ldoms-discuss mailing list >>> ldoms-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss >> >> >> >> > -- Pallab Bhattacharya Performance & Architecture Engineering
