I agree that there is a need something to put a collection of zones into the "ready" state, but I don't think the txzonemgr script should do this. Currently the script is noun- verb. But I think what you need is verb, then noun. For example, you would select the "Make Ready" verb and then get a list of eligible zones with checkboxes. That seems to require a different solution.
Maybe the current autoboot keyword in the zonecfg command should take a second parameter, e.g. "ready", or a new keyword, like "autoready" might be better. I also question the implementation of autobooting being done in background; this causes excessive thrashing when you simultaneously boot a large number of zones. So there should be an option of whether to bring up the zones simultaneously or in a specified order. For Trusted Extensions, the peferred order is lower labels first, so that higher labeled zones can get the read-down mounts to work properly. --Glenn David Gaines wrote: >I've been using txzonemgr and it is quite handy, it centralizes things nicely. > I do have a question about what would be the best approach to handle changing >the state of multiple zones with one command. Currently I have 12 zones, >using Glenn's advice I put them in the ready state on my NFS server. To my >knowledge these zones can only be in one of two states when I boot my server, >halted (installed) or booted. So I start my NFS server with the zones halted, >which allows the server to come up quicker, then I run a script that wraps >zoneadm and loops through the zones I want to put in the ready state without >having to run zoneadm numerous times. Of course on a production system I >would not be restarting my servers frequently but right now while evaluating >TX I do a lot of rebooting and rebuilding, thank god for jumpstart. A utility >that allows me to selectively manipulate multiple zones with one action would >be nice to have. This way I can quickly change the state of zones as >necessary to meet mine and my user?s needs. Right now the script I use is >crude and not very robust; I just stole the lslabels loop from clonebylabel >and wrapped zoneadm. After looking at Glenn?s script I see there is a better >approach by parsing tnzonecfg. So my question is this, should txzonemgr be >extended and a checkbox column added to it so someone can select multiple >zones for simultaneous state changes, sounds simple but the devil?s in the >details, or should it be a separate utility? Or is it a waste of time? I?m >leaning to a separate utility. Already txzoneadm is a busy script and >extending it may not be simple. Also I have seen many good, well thought out >scripts made useless and unmanageable by trying to make them do everything for >everyone. So I welcome your opinions and suggestions? First, would such a >script be worth while? Second, if such a script is worth while, should >Glenn?s script be extended or should it be a separate script? > > >This message posted from opensolaris.org >_______________________________________________ >security-discuss mailing list >security-discuss at opensolaris.org > > >
