Today, we’re happy to announce Pantavisor Engine, a new and exciting version of our lightweight container framework and runtime for embedded Linux-based projects. This new version of Pantavisor extends the capabilities of Pantavisor, enabling service and product operators to install the container runtime agent on top of existing firmware.
This year the Open Source Summit North America takes place in Austin from June 21st to the 24th. The conference gathers open source developers, technologists, and community leaders to further open source innovation. Pantacor will be exhibiting both in-person and virtually. In addition to this, key Pantacor engineers, Anibal Portrero and Ricardo Mendoza are delivering talks.
Senior Engineer Anibal Portero gave a talk at the Open Source Summit held in Austin earlier this year. Anibal spoke on how to leverage modern open protocols and containers so that operators can update IoT fleets that run on multiple architectures with any OTA cloud provider.
Few of the millions of embedded systems connected and running in people’s homes and businesses can deliver meaningful logs. Yet, logs are essential for maintaining, monitoring, and troubleshooting device fleets so operators can drill down and promptly solve issues.
The CPEs and routers available today in homes and businesses are more than capable of delivering services beyond the standard bundle of voice, data, and video. However, up until now, it’s been challenging to modernize the CPE stack so that it can be updated and secured, let alone offer new services to subscribers.
In this post, we’ll drill down further into how Pantacor Fleet implements modern deployment strategies like canary and A/B testing. We also describe a powerful feature that enables product makers to control and customize firmware with containers without re-building the manufacturer’s BSP.
How can you increase deployment velocity to embedded Linux? In this post, we step through a tutorial on how Pantacor automates kernel and firmware updates in the BSP for device fleets to reduce CVEs.
Distros and FOSS have not supported product builders to make great embedded Linux products. As a result, proprietary OS dinosaurs still endure as the SDK of choice.