Chapter 3. Changing the configuration of a Fuse Online environment

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 the OpenShift project that is running the Fuse Online environment whose configuration you want to change. For example:

   oc project my-fuse-online-project

3. Optional. Create a backup copy of the current settings in the syndesis custom resource, just in case you update and save incorrect content. For example, invoking the following command saves a backup in the syndesis_app_backup.yml file:

   oc get syndesis app -o yaml > syndesis_app_backup.yml

4. Invoke the following command to open the syndesis custom resource in an editor:

   oc edit syndesis/app

   Note: This procedure describes how to set configurations by opening the custom resource file in an editor. Alternatively, you can use oc patch commands to edit the custom resource.

5. Edit the syndesis custom resource as needed.

6. Save the resource.

   Depending on the type of object that your edits apply to, your update triggers the syndesis-operator to redeploy some Fuse Online components when you save the resource.

7. Wait two or three minutes, and then confirm that the syndesis custom resource was updated correctly:

   1. Invoke the following command to display the content of the syndesis custom resource:

      oc describe syndesis/app

   2. Check the content.

      If the syndesis custom resource does not contain the settings that you need, edit it again to specify valid settings.

Procedure

1. Use the oc patch command with the following syntax to configure tolerations settings. Specify infraScheduling for Fuse Online infrastructure component deployments or integrationScheduling for Fuse Online integration deployments:

   oc patch syndesis/app --type=merge -p '{"spec":{"infraScheduling"|"infraScheduling":{"tolerations":[{"key":"_value1_","operator":"_value2_","effect":"_value3_"},{"key":"_value4_","operator":"_value5_","effect":"_value6_"}]}}}'

   For example, the following command adds tolerations for Fuse Online infrastructure components:

   oc patch syndesis/app --type=merge -p '{"spec":{"infraScheduling":{"tolerations":[{"key":"tol_1","operator":"Equal","effect":"NoSchedule"},{"key":"tol_2","operator":"Equal","value":"value2","effect":"NoSchedule"}]}}}'

2. Use the oc patch command with the following syntax to configure node affinity settings. Specify infraScheduling for Fuse Online infrastructure component deployments or integrationScheduling for Fuse Online integration deployments:

    oc patch syndesis/app --type=merge  -p '{"spec":{"infraScheduling"|"infraScheduling":{"affinity":{"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"weight":_value1_,"preference":{"matchExpressions":[{"key":"_value1_","operator":"_value2_","values":["_value3_","_value4_"]}]}}]}}}'

   For example, the following command sets nodeAffinity to both Fuse Online infrastructure components and integrations:

    oc patch syndesis/app --type=merge  -p '{"spec":{"infraScheduling":{"affinity":{"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"weight":11,"preference":{"matchExpressions":[{"key":"_affinity","operator":"In","values":["foo","bar"]}]}}]}}},"integrationScheduling":{"affinity":{"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"weight":22,"preference":{"matchExpressions":[{"key":"my_affinity2","operator":"In","values":["foo","bar"]}]}}]}}}}}'

3. To remove a configuration setting, use the remove option in the oc patch command, as demonstrated in the following example commands:

   • The following example command removes the preferredDuringSchedulingIgnoredDuringExecution setting from a nodeAffinity for Fuse Online integrations:

     oc patch syndesis/app --type=json -p '[{"op": "remove", "path": "/spec/integrationScheduling/affinity/nodeAffinity/preferredDuringSchedulingIgnoredDuringExecution" }]'

   • The following example removes the tolerations from Fuse Online infrastructure components:

     oc patch syndesis/app --type=json -p '[{"op": "remove", "path": "/spec/infraScheduling/tolerations" }]'

Procedure

1. Open the custom resource in an editor:

   If you have already installed Fuse Online, open the custom resource by following the steps in “General procedure for changing Fuse Online configuration.

   If you have not yet installed Fuse Online, open the custom resource by following the steps in these topics, depending on your OCP version:

   • For OCP 4.x: Adding a Fuse Online instance to an OpenShift 4.x project
   • For OCP 3.11: Editing the default custom resource file before installing Fuse Online

2. For the syndesis-server and syndesis-meta components, set the Java Options (javaOptions) parameter and specify values for the HTTP proxy host and port. Use the same HTTP proxy values for both syndesis-server and syndesis-meta.

   For example:

   spec:
     components:
       server:
         javaOptions:
   -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800
   
       meta:
         javaOptions:
   -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800

3. For Fuse Online integrations, set the Maven Arguments (additionalArguments) parameter. For example:

   spec:
     components:
       server:
         features:
           maven:
             additionalArguments: "-Dhttp.proxy=10.0.0.100 -Dhttp.proxyPort=8800"

4. Save the custom resource.

   If Fuse Online is already installed, the syndesis-server pod is redeployed in response to the javaOptions update in Step 2.

5. Republish any running integrations that use the HTTP proxy.

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

Procedure

1. Log in to OpenShift with an account that has permission to edit the Fuse Online custom resource. For example:

   oc login -u developer -p developer

2. Switch to the project in which Fuse Online is running. For example:

   oc project my-fuse-online-project

3. Edit the syndesis custom resource:

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

      oc edit syndesis

   2. Edit the custom resource by changing the addons:todo:enabled field to true:

      spec:
        addons:
          todo:
            enabled: true

   3. Save the resource.

      Saving this change to the syndesis custom resource triggers the syndesis-operator to create a new todo pod and triggers the redeployment of the syndesis-server and syndesis-db pods.