Code review comment for lp:~johnsca/charm-helpers/services-framework

Revision history for this message
Cory Johns (johnsca) wrote :

This MP includes the most recent version of the Services framework, which changes the focus of charms from handling charm events (hooks) to describing the data (and sources of that data) required to set up the software and the actions to take when all of the required data is available. It also creates a standard for rendering config and services jobs based on Jinja templates, and manages re-rendering the files and restarting the services when the data changes.

This relieves the charm author of having to do things like keep track of a bunch of .foo flag files for indicating whether or not such-and-such file has been written or such-and-such service has been started.

The docstrings below are fairly complete, and some (somewhat simple) real-world example usages can be found in the Apache Allura charm (http://bazaar.launchpad.net/~johnsca/charms/precise/apache-allura/refactoring-with-tests/files) and the RethinkDB Docker charm (https://github.com/bcsaller/juju-docker/).

« Back to merge proposal