Administrator panels

The administrator panels allow you ton configure OKA and its modules.

To access these panels, you must be an admin user. An admin user is created during OKA installation. Other users can be created from the Users section in this administrator panel (see Users).

You can access OKA administration panels here: https://<OKA SERVER>/admin/ or using the admin panel button in OKA navigation bar. The VIEW SITE link at the top right of the administrator panel allows you to go back to OKA interface.

Analyze-IT - Filters

In this panel, you fill find all filter profiles created by the users from OKA interface (see Save filters as profile). For more details about the filters see Filters.

CloudSHaper

Conf cloud reports

To use the cost consumption module of CloudSHaper, you must define in this panel the AWS bucket where the consumption reports are stored. You can also filter the reports for a specific account or on a delimited period.

Data manager

Cluster configurations

In this panel, you can update the number of nodes and cores of your cluster.

The minimum memory per job is used to identify memory-bound nodes (see Load > Occupancy). It is the minimum available memory needed by a node to be able to run a job. If not provided, it will be automatically computed to the median of requested memory by users in the last accounting logs ingested.

In this panel there is also an option to specify a Timezone. For the time being, this is only used in case data are retrieved directly by calling to a Slurm scheduler to avoid having data retrieved in UTC when you expect them in your own timezone.

Conf apis

In this panel, you can update configurations for available APIs output and input capabilities. This include for example, ouput_db objects used to configure access to your Elasticsearch database.

Conf files

In this panel, you can update the path to your input files (e.g. accounting file) and the output directories where to save your trained models.

Conf job schedulers

In this panel, you can update the configuration of your Jobscheduler (version, how to connect…).

See also Clusters management for how to create a new cluster and manually upload job scheduler logs through the web interface.

Conf pipelines

In this panel, you can associate filters (see Filters) and data enhancers (see Data enhancers) to each pipeline.

Pipelines

You will find here the list of all the pipelines set up in your environment. Their names can be used to execute each pipeline manually using the run API (see Usage). Pipelines can also be edited if you for example wish to change the queue used when executed through a task.

Periodic Tasks

In this panel you can access all available tasks provided by OKA. You will be able to see basic information regarding those tasks at a glance. Tasks can be edited if you for example wish to enable/disable them or update the CRONTAB value associated with it.

image_periodic_tasks

  • ENABLED: Show if the task is setup to run automatically or not.

  • CRONTAB SCHEDULE: Show the current schedule on which the task will run if enabled.

Warning

Be careful if you wish to delete a Crontabs object as it would automatically remove all associated Periodic tasks and you would have to recreate manually.

  • STATUS: Gives you information regarding the execution of the process handled by the scheduled task. This is not the periodic task status but one for the actual method that ran within the task. If the periodic task is attached to a pipeline then, the status shown is an information telling you if the pipeline execution was successful or not.

  • RUN NOW: Allows you to request the immediate execution of the task.

Note

Some tasks might not have any STATUS or CRONTAB because what they execute does not return any information and their schedule is actually set to something like “every day”. This is the case for example for the clear_expired_sessions. image_scheduled_clear_session

Users

In this panel, you can create, update or delete a user. Three types of users can be created depending on their permissions:

  • A regular user: has no advanced permission, will have access to OKA interface only.

  • A Staff user: can access OKA interface and has permission to connect to the admin panel to clear the caches.

  • A Superuser / admin user (MUST BE Staff): can access OKA interface and has permission to connect to the whole admin panel.

Upon creation of a new user, you will need to activate the user in this panel.

Clear cache

Caches are used to temporarily cache the result of OKA APIs to give you faster results if you try to access the same data many times in a row. Caches are automatically cleared:

  • On a time basis, based on CACHE_DURATION variable set in the ${OKA_INSTALL_DIR}/config/oka/oka.yaml (every 3 hours by default)

  • At pipeline execution (accounting logs ingestion, etc.)

If you witness some inconsistency in the data shown by OKA interface, you can use this panel to manually reset the caches. We advise you to clear both fallback and main caches.

Rosetta

Use this panel to customize the terms used by OKA interface (titles, traces names…). The eligible terms have been chosen by OKA development team. If you wish to be able to customize other terms, please contact UCit Support or your OKA reseller.

On Rosetta interface, use the PROJECT filter to identify the custom applications. For each application, you will be able to customize the eligible terms. Click on SAVE AND TRANSLATE NEXT BLOCK to save your changes. Restart OKA server and refresh OKA interface to see your modifications (be careful that your browser cache doesn’t show you the unmodified OKA interface).