Cloud

Login

Login to Berlioz account. Remote region should be specified. Command would accept username and password from interactive shell.

$ berlioz login

For integration with CI/CD tools login can accept username/password combination as input arguments:

$ berlioz login --user <username> --pass <password>

Build Images

Builds docker images. Run from project directory.

$ berlioz build

Push Images

Builds docker images and uploads them to cloud registry. Run from project directory. No need to run berlioz build beforehand.

$ berlioz push --region <region>

Run

Triggers cloud deployment. Use berlioz status and berlioz wait to monitor deployment process.

$ berlioz run --region <region> --deployment <deployment> --cluster <cluster>

Deploy

Convenience command to build & push images, as well as to trigger deployment. Should be called from project directory.

$ berlioz deploy --region <region> --deployment <deployment>

Status

Checks deployment status

$ berlioz status --region <region> --deployment <deployment>
┌──────────────────────┬──────────────────────┬─────────────┬────────────────┬────────────┐
│ Deployment           │ Cluster              │ Region      │ Desired State  │ Status     │
├──────────────────────┼──────────────────────┼─────────────┼────────────────┼────────────┤
│ gprod                │ addr                 │ us-west1-c  │ undeploy       │ completed  │
├──────────────────────┼──────────────────────┼─────────────┼────────────────┼────────────┤
│ gprod                │ hello                │ us-west1-c  │ deploy         │ completed  │
├──────────────────────┴──────────────────────┼─────────────┴────────────────┴────────────┤
│ gprod                │ berlioz              │ us-west1-c  │ deploy         │ completed  │
├──────────────────────┼──────────────────────┼─────────────┼────────────────┼────────────┤
│ gprod                │ sprt                 │ us-west1-c  │ deploy         │ completed  │
└──────────────────────┴──────────────────────┴─────────────┴────────────────┴────────────┘

Statuses:

Status Description
completed All operations are completed
processing Deployment is in process
waiting Deployment is waiting for dependent resources to be provisioned (K8s cluster, SQL database, etc.)
resovering In case of errors like API threshold limit, recovering indicates cool off period before retrying
failed Unrecoverable error happened. Status command would show error details. Once the condition is resolved restart the deployment using berlioz run –force command.

Undeploy

Following command terminates deployment. Use berlioz status and berlioz wait to monitor deployment process.

$ berlioz stop --deployment <deployment> --cluster <cluster> --region <region>