Installing SA Provisioning components on the Satellite host

Phase 1: Completing the installer interview

1. If you are installing the SA Provisioning components on the same host as the Satellite, invoke the installer again with the -c option. This specifies the CDF created by the interview when you installed the satellite component:
   # <distro>/disk001//opsware_installer/hpsa_add_satellite.sh -c /var/opt/opsware/install_opsware/cdf/cdf_<timestamp>.xml
2. At the Specify Satellite hosts prompt, add the IP or hostname of the server where you want to install the SA Provisioning components. If the IP/hostname of Satellite where you want to add the SA Provisioning components is already listed, press c to continue, otherwise press 1 to add it to the list of hosts:
   Specify Satellite hosts:
========================
Currently specified hosts:
<ip_address>
Please select one of the following options:
1. Add/edit host(s)
2. Delete host(s)
Enter the option number or one of the following directives
(<c>ontinue, <h>elp, <q>uit):

   
3. At the components prompt, select the OS Provisioning components to install:
   Host/Component Layout
=====================
1. Satellite [<ip_address>]
2. OS Provisioning Boot Server
3. OS Provisioning Media Server
Enter the number of the component or one of the following directives
(<c>ontinue, <p>revious, <h>elp, <q>uit): 2

4. Select the IDs of the components you want to install (OS Provisioning Boot Server and OS Provisioning Media Server) and assign each of them to a host:
   Host/Component Layout
=====================
1. Satellite [<ip_address>]
2. OS Provisioning Boot Server [<ip_address>]
3. OS Provisioning Media Server [<ip_address>]
Enter the number of the component or one of the following directives
(<c>ontinue, <p>revious, <h>elp, <q>uit): c

After all the components have been assigned to a host, press c to continue.

Phase 2: Installing the Satellite components

1. Before starting the installation, SA performs a prerequisites check to validate that the host on which you are installing SA meets the minimum requirements for the installation:
   
   • the required packages are installed
   • the required environment variables are set
   • sufficient disk space is available, and so on.
     
   For more information, see System requirements for installation
   If your host fails the prerequisites check, the installation fails with an error message that describes the problem. In this case, correct the problem and retry the installation. If you are unable to resolve the problem, contact HPE support services.
   If the prerequisites check completes successfully, you may still see some messages similar to the following:
   Prerequisite Checks
==============
Results for <IP_address>:

WARNING File system ‘/’ has 29447 MBytes available and 154050 is recommended.

Enter the option number or one of the following directives:
(<c>ontinue, <p>revious, <h>elp, <q>uit):

The prerequisites check identifies WARNINGs and/or FAILUREs. FAILUREs can cause a failed or incomplete installation. Resolve these issues before continuing the installation. WARNINGs allow you to continue the installation, however, core performance may be negatively affected if you continue without resolving them. If your server passes the prerequisite check, enter c and press Enter to start the installation.
2. In third-party certificate mode, SA installs the OCT (Opsware Cert Tool) component on the Satellite server before the Satellite installation begins. The OCT component will generate the Certificate Signing Requests (CSRs) for the certificates required for the current installation configuration. After OCT install, follow the following two additional steps before the SA installation begins:
   
   1. Enter the location where you want the OCT component to generate the *.csr files.

      Select path where to generate CSRs

      =============================

      Specify the path on the Model Repository server where SA will generate the CSR files

      [/var/tmp/csrFiles]:

      CSRs were generated in the /var/tmp/csrFiles directory on the server that hosts the Model Repository component [192.168.136.39].

      Please have them signed by your CA. You can resume the install process after all CSRs are signed.

      Make sure you copy all certificates in the same directory on the core's Model Repository server.

      You will be prompted for the path to this directory in the next step of the install process.

      Submit these files to your CA for signing and place the issued certificates in a folder of your choice.
      After generating the cryptographic material, SA places the CSRs created for that instance in a subfolder named by date. For example: csr_2017-05-02.08:21:05 csr_2017-05-02.08:22:10. Any new CSRs are placed in the dedicated folder that you provide during the installer interview.
      When providing the third-party certificates, make sure to follow the certificate format and naming requirements described in the SA certificates format.
      

   2. Provide the location where you have placed the custom certificates signed by your CA. The installer checks that the path is correct and that all required certificates are available.
      Enter the path to the directory containing the custom certificates.
===================================================================

      Path to the directory containing the certificates. [/var/tmp/certificateFiles]:
      SA now generates a new cryptographic material containing your signed certificates. The cryptographic material is then copied it on all hosts in the mesh.

When the Satellite installation completes, the installer displays a message indicating that the installation was successful.