README.html

<h1>OmniOS Packer Templates</h1>

<p>Creates a vagrant base box for OmniOS.</p>

<h2>How to Build</h2>

<p>Run using <code>packer build templates/&lt;release&gt;.json</code> from the omnios-packer
directory (necessary so that the relative paths for post-install scripts will
be valid).</p>

<h2>Templates</h2>

<p>The <code>templates/</code> subdirectory contains individual JSON templates for every
OmniOS release. When building a base box for a new OmniOS release, you should
copy the latest template to a new file, named for the release you are adding.</p>

<p>Do not simply change an existing template in-place, as doing so will make it
more cumbersome to rebuild a previous release's basebox in the event we need
to do so for any reason (critical fixes to a previously published basebox).</p>

<h3>Notes</h3>

<ul>
<li>A single ZFS pool (rpool) is created for the entire disk</li>
<li>The omniti-ms publisher is added by default</li>
<li>The VM is set to have 1024MB of RAM and a 40GB drive</li>
</ul>

<h2>Internal OmniTI Baseboxes</h2>

<p>In addition to the templates for baseboxes intended for public consumption,
this repository contains templates for largely internal-only use baseboxes.
These exist as separate templates because some of our internal projects have
additional configuration requirements that aren't appropriate or useful for
public users of OmniOS (e.g. data pools, slightly higher default memory
allocations, etc.).</p>

<p>These templates may not be updated for every release of OmniOS, as they are
typically only built on an as-needed basis.</p>

<p>They are located in the appropriate <code>templates/&lt;project&gt;/</code> subdirectories.</p>

<h3>Notes</h3>

<p>In addition to the configurations used by the default/public templates, the
project specific templates generally provide the following extras:</p>

<ul>
<li>Additional virtual disk attached to VM</li>
<li>A second ZFS pool (data) created using entire disk</li>
<li>VM memory increased to 2048MB</li>
<li>The omniti-perl publisher is added by default</li>
</ul>

<h2>Post-install Scripts</h2>

<p>The <code>scripts/</code> subdirectory contains additional scripts which are used by
some of the templates for post-install configuration. They are not tied to
specific OmniOS releases and are each used by several templates, as they
contain common configuration functionality.</p>