...
This first EdgeX release is focused on delivering a minimum viable product (MVP) for further accelerating community contributions. It would not be a product ready for mission-critical use cases, but it is the hope of the EdgeX community that with the Barcelona release, the shape of the architecture, APIs, etc. are such that the larger IoT development community will feel comfortable exploring EdgeX and using EdgeX in upcoming begin planning integration of the EdgeX foundation with their own IoT projects.
Release Themes & Objectives
- Stabilize the platform
- Build community understanding of the platform
- General majority agreement on the architecture
- General majority agreement on micro services and APIs
- General majority agreement on the development of an open, platform independent, technology agnostic platform for the IoT/edge
- General agreement on temporary performance targetslonger-term performance targets
Key Features
- Stabilization of key APIs
- Better code quality, fit and finish
- More than double the test coverage across EdgeX microservices
- Addition of reference Device Services supporting BACNet, Modbus, Bluetooth Low Energy (BLE), MQTT, SNMP and Fischertechnik
- Extra “north side” Export Service interfaces that provide connectors to Azure IoT Suite and Google IoT Core as well as support for connections via MQTTS and HTTPS
- Progress towards the definition of unified APIs for security and system management
General Release Tasks and Notes
- Supported OS
- Windows 10 (latest 2016 version)
- Linux, Ubuntu 16.04 classic (but does not enforce secure boot)
- EdgeX supports and welcomes other OS providers to test and validate EdgeX works on their OS
- Example, Canonical plans to test/validate EdgeX on Ubuntu Core 16
- Supported Hardware:
- Intel x86
- EdgeX welcomes and will support 3rd party contribution of Arm support. Work Note: work to port to Arm is nearing completion although the automated build environment needs further attention.
- Performance targets stand, but may not be achieved in this release
- EdgeX to develop performance tests to show current performance metrics
- No significant performance-specific work will be accomplished in this release (unless it is easy to achieve with no other impacts)
- EdgeX will provide early Go performance numbers to show intended path to achieve performance targets (that is slowly replacing Java-based micro services with Go or other faster/smaller programming language micro services over the next few releases)
- EdgeX will use current scalability metrics on devices, collection, etc. as scale guidance
- More formal scalability concerns to be addressed in future releases
- All Micro Services will be hardened; meaning
- Works properly for the intended use case
- It may not be 100% complete implementations for all use cases or parts of a protocol for example, but it provides enough implementation to sustain the demo use cases for Barcelona and could support extension to the full needs or protocol in the future
- Handles errors and exceptions gracefully
- Contains proper unit and integration tests
- Follows good coding standards, and is well documented
- Following some prescribed standard (like Oracle, Google or Twitter guides for Java)
- Performs within the target measures established for Barcelona
- Code base is not exploitable
- API set is solid
...
- Harden as defined above
- Provide Azure IoT Hub integration (improve/clean up the existing Dell work)functionality in the original seed code) and support for Google IoT Core
- Provide routing to endpoints by device idID
- Support MQTTS and HTTPS for endpoint distribution
- No additional formats/transformations/filters/etc. will be provided beyond what already exist in the export services today
- Provide guidance on number of simultaneous clients that can be supported (to address any potential scale problems with the export services)
- Stretch Goal: binary message format distribution (picking one to start)
...
Device Service SDK and Device Services Tasks and Notes
- Harden as defined above
- Provide the Dell 7 Set of reference Device Services (Modbus, BACnet, BLE, MQTT, SNMP, Fishertechnik, and virtual device)
- Clean up SDK (and Device Services)
- Improve documentation
- Be more developer friendly (see improve tooling - stretch)
- Merge device-sdk into SDK tools
- Cleanup scheduler
- Apply cleanup back to DS (with exception of BACnet and BLE)
- Stretch Goals
- Improve tooling (Eclipse Plugin)
...