Task #7426: Add a general purpose postgresql server to collect the dev and preprod databases - D4Science Infrastructure - D4science

Custom queries

03. VRE Plan
04. All Projects Deliverables
04. All Projects Milestones
06. D4Science Projects Activities
All open Issues
D4Science Infrastructure Upgrade
My InProgress Tasks
My Paused Tasks
My Watched Tasks
Not Closed Assigned To Me
Not Closed Assigned To Me (No Releases, No Project Tasks)
Not Closed Opened by Me
Open Issues
Upgrade Plan
Upgrade Plan Clear

Actions

Copy link

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:

PostgreSQL cluster

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 open — 1 closed)

Task #7434: Activate backups for the postgresql dev service

Closed

_InfraScience Systems Engineer

Mar 07, 2017

Actions

Related issues

Related to D4Science Infrastructure - Incident #7647: Cannot edit Service endpoint on /gcube

Closed

Roberto Cirillo

Mar 22, 2017

Mar 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.org

Closed

_InfraScience Systems Engineer

Mar 23, 2017

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

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

Copy link

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

Copy link

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

Copy link

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

Copy link