1.1. Quick Start

This quick start guide provides a streamlined self-trial installation via systemd on Mac OS, Linux OS, Linux VMs and Cloud Servers. Many advanced options are including air-gap, local UX, using another DHCP are available but outside of this scope.

We recommend consulting the video guide of this process during the installation and our advanced features showcase.

Most Digital Rebar environments require knowledge of your network and DHCP environment. Cloud and fully Virtual environments generally require less networking knowledge.

Other installation paths:

This graphic shows the basic layout for a quick start system:

Basic layout for a Digital Rebar Quick Start

1.1.1. Prepare Your Environment

This quick start guide will install the latest stable release of Digital Rebar onto a Linux or MacOS system as a systemd service running on port 8092 (these Ports are used by default).

For a quick trial, we recommend using a dedicated Virtual Machine using host only networking on one interface for your trial.

  • Linux or MacOS system (we recommend Centos 8, Windows is not supported)
  • 4 Gb of RAM (minimum)
  • 20 Gb of Disk Space (60 Gb is better because some O/S installation ISOs require much more space)
  • Access to the internet to download components (not a requirement for production systems)
  • Provisioning network without a DHCP server (Digital Rebar will provide DHCP by default)

If you are concerned about installing Digital Rebar as a service, please review our Developer Install (Console Isolated) guide to run it isolated in a single directory.

You must install Digital Rebar to use it, there is no SaaS version. Why do I have to install Digital Rebar locally?

1.1.2. Install Digital Rebar Endpoint

To begin, execute the following commands in a shell or terminal:

curl -fsSL get.rebar.digital/stable | bash -s -- install --systemd --version=stable

The command will download the stable Digital Rebar (the systemctl service name is dr-provision) bundle and checksum from github, extract the files, verify prerequisites are installed, and create needed directories and links under /var/lib/dr-provision. The --systemd and --version flags included for clarity, they are not required for this install.

The install script used by our installs has many additional options including remove that are documented in its help and explored in other install guides.

Once the installation script completes, a Digital Rebar endpoint will be running your local system!

1.1.3. Open the RackN UX & Trial License

All Digital Rebar operations are securely local and behind your firewall. RackN never has direct access to your DRP endpoint.

The Digital Rebar UX is hosted at RackN as a convenience for new users. RackN does not have access to your data, credentials or provisioning APIs because The RackN portal runs as a single-page app locally in your browser so all DRP API calls remain behind your firewall.

To start, open new Digital Rebar API:


You will be redirected to the RackN Portal UX after you visit the Digital Rebar API port and accept the self-signed certificate generated by the installation.

Then login Digital Rebar:

username: rocketskates
password: r0cketsk8ts

After login, you will be promoted to create and download a extendable self-trial license that enables most enterprise feature of Digital Rebar. If you save the generated license file then you’ll be able to use it to bypass this process in the future.

1.1.4. UX System Bootstrap Wizard

On the top left section of the Info & Preferences page, the RackN Portal shows the steps needed to create a fully operational Digital Rebar endpoint.

A quick start system will have some initial configuration already done. Work through the bootstrap check list until all items have green check marks. The final Machines step requires actions outside of Digital Rebar, consult Provision a Machine for assistance.

If you prefer command line actions over a UX, all of the UX Wizard steps can also be performed using the steps below.

1.1.5. CLI System Bootstrap (optional)

These Digital Rebar Provision Command Line Interface (CLI) bootstrapping steps include the ones suggested by the install script.

To use DRPCLI, you need to set the target endpoint and credentials. This can be done per call using command line flags; however, most users prefer to set environment variables for this purpose.

export RS_ENDPOINT=https://<ip_address_of_your_endpoint>:8092/
export RS_KEY=rocketskates:r0cketsk8ts

First, set a more secure password for your endpoint.

drpcli users password rocketskates $mypass
export RS_KEY=rocketskates:$mypass

Next, upload the discovery O/S (aka “sledgehammer”) and set the defaults to use it.

