Versions Compared

Old Version 2

changes.mady.by.user Guixiang Miao

Saved on

compared with

New Version Current

changes.mady.by.user Colin Peters

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This is the second release of the Smart the Smart Data Transaction for CPS (Cyber-Physical Systems) Blueprint. The blueprint is focused on two main the following goals:

  • Integrating EdgeX device-camera-go and IP camera into SDT blueprint to enable edge nodes to receive image data from Camera
  • Sharing image data between edge nodes
  • Analyzing image data on edge nodes, and comparing image analysis results

...

  • Upgrade the source code to Release7, then modify the deploy/playbook/group_vars/all/edgex.yml file and files in deploy/playbook/host_vars directory according to the Installation Guide.
  • Run the edgex_stop.yml playbook to stop the EdgeX services.
  • Run the build_images.yml and push_images.yml playbooks to update the docker images in the private registry.
  • Run the edge_install.yml playbook to update the default docker runtime of edge nodes.

  • Run the edgex_start.yml playbook to start the Edgex services.

Release Data

Module Version Changes

N/A. All modules that are part of included with this release are version 1.01.

Document Version Changes

N/A. All documents included with this release are version 1.01.

Fixed Issues and Bugs

N/A. As this is a first release there are no bug fixes included.

Enhancements

N/A. As this is a first release there are no enhancements from previous versionsNo existing issues and bugs are fixed in this release.

Enhancements

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.

Version Change

This is release 1.0 1 of this blueprint.

Deliverable

...

Known Limitations, Issues and Workarounds

...

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):

  • A similar issue that hides the Kong (API gateway) application's /usr/kong/lib directory, leading to the process crashing
  • An issue with Kong's DNS processing that makes it fail to resolve the "localhost" address

...

With these workarounds in place the blueprint can be installed and operated successfully according to the Installation Guide.

References