matahari bug fix and enhancement update

Updated matahari packages that fix multiple bugs and add various enhancements
are now available for Red Hat Enterprise Linux 6.

The matahari packages provide a set of APIs for operating system management that
are exposed to remote access over the Qpid Management Framework (QMF).

This update fixes the following bugs:

* Prior to this update, the matahari services agent could not monitor the status
of a system service. As a consequence, matahari could not be used in
high-availability (HA) environments where status monitoring is a requirement.
With this update, the user of the services agent can specify the frequency for
the status check and the matahari services agent can now provide service health
information for applications such as HA. (BZ#688193)

* Prior to this update, the wrong CPU core count was returned when requesting
the CPU core count from the matahari host agent. With this update, matahari and
the supporting library, sigar, have been modified to ensure that the core count
is not improperly affected by hyperthreading support. Now, the expected CPU core
count is returned. (BZ#714249)

* Prior to this update, the host agent included only time related metadata when
producing heartbeat events. As a consequence, it was problematic to associate
heartbeat events with the host they originated from, especially in logs. With
this update, the heartbeat events produced by the Host agent include the
hostname and the hardware's Universally Unique Identifier (UUID) as additional
metadata. Now, it is easier to associate the host agent heartbeat events with
the host they originated from. (BZ#729063)

* Prior to this update, the data address for matahari QMF objects was
inconsistent. As a consequence, the data address for some agents was the class
name, for others it was a UUID. This update uses consistently the class name as
the data address. Now, the data address across all matahari agents is
consistent. (BZ#732498)

This update adds the following enhancements:

* Prior to this update, matahari only supported IBM eServer xSeries 366, AMD64
and Intel 64 architectures. This update adds support for PowerPC and IBM System
z architectures as a Technology Preview. (BZ#663468)

* This update adds support for QMF to allow for kerberos authentication.
(BZ#688181)

* With this update, matahari includes an agent for system configuration to
support updating the system configuration with both puppet and augeas.
(BZ#688191)

* Prior to this update, users could only specify a hostname or IP address. As a
consequence, a dynamically updated list of brokers to connect to was not
provided. With this update, matahari supports querying for DNS SRV records to
determine the broker, or the list of brokers to connect to. Now administrators
can use DNS SRV to control where matahari agents connect to. (BZ#735419)

All users of matahari are advised to install these packages, which fix these
bugs and add these enhancements.

Before applying this update, make sure all previously-released errata relevant
to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red
Hat Network to apply this update are available at
https://access.redhat.com/kb/docs/DOC-11259

663468 - expand matahari to support PPC and zSeries architectures
688181 - support kerberos authentication in matahari
688191 - Matahari Agent for configuration
688193 - Implement recurring actions for Matahari Services Agent
688199 - Include common lib function for looking up broker info via DNS SRV records
709649 - fails to build without upstream patches
714249 - matahari host agent reports wrong cpu core count
727192 - agent property uuid: Failed to open file '/etc/machine-id'
727194 - matahari-sysconfig-console start unrecognized option '--daemon'
727954 - matahari agents core dump w/ sigar-1.6.5-0.2.git58097d9
727961 - RFE: matahari agent reconnect too verbose
728360 - matahari broker config issue in init script, SSL config fails to load
728631 - matahari agents fail to determine domain name for DNS SRV record query
728977 - matahari-host agent coredumps when connected broker stops
728988 - matahari agents fail to reconnect after broker restarted
729063 - RFE: include hostname in matahari-hostd heartbeat event
729331 - clean up matahari log messages
729332 - matahari-qmf-service-cli specifies two -P, displays error
729516 - matahari-consoles rpm non-fatal install error
730044 - matahari-host shutdown/reboot not graceful
730066 - matahari-host custom uuid problems
730087 - matahari sysconfig crashes
731433 - RFE: matahari init script shouldn't allow multiple instances of the same agent
731534 - matahari agents unable to connect to remote broker
731858 - matahari agents fail to use broker from DNS SRV record
731914 - matahari service seg fault on multiple method timeouts
732498 - Data addresses populated with class name
733013 - package matahari-selinux should not exists
733150 - matahari sysconfig crash on is_configured()
733384 - sysconfig core dump with bad scheme parmeter
733393 - sysconfig agent doesn't execute puppet script
733451 - matahari-sysconfig query() segfaults
733468 - RFE: better error messaging for resource invoke() failures
733483 - windows agents fail to connect to broker
734522 - matahari-qmf-service-cli needs to require resource instance name
734536 - timeout/interval inconsistency with matahari-qmf-service-cli
734981 - matahari-brokerd needs execute permission
735419 - Agents should support multiple SRV records
735426 - Add support for DNS SRV to matahari-brokerd
735429 - Matahari agents on Linux should connect to localhost only by default
736468 - garbage printed on get_ip_address("badNicValue")
737088 - Include man pages in Matahari package
737137 - sysconfig run methods return zero on bad data
737541 - upgrade missing hostname, matahari should pre-req sigar v1.6.5-0.3?
737618 - matahari upgrade fails to stop correct processes
739666 - uuid generation returns NULL on minimal installation profiles
739952 - mingw32-matahari services agent lists "LSB" as a valid standard
740038 - sysconfig times out with existing key
740090 - Sysconfig key handling can be used to read/write to/from any file on the system
740091 - Store sysconfig keys in a sub directory of /var/lib/matahari
741965 - special characters in key results in error
746084 - matahari services missing from chkconfig
751799 - spec file need to change require qmf-devel to qpid-qmf-devel