Project

General

Profile

Actions

VM Creation #11771

closed

Please create a VM having access to prod authorization service

Added by Luca Frosini about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Start date:
May 14, 2018
Due date:
% Done:

100%

Infrastructure:
Production
RAM:
4
CPU:
2
DiskSpace:
15
Smartgears:
Yes
Smartgears Version:
latest
Application Instructions:

default smart executor installation with accounting-dashboard-harvester-se-plugin

Smartgears scopes:

/d4science.research-infrastructures.eu

Applications list and version:

latest smart-executor

Applications context path:
External storage data disk:
Smartgears auth connector:
data transfer enabled:
PostgreSQL database:
Number of VMs:
1

Related issues

Related to D4Science Infrastructure - VM Creation #11770: Please create a VM having access to dev authorization serviceRejected_InfraScience Systems EngineerMay 14, 2018

Actions
Actions #1

Updated by Luca Frosini about 7 years ago

  • Tracker changed from Support to VM Creation
  • RAM set to 2
  • CPU set to 2
  • DiskSpace set to 10
  • Smartgears set to Yes
  • Smartgears Version set to latest
  • Application Instructions updated (diff)
  • Smartgears scopes updated (diff)
  • Applications list and version updated (diff)
  • Number of VMs set to 1
Actions #2

Updated by Luca Frosini about 7 years ago

  • Blocked by VM Creation #11770: Please create a VM having access to dev authorization service added
Actions #3

Updated by Luca Frosini about 7 years ago

this VM is not required until the ticket #11770 is not closed. See such tickets for more details

Actions #4

Updated by Luca Frosini about 7 years ago

  • Blocked by deleted (VM Creation #11770: Please create a VM having access to dev authorization service)
Actions #6

Updated by Luca Frosini about 7 years ago

  • Related to VM Creation #11770: Please create a VM having access to dev authorization service added
Actions #9

Updated by Luca Frosini about 7 years ago

I set The VM creation blocked by the ticket tracking refactoring the smart-executor plugin #11756. You don't need to create it until the refactoring has been completed.
The name of the plugin will be 'accounting-dashboard-harvester-se-plugin' so the name of machine could be something like accounting-harverster.

Actions #10

Updated by Andrea Dell'Amico almost 7 years ago

  • RAM changed from 2 to 4
  • DiskSpace changed from 10 to 15
Actions #12

Updated by Luca Frosini almost 7 years ago

The plugin has been refactored to support scheduling but the DB read from the portlet has been changed and maybe it is not yet stable.
Actually, the plugin export to the old DB and another procedure made by @fabio.sinibaldi@isti.cnr.it migrate data.

I added the blocking task for this (see #11760).

Actions #13

Updated by Luca Frosini almost 7 years ago

The plugin refactor has been completed.
The plugin will be released with Release 4.13.0. Then we have to deploy it on a smart-executor node which requires this issues.

Actions #14

Updated by Luca Frosini almost 7 years ago

Please note the plugin will be released as uber-jar

Actions #15

Updated by Andrea Dell'Amico almost 7 years ago

Luca Frosini wrote:

Please note the plugin will be released as uber-jar

Does that means that the VM should be deployed after 4.13.0 has been released?

Actions #16

Updated by Luca Frosini almost 7 years ago

Andrea Dell'Amico wrote:

Does that means that the VM should be deployed after 4.13.0 has been released?

Yes

Actions #17

Updated by Andrea Dell'Amico over 6 years ago

Can we start the activity now?

Actions #18

Updated by Luca Frosini over 6 years ago

Yes, please

Actions #19

Updated by Andrea Dell'Amico over 6 years ago

  • Status changed from New to In Progress

Hostname and Ip address are going to be accounting-harvester.d4science.org 146.48.122.7.

Actions #20

Updated by Andrea Dell'Amico over 6 years ago

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

The service has been deployed. I see no errors in the tomcat logs, can you check if it's working?

Actions #21

Updated by Luca Frosini over 6 years ago

I checked the machine and the plugin is not working properly. I'm investigating the issue.
Apart from the issue, I just recognised that we need to add a task in the playbook.
I'll let you know all the details.

Actions #22

Updated by Andrea Dell'Amico over 6 years ago

Yes please.

Actions #23

Updated by Luca Frosini over 6 years ago

The error was related to duplicated and missing dependencies causing exceptions (the error was related to wrong scope declaration in pom). I should have fixed this.

Furthermore, we have to add a properties file (i.e. 'config.properties') in 'tomcat/webapps/smart-executor/WEB-INF/classes/'

I'm going to try to fix the playbook

Actions #24

Updated by Luca Frosini over 6 years ago

I fixed the playbook and tried to launch the playbook which stop after few steps.

./run.sh smartgears-node.yml -i inventory/hosts.production -l accounting_dashboard_harvester_se_plugin_prod
There are password protected encrypted files, we will ask for password before proceeding
Vault password: 
 [WARNING]: While constructing a mapping from /home/lucafrosini/workspace/ANSIBLE/ansible-playbooks/library/roles/smartgears/dm_pool_manager/tasks/main.yml, line 24, column 7, found a duplicate dict key
(file). Using last defined value only.

 [WARNING]: While constructing a mapping from /home/lucafrosini/workspace/ANSIBLE/ansible-playbooks/library/roles/smartgears/dm_pool_manager/tasks/main.yml, line 29, column 7, found a duplicate dict key
(file). Using last defined value only.

 [WARNING]: Could not match supplied host pattern, ignoring: smartgears_dev_nodes

 [WARNING]: Could not match supplied host pattern, ignoring: smartgears_preprod_nodes

 [WARNING]: Could not match supplied host pattern, ignoring: egi_dataminer

 [WARNING]: Could not match supplied host pattern, ignoring: egi_smartexecutor


PLAY [smartgears_nodes:smartgears_dev_nodes:smartgears_preprod_nodes:egi_dataminer:egi_smartexecutor] ********************************************************************************************************
skipping: no hosts matched

PLAY RECAP ***************************************************************************************************************************************************************************************************
Actions #25

Updated by Andrea Dell'Amico over 6 years ago

The correct playbook for the smart excutors is smartexecutor-services.yml. They were split some months ago, because there was too much bloat into smartgears-node.yml.

Actions #26

Updated by Luca Frosini over 6 years ago

The playbook fail for me because I have no root access on "monitoring.research-infrastructures.eu".
It fails when the playbook tries to disable nagios alert.

Actions #27

Updated by Andrea Dell'Amico over 6 years ago

Nope, the cause must be different. The nagios-related tasks have a ignore_errors: True entry.

Actions #28

Updated by Luca Frosini over 6 years ago

I was using an incomplete command. The right one is:

./run.sh smartexecutor-services.yml -i inventory/hosts.production -l accounting_dashboard_harvester_se_plugin_prod -t smartgears
Actions #29

Updated by Luca Frosini over 6 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)