1. Introduction
ZEDEDA supports remotely managing the compute hardware running LF Edge/Edge Virtualization Engine (EVE-OS) software. The compute hardware can either be an ARM or an Intel CPU device. Typically, these devices can be of many forms, such as standard IoT Gateway, Industrial PCs, Single Board Computing boards, rack-mount servers, or desktop servers. In ZEDEDA, any device with EVE-OS software installed is called an 'Edge Node.' Each Edge Node belongs to a resource group or 'Project.'
ZEDEDA platform defines a project as a resource group that allows you to manage a group of Edge Nodes as one logical entity. Given an Edge Node can be part of only a single project, the project's properties can apply to all the Edge Nodes in that project. We recommend (though not mandatory) similar Edge Nodes in every project because bulk operations can be performed easily.
Edge Nodes require standard object-level attributes like the name–which has to be unique, and the title–can be changed later. The illustration below shows the typical Edge Node hosts the EVE-OS software to orchestrate cloud-native and/or legacy IoT applications.
2. Concepts related to Edge Nodes
2.1. Project
Project is the logical grouping of Edge Nodes. Edge Node can be a part of only one project. An enterprise may have multiple projects. The project can be a Regular project or a specific type like 'Azure.' In Azure, some default apps are deployed automatically as soon as a new edge node is added to a project.
The project requires standard object-level attributes like the name, which must be unique, and the title, which can be changed later. Depending on the type of project, other project-related attributes are configurable.
2.2. Models
ZEDEDA provides pre-created models to define the physical hardware attributes of the Edge Nodes. Models have the following attributes.
-
Resource capacity for memory, storage, and CPU,
-
Type of CPU–if it's an ARM device or x86 device.
-
The model also describes what physical interfaces or ports are available on the device.
-
The hardware bus interfaces and numbers are also captured.
2.3. Status and State
In ZEDEDA, each Edge Node has an Admin Status and a Run State.
The operator controls the Admin Status. As part of the Edge Node create a workflow, the newly created Edge Node will be in the 'Inactive' status. Once the operator activates the Edge Node, the 'Admin Status is moved from 'Inactive' to 'Active' status. At this point, the Edge Node calls back to ZEDEDA CLOUD and presents its credentials. ZEDEDA platform, after verification of credentials, moves the device from 'Active' status into a 'Registered' state.
The Run State mainly shows the current state of the Edge Node, whether online or in error. It also depicts the other Run States like provisioned, unprovisioned, suspect, etc. ZEDEDA platform, after verifying the actual state of the Edge Node, moves it to a particular state.
2.4. Onboarding
Edge Nodes can be onboarded using multiple ways. Depending on the onboarding options, the Admin Status might be affected.
Option A: Upload Edge Node Certificate
One can onboard the Edge Node using the Trusted Platform Module/Hardware Security Module (TPM/HSM) backed device certificate. If you use this method, you need to extract the device certificate from the Edge Node after it is first installed. The device automatically goes into a 'Registered' Admin Status if you use this method.
Option B: Onboarding Key
To use the onboarding key, one of the below methods can be used to get the required serial number:
-
Hardware Serial Key
We use the hardware-based serial number provided with the Edge Node in this method. Assuming that the serial number is programmed into the DMI table of the Edge Node and the EVE-OS software interprets it.
-
Software Serial Key
In this method, the software serial key is dynamically generated on the platform by EVE-OS instead of using the software serial number available when the EVE-OS is installed on the hardware.