OpenSolaris

Printable Version Enter a New Search
Bug ID 6222025
Synopsis RFE: simplify rctl syntax and improve cpu-shares/FSS interaction
State 10-Fix Delivered (Fix available in build)
Category:Subcategory utility:zones
Keywords zones
Responsible Engineer Gerald Jelinek
Reported Against
Duplicate Of
Introduced In
Commit to Fix snv_56
Fixed In snv_56
Release Fixed solaris_nevada(snv_56) , solaris_10u4(s10u4_03) (Bug ID:2145577)
Related Bugs 6421202 , 4970603
Submit Date 26-January-2005
Last Update Date 25-January-2007
Description
One of the most common things people want to do in conjunction with zones
is manage the CPU shares assigned to each zone.  Currently, this requires
uttering the following incantation in zonecfg:

     zonecfg:my-zone3> add rctl
     zonecfg:my-zone3:rctl> set name=zone.cpu-shares
     zonecfg:my-zone3:rctl> add value (priv=privileged,limit=5,action=none)
     zonecfg:my-zone3:rctl> end

The person setting up the zone probably doesn't care about the nuances
of rctl syntax (basic vs. privileged, none vs. deny, etc.).  This would
be much easier to do (and much less prone to error due to typos, spelling
mistakes, and other problems) if one could just type:

     zonecfg:my-zone3> set cpu-shares=5

This could be done compatibly by supporting either input method, though
there are undoubtedly some issues to work out.  (What if someone
specifies using both forms?  What should "zonecfg info" or "zonecfg export"
say?)

We could also improve usability by having zoneadm/zoneadmd print a warning
if booting a zone with the cpu-shares property set that is bound to a pool
that is not running in the FSS class.

 xxxxx@xxxxx.com 2005-1-26 22:46:00 GMT
Work Around
N/A
Comments
N/A