Skip to content

Define LUNA PLATFORM settings#

The following settings must be set for LUNA PLATFORM to work minimally:

  • LICENSE_VENDOR — License settings.
  • INFLUX_MONITORING — Settings for monitoring and connection to the InfluxDB database.
  • LUNA_ATTRIBUTES_DB — Redis database address for storing temporary attributes.
  • TASKS_REDIS_DB_ADDRESS — Redis database address for the Tasks service.
  • LUNA_<SERVICE>_DB — Settings of connection to service databases.
  • LUNA_<SERVICE>_ADDRESS — Settings with service addresses.
  • REDIS_DB_ADDRESS — Redis database address for Sender service (when using Sender service).
  • LUNA_IMAGE_STORE_<BUCKET>_ADDRESS — Settings for access to bucket (when using Image Store service).
  • STORAGE_TYPE — Type of storage for bucket storage (S3 or local, when using Image Store service).
  • S3 — Settings of S3-like storage for storing bucket (when using Image Store service and STORAGE_TYPE = S3).
  • LAMBDA_S3 — Settings of S3-like storage for storing archives with modules (when using Lambda service).

The settings can be specified in the extras/helms/luna-configurator/files/platform_settings.json dump file, which is automatically loaded into the Configurator database during the installation of the Configurator service Helm chart. The dump file contains a template that must be updated by entering the correct user data.

Important: The downloaded dump file contains the minimum required list of settings. If necessary, you can add additional settings using the full dump file located at extras/conf/luna_platform_<version>_dump.json as an example.

Update the dump file to be loaded using the following command:

vi /var/lib/luna/luna_v.5.62.3/extras/helms/luna-configurator/files/platform_settings.json

The Helm template luna-configurator/templates/init-configmap.yaml uses the Files.Glob function to find all JSON files in the luna-configurator/files folder in the Helm chart of the Configurator service.

HASP and Guardant license settings are set differently. Select the section below to configure the license based on the required protection mechanism:

HASP license settings#

Note: Follow the steps in this section only if you are activating the license with HASP. If you need to activate a Guardant license, follow the steps in "Guardant license settings".

Specify the IP address of the server with your HASP key in the "server_address" field:

{
    "value": {
        "vendor": "hasp",
        "server_address": "<your-server-address>"
    },
    "description":"License vendor config",
    "name":"LICENSE_VENDOR",
    "tags":[]
},

Save the file.

Guardant License Settings#

Note: Follow the steps in this section only if you are activating the license with Guardant. If you need to activate a HASP license, follow the steps in "HASP license settings".

Set the following details:

  • IP address of the server with your Guardant key in the "server_address" field.
  • License ID in the format 0x<your_license_id> obtained in the section "Saving the license ID" in the license activation guide, in the field "license_id":
{
    "value": {
        "vendor": "guardant",
        "server_address": "<your-server-address>",
        "license_id": "0x92683BEA"
    },
    "description":"License vendor config",
    "name":"LICENSE_VENDOR",
    "tags":[]
},

Save file.

GPU settings#

Note: Skip this section if you do not intend to use the GPU.

GPU can be enabled for Remote SDK services and for individual Lambda instances.

GPU settings for individual Lambda instances are set at creation time (see the "create lambda" request).

The Remote SDK service does not use the GPU by default.

If you want to use the GPU for all estimators and detectors at once, you must use the "global_device_class" parameter in the "LUNA_REMOTE_SDK_RUNTIME_SETTINGS" section. All estimators and detectors will use the value of this parameter if the "device_class" parameter of their own settings is set to "global" (default).

If you want to use the GPU for a specific estimator or detector, you must use the "device_class" parameter in sections like "LUNA_REMOTE_SDK__SETTINGS.runtime_settings".

Note: The extras/helms/luna-configurator/files/platform_settings.json dump file from the delivery set contains only the "LUNA_REMOTE_SDK_RUNTIME_SETTINGS" section, which allows enabling GPU for all estimators and detectors at once. If necessary, you can add settings for the required estimator or detector to the dump file yourself, using the full dump file located at the path extras/conf/luna_platform_<version>_dump.json as an example.

Note that the "LUNA_REMOTE_SDK_RUNTIME_SETTINGS" section in the dump file has the "gpu" tag specified. To use the settings from this section, you need to transfer the tagged section using the "EXTEND_CMD" environment variable in the Helm chart of the Remote SDK service. An example of passing a tagged setting is commented out in the values.yaml file for the Remote SDK service.