Commit c136454e authored by Dimitrios Giannopoulos's avatar Dimitrios Giannopoulos
Browse files

Deployed 91750aa3 to develop in public with MkDocs 1.6.0 and mike 2.1.2

parent 961c0c61

public/develop/naas/lcm/img01.png

0 → 100644
+416 KiB
Loading image diff...

public/develop/naas/lcm_intro/index.html

+430 −3
Original line number Diff line number Diff line
@@ -75,6 +75,11 @@ 
    <label class="md-overlay" for="__drawer"></label>

    <div data-md-component="skip">

      

        

        <a href="#lifecycle-management-lcm" class="md-skip">

          Skip to content

        </a>

      

    </div>

    <div data-md-component="announce">
@@ -1111,6 +1116,19 @@ 
      

      

        

      

      

        <label class="md-nav__link md-nav__link--active" for="__toc">

          

  

  <span class="md-ellipsis">

    Service Lifecycle management

  </span>

  



          <span class="md-nav__icon md-icon"></span>

        </label>

      

      <a href="./" class="md-nav__link md-nav__link--active">
@@ -1121,6 +1139,172 @@ 


      </a>

      

        



<nav class="md-nav md-nav--secondary" aria-label="Table of contents">

  

  

  

    

  

  

    <label class="md-nav__title" for="__toc">

      <span class="md-nav__icon md-icon"></span>

      Table of contents

    </label>

    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>

      

        <li class="md-nav__item">

  <a href="#intended-audience-service-designers" class="md-nav__link">

    <span class="md-ellipsis">

      Intended Audience: Service Designers

    </span>

  </a>

  

</li>

      

        <li class="md-nav__item">

  <a href="#introduction-in-openslice-lcm" class="md-nav__link">

    <span class="md-ellipsis">

      Introduction in OpenSlice LCM

    </span>

  </a>

  

    <nav class="md-nav" aria-label="Introduction in OpenSlice LCM">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#0-preparation-phase" class="md-nav__link">

    <span class="md-ellipsis">

      0. Preparation Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="0. Preparation Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-design" class="md-nav__link">

    <span class="md-ellipsis">

      Service Design:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#1-instantiation-phase" class="md-nav__link">

    <span class="md-ellipsis">

      1. Instantiation Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="1. Instantiation Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-instantiation" class="md-nav__link">

    <span class="md-ellipsis">

      Service Instantiation:

    </span>

  </a>

  

</li>

        

          <li class="md-nav__item">

  <a href="#service-deployment" class="md-nav__link">

    <span class="md-ellipsis">

      Service Deployment:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#2-operation-phase" class="md-nav__link">

    <span class="md-ellipsis">

      2. Operation Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="2. Operation Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-operation" class="md-nav__link">

    <span class="md-ellipsis">

      Service Operation:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#3-decommissioning-phase" class="md-nav__link">

    <span class="md-ellipsis">

      3. Decommissioning Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="3. Decommissioning Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-decommissioning" class="md-nav__link">

    <span class="md-ellipsis">

      Service Decommissioning:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#high-level-example-enhanced-mobile-broadband-embb-service-lifecycle" class="md-nav__link">

    <span class="md-ellipsis">

      High level example: Enhanced Mobile Broadband (eMBB) Service Lifecycle

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

      

        <li class="md-nav__item">

  <a href="#probe-further" class="md-nav__link">

    <span class="md-ellipsis">

      Probe further

    </span>

  </a>

  

</li>

      

    </ul>

  

</nav>

      

    </li>
@@ -2615,6 +2799,163 @@ 
  

  

    

  

  

    <label class="md-nav__title" for="__toc">

      <span class="md-nav__icon md-icon"></span>

      Table of contents

    </label>

    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>

      

        <li class="md-nav__item">

  <a href="#intended-audience-service-designers" class="md-nav__link">

    <span class="md-ellipsis">

      Intended Audience: Service Designers

    </span>

  </a>

  

</li>

      

        <li class="md-nav__item">

  <a href="#introduction-in-openslice-lcm" class="md-nav__link">

    <span class="md-ellipsis">

      Introduction in OpenSlice LCM

    </span>

  </a>

  

    <nav class="md-nav" aria-label="Introduction in OpenSlice LCM">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#0-preparation-phase" class="md-nav__link">

    <span class="md-ellipsis">

      0. Preparation Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="0. Preparation Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-design" class="md-nav__link">

    <span class="md-ellipsis">

      Service Design:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#1-instantiation-phase" class="md-nav__link">

    <span class="md-ellipsis">

      1. Instantiation Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="1. Instantiation Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-instantiation" class="md-nav__link">

    <span class="md-ellipsis">

      Service Instantiation:

    </span>

  </a>

  

