* Web frontend User Interface (UI) that consists of mainly two portal categories:
* Web frontend User Interface (UI) that consists of mainly three portal categories:
1. An NFV portal allowing users to onboard VNFDs/NSDs to facility’s NFVOs and self-service management
1. An NFV portal allowing users to onboard VNFDs/NSDs to facility’s NFVOs and self-service management
2. Several TMF-family portals (Product, Service, Resource, Testing) which allow users to browse the respective layers of a modern BSS/OSS solution
2. Several TMF-family portals (Product, Service, Resource, Testing) which allow users to browse the respective layers of a modern BSS/OSS solution
3. An AI assistant that aggregates the offered functionalities into a chat-based interaction
* An API gateway that proxies the internal APIs, which are used by the Web frontend as well as any other 3rd party services, and consist of:
* An API gateway that proxies the internal APIs, which are used by the Web frontend as well as any other 3rd party services, and consist of:
1. A microservice offering TMF-compliant API services (e.g. Product/Service/Resource Catalog API, Service Ordering API, etc)
1. A microservice offering TMF-compliant API services (e.g. Product/Service/Resource Catalog API, Service Ordering API, etc)
2. A microservice offering NFV-compliant API services (e.g. VNFD/NSD onboarding and management, etc) allowing to manage multiple NFVOs and store VNFDs and NSDs in the respective catalogues
2. A microservice offering NFV-compliant API services (e.g. VNFD/NSD onboarding and management, etc) allowing to manage multiple NFVOs and store VNFDs and NSDs in the respective catalogues
* A Service Orchestrator (SO) solution that will fulfill Service Ordering requests by propagating the orchestration actions to underlying components (e.g. NFVOs, Kubernetes, or other controllers) or to external SOs
* A MANO Client microservice which interfaces with SOL005-compliant NFVOs (synchronizing artifacts and propagating actions)
* A Custom Resource (CR) to TMF bridge (CRIDGE) microservice which interfaces with Kubernetes
* A Metrics Retrieval Component (METRICO) which interfaces with external monitoring tools, retrieving and injecting desired metrics into OpenSlice orchestration pipeline
* A pool of several controllers (e.g., Sylva, Camara, 3GPP, gitops, etc.), offered as optionally enabled addons
* An AI layer, integrating the built-in MCP Server and open-source LLMs, which interfaces and interworks with the rest components
* A Message Bus used by all microservices to exchange messages either via message Queues or via publish/subscribe Topics
* A Message Bus used by all microservices to exchange messages either via message Queues or via publish/subscribe Topics
* An Authentication Server implementing Oauth2 authentication scheme
* An Authentication Server implementing Oauth2 authentication scheme
* A microservice that is capable to interface with an issue management system (e.g. it raises an issue to all related stakeholders - CSPs, NOPs, CSCs - that a new Service Order is requested)
* A microservice that is capable to interface with an issue management system (e.g. it raises an issue to all related stakeholders - CSPs, NOPs, CSCs - that a new Service Order is requested)
* A Central Logging microservice that logs all distributed actions into an Elasticsearch cluster
* A Central Logging microservice that logs all distributed actions into an Elasticsearch cluster
* A Service Orchestrator (SO) solution that will fulfill Service Ordering requests by propagating the orchestration actions to underlying components (e.g. NFVOs or Kubernetes) or to external SOs
* A MANO Client microservice which interfaces with SOL005-compliant NFVOs (synchronizing artifacts and propagating actions)
* A Custom Resource (CR) to TMF bridge (CRIDGE) microservice which interfaces with Kubernetes
* A Metrics Retrieval Component (METRICO) which interfaces with external monitoring tools, retrieving and injecting desired metrics into OpenSlice orchestration pipeline
* An Assurance Services component which generates and monitors alerts, as well executing defined actions based on the latter
* An Assurance Services component which generates and monitors alerts, as well executing defined actions based on the latter
* A visualization server (KROKI) microservice which enables a intuitive illustration of dependency graphs and interactions
* A visualization server (KROKI) microservice which enables a intuitive illustration of dependency graphs and interactions
<!--
## Microservices Deployment
## Microservices Deployment
The following figure depicts how OpenSlice microservices are deployed
The following figure depicts how OpenSlice microservices are deployed
