Infrastructure configuration

Note: If you have changed the configuration or changed the operating status of any component involved in this document while LiCO container is running, the following command must be executed to restart LiCO container:

Cluster configuration

The following part of the infrastructure configuration in the /etc/lico/lico.ini should be modified:

Storage configuration

To adhere to the shared directory configurations in this document, the following part of the storage configuration in the /etc/lico/lico.ini should be modified:

Scheduler configuration

The following part of the scheduler configuration in the /etc/lico/lico.ini should be modified:

Shared folders configuration

To make new users accessible to one or more custom shared directory, do the following:

Step 1. Create one or more shared folder, change the permission

Attention:

Step 2. Modify the share directories configuration in the /etc/lico/lico.ini:

Note: You need to run the following command for the changes to take effect

Transiter configuration

Job submission, singularity command query, etc. will be executed on the configured transit node. You could modify the following configuration in the /etc/lico/lico.ini:

Note: When running LiCO inside docker, HOST must be specified.

Login configuration

The following part of the login configuration in the /etc/lico/lico.ini.d/user.ini should be modified:

Accounting configuration

If you need to use the billing function. The following part of the billing configuration in the /etc/lico/lico.ini.d/accounting.ini should be modified. Through this configuration, you can set the time and content format of the exported report according to your time zone and your needs.

Attention: When the scheduler is PBS, daily billing mode is not currently supported.

Job configuration

Due to the delay in slurm statistic date collection, billing data of memory will be lost if the memory usage of the job is not obtained immediately after job is completed. To get memory at the best effort, the following part of the job configuration in the /etc/lico/lico.ini.d/job.ini should be modified:

When the file lsb.events does not exist in its default path $(LSB_SHAREDIR)/cluster_name/logdir, or lsf is not installed on the lico head node, the bhist command won't retrieve job information. Enabling the following configuration provides more accurate historical run times for jobs.

Database configuration

If you database server is not the same as the LiCO management node. Change the instructions in the following configuration file to the ip address of your database server.

  1. /etc/lico/lico.ini

  2. /etc/lico/lico.ini.d/monitor.ini

Confluent configuration

If your confluent server is not the same as the LiCO management node. Change the instructions in the following configuration file to the ip address and port of your confluent server

  1. /etc/lico/lico.ini.d/cluster.ini

  2. /etc/lico/confluent-proxy.ini

    Note: You need to run the following command for the changes to take effect

OneAPI configuration

Note: This function is unavailable if Intel oneAPI is not installed.

If you have installed intel oneAPI and want to use intel oneAPI by LiCO. The following part of the oneapi configuration in the /etc/lico/lico.ini.d/oneapi.ini should be modified

Monitor configuration

LiCO supports the unmonitored version, if you need to use the unmonitored version. The following part of the monitor configuration in the /etc/lico/lico.ini.d/monitor.ini should be modified:

EAR configuration

LiCO supports to configure EAR through LiCO. If you want to use this function, the following part of the EAR configuration in the /etc/lico/lico.ini.d/ear.ini should be modified:

Publish configuration

In the publish operation, the /tmp directory is used by default to cache temporary files. If you want to change it,the following part of the Publish configuration in the /etc/lico/lico.ini.d/publish.ini should be modified:

When you need to publish docker. you need to edit the /etc/containers/storage.conf file. modify the mountopt = "nodev,metacopy=on" to mountopt = "nodev,metacopy=off".

Container configuration

If you want to use lico web to build images. the following part of the container configuration in the /etc/lico/lico.ini.d/container.ini should be modified:

Cloudtools configuration

If you want to control the time when jupyter is automatically closed, you can modify the defaultValue while the id of the params in the file /var/lib/lico/core/templates/jupyter/template.json is one of jupyter_timeoutkernel_timeoutterminal_timeout.

The meaning of these three parameters is as follows:

If you want to add automatic labeling function in CVAT, you need to add nuclio server address to defaultValue while the id of the params in the file in /var/lib/lico/core/templates/cvat/template.json is CVAT_NUCLIO_HOST (If you don't have Nuclio or auto annotation model installed, Please refer to https://opencv.github.io/cvat/docs/administration/advanced/installation_automatic_annotation/).

Notice configuration

Attention: The configuration in this section is needed only when lico-wechat-agent module is installed for the cluster. You can obtain and from https://developers.weixin.qq.com/doc/offiaccount/Basic_Information/Get_access_token.html

The following part of the wechat-agent configuration in the /etc/lico/wechat-agent.ini should be modified:

Template configuration

When the operating system on the host machine is Ubuntu, do the following modification:

Note: You need to run the following command for the changes to take effect