</li>

        

          <li class="md-nav__item">

  <a href="#service-deployment" class="md-nav__link">

    <span class="md-ellipsis">

      Service Deployment:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#2-operation-phase" class="md-nav__link">

    <span class="md-ellipsis">

      2. Operation Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="2. Operation Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-operation" class="md-nav__link">

    <span class="md-ellipsis">

      Service Operation:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#3-decommissioning-phase" class="md-nav__link">

    <span class="md-ellipsis">

      3. Decommissioning Phase

    </span>

  </a>

  

    <nav class="md-nav" aria-label="3. Decommissioning Phase">

      <ul class="md-nav__list">

        

          <li class="md-nav__item">

  <a href="#service-decommissioning" class="md-nav__link">

    <span class="md-ellipsis">

      Service Decommissioning:

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

        

          <li class="md-nav__item">

  <a href="#high-level-example-enhanced-mobile-broadband-embb-service-lifecycle" class="md-nav__link">

    <span class="md-ellipsis">

      High level example: Enhanced Mobile Broadband (eMBB) Service Lifecycle

    </span>

  </a>

  

</li>

        

      </ul>

    </nav>

  

</li>

      

        <li class="md-nav__item">

  <a href="#probe-further" class="md-nav__link">

    <span class="md-ellipsis">

      Probe further

    </span>

  </a>

  

</li>

      

    </ul>

  

</nav>

                  </div>

                </div>
@@ -2628,10 +2969,96 @@ 
                  





  <h1>Service Lifecycle management</h1>



<h1 id="lifecycle-management-lcm">Lifecycle Management - LCM</h1>

<p>Lifecycle Management: The orchestration framework handles updates, scaling, and any necessary modifications throughout the service lifecycle.</p>

<h2 id="intended-audience-service-designers">Intended Audience: Service Designers</h2>

<p>In OpenSlice the Lifecycle of a service follows in general the concept of Network Slice lifecycle as defined by 3GPP.</p>

<p><a href="../lcm/img01.png"><img alt="lcm" src="../lcm/img01.png" /></a></p>

<h2 id="introduction-in-openslice-lcm">Introduction in OpenSlice LCM</h2>

<p>OpenSlice Adopted adopted the LCM model by 3GPP and mapped to the TMF model service state. Next we discuss briefly the process and the relationships.</p>

<p>The lifecycle of a service, particularly in the context of Network Service lifecycleencompasses several stages that ensure the service is effectively planned, deployed, managed, and eventually decommissioned. </p>

<p>Here is an overview of these stages and relationships with OpenSlice:</p>

<h3 id="0-preparation-phase">0. Preparation Phase</h3>

<p>This phase is performed by Service Designers</p>

<h4 id="service-design">Service Design:</h4>

<ul>

<li><strong>Requirements Gathering:</strong> Collect service requirements from stakeholders, including performance metrics, quality of service (QoS), security needs, and geographical coverage.</li>

<li><strong>Service Specification:</strong> Define the service in terms of functionalities, attributes, and dependencies. This can be formalized using standardized templates such as the GSMA Generic Slice Template (GST).</li>

<li><strong>Resource Planning:</strong> Identify and plan the required resources, including network functions, computing power, storage, and connectivity, inclluding network function configurations.</li>

<li><strong>Expose to Service Catalog</strong>:  Expose to service catalog for user ordering.</li>

</ul>

<p><strong>Next phases are handled by the Service Orchestrator after a service is scheduled for instantiation</strong></p>

<p><strong>If it is a bundle of services, each services follows its own Lifecycle!</strong></p>

<h3 id="1-instantiation-phase">1. Instantiation Phase</h3>

<h4 id="service-instantiation">Service Instantiation:</h4>

<ul>

<li><strong>Configuration:</strong> Configure the network service according to the specifications includin the user requirements from the service order, ensuring that all components are correctly set up to provide the desired service.</li>

<li><strong>Resource Allocation - Feasibility check:</strong> Allocate the necessary physical and virtual resources based on the service specification. This includes any containerized resources, virtual network functions (VNFs) and software-defined networking (SDN) components. (This step is not perfromed in OpenSlice)</li>

<li>OpenSlice Service Orchestrator creates the services at "RESERVED" state</li>

