Baetyl Versions Save

Extend cloud computing, data and service seamlessly to edge devices.

v2.4.3

1 year ago

自Baetyl v2.3.0发版以来,在众多活跃贡献者的努力下,新增了更多新功能,并对部分已有功能进行了持续优化。这些新的特性依然本持着云原生的理念,继续朝着构建开放、安全、可扩展、可控制的智能边缘计算平台的方向前进。 具体来说,相较于之前发布的Baetyl v2.3.0版本,v2.4.3版本提供的新功能及功能优化主要包括:

  1. 重构了设备管理功能的实现 a. 设计了设备模版的接口,设备接入模板是一种类型设备的接入方式的模板,相同接入方式的设备可以复用同一个模板 b. 新增了对设备采集值 OT 数采点位计算的支持 c. 新增了对 IEC-104 协议驱动的支持 d. 更新了 OPC-UA 驱动的实现,适配重构后的设备管理接口 e. 更新了 Modbus 驱动的实现,适配重构后的设备管理接口 f. 更新了驱动与节点的绑定逻辑
  2. 增加了对 Windows 平台的支持,Baetyl 边缘侧主模块可以指定生成 Window 平台镜像
  3. 实现了远程调用功能,可以通过云端向边缘侧指定服务地址发起访问并获取访问结果
  4. 新增容器模式下 eKuiper 作为系统可选应用
  5. 新增 Baetyl-rule 模块对 HTTP Target 的支持
  6. 增加最高到 K3s 1.24.4 版本的适配
  7. 修复job负载类型创建失败的问题

以上新功能会随着Baetyl v2.4.3的发布立即可用。其他功能各位开发者可以进一步探索,Baetyl 后续将持续进行功能的完善和优化。


Baetyl v2.4.2 has added new features and optimized existing ones compared to the previous version v2.3.0. These new features still follow the cloud-native philosophy and continue to build an open, secure, scalable, and controllable intelligent edge computing platform. Specifically, compared to Baetyl v2.3.0, the new features and optimizations in v2.4.3 include:

  1. device management functionality has been refactored with the addition of a device template interface, support for calculating OT data collection values, support for IEC-104 protocol, updated OPC-UA and Modbus drivers, and updated driver-node binding logic;
  2. support for Windows platform has been added with the ability to generate Windows platform images for the Baetyl edge main module;
  3. remote invocation has been implemented, allowing for remote access to specified edge services with results returned from the cloud.
  4. New container mode with eKuiper as an optional system application
  5. New Baetyl-rule module supports HTTP Target
  6. Adaptation to the highest K3s 1.24.4 version
  7. Fix workload type creation failure bug

These new features will be immediately available with the release of Baetyl v2.4.3. Other features can be further explored by developers, and Baetyl will continue to improve and optimize its functionality.

v2.3.0

1 year ago

自Baetyl v2.2.0发版以来,在众多活跃贡献者的努力下,新增了更多新功能,并对部分已有功能进行了持续优化。这些新的特性依然本持着云原生的理念,继续朝着构建开放、安全、可扩展、可控制的智能边缘计算平台的方向前进。

具体来说,相较于之前发布的Baetyl v2.2.0版本,v2.3.0版本提供的新功能及功能优化主要包括:

  1. 新增了对k8s原生yaml的支持
  2. 新增了对应用模块更多功能的支持
  3. 新增了配置项功能对镜像类型的支持
  4. 新增了对边缘文件清理的逻辑
  5. 新增了设备接入模板的定义,通过设备接入模板完成南向采集点位到物模型点位的映射
  6. 新增了边缘集群对多master的支持,并提供了配套的baetyl-agent官方模块进行使用
  7. 边缘增加了对k3s/k8s v1.22.0及以上版本的适配
  8. 边缘核心模块服务默认开启TLS证书认证
  9. 对安装命令进行了优化,新增了wget模式,采用 sh 执行脚本

关于对k8s原生yaml的支持,在Baetyl v2.2.0版本中用户创建应用、配置项等资源需要调用baetyl云端开发接口,经由Baetyl转换成对应的k8s资源。新版本支持用户直接提交原生k8s资源定义来创建对应的资源。

