NEMO has defined its meta-OS meta-architecture which is a useful blueprint for designing similar meta-OS ecosystems.
NEMO CFDRL extends MLOps to a novel paradigm ensuring cybersecure, federated real-time DRL with a balance between efficiency and ML convergence performance, while supporting the complete ML development and delivery lifecycle towards ML as a Service provisioning and meta-OS orchestration decision making.
NEMO meta-Network Cluster Controller (mNCC) supports intent-based networking for service delivery between NEMO nodes, possibly located across administrative domains. mNCC incorporates an overlay mechanism to establish connectivity between NEMO nodes, which is based on an intent-based interface to accommodate service requests (currently in beta version), allowing alignment of application Service Level Objectives (SLOs) with network provider’s operational actions.
The NEMO meta-Orchestrator serves as the meta-control plane, strategically placed atop existing container orchestration clusters such as Kubernetes (K8s). The NEMO meta-Orchestrator has been designed as a set of microservices, addressing, service orchestration across the continuum, resource (cluster) management, observability, intelligent decision making, as well as intent-based service management for integration with other NEMO components.
NEMO encompasses the Secure Execution Environment (SEE), which part of the NEMO Kernel Space and aims to enhance security and isolation of microservices, as well as secure and seamless migration capabilities on top of Kubernetes.
NEMO provides a set of automation tools, which enable full-stack automation for the NEMO meta-OS. NEMO adopts ZeroOps with automated workload delivery in meta-OS addressed by IaC practices of the meta-orchestrator, offering unified operational runtime for containerized workloads with built-in runtime protection, offered by the Plugins and Applications Lifecycle Manager (LCM) and application observability, provided by PPEF.
The Monetization and Consensus-based Accountability (MOCA) component provides a trusted and secure mechanism for any type of user who offers or consumes resources to the NEMO platform, referring to workloads (applications, services, plugins), data and nodes.
NEMO adopts ZeroTrust and cybersecurity by design. NEMO incorporates a set of modules to provide high levels of security and privacy for an effective OS, which will mainly support efficient Identity Management, Access Control Management and Intercommunication Security. The NEMO PRESS & Policy Enforcement Framework (PPEF) aims to safeguard security, privacy, ethics, cost, performance, environmental requirements and associated concerns that are defined for each of the NEMO-hosted services. PPEF handles policies for workloads similarly to Service Level Agreements (SLAs).
With Eclipse Foundation leading impact creation activities, NEMO commits strongly to open source and its community. NEMO code is already available as open source on Eclipse Research Labs’ Gitlab repository (
https://gitlab.eclipse.org/eclipse-research-labs/nemo-project(s’ouvre dans une nouvelle fenêtre))