Table of contents

Obtaining the installation files

Before you install Cloud Pak for Data, ensure that the installation files are available on your client system.

Before you begin

Ensure that you have:
  • Your entitlement license API key from the Container software library on My IBM and your IBM ID.
    After you order IBM® Cloud Pak for Data, an entitlement key for the software is associated with your My IBM account. To get the entitlement key:
    1. Log in to Container software library on My IBM with the IBM ID and password that are associated with the entitled software.
    2. On the Get entitlement key tab, select Copy key to copy the entitlement key to the clipboard.
    3. Save the API key in a text file.
  • A Linux or Mac OS client workstation to run the installation from. The workstation does not have to be a node of the cluster, but must have internet access and be able to connect to the Red Hat® OpenShift® cluster.

Procedure

  1. Obtain the installation files:
    1. On the Linux or Mac OS workstation, download the appropriate file from cpd-cli GitHub:
      Edition TAR file
      Enterprise Edition cloudpak4data-ee-3.0.1.tgz
      Standard Edition cloudpak4data-ste-3.0.1.tgz
    2. Extract the contents of the TAR file:
      tar -xvf cloudpak4data*.tgz
      A bin folder is created in the current directory with the cpd command binaries and a repo.yaml. After you extract the contents of the TAR file, you can delete it from your file system to save space.
  2. Set up the requirements for the cpd command:
    1. On the same workstation, download and extract either the Linux or Mac OS oc client tools that match your OpenShift version from the Get Started with the CLI 3.11 or Getting started with the CLI 4.5 web site.
      The oc command is required for the cpd command to succeed.
    2. Edit the repo.yaml server definition file that you downloaded.
      This file specifies the repositories for the cpd command to download the installation files from. Make the following changes to the file:
      Parameter Value
      username Specify cp.
      apikey Specify your entitlement license API key.
    3. Some services are hosted in separate repositories. If you plan to install any of the services listed in the following table, add the appropriate entries the repo.yaml file:
      Service Entry in repo.yaml Details
      Guardium® External S-TAP® Append the following entry to the registry section of the repo.yaml file:
        - url: store/ibmcorp
          username: Docker_ID
          apikey: Docker_access_token
          name: estap-registry
      Replace the following values:
      Docker_ID
      Specify your Docker ID.
      Docker_access_token
      Specify your Docker access token.

      You can use an existing access token or create an access token specifically for the repo.yaml file. Your access tokens are listed on the Docker Account Settings > Security page.

      Watson™ Assistant Append the following entry to the registry section of the repo.yaml file:
        - url: cp.icr.io
          username: "cp"
          apikey: entitlement-key
          namespace: "cp/watson-assistant"
          name: wa-registry
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
      Watson Assistant for Voice Interaction Append the following entry to the registry section of the repo.yaml file:
        - url: cp.icr.io/cp
          username: cp
          apikey: entitlement-key
          name: voice-gateway
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
      Watson Discovery Append the following entry to the registry section of the repo.yaml file:
        - url: cp.icr.io
          username: cp
          apikey: entitlement-key
          namespace: "cp/watson-discovery"
          name: watson-discovery-registry
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
      Watson Knowledge Studio Append the following entry to the registry section of the repo.yaml file:
        - url: cp.icr.io
          username: cp
          apikey: entitlement-key
          namespace: "cp/knowledge-studio"
          name: wks-registry
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
      Watson Language Translator Append the following entry to the registry section of the repo.yaml file:
         - url: cp.icr.io
           username: cp
           apikey: entitlement-key
           namespace: "cp/watson-lt"
           name: lt-registry
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
      Watson Speech to Text or Watson Text to Speech Append the following entry to the registry section of the repo.yaml file:
        - url: cp.icr.io
          username: cp
          apikey: entitlement-key
          namespace: "cp/watson-speech"
          name: spch-registry
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
      Edge Analytics Append the following entry to the registry section of the repo.yaml file:
        - url: x.y.z
          username: cp
          apikey: entitlement-key
          namespace: "cp/edge"
          name: edge-analytics
      Replace entitlement-key with the same entitlement license API key that you specified for the default registry in the repo.yaml.
  3. Save the file.