关于应用功能模块,也新增了多项功能支持:

  • 应用部署逻辑更新,原先一个应用多个服务部署为多个Pod的运行模式,更新为一个应用启动一个Pod,应用的多个服务以同一个Pod中不同容器的形式运行;
  • 应用负载类型新增对 Job 类型的支持;
  • 应用增加对初始化容器类型的支持;
  • 应用服务增加工作目录设置的支持;
  • 应用服务卷挂载时增加对子路径(subPath)的支持;

以上新功能会随着Baetyl v2.3.0的发布立即可用。其他功能各位开发者可以进一步探索,Baetyl 后续将持续进行功能的完善和优化。


Baetyl has now achieved more advanced functions and improvements with the efforts of many active contributors. These new features still adhere to the concept of Cloud Native, and continue to move towards building an open, secure, scalable, and controllable intelligent edge computing platform.

Specifically, compared to the previously released Baetyl v2.2.0 version, the new features provided by the v2.3.0 version include:

  1. Support for k8s native yaml
  2. Application module optimization
  3. Support for image type in configuration module
  4. Support for edge file cleanup
  5. New api definations for device access template to support the mapping of southward acquisition points to device model points
  6. Multiple masters support for edge clusters, and an official baetyl-agent module to use
  7. Edge adaption to k3s/k8s version 1.22.0 and above
  8. The baetyl-core module service enables TLS certificate authentication by default
  9. Optimization for installation command, wget mode added, using sh to execute the script

About support for k8s native yaml. In baetyl v2.2.0, users need to call the baetyl cloud open APIs to create application, configurations and other resources, and convert them into corresponding k8s resources through baetyl. The new version supports users to directly submit native k8s resource definitions to create corresponding resources.

About application module, a number of new features are added:

  • The application deployment logic is updated. The application running mode in Baetyl v2.2.0 is that multiple services are deployed as different pods. In v2.3.0, multiple services are deployed as different containers in the same pod.
  • Support for Job load type applicatiopns
  • Support for init container type applications
  • Support for working directory settings for application services
  • Support for subpath when the application service volume is mounted

All these new features will be available immediately with the release of Baetyl v2.3.0. Developers can further explore other functions with baetyl. Baetyl will continue to improve and optimize its functions in the future.

v2.2.0

2 years ago

在过去的一段时间里,Baetyl在众多的活跃贡献者的努力下,实现了更多有挑战性的功能。这些新的特性依然本持着云原生的理念,继续朝着构建开放、安全、可扩展、可控制的智能边缘计算平台的方向前进。 具体来说,相较于之前发布的Baetyl v2.1.1版本,v2.2.0 版本提供的新特性包括:

  • 新增了对EdgeX Foundry的支持
  • 新增了对支持边缘集群环境的所需的API定义
  • 新增了对DaemonSet负载类型应用的支持
  • 新增了对已部署应用的远程调试、远程日志查看的API定义
  • 新增了对GPU 监控及共享功能的API定义
  • 更多的官方模块

以上的特性在边缘计算场景下都是需求比较急迫且具有很高实用价值的功能。 关于对EdgeX Foundry的支持。Baetyl v2.2.0版本已经完成对开源计算框架EdgeX Foundry的兼容,通过baetyl的云端管理套件,你可以向边缘侧下发完整的EdgeX 14个服务,下发的EdgeX服务将由baetyl提交部署并统一监测信息与云端进行信息同步。 关于对边缘集群的支持。在工业物联网场景中,经常会有大量工控盒子构成一个边缘集群的场景。Baetyl定义了开放的多集群管理API,通过实现这些API,可以把整个集群反映在云端控制台上,你可以方便的将应用部署到定义的集群中,更进一步的你可以指定部署到某些边缘子节点上。 关于对DaemonSet负载类型应用的支持。在支持了集群的背景下,类似于针对集群中每个节点状态监控的功能就需要一种新的负载方式来支持部署,所以我们也对DaemonSet进行了支持,通过这种负载类型,可以将服务在匹配到的每个集群中的节点上启动一个副本,并会随着新节点的增删自动调整。 关于远程调试、远程日志查看功能。为方便对边缘设备进行调试或日志查看操作,我们建立了开放的远程调试API,能够在未来与多种云端控制系统打通。 关于对GPU的支持。对GPU的支持主要包括两方面,一是对GPU的使用监控,二是对GPU共享的支持。通过GPU监控模块,baetyl-core可以实时获取GPU当前显存使用量、温度、能耗等信息。通过GPU共享功能,多个应用可以共享使用设备的GPU资源。目前已经完成了GPU支持接口的定义,仅需在端侧提供一个包含GPU share功能的模块即可使用。 在边缘侧,也提供了更多的官方系统模块:

  1. baetyl-init: 负责激活边缘节点到云端,初始化并守护 baetyl-core,任务完成后会持续上报并同步core状态;
  2. baetyl-rule: 可以实现 baetyl 框架端侧的消息流转,在 baetyl-broker (端侧消息中心)、函数服务、Iot Hub (云端 mqtt broker) 进行消息交换。

