Actions
VM Creation #8551
closed
Please Create a VM to install Resource Registry for PARTHENOS
Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Target version:
Start date:
May 12, 2017
Due date:
% Done:
100%
Infrastructure:
Production
RAM:
2
CPU:
2
DiskSpace:
10
Smartgears:
Yes
Smartgears Version:
latest
Application Instructions:
latest
Smartgears scopes:
/d4science.research-infrastructures.eu/Parthenos
/d4science.research-infrastructures.eu/Parthenos/PARTHENOS_Registry
Applications list and version:
As already defined in ansible task the instance must be provided with resource-registry-orientdb-hooks
Applications context path:
as already declared in ansible script
External storage data disk:
Smartgears auth connector:
data transfer enabled:
No
PostgreSQL database:
No
Number of VMs:
1
Related issues
Updated by Luca Frosini almost 8 years ago
- Related to VM Creation #8552: Please Create a VM to install an OrientDB instance for PARTHENOS added
Updated by Luca Frosini almost 8 years ago
- Applications list and version updated (diff)
Updated by Luca Frosini almost 8 years ago
- RAM changed from 2 to 8
- CPU changed from 2 to 4
Updated by Luca Frosini almost 8 years ago
- RAM changed from 8 to 2
- CPU changed from 4 to 2
Updated by Luca Frosini almost 8 years ago
- Related to deleted (VM Creation #8552: Please Create a VM to install an OrientDB instance for PARTHENOS)
Updated by Luca Frosini almost 8 years ago
- Blocked by VM Creation #8552: Please Create a VM to install an OrientDB instance for PARTHENOS added
Updated by Tommaso Piccioli almost 8 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 30
registry-parthenos.d4science.org is up, to be provisioned.
Updated by Andrea Dell'Amico almost 8 years ago
- Status changed from In Progress to Feedback
- % Done changed from 30 to 100
Resource registry installed. But it seems that /d4science.research-infrastructures.eu/Parthenos
does not exist.
Updated by Luca Frosini almost 8 years ago
- Status changed from Feedback to In Progress
You are right infact correctly Ticket #8511 blocks this ticket which is blocked by #8591.
Updated by Luca Frosini almost 8 years ago
- Status changed from In Progress to Paused
I can successfully login via ssh.
Updated by Andrea Dell'Amico over 7 years ago
- Number of VMs set to 1
There are no more blockers for this one. Can we complete this task yet?
Actions