WARNING WARNING WARNING: This is the Digital Rebar v2 product documentation. The v2 version is EOL as of September 2017. Please refer to the new Digital Rebar Provision v3 documentation:

1. General Installation

Workloads require a specific set of roles to be included in the Digital Rebar server before they can run. Make sure that the server has been started with these roles in place. We are actively making it easier to add roles, so workload scripts will soon be able to upload the needed roles as part of their installation.

All workload scripts leverage the Digital Rebar annealer (see Simulated Annealing) to coordinate work. That means that all of the requested tasks are loaded into the system as quickly as possible: generally as soon as the node placeholders appear but before they are fully provisioned. Once the work has been queued, the scripts have completed their function. By default, the scripts will appear to continue acting as they monitor the annealer. During this time, users could stop the script and login to Rebar to monitor progress themselves.

To install the required workloads, the Digital Rebar Deploy infrastructure is needed:

mkdir ~/digitalrebar
cd ~/digitalrebar
git clone digitalrebar/deploy

Make sure to open the correct port, see Rebar Admin Node Port Mapping.

If AWS provider credentials have been added to DR Info File (.dr_info), then a Kubernetes workload can be deployed as follows (see Kubernetes Workload for more details):

cd ~/digitalrebar/deploy
workloads/ --deploy-admin=aws --provider=aws --deployment-name=rebarrocks

Read more about Workload Parameters or use --help to get a full list of parameters.

1.1. Developer Notes

The remote install and workload scripts do NOT play well with doing local development using Developer Server (docker-admin). Create a second deployment clone if tools/docker-admin is being useed because it takes over the ../deployment directory.