Project

General

Profile

Actions

Task #4815

closed

Enable dev2.d4science to reach postgreSQL instance on preprod1.d4science and viceversa

Added by Massimiliano Assante almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Category:
-
Target version:
Start date:
Jul 27, 2016
Due date:
Aug 26, 2016
% Done:

100%

Estimated time:
2.00 h
Infrastructure:
Development, Pre-Production

Description

In production we had (minor) issues related to the fact that the Liferay DB is no longer on the same portal node. For this reason we would like to replicate the same in dev and preprod.

The easier way to do so is to Enable dev2.d4science to reach postgreSQL instance on preprod1.d4science and viceversa. I will then take care of dumping and restoring the DB in the 2 nodes.

Actions #1

Updated by Massimiliano Assante almost 9 years ago

  • Target version changed from gCube related support to UnSprintable
Actions #2

Updated by Andrea Dell'Amico almost 9 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Andrea Dell'Amico almost 9 years ago

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

On preprod1.d4science.org you now have a db named infra_dev_db accessible by the infra_dev user from dev2.d4science.org

On dev2.d4science.org you have a db named infra_pre_db accessible by the infra_pre user from preprod[1:2].d4science.org

Same password of the other ones.
All the DB are accessible by your desktop IP.

A plea: if you need to drop/create a database, please create it as owned by the user that will access it, and UTF8 encoded.

Actions #4

Updated by Andrea Dell'Amico almost 9 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)