Make all binaries activate support for automatically dumping
a guru meditation report on SIGUSR1. This is useful for
debugging of production systems where it is not practical to
have the service interruption inherant in attaching a debugger
to the process. Upon receipt of SIGUSR1, a dump will be sent
to the daemon's stderr stream.

Blueprint guru-meditation-reports
Change-Id: Ie4976d434c8d6c27c70a56c6466e47f1106a6678
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

This introduces a set of APIs for creating / outputting
guru meditation reports in a variety of formats (text,
XML, JSON). It also adds the ability to hook up a signal
handler to automatically generate reports.

Blueprint guru-meditation-reports
Change-Id: I1b7527dba7abd85561f4703b0629d6838a7193d6
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

This introduces the 'generator' module concept for the
guru meditation report framework. This allows for arbitrary
data sections to be added to the core sections provided for
all reports. The "default" generators will dump native
thread, green thread and config information. Nova/Glance/etc
apps will be able to register additional custom data.

Blueprint guru-meditation-reports
Change-Id: Ibd17ac7b1640ad27be9cee1deb2612cb81f423ec
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

Implement the '__str__' method on all guru meditation
models to provide a sensible plain text representation
of the data

Blueprint guru-meditation-reports
Change-Id: Ic558a62963bedcea64dae2336241340569ea7147
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

This introduces a new namespace openstack.common.gurumed.
This package will contain modules related to generation
of guru meditation reports, which provide details on all
system state. This commit includs the first part of the
impl, which is the 'model' module containing a number
of classes for the core data models involved.

Blueprint guru-meditation-reports
Change-Id: I5d81cbe73f5646c4932edd1cf1ef6fd8aedda428
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

Delete all duplicate rows with same (task_name, host, period_beginning,
period_ending) expect one with the biggest value in `id` column.

Create UC on fields (task_name, host, period_beginning, period_ending)

Replace Select then Insert -> Try to Insert.

blueprint db-unique-keys

Change-Id: I99f45a6de6630482e9c56738f894cc55a37fffaf

Add generic function that help us to drop duplicated rows from table,
before creating unique constarints. It is very usefull in migrations,
because it will allow DBA to make migrations without IntegrityError
exceptions.

It deletes all duplicates of rows except row with max value in id column.

blueprint db-unique-keys

Change-Id: I7e48d3eb78cf9a5d30752541b143b0c9fa1f838a

Change *fields -> *columns.

There should be tests for other backends mysql and postgres
but at this moment it is not so easy to implement it.

Fixes bug 1123848

Change-Id: I65a618760d499501589d5536c9f7dc64483b19ed

Change-Id: Icc0a69178da13f4679b594b50e3a980ba9ec19bd

Running pep8 results in the following error:

Traceback (most recent call last):
File "tools/hacking.py", line 34, in <module>
import pep8
ImportError: No module named pep8

Change-Id: I31a8bfbffa9ddee306ab414fab367c74d34fdd6b

The test class removed actually being an exact copy of the above
MultiDriverTestCase.

Change-Id: Id2c4141a7da8475e44d534d2e61ae83bf532d980

…age"

The HostState class in the libvirt driver still uses the old
'connection' terminology instead of the preferred 'driver'.

Blueprint: compute-driver-events
Change-Id: I942237c329abbb0b857a5363ce71bd4b9377470d
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

The HostState() class in libvirt creates a second instance of
the LibvirtDriver() class, which cause duplicate initialization
of various things. This is pointless, since it was a method on
the original LibvirtDriver() which created the HostState()
instance, and thus it could easily pass in the original object.

Blueprint: compute-driver-events
Change-Id: I0734bfcc1b014406ffe64ef7abb14a533998dea2
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

No idea how this got this far without being detected.

Change-Id: I5ddf3b4d2ad831fd32008a43d6884fc09405c117

Change-Id: I85a0348b978d4045ebb12a99f1bd9d5888a65b3b