在这些新特性之外,还提供了很多其他功能细节上的优化和机制上的完善,比如安装过程的优化、系统应用可根据需要选择配置、定义了事务执行接口、任务队列接口等。 以上新功能会随着 Baetyl 2.2.0 的正式发布立即可用。


Baetyl has now achieved more advanced functions with the efforts of many active contributors. These new features still adhere to the concept of Cloud Native, and continue to move towards building an open, secure, scalable, and controllable intelligent edge computing platform. Specifically, compared to the previously released Baetyl v2.1.1 version, the new features provided by the v2.2.0 version include:

  • Support for working with EdgeX Foundry
  • New API definition needed to support edge cluster environment
  • Support for DaemonSet load type applications
  • New API definitions for remote debugging and remote log viewing of deployed applications
  • New API definitions for GPU monitoring and sharing functions
  • More official modules

The above features are functions that are in urgent need and have high practical value in edge computing scenarios. About support for EdgeX Foundry. The Baetyl v2.2.0 has completed compatibility with the open-source computing framework EdgeX Foundry. Through baetyl's remote management suite aka. Baetyl-cloud, users can deliver all 14 EdgeX services to the edge. The delivered EdgeX services will be submitted by Baetyl to local Kubernetes cluster for deployment and monitoring synchronized to the cloud. About support for edge clusters. In the industrial IoT scenario, there are often many industrial control boxes to form an edge cluster scenario. Baetyl defines open multi-cluster management APIs. By implementing these APIs, the entire cluster can be reflected on the cloud console. Users can easily deploy applications to defined edge clusters and specify edge node affinity within cluster. About support for DaemonSet load type applications. In the context of supporting clusters, a new load method is needed to support deployment like the function of monitoring the status of each node in the cluster, so baetyl also support DaemonSet. Through this load type, the service can be a single replica launched on every node in the matched cluster, and it will be automatically scaled to new added nodes and vice-versa. About remote debugging and remote log viewing functions. To facilitate debugging or log viewing operations on edge devices, baetyl have established an open remote debugging API that can connect with multiple cloud control systems in the future. About GPU support. The support for the GPU mainly includes two aspects, one is the monitoring of the use of the GPU, and the other is the support for the GPU sharing. Through the GPU monitoring module, baetyl-core can obtain the current GPU memory usage, temperature, energy consumption and other information in real time. With the GPU sharing function, multiple applications can share the GPU resources of the device. At present, the definition of the GPU support interface has been completed, and only a module containing the GPU share function needs to be provided on the end side to use. There will be more official system modules are also provided:

  1. baetyl-init: Responsible for activating edge nodes to the cloud, initializing and guarding baetyl-core, after the task is completed, it will continue to report and synchronize the core state.
  2. baetyl-rule: can realize the message flow of baetyl framework end-side, and exchange messages in baetyl-broker (end-side message center), function service, IoT Hub (cloud MQTT broker).

In addition to these new features, it also provides many other functional details optimization and mechanism improvement, such as the optimization of the installation process, the system application can be configured according to needs, and the transaction execution interface and task queue interface are defined.

All these new features will be available immediately with the release of Baetyl 2.2.0.

v2.2.0-rc37

3 years ago

v2.2.0-rc36

3 years ago

v2.2.0-rc35

3 years ago

v2.2.0-rc34

3 years ago

v2.2.0-rc33

3 years ago

v2.2.0-rc32

3 years ago

v2.2.0-rc31

3 years ago