fix for #9

and add:

```

```json

{ 

  "dns": ["8.8.8.8", "8.8.4.4"]

}

In folder `org.etsi.osl.main/compose/` edit the file `docker-compose.yaml`

```

```json

SPRING_APPLICATION_JSON: '{

  "spring.activemq.brokerUrl": "tcp://anartemis:61616?jms.watchTopicAdvisories=false",

  "spring.activemq.user": "artemis",

In folder `org.etsi.osl.main/compose/` edit the file `docker-compose.yaml`

```

```json

SPRING_APPLICATION_JSON: '{

  "spring.datasource.username":"root",

  "spring.datasource.password":"letmein",

In folder `org.etsi.osl.main/compose/` edit the file `docker-compose.yaml`

```

```json

SPRING_APPLICATION_JSON: '{

  "spring.datasource.username":"root",

  "spring.datasource.password":"letmein",

Example file:

```

```json

{	  

  BUGZILLA: "ROOTURL/bugzilla/",

  STATUS: "ROOTURL/status/",

  APIURL: "http://localhost",

  WEBURL: "ROOTURL/nfvportal",

  APIOAUTHURL: "ROOTURL/auth/realms/openslice",

  APITMFURL: "ROOTURL/tmf-api/serviceCatalogManagement/v4"

  "BUGZILLA": "ROOTURL/bugzilla/",

  "STATUS": "ROOTURL/status/",

  "APIURL": "http://localhost",

  "WEBURL": "ROOTURL/nfvportal",

  "APIOAUTHURL": "ROOTURL/auth/realms/openslice",

  "APITMFURL": "ROOTURL/tmf-api/serviceCatalogManagement/v4"

}

```

Example file:

```

```json

{	      

    "TITLE": "OpenSlice by ETSI",

    "PORTALVERSION":"2024Q2",

2 - Replace http://localhost/auth/ with http://keycloak:8080/auth/ in your Keycloak config for AngularJS and Angular (see examples below).

> Explanation

Nginx uses the http://keycloak:8080 URL, which is accessible via the internal docker system's network.

> **Explanation**: Nginx uses the http://keycloak:8080 URL, which is accessible via the internal docker system's network.

The Front-end (TS/Angular) shall also use the http://keycloak:8080.

This way, you will not get the invalid token error, as the API is acquiring the token from http://keycloak:8080 (internally) and the Front-end is getting verified by an issuer at the same URL, as well.

After editing, the displayed properties should look like the example below:

```yaml

```json

{	      

  "OAUTH_CONFIG" : {

      "issuer": "http://keycloak:8080/auth/realms/openslice",

After editing, the displayed properties should look like the example below:

```

