doc: Fix RPM building documentation

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Reporting: properly close db connection

Close the db connection at the end of each DjangoORM import, not when
the reporting collector shuts down.  The collector may not have even
opened a connection, in the case of a storage backend other than
DjangoORM.

Fixes #157
Core: close all database connections at the end of XML-RPC requests
cleared pylint error on PluginDatabaseModel metadata options
bcfg2-report-collector: better error messages when failing to daemonize
Core: better error messages when altsrc bind fails
doc: Remove references to ConfigFiles

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
doc: Add information about ecdsa keys

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Revert "Systemd: systemd is a replacement for chkconfig"

This reverts commit 690a18b5bb61516e5c11f6da3d788332373c196b.

While systemd is meant to replace chkconfig, it appears that RHEL7 has
both and does not provide systemd alternatives for certain SYSV init
scripts by default.
Merge branch 'maint' of https://github.com/zultron/bcfg2 into maint
Correctly upgrade or downgrade yum packages

Formerly, yum did an 'update' to install the correct version of a
package, even if the desired package was older than the installed
package.  This is wrong; it needs to do a downgrade.  This changes it
to downgrade when the desired package is older, and upgrade if it is
newer.

There is still the possibility of upgrading a package that should be
downgraded if the desired package is only partially specified, but
this should be very rare.
Reporting: Log to debug to prevent spam in logs

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Enable bcfg2-yum-helper to depsolve for arches incompatible with server

By default, the yum dependency resolver uses the host's architecture
to filter compatible packages.  This prevents dependency resolution
when the bcfg2 client's architecture is incompatible with the
server's.

This workaround checks the <Arch/> element for each of the client's yum
sources, and if they are all identical, passes that architecture to
bcfg2-yum-helper to override the default.

The rpmUtils.arch module may only be configured for a single
architecture.  If multiple architectures are configured in yum
sources, we don't know what to do*, so use the default behavior
instead.

* There are functions in rpmUtils.arch that can probably be used to
pick the right arch from a list, but I haven't explored that.