6.2. Server Sync

What is the Server Sync Command?

The Server Sync command checks the status of each cluster represented by d3VIEW HPC Servers. Once the server connection information is gathered, Lucy will check the scheduler for all jobs, nodes, and queues to update the d3VIEW HPC Server status.

Metrics captured during the status update are as follows:

– Generic Core Utilization (running, queued, total available) – Application Utilization (Core status per application) – Queue status (Running jobs per queue) – Node status (Jobs running per node, uptime, availability) – Job status (Job statuses and scheduler details per job) – Storage Utilization (Size, Used, Available, Usage Percent, and Mount) – License status (Number of total licenses vs available licenses)

Once the status is acquired, the server sync will post the updated status to d3VIEW so it can be viewed at job submission or captured for utilization data.

Similar to the Jobs Sync command, if no arguments are specified, the sync will automatically run for each d3VIEW HPC Server sequentially in order of id.

Arguments

Parameter name	Requirement
-h –help	optional
-s -server-to-update	optional
-log-file	optional
-otype	optional

-h

Help

-s

Id or name of d3VIEW HPC Server

-server-to-update

Id or name of d3VIEW HPC Server

-log-file

Path to write log file.

-otype

Terminal output type. If none is selected, no output will be written.

Configuration

To configure Lucy to run this command, Lucy needs a valid connection to d3VIEW and the HPC Servers will need to be available from the server running the command. If being run as a cronjob, all ssh connections between the application server and the scheduler would need to be passwordless.