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 
Updated by 
