With the Ironic solaris driver, you can provision a bare metal node by using either Oracle Solaris's Unified Archive (UAR) feature or its Image Packaging System (IPS). When you create a node, you would pass information to the solaris driver by means of configurable node elements.
The following table lists the elements for creating nodes. The driver_info/archive_uri element applies to provisioning nodes with a UAR file. The remaining elements in the table apply to provisioning nodes by using IPS.
If you provision a node by using a UAR file, you only need to provide the information for driver_info/archive_uri. The archive URI can use one of the schemas in the following list. The same schema options apply to specifying profiles if you opt to provision the node by using IPS.
file://
http://
https://
glance://
If you provision a node by using IPS, ensure first that at least a default AI service for your node's architecture exists, as shown in the following example:
# installadm list Service Name Status Arch Type Alias Aliases Clients Profiles Manifests ------------ ------ ---- ---- ----- ------- ------- -------- --------- default-i386 on i386 pkg yes 0 0 0 1 default-sparc on i386 pkg yes 0 0 0 1 ironic-x86 on i386 pkg no 0 0 0 1 ironic-sparc on i386 pkg no 0 0 0 1 # installadm list -vcn ironic-x86 There are no clients configured for service 'ironic-x86'. # installadm list -vmn ironic-x86 Service Name Manifest Name Status Criteria ------------ ------------- ------ -------- ironic-x86 orig_default default none ironic-sparc orig_default default none
When you use IPS to provision nodes, specifying the driver_info/ai_service is optional. If you omit the name of the AI service, the default AI service for that node's architecture is used.
If you specify custom packages for driver_info/fmri, you must also specify publishers for the driver_info/publishers element.