Standard Installation

CAUTION

If you are unable to install after attempting to remediate errors and warnings, contact Hewlett Packard Enterprise for support.

To perform a manual installation on the Controller host:

  1. Log into the host that you will be using as the Controller host using either the root account and password or your assigned username and password.
  2. If needed, copy the HPE Ezmeral Runtime Enterprise Enterprise binary (.bin) to the host that you will use as the Controller host.
  3. Make the .bin file executable by executing the command chmod a+x hpe-cp-<os>-<version>-<build>.bin, where:
    • <os> is the operating system supported by this .bin file. This can be either sles (for SLES) or rhel (for Red Hat Enterprise Linux).
    • <version> is the .bin version.
    • <build> is the specific .bin build number.
  4. Run the executable binary from the Linux console as the assigned user by typing ./<hpe_ezmeral>.bin <options>, where <options> is a list of one or more configuration option(s). See Installer Options and Examples, below.
    CAUTION
    See the top row of the Installer Options table for the --default-password OPTION.
    CAUTION
    If you want to install HPE Ezmeral Runtime Enterprise Essentials, see the second row of the Installer Options table for the --default-password <password> --tier essentials OPTION.
    CAUTION
    If you want to install HPE Ezmeral Runtime Enterprise, see the third row of the Installer Options table for the --default-password <password> --tier enterprise OPTION.
    CAUTION
    If you do not specify --tier option with --default-password, HPE Ezmeral Runtime Enterprise will be installed by default.
  5. The installer checks the integrity of the bundle and then extracts the bundle contents.
  6. The End User License Agreement (EULA) appears, if you have not used the -s or --skipeula option. Read through the EULA, pressing [SPACE] to page through the content. Once you have viewed the entire EULA, press [y] to accept it and continue the installation.
  7. HPE Ezmeral Runtime Enterprise installs on the Controller host. A series of messages appear during the installation. The following message appears once the installation is complete:
Successfully installed HPE CP.
Please visit https://10.50.1.1 to configure the server.
[root@hostname-1 ~] .

This concludes the first phase of the installation. Note the URL provided, as you will use this to continue the configuration. Proceed to Platform Controller Setup to continue via the web interface.

Installer Options

This table lists all of the Controller-specific options that can be used with the installation script. Not all of these options will apply in all situations.

Option Shortcut Description Notes Example 
--default-password
 Specify a default password. Specifies the default password for the admin and demo.user users that are created during the installation process. Failure to include this parameter will cause the default password for these users to be set to admin123. 
--default-password <password>  --tier essentials
 Install --tier must be specified with essentials to install HPE Ezmeral Runtime Enterprise Essentials 
--default-password <password>  --tier enterprise
 Install --tier must be specified with enterprise to install HPE Ezmeral Runtime Enterprise 
--proxy
 
-p

Proxy URL in the format

