Project

General

Profile

Story #1827

Design AccessPolicy update restrictions

Added by Robert Waltz about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_cn_service
Target version:
Sprint-2011.45-Block.6
Start date:
2011-10-07
Due date:
% Done:

100%

Story Points:
Sprint:

Description

AccessPolicy as it is currently designed allows for conflicting updates to be made on CNs and MNs. We need to redesign in order to assure AccessPolicy consistency will result in updates to SystemMetadata.

Related issues

Related to Infrastructure - Story #1966: CNs should keep all replica MNs up to date with SystemMetadata changes Closed 2011-11-01 2011-11-19

History

#1 Updated by Robert Waltz about 13 years ago

  • Position set to 1
  • Position changed from 1 to 288

#2 Updated by Robert Waltz about 13 years ago

  • Target version changed from Sprint-2011.42-Block.6 to Sprint-2011.43-Block.6

#3 Updated by Robert Waltz about 13 years ago

  • Target version changed from Sprint-2011.43-Block.6 to Sprint-2011.42-Block.6

#4 Updated by Dave Vieglais about 13 years ago

  • Position deleted (290)
  • Position set to 1
  • Target version changed from Sprint-2011.42-Block.6 to Sprint-2011.44-Block.6

#5 Updated by Dave Vieglais about 13 years ago

  • Target version changed from Sprint-2011.44-Block.6 to Sprint-2011.45-Block.6
  • Position deleted (22)
  • Position set to 2

#6 Updated by Robert Waltz about 13 years ago

  • Status changed from New to Closed

CNs will be the sole manager of AccessPolicies after initial creation.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)