D4Science Infrastructure

During the last six months I worked on several ansible roles to automate the deployment of our gcube-based testing infrastructure.

As of now, our infrastructure is being redeployed every night, and we're integrating this process with ETICS, so that ETICS will actively redeploy everything that needs to be refreshed after a build run, while exposing the results report.

In the meantime I've pushed those roles into CNR's gitorious ansible repository and I'm cooperating with Andrea Dell'Amico to port those roles over to CNR's infrastructure and improve them together.

This ticket will be used to keep track of the rest of the activity.

A tentative action list is:

• integrate those roles into CNR's infratructure
• render those roles capable of upgrading existing instances instead of deploying everything from scratch
• finish the ETICS integration so that every BUILD instance triggers a redeployment of the infrastructure
• possibly render those roles capable to be used both for testing (less complex deployment scale, no clusters, etc.) and for production

This is a non-comprehensive list of the roles that I devised to deploy the GHN based enabling services:

• roles/gcore-base/
• roles/gcore-collector/
• roles/gcore-notifier/
• roles/gcore-portal/
• roles/gcore-registry/
• roles/gcore-resourcebroker/
• roles/gcore-resourcemanager/
• roles/gcore-softwaregateway/