Deploying a single server topology

You can deploy any of the IBM Storage Scale pattern configurations in a single server topology.

1. From the console, click Patterns > Virtual Applications.
2. Locate the IBM Storage Scale virtual application pattern that you created for a single server IBM Storage Scale Primary, Mirror, Tiebreaker, or Passive configuration.
3. In the Actions column of the Virtual Application Patterns table, click the Deploy the pattern into the cloud icon.
   The Deploy Pattern window is displayed, where you can configure the pattern before deploying it into the cloud.
4. Optional: To deploy a pattern instance with a different name than the original pattern name, replace the name in the Name field as needed.
5. The Select deployment environment section contains several parameters with default values that you can accept or change as needed for your environment. For more information, see the Related links.
6. Expand the Pattern Configuration section.
   This section contains additional IBM Storage Scale related parameters that you can configure if they were not defined and locked when the pattern was created. Expand the Configure unlocked component-level attributes subsection to display and modify these IBM Storage Scale parameters as needed. For more information on these IBM Storage Scale configuration parameters, see the Related links.

   Key Management

   You can change the IBM Storage Scale Managers Key, IBM Storage Scale Cluster Key, or the IBM Storage Scale Clients Key as needed. These keys that are specified for all IBM Storage Scale servers, have specific requirements. See the Related links for more information about configuring these settings during pattern creation.

   IBM Storage Scale Configurations

   You can change the type of IBM Storage Scale configuration, if needed, for this deployment, by selecting one of the following choices:

   • Primary Configuration
   • Mirror Configuration
   • Passive Configuration
   • Tiebreaker

   Number of IBM Storage Scale Node(s)

   If this deployment is for a Primary, Mirror, or Passive configuration, you can change the number of nodes for this deployment, if needed.

   Cluster Name

   If this deployment is for a Primary or Passive configuration, you can change the name of the Cluster for this deployment, if needed.

   Note: The cluster name specified when deploying a Passive configuration must be different from the cluster name specified for the associated Primary configuration.

   File System name for selected shared volumes

   You can change the name of the file system for this deployment, if needed.

   Attach to Shareable Volume by Name

   If you deploy a one GPFS node configuration, you should use block storage volumes to store data. For GPFS deployments with 3, 5, or 7 nodes, use block shared storage volumes instead, because these volumes must be shared and attached to all GPFS nodes in your configuration.

   You should have already created one or more block shared storage volumes if you are deploying a configuration with multiple GPFS nodes, or one or more block storage volumes for a single node GPFS deployment (for more information, see the Related links).

   The selection menu prompts you to select the right type of storage based on your deployment setting. As a result, if you deploy a one node configuration, you can select only from a list of available block storage volumes to be used by the IBM Storage Scale shared file systems. When you deploy a configuration with multiple nodes, you can select only from a list of available block shared storage volumes.

   Note that all of your selected storage volumes will be attached to each of the deployed IBM Storage Scale Server virtual machines.

   After deployment, you can update the list of storage volumes that are used by this configuration, by using the operations available under Manage > Operations > GPFS_Manager > Manage Storage Volumes. You can use these operations to attach new volumes to the existing IBM Storage Scale file system, or to a new file system, or to detach existing volumes.

   Any volumes that you attach must be newly created and cannot have been previously used or partitioned by other entities.

   Snapshot Interval

   If this deployment is for a IBM Storage Scale Primary configuration, you can change the frequency of snapshots taken of the file system for this deployment, if needed.

   Active Configuration (Mirror and Tie)

   If this deployment is for a IBM Storage Scale Primary configuration, you can change any IP addresses, if needed, to point to the IBM Storage Scale Manager virtual machine for a deployed Mirror Configuration and a deployed Tiebreaker Configuration. For this procedure, because we are deploying only a single server configuration, you should leave these IP address fields blank.

   Passive Configuration

   If this deployment is for a IBM Storage Scale Primary configuration, you can change the IP address, if needed, to point to the IBM Storage Scale Manager virtual machine for a deployed Passive Configuration. For this procedure, because we are deploying only a single server configuration, you should leave this IP address field blank.

7. Optional: Click Advanced Options to configure several additional options for your deployment, as needed.
   For more information on these advanced options, see the Related links.
8. Click Deploy to deploy your pattern and create an instance of the pattern in the cloud.