|
|
|---|
<build_area>rpool/dc</build_area> |
The build area field specifies the area where the Virtual
Machine will be created. You can use the default area if it is
suitable for your system, or you can specify a different build area on
the host system.
Note - To use checkpointing to pause and resume during the build,
you must specify a ZFS dataset, or a mount point that correlates to
a ZFS dataset, as your build area. If the ZFS dataset does not
exist, it is created during the build. The ZFS pool that you specify,
however, must already exist.
|
<distro_constr_flags>
<stop_on_error>true</stop_on_error>
<checkpoint_enable>
true
</checkpoint_enable> |
Within the <distro_constr_flags> tag, the value of true for <stop_on_error>
means that, if an error occurs in the build, the distribution constructor stops
running. The value of true for <checkpoint_enable> gives you the ability to pause at
any specified steps, called checkpoints, when building the Virtual Machine, and to restart
the build at any specified checkpoints. For instructions, see Building an Image in Stages by Using Checkpoint Options. |
|
The finalizer section contains
a list of references to the finalizer scripts that are run when the
Virtual Machine is built. These scripts are used to customize the image and
are run in the order listed in this manifest. As shown in the following
script entries, each script field includes a required checkpoint field with a name
for the checkpoint. The checkpoint marks the stage during the Virtual Machine build
when this script is run. The checkpoint field also contains a checkpoint message.
When the script runs, the message will display. Each script also includes a field,
argslist, that provides any arguments that are required for that particular script to
run. You can edit these arguments as described in this table.
Note - The arguments are
provided within quotes. Do not remove the quotes. The quotes are used to
delineate each argument in the field.
|
<script name="/usr/share/distro_const/vmc/prepare_ai_image">
<checkpoint
name="prepare-image"
message="prepare bootable ai image"/>
<argslist>
<!-- Path to bootable AI image ISO -->
"/export/home/name_of_bootable_ai_image"
<!-- What AI client manifest to use for installation.
"default" will use the existing AI client manifest
included on the AI media. To use a custom
AI client manifest, provide a path to
your custom manifest -->
"default"
</argslist>
</script> |
In the prior section, you modified this
prepare_ai_image script reference to point to the AI image that you have
downloaded. You can, also, in this field, provide a pointer to a custom
AI client manifest. By providing a custom AI client manifest, you can change
the default installation specifications such as defining a particular installation target or changing the
list of packages to be installed with the operating system. Change the variable,
"default", to the path for your custom AI client manifest. The path will
be a file path on the system where you are running the distribution
constructor, as shown in this example. "home/user/mymanifest.xml" For instructions about creating a custom AI
client manifest, see Creating a Custom AI Manifest in Oracle Solaris 11 Express Automated Installer Guide . |
<script name="/usr/share/distro_const/vmc/create_vm">
<checkpoint
name="create-vm"
message="create and configure virtual machine"/>
<argslist>
"16000"
"1536"
"opensolaris"
</argslist>
</script> |
The create_vm script builds and configures the Virtual Machine. The
argslist field provides 3 arguments for the script. You can edit these arguments
as follows.
- Virtual machine disk size – The default is 16000 MB. Values between 12000 and 99.999.999 are valid.
Virtual machine ram size – The default is 1536 MB. Values between 1000 and 16,384 MB are valid. Virtual machine type – The default is opensolaris for a 32–bit Virtual Machine. Or, use opensolaris_64 for a 64–bit Virtual Machine.
Note - The create_vm script and its arguments affect the Virtual Machine specifically while
it is being created. See the post_install_vm_config script below for arguments that
affect the postinstallation Virtual Machine.
|
<script name="/usr/share/distro_const/vmc/install_vm">
<checkpoint
name="install-vm"
message="Boot and Install virtual machine"/>
</script> |
The install_vm script boots and installs the Virtual Machine in
the build area. |
<script name="/usr/share/distro_const/vmc/
post_install_vm_config">
<checkpoint
name="post-config"
message="Post installation virtual machine
configuration"/>
<argslist>
"1024"
"1"
"on"
</argslist>
</script> |
The post_install_vm_config script performs postinstallation configuration on the Virtual Machine. The
argslist field provides 3 arguments for the script. You can edit these arguments
as follows.
|
<script name="/usr/share/distro_const/vmc/export_esx">
<checkpoint
name="export-esx"
message="Export virtual machine for VMWare ESX"/>
<argslist>
"esx"
</argslist>
</script> |
The export_esx script converts the Virtual Machine into a set of ESX
files that are ready for import. If you want your Virtual Machine files
to be set up in ESX format, use this script. Otherwise, comment out
this script. For example, if you want to comment out the following field: <sample_script>example</sample_script> Enclose
it as follows: <!--
<sample_script>example</sample_script>
--> The ESX Virtual Machine will consist of a set of
files in the build_area/media/esx folder.
Note - If you use both the export_esx and export_ovf
scripts, identical Virtual Machines for each format are created.
|
<script name="/usr/share/distro_const/vmc/export_ovf">
<checkpoint
name="export-ovf"
message="Export virtual machine in OVF format"/>
<argslist>
"ovf"
</argslist>
</script> |
The export_ovf script converts the
Virtual Machine into a set of OVF files that are ready for import.
If you want your Virtual Machine files to be set up in
OVF format, use this script. Otherwise, comment out this script, so it will
not be run. The OVF Virtual Machine will consist of a set of
files in the build_area/media/ovf folder. |
