Add reboot collection to state
Respond to feedback
Remove dependency on apiserver/params
exact error messages in assert
renamed error
split up SetReboot
responded to feedback
Merge pull request #707 from gabriel-samfira/reboot-state

Implement reboot watcher

This is just the first branch in a series that is meant to add safe reboot support via juju hooks.

The watcher will look for any reboot event hat happens for a given machine. If that machine is a container, then the watcher will look for reboot events on its own ID and the ID of all parents. For example, lets say we have a machine with ID:

1/lxc/22/kvm/0
1/lxc/21/kvm/2

A reboot event on 1, will trigger a reboot on: 1, 1/lxc/22, 1/lxc/22/kvm/0 and on 1/lxc/21/kvm/2. A reboot on 1/lxc/22, will trigger a reboot on 1/lxc/22 and 1/lxc/22/kvm/0. And finally, a reboot on 1/lxc/22/kvm/0 will only be visible to its own worker.

This is still a work in progress.
uniter: open-port and close-port now sandboxed and validated
Merge pull request #878 from dimitern/uniter-open-close-ports-sandboxing

uniter: open-port and close-port now sandboxed and validated

An important improvement in supporting opening and
closing port ranges for charms is to also provide
sandboxing for these operations. This PR implements
an internal caching of all pending port ranges to
open or close for the unit, as well as existing ports
opened on the unit's assigned machine by other units.
Each time open-port or close-port is called, we validate
the given range against other existing ranges on the
machine and other pending ranges and returns errors
when there's a conflict. Ports are only actually opened
or closed when the current hook is committed.

NOTE: This was proposed as WIP as dimitern:#5 and was
reviewed as http://reviews.vapour.ws/r/125/. After
fixing some suggestions from reviews, now proposing
against juju:master
collect-metrics hook execution triggered by uniter. The uniter signals the collect-metrics hook to be executed every 5 minutes.