Commit 08839b4e authored by Kostis Trantzas's avatar Kostis Trantzas
Browse files

Populating Service Ordering section (fix for #18)

parent 4bc732e2
Loading
Loading
Loading
Loading
Loading
+6 −3
Original line number Diff line number Diff line
# Catalogs and Templates

The OpenSlice Service Catalogue (accessible through the API or Services portal) contains the representation of Service Specifications, either created from the provider defining service attributes, or by supporting the GSMA Generic Slice Templates (GST) as well as the VINNI Service Blueprint. The following scenarios are supported by the OpenSlice Service Catalogue.
The OpenSlice Service Catalogue (accessible through the API or Services portal) contains the representation of Service Specifications, either created from the provider defining service attributes, or by supporting the GSMA Generic Slice Template (GST). The following scenarios are supported by the OpenSlice Service Catalogue.


## Create/Design a Service Specification
@@ -91,6 +91,9 @@ See more on [Consuming Services From External Partner Organizations]( ../getting

## Probe further

[Design Kubernetes-based Service Specifications](./kubernetes/exposing_kubernetes_resources.md/)
Design and expose services based on:

[Design NFV/OSM-based Service Specifications](./nfv/design_nfv_services.md)
* [Containerized resources via the Kubernetes Operator pattern](./kubernetes/exposing_kubernetes_resources.md)
* [NFV artifacts](./nfv/design_nfv_services.md)
* [Monitoring sources](./monitoring/design_monitoring_services.md)
* [Generic, developer-owned controllers](./generic/design_generic_services.md)
+3 −10
Original line number Diff line number Diff line
@@ -3,17 +3,10 @@
**Intended Audience: OpenSlice Service Designers**


This section offers details on how to design Service Specifications and expose them in Service Catalogs
This section offers details on how to design Service Specifications and expose them in Service Catalogs.

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.

## Probe further

* [Design and expose services based on containerized resources via the Kubernetes Operator pattern](./kubernetes/exposing_kubernetes_resources.md)
* [Design and expose services based on NFV artifacts](./nfv/design_nfv_services.md)
Service Designers create detailed Service Specifications, which are then managed and exposed in Service Catalogs. These services are integrated into OpenSlice end-to-end 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 ones. Here we cover how Service Designers can expose services, related to the cloud world (containerized/Kubernetes and NFV), monitoring domain, or even generic developer-owned ones.

+256 KiB
Loading image diff...
+119 KiB
Loading image diff...
+171 KiB
Loading image diff...
Loading