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 "PTP/designs/rm framework"
(New page: This page describes the new design for the PTP resource manager monitoring/control framework. The purpose of this framework is to: # Collect and display monitoring information relating t...) |
|||
| Line 16: | Line 16: | ||
* Predictive information about job execution | * Predictive information about job execution | ||
| − | + | Key attributes of the framework include: | |
| + | * Support for arbitrary system configurations | ||
| + | * The ability to scale to petascale system sizes and beyond | ||
| + | * Support for both use-installable and system-installable modes of operation | ||
| + | * Simple to add support for new resource managers | ||
Revision as of 13:25, 19 November 2010
This page describes the new design for the PTP resource manager monitoring/control framework.
The purpose of this framework is to:
- Collect and display monitoring information relating to the operation of a target system in a scalable manner
- Provide job submission, termination, and other job-related operations
- Support debugger launch and attach
- Enable the collection and display of stdin and transmission of stdout information from running jobs (where supported by the target system)
Monitoring information will comprise:
- The status and position of user's jobs in queues
- Job attribute information
- Target system status and health information for arbitrary configurations
- The physical/logical location of jobs on the target system
- Predictive information about job execution
Key attributes of the framework include:
- Support for arbitrary system configurations
- The ability to scale to petascale system sizes and beyond
- Support for both use-installable and system-installable modes of operation
- Simple to add support for new resource managers