OpenSolaris

Submit a Request for Feature Enhancement

Click here to submit a new feature enhancement.

Current Requests for Feature Enhancements

• Add zone accounting for capacity planning and charge back system.
• Convert zonemgr script into a Solaris package (SUNWzonemgr)
  containing the following:
  
         /usr/bin/zonemgr
         /usr/share/man/man1/zonemgr.1
         /usr/share/zonemgr/LICENSE
         /usr/share/zonemgr/usage.html
         Pre-requisite packages: SUNWzoner, SUNWzoneu, SUNWwgetr, SUNWwgetu

• Add localization support for manual page, usage info, and error messages.
• Add support for Solaris Trusted Extensions
        http://www.opensolaris.org/os/community/security/projects/tx/
        http://www.opensolaris.org/os/community/security/projects/tx/txzonemgr
        http://www.opensolaris.org/os/community/security/projects/tx/txnetmgr
• Add support for the new package minimization feature to make
  minimization much quicker. Excludes list of packages during zone creation instead of removing them after the zone is created. This feature is RFE (CR4963323). http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4963323 * Integration into N1 SPS. N1 SPS allows administrators to provision applications. N1 could provide a GUI-based front-end to Zonemgr to allow provisioning of JES applications within Zone Containers. This (combined with something like Anthony's EMRA toolkit) could be used to provide automated installations into multiple zones. * The Sun Cluster Product group has released an Agent for Solaris Containers (Zones). My thought was this significantly simplifies HA installations of JES. Rather than requiring the installation and configuration of each application's HA agent, you would simply configure an agent for the Container which has the JES application installed. On failover, the entire Zone would be failed over to the standby server. The JES applications would treat the failover condition as a reboot. This would serve the primary purpose of HA which is to protect applications from hardware faults. * All interfaces that may be used by zones are given an IPMP group name that matches the network number during the jumpstart installation. My script does not allow you to specify a physical interface, rather it looks at the address to be used and picks an interface for you based upon the IPMP group name. That is ( ip & netmask = ipmp_group ). If multiple interfaces exist in the IPMP group, it balances zones between interfaces. * I don't check to see if the IP is up because I may be pre-staging a zone for a "migration". I have instead re-written the zone boot script (/lib/svc/method/...) to only bring a zone up if it is not pingable. This script does some other magic too, such as setting up resource pools, default routes, etc. * Add GUI front end. * Add action to delete all zones but those specified to keep.