Story #1026
cn/resolve behavior across different environments
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
d1_cn_service
Target version:
-
Start date:
Due date:
% Done:
100%
Estimated time:
10.00 h
Story Points:
Sprint:
Description
While systemMetadata knows where copies of its object are located, it does not know the context (environment) of those locations. That information is in the nodelist. So, clarity is needed for cn/resolve on how to handle situations where the systemMetadata contains replica nodes other than its operating environment. (If in production, should cn/resolve return locations pointing to test MNs? If in test environment, should cn/resolve return locations pointing to production MNs? Are there cases (data migration?), where we want cn/resolve to be able to resolve across environments?
If cn/resolve encounters out-of-bounds situations, should that information be logged?
History
#1 Updated by Skye Roseboom over 9 years ago
- Status changed from New to Closed
- Start date deleted (
2010-10-26) - translation missing: en.field_remaining_hours set to 0.0
- Milestone set to None