azurehpc/examples/lustre_avset
Paul Edwards d1d9993698 Updated docs for SAS key instead of storage key with hsm 2021-09-07 09:16:58 +01:00
..
scripts Added a version of lustre to use an avset 2020-06-11 17:08:46 +01:00
config.json Sensible max hsm concurrency values 2021-09-07 09:11:07 +01:00
pipeline.yml use common group variables 2020-10-19 13:07:39 +02:00
readme.md Updated docs for SAS key instead of storage key with hsm 2021-09-07 09:16:58 +01:00
test.yml Added a version of lustre to use an avset 2020-06-11 17:08:46 +01:00

readme.md

Lustre Cluster

Build Status

Visualisation: config.json

This is a Lustre setup where an Availability Set is used.

Resources:

  • Head node (headnode)
  • Compute nodes (compute)
  • Lustre scaleset
    • Management/Meta-data server on first node using resource disk
    • Object storage servers using all the NVME in a RAID 0
    • Hierarchical storage management daemon on all OSS nodes

The configuration file requires the following variables to be set:

Variable Description
resource_group The resource group for the project
storage_account The storage account for HSM
storage_sas The storage SAS key for HSM
storage_container The container to use for HSM
log_analytics_lfs_name The name to use in log analytics
log_analytics_workspace The log analytics workspace id
log_analytics_key The log analytics key

Note: Macros exist to get the log_analytics_workspace using laworkspace.<resource-group>.<workspace-name> and log_analytics_key using lakey.<resource-group>.<workspace-name>.