Project

General

Profile

Task #4156

MNDeployment #3221: EDAC member node

confirm nodeID is right level of specificity

Added by Rob Nahf over 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2013-11-05
Due date:
% Done:

100%

Story Points:
Sprint:

Description

In stage, the NodeReference is "urn:node:EDACGSTORE".
In the interest of keeping transient details out of node ids, is the GSTORE necessary? would "urn:node:EDAC" be sufficient?


Related issues

Blocks Member Nodes - Task #4161: issue and install production certificates Closed 2014-02-04

History

#1 Updated by Rob Nahf over 10 years ago

  • Target version changed from 315 to Deploy by end of Y5Q2

#2 Updated by Rob Nahf over 10 years ago

  • % Done changed from 0 to 100
  • translation missing: en.field_remaining_hours set to 0.0
  • Status changed from New to Closed

gstore is a custom product that is representative of the collection, so having both EDAC and GSTORE in the node id is appropriate.

#3 Updated by Laura Moyers about 10 years ago

  • Target version changed from Deploy by end of Y5Q2 to Deploy by end of Y5Q3

#4 Updated by Laura Moyers almost 10 years ago

  • Target version changed from Deploy by end of Y5Q3 to Deploy by end of Y5Q4

#5 Updated by Laura Moyers almost 10 years ago

  • Target version changed from Deploy by end of Y5Q4 to Operational

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)