drpcli bootenvs uploadiso sledgehammer
drpcli prefs set defaultWorkflow discover-base unknownBootEnv discovery

Note that drpcli bootenvs uploadiso command is a helper command that combines two common steps: it fetchs the ISO referenced ISO in the bootenv from the internet and then uploads the ISO to Digital Rebar. If you perform these steps many times, we recommend storing the downloaded ISO media locally and then uploading it using drpcli isos upload.

Next, define the provisioning Subnet in Digital Rebar DHCP. Since you _must_ include all of the necessary DHCP boot options to correctly PXE boot a Machine; we recommend using the UX to create Subnets because it has logic to determine sane defaults.

The following command line example contains the JSON Subnet and DHCP definitions. You MUST modify the network parameters to match your environment.

#  EXAMPLE - please modify the below values according to your environment  !!!

echo '{
  "Name": "local_subnet",
  "Subnet": "",
  "ActiveStart": "",
  "ActiveEnd": "",
  "ActiveLeaseTime": 60,
  "Enabled": true,
  "ReservedLeaseTime": 7200,
  "Strategy": "MAC",
  "Options": [
    { "Code": 3, "Value": "", "Description": "Default Gateway" },
    { "Code": 6, "Value": "", "Description": "DNS Servers" },
    { "Code": 15, "Value": "example.com", "Description": "Domain Name" }
}' > /tmp/local_subnet.json

vim /tmp/local_subnet.json

drpcli subnets create - < /tmp/local_subnet.json

Finally, install one of these popular trial operating systems.

drpcli bootenvs uploadiso ubuntu-20.04-install # optional, requires at least 3G of free space
drpcli bootenvs uploadiso centos-8-install # optional, requires at least 30G of free space

We recommend reviewing the UX System Bootstrap Wizard to ensure that all steps have been completed.

1.1.6. Provision a Machine

Create network bootable virtual machine (physical machines on the DHCP network will work too):

  • with at least 2 Gb of RAM (4 Gb is preferred)
  • set to network boot first
  • attached to Digital Rebar provisioning network (aka Layer 2 subnet)

Power on the machine! No further action is required.

The machine should boot in to the Sledgehammer discovery operating system. Typically, the machine console looks like (the version signature may differ):

Digital Rebar: Sledgehammer ###................................####
Kernel 3.10.0-693.21.1.el7.x86_64 on an x86_64

d0c-c4-7a-e5-48-b6 login:

After the boot is complete, the UX Machines page should show the newly discovered machine.

If you have installed another operating system ISO besides Sledgehammer, then you can now provision an operating system by setting the target workflow on the machine:

  1. select the target machine (indicated with a check in the left most box)
  2. select the target workflow from the action list at the top of the page (typically centos-base or ubuntu-base)
  3. press the “Run Workflow” button (looks like a play icon next to the workflow list)

You should see immediate updates to the machine’s stages and tasks as Digital Rebar processes the workflow.

After installation completes, you can quickly return to Sledgehammer by running the discover-base workflow.

1.1.7. Advanced Features Catalog (next steps)

Digital Rebar is capable of automated workflow management of the boot process, power control, and much more. This quickstart walks through the simplest process to get you up and running with a single test install. Please review the rest of the documentation for further configuration details and information on automation of your provisioning environment.

The UX Catalog contains a list of available extensions to Digital Rebar that are avaible for installation. Choosing an item from the Catalog will automatically download and install the capability. All items run locally in your Digital Rebar endpoint, no connection to RackN is required after the download.

Fully automated provisioning control requires use of plugins for Power Management actions. These are done through the IPMI subsystem, with a specific IPMI plugin for a specific environments. Some existing plugins exist and are documented in Environment Setup Instructions.

1.1.8. Clean Up

Once you are finished exploring Digital Rebar, you can uninstall the service

curl -fsSL get.rebar.digital/stable | bash -s -- remove

Note that remove will not remove the data files stored in /var/lib/dr-provision, /etc/dr-provision, or /usr/share/dr-provision. Include the --remove-data flag for a full clean-up.