Project

General

Profile

Actions

Task #12678

closed

Ansible-dataminer: manage parallel computation as parameter in web.xml

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

Status:
Closed
Priority:
Normal
Category:
Application
Start date:
Oct 12, 2018
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Pre-Production, Production

Description

It's needed to create an ansible task for adding the parallel computation parameter in the web.xml as reported here: #12675.
It should be set to:

  • 1 for each dataminer-gw
  • 4 for each production and proto instance
Actions #2

Updated by Roberto Cirillo over 6 years ago

  • Status changed from New to In Progress
Actions #4

Updated by Andrea Dell'Amico over 6 years ago

  • Parent task set to #12675
Actions #5

Updated by Roberto Cirillo over 6 years ago

  • Status changed from In Progress to Paused
  • % Done changed from 0 to 80

New variable managed. I need to test it in preproduction environment when the new dataminer version (1.5.5) is available in gCube-Staging repo.

Actions #6

Updated by Roberto Cirillo over 6 years ago

  • Status changed from Paused to In Progress
Actions #7

Updated by Roberto Cirillo over 6 years ago

The playbook take very long time: about one hour for update a single instance.
Most of the time used for installing additional packages as knime, etc.
@andrea.dellamico@isti.cnr.it do you think in production the running will be more fast?

Actions #8

Updated by Roberto Cirillo over 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100

The new dataminer app has been installed successfully: The new web.xml is properly managed.
I've explicitly set the new wps version (1.1.2-4.13.0-173396) in the playbook otherwise the playbook doesn't install the latest webapp version. We should find a way ( if it there isn't yet) to force a webapp upgrade.

Actions #9

Updated by Andrea Dell'Amico over 6 years ago

Roberto Cirillo wrote:

The new dataminer app has been installed successfully: The new web.xml is properly managed.
I've explicitly set the new wps version (1.1.2-4.13.0-173396) in the playbook otherwise the playbook doesn't install the latest webapp version. We should find a way ( if it there isn't yet) to force a webapp upgrade.

As we use maven, the webapp is upgraded every time a new version is found on maven. Why latest didn't work? That could be a problem.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)