use the mgo built in remove rather than a custom one
Update port conflict checker to distinguish between conflicts and exact matches.
Merge pull request #667 from tasdomas/fix-existing-port-open

Update port conflict checker to distinguish between conflicts and exact matches.

This is a fix for #1359837 (https://bugs.launchpad.net/juju-core/+bug/1359837).

Opening a port that is already open should not result in an error.
added comment regarding the use of mgo.Remove to cleanup metrics
Merge pull request #681 from mattyw/delete-metric-batch-bulk

use the mgo built in remove rather than a custom one

Previously we had our own function for deleting a metric batch during the Cleanup call. All we need to do is delete metrics based on a certain selection so we can just use collection.Remove() from mgo.
Hook tool for sending metrics from charm.