1. Introduction
Like any other managed hardware device, you can Activate, Deactivate, Reboot, Update EVE-OS Image, Prepare Poweroff, Off-board, or Delete the Edge Nodes along with updating EVE-OS for better compatibility, increased security, and availability of the latest features with different devices resulting in an enhanced user experience.
Let's now see how to perform different operations on edge applications.
2. Operations using ZEDEDA GUI
After you log in to the ZEDEDA platform, you can perform the following life cycle operations on Edge Nodes. The life cycle operations for Edge Nodes are:
- Activate
- Deactivate
- Reboot
- Update EVE-OS image
- Prepare Power Off
- Off-board
- Delete
You can initiate the above operations from three (3) different options.
Option A: Dashboard
From the dashboard, you can initiate 'Update EVE-OS Image' life cycle operations from the 'Quick Links' widget:
Option B: Edge Node List View
After you log in to the ZEDEDA platform, click on the 'Edge Nodes' link on the left panel, which will take you to the Edge Nodes list view screen.
- Step 1 > Click on the checkboxes to select the Edge Node(s) from the list on which the required operation needs to be performed. You can perform all operations either on single or multiple Edge Nodes.
- Step 2 > Click on the More icon in the top right corner to view the life cycle operations.
You can perform all operations mentioned above from the 'Edge Nodes list view' and 'Edge Node detail view' screens. For simplicity, we will go through all the operations from the 'Edge Nodes list view' screen.
Let's go through the dropdown list operations:
a) Activate
You can activate the Edge Node(s) using the following steps:
- Step 1 > From the dropdown, select 'Activate.' This activates all the selected Edge Nodes.
- Step 2 > A toast message announcing the activate request appears, as shown below.
Activating the Edge Node(s) shows Admin Status as 'Registered' and eventually turns the Run state to 'Online.'
b) Deactivate
You can deactivate the Edge Node(s) using the following steps:
- Step 1 > From the dropdown, select 'Deactivate.'
- Step 2 > Click the 'Deactivate' button on the modal dialogue, which appears as below:
- Step 3 > When you click on the 'Deactivate' button, a toast message appears, as shown below.
Deactivating the Edge Node(s) shows Admin Status as 'Inactive' and Run state as 'Unprovisioned.'
c) Reboot
You can reboot the Edge Node(s) using the following steps:
- Step 1 > From the dropdown, select 'Reboot.'
- Step 2 > Click the 'Reboot' button on the modal dialogue, which appears below.
- Step 3 > When you click the 'Reboot' button, a toast message appears, as shown below.
Rebooting the Edge Node(s) must show Admin Status as 'Active,' and the Run state will eventually become 'Online.'
d) Update EVE-OS Image
Click here to see how to 'Update EVE-OS Image' operation steps.
e) Prepare Power Off
This feature is useful when you need to shut down the set of applications running on EVE-OS gracefully.
You can prepare for the power off of an Edge Node(s) using the following steps:
- Step 1 > Select 'Prepare Power Off' from the dropdown.
- Step 2 > Click the 'Prepare Power Off' button on the modal dialogue, which appears as below.
- Step 3 > When you click on the 'Prepare Power Off' button, a toast message appears, as shown below.
f) Off-board
The off-board feature enables the users to migrate the Edge Nodes across the enterprise retaining the volume instances intact.
Note: Other than the Edge Node default network instance and the user-created volume instances, everything else (edge application instances, manually created network instances, etc.) needs to be deleted before offboarding.
For example, suppose the Edge Node has to be shipped to the low bandwidth customer location. In that case, there will be a delay in downloading the required software (volume instances) and onboarding the Edge Node into the ZEDEDA platform. In such an instance, all the required software is downloaded to the Edge Node and onboarded to a particular enterprise (for example, a manufacturing facility), where bandwidth connectivity is not an issue. This Edge Node is offboarded from the manufacturing facility enterprise and re-onboarded to either the same or another enterprise (with low bandwidth issues).
When a device is offboarded, the identity is NOT lost/wiped. The device is "archived” and does not belong to any tenant while it is archived. When re-onboarded in a new enterprise, the device will register without any extra touch points. However, the device will be onboarded as a "new device"; this means it will lose all the previous configurations.
The re-onboarding workflow is the same as the initial onboarding. The device serial number of the Edge Node must match while re-onboarding. This is the recommended method.
The user can also use the soft serial key to re-onboard. However, this method has its limitations in that the USB stick with the soft serial key may not be available for the users easily.
You can off-board the Edge Node(s) using the following steps:
- Step 1 > From the dropdown, select 'Off-board.’
- Step 2 > Click the 'Off-board' button on the modal dialogue, which appears as below:
- Step 3 > When you click the 'Off-board' button, a toast message appears, as shown below.
g) Delete
Once a device is deleted, its identity is completely wiped from the cloud. If the device needs to be re-onboarded, the identity on the device must be reset. The easiest way to achieve that is by re-imaging it and resetting the TPM.
You can delete the Edge Node(s) using the following steps:
- Step 1 > From the dropdown, select 'Delete.’
- Step 2 > Click the 'Delete' button on the modal dialogue, which appears below.
- Step 3 > When you click on the 'Delete' button, a toast message appears, as shown below.
The 'Delete' operation removes the Edge Node(s) from the list view.
Option C: Edge Node Detail View
Once you are on the 'Edge Nodes' list view page, click on one of the Edge Nodes to view the details page.
Click on the More icon on the top right corner to display the dropdown list that shows similar operations as seen in the Edge Nodes list view.
From ZEDEDA CLOUD release 9.11.0, you can see an additional operation named 'Download LOC Config.' When you click on this operation, the local–operator console (LOC) configuration file from the Edge Node detail page is downloaded to the system.
3. Operations using ZEDEDA CLI
3.1. Activate
You can activate the Edge Node using the following command:
zcli> zcli edge-node activate <name>
3.2. Deactivate
You can deactivate the Edge Node using the following command:
zcli> zcli edge-node deactivate <name>
3.3. Delete
You can delete the Edge Node using the following command:
zcli> zcli edge-node delete <name> [-f]
Note: -f in Reboot and Delete operations are used to forcefully make the delete request to the ZEDEDA without prompting the user.
3.4. Off-board
You can off-board the Edge Node using the following command:
zcli> zcli edge-node offboard [-f] <name>
3.5. Reboot
You can reboot the Edge Node using the following command:
zcli> zcli edge-node reboot [-f] <name>
3.6 Prepare Power Off
You can prepare the power off of an Edge Node using the following command:
zcli edge-node prepare-poweroff <name> [-f]
3.7. Update
You can update the Edge Node using the following command:
zcli> zcli edge-node update <name> [--title=<title>] [--description=<description>] [--tags=<key:value>...] [--project=<project>] [--clear-onboarding-certs] [--config=<key:value>...] [--network=<network>...] [--network-tag=<key:value>...]
3.8. Update EVE-OS image
You can update the EVE-OS image of the Edge Node using the following command:
zcli> zcli edge-node eveimage-update <name> --image=<image> [--activate]
3.9. Remove the EVE-OS image
You can remove the EVE-OS image of the Edge Node using the following command:
zcli> zcli edge-node eveimage-remove <name> --image=<image>
3.10. Get-config
You can get the configuration of the Edge Node using one of the following commands:
zcli> zcli edge-node get-config <name> [--offline] [--summary] [--next]
zcli> zcli edge-node gen-config <name>
3.11. Get-PCR Values
You can get the PCR values from the Edge Node using the following command:
zcli> zcli edge-node get-pcr <name>