Openslice is a prototype open source, operations support system. It supports VNF/NSD onboarding to OpenSourceMANO (OSM) and NSD deployment management. It also supports TMFORUM OpenAPIs regarding Service Catalog Management, Ordering, Resource, etc.
...
...
@@ -22,13 +22,13 @@ There are two portals offering UI friendly access to users:
Service Specifications reside into Service Catalogs, grouped in Categories. Openslice offers a Service Orchestrator called [OSOM](./architecture/osom.md). OSOM instantiates Service Specifications by requesting Network Services from target MANOs/NFVOs. NFV artifacts reside into a VNF/NSD catalog and are onboarded to a target MANO/NFV Orchestrator. Service Specifications reference NSD from the VNF/NSD catalog.
Customers make Service Orders and Openslice instantiates the requested Service Specifications of the Service Order. Running Services instantiated by Openslice, reside in Openslice Service Inventory. The following picture displays how Service Specifications are related to Running Services and how Running Services relate with instantiated running Network Services. (See also [Service Inventory](./service_inventory.md))
Customers make Service Orders and Openslice instantiates the requested Service Specifications of the Service Order. Running Services instantiated by Openslice, reside in Openslice Service Inventory. The following picture displays how Service Specifications are related to Running Services and how Running Services relate with instantiated running Network Services. (See also [Service Inventory](./service_inventory.md))
[](./images/service_specification_instantiation.png)
## Service Lifecycle Rules
Openslice constains support for defining rules of services, affecting their behavior. See [LCm Rules](./lcm.md)
Openslice constains support for defining rules of services, affecting their behavior. See [LCM Rules](./lcm.md).
## Multidomain scenarios and federation
...
...
@@ -36,9 +36,9 @@ Openslice can be used to exchange service specifications/catalogs and make servi
[](./images/multi-domain-organizations.png)
An Identity federation is also possible since our authentication service is based on Keycloak (see [OAuth](./architecture/oauth.md))
An Identity federation is also possible since our authentication service is based on Keycloak (see [OAuth](./architecture/oauth.md)).
See more on [Consuming Services From External Partner Organizations](./architecture/consumingServicesFromExternalPartners.md)
See more on [Consuming Services From External Partner Organizations](./architecture/consumingServicesFromExternalPartners.md).
## Live Demo
...
...
@@ -57,13 +57,13 @@ See more on [Consuming Services From External Partner Organizations](./architect
## Installing
See [Deployment/Installation](./deployment.md)
See [Deployment/Installation](./deployment.md).
---
## Hardware requirements
The complete environment consists of microservices deployed as docker containers. Portainer is also installed to monitor them at port 9000
The complete environment consists of microservices deployed as docker containers. Portainer is also installed to monitor them at port 9000.
If you would like to operate all APIs, OSOM, the Mysql Server, nginx, etc then you need at least:
...
...
@@ -84,12 +84,12 @@ However you can try with a minimum installation on a VM on a laptop with:
