Project

General

Profile

Actions

Task #7426

closed

Add a general purpose postgresql server to collect the dev and preprod databases

Added by Andrea Dell'Amico about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Category:
System Application
Target version:
Start date:
Mar 07, 2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Infrastructure:
Development, Pre-Production

Description

With the postgis extensions installed.


Subtasks 1 (0 open1 closed)

Task #7434: Activate backups for the postgresql dev serviceClosed_InfraScience Systems EngineerMar 07, 2017

Actions

Related issues

Related to D4Science Infrastructure - Incident #7647: Cannot edit Service endpoint on /gcubeClosedRoberto CirilloMar 22, 2017Mar 23, 2017

Actions
Related to D4Science Infrastructure - Task #7708: Please move Databases of dev2.d4science.org and preprod1.d4science.org to postgresql-srv-dev.d4science.orgClosed_InfraScience Systems EngineerMar 23, 2017

Actions
Actions #3

Updated by Andrea Dell'Amico about 8 years ago

  • Status changed from New to In Progress

hostname and IP address: postgresql-srv-dev.d4science.org 146.48.123.24

Actions #4

Updated by Andrea Dell'Amico about 8 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

The VM is ready. We should migrate there all the postgres 9.x db instances used in dev and preproduction but the portal ones (and maybe them too):

geonetwork and geoservers when they are able to work against postgresql 9.6+
SimulFishGrowth_pre
SimulFishGrowth_prod
survey-db-1
survey-db-2
survey-db-3
surveyTestCreation
quota_dev_db
Others that I don't know about?

The database creation will be ansible provisioned until the service of #7429 will be ready.

Actions #5

Updated by Massimiliano Assante about 8 years ago

Let's do this, dev.d4science.org:5432/gcube-releases should be migrated too.

How should we proceed? We need one performing actions on the DB side and on Infrastructure Side to update the resources pointing to the db(s)

Actions #6

Updated by Andrea Dell'Amico about 8 years ago

Massimiliano Assante wrote:

Let's do this, dev.d4science.org:5432/gcube-releases should be migrated too.

This is a production one despite it running on dev.d4science.org, correct?

How should we proceed? We need one performing actions on the DB side and on Infrastructure Side to update the resources pointing to the db(s)

We first need to collect the database name, the username that needs to access the database (some of them are accessed as postgres but we need an unprivileged user; better if we have a different user for every database), and the passwords.
DB names and users are easy to collect, the passwords are not.

Then we need to perform a dump and a restore, and the applications data sources need to be modified.

Actions #7

Updated by Andrea Dell'Amico about 8 years ago

gcube-releases-dev has been imported on postgresql-srv-dev.d4science.org

unfortunately I could not test this because of Incident #7647: Cannot edit Service endpoint on /gcube

Actions #8

Updated by Massimiliano Assante about 8 years ago

  • Related to Incident #7647: Cannot edit Service endpoint on /gcube added
Actions #9

Updated by Massimiliano Assante about 8 years ago

  • Related to Task #7708: Please move Databases of dev2.d4science.org and preprod1.d4science.org to postgresql-srv-dev.d4science.org added
Actions #10

Updated by Andrea Dell'Amico about 8 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)