summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 2143931)
raw | patch | inline | side by side (parent: 2143931)
author | Sebastian Harl <sh@tokkee.org> | |
Mon, 10 Aug 2015 07:44:23 +0000 (09:44 +0200) | ||
committer | Sebastian Harl <sh@tokkee.org> | |
Mon, 10 Aug 2015 07:45:15 +0000 (09:45 +0200) |
doc/sysdb.7.txt | patch | blob | history |
diff --git a/doc/sysdb.7.txt b/doc/sysdb.7.txt
index 6e81c47035298fc0bb20f5675de5de14a35db9b3..383784855281edd1b8372edcb460b62106b6f287 100644 (file)
--- a/doc/sysdb.7.txt
+++ b/doc/sysdb.7.txt
SysDB's features are build around a set of concepts which are explained in
this section.
+Object Store
+~~~~~~~~~~~~
+The central part of SysDB's database is the object store which stores all
+objects (hosts, services) known to SysDB. The implementation is provided by a
+"store" plugin and may be backed by arbitrary data-stores. At least one store
+plugin has to be loaded to let the daemon do its work.
+
Hosts and Services
~~~~~~~~~~~~~~~~~~
The basic building block of SysDB's store are host and service objects
based on facts like architecture or LSB information using query commands like
*LOOKUP* (see manpage:sysdbql[7]).
-Host and service objects are managed by backend plugins and queried from other
-systems, like inventory databases or monitoring systems.
+Host and service objects are provided and updated by backend plugins and
+queried from other systems, like inventory databases or monitoring systems.
Hostname Canonicalization
~~~~~~~~~~~~~~~~~~~~~~~~~