Actions
VM Creation #8779
closed
Create new VM for ResourceManager on D4Research
Start date:
May 29, 2017
Due date:
% Done:
100%
Infrastructure:
Production
RAM:
4
CPU:
2
DiskSpace:
10
Smartgears:
No
Smartgears Version:
Application Instructions:
Smartgears scopes:
Applications list and version:
Applications context path:
External storage data disk:
Smartgears auth connector:
data transfer enabled:
No
PostgreSQL database:
No
Number of VMs:
Description
In order to avoid heap space problem it's needed to transfer the ResourceManager gCore service from "node66.p.d4science" to a new VM called:
resourcemanager-d4research.d4science.org
Related issues
Updated by Tommaso Piccioli almost 8 years ago
- Status changed from New to In Progress
- Assignee changed from _InfraScience Systems Engineer to Roberto Aquilano
- % Done changed from 0 to 50
resourcemanager-d4research.d4science.org is running.
Updated by Tommaso Piccioli almost 8 years ago
- Assignee changed from Roberto Aquilano to Roberto Cirillo
Updated by Roberto Cirillo almost 8 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
The ResourceManager service is running now on the new node.
I've stopped the old resource-manager instance running on gcube1@node66.p.d4science.research-infrastructures.eu
Updated by Roberto Cirillo almost 8 years ago
- Related to Task #8979: Nagios: switch check from collector-d4research:8000 to resourcemanager-d4research.d4science.org added
Actions
