Task #9668
closed
Produce ansible role for GeoNetwork 3.x
Added by Fabio Sinibaldi over 7 years ago.
Updated over 7 years ago.
Infrastructure:
Development, Production
Description
Configuration of GeoNetwork 3 is different from previous versions, so a different rule must be produced.
Following are the changes from previous versions' ansible rules.
- The war (latest version 3.2.2) can be downloaded from https://sourceforge.net/projects/geonetwork/files/GeoNetwork_opensource/v3.2.2/geonetwork.war/download
- Database can be configured by editing file WEB-INF/config-db/jdbc.properties
- The file WEB-INF/classes/setup/sql/data/data-db-default.sql initialize the database by inserting configuration settings that should be changed. In particular the following parameters:
HOST DETAILS, values should be provided by VM requester
3.1 "system/site/name"
3.2 "system/site/organization"
VM DETAILS, come from node settings
3.3 "system/server/host"
3.4 "system/server/protocol"
3.5 "system/server/port"
3.6 "system/server/securePort"
SDI support contact still needs to be identified
3.7 "system/feedback/email"
3.8 "system/feedback/mailServer/host"
3.9 "system/feedback/mailServer/username"
3.10 "system/feedback/mailServer/password"
3.11 "system/feedback/mailServer/ssl"
3.12 "system/feedback/mailServer/tls"
Related to VM resources and DB configuration, needs investigation on fine-tuning
3.13 "system/threadedindexing/maxthreads"
- Description updated (diff)
- Description updated (diff)
- Assignee changed from _InfraScience Systems Engineer to Andrea Dell'Amico
- Status changed from New to In Progress
- % Done changed from 0 to 70
At least config-node/srv.xml needs to be changed with the chosen DB engine.
All the three templates has been changed, there's a last piece that we can manage and it's the default admin user password. We do not have a way to enforce a change after the installation is complete, so we should initialize the service with a password different from the default one.
- Status changed from In Progress to Feedback
- % Done changed from 70 to 90
Two points, one of them fixed:
The sql file changed between the 3.2.1 version installed on dev and the 3.2.2 that was requested, the user table changed a column name from enabled to isenabled and its type is now character(1) and not bool. I fixed my template and now the initialization goes through
geoserver logs into catalina.out, a log4j.xml configuration must be setup so that it logs properly.
Andrea Dell'Amico wrote:
Two points, one of them fixed:
- The sql file changed between the 3.2.1 version installed on dev and the 3.2.2 that was requested, the user table changed a column name from
enabled to isenabled and its type is now character(1) and not bool. I fixed my template and now the initialization goes through
We now support the 3.2.1 version too. Just tested on geonetwork2-tunaatlas.d4science.org and the setup goes well.
- Status changed from Feedback to Closed
- % Done changed from 90 to 100
- Infrastructure Production added
And we now support the latest in the 3.0 series, 3.0.4.
Also available in: Atom
PDF
Updated by Fabio Sinibaldi 
Updated by 
