QuantaStor Configuration Files

From OSNEXUS Online Documentation Site
Jump to: navigation, search

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. Configuration files are stored in /opt/osnexus/quantastor/conf and most can be overridden using a customized version of the file stored in /var/opt/osnexus/quantastor/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.


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.


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.


When creating or modifying a Storage Pool there's an option to apply a performance tuning profile to the pool so that it operates optimally for specific use cases like Server Virtualization. New profiles can be added to the system via this configuration file.


Some NVMeoF system vendors require special options to be applied at the time of NVMeoF connection in order for the device to work optimally with QuantaStor. One common example is customizing the number of IO queues:



This file is used to hide iSCSI and NVMeoF targets from showing up in the discovered targets list of a Software Adapter. This is used to hide control device LUNs shared by 3rd party systems.


Custom settings to adjust how we use rclone for mounting object storage as local NAS storage. These settings should generally not be modified but can be helpful for performance tuning.


Certain devices can show up on some server platforms which are block devices but are not suitable for use with Storage Pools. These are often internal use devices or USB storage devices and they can be masked and hidden based on their vendor / product identifiers. If you have a device that's appearing within your QuantaStor system that shouldn't be presented in the WUI this file can help hide those.


This is the main configuration file for adding support for new server, JBOF, and JBOD enclosures of all types. It has key information about the layout of the drive slots, vendor, and manufacture details and more. If you have new hardware that needs adding to QuantaStor it can be done by editing this file but we recommend contacting OSNexus support to get assistance with this so that the hardware can be added to our official supported HCL.


QuantaStor has internal hardware integration modules to support most of the major HBAs and RAID controllers and this configuration file indicates which version of the vendor CLI to use. HBAs are used for Storage Pool devices and RAID controllers are generally only used for boot devices.


The IPMI (Intelligent Platform Management Interface) standard provides QuantaStor with server platform information about system thermals, power-supplies, fans, CPUs, and other sensors. Unfortunately the identifier tags for these different pieces of information can vary by vendor as there is very little standardization of the tags. This configuration file helps to normalize the vendors so that QuantaStor can monitor hardware from a broad spectrum of manufacturers and generations of hardware.


NVMe devices effectively connect directly to the PCIe bus of a server motherboard rather than through an HBA like one would see with SAS and SATA media. QuantaStor creates a synthetic virtual NVMe Adapter on NVMe based servers which can then be associated with a PCIe NVMe slotmap. These in turn are mapped to an enclosure layout so that QuantaStor is able to support newer NVMe based servers and JBOFs with the same level of device correlation as we get for SAS/SATA.


This maps each NVMe/NVMeoF device pcie slot identifier to a drive slot identifier like 1, 2, 3, 4. Each vendor/model of server has a unique pcie slot map identifier set and this file is used to store those.


This contains a list of configuration settings as 'profiles' for Storage Volumes that can be applied as a Storage Volume Profile when a new Storage Volume is created or modified.