```js

var appConfig = angular.module('portalwebapp.config',[]);

            helm upgrade nginx-ingress ingress-nginx/ingress-nginx --namespace ingress \

            --set tcp.61616="<openslice-namespace>/<openslice-helm-release-name>-artemis:61616"

            ```

            Replace `<helm-release-name>` with the name of your OpenSlice Helm release.

        * More details regarding the Nginx Ingress Controller (Kubernetes Community Edition) can be found [here](https://kubernetes.github.io/ingress-nginx/deploy/).

    * **Other Ingress Controller:**  For non-Nginx ingress controllers, modify `[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml` to meet your controller’s requirements.

### Exposure

### Additional Configuration

* **Storage Class:** In a production environment, specify your `storageClass` in `[repo-root]/kubernetes/helm/openslice/values.yaml` under `storageClass`. If not defined, PVs will be created and managed manually.

    * **Disclaimer:** Before deploying, confirm that your storage system supports claims of one 10G and two 1G volumes.

> **Disclaimer:** Before deploying, confirm that your storage system supports claims of one 10G and two 1G volumes.

## Preparing the environment

When deploying OpenSlice with Helm, service configurations are handled through the `values.yaml` 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.

### Configuring Services

#### 1. Database Configuration

### Database

To configure MySQL and other related services, you can directly set the values in your `values.yaml` file under the `oscreds` and `mysql` sections. For example:

      password: "12345"

```

#### 2. Keycloak Configuration

### Keycloak

Keycloak settings, including the database and admin password, are part of the `oscreds.mysql.keycloak` section. If you need to adjust Keycloak-specific settings like realms or client configurations, you'll likely need to customize your Helm chart further or manage these settings directly within Keycloak after deployment. The Keycloak realm configuration that is imported by default can be found under `kubernetes/helm/openslice/files/keycloak-init/realm-export.json`.

      adminpassword: "Pa55w0rd"

```

#### 3. CRIDGE Configuration

### CRIDGE

To create and manage Kubernetes Custom Resources (CRs), you have to install and configure the CRIDGE component. 

There are two ways to install CRIDGE:

##### 3.1 **Bundled CRIDGE deployment with the OpenSlice Helm chart (same cluster environment)**

#### **Bundled CRIDGE deployment with the OpenSlice Helm chart (same cluster environment)**

By default, the OpenSlice Helm chart also deploys CRIDGE alongside the bundle. To configure CRIDGE, there are three different ways to provide this kubeconfig file during deployment:

> **Note:** Regardless of the method you choose, if you're using a non-standard kubeconfig file name, make sure to adjust the references or rename the file as needed.

##### 3.2 **Standalone CRIDGE deployment**

#### **Standalone CRIDGE deployment**

There can be cases where a separate deployment of CRIDGE, apart from the bundled OpenSlice deployment, may be needed. These cases comprise:

    brokerUrl: "tcp://<openslice-rootURL>:61616?jms.watchTopicAdvisories=false"

```

##### Management of multiple Kubernetes Clusters

#### Management of multiple Kubernetes Clusters

OpenSlice also offers management support of *multiple Kubernetes Clusters* simultaneously. 

For this, you will have to replicate the steps in [Standalone CRIDGE deployment](#32-standalone-cridge-deployment) for every Cluster. Each CRIDGE instance will be in charged with the management of one Kubernetes Cluster.

#### 4. External Services Configuration

### External Services (optional)

For configuring optional external services like Bugzilla and CentralLog, specify their URLs and credentials in the `values.yaml` file:

Also in the 'Main Site Operations' product, a version named 'unspecified' must be created.

#### 5. Application and Logging Configuration

### Application and Logging

Application-specific configurations, such as OAuth client secrets, can be set in the `spring` section:

  oauthClientSecret: "secret"

```

#### 6. Ingress and Root URL

### Ingress and Root URL

To configure the ingress controller and root URL for OpenSlice, update the rooturl field with your ingress load balancer IP or domain. This setting is crucial for external access to your application:

rooturl: "http://3.15.198.35:8080" # Example IP with port

```

#### 7. Persistent Volume for MySQL

### Persistent Volume for MySQL

For persistent storage, especially for MySQL, define the storage size under the `mysql` section. This ensures that your database retains data across pod restarts and deployments.

  storage: "10Gi"

```

#### 8. Configuring TCP Forwarding for Artemis

### TCP Forwarding for Artemis

To expose the message bus service (Artemis) via the ingress controller, it’s essential to configure TCP traffic forwarding. Artemis listens on port `61616`, and this traffic needs to be directed to the Artemis service within your Kubernetes cluster.

This setup ensures that the message bus service is accessible externally via the ingress controller, completing the necessary configuration for Artemis.

### Configure Web UI

### Web UI

In folder `kubernetes/helm/openslice/files/org.etsi.osl.portal.web/src/js` you must make a copy of `config.js.default` file and rename it to `config.js`. 

Edit the `config.js` configuration file with your static configuration, if needed.

```

```js

{

  TITLE: "OpenSlice by ETSI",

  WIKI: "https://osl.etsi.org/documentation/",

### Configure TMF Web UI

### TMF Web UI

In the folder `kubernetes/helm/openslice/files/org.etsi.osl.tmf.web/src/assets/config` there are 3 files available for configuration:

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.

```

```json

{	      

    "TITLE": "OpenSlice by ETSI",

    "PORTALVERSION":"2024Q2",

kubectl logs <pod-name> -n openslice

```

## Post installation steps 

## Post installation steps (mandatory)

After the successful deployment of OpenSlice, to ensure the E2E user experience, **this section is mandatory**. It contains crucial configuration in regard of authentication and user creation.

After the successful deployment of OpenSlice, to ensure the end-to-end user experience, **this section is mandatory**. It contains crucial configuration in regard of authentication and user creation.

### Configure Keycloak server

  - navigation.path

  - search

  - search.highlight

  - content.code.copy

  palette:

    primary: 'cyan'

  icon:

    repo: fontawesome/brands/gitlab

markdown_extensions:

  - pymdownx.highlight:

      anchor_linenums: true

      line_spans: __span

      pygments_lang_class: true

  - pymdownx.inlinehilite

  - pymdownx.snippets

  - pymdownx.superfences    

# Copyright

copyright: "Copyright © 2024 ETSI OSL"