Deploying shared services in a multisystem environment

Shared service deployments to a multi-cloud environment profile that could contain multiple cloud groups configured across multiple systems are supported.

Before you begin

To view shared services, you must be assigned either the Workload resources administration with Full permission or the cloud administrator role.

About this task

These steps are specific to shared services deployed in a multisystem environment. You can use the console or the command line interface to complete this task. For the command line information, see the Related information section.

If you deploy to a multi-cloud environment profile, the shared service instance is scoped at the environment profile level. The shared service can be used by application deployments in all cloud groups in that environment profile. Application deployments in other a multi-cloud environment profiles do not have access to the shared service.

If you do not want to deploy the shared service and consume virtual machine resources in every multi-cloud environment profile you want to use it in, you can deploy it once in a multi-cloud environment profile and then make that deployed instance available in other multi-cloud environment profiles. If you deploy to a multi-cloud environment profile and also choose to make the shared service available in other multi-cloud environment profiles, the shared service is scoped at the environment profile level in each environment profile it is deployed and made available in. The shared service can be used by application deployments in all cloud groups in all environment profiles the shared service is deployed and made available in. Note that external shared services (with no virtual machines) do not support this feature since deploying them do not consume any virtual machine resources.

The following shared services support availability across multi-cloud environment profiles:
  • Caching shared service
  • On Demand Router based Load Balancer
  • IBM® Endpoint Manager Service
  • System Monitoring shared services

Procedure

  1. Click Patterns > Shared Services. If you are on 2.3.3.3 or later, click Patterns > Provision > Shared Services.
  2. Select the shared service for deployment.
  3. Click Deploy in the toolbar to configure the following general properties for the shared service.
    Name
    Shows the name of the shared service.
    Environment Profile
    Select the environment profile used to control aspects of your deployment.
    Operating system family
    Select the operating system family to use when deploying the shared service.
    Note: Only Linux® is supported at this time. Windows is not a supported operating system family for shared services.
    Base image
    Select the Base image to use for the deployment.
    Note: Only images with an operating system that is supported by the shared service are displayed in the list.
    SSH key
    To upload a public key so that you can connect to the deployed virtual machines using SSH, complete the SSH section and specify the SSH public key. If you do not have an existing SSH key pair, you can generate one that can be reused with other deployments. Click Generate. The SSH Key field populates with the generated public key. Select Click here to download the file containing the private key and save the private key to your local system.

    By downloading and saving the key, you can access your virtual machines even if the appliance loses connectivity or encounters problems.

  4. Configure the properties specific to the shared service. The configuration information you will provide varies depending on the shared service you are working with. For more information about each shared service and their properties, see the deployment procedure in Table 1.
    Table 1. Shared service deployment procedures
    Shared service Deployment procedure
    Caching shared service Deploying the Caching shared service in a multisystem environment
    Elastic load balancing (ELB) proxy shared service Deploying an ELB proxy shared service in a multisystem environment
    IBM Endpoint Manager Service Deploying the IBM Endpoint Manager Service in a multisystem environment
    System Monitoring shared service Deploying a System Monitoring shared service in internal mode

    Deploying a System Monitoring shared service in external mode

    System Monitoring for DataPower® shared service Deploying the System Monitoring for DataPower service in a multisystem environment
    System Monitoring for Db2® Application Server service Deploying the System Monitoring for Db2 Application server service in a multisystem environment
    System Monitoring for HTTP Servers service Deploying the System Monitoring for HTTP Servers service in a multisystem environment
    System Monitoring for Liberty server service Deploying the System Monitoring for Liberty server service in a multisystem environment
    System Monitoring for WebSphere® Application server service Deploying the System Monitoring for WebSphere Application server service in a multisystem environment
    System Monitoring for WebSphere Message Broker service Deploying the System Monitoring for WebSphere Message Broker service in a multisystem environment
    System Monitoring for WebSphere MQ service Deploying the System Monitoring for WebSphere MQ service in a multisystem environment
  5. When you are finished configuring all of the fields on the Configure tab:
    • If you chose an environment profile that does not have the IP addresses provided by field set to Pattern Deployer and you do not want to modify the placement, click Quick Deploy. If you choose this option, the deployment process starts. You do not need to complete any of the subsequent steps.
    • If you chose an environment profile that has the IP addresses provided by field set to Pattern Deployer, or you want to modify the placement, click Prepare to Deploy.

On the Distribute pane:

The virtual machines in the deployment are placed in cloud groups by the system.

  1. Optional: To modify the placement of the virtual machines, drag the virtual machines to different cloud groups.
    • If you drag a virtual machine cell that contains more than one virtual machine, you are prompted to select the number of virtual machines that you want to move. You must select the number from the list in the dialog. After you move a virtual machine to a different cell, the IP group assignments are set to default values. If needed, you can edit the virtual machine network settings in the next step to modify the IP group.
    • If you modify the placement of the virtual machines, the new placement is validated to ensure that the necessary resources and artifacts are available in the selected cloud group.
    • If there is a problem with the placement, a message is displayed. Resolve the issue with the placement before you continue.

      For example, if this message displays when you modify the placement: CWZKS7002E Insufficient memory to place the pattern, move the virtual machine to a different cloud group with sufficient memory resources for the pattern.

      If you see the error: Unable to assign to cloud group, there is an error with the location, cloud group, NIC or IP groups for the cell where the error is displayed. If this error message occurs, you must resolve the issue with that cell before you are allowed to drag a virtual machine to that cell for placement there. Move the mouse pointer over the error to display more details about the problem in a window.

  2. Optional: To edit the network or volume settings for a virtual machine, move your mouse pointer over the virtual machine icon and click the pencil icon.
    1. On the IP Groups tab, you can modify the IP group for each of the NICs in the virtual machine. The IP groups that are listed are the IP groups that are associated with the environment profile that you chose for the deployment.
    2. If you are deploying the IBM General Parallel File System (IBM Spectrum Scale) Pattern, you can modify the volumes for the virtual machine on the Volumes tab.
    3. Click OK when you are finished updating the settings.
  3. When you are finished modifying the settings, click Deploy.
  4. View the details of the deployed shared service on the Shared Service Instances page.
    The details include a list of virtual machines that are provisioned on the cloud infrastructure for that deployment, the IP address, virtual machine status, and middleware status.