Cloudbreak Deployer helps to deploy a Cloudbreak environment into Docker containers. For recent changes please check the CHANGELOG.md.
Currently only Linux and OSX 64 bit binaries are released for Cloudbreak Deployer. For anything else we will create a special Docker container. The deployment itself needs only Docker 1.7.0 or later.
To install Cloudbreak Deployer, you just have to unzip the platform specific single binary to your PATH. The one-liner way is:
curl https://raw.githubusercontent.com/sequenceiq/cloudbreak-deployer/master/install | sh && cbd --version
cbd will generate some config files, and will download supporting binaries. It is advised that you create a dedicated directory for it:
mkdir cloudbreak-deployment
cd cloudbreak-deployment
First initialize your directory by creating a Profile file:
cbd init
It will create a Profile file in the current directory. The only required
configuration is the PUBLIC_IP. This IP will be used for the Cloudbreak UI
(called Uluwatu). In some case the cbd tool tries to guess it, if can't than will give a hint.
To start all the containers run:
cbd start
At the first time it will take more time, as it does additional steps:
- download all the docker images, neded by Cloudbreak.
- create docker-compose.yml: Full confirguration of containers needed for Cloudbreak deployment.
- create uaa.yml: Identity Server configuration. (For example default user/password in the last line)
cbd logs
All Cloudbreak components and the backend database is running inside containers.
The pull command is optional but you can run it prior to cbd start
cbd pull
It will take some time, depending on your network connection, so you can grab a cup of coffee.
If you check the output of cbd env you can see the default principal/credential combination:
- user: admin@example.com
- password: cloudbreak
These values are generated in the uaa.yml end section. To change these values, add 2 lines into your Profile:
export UAA_DEFAULT_USER_EMAIL=myself@example.com
export UAA_DEFAULT_USER_PW=demo123
and than you need to recreate configs:
rm *.yml
cbd generate
In order to be able to assume roles on AWS you need to set up your AWS keys in the Profile file:
export AWS_ACCESS_KEY_ID=AKIA**************W7SA
export AWS_SECRET_ACCESS_KEY=RWCT4Cs8******************/*skiOkWD
If you do not have plans to launch clusters in AWS, then you can safely skip these settings.
For more details regarding accounts please check Cloudbreak documentation.
If you want to have more detailed output set the DEBUG env variable to non-zero:
DEBUG=1 cbd some_command
You can also use the doctor command to diagnose your environment:
cbd doctor
The tool is capable to upgrade itself to a newer version.
cbd update
This tool, and the PR driven release, is inspired from glidergun. Actually it could be a fork of it. The reason it’s not a fork, because we wanted to have our own binary with all modules built in, so only a single binary is needed.