Release Date: ~ Dec 2024Feb 2025
05/20/2024 - The TSC voted to approve delaying 3.2 until the December timeframe. This is to allow the key features of Core Keeper, OpenBao and OpenZiti to be fully available in this release.
Q4 2024 - In order to start fresh with the new features and remove the outgoing services, increasingly likely that Odessa will be a 4.0 release. However at a user code and API level it will be compatible with V3 services and applications so migration will be straightforward.
Code Freeze: TBD
Namer: Farshid Tavakolizadeh and Mengyi Wang (both Canonical)
The Odessa release is EdgeX version 34.2 0 (the 14th overall release and the second dot release off EdgeX 3.0of EdgeX).
Release Major Themes (Planned)
...
- Addition of PostgreSQL as a database option
- New time-based support scheduler service
- Replace Hashicorp Consul with Core-Keeper
Replace Hashicorp Vault with OpenBao
- EdgeX modelling and relationship enhancements
- Parent/Child Devices
- Virtual Device Resources
- Device Metadata in Provision Watchers
- Protocol Info in Device Definitions (at least a UCR in this cycle)
- Device Functions (at least a UCR in this cycle)
- Replace Redis with Valkey (LF supported fork of Redis)
- EdgeX Parent/Child Device relationships
Zero Trust / Secure Distributed EdgeX (OpenZiti Integration)
- Continue EdgeX documentation redesign - focusing on updating all device service docs to the new consistent formatting, and an overhaul of the security section
- Add security capability to our NanoMQ optionDevice discovery feedback added to the Device Services SDK
- Support for running in Docker rootless mode
See the Odessa Planning page for details