Description of problem:

For users updating the cumin package on top of an existing install, the MCIG should suggest that they run "cumin-admin upgrade-schema" instead of "cumin-database install".  The latter will tell them that the database is already installed and will do nothing, the former *may* be required for cumin to run after the update.

There won't always be schema changes in a release, but if there are and the upgrade command is not run the service will fail on start up with messages in the log files noting that the upgrade should be run.  The command will return with "nothing to do" if there is indeed nothing to do.