This is the first release of the Smart Data Transaction for CPS (Cyber-Physical Systems) Blueprint. The blueprint is focused on two main 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:
sync-app: An application micro-service built with EdgeX Foundry for sharing data between nodes
The dependencies of this release are summarized below:
Kubernetes 1.22 or above
There are no upstream code changes.
Since this is the first release, there are no differences from previous version.
As this is the first release there are no upgrade procedures. Follow the process described in the Installation Guide.
N/A. All modules that are part of this release are version 1.0.
N/A. All documents included with this release are version 1.0.
N/A. As this is a first release there are no bug fixes included.
N/A. As this is a first release there are no enhancements from previous versions.
This is release 1.0 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:
/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.