Best practices for IBM Software Hub administrators

If you are responsible for installing or maintaining IBM Software Hub, use the following tools and best practices to keep IBM Software Hub running smoothly and to resolve problems when they arise.

Pre-installation best practices

Cluster health

If your cluster is unhealthy, it can negatively impact the performance of IBM Software Hub. It is strongly recommended that you run the following commands before you install IBM Software Hub:

  • cpd-cli health cluster
  • cpd-cli health nodes
  • cpd-cli health network-performance

For more information, see Checking the health of your cluster before installing IBM Software Hub

Storage health

Storage is critical to the functionality of and performance of IBM Software Hub.

It is strongly recommended that you use storage that has been validated by IBM. If you plan to use different storage, ensure that you use the storage validation tool before you proceed with your installation. For more information, see the cpd-cli health storage-validation command reference.

In addition, you must ensure that your storage has sufficient IO performance, you can run the cpd-cli health storage-performance command before you install IBM Software Hub or as part of the IBM Software Hub installation.

Post-installation best practices

After you install IBM Software Hub, you can run the following commands to confirm that the instance is healthy:

You can run these commands after you install the IBM Software Hub control plane or after you install services.

Ongoing maintenance

Use the following resources to ensure that your IBM Software Hub is healthy: