PARSEC, the opensource CNCF project has been adopted for edge deployments as it offers a common API that abstracts secure roots of trust which are required to protect devices outside of the datacenter. This enables the cloud native principle of being able to freely move your applications from one platform to another while maintaining level of security that was not possible in the past.
Building on this abstraction, PARSEC can mediate access to hardware security primitives and create isolated key stores for a multi-tenancy environment.
Starting your project with the right platform for security will accelerate your deployments and scale.
Come read about Parsec at: https://parallaxsecond.github.io/parsec-book
And talk to the experts during our weekly community calls (see github).
Or join us on the CNCF slack channel: https://cloud-native.slack.com
API Subcommittee Notes
IoT apps must run on a wide range of devices (not just mobile phones), be able to sustain functionality through loss of Internet connectivity, and often run on devices or platforms with substantial size, weight, and power consumption (SWaP) constraints. Due to this need for robustness, and the underlying variety of devices and OS, IoT applications utilize all types of interfaces, including API, CLI, and web GUI. In an edge computing scenario, remote sensors may connect with edge nodes that host containerized IoT apps.
The next version of the API Portal (api.akraino.org) will contain a new top-level category for IoT applications showing APIs both exposed and consumed by the ELIOT and IIoT at the Smart Device Edge Blueprint
oneM2M IoT Service Layer (SL) Platform
- Blueprints under IoT Area choose to comply with oneM2M IoT Service Layer (SL) Platform
- If oneM2M IoT Service Layer (SL) Platform has ecosystem page, IoT Area blueprints can participate.