Committing everestd

everestd is a simple service for handling our everest machine types.  Currently
is serves the following purposes:

1) Backend service for everest-bootstrap
2) Creates the yaml files used for Puppet's external nodes.

Usage:
Once installed simply browse to http://[hostname]:8601/nodes.html.  From there
it should be easy to navigate to the rest of the functionality.  Most resources
have several representations.  Try changing 'html' to 'xml' or 'yaml' in the
urls.

Configuration:
The config file gets laid down in /etc/everestd/

In the future it could be switched to use a db for storing the external node
data.  This would allow us to do some interesting things but it would make
bootstrapping a repo more complicated.  Currently Puppet installs everestd once
it has alread been bootstrapped.  Since our external node script simply looks
to the yaml files on disk Puppet doesn't even have to know everestd exists.
This is also closer to how Prod Ops manages there external nodes.

Implementation details:
everestd uses the everest gem to get at the machine type information for a
particular repo.  This is similar to how our old external nodes script worked.

For the web portion everestd makes use of the camping microframework.  This
includes the reststop library for restful controllers and views as well as the
the picnic gem for the service script.  Yay for stupid names.

The gem was created with newgem and the rpm spec file was generated with
gem2rpm.

TODO:
* make the yaml node dir configurable.
* consider allowing machines to be configured/koan from the web ui (as a
possible replacement for everest-bootstrap)

0 files changed, 0 insertions, 0 deletions