-####TODOS:
-- Integrate with the maven-based template expansion.
-- Integrate with maven-based Docker build and push to LF Docker repo
-- Add full list of plugins to be installed onto CM
-- Separate the Docker stuff from the non-Docker installation. (The blueprints are common to both methods.)
-- Get rid of any AT&T-isms
-- (Maybe) Move the installation of the Cloudify CLI and the sshkeyshare and dnsdesig plugins into the Dockerfile,
-so the image has everything set up and can just enter the vevn and start the Centos VM installation.
-- Figure out what (if anything) needs to change if the container is deployed by Kubernetes rather than vanilla Docker
-- Make sure the script never exits, even in the face of errors. We need the container to stay up so we can do uninstalls.
-- Figure out how to add in the deployments for the rest of the DCAE platform components. (If this container deploys all of DCAE,
-should it move out of the CCSDK project and into DCAE?)
-- Figure out the right way to get the Cloudify OpenStack plugins and the Cloudify Fabric plugins onto CM. Right now there are
-handbuilt wagons in the Nexus repo. (In theory, CM should be able to install these plugins whenever a blueprint calls for them. However,
-they require gcc, and we're not installing gcc on our CM host.)
-- Maybe look at using a different base image--the Ubuntu 16.04 image needs numerous extra packages installed.
-- The blueprint for Consul shows up in Cloudify Manager with the name 'blueprints'. I'll leave it as an exercise for the reader to figure why
-and to figure out how to change it. (See ~ line 248 of installer-docker.sh-template.)