Installing and Configuring OpenStack (Juno) in Oracle® Solaris

Exit Print View

Updated: June 2016
 
 

Overview: Bare Metal Deployment With Ironic

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.

Element
Description
Example
driver_info/archive_uri
URI of Unified Archive with which the bare metal is provisioned.
http://host.example.com/sol-11_3-x86.uar
driver_info/ai_service
Name of the AI service to use
default-x86
driver_info/publishers
List of IPS publishers, separated by the plus (+) sign and using the naming format publisher-name@origin.
solaris@http://ipkg.us.oracle.com/solarisN/dev+userland@http://my.example.repo
driver_info/fmri
List of PKG FMRIs to install, separated by the plus (+) sign.
pkg:/group/system/solaris-small-server+pkg:/cloud/openstack/nova
driver_info/install_profiles
List of URIs of the configuration profiles to apply to the installation environment. The URIs are separated by the plus (+) sign.
http://host.example.com/profile1.xml+glance://glance-image
driver_info/sc_profiles
List of URIs of the System Configuration profiles to apply to the installed system. The URIs are separated by the plus (+) sign.
http://host.example.com/profile1.xml+glance://glance-image
driver_info/manifest
URI of the AI manifest to use to provision the bare metal.
http://host.example.com/my-manifest.xml
driver_info/ipmi_address
IP address or host name of the serial console to connect to the ILOM of the node to be provisioned.
192.168.2.200
driver_info/ipmi_username
User name for the IPMI connection.
root
driver_info/ipmi_password
Password for the IPMI connection.
password

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://


Note -  Even though Glance is typically used for storing install images, adding profiles to the storage is acceptable.

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.