...
| Panel |
|---|
I wrote these instructions back in Feb 2008 and just dumped information this from my old Google Sites wiki. |
...
- SUNWtcpd (tcp_wrappers for network services)
- SUNWman (man pages)
Zone Packages
This has been production proven but I've only stayed with sparse zones (there are also full-root zones). Below is Since ~ Jan 2007 - Feb 2008 we've had production proven use of container technology. Before we used to hack "cloning" but since becoming a feature in build 33 (date?), I would say we are not cutting edge (rather than bleeding edge).
Note we've are comfortable with other types of zone, but our enterprise production proven use case has been sparse zones. As of this article, the technology is brand new so here is a quick excerpt,
The default zone filesystem model is called sparse-root. This model emphasizes efficiency at the cost of some configuration flexibility. Sparse-root zones optimize physical memory and disk space usage by sharing some directories, like /usr and /lib. Any updates and programs installed in the global zone (where all the other zones site) for the most part affect the sparse-root zones. Further, sparse-root zones have their own private file areas for directories like /etc and /var (this is where your service software like Apache Web Server go).
Whole-root zones increase configuration flexibility but increase resource usage. They do not use shared filesystems for /usr, /lib, and a few others. http://opensolaris.org/os/community/zones/faq/#basic_zonetypes. We do not use Whole-root zones as it increaes maintenance (more systems to update).
...