digitalrebar / edgelab Goto Github PK

Materials to build and deploy a simple Edge Lab for demonstration, training and development

License: Apache License 2.0

HCL 28.33% Shell 71.67%

edgelab's Introduction

END OF LIFE NOTICE FOR VERSION 2.x

Version 2 of Digital Rebar is no longer being maintained. All development has shifted to v3 (Digital Rebar Provision) which is being actively supported. If you need help migrating, please contact RackN for assistance.

Ref: https://github.com/digitalrebar/provision

Welcome to Digital Rebar

The Digital Rebar is a container-ready cloud & hardware provisioning platform that delivers the best of software deployment automation and orchestration without locking you into a single platform or operating system. Our mission is to embrace the heterogenous nature of cloud and data center operations.

While it's been completely rebuilt by DevOps artisans, Digital Rebar history includes years of battle-tested ops learnings by the Crowbar Project founders.

Getting Started & Documentation

Documentation is maintained in Read The Docs and sourced from our doc repository.

Help & Community

Help & Chat
- Gitter: ![Gitter](https://badges.gitter.im/Join Chat.svg)
Documentation
Live Weekly Planning and Design Meetings
Mailing List

Commercial support for Digital Rebar is available from RackN Inc.

Codebase History

Fall 2016: Digital Rebar / DigitalRebar converged into single repo + workloads.
Summer 2015: Digital Rebar / Core (and many repos) restructured into microservice containers
Fall 2013: OpenCrowbar Rearchitecture (v2) was a complete re-write of Crowbar to be composable
Spring 2011: Original Project: Crowbar (still maintained by SUSE) was a Chef wrapper layer

Dangerous and Fun Quick Start command.

We know you'll ignore this advice, but we recommend that you Read The Docs Deployment Install Guide first!

WARNING: This is only for clean systems. If you've already cloned this repo, use the run-in-system script!

From the home directory of a user with sudo capabilities,

curl -fsSL https://raw.githubusercontent.com/digitalrebar/digitalrebar/master/deploy/quickstart.sh | bash

This command will turn the current node into a DigitalRebar admin node in Host mode operating as the IP on the default gateway interface. For cloud instances, this means that it will use the private network and will only safely manage nodes in its private network. UX and API will be available through the public IP of the cloud instance assuming https is allowed through the cloud's network protections.

You may add additional arguments to bash to enable features or change the IP address that ADMIN node will use.

E.g. curl -fsSL https://raw.githubusercontent.com/digitalrebar/digitalrebar/master/deploy/quickstart.sh | bash -s -- --con-provisioner --con-dhcp --admin-ip=1.1.2.3/24

will enable the dhcp server and provisioner for the admin node. You will need to edit the admin-internal network to boot nodes properly. This would also set the admin-ip to 1.1.2.3/24 in the configuration files. This last part is needed if you are using an AWS or google instance and you want to use your admin node for things not directly in your VPC/Network.

NOTE: When enabling the provisioner, you will need about 20GB of disk space. Plan accordingly.

edgelab's People

Contributors

Stargazers

Watchers

Forkers

sangam14 kscarlett natejswenson forkkit deepandy seenureddy xujintao1996 cedricmc cwdrunner raviseerapu jt3kt cybercorey bradleya ezajko vusonbmt alannyuma

edgelab's Issues

Fetch rpi4 iso

Fetch rpi4 iso sledgehammer-xxx56.rpi4.tar

Following EdgeLab Bootstrap instructions I ran into an issue where the EdgeClient rpi4's looked like they attempted to boot but did not come up in the discovered machines. This is how I figured out that the rpi4 was complaining about and how I figured out / remembered how drp discovery worked.

Steps

Following EdgeLab Bootstrap I got to step 6.
Using the video monitor and keyboard on edgelab-server rpi4 I found the start_me.sh in the root home directory and ran the following:

root@ubuntu:~# ./start_me.sh [Wifi SSID] [Wifi Password]

Step 6 warned I may need to run this again, which I did. It complained about drp already running so I went to IP found on wlan0. https://192.168.2.170:8092
Got the normal redirect to https://portal.rackn.io/#/e/192.168.2.170:8092
Went to Machines which only had one with no workflow. The name was the mac of the endpoint and BootEnv was local.
Went to Leases I did see 2 IP's with tokens that I assumed were the rpi4 I expected to see in machines.
I reset the edgelab-client rpi4's via unplug and plug usb-c power.
The edgelab-client showed network activity as expected, but did not show up in machines. After awhile, the edgelab-client GreenLED did a 7 flashes: kernel.img not found sequence ( see Pi4-Powerup LED TroubleShoot ).
Rob's tour of the rpi4 mods View video time here pointed out to me that maybe I'm missing sledgehammer-xxx56.rpi4.tar
I went to Boot Environments clicked on discovery found the rpi4 IsoUrl
I went back to isos clicked Upload and gave the URL to fetch.
The sledgehammer-xxx56.rpi4.tar appeared in isos.
I power cycled the edgelab-client rpi4 again.
Happiness! The Machines appeared!

Notes

sledgehammer-xxx56.rpi4.tar

Finding IP on edgelab-server

root@ubuntu:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen  
  ...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
 ...
    inet 10.3.14.1/24 brd 10.3.14.255 scope global eth0
 ...
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
 ...
    inet 192.168.2.170/24 brd 192.168.2.255 scope global dynamic wlan0
 ...
root@ubuntu:~#

root@ubuntu:~# drpcli catalog item install edge-lab --version=tip 

root@ubuntu:~# drpcli machines list
[
  {
    "Address": "",
    "Arch": "amd64",
    "Available": true,
    "BootEnv": "local",
    "Bundle": "BackingStore",
    "Context": "",
    "CurrentJob": "",
    "CurrentTask": 0,
    "Description": "",
    "Endpoint": "",
    "Errors": [],
    "HardwareAddrs": [],
    "Locked": false,
    "Meta": {
      "feature-flags": "change-stage-v2"
    },
    "Name": "dc-a6-32-63-e7-bd",
    "OS": "",
    "Params": {},
    "Partial": false,
    "Profiles": [],
    "ReadOnly": false,
    "Runnable": true,
    "Secret": "Z1kQcs4HlEfEUL-V",
    "Stage": "none",
    "Tasks": [],
    "Uuid": "69e85dab-230e-4647-a9cf-7e4f134ce66c",
    "Validated": true,
    "Workflow": ""
  }
]

root@ubuntu:~# drpcli isos list
[
  "sledgehammer-9b5276ac5826520829aa73c149fe672fe2363656.arm64.tar.part",
  "sledgehammer-c7305a9ba2c6b12351530c4a9021fd5e07ef1ce1.amd64.tar"
]

Download or Fetch [sledgehammer-xxx56.rpi4.tar](http://rackn-sledgehammer.s3-website-us-west-2.amazonaws.com/sledgehammer/9b5276ac5826520829aa73c149fe672fe2363656/sledgehammer-9b5276ac5826520829aa73c149fe672fe2363656.rpi4.tar) iso to the edgelab-server endpoint

root@ubuntu:~# drpcli isos list
[
  "sledgehammer-9b5276ac5826520829aa73c149fe672fe2363656.arm64.tar.part",
  "sledgehammer-9b5276ac5826520829aa73c149fe672fe2363656.rpi4.tar",
  "sledgehammer-c7305a9ba2c6b12351530c4a9021fd5e07ef1ce1.amd64.tar"
]

eeprom update

So, I ran into an issue with 'fresh from factory pi'
Both the server and client boots look like the started but never 'seemed' to finish.