This is the second release of the Smart Data Transaction for CPS (Cyber-Physical Systems) Blueprint. The blueprint is focused on the following goals:
In addition, this release provides a basic framework for installing, configuring and monitoring the collection of edge nodes, using Kubernetes and Ansible scripting.
The following components are new with this release:
image-app: An application micro-service built with EdgeX Foundry for anlyzing image data and comparing image analysis results
The dependencies of this release are summarized below:
Kubernetes 1.22.9
There are no upstream code changes.
The steps to upgrade from the previous version to the current version are as follows。
deploy/playbook/group_vars/all/edgex.yml
file and files in deploy/playbook/host_vars
directory according to the Installation Guide.edgex_stop.yml
playbook to stop the EdgeX services.build_images.yml
and push_images.yml
playbooks to update the docker images in the private registry.edge_install.yml
playbook to update the default docker runtime of edge nodes.Run the edgex_start.yml
playbook to start the Edgex services.
All modules included with this release are version 1.1.
All documents included with this release are version 1.1.
No existing issues and bugs are fixed in this release.
This release introduces support for IP cameras and sharing of static images via the synchronization application. Support for GPU acceleration of selected applications on the edge nodes has been added. A new application is introduced which analyses static images to perform shape detection.
This is release 1.1 of this blueprint.
The deliverables consist of a Git repository containing all the source code for the new modules and script files for installation and operation of the blueprint, and the documents:
The following limitations are intended to be addressed in later releases:
The following known issues exist in the EdgeX Foundry implementation and impact this blueprint (note that these issues may have been addressed in later releases of the upstream code):
/usr/kong/lib
directory, leading to the process crashingThese issues are all addressed by workarounds described below.
The edgex-go
issues 3851 and 3852, as well as the issue hiding Kong's lib
directory, are addressed by changes to the volume mappings of containers, found in the configuration files under edgex/deployments
, edgex/claims
, and edgex/volumes
, and patches to the EdgeX Foundry security-bootstrapper
and security-secretstore-setup
Docker images. The patched images are generated using the Makefile
and Dockerfile
in the directories under edgex
named after the affected images.
The Kong DNS name resolution problem is worked around with a patched Kong image, generated from the source under edgex/kong
.
With these workarounds in place the blueprint can be installed and operated successfully according to the Installation Guide.