Service Inventory contains refences to running services that realize a Service Order
## Intended Audience: Service Designers, OpenSlice administrators, Users
The Service Inventory is a repository that maintains detailed records of all active services and the underlying resources that support them. It acts as a central repository, tracking the lifecycle of each service from provisioning to decommissioning, and includes references to the specific virtual and physical resources that realize the service, such as servers, network components, storage, and software instances.
This inventory enables real-time visibility into the status, configuration, and dependencies of each service, facilitating effective management, troubleshooting, and optimization.
By providing a view of the active services, the Service Inventory includes services/resource allocation, and ensures that services are delivered in alignment with the inital requst.
## UI management
Through the menu and dedicated forms the administrator can manage the Service Inventory and any active Services (reconfigure or terminate).Various examples in this document will guide you to the usage and the management of the Services in Service Inventory.
## API exposed
When installing OpenSlice the API endpoints can be browsed at:
Customer Facing Service Specifications - or also CFSSpec (organized in Service Categories) are exposed to users for Service Orders.
## Intended Audience: Service Designers, OpenSlice administrators
The Service Order process is a structured sequence of steps initiated by a customer's Service Order request for a specific service, aimed at delivering and activating the desired service or services (if it is a service bunlde), as well as its related services. It begins with the customer submitting a service request through OpenSlice Services portal or the Service Order API, specifying the necessary details such as service specification, configurations, and any specific requirements.
The request is then validated and verified for completeness and eligibility by an administrator which marks the Service Order as ACKNOWLEDGED otherwise it rejects it.
Once ACKNOWLEDGED, the service order is processed by OpenSlice orchestration system (OSOM), which schedules/automates the provisioning of the required resources and configurations, coordinating across various components such as MANO controlers for virtual network functions (VNFs), or Containerized controllers or any 3rd party controllers or services or even physical infrastructure. The OpenSlice orchestration system ensures that all dependencies are managed and that the service is correctly configured.
After provisioning, the service is activated and handed over to the customer, . This end-to-end process ensures a seamless, efficient, and automated delivery of services, enhancing customer satisfaction and operational efficiency.
Ongoing monitoring and other actions can be performed by the Life Cycle management rules
<i>***Future developments***:
In future releases it might be possible the ongoing monitoring and support provided to ensure continuous performance and reliability. The service could undergoe a series of tests to ensure it meets the specified performance metrics and SLAs before delivering</i>
## What's next ##
* See [Ordering Services from catalogs](../service_ordering/ordering_services.md)
* See [Service Design](../service_design/intro.md)
Through the menu and dedicated forms the administrator can manage the Service Specifications. Various examples in this document will guide you to the usage and the design of the services.
## API exposed
@@ -66,7 +60,7 @@ endpoint examples:
Scenario: A service provider wants to offer a new managed XXXX service to enterprise customers.
* Service Definition: SCreate a service specification template for the XXXX service, including specifications for bandwidth, network features, and performance metrics.
* Service Definition: Create a service specification template for the XXXX service, including specifications for bandwidth, network features, and performance metrics.
