test for regular file, not executable (https://github.com/wanelo/boundary_scripts/commit/9c72c0d056d7906eaf7d457e1e177be7fe3db1d8)
disconnect script was not cleaning up meters for which no connection events exist.  the script will now purge any meters that have either 1) not been connected since the timegiven in the -s option. or 2) Do not have any connection or disconnection events.  These meters are assumed to be older than the -s cutoff.
If we detect that the script is being run as root, like in an AWS instance kickoff, we will elide the use of sudo.
Remove annotation scripts and update event ones.

Remove the use of annotations service and sync the create event scripts
with the ones on app.boundary.com.
Merge pull request #11 from pkwarren/update_event_scripts

Remove annotation scripts and update event ones.
Reenable the '-f "OS VERSION" masquerade option when provisioning meters.

To allow installing meters on unsupported systems, reenable the '-f'
option. To install on Fedora, for example, use this:

setup_meter.sh -f "RHEL 6.5"
Simplify Fedora installs by installing the highest supported Redhat RPM.

Since we build the meter dependencies statically, Redhat and Fedora are
compatible enough to run the same meter binaries.
new script delete_events.py

rev 1 - deletes all events tied to the ORG specified in the ORG_ID
variable
Merge pull request #12 from pvfkb/master

new script delete_events.py
Update delete_events.py

removed api key and org id values to protect the innocent
Use meter 2.0.2's built-in provisioning ability

This simplifies the script a fair amount and makes future additions to
the meter provisioning process easier as the logic is centralized in the
package itself.
tag the meter with all available tags in an EC2 environment

attempt to discover what tags the meter has by using ec2/euca tools

Thanks to ralph-tice for a prototype patch.

https://github.com/boundary/boundary_scripts/pull/5
openSUSE support
minor fixes to installation checks

 use the correct VERSION_CMP for checking supported versions
 hide output of checks for ec2 tools
 document existence of -s flag
resurrect FreeBSD install support
gracefully handle running as the root user when there is no sudo command installed

In some cases, we would end up with a missing $SUDO substitution that
would cause some variables to get set in the wrong place
add LinuxMint support
rework usage of 'SUDO' in setup_meter.sh to be more bulletproof

Removes individual SUDO calls, replace by respawning the script as sudo
-E. This makes things like inheriting environment variables work in a
predictable fashion.
Revise error handling to point users in the right direction.

Only check for privileges after ensuring that we support the platform.
auto-update the repository on openSUSE