D4Science Infrastructure

Roberto Cirillo wrote:

The ansible playbook should perform the following steps for every smart-executor deployed in production:

• stop the container
• add the following tags in the container.xml:

The container.xml file is a template already, so it's a matter of changing and redistributing it (on the 'new' smartexecutor VMs)

• add the gCubeApps.gcubekey to the tomcat/lib folder

This is already installed.

• clean the state
• restart the container

These steps are part of the (re)configuration process already (for the 'new' smartgears, as always).

In attachment an example of container.xml.

I'd like to associate this reconfiguration to the reinstallation of the 'old' smartgears so that we can manage all of them in the same way.

I've updated the playbook. It now installs a container.xml with the proposed entries when:

• The smartgears node is a smart executor
• It's a production node