Project

General

Profile

Feature #5576

Move OneMercury onto another virtual machine / servlet container

Added by Skye Roseboom over 7 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Skye Roseboom
Category:
-
Target version:
Start date:
2014-09-25
Due date:
2014-09-25
% Done:

0%

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

Description

To separate dependency between metacat, D1 rest, solr tomcat container from the OneMercury web app container.

Requires - new VM/hosts. Need to determine how many, where they will be. Need to have them configured per environment for testing.

Requires small network config agreement on how/when to forward from cn.dataone.org to the 'oneMercury' VM/servlet machine(s).

Requires discussion whether and how to support certificate management for authenticated users. Strategy for managing certificates across hosts/VMs that are not part of the portal hazelcast cluster.

Priority of this story? Is oneMercury coming to EOL? These strategies/solutions must also work for its replacement.

History

#1 Updated by Skye Roseboom over 7 years ago

  • Description updated (diff)

#2 Updated by Dave Vieglais about 7 years ago

  • Due date set to 2014-09-25
  • Target version set to Release Backlog
  • Start date set to 2014-09-25

#3 Updated by Dave Vieglais over 2 years ago

  • Status changed from New to Rejected

Closing with deprecation of ONEMercury

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)