not writing a crashlog when we have a better message already present to tell the user what went wrong and how to fix it
always printing out error message in red, then directing users to the crash log
Merge pull request #241 from shatterednirvana/no-crashlog-on-appscale-exceptions

Not writing a crashlog if AppScaleException is thrown
removed mention of crash from crash log
Merge pull request #242 from shatterednirvana/no-crashlog-on-appscale-exceptions

removed mention of crash from crash log
not using exception.message in crashlog reporting
Merge pull request #243 from shatterednirvana/no-crashlog-on-appscale-exceptions

not using exception.message in crashlog reporting
properly sending over credentials for multinode cloud deployments
added documentation on PARAMS in GCE
removing mysql references from tools (forgot git add earlier)
Merge pull request #245 from AppScale/mysql_tools_removal

removing mysql references from tools (forgot git add earlier)
Merge pull request #244 from shatterednirvana/fixed-multinode-deployment

properly sending over credentials for multinode cloud deployments
creating ~/.appscale if it does not exist when writing crash logs
Merge pull request #246 from shatterednirvana/make-crashlog-dir-if-not-present

creating ~/.appscale if it does not exist when writing crash logs
checking for client_secrets before attempting to use it
added raises section for get_params_from_args, since it raises AgentConfigurationException
not using termcolor in version helper, since it isn't supported on python 2.5
Merge pull request #248 from shatterednirvana/no-termcolor-in-version-helper

not using termcolor in version helper, since it isn't supported on python 2.5
Merge pull request #247 from shatterednirvana/properly-require-client-secrets

Properly require client secrets to be specified
Merge branch 'testing' of github.com:AppScale/appscale-tools into fix-enable-root-login-to-retry