Chapter 2. Managing Fuse Online on OCP

Procedure

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

   $ oc login -u developer -p developer

2. Switch to an OpenShift project in which Fuse Online is running. You are enabling discovery for only this project. For example:

   $ oc project my-fuse-online-project

3. Invoke the oc patch command on the syndesis custom resource and provide the URL for the 3scale user interface. In the following sample command, replace 3scale-url-here with the actual URL for your 3scale user interface:

   oc patch syndesis app --type='merge' -p '{"spec":{"components":{"server":{"features":{"managementUrlFor3scale":"3scale-url-here"}}}}}'

4. Optional. To confirm that discovery is turned on for the project that you switched to, invoke the following command:

   oc describe dc/syndesis-server

   When discovery is turned on, the output from this command shows that the OPENSHIFT_MANAGEMENT_URL_FOR3SCALE environment variable is set to the URL that you specified in the oc patch command.

Procedure

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

   $ oc login -u developer -p developer

2. Switch to an OpenShift project in which 3scale discovery was enabled. For example:

   $ oc project my-fuse-online-project

3. Invoke the oc patch command on the syndesis custom resource and set the URL for the 3scale user interface to the empty value:

   oc patch syndesis app --type='merge' -p '{"spec":{"components":{"server":{"features":{"managementUrlFor3scale":""}}}}}'

   This command updates the syndesis custom resource. The update disables the OPENSHIFT_MANAGEMENT_URL_FOR3SCALE environment variable. This change to the syndesis custom resource triggers the syndesis-operator, which is responsible for installing Fuse Online, to redeploy syndesis-server. The new default behavior is that APIs are no longer exposed for discovery in 3scale.

   Do not edit the syndesis-server DeploymentConfig object to set the OPENSHIFT_MANAGEMENT_URL_FOR3SCALE environment variable. This does not work because the syndesis-operator reverts your change. The syndesis-operator ensures that Fuse Online is deployed only and always according to the syndesis custom resource.

4. Republish any API provider integration that had discovery enabled and that was created in the project in which you just disabled discovery.

   In other words, you do not need to republish an API provider integration if you disabled discovery of that integration’s API while discovery was enabled for the project in which the API provider integration was created.

Procedure

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

   $ oc login -u developer -p developer

2. Ensure that the current project is the project in which Fuse Online is running. To view the current project:

   $ oc project

3. Edit the syndesis custom resource:

   1. Invoke the following command, which typically opens the resource in an editor:

      oc edit syndesis

   2. Add the following lines to the end of the resource:

      spec:
        demoData: true
        addons:
          todo:
            enabled: true

   3. Save the resource.

      Saving this change to the syndesis custom resource triggers the syndesis-operator, which is responsible for installing Fuse Online, to redeploy syndesis-server.

4. Confirm that the redeployed server provides the sample data:

   1. Display the Fuse Online console in a browser.
   2. In the left navigation panel, click Connections.
   3. Confirm that the PostgresDB connection appears.

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.8

   Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.8 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.8

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.

Procedure

1. If you did not already download the package that contains the Fuse Online installation scripts, download it now from the following location:

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

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

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

   $ oc login -u developer -p developer

4. Ensure that the current project is the project into which you want to install Fuse Online. To view the current project:

   $ oc project

5. In the directory in which you downloaded the installation script, run it to obtain the syndesis custom resource, which you will edit in a subsequent step.

   $ bash install_ocp.sh

6. Obtain the syndesis custom resource as a YAML file:

   oc get syndesis app -o yaml > syndesis.yaml

7. Edit syndesis.yaml to increase the volumeCapacity parameter setting. For example:

   apiVersion: "syndesis.io/v1alpha1"
   kind: "Syndesis"
   metadata:
     name: "app"
   spec:
     components:
       db:
         resources:
           volumeCapacity: 10Gi

8. Save the edited syndesis resource with a new name, for example, custom-syndesis.yaml.

   OpenShift copies the new volumeCapacity value to a PersistentVolumeClaim object.

   Warning

   Do not invoke the next command in a Fuse Online environment in which there is any data, such as connections and integrations, that you do not want to delete. The command in the next instruction removes data for all Fuse Online objects in this Fuse Online environment.

9. Remove Fuse Online data by running:

   oc delete syndesis app

10. Create a new syndesis custom resource that configures the increased volume capacity. In the command line, specify the .yaml file in which you updated the volumeCapacity setting. For example:

    oc create -f custom-syndesis.yaml