VM Creation #13112
closed
perform-service development instance
100%
/gcube
/gcube/preprod
/gcube/preprod/preVRE
perform-service
Description
A new VM is needed in order to test the new service 'perform-service'.
Such service needs to connect to the VRE's perform-fish-db as manager (see ticket #13111 for database details).
Related issues
Updated by Fabio Sinibaldi almost 7 years ago
- Smartgears scopes updated (diff)
- Infrastructure Pre-Production added
- Infrastructure deleted (
Development)
Updated by Tommaso Piccioli almost 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 40
new VM perform.dev.d4science.org ready to be provisioned
Updated by Andrea Dell'Amico almost 7 years ago
@fabio.sinibaldi@isti.cnr.it do you already have the maven coordinates to the perform-service artifact?
Updated by Fabio Sinibaldi almost 7 years ago
Yes, Maven coordinates are :
org.gcube.application
perform-service
We are going to need this service in production by the end of the month, so probably we will need to deploy the artifact from SNAPSHOT repository.
I'm creating a similar ticket for the production VM.
Updated by Fabio Sinibaldi almost 7 years ago
- Copied to VM Creation #13149: perform-service production instance added
Updated by Andrea Dell'Amico almost 7 years ago
- % Done changed from 40 to 90
provisioning is ongoing, but I expect an error identical to the one present in production. See #13149#note-5
Updated by Fabio Sinibaldi almost 7 years ago
Most probably yes. Service's development / testing is still ongoing, so I'm going to run provision frequently in order to perform integration tests / bugfix.
Updated by Andrea Dell'Amico almost 7 years ago
Confirm, same error. You have access to both the servers so you can reinstall when ready.
Updated by Andrea Dell'Amico almost 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
