Handle 404 in maasEnviron.StopInstances
implemented metric validation prior to storing
make validate a method on the metricBatch
review comments fixed and fixed unit tests
Retry release individually in certain cases
Improved error handling and test
Test recursive case
Log warnings for release failure
Logging improvement
Merge branch 'master' into maas-404
Merge pull request #1127 from voidspace/maas-404

Handle missing nodes and permission errors when releasing MaaS nodes

When releasing MaaS nodes a 400, 403 or 404 response means that one or more nodes had errors and none have been released. The error is that the node is no longer available, so we can ignore the error (it's already been released) but we still need to release the other nodes. 

Fixes bug 1319016.
return errors.trace instead of bare err
Merge pull request #1074 from mattyw/metric-state-server-validation

implemented metric validation prior to storing

Before metrics are stored we do a validation check.  Validity is defined by the charm package - This pr just adds the call to the state server. The metrics tests have been updated to check the failure modes of validation and existing tests have been updated to ensure they use valid data

http://reviews.vapour.ws/r/376/
First step in refactoring Action, ActionResult, and ActionStatus