| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-06-21 |
hpc-spectrum-symphony |
{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:external: target="_blank" .external} {:pre: .pre} {:tip: .tip} {:note: .note} {:important: .important} {:step: data-tutorial-type='step'} {:table: .aria-labeledby="caption"}
{: #getting-started-tutorial}
{{site.data.keyword.symphony_full}} enables customers to deploy HPC clusters that use {{site.data.keyword.symphony_full_notm}} as a scheduling software. The deployment is performed by using Terraform and {{site.data.keyword.bplong_notm}} as automation frameworks. The following steps outline the high-level flow of events that are performed:
- Create a workspace - with the Terraform code from {{site.data.keyword.bplong_notm}}. This step defines the set of configuration properties that are used to perform the automation.
- Generate a plan - to confirm whether the configuration properties are valid, so that when you run the Terraform code, all the resources are provisioned correctly. If the validation fails, fix the configuration properties and try again.
- Apply a plan - triggers the actual deployment of the {{site.data.keyword.cloud_notm}} resources to have an HPC cluster up and running by the time the deployment completes. If the deployment fails, identify the reason for failure, fix the problem, and try again. If a change is needed to the configuration properties, it might be better to generate a plan again.
If you decide to deploy your {{site.data.keyword.symphony_full_notm}} cluster through the {{site.data.keyword.cloud_notm}} catalog, when you click Install, the Generate Plan action is skipped, and the steps go from Create Workspace to Apply Plan directly. You need to enter values in the catalog that work for your permissions and {{site.data.keyword.cloud_notm}} account. If the deployment fails, the {{site.data.keyword.bpshort}} UI can be used to fix the errors, and you can retry the Apply Plan step. {: note}
Before you can deploy your {{site.data.keyword.symphony_short}} cluster, you need to create or gather some information. To get started, complete the following steps:
{: #generate-api-key} {: step}
Generate an API key for your {{site.data.keyword.cloud_notm}} account where the {{site.data.keyword.symphony_short}} cluster will be deployed. For more information, see Managing user API keys.
{: #create-ssh-key} {: step}
Create an SHH key in your {{site.data.keyword.cloud_notm}} account. This is your SSH key that you use to access the Symphony cluster. For more information, see Managing SSH keys.
{: #create-custom-image} {: step}
The offering provides a default set of images that you can use for the nodes within your HPC cluster. However, if you prefer to use your own custom images, documentation and scripts are provided to help you create them.
Worker Image: The default image that is specified in image_name acts as the worker image. This image is used to create the Symphony cluster nodes: management, management-candidates, and workers.
If you prefer to create the worker custom image with your own settings and configurations, follow the instructions that are provided here{: external}.
Storage Image: If you intend to use {{site.data.keyword.scale_short}} as shared storage for the cluster, the default image that is specified in scale_storage_image_name acts as the storage image. This image is used to create the {{site.data.keyword.scale_short}} storage cluster nodes. In addition to the base operating system, the image also includes the required {{site.data.keyword.scale_short}} software packages.
If you prefer to create the storage custom image with your own settings and configurations, follow the instructions that are provided here{: external}.
{: #gather-spectrum-entitlement-information} {: step}
The offering uses the Bring Your Own License (BYOL) model for Spectrum software when you deploy an HPC cluster on {{site.data.keyword.cloud_notm}}. This applies to {{site.data.keyword.symphony_full_notm}} in all cases and to IBM Spectrum Scale if you decide to use that for the HPC cluster storage instead of just NFS. Work with your business owners or license management team to make sure that your organization has procured enough licenses to deploy the HPC cluster using the Spectrum software. Failure to comply with licenses for production use of software is a violation of the IBM International Program License Agreement{: external}.
{: #getting-started-next-steps} {: step}
After you gather the necessary input values to define your cluster configuration, you are ready to deploy your {{site.data.keyword.symphony_full_notm}} cluster. The {{site.data.keyword.symphony_short}} cluster can be deployed on {{site.data.keyword.cloud_notm}} by using the {{site.data.keyword.cloud_notm}} catalog, {{site.data.keyword.bpshort}} CLI, or the {{site.data.keyword.bpshort}} APIs. If you want to deploy your cluster by using the CLI or API, review the prerequisites for your interface of choice:
- Setting up the {{site.data.keyword.bplong_notm}} CLI
- Setting up the {{site.data.keyword.bplong_notm}} API
After you create and gather your information and review for any additional prerequisites for your interface of choice, you are ready to begin Creating a workspace.