Can we get summaries on what's new with the existing BPs (Public Cloud Edge Interface, Smart Cities, ICN, Android Cloud, SmartNIC, Enterprise Lightweight Application for 5G MEC) so we can highlight in a blog post or PR? We will also need to update a slide deck for R6.
As a follow up to the R6 announcement, let's look to tie in Akraino examples as part of the broader LF Edge effort to publish user stories across projects. There is SO MUCH happening with Akraino and we want to be sure we are telling these super compelling stories appropriately. See the recent Fledge case study as an example of what we're trying to do: https://www.lfedge.org/resources/case-studies/. Can we identify a handful of examples from Akraino that we can work into some similar narratives?
PCEI R6 Summary
The Public Cloud Edge Interface (PCEI) blueprint continued development and integration of new capabilities into the multi-domain orchestrator to enable infrastructure orchestration and cloud native application deployment across public clouds (core and edge), edge clouds, interconnection providers and network operators. To do that, PCEI makes use of Edge Multi-Cluster Orchestrator (EMCO -the new LFN project) as well as additional components such as Controller Design Studio (CDS) and Camunda workflow engine. The notable innovations in PCEI are the integration of Terraform as a microservice to enable DevOps driven Infrastructure-as-Code provisioning, integration of Ansible as a microservice to enable automation of configuration of infrastructure resources (e.g., servers) and deployment of Kubernetes and its critical components (e.g., CNIs) on the edge cloud, and introduction of a workflow engine to manage the stages and parameter exchange for infrastructure orchestration and application deployment as part of a composable workflow. PCEI R6 can help simplify the process of multi-domain orchestration by enabling uniform representation of diverse services, features, attributes, and APIs used in individual domains as resources and data in the code that can be written by developers and executed by the orchestrator, effectively making the infrastructure orchestration across multiple domains DevOps-driven.
For more Information, please go to: https://wiki.akraino.org/x/Qi0wAw