@@ -47,16 +47,16 @@ Refer to the official Kubernetes documentation for setting up a cluster. Ensure
### 2. Installing Helm
Helm must be installed on your machine to deploy OpenSlice via Helm charts. Follow the [official Helm installation guide](https://helm.sh/docs/intro/install/).
## Downloading the Project
## Downloading the project
### 1. Create a New Folder to Download the Project
### 1. Create a new folder to download the project
```bash
mkdir openslice
cd openslice
```
### 2. Download the Project Code
### 2. Download the project code
Clone the project code from the GitLab repository.
**Note:** This process will be simplified once the charts are published in the GitLab registry, requiring only the chart to be pulled.
@@ -69,9 +69,10 @@ cd kubernetes/helm/openslice/
Before deploying the Helm chart, ensure you have configured the necessary components as detailed in the [Configure Helm Chart Services](#configure-helm-chart-services) section. By default, the `main` branch is selected for deployment.
We recommend using:
- The **main** branch for the most stable experience.
- The **develop** branch for access to the latest features. For the develop branch installation, it's strongly advisable to follow the [develop documentation](https://osl.etsi.org/documentation/develop/deployment/).
We recommend:
* main branch for the most stable experience and
* develop branch for an experience with the latest features (for develop branch installation, it is strongly advisable that you may as well follow the [develop documentation](https://osl.etsi.org/documentation/develop/deployment/))
Deploy OpenSlice with Helm:
@@ -99,7 +100,7 @@ oscreds:
database:"keycloak"
username:"keycloak"
password:"password"
adminpassword:"keycloakadminpass"
adminpassword:"Pa55w0rd"
portal:
database:"osdb"
username:"portaluser"
@@ -138,7 +139,7 @@ oscreds:
database:"keycloak"
username:"keycloak"
password:"password"
adminpassword:"keycloakadminpass"
adminpassword:"Pa55w0rd"
```
#### 4. Application and Logging Configuration
@@ -177,10 +178,10 @@ In folder `kubernetes/helm/openslice/files/org.etsi.osl.portal.web/src/js` edit
The first 2 files above (i.e. config.prod.json, theming.scss) are essential for the successful deployment of OpenSlice.
Therefore, ensure that you check the `config.prod.json` and `theming.scss` files and readjust to your deployment if needed.
Default versions of such files exist in this path, which must be renamed to not include the `.default` suffix, before deploying OpenSlice.
The first 2 files above (i.e. config.prod.json, theming.scss) are essential for the successful deployment of OpenSlice, thus created automatically during the initial deployment at `org.etsi.osl.tmf.web/src/assets/config` directory as a copy of the default ones from the remote repository.
E.g. Edit "TITLE", "WIKI", etc properties with your domain title. Also configure TMF's API and Keycloak's location for the web application, if needed.
Ensure that you check the `config.prod.json` and `theming.scss` files and readjust to your deployment if needed.
```bash
# Starting from the root project directory
cd kubernetes/helm/openslice/files/org.etsi.osl.tmf.web/src/assets/config
```
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.
If you want to apply changes to the JSON configuration files without the need to rebuild the application, you have to apply the changes at the `org.etsi.osl.tmf.web/dist/io-openslice-portal-web/assets/config` directory. Although, it is <u>mandatory</u> to also apply these changes to the `org.etsi.osl.tmf.web/src/assets/config` for <u>persistancy</u>, as after any future rebuild of OpenSlice the `/dist` directory is being overwritten along with its contents. The OpenSlice team strongly recommends to always apply your changes to the TMF web UI configuration files at `org.etsi.osl.tmf.web/src/assets/config` and rebuild the application.
@@ -285,7 +302,6 @@ NAME READY STATUS RESTARTS AGE IP
@@ -347,7 +361,7 @@ The Keycloack server is managing authentication and running on a container at po
- Login with the credentials from section [Keycloak Configuration](#3-keycloak-configuration). Default values are:
- user: admin
- password: KEYCLOAK_PASSWORD
- password: Pa55w0rd
> if you are running in HTTP you will get a message: HTTPS required.
@@ -362,7 +376,7 @@ To resolve this issue <u>when running in HTTP</u>:
#### 1. Configure redirects
Navigate to realm Openslice > client > osapiWebClientId and change the Root URL to your domain.
Navigate to realm Openslice > Clients > osapiWebClientId and change the Root URL to your domain.
Also, insert your domain, e.g. http://example.org/*, at:
* Valid Redirect URIs
@@ -372,18 +386,21 @@ Also, insert your domain, e.g. http://example.org/*, at:
Keycloak allows new users to register. Subsequently, this will also allow new users to register to the OpenSlice portal.
On Tab Login > check User registration, Verify email, Forgot password etc.
Navigate to realm Openslice > Realm Settings > Login Tab > check User registration, Verify email, Forgot password etc.
Finally, enter the details of the mail server at the Email Tab.
> Email configuration is optional for test runs, but if not provided the above functionalities (e.g. external user registration) will not be possible.
Also, enter the details on Realm > Email > Enable Authentication.
#### 3. Add an OpenSlice admin user
This step is mandatory so as to access the OpenSlice Web UI. To add an OpenSlice admin user you must:
- Navigate to manage/users and add an OpenSlice admin user, e.g. username=admin.
- Navigate to realm Openslice > Users > Add user
- Set a password
-Navigate to Role Mappings and add ADMIN and MENTOR to Assigned Roles.
-Upon creation, navigate to Role Mappings and add ADMIN to Assigned Roles list
> That user is different from the Keycloak admin user. It is required to login and browse the OpenSlice Web UI. The Roles ADMIN and MENTOR guarantee full access through the Openslice UI, thus such a user is always required.
> That user is different from the Keycloak admin user. It is required to login and browse the OpenSlice Web UI. The Role ADMIN guarantee full access through the OpenSlice UI, thus such a user is always required.
***IMPORTANT: The following is not currently supported in Kubernetes installation.**
### Keycloak at localhost
@@ -422,19 +439,10 @@ cd org.etsi.osl.tmf.web/src/assets/config
nano config.prod.json
```
After editing it should look like the example bellow:
After editing, the displayed properties should look like the example below:
"WHO_WE_ARE_HTML":"<address class='font-weight-light'><span class='font-weight-bold'>ETSI SDG OpenSlice</span>|<a href='https://osl.etsi.org/' class='text-white'>https://osl.etsi.org</a><br>The ETSI Software Development Group for OpenSlice (SDG OSL) is developing an opensource service based Operations Support System (OSS) to deliver Network Slice as a Service (NSaaS).</address><address class='font-weight-light'><span class='font-weight-bold'>OpenSlice by ETSI</span>|<a href='http' class='text-white'>http://portal.openslice.io</a><br>A portal that allows 5G experimenters to design and deploy network services towards the infrastructure.</address><address class='font-weight-light'><span class='font-weight-bold'>OpenSlice by ETSI wiki</span>|<a href='https://osl.etsi.org/documentation' class='text-white'>https://osl.etsi.org/documentation</a><br>A wiki containing OpenSlice software documentation.</address>",