At the end of this task, the OS provisioning software is installed on the OS provisioning server. In addition, the DHCP service is installed on the OS provisioning server.
For OS Provisioning servers that are running the Solaris OS, you must install the Java 2 SE 1.4.2 release on the system before you create the OS Provisioning server. The Java 2 SE 1.4.2 release must be located in, or linked to, the /usr/bin/java directory.
For OS Provisioning servers that are running RedHat Enterprise Linux, you must install the Java 2 SE 1.4.2 32–bit release and the DHCP RPM for your RedHat distribution on the system before you create the OS Provisioning server. The Java 2 SE 1.4.2 release must be located in, or linked to, the /usr/bin/java directory. If a 64–bit Java version is installed on the system, link /opt/SUNWn1osp/lib/libgridos.so to /opt/SUNWn1osp/lib/libgridos_rhel3_x86_64.so. Verify that the host name of the OS Provisioning server resolves to a primary interface on the system, and not a loopback address.
In the Common Tasks section of the N1 SPS browser interface, select OS Provisioning.
On the OS Provisioning Common Tasks page, click Create in the OSP Control Server section.
On the Plans Details page, click Run.
Choose variables to use for this plan.
To use an existing variables set, select a name from the drop-down menu in the Service component row of the Plan Parameters table.
To create a new variables set, click Select from List in the Service component row of the Plan Parameters table.
Click Create Set.
Type a name for the variables set.
Change variables as needed.
Variable Name |
Description |
---|---|
installPath |
Base directory into which to install the OS provisioning software. |
vhost_name |
Name of the virtual host that represents the OS provisioning server. |
host_dir |
Path to directory in which target host files reside. |
profile_dir |
Path to directory in which OS profile resides. |
subnet_dir |
Path to directory in which subnet files reside. |
logs_console_dir |
Path to directory in which logs and console files reside. |
run_provisioning_foreground |
Specifies whether to run the provisioning operation in the foreground. If you set this variable value to true, all deployments are run in the foreground. You cannot reset this value for individual deployments. Note – To enable this feature, you must disable locking of physical hosts, which is an unsupported configuration. For more information about how to disable physical locking of hosts, see Running Deployment Jobs in the Foreground. |
java_bin |
Path to the Java binary. |
dhcpd_bin |
Path to the DHCP daemon binary. |
sps_cli |
Location of the N1 SPS command line interface (CLI) binaries. Note – If you are using the OS Provisioning Plug-In 3.1 with the N1 SPS 5.1 release, you must edit this value to point to the location of the cr_cli directory in your environment. Do not accept the default value. |
Save the variables set.
Select the variables set that you just saved from the drop-down menu in the Service component row of the Plan Parameters table.
Select the host on which you want to create the OS provisioning server.
Click Run Plan (includes preflight).
This plan takes some time to run, usually approximately 15 minutes. While the installation is proceeding, click on the Details links in the Plan Run window to see progress.
To verify that the OS provisioning server is created successfully, click the Hosts link in the left side of the provisioning server window.
You should see the name of the virtual host appended with -osp. For example, if you installed on host masterserver, the virtual host is masterserver-osp.
In some environments, you might want to use your network's DHCP server rather than the ISC DHCP server that is created and started after you complete the previous procedure. If you want to disable the ISC DHCP server that is set up by the provisioning software, see Disabling the Plug-In Provided DHCP.
If your OS provisioning server is located on the same physical host as the boot and install server, you must configure the interfaces on the system before your provision any target hosts. The OS provisioning server does not automatically configure the interfaces of the boot and install server.