1.1. Digital Rebar Quick Start

This is a TL;DR only! See Deploy Digital Rebar Admin Node for more options.

Don’t like to read? Try our Videos. Training videos 001a, 001b and 001c cover all the information found in this guide in depth.

For this quick start, we will assume SSH access to the install server. The goal is a temporary playground, not a long term install. It is possible to install different operating systems and work by remote or fully automated. We are keeping it very simple in this quick start.

For more on the Web UX that is used extensively throughout this quick start, see Web UX Guide.

Once the server is available and the install step is executed, it should take about 20 minutes in AWS or Packet.net for the system to be ready.

1.1.1. SSH to an Ubuntu Server 16.04 with 8 GB RAM

Note: This quick start focuses on a minimal fast path with Ubuntu 16.04. However, Digital Rebar will run on Centos, RHEL and other distros.

  1. AWS Path:
    1. Create AWS m4.large (or larger!) Ubuntu instance. This can be done with the SSH key or by following these steps:
      1. Login to AWS and click on EC2 under Compute.
      2. Our AWS provider default is US West (Oregon) so that region is recommended for this quick start.
      3. Click on Launch Instance. This will begin the instance set up.
      4. Select 16.04 Ubuntu Server (not 14.04!) for the AMI, then select m4.large or larger. A minimum of 8 Gb of RAM is required.
      5. A minimum of 20 Gb of Disk is recommended. 8 Gb is required.
      6. Next, navigate to the Configure Security Group tab. The “default” Security Group for this server needs Port 22 (ssh), 443 (rebar/HTTPS) and ICMP to be available! This is just our recommended base. Depending on the application, additional ports might be required such as Docker, Chef and Consul. For more on this, see Rebar Admin Node Port Mapping.
      7. Launch the instance and save the .pem key as [key_name].pem to the home directory. This can be done by using the gedit command in the terminal, then copying and pasting the key to the new file.
      8. Modify key permissions using chmod 600 [key_name].pem.
    2. Connect to the server: ssh -i "[key_name].pem" ubuntu@[public_DNS].
  2. Packet.net Path:
    1. Create a Packet Account
    2. Use ssh-keygen -t rsa , cd ~/.ssh , cat id_rsa.pub to generate a required key.
    3. Use the key to create a server.
    4. Now go to Manage>[the project::servers]>[the server::overview]>Console and use the command there to SSH to the server.
    5. Provision at Type 1 Ubuntu Server then follow the B-Y-O-Server steps below.
  3. B-Y-O-Server Path:
    1. Create an Ubuntu Server with the SSH key (16.04 preferred, 8 Gb RAM minimum)
    2. Make sure ports 443, 22 and ICMP are available through the enacted policy.
    3. Connect to the server: ssh root@[ip address]

1.1.2. Install Digital Rebar

In this section only, using SSH is necessary to the target install server. This step adds pre-reqs and then deploys via the deploy/run-in-system command.

  1. Run the Quick Start script

    curl -fsSL https://raw.githubusercontent.com/digitalrebar/digitalrebar/master/deploy/quickstart.sh | bash
    
    1. Troubleshooting Ansible Install "Prereqs" fail: You may have to upgrade Ansible to v 2.1+ yourself
    2. Troubleshooting wait for admin convergence fail: This is just a timeout. The system is generally running but slower than expected.
  2. Using the node’s public IP, open Digital Rebar on your Server via the Digital Rebar UX on https://[public_ip]

    1. The default username and password are rebar and rebar1 respectively.

1.1.3. Add a Provider and Node

In order to maintain simplicity for new users, use cloud servers instead of local VMs or physical servers. The latter two are supported in a more complex setup. This quick start guide covers adding nodes using the New UX.

  1. From the client, log on to the system using https://[external ip address]. Reminders:

    1. Use External IP. This is the same as the SSH address.
    2. Since it is HTTPS, it is required to accept the self-signed SSL certificate.
  2. Add a AWS Provider from the “Providers” page by clicking the add (+) button, located in the bottom right corner:

    1. To Automatically Add AWS credentials, you must have used the AWS CLI on your local system to populate the .aws configuration files.

      curl -fsSL https://raw.githubusercontent.com/digitalrebar/digitalrebar/master/deploy/aws-add-provider.sh | bash -s -- --provider=aws --admin-ip=[external ip address]
      
      1. REMEMBER to set the external IP in the command
      2. You must have AWS credentials stored locally for this script to work
    2. To Manually Add AWS Key (similar steps for Packet or Google)

      1. Add a provider using AWS type and your Credentials.
      2. Choose the same region as the admin is using. Note that the default AMI targets us-west-2. Thus, if a different region is selected, the AMI must also be changed to match (for demo use Centos 7.2+).
      3. Consult Configuring Providers for detailed instructions and troubleshooting including live log review.
  3. Add a node from the “Nodes” and the add (+) button (lower right side)

    1. Pick a name for your node and the provider added above.
    2. You can use the system deployment for now.
    3. Additional instructions can be found at Configuring Providers.
    4. After adding, you can also watch the node being created in your AWS Cloud console.
  4. Allow the system to complete annealing (progress in top right corner).

  5. For troubleshooting help, see Troubleshooting Tips.

Remember to delete used nodes from the Nodes page before taking the system down! There is no automatic cleanup.

For instructions on how to add nodes with the UX, see Nodes.

1.1.4. Workload Wizard to Build a Cluster with RackN UX

We are using a basic Kubernetes as a reference app for this quick install.

  1. Select App Catalog...Kubernetes from the left hand navigation and follow these steps:
    1. Name the deployment. (These names are case sensitive!) If auto-commit is left on, deployment review is skipped. This is recommended for quick start.
    2. The OS is set when the provider is created. (Note: There may only be one.) Do not try System (Physical) Nodes for quick start.
    3. Configure select options. There may be additional options, but only the key ones are exposed in the Wizard. The defaults here are safe.
    4. Select desired nodes and set their roles in the deployment. The defaults are safe here.
    5. Review the JSON that will be submitted to direct the install. The JSON can be edited by clicking the pencil icon in the top right corner.
  2. Watch Digital Rebar build the cluster from the Deployment page or from the Annealer button in the top right corner. For more on the Deployment page and the Annealer, see Deployments and The Annealer respectively. #. Troubleshooting for etcd-install fail.
  3. Login to the cluster from the Master Node using https://[ip of master]/ux (admin/changeme)
    1. Get the IP of the manager from Nodes and look for the address of the node that is assigned as the cluster-master.