Help Center/ Intelligent EdgeFabric/ Service Overview/ Constraints
Updated on 2024-09-05 GMT+08:00
View PDF
Share

Constraints

Edge Node Specification Requirements

An edge node can be a physical device or a virtual machine (VM). It must meet the specifications described in Table 1.

Table 1 Edge node requirements

Item

Specifications

OS

The language of the operating system must be English.

  • x86_64 architecture

    Ubuntu LTS (Xenial Xerus), Ubuntu LTS (Bionic Beaver), CentOS, EulerOS, RHEL, Kylin, NewStart CGS Linux, NeoKylin, openEuler, Unity Operating System (UOS), Oracle Linux (OL), Huawei Cloud Euler (HCE), openEuler 23.09 Edge

  • Armv7i (Arm32) architecture

    Raspbian GNU/Linux (stretch)

  • AArch64 (Arm64) architecture

    Ubuntu LTS (Xenial Xerus), Ubuntu LTS (Bionic Beaver), CentOS, EulerOS, RHEL, Kylin, NewStart CGS Linux, NeoKylin, openEuler, Unity Operating System (UOS), Oracle Linux (OL), Huawei Cloud Euler (HCE), openEuler 23.09 Edge

    NOTE:

    The openEuler 23.09 Edge operating system is recommended for edge computing scenarios.

Memory

More than 256 MB of memory is recommended as 128 MB of memory is required to run the edge software.

CPU

≥ 1 core

Hard disk

≥ 1 GB

GPU (optional)

The GPU models on the same edge node must be the same.

NOTE:

Currently, NVIDIA Tesla GPUs such as P4, P40, and T4 are supported.

If an edge node is equipped with GPUs, you can choose not to enable its GPUs when registering it on IEF.

If you choose to enable GPUs of an edge node, the GPU driver has to be installed on the edge node before you can manage it on IEF.

Currently, only x86-based GPU nodes can be managed by IEF.

NPU (optional)

Ascend AI processors

NOTE:

Currently, edge nodes integrated with Ascend Processors are supported, such as Atlas 300 inference cards, and Atlas 800 inference servers. Supported NPU specifications include Ascend 310P, 310B, Ascend 310P-share, and virtualization partition NPUs..

If you choose to enable NPUs of an edge node, ensure that the NPU driver has been installed on it. Currently, Ascend 310 supports only firmware versions 1.3.x.x and 1.32.x.x, for example, 1.3.2.B893. You can run the npu-smi info command to view your firmware version.The NPU driver version must be 22.0.4 or later. You can go to the driver path, for example, /usr/local/Ascend/driver, and run the cat version.info command to view your driver version. If the driver is not installed, contact the device manufacturer for assistance.

Container engine

The Docker version must be later than 17.06. If Docker 1.23 or later is used, set the docker cgroupfs version to 1. Docker HTTP API v2 is not supported.

(However, Docker 18.09.0 is not recommended as it has a serious bug. For details, see https://github.com/docker/for-linux/issues/543. If this version has been installed, upgrade it at the earliest possible opportunity. )

NOTICE:

After Docker is installed, configure the Docker process to start at host startup. This configuration prevents system exceptions caused by Docker startup failures after the host is restarted.

Docker Cgroup Driver must be set to cgroupfs. For details, see How Do I Set Docker Cgroup Driver After Installing Docker on an Edge Node?.

Glibc

The Glibc version must be later than 2.17.

Port

Edge nodes require port 8883, which is the listening port of the built-in MQTT broker on edge nodes. Ensure that this port works properly.

Time synchronization

The time on an edge node must be consistent with the UTC time. Otherwise, the monitoring data and logs of the edge node may be inaccurate. You can select an NTP server for time synchronization. For details, see How Do I Synchronize Time with the NTP Server?

MQTT Usage Constraints

Table 2 MQTT usage constraints

Description

Constraint

Supported MQTT version

3.1.1

Differences from the standard MQTT protocol
  • Quality of Service (QoS) 0 is supported.
  • Topic customization is supported.
  • QoS 1 and QoS 2 are not supported.
  • will and retain msg are not supported.

MQTTS security levels

TCP channel basic + TLS protocol (TLS v1.2)