Project

General

Profile

Actions

VM Creation #8197

closed

Provide a new SmartGears node equipped with the SmartExecutor

Added by Costantino Perciante over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
_InfraScience Systems Engineer
Target version:
Start date:
Apr 20, 2017
Due date:
Apr 21, 2017
% Done:

100%

Infrastructure:
Development
RAM:
2
CPU:
1
DiskSpace:
4
Smartgears:
Yes
Smartgears Version:
Application Instructions:

resource-checker-se-plugin as smart-executor plugin needs to run on the machine

Smartgears scopes:

/gcube

Applications list and version:

smart-executor-1-5-0
resource-checker-se-plugin-1.0.0

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

Description

The resource-checker-se-plugin will run on it (available on subversion at trunk/information-system/resource-checker-se-plugin)

This plugin will write a file at /home/gcube/missing_resources/identifiers, if it is the case, that needs to be read by nagios and used as input for the script reported here #8103

Actions #1

Updated by Costantino Perciante over 8 years ago

  • Application Instructions updated (diff)
  • Applications list and version updated (diff)
Actions #2

Updated by Costantino Perciante over 8 years ago

  • Due date set to Apr 21, 2017
  • Applications list and version updated (diff)
Actions #3

Updated by Costantino Perciante over 8 years ago

  • Description updated (diff)
Actions #4

Updated by Costantino Perciante over 8 years ago

  • Applications list and version updated (diff)
Actions #5

Updated by Andrea Dell'Amico over 8 years ago

  • Status changed from New to In Progress

Can you provide the maven information to access the resource-checker-se plugin?

Actions #6

Updated by Andrea Dell'Amico over 8 years ago

resource-checker-d4s.d4science.org 146.48.123.109

Actions #7

Updated by Andrea Dell'Amico over 8 years ago

Andrea Dell'Amico wrote:
So it's a dev VM. I'm going to change the hostname. The one above will be used for the production VM.

Actions #8

Updated by Andrea Dell'Amico over 8 years ago

  • Project changed from 2 to D4Science Infrastructure
  • Target version changed from gCube Release 4.4.0 to UnSprintable
  • Infrastructure Development added
Actions #9

Updated by Andrea Dell'Amico over 8 years ago

resource-checker-d-d4s.d4science.org 146.48.123.110

Actions #10

Updated by Andrea Dell'Amico over 8 years ago

The VM has been configured. The only missing part are the smart executor plugin and the script that reinstates the missing resources.

Actions #12

Updated by Andrea Dell'Amico over 8 years ago

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

The plugin has been installed with ansible, so the playbook is complete.
But there are scopes problems, I see from the logs:

ERROR SmartExecutorInitializator: Unable to Create ServiceEndpoint for scope /gcube. The Service will be aborted
java.lang.RuntimeException: could not configure discovery service
Actions #14

Updated by Costantino Perciante over 8 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)