[protocol://]
                        [username:password@]
                        proxy_address[:port]
 Skip this option if no web proxy is being used for EPIC applications. See Web Proxy Requirements. 
--proxy https://admin:admin123@ 172.1.1.2:8080
--no-proxy-ips Comma-separated list of IP address that have been assigned for use by HPE Ezmeral Runtime Enterprise. See Web Proxy Requirements. --no-proxy-ips 127.0.0.1,172.16.1.10 
--no-ntp-config
 Optional. Specify this option to prevent the installer from modifying the NTP configuration. 
--worker-agent-install
 Worker hosts must be initialized manually before installing them via the web interface. ONLY USE THIS OPTION WHEN YOUR ENVIRONMENT DOES NOT ALLOW KEY-BASED SSH. SEE Configuration Requirements. 
--storagepolicy
 Optional. Storage policy to use for tenant storage. Click here for a list of supported storage policies (link opens a new browser tab/window). The --reportstoragetype option is REQUIRED when using this option. 
--storagepolicy ONE_SSD
 
--reportstoragetype
 Optional*. Allow the data node to report the storage type (either DISK or SSD. *This option is REQUIRED when using the --storagepolicy option, above. 
--storagepolicy ONE_SSD
 
--int-gateway-ip
 Internal gateway IP address for virtual nodes. This address cannot be used by another resource on the corporate network. See Network Requirements. Optional. If not specified, default value is 172.16.13.1 
--int-gateway-ip 172.1.1.1
 
SUDO_PREFIX
 Specify the actual sudo prefix to use when running privileged commands as a non-root user. Defaults to sudo -n if no other option provided. 
export SUDO_PREFIX="usr/sbin/dzdo/dzdo"
 
--ssl-cert
 SSL certificate to use for secure (https://) access to the web interface.

Do not use this option if you will be using non-secured (http://) access to the web interface.

If you expect to be creating and using Kubernetes clusters, then you must provide a previously-created and signed TLS Certificate and Key with Subject Alternate Names that indicate all IP Addresses (as IP Addresses), hostnames (as Domains), URLs (as Domains) and aliases (as Domains) that users expect to be able to use to access the installation. (A Kubernetes cluster can be created without specifying an SSL certification for your controller/gateway.) This encompasses all Controller hosts (Primary, Shadow, Arbiter), all Gateway hosts, and all Gateway sets, except in cases where gateway hosts and controllers have different certificates.

 
--ssl-cert /root/bds-https.cert
 
--ssl-priv-key
 SSL private key to use for secure (https://) access to the web interface. Do not use this option if you will be using non-secured (http://) access to the web interface. 
--ssl-priv-key /root/bds-https.pem
--ssl-ca-data Provide the CA authentication chain data required for having an SSL client authenticate the server certificate. This must be an absolute file path that will be readable by the httpd process. The “CA data” file is used for an openssl verify -CAfile command to ensure that an SSL client (such as those used in our k8s support) can validate the certificate. --ssl-ca-data <path>
--gateway-ssl-cert Provide the public-key SSL certificate for SSL termination in the gateway. If this is not provided, but the server certificate and private key are, these values will now default from those server certificate values (--ssl-cert and --ssl-priv-key). This must be an absolute path. --gateway-ssl-cert <path>
--gateway-priv-key Provide the private key corresponding to the above. This also must be an absolute path if given. --gateway-priv-key <path> 
--force
 
-f
 Force the installer to proceed despite any error(s) that may be encountered. USING THIS OPTION MAY RENDER HPE EZMERAL CONTAINER PLATFORM UNSTABLE AND/OR UNUSABLE, EVEN IF THE INSTALLER SEEMS TO COMPLETE SUCCESSFULLY. THIS IS AN ADVANCED OPTION THAT MUST ONLY BE USED WHEN THE CAUSE OF THE ERROR IS KNOWN AND PROCEEDING WITH THE INSTALLATION WILL NOT CAUSE ANY PROBLEMS. CONTACT HPE FOR SUPPORT BEFORE USING THIS OPTION. 
--skipeula
 
-s
 Optional. Skips displaying the End User License Agreement (EULA).
--controller-public-if Interface name to use for the Controller host. Use this option for a Controller installation if there are multiple interfaces present on the Controller with the same IP addresses assigned. --controller-public-if ens32

Examples

This section presents some examples of using the installer.

  • Root/Agent: This example installs HPE Ezmeral Runtime Enterprise as the root user and includes the Worker agent because password-less SSH is not available in the environment.

    # root@localhost> /root/hpe-cp-rhel-release-5.1-3010.bin --worker-agent-install

  • Root/non-Agent: This example installs HPE Ezmeral Runtime Enterprise as the root user. The environment does allow password-less SSH, and thus the --worker-agent-install option is not used.

    # root@localhost> /root/hpe-cp-rhel-release-5.1-3010.bin

  • Root/Agent/SSL: This example installs HPE Ezmeral Runtime Enterprise as the root user and includes the Worker agent because password-less SSH is not available in the environment. It also provides SSL information to enable secure (https://) access to the web interface.

    # root@localhost> /root/hpe-cp-rhel-release-5.1-3010.bin --worker-agent-install --ssl-cert /root/bdhost.cert --ssl-priv-key /root/bdhost.pem

  • Root/Non-Agent/SSL: This example installs HPE Ezmeral Runtime Enterprise as the root user. The environment does allow password-less SSH, and thus the --worker-agent-install option is not used. This example also provides SSL information to enable secure (https://) access to the web interface.

    # root@localhost> /root/hpe-cp-rhel-release-5.1-3010.bin --ssl-cert /root/bdhost.cert --ssl-priv-key /root/bdhost.pem

  • Non-root/Agent: This example installs HPE Ezmeral Runtime Enterprise as a non-root user and includes the Worker agent because password-less SSH is not available in the environment. To perform this action, login as the specific non-root user, for example "epic" in this case.

    # # epic@localhost> /home/epic/hpe-cp-rhel-release-5.1-3010.bin --worker-agent-install

  • Non-root/non-Agent: This example installs HPE Ezmeral Runtime Enterprise as a non-root user. The environment does allow password-less SSH, and thus the --worker-agent-install option is not used. To perform this action, login as the specific non-root user, for example "epic" in this case.

    # epic@localhost> /home/epic/hpe-cp-rhel-release-5.1-3010.bin

  • Non-root/Agent/SSL: This example installs HPE Ezmeral Runtime Enterprise as a non-root user and includes the Worker agent because password-less SSH is not available in the environment. It also provides SSL information to enable secure (https://) access to the web interface. To perform this action, login as the specific non-root user, for example "epic" in this case.

    # epic@localhost> /home/epic/hpe-cp-rhel-release-5.1-3010.bin --worker-agent-install --ssl-cert /home/epic/bdhost.cert --ssl-priv-key /home/epic/bdhost.pem

  • Non-root/non-Agent/SSL: This example installs HPE Ezmeral Runtime Enterprise as a non-root user. The environment does allow password-less SSH, and thus the --worker-agent-install option is not used. This example also provides SSL information to enable secure (https://) access to the web interface. To perform this action, login as the specific non-root user, for example "epic" in this case.

    # epic@localhost> /home/epic/hpe-cp-rhel-release-5.1-3010.bin --ssl-cert /home/epic/bdhost.cert --ssl-priv-key /home/epic/bdhost.pem