Product Selector

Fusion 5.9
    Fusion 5.9

    Configure a Fusion integration with Lucidworks AISelf-hosted Fusion

    This topic details how to configure an integration between Fusion and Lucidworks AI.

    Prerequisites

    Your Lucidworks technical account manager (TAM) creates the workspace and grants appropriate personnel in your organization the admin privileges to that workspace.

    Integration maintenance must be completed by the personnel in your organization who have been granted privileges to access confidential client information and perform system administration tasks. Both the workspace owner role and the app admin role can manage integrations.

    In addition, the TAM creates the initial Lucidworks AI application for your organization.

    Configure a Fusion integration

    1. When the workspace is created and the appropriate personnel in your organization have been assigned the workspace owner role, verify designated personnel can sign in to Lucidworks Platform and access the Lucidworks AI application.

    2. Click the Lucidworks AI app where you want to add an integration.

    3. Click Integrations > Self-hosted Fusion > + Add new integration.

    4. On the New integration screen in the Name field, enter a unique name for your integration.

    5. In the Tags field, enter optional freeform text to identify the integration.

    6. Click Save. To exit the screen without saving changes, click Cancel.

    7. In the New integration screen, click Download to download the YAML code. You can also copy and paste the information to replace the contents of an existing account.yaml file. This file is needed in the next procedure to configure Lucidworks AI Gateway through Helm.

    8. Click Done to close the screen.

    Configure Lucidworks AI gateway through Helm

    1. Run the following command in Kubernetes to configure Lucidworks AI Gateway through Helm:

      helm install <RELEASE-NAME> oci://us-docker.pkg.dev/fusion-beta/fusion-beta-charts/fusion-beta --version 5.11.0-beta1 --namespace <NAMESPACE> --set global.zkReplicaCount=3 --values <VALUES-FILE> --values <INTEGRATION-CONFIG-FILE>
      If Fusion is being installed into a Kubernetes cluster where Fusion is already running in another namespace, you must add --set seldon-core-operator.crd.create=false to the Helm command to prevent attempted creation of a duplicate Seldon Custom Resource Definition (CRD).
      Variable Definition

      <RELEASE-NAME>

      The freeform text name of the Fusion deployment.

      If you do not wish to enter a specific name, enter

      --GENERATE-NAME.

      <NAMESPACE>

      The name of the Kubernetes namespace where you are installing the Fusion deployment.

      <VALUES-FILE>

      The Helm values used in the Fusion deployment. Use one of the following methods to determine the values:

      • Use the scripts in the Fusion cloud native repository to generate values.

      • Copy the values from one of your existing environments by completing one of the following:

        • If the values file used to configure that environment is readily available, use those values.

        • Run helm -n <NAMESPACE> get values <RELEASE-NAME> in the existing environment to obtain the values. You must then copy and paste into a new values file. Then complete necessary edits after the USER-SUPPLIED VALUES: line to create new values for the deployment.

        • To use the default Fusion values, do not use the --values argument.

      <INTEGRATION-CONFIG-FILE>

      This is the account.yaml additional values file that was generated in the Lucidworks Platform Integrations > Self-Hosted Fusion screen, and that you saved in the directory from which you run the helm command. For more information, see Configure a Fusion integration and Add a Fusion integration with Lucidworks AI.