In general Network as a Service (NaaS) is a service model that allows users to consume network infrastructure and services , similar to how they would consume other cloud services like Software as a Service (SaaS) or Infrastructure as a Service (IaaS). NaaS abstracts the complexity of managing physical network infrastructure, providing users with virtualized network resources that can be dynamically allocated and managed through software.
# OpenSlice and NaaS
OpenSlice makes extensive use of TMFORUM's models and APIs. Therefore if one is familiar with TMF APIs the terminology and ideas are the same.
To deliver NaaS we need to incorporate various APIs (see TMF909 API Suite Specification for NaaS). OpenSlice implements various TMF APIs to deliver NaaS and support the lifecycle functions required to manage the network capabilities exposed as Network as a Service and managed by operational domains.
For a complete list of supported APIs, see [Supported APIs](exposed_apis.md)
OpenSlice offers complete management of Service Catalogs which offer to end users:
* Service categories: Lists the available services, including their specifications and performance metrics.
* Service Bundles: Combines multiple services into a single offering to provide added value to customers.
Service Catalogs contain Service Specifications exposed to users for Service Orders.
In the UI this looks like this
## Example Use Case
Scenario: A service provider wants to offer a new managed XXXX service to enterprise customers.
* Service Definition: Service Template thus create a template for the XXXX service, including specifications for bandwidth, network features, and performance metrics.
* Service Catalog Integration: Add to Service Catalog the XXXX service with all relevant details.
* Service Delivery/Order: Provision Service by Using the orchestration system to provision and configure the XXXX service based on customer orders.
This section offers details on how to design Service Specifications and expose them in Service Catalogs
## Intended Audience: Service Designers
Service Designers create detailed service specifications, which are then managed and exposed in service catalogs. These services are integrated into OpenSlice E2E service orchestration framework to automate and optimize the delivery of network services.
OpenSlice can be used to design service specifications for various services, even not networking related services. Here we cover how service designers can expose services related to the NFV world and the containerized world.
## What's next
*[Design and expose services based on containerized resources via the Kubernetes Operator pattern](ExposingKubernetesResources.md)
*[Design and expose services based on NFV artifacts](./nfv/design_nfv_services.md)