![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
index 1db223979cb6daa1db6f3d450f90954b412d9481..191979e1ebe33065271a27e353cb15d51d1d3c20 100644 (file)
--- a/README
+++ b/README
===============================================================
“System DataBase” (SysDB) is a multi-backend system management and inventory
- collection service. It may be used to (continuously) collect information
- about your systems from various backends (inventory services, monitoring
- services, etc.) and provides a unique interface to access the information
- independent of the active backends. This is done by storing and mapping the
- backend objects to generic objects and correlating the attributes to create
- a single hierarchical view of your infrastructure.
+ collection service. It stores system and inventory information about
+ hardware and software systems. This information is (continuously) collected
+ from various configurable backends (inventory services, monitoring services,
+ etc.) and stored in a graph-like hierarchy of generic objects. The store may
+ be queried through a generic interface independent of the active backends.
+ Object names are canonicalized before they are added to the store to ensure
+ a consistent view of your infrastructure.
+
+ The central object type is a host, which generally represents a physical or
+ virtual machine or any other type of physical resource. Hosts, in turn, may
+ reference a list of services which represent any kind of logical resource
+ like a software system. Both, hosts and services, may reference a list of
+ attributes which represent further information about the respective host or
+ service object. For example, attributes may specify static information like
+ a host's architecture or the software version or reference performance data
+ like the current memory utilization or much more.
SysDB is free and open source software, licensed under the 2-clause BSD
- license. See COPYING for details.
+ license. See COPYING for details. Changes between all SysDB releases can be
+ found in the file ReleaseNotes.
+
+ <http://sysdb.io/>
+
+Configure and install SysDB
+---------------------------
+
+ To configure, build and install SysDB with the default settings, run
+ ‘./configure && make && make install’. For detailed, generic instructions
+ see INSTALL. For a complete list of configure options and their description,
+ run ‘./configure --help’.
+
+ Various third-party packages are required for a full installation of SysDB.
+ See the section ‘Prerequisites’ below for details. A summary of
+ user-supplied and auto-detected build settings is displayed at the end of
+ each ‘configure’ run. Consult this first for trouble-shooting.
+
+ By default, SysDB will be installed into ‘/opt/sysdb’. You can adjust this
+ setting by specifying the ‘--prefix’ configure option - see INSTALL for
+ details. If you pass DESTDIR=<path> to ‘make install’, <path> will be
+ prefixed to all installation directories. This might be useful when creating
+ packages for SysDB.
Prerequisites
-------------
<http://pubs.opengroup.org/onlinepubs/9699919799/>
- * asciidoc, xsltproc, xmlto:
+ * asciidoc, xmlto:
The AsciiDoc text document format is used to write the manpages.
<http://www.methods.co.nz/asciidoc/>
- <http://xmlsoft.org/XSLT/>
<https://fedorahosted.org/xmlto/>
* libedit or libreadline:
Testing
-------
- Unit tests for SysDB are shipped along with the source code in the ‘t’
- subdirectory. Run ‘make test’ to run all available tests.
+ Unit and integration tests for SysDB are shipped along with the source code
+ in the ‘t’ subdirectory. Run ‘make test’ to run all available tests.
Some tests require the ‘fopencookie’ function as provided by the GNU libc
library. It used used to mock I/O related functions. In case this function
is not available, the respective tests will be disabled automatically.
- Code coverage testing using Gcov may be enabled when using the
- ‘--enable-gcov’ configure option.
+ The integration tests require valgrind. If it is not available, integration
+ tests will be disabled automatically.
-Configuring / Compiling / Installing
-------------------------------------
+ For the latest build status, see:
+ <https://travis-ci.org/tokkee/sysdb>
- To configure, build and install SysDB with the default settings, run
- ‘./configure && make && make install’. For detailed, generic instructions
- see INSTALL. For a complete list of configure options and their description,
- run ‘./configure --help’.
+ Code coverage testing using Gcov may be enabled when using the
+ ‘--enable-gcov’ configure option.
- By default, SysDB will be installed into ‘/opt/sysdb’. You can adjust this
- setting by specifying the ‘--prefix’ configure option - see INSTALL for
- details. If you pass DESTDIR=<path> to ‘make install’, <path> will be
- prefixed to all installation directories. This might be useful when creating
- packages for SysDB.
+ For the latest coverage report, see:
+ <https://coveralls.io/r/tokkee/sysdb>
Author
------