Date: Fri, 29 Mar 2024 08:28:45 +0000 (UTC) Message-ID: <1598484529.50561.1711700925390@aws-us-west-2-akraino-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_50560_472065450.1711700925389" ------=_Part_50560_472065450.1711700925389 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is the first release of the = ;Smart Data Transaction for CPS (Cyber-Physical Systems) Blueprint. The blu= eprint is focused on two main goals:
In addition, this release provides a = basic framework for installing, configuring and monitoring the collection o= f 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.= span>
Since this is the first release, ther= e are no differences from previous version.
As this is the first release there ar= e no upgrade procedures. Follow the process described in the Installation G= uide.
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 c= ode 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 hid=
ing Kong's lib
directory, are addressed by changes to the volu=
me mappings of containers, found in the configuration files under edg=
ex/deployments
, edgex/claims
, and edgex/volumes=
code>, and patches to the EdgeX Foundry
security-bootstrapper
=
and security-secretstore-setup
Docker images. The patched imag=
es are generated using the Makefile
and Dockerfile
in the directories under edgex
named after the affected imag=
es.
The Kong DNS name resolution problem is worked around with a patched Kon=
g image, generated from the source under edgex/kong
.
With these workarounds in place the blueprint can be installed and opera= ted successfully according to the Installation Guide.