Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Aperi Use Cases"
| Line 10: | Line 10: | ||
== Discovery Management == | == Discovery Management == | ||
| − | + | === '''Identify the storage network,''' ''and applications'' === | |
| − | + | * '''''Support filtering for discovery''''' | |
| − | + | * ''Support physical location of the resource'' | |
| − | + | * ''Resource ownership/management information'' | |
| − | + | * '''Multi-driven discovery cycle periodicities''' | |
| − | + | * '''User-driven “timeout” specifications for resources''' | |
| + | |||
| + | === Display the topology (elements/connections) === | ||
| + | * '''''Supply different views''''' | ||
| + | * '''''Topology drill-down''''' | ||
| + | * '''''Visually display events for critical situations''''' | ||
Revision as of 20:04, 9 March 2007
Contents
Introduction
Authors: John Tyrrell and Ted Slupesky
This is a living document intended to capture use cases that apply to the Aperi project. The document lists the applicable use cases, arranged according to the traditional disciplines of storage resource management. Each use case is marked up with an indication of the degree we believe Aperi satisfies the use case, as follows:
- bold text means Aperi currently satisfies the use case,
- bold italic text means Aperi currently partially satisfies the use case
- italic text indicates that Aperi does not currently satisfy the use case.
Discovery Management
Identify the storage network, and applications
- Support filtering for discovery
- Support physical location of the resource
- Resource ownership/management information
- Multi-driven discovery cycle periodicities
- User-driven “timeout” specifications for resources
Display the topology (elements/connections)
- Supply different views
- Topology drill-down
- Visually display events for critical situations