You can attach your zones to static or dynamic pools that will control
the CPU utilization of them. You can weight zones via the share concept
within the same pool to determine which zone is more important within a
given pool. You can also control the inband and outband network traffic
of the zone. You can then further set projects up inside your zones to
control the memory and CPU utilization of applications or groups of
users that may be running within them. The layers look like this:
Raw host utilization
static/dynamic pool CPU utilization
zones: shares | IPQoS
projects: shares | mem limits
Solaris will soon add memory set constraints for zones.
It you want a tool to not only discover all of that graphically no
matter how you have created it across your enterprise, allow you to set
thresholds to generate SNMP traps and email notifications on resource
breeches or status conditions, and provision these conceptscheck out
Solaris Container Manager.
Thanks,
Mike
[EMAIL PROTECTED] wrote:
Hello,
Following a recent successfull deployment of 8 default sparse zones using
zonemgr.
I would like to add some simple resource caps to prevent one app stealing all
the resources (as actually happened - on a T2k). What would be the next most
logical step?
TIA
Tony
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
