You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Delivery:  ~June 2018

This main theme for this release is to provide a solid foundation for deployment in a wide variety of edge use cases including the first implementation of priority APIs and reference services for security and system management.  It will also improve EdgeX ease of use among a larger, more polyglot, development community.

Functionality is still being finalized by the TSC but directional themes are below.

Release Themes and Objectives

  • Deliver top priority security and system management APIs and reference implementations of supporting microservices (e.g. key management)
  • Deliver on mission critical / reliable platform promise
    • Near real-time performance (enabling hard real time use cases planned through community extensions)
    • Improve overall performance and deliver to target performance #’s
    • Reduce overall footprint by an order of magnitude through alternative microservice implementations in Go Lang and possibly C
  • Provide additional connectivity
    • Some additional north side connectors (e.g. AWS/Greengrass)
    • Some additional device services (e.g. OPC-UA)
  • An additional Device Service and Export Service SDKs in Go Lang
  • Demonstrate EdgeX in real-world POC/Test Bed through collaboration with IIC

General Release Tasks and Notes

  • Expand OS support
    • Mac
    • Other flavors of Linux
  • Expand hardware support
    • Arm
  • Provide EdgeX User Interface(s)

Core and Supporting Tasks and Notes

  • Meet all performance targets
  • Go services for core
  • More dynamic configuration
  • Address use of Consul as config/registry?
  • Implement security & system management API hooks
  • Stretch – Go services for supporting services

Application Tasks and Notes

  • Define and meet performance metrics
    • Provide better scale in terms of number of clients
    • Improve the number of messages exported/sec
  • Support additional cloud integration(s)
    • Ex:  Watson, AWS/Greengrass, …
  • Support additional export feature(s)
    • Support additional formats (Ex: Haystack, OPC-UA, …)
    • Support additional endpoint types (Ex:  DDS, AMQP, …)
    • Explore potential use of hyperledger
  • Implement security & system management API hooks
  • Provide additional export capability
    • Enrichment services
    • How best to facilitate client command requests/actuation

Device Service SDK and Device Service Tasks and Notes

  • Provide an alternate language DS SDK
  • Provide SDK Tool plugins to facility developers
    • Ex:  Eclipse plugin
    • SDK download (non-github oriented)
  • Provide new and/or updated Device Services
    • Real BACnet or BLE
    • Additional DS (i.e. Zigbee, OPC-UA, CANBus, …)
  • Reduce/optimize Java DS (remove Spring Framework, etc.)
  • Updates to SDK get propagated back out to existing DS via common shared libraries
  • Implement security & system management API hooks

Security and System Management Tasks and Notes

  • The first implementation of
  • Ref Impl security micro services
  • Demonstrate EdgeX management via System Management app of choice
    • Ex:  Pulse IoT Center, System Center, …
  • Secty and Sys Mngmt API hooks in other micro services
  • Security testing framework
  • Demonstrate EdgeX software updates
  • Updates to non-EdgeX components (drivers, end-devices)
  • Root of trust – what defines and how to implement
  • Code signing – how to certify integrity of the system
  • No labels