Actions
VM Creation #10790
closed
Catalogue-ws: please create a VM for it in preprod
Start date:
Dec 22, 2017
Due date:
% Done:
100%
Infrastructure:
Pre-Production
RAM:
3
CPU:
2
DiskSpace:
10
Smartgears:
Yes
Smartgears Version:
latest
Application Instructions:
Smartgears scopes:
/gcube/preprod
/gcube/preprod/preVRE
/gcube/preprod/preECO
/gcube/preprod/Dorne
Applications list and version:
catalogue-ws 1-1-0
Applications context path:
/catalogue-ws
External storage data disk:
Smartgears auth connector:
data transfer enabled:
No
PostgreSQL database:
No
Number of VMs:
1
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from New to In Progress
- RAM changed from 2 to 3
Updated by Andrea Dell'Amico over 7 years ago
hostname and IP address are going to be: catalogue-ws-t.pre.d4science.org 146.48.122.76
Updated by Andrea Dell'Amico over 7 years ago
I see that the dev catalogue-ws is also used for the preproduction environment. Shouldn't it removed from it?
Updated by Costantino Perciante over 7 years ago
Andrea Dell'Amico wrote:
I see that the dev catalogue-ws is also used for the preproduction environment. Shouldn't it removed from it?
Sure, let's keep catalogue-ws-d-d4s working under the following contexts:
- /gcube
- /gcube/devsec (and children)
- /gcube/devNext (and children)
Updated by Andrea Dell'Amico over 7 years ago
Provisioning is running on the new VM.
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
- Smartgears scopes updated (diff)
The VM is running
Updated by Costantino Perciante over 7 years ago
- % Done changed from 100 to 0
Should I change the scopes of the dev machine or can it be done via ansible?
Updated by Costantino Perciante over 7 years ago
- Status changed from Feedback to Closed
Actions
