Delivery: ~June 2018
This The main theme for the California release of EdgeX is to provide a solid open source foundation for commercialization and deployment in a wide variety of Industrial IoT edge use cases including .
Key to this is the first implementation of priority APIs and reference services microservices for security and system management. It will also improve EdgeX ease of use among a larger, more polyglot, development community.Another manageability. Another key theme for the California release is improving overall performance and lowering the baseline footprint of the code base. Work is currently underway for drop-in alternatives for key microservices (e.g. Core Services, Export and Device Services) based in Go Lang which promises to offer a with a stretch goal being select implementations in C. Overall, the California release will improve EdgeX ease of use among a larger, more polyglot, development community.
Further exploratory work is being will be done for a high performance message bus as an option to the current REST-based intercommunication between microservices.
Functionality is still being finalized by the TSC but directional themes are detailed outlined 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 promise for a performant, reliable IoT edge platform promise
- Reduce overall footprint by an order of magnitude through alternative microservice implementations in Go Lang and possibly C
- Near Enable near real-time performance (targets to be finalized in January 2018)
- Explore future extensions for enabling future community extensions in planning for deterministic real time use cases)
- Improve overall performance and deliver to target performance #’s
- Provide additional reference connectivity
- Export Services (e.g. AWS/Greengrass)
- Device Services (e.g. OPC-UA)
- Device Service and Export Service SDKs in Go Lang
- Stretch goal: C-based Device Service SDK
- Demonstration of EdgeX in real-world POC/test bed, including through collaboration with the IIC
...
- Meet all performance targets
- Alternative Go-based implementation of Core Services implementationmicroservices
- More dynamic configuration
- Address use of Consul as config/registry?
- Implement security & system management API hooks
- Stretch goal: Go-lang based services for select Supporting Services
Application Tasks and Notes
- Implement security & system management API hooksneccesary hooks for top priority security and manageability functionality
- Define and meet performance metrics
- Provide better scale in terms of number of clients
- Improve the number of messages exported/sec
- Support additional cloud backend 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
- Provide additional export capability
- Enrichment services
- How best to facilitate client command requests/actuation
...
Security and System Management Tasks and Notes
- The first Initial implementation of
- Ref Impl security micro services
- key security and manageability APIs plus supporting referencne microservices
- Security and management API hooks in other microservices
- Security testing framework
- Demonstrate basic management of EdgeX via select 3rd party console (ex: VMware Demonstrate EdgeX management via System Management app of choiceEx: 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
- Explore container orchestration via Kubernetes