Difference between revisions of "QuantaStor Configuration Files"

From OSNEXUS Online Documentation Site
Jump to: navigation, search
m (qs_cloud_providers.conf)
m (qs_device_link.conf)
Line 8: Line 8:
  
 
==qs_device_link.conf==
 
==qs_device_link.conf==
 +
This is an internal configuration file that controls how QuantaStor prioritizes device paths generated by udev.  The Linux udev system generates links to block devices and stores them in /dev/disk/by-id and other areas under /dev/disk.  These links generally contain unique identifiers or serial numbers for the device within the link name so that devices can be referred to via a strong name that will not change between reboots.  Some of these links are better than others and this configuration file applies weights to the different paths according to what works best for unique device identification.  It should only be edited by OSNexus support and engineering but can be used to hide invalid devices and add support for media with unique udev rules.
 +
 
==qs_ha_modules.conf==
 
==qs_ha_modules.conf==
 
==qs_io_profiles.conf==
 
==qs_io_profiles.conf==

Revision as of 12:56, 11 November 2021

QuantaStor has a series of configuration files that support the platform and make it customizable by our engineering and support team (usually to support new hardware) without requiring code level changes.

qs_ceph_defaults.conf

This file contains a series of defaults to be written to the global section of the ceph.conf file when a new cluster is being created.

qs_cloud_providers.conf

QuantaStor supports integration of object storage with a number of public cloud service providers including Amazon S3, Azure Blob, Dropbox, Wasabi and others. This feature is accessible via the Cloud Integration section of the QuantaStor web management interface. This configuration file enables one to add new service providers and locations to the Cloud Integration system.

qs_device_link.conf

This is an internal configuration file that controls how QuantaStor prioritizes device paths generated by udev. The Linux udev system generates links to block devices and stores them in /dev/disk/by-id and other areas under /dev/disk. These links generally contain unique identifiers or serial numbers for the device within the link name so that devices can be referred to via a strong name that will not change between reboots. Some of these links are better than others and this configuration file applies weights to the different paths according to what works best for unique device identification. It should only be edited by OSNexus support and engineering but can be used to hide invalid devices and add support for media with unique udev rules.

qs_ha_modules.conf

qs_io_profiles.conf

qs_keyvault_modules.conf

qs_nvme_initiator.conf

qs_target_blocklist.conf

qs_cloudcontainers.conf

qs_device_blocklist.conf

qs_enclosure_layout.conf

qs_hwadapter.conf

qs_ipmi.conf

qs_nvme_adapter.conf

qs_nvme_slotmap.conf

qs_volume_profiles.conf