The interface was too packed causing the facts and reports tables to be
jammed into place.
Currently working on a complete new node overview page but this should
make things a bit more workable in the meantime.
The Nodes status detail now shows for how many nodes we have events.
Additionally when there are no events we simply show an alert that
nothing is going on.
This commit uses the new parameter with_status from nedap/pypuppetdb#18
Node status is now shown as text with the additional information of
failed/succeded events, unreported time
The statistics on Overview now show the *number of nodes*
that have status failed/changed/unreported
I broke things with 795d243e9d because I
forgot to remove it everywhere from functions and templates. Also
removed the old PUPPETDB_EXPERIMENTAL switching.
PUPPETDB_API is no longer configurable since we're now using features
that are v3 only. Limiting ourselves to v2 compatibility is far too
troublesome and people tend to update to newer versions of PuppetDB
fairly quickly.
* Don't pass unresponsive to the view, access config[] object instead
* Remove the statistics header, it only takes up space
* Lowercase a few things
* Change the descriptions for 'radiator' to make the math work: Because
of how PuppetDB's aggregate-events-count works nodes with both
successful and failed events count for both causing success + failure
+ unreported to not equal population, which is weird. Now we're simply
stating that they have failed events instead of saying that the node
is succesful/failed.
- the amount of hours is defined as `UNRESPONSIVE_HOURS` in default_settings.py
- small status layout improvement in nodes list
- latest report button in nodes list
- nedap/pypuppetdb repo as requirement ( new api was merged nedap/pypuppetdb#17 )
The following frontend features are implemented
- Number of failures, successes, noops/skips in overview
- Show latest reports with 1 or more events in overview
- Direct links to latest Report
- Number and types of events in nodes list
Currently the graphs are shown at the top of the page and because of
that really take up a lot of screen real estate. This commit makes the
graphs a bit smaller but we really need to rethink the layout here.
Additionally we switch the colors to the FlatUI swatches to match the
rest of the theme better.
Puppetboard is an excelent radiator of information, but sometimes
we want to expose information to users we don't trust giving full
access to the PuppetDB query language.
I would reccomend that Puppetboard be run twice. One, with query
enabled, run on a port behind apache login. Another, with query
disabled, run unproxied for the unwashed masses.
Closes#10.
Recently changes were made to pypuppetdb to support, at a basic level,
the v3 API introduced with PuppetDB 1.5.
This commit changes some internals of Puppetboard to handle the new
situation:
* The experimental endpoints are gone, so is the ExperimentalDisabled
Error;
* v2 API can no longer access Reports/Events so we now check that we're
talking at least v3 API;
* Introduce a configuration setting PUPPETDB_API which takes an integer
repersenting the API version we want to talk.
