[UX enhancements] amp cluster create

[JosephGJ]

ref: #1216

amp cluster create command improvements to the user experience:

• Should display the number of managers and workers
• Should display clear status about cluster nodes deployment (Creating/Created)
• Should display clear status about AMP deployment
  • Pulling required images
    • Trim down output from pulling image
    • If a problem occurs, exit with a suggestion on how to fix it
  • Starting amp stack shouldn’t be this detailed for common user
    • Just printing dots should be enough while we’re starting amp services and check their health.
• If the certificate creation fails, the command should exit with a clear error message and must not continue by deactivating the amp-proxy (which is the case today)
• After a successful AMP deployment:
  • A clear report stating that amp is running should be printed in green.
  • The WebUI address should be displayed so that the user can connect to it
  • The user should be told to create a user to continue with the appropriate command line.
• CLI options should be synchronized with deploy and bootstrap script options.
• We should have a way to provide secrets as CLI parameters for deployment:
  • Sendgrid key
  • Token secret key

Example output:

$ amp cluster create
[localhost:50101]
Creating cluster on localhost using local swarm with 1 manager(s) and 0 worker(s).

Pulling Images:
Image appcelerator/amp-bootstrap:0.10.1 has been successfully pulled.

Deploying Cluster:
Manager node(s) ready.
No worker node.

Cluster has been successfully created.

Deploying AMP:

Pulling Images:
Image appcelerator/amp-ui:0.10.1 has been successfully pulled.
Image appcelerator/agent:0.10.1 has been successfully pulled.
Image appcelerator/ampbeat:0.10.1 has been successfully pulled.
Image appcelerator/amplifier-gateway:0.10.1 has been successfully pulled.
Image appcelerator/amplifier:0.10.1 has been successfully pulled.
Image appcelerator/elasticsearch-amp:5.3.2 has been successfully pulled.
Image appcelerator/amp-nats-streaming:v0.3.8 has been successfully pulled.
Image appcelerator/etcd:3.1.6 has been successfully pulled.
Image appcelerator/kibana:5.3.1 has been successfully pulled.
Starting services:
Service amplifier has been successfully started.    
Service amplifier-gateway has been successfully started.
Service agent has been successfully started.
Service elasticsearch has been successfully started.
Service nats has been successfully started.
Service etcd has been successfully started.
Service ampbeat has been successfully started.
Service kibana has been successfully started.
Service proxy has been successfully started.

AMP has been successfully deployed.
See `amp user signup --help` in order to create your first user.
Read the documentation here https://github.com/appcelerator/amp/tree/master/docs. 
The web portal is accessible at https://ui.local.appcelerator.io/

[JosephGJ]

Add log levels to deploy + bootstrap script outputs so that they can be filtered via some "log level" (similar to infrakit). These can then be synchronized with the CLI errors.

Infrakits log levels (each step up includes the previous logs).

• 0 = no logs
• 1 = critical errors
• 2 = errors, most failing cases in the scripts
• 3 = warnings
• 4 = information, output only a user would want to see (e.g. "bootstrapping cluster", "Managers deployed: 2" etc...)
• 5 = debug mode, all of the output from the scripts
• default = 4

for example:

$ amp cluster create --provider=docker --log=4
[DEBUG]: creating Docker volume "some volume id" with the configuration data
[INFO]: Bootstrapping cluster on docker
[WARN]: warning: force start, removing Docker volume "some volume id"
[ERROR]: asking for -5 manager(s) and -1488 worker(s), abort

There needs to be a better definition between what a critical error is and what a regular error is

[JosephGJ]

amp cluster command ux enhancements are going to be put on hold whilst the method of cluster deployment is being modified to use golangs AWS sdk.