<li>main branch for the most stable experience and</li>
<li>develop branch for an experience with the latest features (for develop branch installation, it is strongly advisable that you may as well follow the <ahref="https://osl.etsi.org/documentation/develop/deployment/">develop documentation</a>)</li>
<li>develop branch for an experience with the latest features (for develop branch installation, it is strongly advisable that you may as well follow the <ahref="https://osl.etsi.org/documentation/develop/">develop documentation</a>)</li>
</ul>
<divclass="language-bash highlight"><pre><span></span><code><spanid="__span-8-1"><aid="__codelineno-8-1"name="__codelineno-8-1"href="#__codelineno-8-1"></a>sudo<spanclass="w"></span>./deploy.sh<spanclass="w"></span>develop<spanclass="w"></span><spanclass="c1">#[or replace main with other branch name]</span>
<divclass="language-bash highlight"><pre><span></span><code><spanid="__span-8-1"><aid="__codelineno-8-1"name="__codelineno-8-1"href="#__codelineno-8-1"></a>sudo<spanclass="w"></span>./deploy.sh<spanclass="w"></span>main<spanclass="w"></span><spanclass="c1">#[or replace main with other branch name]</span>
</span></code></pre></div>
<blockquote>
<p><strong>We recommend running the deploy.sh script with root permissions! In other case, some directories may not be accessible by the project building tools and hinder the smooth installation.</strong></p>
</span><spanid="__span-26-2"><aid="__codelineno-26-2"name="__codelineno-26-2"href="#__codelineno-26-2"></a><spanclass="w"></span><spanclass="nt">"TITLE"</span><spanclass="p">:</span><spanclass="w"></span><spanclass="s2">"OpenSlice by ETSI"</span><spanclass="p">,</span>
<h3id="3-prerequisites-before-deployment">3. Prerequisites before deployment</h3>
<p>Before deploying the Helm chart, ensure you have configured the necessary components as detailed in the following section, i.e. <ahref="#configure-helm-chart">Configure Helm Chart Services</a>. By default, the <code>main</code> branch is selected for deployment.</p>
<p>Before deploying the Helm chart, ensure you have configured the necessary components as detailed in the following section, i.e. <ahref="#configure-helm-chart">Configure Helm Chart Services</a>.</p>
<p>We recommend:</p>
<ul>
<li>main branch for the most stable experience and</li>
<li>develop branch for an experience with the latest features (for develop branch installation, it is strongly advisable that you may as well follow the <ahref="https://osl.etsi.org/documentation/develop/deployment/">develop documentation</a>)</li>
<li>develop branch for an experience with the latest features (for develop branch installation, it is strongly advisable that you may as well follow the <ahref="https://osl.etsi.org/documentation/develop/">develop documentation</a>)</li>
<p>When deploying OpenSlice with Helm, service configurations are handled through the <code>values.yaml</code> file. This file allows you to define all necessary configurations for your deployment, including database credentials, service URLs, and logging levels. Below are examples of how to configure your services in Helm based on your provided values.</p>
@@ -3354,7 +3354,7 @@ Replace <code><helm-release-name></code> with the name of your OpenSlice H
<p>E.g. You may edit "TITLE", "WIKI", etc properties with your domain title. Also configure TMF's API and Keycloak's location for the web application, if needed.</p>
</span><spanid="__span-19-2"><aid="__codelineno-19-2"name="__codelineno-19-2"href="#__codelineno-19-2"></a><spanclass="w"></span><spanclass="nt">"TITLE"</span><spanclass="p">:</span><spanclass="w"></span><spanclass="s2">"OpenSlice by ETSI"</span><spanclass="p">,</span>
<p>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.</p>
<h2id="usage">Usage</h2>
<p>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. </p>