[zones-discuss] ZoneMgr 2.0.7 Released...

2010-06-05 Thread Brad Diggs
Hello All,Thanks again to all of the folks that have contributed bugs, fixes, new code and great ideas for the Zone Managerproject. Today, the final version 2.0.7 is now available atdl.thezonemanager.com. With the release of this version,I have officially deprecated and removed version 1.8.1. Version 2.0.7 includes many new features and bug fixes.Here is the list new features in version 2.0.7:* When adding a zone, add support for specifying autoboot, comment, and bootargs via -o option. As a result of this new feature, the -A feature for disabling autoboot has been depricated.* When adding or cloning a zone, if the root user password of the new non-global zone is not specified via -P or -E, the root user password of the global zone is inherited bythe new non-global zone.* Made sparse root filesystem list inherit default values from the contents of the /etc/zones/SUNWdefault.xml file of the global zone.* When creating a whole root zone, use /etc/zones/SUNWdefault.xml to determine what directories should be removed (un-inherited) from the zone configuration.* Added the ability to add and remove directory inheritance via -o "addDir|/dir1[|/dir2|...]" or -o "rmDir|/dir1[|/dir2|...]".* Addedd ability to delete a device from the non-global zone via -a modify -m "del|device|match_value".* Added support for modifying the default router.* Added support for FSS cpu shares with -p 'scpu|number'.* Added status action to list the status of all non-global zones. The status action shows the state of the zones, the number of frequency of CPUs visible within the zones, and the zone uptime information.* Saved JASS output into its own log file.* Added the ability to apply resource management controls immediately. This removed the need to reboot the zone when applying resource constraints.* Added support for multiple zonemgr invocations within a single input config file. Use 'newcmd' to delimit between zonemgr invocations.* Added support for comments within input config file.* Unified the file format and location of all artifacts. e.g. artifacts are files like output, log files, and configuration files. Each invocation of the zonemgr script results in the creation of a new folder in ${HOME}/.zonemgr/yearMonthDayHourMinuteSecond) where the folder name is the current date and time. All artifacts created for that invocation are stored in that directory.* With the addition of support for multiple zonemgr invocations as well as multiple zone actions, the artifacts have been broken out per action.* Provide option (-o keep_artifiacts) to keep and list of all artifacts created during the invocation of the zonemgr command. The default action is to remove all artifacts upon successful completion of the zonemgr.* Added new service management mode called 'jail'. This disables all but the very bare necessities including ssh to keep the zone running.* Added -o debug option to enable debuging.* Expanded the context of -n zonename to support multiple pipe delimited zone names. e.g. -n "zone1[|zone2|zone3|...]. This applies to nearly all actions. For example, now you can add 3 zones with zonemgr -a add -n "z1|z2|z3".* Enabled parallelization of select actions.* Removed requirement to speicfy a zone name by using a default zone name. If you run zonemgr without specifying a zonename (e.g. -n zonename), it will use a default zonename of zone where  is an incrementing number with prefixed zeros to keep the number four digits in length. This feature also finds the next available zone name in orderto avoid errors when creating a new zone. For example, if zones zone0001, zone0002, and zone0005 exist. When I add 3 new zones with -o "dCount|3", zonemgr will create zoneszone0003, zone0004, and zone0006.* Add the ability to name the prefix used by the default zone namer via -o "dPrefix|prefix". The default prefix is 'zone'. For example, if no zones exist with the prefix'mysql' exist, creating three new zones with the 'mysql' prefix via -o "dPrefix|mysql" -o "dCount|3" will result in three new zones named mysql0001, mysql0002, and mysql0003.* Simplified the service restart flag format to support both multiple invocations of -S svc as well as a single invocation with multiple svcs with a single -S "svc1[|svc2|svc3|...]" format.* Reformatted all of the documentation to conform to a 80 character width format.Here is the list of bugs fixed in version 2.0.7:* Updated all examples in documentation for new usage and new features.* Added exception update_hosts to not update /etc/hosts, if hosts are looked up rather than specified. e.g. 'hosts' specified rather than IP address.* Fixed bug where applying a swap resource control to a non-global zone failed because multiple swaps exist in global zone.* Fixed bug where zonecfg fails if TERM=xterm-color.* Fixed bug where lofi/lofs filesystems were forced to readonly even for -w.* Fixed bug where netservices was not found.* Fixed bug in ck4fs bug in check_fs.* Fixed bug where quotes of -m flag are being 

Re: [zones-discuss] how dynamic is your zones network configuration?

2010-06-05 Thread Mike Gerdts
On Sat, Jun 5, 2010 at 3:35 AM, Peter Tribble peter.trib...@gmail.com wrote:
 On Fri, Jun 4, 2010 at 6:38 PM, Edward Pilatowicz
 edward.pilatow...@oracle.com wrote:
 hey all,

 i had a quick questions for all the zones users out there.

 after you've configured and installed a zone with ip-type=shared (the
 default), how often do you change the network interfaces assigned to
 that zone via zonecfg(1m)?  frequently? infrequently? never?  only when
 moving from testing to production?  etc...

 Almost never.

 The only time I've ever done this was when a network interface on a
 machine failed
 and I had to use a different interface temporarily before the hardware
 was repaired.

 Mind you, I've always regarded it as a bug that you have to specify the 
 physical
 interface in the configuration rather than just assigning an address
 and letting the
 system find the correct interface for you.

I'm with you on this.  Since I wrote a tool to create and harden zones
(analogous to zonemgr), I added logic for it to automatically select
an appropriate interface.  My implementation relies upon each
interface being configured for IPMP with the IPMP group name set to
the network number.  Having this logic is very helpful when it comes
time to migrate zones between machines - I don't have to worry about
bge vs. e1000g, vs. ...

 That's for physical interfaces; I occasionally have to add extra IP
 addresses to a
 zone, using ifconfig to add them on the fly and zonecfg so they stick at boot.

Wouldn't it be nice to have an option in zonecfg or zoneadm to apply
the current configuration to the running zone?  That could be used for
adding/removing mounts, networks, resource controls, etc.

-- 
Mike Gerdts
http://mgerdts.blogspot.com/
___
zones-discuss mailing list
zones-discuss@opensolaris.org