<li><strong>User Notification:</strong>  There could be an email notification from the system (if Bugzilla is configured)</li>

</ul>

<h4 id="service-deployment">Service Deployment:</h4>

<ul>

<li><strong>Activation:</strong> OpenSlice Service Orchestrator activates the network service and makes the service available to the end-users. This may involve:</li>

<li>Create any related services that the service depends on</li>

<li>Contacting all related controllers during provisioning, e.g. Kubernetes controllers, Kubernetes operators, MANO Orchestrators, RAN controllers, SDN Controlles, or other external services (e.g. via REST calls)</li>

<li>Scheduling instantiation, Resolving dependencies and passing paramemters between controllers,</li>

<li>setting up user accounts, provisioning access credentials -this is performed either offline or via other services.</li>

<li>OpenSlice Service Orchestrator if everything is succesful put the service at "ACTIVE" state</li>

<li><strong>User Notification:</strong>  There could be an email notification from the system (if Bugzilla is configured)</li>

</ul>

<h3 id="2-operation-phase">2. Operation Phase</h3>

<h4 id="service-operation">Service Operation:</h4>

<ul>

<li><strong>Lifecycle Management:</strong> Manage the network slice throughout its lifecycle, including scaling, reconfiguration, and adaptation to changing requirements. </li>

<li>In OpenSlice this is performed with Lifecycle management Rules (see next)</li>

</ul>

<p>In this phase the Service Designer can define several aspects.  <strong>Be aware that these are NOT performed automatically by OpenSlice - further examples and future enhancements will address these</strong>. This could include:</p>

<ul>

<li><strong>Monitoring:</strong> Continuously monitor the service for performance, availability, and compliance with SLAs. Utilize tools for real-time tracking and alerts for any anomalies or performance degradation.</li>

<li><strong>Maintenance:</strong> Conduct regular maintenance activities, including software updates, patching, and optimization to ensure the service runs smoothly.</li>

<li><strong>Scaling:</strong> Dynamically scale the resources up or down based on the demand and performance requirements.</li>

<li><strong>Fault Management:</strong> Detect and resolve faults in the network slice to minimize downtime and maintain service quality.</li>

</ul>

<h3 id="3-decommissioning-phase">3. Decommissioning Phase</h3>

<h4 id="service-decommissioning">Service Decommissioning:</h4>

<p><strong>Service Termination:</strong> Service Orchestrator terminates the network service . This may involve:

  - Terminate any related services that the service depends on

  - Contacting all related controllers during termination to release resources, e.g. Kubernetes controllers, Kubernetes operators, MANO Orchestrators, RAN controllers, SDN Controlles, or other external services (e.g. via REST calls)

  - Scheduling termination, Resolving dependencies and passing paramemters between controllers

- OpenSlice Service Orchestrator if everything is succesful put the service at "TERMINATED" state

- <strong>User Notification:</strong>  There could be an email notification from the system (if Bugzilla is configured)</p>

<h3 id="high-level-example-enhanced-mobile-broadband-embb-service-lifecycle">High level example: Enhanced Mobile Broadband (eMBB) Service Lifecycle</h3>

<ol>

<li><strong>Preparation:</strong></li>

<li>Define eMBB service requirements for high bandwidth and low latency.</li>

<li>Create an eMBB service specification template specifying related services and resources to Kubernetes Operators, VNFs for content delivery and traffic management.</li>

<li>

<p>Expose to catalog</p>

</li>

<li>

<p><strong>Instantiation:</strong></p>

</li>

<li>Instantiate other services and allocate resources such as edge computing nodes and high-capacity links.</li>

<li>

<p>Configure the service to prioritize video streaming traffic.</p>

</li>

<li>

<p><strong>Operation:</strong></p>

</li>

<li>Monitor the service to ensure it meets high-bandwidth requirements.</li>

<li>

<p>Scale up resources during peak usage periods, such as live sports events.</p>

</li>

<li>

<p><strong>Decommissioning:</strong></p>

</li>

<li>Notify users about service termination.</li>

<li>Decommission the network service, reclaiming resources for other services.</li>

</ol>

<h2 id="probe-further">Probe further</h2>

<ul>

<li>Lifecycle Management: The orchestration framework handles updates, scaling, and any necessary modifications throughout the service lifecycle.</li>

<li>See 3GPP <a href="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3091">Lifecycle</a></li>

</ul>

public/develop/search/search_index.json

+1 −1

File changed.

Preview size limit exceeded, changes collapsed.