search

EOSC-synergy / SQAaaS

6 stars 1 forks source link

SQAaaS platform deployment using Infrastructure Manager (and eventually k8s) #10

Open orviz opened 3 years ago

micafer commented 3 years ago

On the README it is said that you install the ingress controller after the deployment of the Kubernetes cluster. The IM-Dashboard Kubernetes recipe already has an option to install it on the initial contextualzation step and it is set to "true" by default, so you should not need to do this extra step of installing the ingress controller.

micafer commented 3 years ago

Regarding the volumes: The IM-Dashboard Kubernetes recipe also installs the NFS-Client-provisioner. It enables to create only the PVC and it internally manages the PV creation, making easier the deployment of the application.

micafer commented 3 years ago

I can create a new TOSCA template and include it in the IM-Dasboard to automatically deploy the SQAaaS. It can be easy and will give "visibilty" to de platform.

micafer commented 3 years ago

First version of the TOSCA document: https://github.com/grycap/im-dashboard/blob/master/tosca-templates/sqaaas.yaml

orviz commented 3 years ago

We should test the TOSCA deployment with appropriate tokens

micafer commented 3 years ago

TOSCA and recipes updated to include Web UI. The tosca has been also added to the IM dashboard and can be tested.

orviz commented 3 years ago

Joint effort for deploying Jenkins Operator (LIP & IFCA)

Sgb597 commented 3 years ago

As of now the Jenkins Operator on K8s has only successfully been deployed on minikube. The following plugins have been successfully configured via CasC: matrix-auth, github-oauth, and configuration-as-code. The one plugin that has not been successfully configured via CasC is the github plugin.