Develop

Merge request reports

Loading
+3 −0
Changes for doc/getting_started/deployment/docker_compose.md: 3 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -457,11 +457,14 @@ Finally, enter the details of the mail server at the Email Tab.
This step is mandatory so as to access the OpenSlice Web UI. To add an OpenSlice admin user you must:

- Navigate to realm Openslice > Users > Add user
- Set ```admin``` username
- Set a password
- 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 Role ADMIN guarantee full access through the OpenSlice UI, thus such a user is always required.

> You may have multiple ADMIN role users, but you must have at least one with ```admin``` username.

### Keycloak at localhost

> **This is an important step if you run Keycloak on localhost!**
+23 −1
Changes for doc/getting_started/deployment/kubernetes.md: 23 added lines, 1 removed line.
Original line number Diff line number Diff line
@@ -31,7 +31,25 @@
      
        * 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.
    * **GKE Ingress Controller:** 
        * Modify `[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml`, as following:

            ``` 
            - - pathType: ImplementationSpecific
            + - pathType: Prefix
            ```
        
        * Modify `[repo-root]/kubernetes/helm/openslice/values.yaml`, as following:

            ``` 
            - -  ingressClassName: nginx
            - -  annotations: {}
            + -  annotations:
            +      kubernetes.io/ingress.class: gce
            +      kubernetes.io/ingress.global-static-ip-name: web-static-ip 
            ```

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

### Exposure

@@ -516,12 +534,16 @@ Finally, enter the details of the mail server at the Email Tab.
#### 2. 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 realm Openslice > Users > Add user
- Set ```admin``` username
- Set a password
- 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 Role ADMIN guarantee full access through the OpenSlice UI, thus such a user is always required.

> You may have multiple ADMIN role users, but you must have at least one with ```admin``` username.

### NFV Orchestrator Configuration

After successfully deploying and configuring OpenSlice, you may configure its environment (e.g. the NFVO) that will facilitate the deployment of NFV artifacts.
+1 −1
Changes for mkdocs.yml: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -167,7 +167,7 @@ nav:
      - Jenkins Helm Installation aaS : ./service_design/examples/jenkins_helm_install_aas/jenkins_helm_install_aas.md
      - Monitoring aaS: ./service_design/examples/monitoring_aas/monitoring_aas.md
  - Service Ordering:
    - Ordering Services from catalogs: ./service_ordering/ordering_services.md
    - Ordering Services from Catalogs: ./service_ordering/ordering_services.md
  # - Testing services:
  #   - Testing Specification: ./testing_services/test_spec.md
  #   - Testing Catalogs: ./testing_services/test_catalogs.md
Loading