Retail Workload Orchestrator is a ZeroConfig Technology enable edge devices to scale like Lego blocks. It is the set of open source services used to enable autonomous horizontally scaling of edge devices services to support Workload Orchestration. As application workloads demand more resources, add Intel x86 hardware as Lego building blocks to the infrastructure. Simply plug a machine into the network and walk away; the new system will auto configure itself, join the cluster and become an available resource for the application workloads. This ZeroConfig architecture can provide high availability, distributed workloads, workload affinity to specific hardware, upgrade hardware with 24/7 uptime, and more. The ZeroConfig architecture can simultaneously run Linux, Windows and Android applications across a heterogeneous infrastructure on Intel x86 Architecture from Celeron to Xeon in the same compute environment.
- Scaling vertically can be very expensive, limiting and still be a single point of failure; instead scale horizontally and start with commodity hardware.
- To scale horizontally on heterogeneous x86 hardware from Intel Celeron to Xeon.
- To provide the ability to use existing hardware and provide a migration path to new hardware with near 100% uptime.
- To provide high availability with heterogeneous x86 hardware.
- To provide software abstraction from multiple nodes.
RWO version components:
- Hashicorp Serf version 0.8.4
- Device discovery and event driven orchestration
- RedHat GlusterFS version 5.10
- Persisted file storage
- GlusterFS Plugin version 1.0
- Docker volume plugin
- Docker Swarm version 19.03.0
- Dynamic Hardware Orchestrator
- Dynamically discovers the state of the hardware or VM resources
- Alpine Console
- Management Console
- Install Docker Compose
mkdir -p /usr/local/bin
wget -O /usr/local/bin/docker-compose "https://github.com/docker/compose/releases/download/1.24.0/docker-compose-$(uname -s)-$(uname -m)"
chmod a+x /usr/local/bin/docker-compose- Clone this project to /opt/rwo
cd /opt
git clone https://github.com/intel/RetailWorkloadOrchestrator.git rwo- Build the container images
cd /opt/rwo
./build.sh- Install Demo Keys. NOTE: These keys are published and should be used for demonstration purposes only. Please refer to the Production Installation section to genereate unique keys.
./install.sh demo- Start RWO
systemctl start rwo- Confirm all services are running. (It will take 2 minutes for all services to start)
docker ps- Enter the RWO Console
docker exec -it rwo_console_1 bash- Install Portainer.io Management
curl -L https://downloads.portainer.io/portainer-agent-stack.yml -o portainer-agent-stack.yml
docker stack deploy --compose-file=portainer-agent-stack.yml portainer-
Get the IP address of this a node and connect to Portainer at :9000. Create a username and password. Once logged in go to the "Swarm" link on the left navigation panel.
-
On another node repeat steps 1 through 4. From Poratiner UI refresh the Swarm page to watch an aditional node be added.
Prerequisites:
- x86 Hardware or x86 Virtual Machine
- At Least 5 GB of Disk Space
- 4 GB of RAM
- Linux Distro that supports Docker
docker18.06.x or greaterdocker-composev1.23.2 or greaterbashv4.3.48 or greater
NOTE: SSH Service is not required as RWO will create one. If SSH Service is running on Port 22 on the host you must add "PORT=(some alternate port number)" to /opt/rwo/compose/docker-compose.yml under the 'console:' service environment virables. The option is to change the default Port number on the host.
For steps to build and install. See this
- Clone this project to /opt/rwo
cd /opt
git clone https://github.com/intel/RetailWorkloadOrchestrator.git rwo- Build the container images
cd /opt/rwo
./build.sh- Push all RWO images to your Docker Registry.
edge/glusterfs-plugin
edge/dxo
edge/app-docker
edge/dho
edge/serf
edge/glusterfs-rest
edge/console-alpine
-
Update compose/docker-compose.yml images to reflect your registry path.
-
Generate RWO Certifcates and Keys. NOTE: All Certifcates and Keys must be copied to all other nodes you plan to join this node. For more details, please refer to https://github.com/intel/RetailWorkloadOrchestrator/blob/master/docs/02_Security.md
./generate_keys.sh- Install
./install.sh- Start RWO
systemctl start rwoRetail Workload Orchestrator uses hashicorp serf for service discovery. Encryption with AES-256 is enabled for serf v0.8.4.
The AES-256 key is to be kept in a keyring file in json format.
keyring.json
[
"HvY8ubRZMgafUOWvrOadwOckVa1wN3QWAo46FVKbVN8="
]
This is a symmetric key which needs to be same in all the nodes of a cluster, only then serf will be able to discover them.
For Details. See this.
Security in Retail Workload Orchestrator is taken care of by using PKI architecture and root privileges. Various components of Retail Workload Orchestrator talk to each other either over https or they use docker-volumes/filesystem location protected by root privilege. Glusterfs is also secured using PKI.
For Details. See this.
There are Environment variables defined in /opt/rwo/compose/docker-compose.yml.
- SWARM_RESTORE_TIME_IN_SECONDS : Number of seconds RWO handlers need to wait for a swarm restore to happen after a member leaves the cluster or reboot itself.
- MEMBER_REBOOT_TIME_IN_SECONDS : Number of seconds RWO handlers need to wait for a member to complete its reboot.
- LOG_LEVEL : Specifies different levels at which logs needs to be printed. LOG_LEVEL=1 prints info level log statements. LOG_LEVEL=2 prints debug level log statements.
- Rarely
glustercluster formation may fail and node may not be able to join the cluster, in that case, go ahead run /opt/rwo/bin/reset and reboot. Resetting RWO will wipe out all its state. - Dynamic Hardware Orchestrator (DHO) Currently only detects system state at startup. Does not continuosly check state.