Story #2944: Design and implement a MN kill switch mechanism - Infrastructure - DataONE Tasks

Story #2944

Design and implement a MN kill switch mechanism

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

Status:

New

Priority:

Normal

Assignee:

Dave Vieglais

Category:

Support Operations

Target version:

Start date:

Due date:

% Done:

Story Points:

Sprint:

Infrastructure backlog

Description

We need a mechanism to quickly and effectively de-register a MN and it's content in case there is some issue with the MN that warrants such action (e.g. malware is found on the server or some other inappropriate or malicious activity).

Subtasks

History

#1 Updated by Dave Vieglais almost 12 years ago

Target version changed from Sprint-2012.25-Block.4.1 to Sprint-2012.33-Block.5.1
Milestone changed from CCI-1.0.2 to CCI-1.1

#2 Updated by Chris Jones over 11 years ago

Target version changed from Sprint-2012.33-Block.5.1 to Sprint-2012.41-Block.6.1
Position set to 1

#3 Updated by Chris Jones over 11 years ago

Target version changed from Sprint-2012.41-Block.6.1 to Sprint-2012.39-Block.5.4
Position changed from 1 to 488
Position set to 1
Position deleted (2)

#4 Updated by Dave Vieglais over 11 years ago

translation missing: en.field_remaining_hours set to 0.0
Due date set to 2012-10-06
Milestone changed from CCI-1.1 to CCI-1.1.1

As the number of member nodes increases, so does the likelihood for something unpleasant to happen. Need to at least document the manual process for this.