El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
Edge Node Version Support Announcement
IEF provides one-year maintenance for its versions since their release to ensure stable and reliable connection between your edge nodes and IEF. You are advised to upgrade your edge node software (EdgeCore) before the maintenance period ends.
Version Naming Rule
Edge node software versions use the GNU software version naming rule: major version number.sub-version number.revision version number, for example, 2.22.0.
- A new major version number indicates a major software upgrade.
- A new sub-version number indicates that new functions are available to the software.
- A new revision version number indicates software bug fixes.
Version Support Policy
IEF only maintains the edge node software versions released within one year. Therefore, you are advised to upgrade your edge nodes at least once a year.
Version Upgrade Rule
During edge node upgrade, IEF automatically selects the EdgeCore of the latest version.
For example, if EdgeCore 2.22.0, 2.23.0, and 2.24.0 are available and the EdgeCore version on your edge node is 2.12.0, IEF will push the EdgeCore 2.24.0 to your edge node.
Precautions
- IEF does not proactively upgrade EdgeCore on your edge nodes. You are advised to upgrade the node manually in the time window with the minimum impact on your services.
- Upgrading a version within the maintenance period will not interrupt your applications running on the edge node. However, if message routing is used, services may be temporarily affected.
- Upgrading a version beyond the maintenance period may temporarily interrupt services due to container restart.
- Do not change node configurations during the node upgrade, such as restarting Docker, installing or uninstalling the GPU/NPU driver, upgrading the OS kernel, or modifying network configurations, which may result in node upgrade failures.
Upgrade Method
Earlier Versions
|
Version |
Released On |
Description |
Maintenance status |
|---|---|---|---|
|
2.53.0 |
2021/11/04 |
Supported configuration of possible causes and handling suggestions for preset and customized alarms of IEF. Supported EdgeCore Configuration Management. |
Maintaining |
|
2.52.1 |
2021/07/22 |
Fixed issues found in 2.52.0. |
Maintaining |
|
2.52.0 |
2021/06/03 |
Fixed the issue that the container cannot be started after the edge node software is upgraded from 2.7.0 to the latest version. |
Maintaining |
|
2.51.1 |
2021/04/20 |
Updated the method of installing the GPU node driver to allow offline GPU driver installation. Fixed the D910 issue found in 2.51.0.
NOTICE:
To upgrade the GPU node to this version, prepare the environment by referring to Installing a GPU Driver. |
Maintaining |
|
2.51.0 |
2021/02/25 |
Fixed issues found in 2.24.0. |
Maintaining |
|
2.24.0 |
2020/10/21 |
Supported EdgeMesh session persistence (consistent hashing). Fixed issues found in 2.23.0. |
Not maintained. Upgrade required. |
|
2.23.0 |
2020/08/26 |
Supported distributed health monitoring and automatic scheduling between edge nodes. Supported TLS two-way authentication for edge channels. Fixed issues found in 2.22.0. |
Not maintained. Upgrade required. |
|
2.22.0 |
2020/07/11 |
Supported Kubernetes 1.15 for edge nodes. Supported secret encryption for storage at the edge. Optimized the edge software for lightweight design. Fixed issues found in 2.21.0. |
Not maintained. Upgrade required. |
|
2.21.0 |
2020/05/18 |
Supported monitoring on usage of the disks used by containers. Fixed the issue that an application cannot be deleted due to EdgeCore restart. |
Not maintained. Upgrade required. |
|
2.20.0 |
2020/04/18 |
Supported collecting information about the Da Vinci chip model, driver version and memory. Provided EdgeMesh for the platinum edition. Fixed issues found in 2.12.0. |
Not maintained. Upgrade required. |
|
2.12.0 |
2019/11/01 |
Fixed the issue that domain names of Ubuntu 18.04 edge node containers cannot be resolved. |
Not maintained. Upgrade required. |
|
2.11.0 |
2019/10/30 |
Optimized the edge software performance. Fixed issues found in 2.10.0. |
Not maintained. Upgrade required. |
|
2.10.0 |
2019/10/24 |
Supported image caching and acceleration for application upgrade. Fixed issues found in 2.9.0. |
Not maintained. Upgrade required. |
|
2.9.0 |
2019/10/16 |
Supported Atlas 500 deployment in both IEF and FD modes. Fixed issues found in 2.8.0. |
Not maintained. Upgrade required. |
|
2.8.0 |
2019/10/09 |
Supported multiple containers, pausing containers, and interconnection with CRI. Supported edge node verification to avoid repeated management. Fixed issues found in 2.7.2. |
Not maintained. Upgrade required. |
|
2.7.2 |
2019/08/17 |
Fixed issues found in 2.7.1. |
Not maintained. Upgrade required. |
|
2.7.1 |
2019/08/12 |
Supported alarm reporting through the proxy. Fixed issues found in 2.7.0. |
Not maintained. Upgrade required. |
|
2.7.0 |
2019/07/29 |
Supported alarm reporting when the AK/SK is invalid or the application is restarted. Fixed issues found in 2.6.2. |
Not maintained. Upgrade required. |
|
2.6.2 |
2019/07/26 |
Fixed issues found in 2.6.1. |
Not maintained. Upgrade required. |
|
2.6.1 |
2019/07/20 |
Supported firmware upgrade for Atlas 500 AI edge stations. Supported edge node fault detection. |
Not maintained. Upgrade required. |
|
2.6.0 |
2019/07/11 |
Supported node groups and node group certificates for platinum instances. Fixed issues found in 2.5.0. |
Not maintained. Upgrade required. |
|
2.5.0 |
2019/06/29 |
Supported injecting the hostip of an edge node into a container as an environment variable. Supported Atlas 500 AI edge station management. Supported health check using commands. Fixed issues found in 2.4.0. |
Not maintained. Upgrade required. |
|
2.4.0 |
2019/06/22 |
Supported container restart. Optimized the application deletion logic to accelerate application deletion. |
Not maintained. Upgrade required. |
|
2.3.2 |
2019/05/30 |
Fixed issues found in 2.3.1. |
Not maintained. Upgrade required. |
|
2.3.1 |
2019/05/23 |
Fixed the issue of version 2.3.0 that the health check fails after the proxy is configured. |
Not maintained. Upgrade required. |
|
2.3.0 |
2019/05/10 |
Supported alarm reporting to AOM related to Docker installation exceptions, application liveness probe exceptions, and GPU resource application failures. Supported edge data encryption. Supported the edge time series database. Fixed issues found in 2.2.7. |
Not maintained. Upgrade required. |
|
2.2.7 |
2019/04/19 |
Supported EventBus routing messages. Supported compressed transmission of edge-cloud messages. Allowed access to the cloud through the proxy. Fixed issues found in 2.2.6. |
Not maintained. Upgrade required. |
|
2.2.6 |
2019/04/11 |
Supported the MQTT broker. Fixed issues found in 2.2.5. |
Not maintained. Upgrade required. |
|
2.2.5 |
2019/03/21 |
Supported multiple Kubernetes clusters. |
Not maintained. Upgrade required. |
|
2.2.3 |
2019/03/20 |
Fixed the node failure caused by node restart after long-time disconnection. |
Not maintained. Upgrade required. |
|
2.2.2 |
2019/03/15 |
Allowed node firmware upgrade. |
Not maintained. Upgrade required. |
|
2.2.1 |
2019/03/07 |
Fixed issues found in 2.2.0. |
Not maintained. Upgrade required. |
|
2.2.0 |
2019/02/26 |
Allowed edge node certificate encryption. Allowed temporary AK/SK for the edge. |
Not maintained. Upgrade required. |
|
2.1.7 |
2019/01/25 |
Fixed issues found in 2.1.6. |
Not maintained. Upgrade required. |
|
2.1.6 |
2019/01/22 |
Fixed issues found in 2.1.5. |
Not maintained. Upgrade required. |
|
2.1.5 |
2019/01/03 |
Fixed issues found in 2.1.3. |
Not maintained. Upgrade required. |
|
2.1.3 |
2018/12/21 |
Supported displaying information such as GPU model and video memory. Fixed issues found in 2.1.2. |
Not maintained. Upgrade required. |
|
2.1.2 |
2018/12/07 |
Fixed issues found in 2.1.1. |
Not maintained. Upgrade required. |
|
2.1.1 |
2018/12/06 |
Fixed issues found in 2.1.0. |
Not maintained. Upgrade required. |
|
2.1.0 |
2018/12/01 |
Supported ErrorMsg display for the container startup failure. Added limit on the maximum size of the ServiceBus request file. Fixed the edge node exception when Docker is not installed. |
Not maintained. Upgrade required. |
|
2.0.3 |
2018/11/26 |
Fixed issues found in 2.0.2. |
Not maintained. Upgrade required. |
|
2.0.2 |
2018/11/21 |
Supported ServiceBus. Supported mapping between container ports and host ports. Fixed issues found in 2.0.1. |
Not maintained. Upgrade required. |
|
2.0.1 |
2018/11/08 |
Fixed issues found in 2.0.0. |
Not maintained. Upgrade required. |
|
2.0.0 |
2018/10/31 |
Released EdgeCore 2.0.0, which provides functions such as node management, container management, and message routing. |
Not maintained. Upgrade required. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
