QuantaStor systemd Services: Difference between revisions
mNo edit summary |
|||
Line 15: | Line 15: | ||
== qs-snmpagentd.service == | == qs-snmpagentd.service == | ||
SNMP agent service which works with our MIB to enable discovery and SNMP traps. More documentation on this is available [[SNMP_Agent_Setup|here]]. | SNMP agent service which works with our MIB to enable discovery and SNMP traps. More documentation on this including the SNMP MIB is available [[SNMP_Agent_Setup|here]]. | ||
== qs-boot.service == | |||
This is an early boot stage service which does a series of operations that are important to be completed before the main QuantaStor and other services get started. This includes connecting to KMIP services to gather keys to unlock media, unlocking media via SED and LUKS, and connecting to remote systems to complete NVMeoF and/or iSCSI logins for any Software Adapters that have been configured on the system. | |||
Un-maps Ceph block devices (Storage Volumes) at shutdown | |||
Internal scripting service used by the core service to | == qs-rbdshutdown.service == | ||
ZFS events | Un-maps Ceph block devices (Storage Volumes) at shutdown so as to speed up the shutdown process. | ||
Internal use only REST API for real-time stats which enables the WUI to gather data from our InfluxDB based stats for dashboards | |||
This is our main REST API which we have documented on our web site and this API is also used by our QS Python Client lib | == qs-scriptd.service == | ||
Enables single-sign-on user authentication to LDAP servers and | |||
Internal scripting service used by the core service to do long running tasks like backups and replication. This enables QuantaStor core services to be upgraded and restarted without impacting active replication, cloning or backups. | |||
== quantastor.service == | |||
This is the main QuantaStor core service. In general it can be stopped and restarted at any time without impacting access to file, block, and object storage served by the system. In rare cases the service may be temporarily disabled by support as part of a hardware triage process. | |||
== qs-zfseventd.service == | |||
This service captures ZFS events and routes them to the QuantaStor core service for processing. This enables QuantaStor to react immediately to ZFS pool device failures. | |||
== qs-statsd.service == | |||
Internal use only REST API for real-time stats which enables the WUI to gather data from our InfluxDB based stats for dashboards. | |||
== qs-jsonrpcd.service == | |||
This is our main REST API which we have documented on our web site and this API is also used by our QS Python Client lib. | |||
==qs-sso-authd.service== | |||
Enables single-sign-on user authentication to LDAP servers and Active Directory. |
Latest revision as of 18:56, 11 November 2021
All QuantaStor internal services are managed via systemd configurations which can be found uner /lib/systemd/system:
# du -a /lib/systemd/system | grep "qs\|quanta" 4 /lib/systemd/system/qs-snmpagentd.service 4 /lib/systemd/system/qs-boot.service 4 /lib/systemd/system/qs-rbdshutdown.service 4 /lib/systemd/system/qs-scriptd.service 4 /lib/systemd/system/quantastor.service 4 /lib/systemd/system/qs-zfseventd.service 4 /lib/systemd/system/qs-statsd.service 4 /lib/systemd/system/qs-jsonrpcd.service 4 /lib/systemd/system/qs-sso-authd.service
qs-snmpagentd.service
SNMP agent service which works with our MIB to enable discovery and SNMP traps. More documentation on this including the SNMP MIB is available here.
qs-boot.service
This is an early boot stage service which does a series of operations that are important to be completed before the main QuantaStor and other services get started. This includes connecting to KMIP services to gather keys to unlock media, unlocking media via SED and LUKS, and connecting to remote systems to complete NVMeoF and/or iSCSI logins for any Software Adapters that have been configured on the system.
qs-rbdshutdown.service
Un-maps Ceph block devices (Storage Volumes) at shutdown so as to speed up the shutdown process.
qs-scriptd.service
Internal scripting service used by the core service to do long running tasks like backups and replication. This enables QuantaStor core services to be upgraded and restarted without impacting active replication, cloning or backups.
quantastor.service
This is the main QuantaStor core service. In general it can be stopped and restarted at any time without impacting access to file, block, and object storage served by the system. In rare cases the service may be temporarily disabled by support as part of a hardware triage process.
qs-zfseventd.service
This service captures ZFS events and routes them to the QuantaStor core service for processing. This enables QuantaStor to react immediately to ZFS pool device failures.
qs-statsd.service
Internal use only REST API for real-time stats which enables the WUI to gather data from our InfluxDB based stats for dashboards.
qs-jsonrpcd.service
This is our main REST API which we have documented on our web site and this API is also used by our QS Python Client lib.
qs-sso-authd.service
Enables single-sign-on user authentication to LDAP servers and Active Directory.