Project

General

Profile

Task #2883

Story #2720: KNB, LTER, PISCO, ESA, SANPARKS roll out

Task #2880: SANParks MN upgrade

Determine current SANParks replication setup

Added by Ben Leinfelder over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
2012-06-08
Due date:
% Done:

100%

Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:

Description

SANParks (dataknp.sanparks.org) will be the MN that registers with DataONE.
dataknp.sanparks.org currently replicates to KNB.
Other SANParks servers likely feed dataknp using Metacat replication.
We need to know exactly what the server topology is so that we know which servers need to be upgraded to 2.0.0 in order to keep the Metacat nodes replicating with one another.

History

#1 Updated by Jing Tao over 12 years ago

Here is the xml_replication table on the dataknp.sanparks.org:
metacat=> select * from xml_replication;
serverid | server | last_checked | replicate | datareplicate | hub
----------+------------------------------------------------+--------------+-----------+---------------+-----
1 | localhost | | 0 | 0 | 0
4 | datapha.saeon.ac.za/knb/servlet/replication | | 0 | 0 | 0
2 | knb.ecoinformatics.org/knb/servlet/replication | | 1 | 1 | 1
7 | saeonocean.co.za/knb/servlet/replication | 1980-01-01 | 1 | 1 | 0
8 | saeonmetacat.co.za/knb/servlet/replication | | 1 | 1 | 0
(5 rows)

We think will not maintain the replication between dataknp and datapha.saeon.ac.za.

Ben pointed out that saeonocean is now replaced by saeonmetacat. We needs update database to consolidate the two servers ( saeonocean and saeonmetacat).

So the replication servers we will maintain are:

  1. knb.ecoinformatics.org/knb/servlet/replication
  2. saeonmetacat.co.za/knb/servlet/replication

#2 Updated by Jing Tao over 12 years ago

Ben is trying to figure out who is in charge of the saeonmetacat.co.za server.

#3 Updated by Jing Tao over 12 years ago

  • Status changed from New to Closed

Disable the metacat replication between knb and sanparks. And consolidated the replication servers saeonocean.co.za and saeonmetacat.co.za.
So the only metacat replication server will be saeonmetacat.

#4 Updated by Ben Leinfelder over 12 years ago

  • Status changed from Closed to In Progress

UPDATE: we will keep the SANParks -> KNB replication channel open until D1 replication is fully functional and released.

Please make this change in the xml_replication table (the flags set back to "1") so that content in SANParks is replicated to KNB.

SInce both servers are now running Metacat 2.0.0 this should work. Special attention should be paid to the metacat.properties that specify the certificate locations:
replication.certificate.file=??
replication.privatekey.file=??
replication.privatekey.password=

#5 Updated by Jing Tao over 12 years ago

  • Status changed from In Progress to Closed

change the replicate, datareplicate and hub to be 1 in xml_replication table.
use dataone ca signed key/certificate pair to replace the old one.
import a new go_daddy certificate.

Now the replication should work between knb and dataknp.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)