From 3a0e019f403ea5af467b6a79502601882a420941 Mon Sep 17 00:00:00 2001 From: Dimitrios Date: Wed, 3 Jul 2024 13:04:55 +0000 Subject: [PATCH] Deployed b33c131 to develop in public with MkDocs 1.6.0 and mike 2.1.2 --- public/develop/404.html | 2 +- .../OpenSlice_deployment_examples/index.html | 2 +- public/develop/alarms_actions/index.html | 2 +- .../CRIDGE/CRIDGEforDevelopers/index.html | 2 +- .../architecture/architecture/index.html | 2 +- .../architecture/centrallog/index.html | 2 +- .../index.html | 2 +- .../develop/architecture/issuemgt/index.html | 2 +- .../architecture/messagebus/index.html | 2 +- public/develop/architecture/nfvapi/index.html | 2 +- public/develop/architecture/nfvweb/index.html | 2 +- public/develop/architecture/oauth/index.html | 2 +- public/develop/architecture/osom/index.html | 2 +- public/develop/architecture/tmfapi/index.html | 2 +- public/develop/architecture/tmfweb/index.html | 2 +- public/develop/catalogs/index.html | 2 +- public/develop/config_intro/index.html | 2 +- .../contributing/developing/index.html | 2 +- .../develop/contributing/wishlist/index.html | 2 +- public/develop/deployment/index.html | 2 +- public/develop/deploymentCompose/index.html | 2 +- public/develop/deploymentK8s/index.html | 2 +- public/develop/etsi_osl/index.html | 2 +- public/develop/history/index.html | 2 +- public/develop/index.html | 2 +- public/develop/lcm/index.html | 2 +- public/develop/naas/exposed_apis/index.html | 2 +- public/develop/naas/introduction/index.html | 2 +- public/develop/naas/lcm_intro/index.html | 2 +- .../develop/naas/lcm_rules_intro/index.html | 2 +- public/develop/naas/nfv/intro/index.html | 2 +- .../develop/naas/nfv/nfvcatalogs/index.html | 2 +- .../develop/naas/resource_catalog/index.html | 2 +- .../naas/resource_inventory/index.html | 2 +- public/develop/naas/resource_spec/index.html | 2 +- .../develop/naas/service_catalog/index.html | 2 +- .../develop/naas/service_inventory/index.html | 2 +- public/develop/naas/service_spec/index.html | 2 +- public/develop/naas/so_intro/index.html | 2 +- .../index.html | 2 +- .../so_servicespec_to_services_nfv/index.html | 2 +- public/develop/nfvcatalogs/index.html | 2 +- public/develop/nfvoconfig/index.html | 2 +- .../ole_keycloak_management/index.html | 2 +- public/develop/search/search_index.json | 2 +- .../index.html | 8 +- .../develop/service_design/intro/index.html | 2 +- .../ExposingKubernetesResources/index.html | 8 +- .../index.html | 2 +- .../kubernetes/helm/design_helmaas/index.html | 2880 +++++++++++++++++ .../kubernetes/intro/index.html | 2 +- .../develop/service_design_intro/index.html | 2 +- public/develop/service_inventory/index.html | 2 +- public/develop/sitemap.xml | 5 + public/develop/sitemap.xml.gz | Bin 705 -> 716 bytes public/develop/terminology/index.html | 2 +- public/develop/under_construction/index.html | 2 +- 57 files changed, 2945 insertions(+), 60 deletions(-) create mode 100644 public/develop/service_design/kubernetes/helm/design_helmaas/index.html diff --git a/public/develop/404.html b/public/develop/404.html index 410847a2..d04aab5c 100644 --- a/public/develop/404.html +++ b/public/develop/404.html @@ -1390,7 +1390,7 @@
  • - + diff --git a/public/develop/OpenSlice_deployment_examples/index.html b/public/develop/OpenSlice_deployment_examples/index.html index b2f9f739..96f23e45 100644 --- a/public/develop/OpenSlice_deployment_examples/index.html +++ b/public/develop/OpenSlice_deployment_examples/index.html @@ -1515,7 +1515,7 @@
  • - + diff --git a/public/develop/alarms_actions/index.html b/public/develop/alarms_actions/index.html index 049a783b..d4b8c24f 100644 --- a/public/develop/alarms_actions/index.html +++ b/public/develop/alarms_actions/index.html @@ -1397,7 +1397,7 @@
  • - + diff --git a/public/develop/architecture/CRIDGE/CRIDGEforDevelopers/index.html b/public/develop/architecture/CRIDGE/CRIDGEforDevelopers/index.html index 5dade9be..6aac4f2f 100644 --- a/public/develop/architecture/CRIDGE/CRIDGEforDevelopers/index.html +++ b/public/develop/architecture/CRIDGE/CRIDGEforDevelopers/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/architecture/index.html b/public/develop/architecture/architecture/index.html index ff840964..1099f318 100644 --- a/public/develop/architecture/architecture/index.html +++ b/public/develop/architecture/architecture/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/centrallog/index.html b/public/develop/architecture/centrallog/index.html index 0ea431a2..29c661af 100644 --- a/public/develop/architecture/centrallog/index.html +++ b/public/develop/architecture/centrallog/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/consumingServicesFromExternalPartners/index.html b/public/develop/architecture/consumingServicesFromExternalPartners/index.html index 5022ea1c..ee40b992 100644 --- a/public/develop/architecture/consumingServicesFromExternalPartners/index.html +++ b/public/develop/architecture/consumingServicesFromExternalPartners/index.html @@ -1456,7 +1456,7 @@
  • - + diff --git a/public/develop/architecture/issuemgt/index.html b/public/develop/architecture/issuemgt/index.html index 739ca915..660bbeb2 100644 --- a/public/develop/architecture/issuemgt/index.html +++ b/public/develop/architecture/issuemgt/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/messagebus/index.html b/public/develop/architecture/messagebus/index.html index 60bcc734..29aa6017 100644 --- a/public/develop/architecture/messagebus/index.html +++ b/public/develop/architecture/messagebus/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/nfvapi/index.html b/public/develop/architecture/nfvapi/index.html index f54d1a98..54ca5a21 100644 --- a/public/develop/architecture/nfvapi/index.html +++ b/public/develop/architecture/nfvapi/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/nfvweb/index.html b/public/develop/architecture/nfvweb/index.html index 0873eb9c..09b1d6c0 100644 --- a/public/develop/architecture/nfvweb/index.html +++ b/public/develop/architecture/nfvweb/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/oauth/index.html b/public/develop/architecture/oauth/index.html index 01674587..1dc25646 100644 --- a/public/develop/architecture/oauth/index.html +++ b/public/develop/architecture/oauth/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/osom/index.html b/public/develop/architecture/osom/index.html index 623f7dd9..c29b2ead 100644 --- a/public/develop/architecture/osom/index.html +++ b/public/develop/architecture/osom/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/tmfapi/index.html b/public/develop/architecture/tmfapi/index.html index fd6b204b..985a3b94 100644 --- a/public/develop/architecture/tmfapi/index.html +++ b/public/develop/architecture/tmfapi/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/architecture/tmfweb/index.html b/public/develop/architecture/tmfweb/index.html index f5fa627a..7ff00d0c 100644 --- a/public/develop/architecture/tmfweb/index.html +++ b/public/develop/architecture/tmfweb/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/catalogs/index.html b/public/develop/catalogs/index.html index 41875636..2cfbf7e3 100644 --- a/public/develop/catalogs/index.html +++ b/public/develop/catalogs/index.html @@ -1397,7 +1397,7 @@
  • - + diff --git a/public/develop/config_intro/index.html b/public/develop/config_intro/index.html index 6b5ee465..1ca0bfcb 100644 --- a/public/develop/config_intro/index.html +++ b/public/develop/config_intro/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/contributing/developing/index.html b/public/develop/contributing/developing/index.html index 764d4144..0a0dba14 100644 --- a/public/develop/contributing/developing/index.html +++ b/public/develop/contributing/developing/index.html @@ -1401,7 +1401,7 @@
  • - + diff --git a/public/develop/contributing/wishlist/index.html b/public/develop/contributing/wishlist/index.html index eee920af..4bcf28fb 100644 --- a/public/develop/contributing/wishlist/index.html +++ b/public/develop/contributing/wishlist/index.html @@ -1397,7 +1397,7 @@
  • - + diff --git a/public/develop/deployment/index.html b/public/develop/deployment/index.html index b3cfa414..4d470d0d 100644 --- a/public/develop/deployment/index.html +++ b/public/develop/deployment/index.html @@ -1454,7 +1454,7 @@
  • - + diff --git a/public/develop/deploymentCompose/index.html b/public/develop/deploymentCompose/index.html index 5e338f0b..64c50b6c 100644 --- a/public/develop/deploymentCompose/index.html +++ b/public/develop/deploymentCompose/index.html @@ -1760,7 +1760,7 @@
  • - + diff --git a/public/develop/deploymentK8s/index.html b/public/develop/deploymentK8s/index.html index 409a0693..ea5aca09 100644 --- a/public/develop/deploymentK8s/index.html +++ b/public/develop/deploymentK8s/index.html @@ -1454,7 +1454,7 @@
  • - + diff --git a/public/develop/etsi_osl/index.html b/public/develop/etsi_osl/index.html index 10773da6..02cc3e9f 100644 --- a/public/develop/etsi_osl/index.html +++ b/public/develop/etsi_osl/index.html @@ -1413,7 +1413,7 @@
  • - + diff --git a/public/develop/history/index.html b/public/develop/history/index.html index 1ed16678..da207904 100644 --- a/public/develop/history/index.html +++ b/public/develop/history/index.html @@ -1457,7 +1457,7 @@
  • - + diff --git a/public/develop/index.html b/public/develop/index.html index b11e8c43..91f6cced 100644 --- a/public/develop/index.html +++ b/public/develop/index.html @@ -1506,7 +1506,7 @@
  • - + diff --git a/public/develop/lcm/index.html b/public/develop/lcm/index.html index 9b86b3bc..6a606a26 100644 --- a/public/develop/lcm/index.html +++ b/public/develop/lcm/index.html @@ -1397,7 +1397,7 @@
  • - + diff --git a/public/develop/naas/exposed_apis/index.html b/public/develop/naas/exposed_apis/index.html index d22960b9..bc65d2e8 100644 --- a/public/develop/naas/exposed_apis/index.html +++ b/public/develop/naas/exposed_apis/index.html @@ -1406,7 +1406,7 @@
  • - + diff --git a/public/develop/naas/introduction/index.html b/public/develop/naas/introduction/index.html index ba9de466..c68deeea 100644 --- a/public/develop/naas/introduction/index.html +++ b/public/develop/naas/introduction/index.html @@ -1406,7 +1406,7 @@
  • - + diff --git a/public/develop/naas/lcm_intro/index.html b/public/develop/naas/lcm_intro/index.html index ab028752..d2a7371a 100644 --- a/public/develop/naas/lcm_intro/index.html +++ b/public/develop/naas/lcm_intro/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/lcm_rules_intro/index.html b/public/develop/naas/lcm_rules_intro/index.html index 87c717c9..b6837df6 100644 --- a/public/develop/naas/lcm_rules_intro/index.html +++ b/public/develop/naas/lcm_rules_intro/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/nfv/intro/index.html b/public/develop/naas/nfv/intro/index.html index 9242cee0..821d91fa 100644 --- a/public/develop/naas/nfv/intro/index.html +++ b/public/develop/naas/nfv/intro/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/nfv/nfvcatalogs/index.html b/public/develop/naas/nfv/nfvcatalogs/index.html index 8297fd74..40985881 100644 --- a/public/develop/naas/nfv/nfvcatalogs/index.html +++ b/public/develop/naas/nfv/nfvcatalogs/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/resource_catalog/index.html b/public/develop/naas/resource_catalog/index.html index 1347a0da..c68da5d5 100644 --- a/public/develop/naas/resource_catalog/index.html +++ b/public/develop/naas/resource_catalog/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/resource_inventory/index.html b/public/develop/naas/resource_inventory/index.html index b0a15617..cdf1cc15 100644 --- a/public/develop/naas/resource_inventory/index.html +++ b/public/develop/naas/resource_inventory/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/resource_spec/index.html b/public/develop/naas/resource_spec/index.html index a77a4c66..f259f7eb 100644 --- a/public/develop/naas/resource_spec/index.html +++ b/public/develop/naas/resource_spec/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/service_catalog/index.html b/public/develop/naas/service_catalog/index.html index efe41cf1..b56f5cd5 100644 --- a/public/develop/naas/service_catalog/index.html +++ b/public/develop/naas/service_catalog/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/service_inventory/index.html b/public/develop/naas/service_inventory/index.html index b6cf7229..07000b8b 100644 --- a/public/develop/naas/service_inventory/index.html +++ b/public/develop/naas/service_inventory/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/service_spec/index.html b/public/develop/naas/service_spec/index.html index 6436c435..c702eb55 100644 --- a/public/develop/naas/service_spec/index.html +++ b/public/develop/naas/service_spec/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/so_intro/index.html b/public/develop/naas/so_intro/index.html index 90c89e45..bf44aa21 100644 --- a/public/develop/naas/so_intro/index.html +++ b/public/develop/naas/so_intro/index.html @@ -1408,7 +1408,7 @@
  • - + diff --git a/public/develop/naas/so_servicespec_to_services_kubernetes/index.html b/public/develop/naas/so_servicespec_to_services_kubernetes/index.html index 92dc8350..346abc0e 100644 --- a/public/develop/naas/so_servicespec_to_services_kubernetes/index.html +++ b/public/develop/naas/so_servicespec_to_services_kubernetes/index.html @@ -1410,7 +1410,7 @@
  • - + diff --git a/public/develop/naas/so_servicespec_to_services_nfv/index.html b/public/develop/naas/so_servicespec_to_services_nfv/index.html index 66345bba..5633e4a9 100644 --- a/public/develop/naas/so_servicespec_to_services_nfv/index.html +++ b/public/develop/naas/so_servicespec_to_services_nfv/index.html @@ -1410,7 +1410,7 @@
  • - + diff --git a/public/develop/nfvcatalogs/index.html b/public/develop/nfvcatalogs/index.html index c1a31383..853d35d9 100644 --- a/public/develop/nfvcatalogs/index.html +++ b/public/develop/nfvcatalogs/index.html @@ -1397,7 +1397,7 @@
  • - + diff --git a/public/develop/nfvoconfig/index.html b/public/develop/nfvoconfig/index.html index c5cbf5fa..94ed81b3 100644 --- a/public/develop/nfvoconfig/index.html +++ b/public/develop/nfvoconfig/index.html @@ -1415,7 +1415,7 @@
  • - + diff --git a/public/develop/ole_keycloak_management/index.html b/public/develop/ole_keycloak_management/index.html index c4adb751..149522c9 100644 --- a/public/develop/ole_keycloak_management/index.html +++ b/public/develop/ole_keycloak_management/index.html @@ -1392,7 +1392,7 @@
  • - + diff --git a/public/develop/search/search_index.json b/public/develop/search/search_index.json index 999e9bf9..fd9eea0b 100644 --- a/public/develop/search/search_index.json +++ b/public/develop/search/search_index.json @@ -1 +1 @@ -{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Introduction","text":"

    version: 2024Q2 - SNAPSHOT

    The ETSI Software Development Group for OpenSlice (SDG OSL) is developing an open-source service-based Operations Support System (OSS) to deliver Network as a Service (NaaS) following specifications from major SDOs including ETSI, TM Forum and GSMA.

    "},{"location":"#usage","title":"Usage","text":"

    OpenSlice can be used in managing 5G network services from the user device to the core network and cloud as well as for Orchestrating cloud resources across private and public clouds for enterprise applications. OpenSlice is capable of supporting most of the features of an end-to-end (E2E) service orchestration framework while many of them will be more mature in future releases. The following figure displays the general usage of OpenSlice.

    The image illustrates how OpenSlice supports the idea of an E2E network service orchestration framework by integrating multiple network components and layers, from user devices at the edge to radio, transport networks, core and public cloud services, ensuring seamless, secure, and efficient delivery of network services. Assuming that there are domain controllers for all the above domains OpenSlice can create the end-to-end service via the domain controllers by following the process of creating and deploying the end-to-end service by implementing transformations, and consuming APIs from various network entities. OpenSlice, in a nutchell, offers user interfaces where users can interact with the framework to order, expose, and manage service catalogs, services and resources that can be ordered, following business logic and policies and exposed through the APIs.

    "},{"location":"#an-end-to-end-e2e-service-orchestration-framework","title":"An end-to-end (E2E) service orchestration framework","text":"

    An end-to-end (E2E) service orchestration framework is designed to manage and automate the entire lifecycle of services across multiple domains and technologies. For delivering, especially, Network as a Service (NaaS) a comprehensive system is needed that automates and manages the entire lifecycle of network services, from provisioning to monitoring and decommissioning, while ensuring seamless integration, operation, and delivery of services from the initial request to the final delivery, spanning all involved components and layers. Such E2E frameworks enable users to consume network services on-demand, similar to how cloud computing services are consumed. Some key components and features of such frameworks are:

    • Service Catalogs including predefined Network Services based on service templates for common network services like 5G core functions, 5G slices, VPNs, SD-WAN, firewalls, load balancers, etc. as well as custom Network services with Options for users to define their own network configurations.
    • User Interface (UI) and APIs exposure, offering both a Self-Service Portal that allows users to request, configure, and manage network services as well as APIs for enabling programmatic access to network services for integration with other systems and automation scripts.
    • Service Design and Creation tharough service templates based on predefined models for creating services.
    • Automation and Workflow Management via Orchestration Engines, supporting Process Automation for automating repetitive tasks and processes, workflow management and orchestration for automating the provisioning, configuration, and management of network services while coordinating multiple workflows to ensure services are delivered efficiently, ensuring that services comply with predefined policies and standards.
    • Standardized API exposure for seamless integration with different systems and services and APIs transformation support for converting data formats and protocols to ensure compatibility and information exhange between systems during workflows orchestration
    • Service and Resource management and Orchestration while including the capability of multi-domain coordination in managing services/resources across different domains like cloud, 5G core, radios, transport network, and edge including dynamic allocation with adjusting resources based on demand and service requirements. To accomplish the above advanced technologies need to be exploited like, Containerized workloads, Network Function Virtualization (NFV) which uses virtualized network functions to provide services like routing, switching, and security and Software-Defined Networking (SDN) which Controls the network programmatically to dynamically manage traffic and resources.
    • Monitoring and Analytics including Service Monitoring while continuously tracking the performance and health of services with capabilities to analyse data to optimize service delivery and predict issues. Real-Time Monitoring is also needed for tracking the performance and health of network services enabling analytics that provide insights for optimization and troubleshooting.
    • Security and Access Control for ensuring only authorized users and systems can access network services. while implementing rules and policies to comply with regulatory requirements.
    "},{"location":"#an-e2e-service-orchestration-workflow","title":"An E2E service orchestration workflow","text":"

    In general an E2E service orchestration workflow includes the following phases:

    • Service Request: Users or systems request a network service through the self-service portal or API. The request can specify details such as bandwidth, security features, geographic coverage, and duration.
    • Service Orchestration: The orchestration engine evaluates the request, determines the necessary resources, and initiates the automated workflows.It interacts with the underlying components (e.g. 5G Core, Radios, Containerized controllers, NFV, SDN controllers ) to provision and configure the required network functions and connectivity.
    • Provisioning and Configuration: Services, network resources and network functions (VNFs) are instantiated and configured according to the service request during Service Orchestration through the orchestration engine. Other controllers manage their own domains, for example SDN controllers, manage the flow of data through the network to ensure optimal performance and adherence to policies, RAN controllers manage the RAN resoruces, Containerized controllers manage their workload, etc
    • Service Delivery: The E2E network service is activated and made available to the user. Continuous monitoring ensures the service operates as expected, with automatic adjustments made as necessary.
    • Lifecycle Management: The orchestration framework handles updates, scaling, and any necessary modifications throughout the service lifecycle.
    • At the end of the service period, resources are decommissioned and reclaimed.
    "},{"location":"#openslice-for-service-providers","title":"OpenSlice for Service Providers","text":"

    OpenSlice is used by Service Providers to design Network Services, expose them in Service Catalogues and make them available for Service Orders. OpenSlice then can perform the E2E service orchestration workflow.

    There are various portals offering UI friendly access to users acting as Service Providers:

    • The Services portal allows Service Providers to design and expose services.
    • The Resoruce portal allows users to access resource specifications and running resources in resource inventory.
    • The NFV portal allows users to manage NFV artifacts and onboard them to a target MANO/NFV Orchestrator.
    • The teting portal allows Service Providers to manage test artifacts
    • The Products portal allows Service Providers to expose services as products
    "},{"location":"#openslice-for-service-consumers","title":"OpenSlice for Service Consumers","text":"

    OpenSlice allows Service Consumers to browse the available offered service specifications in a self-service manner. It also supports TMFORUM Northbound APIs regarding Service Catalog Management, Ordering, Resource, etc. There are various portals offering UI friendly access to users acting as Service Consumers:

    • The Services portal allows Service Consumers to select and order predefined services.
    • The Resoruce portal allows users to access running resources in resource inventory.
    • The NFV portal allows users to self-manage NFV artifacts and onboard them to a target MANO/NFV Orchestrator.
    • The testing portal allows Service Consumers to manage test artifacts
    • The Products portal allows Service Consumers to expose services as products

    3rd party applications can use OpenSlice through TMForum Open APIs.

    "},{"location":"#live-demo","title":"Live Demo","text":"

    Check a live demo of OpenSlice in the following pages:

    (username=admin, password=openslice or username=admin, password=changeme)

    • OpenSlice demo: http://portal.openslice.io/
    • OpenSlice Service Catalogs and ordering: http://portal.openslice.io/services/
    • OpenSlice NFV Services onboarding: http://portal.openslice.io/nfvportal
    "},{"location":"#whats-next","title":"What's next","text":"

    Installing OpenSlice. See the Deployment of OpenSlice

    Lear more on how OpenSlice supports Network as a Service(NaaS)

    Who is implementing OpenSlice? See OSL ETSI SDG

    How OpenSlice works? See the Architecture of OpenSlice

    "},{"location":"OpenSlice_deployment_examples/","title":"OpenSlice deployment examples","text":"

    Here are some examples from past and current efforts that use OpenSlice in various cases.

    "},{"location":"OpenSlice_deployment_examples/#5ginfire-eu-project2018","title":"5GinFIRE EU project(2018)","text":"
    • MultiVIM approach
    • 9 Testbeds
    • Automotive, Smart City, eHeath, \u000bPPDR, Media, SDR, Cloud
    • 22 Experiment proposals from Verticals
    • 100+ Users
    • VxF catalog:
    • 150+ ONBOARDED VxFs
    • OSM TWO, FOUR, FIVE
    • 50+ are public to be reused
    • NSD catalog:
    • 90+ ONBOARDED NSDs
    • 30+ are public to be reused
    • 500+ Deployment requests \u000b(orchestrations) performed

    [

    "},{"location":"OpenSlice_deployment_examples/#5g-vinni-eu-project-2020","title":"5G-VINNI EU project (2020)","text":"
    • Multi-vendor challenge \u2013 Commercial and opensource
    • 5G services on multiple sites
    • Introduction of TMFORUM models and APIs

    [

    "},{"location":"OpenSlice_deployment_examples/#5gasp-eu-project-2021-2024","title":"5GASP EU project (2021-2024)","text":"
    • Support a multi-site CI/CD testing automated DevOps cycle for network Applications
    • Multiple NFVOs
    • Introducing Service Test models
    • Introducing the Product models for a network application marketplace

    [

    "},{"location":"OpenSlice_deployment_examples/#fidal-eu-project-2023-","title":"FIDAL EU project (2023-)","text":"
    • Support multi-site automated testing
    • Multiple testbeds/ different APIs

    [

    "},{"location":"OpenSlice_deployment_examples/#across-eu-project-2023-","title":"ACROSS EU project (2023-)","text":"
    • Used as a cross-domain orchestrator
    • Support the multi-domain orchestrator
    • Support Zero-touch provisioning concepts

    [

    "},{"location":"OpenSlice_deployment_examples/#incode-eu-project-2023-","title":"INCODE EU project (2023-)","text":"
    • Support the provisioning of end-to-end domain services

    [

    "},{"location":"OpenSlice_deployment_examples/#imagineb5g-eu-project-2023-","title":"IMAGINEB5G EU project (2023-)","text":"
    • Support the provisioning of end-to-end domain services
    "},{"location":"OpenSlice_deployment_examples/#etsi-zsm-poc-2","title":"ETSI ZSM PoC #2","text":"
    • Automated Network Slice Scaling in Multi-Site Environments

    [

    "},{"location":"alarms_actions/","title":"Alarms","text":"

    In Openslice parts of TMF642 Alarm Management API are currently implemented. Alarms can be managed through the TMF API endpoint as well as the UI.

    "},{"location":"alarms_actions/#alarms-and-actions","title":"Alarms and Actions","text":"

    Note: Actions is an experimental feature. We expect to have a more mature solution in future. The component in the architecture is the Openslcie Assurance Services

    Alarms can be automatically resolved by specific actions. Today only the following actions are offered.

    • execDay2
    • scaleServiceEqually
    "},{"location":"alarms_actions/#execday2","title":"execDay2","text":"

    Usually used to perform a Day2 configuration (towards OSM). To use it, Create a New Action Specification Name=execDay2 as following

    Now make a Service Order for your service. In this example \u03c2\u03b5 used a cirros NSD

    Create a New Action Rule for the running services as the following example:

    The scope is the running cirros service.

    Params should be paramname=value;paramname2=value2;paramname3=value3 (must exist in the VNF otherwise OSM will raise an error).

    In this case should be filename=test.txt

    Primitive=touch

    ServiceId = select the service which will accept the Day2. In this case is the same

    To test it:

    Go to the Service Inventory and select the active Service.

    Note the UUID of the service (e.g. c4e7990a-e174-4cd2-9133-b10e56721e08 copy from address bar), DeploymentRequestID and NSDID from characteristics

    You can either use the UUID of the service or the DeploymentRequestID and POST to the Alarms endpoint ( /tmf-api/alarmManagement/v4/alarm)

    If the DeploymentRequestID is used then POST:

    \n{\n  \"alarmRaisedTime\": \"2021-06-29T12:30:24.675Z\",\n  \"alarmReportingTime\": \"2021-06-29T12:30:54.675Z\",\n  \"state\": \"raised\",\n  \"alarmType\": \"qualityOfServiceAlarm\",\n  \"probableCause\": \"thresholdCrossed\",\n  \"ackState\": \"unacknowledged\",\n  \"perceivedSeverity\": \"major\",\n  \"sourceSystemId\": \"mano-client-service\",\n  \"alarmDetails\": \"NSID=3;DeploymentRequestID=1\",\n  \"specificProblem\": \"myalram raised\"\n}\n\n

    If the UUID is used then POST:

    \n{\n  \"alarmRaisedTime\": \"2021-06-29T12:30:24.675Z\",\n  \"alarmReportingTime\": \"2021-06-29T12:30:54.675Z\",\n  \"state\": \"raised\",\n  \"alarmType\": \"qualityOfServiceAlarm\",\n  \"probableCause\": \"thresholdCrossed\",\n  \"ackState\": \"unacknowledged\",\n  \"perceivedSeverity\": \"major\",\n  \"sourceSystemId\": \"mano-client-service\",\n  \"alarmDetails\": \"analarm\",\n  \"specificProblem\": \"myalram raised\",\n  \"affectedService\": [\n    {\n      \"id\": \"c4e7990a-e174-4cd2-9133-b10e56721e08\"\n    }\n  ]\n\n}\n\n

    The Alarm to be created must have the affected Service ID equal to the running service from the scope (the cirros_ns)

    Go to service inventory you will see the notes and also the service characteristics for any EXEC_ACTION updates

    You can also adjust the alarm conditions. They must match true so the alarm to be acknowledged So if another external service raises an Alarm (with POST) for the running service, a Day2 will be performed on another Service

    "},{"location":"alarms_actions/#scaleserviceequally","title":"scaleServiceEqually","text":"

    This action is used from getting a scaling event from OSM. Please see the next demo for details on how it works

    "},{"location":"alarms_actions/#prototype-demo","title":"Prototype demo","text":"

    You can watch how we used the prototype on the following ETSI ZMS PoC #2

    • ETSI ZMS PoC #2: https://www.etsi.org/events/1905-webinar-zsm-poc-2-showcase-automated-network-slice-scaling-in-multi-site-environments/
    "},{"location":"catalogs/","title":"Catalogs and Templates","text":"

    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.

    "},{"location":"catalogs/#createdesign-a-service-specification","title":"Create/Design a Service Specification","text":""},{"location":"catalogs/#first-import-some-resources-as-resource-facing-services-rfss","title":"First Import some Resources as Resource Facing Services (RFSs)","text":"

    If you have any NSDs as NFV artifacts, import them through the UI menu (Import from NSD list). Then an NSD is imported as a resource and an RFS automatically is created. RFSs then later are used to design a Customer Facing Service Specification

    "},{"location":"catalogs/#createdesign-a-customer-facing-service-specification","title":"Create/Design a Customer Facing Service Specification","text":"

    Customer Facing Service Specification are the services offered to customers. You can create a new Service Specification from the menu. The services created through the UI are Customer Facing Services (CFS). Usually you create a CFS as a bundle and then you include Service Specification Relationships with RFSs or/and CFSs.

    Any Service Specification Characteristics from the RFS are copied to the CFS specification. A CFS can include multiple RFS or/and CFSs. For example you can create a CFS spec called \"A 5G Service\" which is a bundle of two other services (include them in Service Specification Relationships) such as 5G eMBB Slice and a Customer VPN. So when the user orders \"A 5G Service\" services from 5G eMBB Slice and a Customer VPN will be created during the order.

    "},{"location":"catalogs/#initial-configuration-for-osm-deployment","title":"Initial configuration for OSM deployment","text":"

    if you have an initial configuration that needs to be applied in the NSD deployment, then you go to the RFS (or CFS) and in Service Specification Characteristics go and edit the OSM_CONFIG characteristic. You can add in the Service Characteristic Value, in the Value field something like the following example which gives a floating IP to a VNF:

    { \"nsdId\": \"e855be91-567b-45cf-9f86-18653e7ea\", \"vimAccountId\": \"4efd8bf4-5292-4634-87b7-7b3d49108\" , \"vnf\": [ {\"member-vnf-index\": \"1\", \"vdu\": [ {\"id\": \"MyCharmedVNF-VM\", \"interface\": [{\"name\": \"eth0\", \"floating-ip-required\": true }]}]}]}\n\n

    or a more complex example (beautify it first if you want to view it, but in the parameter OSM_CONFIG must be minified like the example):

    {\"nsdId\":\"e855be91-567b-45cf-9f86-18653e7\",\"vimAccountId\":\"4efd8bf4-5292-4634-87b7-7b3d491\",\"vnf\":[{\"member-vnf-index\":\"1\",\"vdu\":[{\"id\":\"haproxy_vdu\",\"interface\":[{\"name\":\"haproxy_vdu_eth1\",\"floating-ip-required\":true}]}]}],\"vld\":[{\"name\":\"pub_net\",\"vim-network-name\":\"OSMFIVE_selfservice01\"},{\"name\":\"management\",\"vim-network-name\":\"OSMFIVE_selfservice01\"},{\"name\":\"lba_net\",\"vim-network-name\":\"lba_net\",\"vnfd-connection-point-ref\":[{\"member-vnf-index-ref\":\"1\",\"vnfd-connection-point-ref\":\"haproxy_private\",\"ip-address\":\"192.168.28.2\"}]},{\"name\":\"backend_net\",\"vim-network-name\":\"backend_net\",\"vnfd-connection-point-ref\":[{\"member-vnf-index-ref\":\"3\",\"vnfd-connection-point-ref\":\"haproxy_public\",\"ip-address\":\"192.168.20.2\"}]},{\"name\":\"lb_sb_net\",\"vim-network-name\":\"lb_sb_net\",\"vnfd-connection-point-ref\":[{\"member-vnf-index-ref\":\"3\",\"vnfd-connection-point-ref\":\"haproxy_private\",\"ip-address\":\"192.168.28.2\"}]},{\"name\":\"breaking_point_Spain\",\"vim-network-name\":\"sb_repo_net\"},{\"name\":\"breaking_point_Greece\",\"vim-network-name\":\"5TONICexternal\"}],\"additionalParamsForVnf\":[{\"member-vnf-index\":\"2\",\"additionalParams\":{\"target_IP\":\"192.168.20.2\"}},{\"member-vnf-index\":\"4\",\"additionalParams\":{\"target1_IP\":\"192.168.21.2\",\"target2_IP\":\"10.154.252.10\"}}]}\n

    You can leave the Alias and Unit of Measure as is. Check also the is Default.

    "},{"location":"catalogs/#day-2-primitive-actions","title":"Day 2 Primitive Actions","text":"

    NFVOs like OSM allow to perform actions while a service is running, for example change attributes or make actions on a specific VNF. To design this do something similar to the following example: