Overview

Skill Level: Beginner

The Transformation Advisor is a free developer tool to help you quickly evaluate on-premise Java EE apps for deployment to the cloud. This recipe describes how to deploy Transformation Advisor onto ICP by using helm charts and persistent volumes.

Ingredients

  • IBM Cloud private 2.1.0.3 or later
  • Kubectl command line (Download it here)
  • Helm command line (This is optional, you can get it here)
  • Latest Transformation Advisor Helm Chart

Step-by-step

  1. Install IBM Cloud Private

    The first step is to install IBM Cloud private. The detailed instructions to do so can be found here. Transformation Advisor can be installed on either IBM Private Cloud or IBM Private Cloud CE edition.

    After completing installation, a url will be generated for you to access your cluster’s dashboard:

     Picture1

    Once you have installed IBM Cloud private, continue to step 2.

  2. Prerequisites for Transformation Advisor installation

    The Transformation Advisor is delivered as an interconnected set of pods and kubernetes services. It consists of three pods: server, ui and database.

    Minimum resources required

    resources

    Storage setup

    By default Transformation Advisor is configured to use dynamic provisioning. We strongly recommend that you use this option for your data storage.

    If you choose not to use dynamic provisioning you can change the default settings for a Persistence Volume (PV), an existing claim (PVC), or no storage at all. Please refer to the chart README for detailed instructions if you wish to setup Static Provisioning.

  3. Create a secret

    As of TA 1.8.0, you need to create a secret on ICP.

    Go to left menu side bar > Configuration > Secrets and hit the Create Secret button as illustrated below

    secret

    In the Secret, enter a name, which will be asked in the TA helm installation page. e.g. you can create a name called transformation-advisor-secret.

    Select the namespace to be the same one which your TA will be installed to. You may need to create a namespace of your choice first.

    Add two entries of data with names called db_username and secret respectively.

    The value of these values must be base64 encoded, and the raw values must have no space. There are many ways to get base64 encoded. e.g. In bash

    echo -n “this-will-be-my-secret-without-space” | base64
    # output: dGhpcy13aWxsLWJlLW15LXNlY3JldC13aXRob3V0LXNwYWNl
    # Please you user own secret value

  4. Install the Transformation Advisor Helm Chart via the UI

    Using IBM Cloud Private’s Catalog UI to deploy the chart.

    Open IBM Cloud Private, log in. On the menu bar on the top of the page select ‚ÄúCatolog‚ÄĚ.

    You can search for the chart or select it from the Tools Category on the right hand side

    Select the ibm-transadv-dev.

    catalogue

    A README is displayed. Click the ‚ÄėConfigure‚Äô button on the bottom right hand side.

    172

    The Configuration Screen is displayed.

    config

    Enter a release name in lowercase and select a namespace into which you want to install. Please note that Prior to TA 1.8, Transformation Advisor must be deployed in to the default namespace.

    Review the Licenses. Two licenses are presented. Review both and if happy to proceed accept the License terms.

    Picture9

    Picture10

    All optional and default paramaters are under the ‘All parameters’ expandable section which do not require any changes unless desired.

    The Quick Start section should be expanded and parameters specified.

    The Edge Node IP must be specified. This is the IP where you log in to ICP. Usually an edge server in the front of ICP, one of the ICP master nodes, or a loader balancer.

    Hit the install button.

  5. Verify the installation

    In ICP version 3.1 and later, once installation is complete go to the main menu and select Tools => Transformation

    The Transformation Advisor UI should be displayed in your browser

    welcome

7 comments on"Deploying IBM Cloud Transformation Advisor into IBM Cloud Private"

  1. Error creating: pods “transadv-ibm-transadv-dev-ui-64cdc48c5-” is forbidden: unable to validate against any pod security policy: [capabilities.add: Invalid value: “CHOWN”: capability may not be added capabilities.add: Invalid value: “DAC_OVERRIDE”: capability may not be added capabilities.add: Invalid value: “FOWNER”: capability may not be added

    Hello, got following error in the ReplicaSet creating:
    *****
    capabilities.add: Invalid value: “FSETID”: capability may not be added capabilities.add: Invalid value: “KILL”: capability may not be added capabilities.add: Invalid value: “SETGID”: capability may not be added capabilities.add: Invalid value: “SETUID”: capability may not be added capabilities.add: Invalid value: “SETPCAP”: capability may not be added capabilities.add: Invalid value: “NET_BIND_SERVICE”: capability may not be added capabilities.add: Invalid value: “NET_RAW”: capability may not be added capabilities.add: Invalid value: “SYS_CHROOT”: capability may not be added capabilities.add: Invalid value: “MKNOD”: capability may not be added capabilities.add: Invalid value: “AUDIT_WRITE”: capability may not be added capabilities.add: Invalid value: “SETFCAP”: capability may not be added]
    *******
    Any ideas, Thanks Jason Li

  2. jose@exisoft.com.pe January 17, 2019

    I can not deploy version 1.9.1 for problem with the pvc help please

  3. Hi NiallH, I have followed your instructions for deploying TA (1.9.1) on ICPEE (3.1). However, could have CouchDB Pod started and 1 deployment shown unhealthy on ICP dashboard. I realized auto provisioning did not work. I have created separate PV and PVC (static provisioning) and it got worked. Hope you include those steps here too. Thanks.

Join The Discussion