Merge branch 'release-0.95' into develop
bump verison back to development status (9999)
configure_ssh_logging -> configure_paramiko_logging

The 'ssh' Python module was renamed back to paramiko. Updated this
convenience method to use the proper paramiko logger and fixed the name.
awsutils: use sg.authorize to apply rules in create_group

closes gh-356
requirements: bump deps to latest versions
requirements: add pudb to the list of reqs
setup: use py.test for 'python setup.py test'
tests: add scaffolding for 'live' tests on AWS

Added --live option to both py.test and 'python setup.py test' for
running StarCluster tests that require a working AWS account.
tests: add --coverage option

Added --coverage option to both py.test and 'python setup.py test' that
will cause py.test to generate a coverage report after running the
tests.
tests: check pep8 compliance via pytest-pep8
tests: check pyflakes compliance via pytest-flakes
setup: workaround for pytest plugin loading bug

For some reason the pytest_cache plugin is not being loaded properly
when using 'python setup.py test' to manage the test dependencies. If
all dependencies are installed in the site-packages directory this issue
doesn't occur. This issue seems to occur when test deps are missing and
therefore are fetched locally as eggs by 'python setup.py test'. The fix
is to manually call configure_setuptools_entrypoints() on pytest's
PluginManager object in order to properly register the plugin(s). An
alternate fix is to import pytest_cache and pass it to pytest's main
function's plugins kwarg.
start: set default value to None for --no-public-ips

By default StarCluster's start command interprets any options that have
a non-None value to be user-specified options. If the default value of
an option is not None then the start command assumes the default value
to be a user specified value and overrides the config with command-line
option values.

In this case the --no-public-ip default value was not None so setting
PUBLIC_IPS in the config had no effect (unless it happened matched the
start command's default for it of course :P) due to the start command
overriding it with the non-None default value.

closes gh-366
cluster: fix max length error with cluster tags

Fixed issue with cluster tags running over the max length limit for
security group tags by chunking the data and spreading it across
multiple tags if necessary.

closes gh-348
cluster: move warning about no pub ips to validation
tests: add live tests for basic cluster setup
bump version to 0.95.1
Merge branch 'hotfix-0.95.1'