Sponsored Content
Operating Systems Solaris Reasons for NOT using LDOMs? reliability? Post 302848695 by os2mac on Thursday 29th of August 2013 08:53:11 PM
Old 08-29-2013
I use this exact configuration. LDOMS with zones installed in the LDOMS. it really comes down to money and complexity. Money in the sense you can use your LDOM configs to limit your exposure to licensing by physical resource limitations in the LDOM config (you can't do this with zones alone) and complexity in that it's essentially a double VM, or a VM running in a VM and all the complexity that brings add mounted storage from a SAN and you can see where it gets complicated very fast.
This User Gave Thanks to os2mac For This Post:
 

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Optimizing the system reliability

My product have around 10-15 programs/services running in the sun box, which together completes a task, sequentially. Several instances of the each program/service are running in the unix box, to manage the load and for risk-management reasons. As of now, we dont follow a strict strategy in... (2 Replies)
Discussion started by: Deepa
2 Replies

2. Solaris

To find out the reasons it crash

What are the steps to find out the reasons it crash in the solaris machine (3 Replies)
Discussion started by: sandeepkv
3 Replies

3. High Performance Computing

High reliability web server - cluster, redundancy, etc

Hi. I am IT manager/developer for a small organization. I have been doing as-needed linux server administration for several years and am by no means an expert. I've built several of my own servers, and our org is currently using hosting services for our servers and I am relatively happy. We... (3 Replies)
Discussion started by: bsaadmin
3 Replies

4. Ubuntu

Kubuntu on (certain) Lenovo laptops not possible - reasons?

Hi. I've used the Wubi install of Ubuntu and Kubuntu on my Windows XP machine for close to half a year now. My brother has let me know of a program where he works by which they're getting rid of (with support negated) several Lenovo laptops, on which, he also informs me, the K 'flavor' of Ubuntu... (1 Reply)
Discussion started by: SilversleevesX
1 Replies

5. AIX

MPIO reliability

Hi, we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes. Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
8 Replies
brands(5)						Standards, Environments, and Macros						 brands(5)

NAME
brands - alternate operating environments for non-global zones DESCRIPTION
The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which provide non-global zones that contain non-native operating environments. The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current zones structure. Every zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time. The default is the native brand. A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ- ment. Once a zone has been assigned a brand, that brand cannot be changed or removed. BrandZ extends the zones tools in the following ways: o A brand is an attribute of a zone, set at zone create time. o The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone. o The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone. Device Support The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects any attempt to add an unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported. ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWzoneu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C), ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F) SunOS 5.11 13 Feb 2009 brands(5)
All times are GMT -4. The time now is 12:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy