Project

General

Profile

Actions

Task #1846

closed

Support #1837: Add SmartGenericWorkers to the VREs

Provide an ansible playbook for publishing the smart-executor services at VRE level

Added by Roberto Cirillo over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Category:
Other
Target version:
Start date:
Dec 17, 2015
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Production

Description

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:
         <application mode="online" context="/smart-executor">
                <scope>/d4science.research-infrastructures.eu/gCubeApps</scope>
                <scope>/d4science.research-infrastructures.eu/gCubeApps/BiodiversityLab</scope>
                <scope>/d4science.research-infrastructures.eu/gCubeApps/BiOnym</scope>
                <scope>/d4science.research-infrastructures.eu/gCubeApps/ScalableDataMining</scope>
        </application>
  • add the gCubeApps.gcubekey to the tomcat/lib folder
  • clean the state
  • restart the container

In attachment an example of container.xml.


Files

container.xml (1.32 KB) container.xml Roberto Cirillo, Dec 17, 2015 04:55 PM

Related issues

Blocked by D4Science Infrastructure - Task #1501: Reinstall the 'old' smartexecutors from the provisioningClosed_InfraScience Systems EngineerNov 23, 2015

Actions
Actions #1

Updated by Roberto Cirillo over 9 years ago

  • Tracker changed from Support to Task
Actions #2

Updated by Andrea Dell'Amico over 9 years ago

  • Status changed from New to In Progress
  • Assignee changed from _InfraScience Systems Engineer to Andrea Dell'Amico

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.

Actions #3

Updated by Andrea Dell'Amico over 9 years ago

  • Blocked by Task #1501: Reinstall the 'old' smartexecutors from the provisioning added
Actions #4

Updated by Andrea Dell'Amico over 9 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

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
Actions #5

Updated by Andrea Dell'Amico over 9 years ago

I'm starting the upgrade of the node[43:78].d4science.org hosts.

Actions #6

Updated by Andrea Dell'Amico over 9 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)