You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
D-release (Q4, 2020)
- Measured boot and Remote Attestation to the controller
- Encrypted disk vault keys sealed under the TPM PCR values
- End-to-end security even with content inspecting proxies
- Off-line support - verify that applications come up even if there is no connectivity to the controller
- Off-line support - user-setable reset/reboot time if connectivity is lost to controller (to recover from hung network adapters)
- App side-loading/pre-loading by being able to specify content trees independent of volume creation
- Use containerd as Content Addressible Storage for containers, VM and EVE images
- Verify device passthrough for primary video adapter
- Provide an API so Azure IoT edge workload can report status/metrics for the running modules via EVE to controller
- Non-virtio emulation of devices
- Reduce EVE memory footprint (single zedbox process for most microservices); apply C-group controls
- Experimental support for ZFS for the /persist filesystem including encryption
E-release (Target : Q1 2021)
- New EVE Logging Infrastructure (replace rsyslogd with simpler and more robust logging)
- Extract and report GPS coordinates to controller (if device has a cellular modem with GPS)
- Make IP geolocation more robust
- Enable deploying K3S workloads (different networking requirements?)
- Incremental image download (rsync-like)
Future - to be planned
- Support multiple disks using different forms of RAID configurations (might use ZFS)
- Tailscale integration?
- Build and download EVE as OCI layers (reduces size of EVE update downloads)