Chapter 2. Managing Fuse Online on OCP

Procedure

1. Create an OAuthClient resource with the following content and format:

   apiVersion: oauth.openshift.io/v1
   kind: OAuthClient
   grantMethod: auto
   metadata:
     name: ${CLIENT_ID}
   redirectURIs:
   - https://${ROUTE_HOSTNAME}/oauth/callback
   secret: ${SECRET}

2. In the OAuthClient resource:

   1. Replace ${CLIENT_ID} with a unique string that distinguishes a particular Fuse Online installation. For example, you might prefix the OpenShift namespace in which Fuse Online is installed: fuse-online-proj123456.

      Or, you might specify something like fuse-online-1. Typically, a name that indicates where the resource is used is most helpful. Then when an administrator lists OAuth clients, the purpose of each client is clear.

   2. Replace ${ROUTE_HOSTNAME} with the fully qualified hostname that is configured for the Fuse Online route. For example, fuse-online.mycorp.com.

   3. Replace ${SECRET} with a sequence of random alphanumeric characters that will be used to authenticate Fuse Online requests to OpenShift.

      For example:

   apiVersion: oauth.openshift.io/v1
   kind: OAuthClient
   grantMethod: auto
   metadata:
     name: fuse-online-1
   redirectURIs:
   - https://fuse-online.mycorp.com/oauth/callback
   secret: lFCbZTwrTOdZi1h86azxoixXkN7wnsUf3gjoSKbb

3. Run the following command to update the syndesis-oauthproxy DeploymentConfig resource:

   oc patch dc syndesis-oauthproxy --type json --patch "[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/args/1\", \"value\": \"--client-id=$CLIENT_ID\"}, {\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/args/2\", \"value\": \"--client-secret=$CLIENT_SECRET\"}]"

   When you installed Fuse Online, the installation script created the syndesis-oauthproxy DeploymentConfig resource. This oc patch command updates the resource so that its container arguments refer to the OAuth client ID and the OAuth secret defined in the new OAuthClient resource. For example, the updated resource looks like this:

   apiVersion: apps.openshift.io/v1
   kind: DeploymentConfig
   metadata:
     name: syndesis-oauthproxy
   spec:
     template:
       spec:
         containers:
         - args:
           - --client-id=fuse-online-1
           - --client-secret=lFCbZTwrTOdZi1h86azxoixXkN7wnsUf3gjoSKbb

Procedure

1. Download the package containing the Fuse Online installation scripts from the following location:

   https://github.com/syndesisio/fuse-online-install/releases/tag/1.7

   Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.7 directory contains the scripts and supporting files for upgrading Fuse Online.

2. Change to the directory that contains the extracted archive. For example:

   $ cd fuse-online-install-1.7

3. Log in to OpenShift with an account that has permission to upgrade Fuse Online. For example:

   $ oc login -u developer

4. Invoke the following command, which returns the name of the current project, to ensure that the current project is the project where Fuse Online is installed:

   $ oc project

   If you need to switch to the project where Fuse Online is installed then invoke the following command with the name of the OpenShift project that contains Fuse Online:

   $ oc project project-name

5. To check which version you are about to upgrade to, run the update script with the --version option, as follows:

   $ bash update_ocp.sh --version

6. Invoke the update script as follows:

   $ bash update_ocp.sh

   To learn more about the script, invoke $ bash update_ocp.sh --help.

   During and after an infrastructure upgrade, existing integrations continue to run with the older versions of Fuse Online libraries and dependencies.

7. Upgrade Fuse Online integrations that are running as follows:

   1. In Fuse Online, select the integration that you want to upgrade.
   2. Select Edit.
   3. Select Publish to republish the integration.

   Republishing the integration forces a rebuild that uses the latest Fuse Online dependencies.