VM Creation #9003
closed
Task #8566: "Rehearsal" of Production Jackrabbit Migration from Derby to PostgreSQL
Provisioning for workspace-repository-prod1.d4science.org and workspace-repository-prod.d4science.org
100%
Staging war link: http://maven.research-infrastructures.eu:8081/nexus/content/repositories/gcube-staging/org/gcube/data/access/home-library-webapp/1.8.0-4.6.0-149356/home-library-webapp-1.8.0-4.6.0-149356.war
/d4science.research-infrastructures.eu
/d4science.research-infrastructures.eu/FARM
/d4science.research-infrastructures.eu/SoBigData
/d4science.research-infrastructures.eu/SmartArea
/d4science.research-infrastructures.eu/gCubeApps
/d4science.research-infrastructures.eu/D4research
home-library-webapp-1.8.0
/home-library-webapp
/data
/tomcat-temp
Description
Both machines need the homelibrary webapp with smartgears. workspace-repository-prod1 needs a local postgres, whereas the other machine will use a remote postgres version. I am using the VM Creation ticket template although the machines have been already created (the original ticket is here #7877).
Please note that the machines run under the scope d4science.research-infrastructures.eu but to avoid problems with the current machine in production, no GcoreEndpoint must be published (i.e. mode='offline' must be written in the container.xml file) We will switch it later on.
They also need 80GB of disk storage to contain some of the content jackrabbit will create (indexes, configuration files), even if most of the content will be on postgres.
Updated by Costantino Perciante
Updated by Andrea Dell'Amico almost 8 years ago
A reminder: it's important that we switch to https as the only point of access, and close the 8080 from the outside.
Updated by Andrea Dell'Amico almost 8 years ago
- Status changed from New to In Progress
On workspace-repository-prod.d4science.org I see:
/dev/xvda3 40G 33M 40G 1% /home/gcube/tomcat/temp /dev/xvda4 100G 28G 73G 28% /data
And the ansible configuration implies that that directory can be on a different file system. The same is not true on workspace-repository-prod1.d4science.org.
I'm assuming that workspace-repository-prod.d4science.org has the correct configuration.
Updated by Andrea Dell'Amico almost 8 years ago
- Smartgears scopes updated (diff)
- External storage data disk updated (diff)
- Number of VMs changed from 1 to 2
authorizeChildrenContext: true
Updated by Andrea Dell'Amico almost 8 years ago
Provisioning is running on both servers.
Updated by Andrea Dell'Amico almost 8 years ago
- Status changed from In Progress to Feedback
The provisioning is complete.
workspace-repository-prod1.d4science.org still has a local postgresql instance, while both the VM can access the database that runs on workspace-repository-pg.d4science.org.
database name, user name and password are the same on both postgresql servers.
The service answers on http and https, there is no http -> https redirection right now.
Updated by Massimiliano Assante almost 8 years ago
- Status changed from Feedback to Closed
