Compatibility Problem of Changing Name of Openedge to Baetyl
Name Change Background
In August 2019, the open source project of Baidu IntelliEdge computing framework officially joined the Linux Foundation EDGE, becoming the first edge computing project in China to join the sub-foundation and continuing to promote industrial development as a platinum member and founding project.
On August 29, 2019, at the ABC Summit, Baidu AI Cloud announced the edge computing module baetyl-video-infer which continued to expand the support of video AI, further implementing ABC Anywhere. Meanwhile, it announced that the open source framework of Baidu IntelliEdge computing was named BAETYL.
Project Path Change Brought by the Name Change
When using the package installation method to install, it will be installed in the three directories of /bin, /etc and /var by default. In version 0.1.6, the default directories for package installation were changed as follows:
Catalog | Before the change | After the change |
---|---|---|
bin | bin/openedge | bin/baetyl |
etc | etc/openedge | etc/baetyl |
etc | etc/openedge/openedge.yml | etc/baetyl/conf.yml |
var | var/db/openedge | var/db/baetyl |
The old and new project structure is shown in the figure below:
- openedge:
- baetyl:
Upgrade from Openedge (0.1.5) to baetyl (0.1.6)
Master Program Upgrade
1.The master program starts to support OTA upgrade from 0.1.5 version, and it can be upgraded from 0.1.5 version to 0.1.6 version through the cloud management suite 2.Enter the core and click the Upgrade button at the latest version 0.1.6 of the operating package
3.Confirm the upgrade in the pop-up box, perform the upgrade operation, and the upgrade process will be recorded in the frontend
4.Close the pop-up box, return to the core details, and you can see the core version has changed from 0.1.5 to 0.1.6, which means it is upgraded successfully.
If bin/openedge does not configure systemd daemon, you have to manually execute the master program starting command on the edge side, otherwise the upgrade process will time out because the cloud does not receive the version information sent by the edge core in a long time. But this does not affect the upgrade operation, and the upgraded version will be automatically reported the next time you start openedge.
Module Upgrade
Module upgrade is divided into agent module upgrade and Other modules upgrade.
Agent Module Upgrade
1.View the openedge-agent module, modify the module to baetyl-agent:0.1.6 (this process cannot be returned after saved, and select hub.baidubce.com/baetyl/baetyl-agent:0.1.6 as the image address.
2.Release a new configuration version
3.Distribute the configuration
4.Check the agent version on the edge side, and you can execute docker ps view on the end.
Other Modules Upgrade
1.Take hub module as an example. View the openedge-hub module, modify the module to baetyl-hub (this process cannot be returned after saved), and select hub.baidubce.com/baetyl/baetyl-hub:0.1.6 as the image address.
2.Modify the directories in the container bound to storage volume mapping, and change all openedge directories to baetyl, for example, change etc/openedge to etc/baetyl.
3.Release a new configuration version
4.Distribute the configuration
5.Check the hub version on the edge side, and you can execute docker ps view on the end.