Thank you, this is amazing! On Jun 3, 2011, at 2:35 PM, Ethan Quach wrote:
> With the push of: > > Author: Ethan Quach<ethan.qu...@sun.com> > Repository: /hg/caiman/slim_source > Latest revision: 6f7e708c38ec04faddbf6d0d8d3f0b0011c026f0 > Total changesets: 1 > Log message: > 16257 Support for zones configuration and installation should be included > in AI > 7041915 TransferFiles ICT should support transferring a directory that is > more than one level deep. > 7049824 System installed via AI ends up with incorrect mountpoints for > shared ZFS datasets > > > in build 167, the Automated Installer now supports specifying Zone > configurations in the AI manifest. These zones will be installed on your > system by a first boot smf service, "svc:/system/zones-install:default". > Once your global system is installed and booted, you can monitor the > state of installation of your zones by monitoring that smf service and/or > monitoring the output of "zoneadm list -cv". > > > 1. To specify zone configurations in your AI manifest, use the > new <configuration> tag specifying the zone's name, and the > source location of its zone config file (this is the output of > "zonecfg export"). The source location of the zone config > file can by located at any http:// or file:// location. The > following is an example of the default AI manifest with two > zone configurations specified: > > <auto_install> > <ai_instance name="default"> > <target> > <logical> > <zpool name="rpool" is_root="true"> > <filesystem name="export" mountpoint="/export"/> > <filesystem name="export/home"/> > <be name="solaris"/> > </zpool> > </logical> > </target> > <software type="IPS"> > <source> > <publisher name="solaris"> > <origin name="http://pkg.oracle.com/solaris/release"/> > </publisher> > </source> > <!-- > By default the latest build available, in the specified IPS > repository, is installed. If another build is required, the > build number has to be appended to the 'entire' package in the > following form: > > <name>pkg:/entire@0.5.11-0.build#</name> > --> > <software_data action="install"> > <name>pkg:/entire</name> > <name>pkg:/server_install</name> > </software_data> > </software> > > <configuration type="zone" name="zone1" > source="http://server/zone1/config"/> > <configuration type="zone" name="zone2" > source="file:///net/server/zone2/config"/> > > </ai_instance> > </auto_install> > > > These zones will get installed using a default AI manifest for > zones which will exist on the installed global zone system at: > > /usr/share/auto_install/manifest/zone_default.xml > > and a default SC profile, which will simply enable an interactive > tool to prompt for basic system configuration parameters upon > first boot of the zone. > > > > 2. To provide custom AI manifests and SC profiles for Zones, > add custom AI manifests and SC profiles into the same > installation service the global zone system is being installed > from, and use the new criteria "zonename" to associate them > with your zones. For example, > > # installadm add-manifest -f /tmp/zmanifest -n snv-167-svc \ > -c zonename="zone1 zone2" > > # installadm create-profile -f /tmp/z1profile -n snv-167-svc \ > -c zonename=zone1 > > # installadm create-profile -f /tmp/z2profile -n snv-167-svc \ > -c zonename=zone2 > > # installadm list -m -n snv-167-svc > Manifest Status Criteria > -------- ------ -------- > line1-netra2000 mac = 00:14:4F:2D:7A:DC > > zmanifest zonename = zone1 zone2 > > orig_default Default None > > > # installadm list -p -n snv-167-svc > Profile Criteria > ------- -------- > z1profile zonename = zone1 > z2profile zonename = zone2 > > > NOTE: zones differ from the global system in that if you do not > specify a custom manifest for the zone in the installation service, > a default manifest from the installation service is not selected. As > noted above, the zone installation will use the default zone AI > manifest from the installed global system in this default case. > > NOTE: the custom SC profiles you create for zones will not take > effect with build 167. In upcoming builds, zones will be converted > to using the new System Configuration model, after which time > these custom SC profiles specified for zones will actually be used > for zones. The general bug that tracks this is 7004790. > > > > Additional Changes: > ------------------------- > > 3. A general change to criteria is that any criteria that is not a > range-type may now be specified as a list of space separated > values, rather than just one value. A match of any one value on > the list is considered a match for that criteria. An example usage > of this can be seen in the above example which adds a manifest > with the zonename criteria being set for both zones "zone1 zone2". > This can also be used with the set-criteria subcommand: > > # installadm set-criteria -m zmanifest -n snv-167-svc -c zonename="zone1 > zone2 zone3" > > > Specifying criteria via an XML file also supports value lists. See > installadm(1M) for more information. > > > > 4. The location of the sample/default manifest files in a service's > imagepath is now changed to: > > /<imagepath>/auto_install/manifest/* > > A symlink for the default.xml file will exist from its old location > to this new location to preserve backwards compatibility with > previous AI servers. > > Also note, the AI manifest sample/default files delivered onto > the AI server has also moved to: > > /usr/share/auto_install/manifest/* > > > > 5. AI Server compatibility. > > Pre-167 AI servers may serve 167 AI services. However, if you > install zones using this 167 service, you will not be able to specify > custom zone AI manifests and SC profiles since the new 'zonename' > criteria is not supported on this server. Further more, because > this is an old AI server, it will provide the default manifest meant for > the global systems to each zone being installed. > > 167 AI servers will continue to be able to serve pre-167 AI services. > Note, if you have existing pre-167 AI services from before you > updated your system to build 167, trying to use the 'zonename' > criteria with these services will cause an error because this service's > manifest table doesn't contain the 'zonename' criteria. > > You should not be using the 'zonename' criteria with older services > since older AI boot image do not support installing zones. > _______________________________________________ > install-discuss mailing list > install-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-discuss _______________________________________________ install-discuss mailing list install-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/install-discuss
