Project

General

Profile

Task #48

Need a process for exposing / working with prototypes for DataONE

Added by Dave Vieglais over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Support Operations
Target version:
Start date:
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

Issue came about when Giri requested a new URL for the ORNL pilot-catalog:

The current URL is http://mercury.ornl.gov/dataone/, can you please setup the domain name https://datanet.ecoinformatics.org/pilot-catalog to point http://mercury.ornl.gov/dataone/ ?

A couple of things here:

  1. perhaps setup a DN for "prototype.dataone.org"

  2. Have a web server running there that performs redirects to other targets based on the path.

So for Giri's example:

http://prototype.dataone.org/ornl-pilot-catalog/

might redirect to:

http://mercury.ornl.gov/dataone/

Bring this issue up at a VDC TWG discussion.

History

#1 Updated by Matthew Jones over 12 years ago

I changed the prototype config to be a proxy rather than redirect. The mercury instance now shows up for the DataONE site:

http://prototype.dataone.org/pilotcatalog/

One problem that still needs to be resolved is that it complains about the Google Maps API key being wrong -- we need a new key for the dataone url. Once a new key is installed then I think everything will be working at the new URL.

If this is an acceptable approach then I think we can close this task.

#2 Updated by Matthew Jones over 12 years ago

Initial support completed. prototype.dataone.org exists and is configured to proxy to other services. mule1 and mule2 VMs exist for other projects.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)