We can attempt to test our publisher code \o/

Unfortunately we can't test it very well, and Ceilometer is a pain in
the arse. I guess we can test the flattening function, which is most of
what matters. Beyond that, it's up to Pymarquise to accept and spool the
sample data that we feed in.
Some work in progress on doing sanity comparisons
Added event_type to primary identifier

Events are in form $counter_name.[update|create|delete].[start|end]
It is possible for the other components of the current primary identifier to be identical to another but have a different event_type.
The change is required to be able to distinguish between start and end events.
modified .travis.yml to include glib as a libmarquise dependency
added flavor type
added ldconfig to travis
Added comments + cpu_number
added timestamp + success/failure messages for events
missing space
sync with current master branch
Update vaultaire.py

wip/braindump
added modified payload generation
minor fixes
version bump
added glib to ldconfig path
Mash testability into the modified implementation branch
Ubuntu puts glib.h somewhere weird
Revert "Ubuntu puts glib.h somewhere weird"

This reverts commit 7734fda92220653b3ab88c6eab42a0cf621d8ee4.
Ubuntu include paths are weird
Try specifying the include directory