Deploying HCP for cloud scale software

Before you begin

Procedure

1. Establish a connection with the PXE nodes and manually configure networking on each node. Ensure that you can successfully SSH into all the nodes.

   ImportantThis step is applicable only for custom networking configuration. If you are using the 4-port or 2-port method, skip this step and go to step 3.

2. To initiate HCP for cloud scale on the PXE nodes, execute this script on the jump node. The script is located at /opt/hcpcs/hcpcsInstaller/csinstaller/start_hcpcs.sh.

   This process may take anywhere between 30 seconds to 5 minutes.

   After the script has successfully executed on all nodes, use SSH to log in to each individual node and perform the following verifications:

   1. Run docker ps and ensure that the watchdog service is running.
   2. Run systemctl status hcpcs.service.
   3. If the systemctl status hcpcs.service either shows as inactive or does not return anything and the watchdog service is not running, check the networking settings on that node.
   4. After you have resolved any networking issues, manually execute the custom_post_deploy.sh script. You can find this script in the root folder.
   ImportantThis step is applicable only for custom networking configuration. If you are using the 4-port or 2-port method, skip this step and go to step 3.

3. Run this script to deploy HCP for cloud scale software:

   /opt/hcpcs/hcpcsInstaller/csinstaller/jump_server_post_deploy.sh [-h] -i <frontend_ip> -I <backend_ip> -m <master_frontend_ips> -M <master_backend_ips>

   For example:

   /opt/hcpcs/hcpcsInstaller/csinstaller/jump_server_post_deploy.sh -i 172.168.10.1 -I 172.168.20.1 -m 172.168.10.1,172.168.10.2,172.168.10.3 -M 172.168.20.1,172.168.20.2,172.168.20.3 -c 172.168.10.0/24 -C 172.168.20.0/24

   NoteThe script installs Docker-CE, applies security updates, configures the firewall, and deploys HCP for cloud scale software. For the rest of the nodes, these steps are automated as part of the boot process.

   Option	Description
   -h	(Optional) Displays command syntax.
   -i <frontend_ip>	The front-end IP address of the installation master node.
   -I <backend_ip>	The back-end IP address of the installation master node.
   -m <master_frontend_ips>	The front-end IP addresses of the HCP for cloud-scale master nodes as a comma-separated list.
   -M <master_backend_ips>	The back-end IP addresses of the HCP for cloud-scale master nodes as a comma-separated list.
   -c <frontend_cidr>	The front-end network CIDR of the cluster.
   -C <backend_cidr>	The back-end network CIDR of the cluster.

   After successful completion, you see the following message and the microservices admin application is launched:

   Successfully ran security hardening script 
   Successfully completed all post deploy actions

4. Connect to the external IP address of the server.

   For example:

   https://10.0.0.1:8000

   You see the HCP for cloud scale application's welcome page. Accept the certificate and enter a new password for the administrator.

   NoteAdministrator is the only local user. You must use either Active Directory or LDAP services to create additional users.

5. Click Continue.

6. In the Cluster hostname/IP Address field, enter the host name and then click Continue.

   You see the Instance Discovery page.

7. Accept the default service port and network assignments and then click Continue.

   Service deployment takes several minutes to complete. You see a progress bar showing the progress. When the deployment is complete, you see a Set Up completed message.

8. Click Finish.

9. Run this script to remove residual files: /opt/hcpcs/hcpcsInstaller/csinstaller/cleanup_artifacts.sh.

   This script removes all installer packages, files, and directories, and disables and removes the TFTP service. It also disables and stops the NFS and DHCP servers but does not remove them.

   If the installation failes, you can restart it. To restart a failed installation, see Restarting a failed installation.

Parent Topic

• Using the cluster deployment tool