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 the hub module as an example. Check 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.

Restrictions on Module Upgrades

The Agent Module

1.The agent module only supports to upgrade the version, such as upgrade from openedge-agent:0.1.5 to baetyl-agent:0.1.6, and in the future it only supports to upgrade to baetyl-agent:0.1.7 or a higher version. 2.The agent module does not support to switch modules. For example, the baetyl-agent module cannot be switched to the baetyl-hub module, because the agent module is a system module and is responsible for the connection between the edge and the cloud. If the module is totally switched, the edge and the cloud are disconnected. 3.The upgraded version of the agent module cannot be higher than the core version. For example, if the version of the master program package is 0.1.6, then the agent version can only be upgraded to version 0.1.6 at most.

Other Modules

1.Since baetyl has undergone a name change and the configuration path mapped in the official module container has also changed from etc/openedge to etc/baetyl, when the official module is upgraded from a version earlier than 0.1.6 to version 0.1.6 or a higher version, the container directory corresponding to the storage volume has to be modified synchronously. Modify etc/openedge to etc/baetyl, and the data files and log files in the container are not affected. 2.For the user module, if the new version module modifies the configuration file read path in the container, the container directory also has to be changed, otherwise, no change is required.