Changes between Version 11 and Version 12 of OperationsIssues
- Timestamp:
- 07/13/08 03:39:11 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OperationsIssues
v11 v12 8 8 ||Observing current network state ||1|| 9 9 ||Collecting network measurements ||1|| 10 ||Making network measurements available to users. Tools that access the archive need to evolve as formats, precision, and other details evolve. But access to historical data needs to be maintained as well.|| 2||10 ||Making network measurements available to users. Tools that access the archive need to evolve as formats, precision, and other details evolve. But access to historical data needs to be maintained as well.||1|| 11 11 ||Archiving network measurements||1|| 12 12 ||Defining and supporting appropriate privacy policies for collected data. Different users have different privacy concerns, and operations supports all users, so there can be many conflicts. Over time, the original experimenter may have moved on and other users come and go.||2|| 13 13 ||Keeping user access policies up to date, especially for mobile users||1|| 14 14 ||Resource trust and reputation management||1|| 15 ||Separating the "production" infrastructure from the "experimental" infrastructure. On a research network, how do you track when a status change is part of an experiment and decide whether it is something that needs operations action?|| 2||15 ||Separating the "production" infrastructure from the "experimental" infrastructure. On a research network, how do you track when a status change is part of an experiment and decide whether it is something that needs operations action?||1|| 16 16 ||Notifying users of planned outages in a way that makes sure they know about any changes that will affect them (not by just sending mass emails)||1|| 17 ||Reflecting underlying outages into experiments that want that vs isolating experiments that want reliability from them.|| 1||17 ||Reflecting underlying outages into experiments that want that vs isolating experiments that want reliability from them.||2|| 18 18 ||Defining and tracking demarcations between network infrastructure and user's infrastructure||1|| 19 19 ||Defining, monitoring, and delivering on service level agreements||1|| 20 20 ||Security monitoring and event management||1|| 21 ||Backwards compatibility for tools (for example, accessing network performance data associated with software releases or hardware devices that are no longer active in the network)|| 1||21 ||Backwards compatibility for tools (for example, accessing network performance data associated with software releases or hardware devices that are no longer active in the network)||2|| 22 22 ||Making multiple security mechanisms and authorization styles work together, particularly for federated networks||1|| 23 23 ||Communications with network administrators at user sites (in both directions). IT managers are very busy, and may not consider research network connections a high priority.||1||
