Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PTP/designs/2.x"

< PTP‎ | designs
m (Runtime Platform)
(Tool Integration Services)
 
(189 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
The Parallel Tools Platform (PTP) is a portable, scalable, standards-based integrated development environment specifically suited for application development for parallel computer architectures. The PTP combines existing functionality in the Eclipse Platform, the C/C++ Development Tools, and new services specifically designed to interface with parallel computing systems, to enable the development of parallel programs suitable for a range of scientific, engineering and commercial applications.
 
The Parallel Tools Platform (PTP) is a portable, scalable, standards-based integrated development environment specifically suited for application development for parallel computer architectures. The PTP combines existing functionality in the Eclipse Platform, the C/C++ Development Tools, and new services specifically designed to interface with parallel computing systems, to enable the development of parallel programs suitable for a range of scientific, engineering and commercial applications.
  
This document provides a detailed design description of the major elements of the Parallel Tools Platform.
+
This document provides a detailed design description of the major elements of the Parallel Tools Platform version 2.x.
  
 
== Architecture ==
 
== Architecture ==
Line 15: Line 15:
 
The PTP architecture has been designed to address these requirements. The following diagram provides an overview of the overall architecture.
 
The PTP architecture has been designed to address these requirements. The following diagram provides an overview of the overall architecture.
  
[[Image:ptp20_arch.png]]
+
[[Image:ptp20_arch.png|center]]
  
The architecture can be roughly divided into to major components: the ''runtime platform'', and the ''debug platform''. These components are defined in more detail in the following sections.
+
The architecture can be roughly divided into three major components: the ''runtime platform'', the ''debug platform'', and ''tool integration services''. These components are defined in more detail in the following sections.
  
== Runtime Platform ==
+
== [[PTP/designs/2.x/runtime_platform | Runtime Platform]] ==
  
The runtime platform comprises those elements relating to the launching, controlling, and monitoring of parallel applications. The runtime platform is comprised of the following elements:
+
This [[PTP/designs/2.x/runtime_platform | section]] describes the runtime monitoring and control features of PTP.
  
* runtime model
+
== [[PTP/designs/2.x/launch_platform | Launch Platform]] ==
* runtime views
+
* resource manager
+
* runtime system
+
* remote proxy runtime
+
* proxy runtime
+
* proxy client
+
* proxy server
+
* launch
+
  
PTP follows a model-view-controller (MVC) design pattern. The heart of the architecture is the ''runtime model'', which provides an abstract representation of the parallel system and the running applications. ''Runtime views'' provide the user with visual feedback of the state of the model, and provide the user interface elements that allow jobs to be launched and controlled. The ''resource manager'' is an abstraction of a resource management system, such as a job scheduler, which is typically responsible for controlling user access to compute resources via queues. The resource manager is responsible for updating the runtime model. The resource manager communicates with the ''runtime system'', which is an abstraction of a parallel runtime system, and is typically responsible for node-to-process allocation, launching processes, and other communication services. The runtime system, in turn, communicates with the ''remote proxy runtime'', which  manages proxy communication via some form of remote service. The ''proxy runtime'' is used to map the runtime system interface onto a set of commands and events that are used to communicate with a physically remote system. The proxy runtime makes use of the ''proxy client'' to provide client-side communication services for managing proxy communication. All of these elements are Eclipse plugins.
+
This [[PTP/designs/2.x/launch_platform | section]] describes the services for launching debug and non-debug jobs.
  
The ''proxy server'' is a small program that typically runs on the remote system front-end, and is responsible for performing local actions in response to commands sent by the proxy client. The results of the actions are return to the client in the form of events. The proxy server is usually written in C. The proxy client/server protocol is defined in more detail [[PTP/designs/rm_proxy|here]].
+
== [[PTP/designs/2.x/debug_platform | Debug Platform]] ==
  
The final element is ''launch'', which is responsible for managing Eclipse launch configurations, and translating these into the appropriate actions required to launch and application on the remote parallel machine.
+
This [[PTP/designs/2.x/debug_platform | section ]] describes the features and operation of the PTP parallel debugger.
  
Each of these elements is described in more detail below.
+
== [[PTP/designs/2.x/remote_services | Remote Services]] ==
  
=== Runtime Model ===
+
This [[PTP/designs/2.x/remote_services | section]] describes the remote services framework that PTP uses for communication with remote systems.
 
+
=== Runtime Views ===
+
 
+
=== Resource Manager ===
+
 
+
=== Runtime System ===
+
 
+
=== Remote Proxy Runtime ===
+
 
+
=== Proxy Runtime ===
+
 
+
=== Proxy Client ===
+
 
+
=== Proxy Server ===
+
 
+
=== Launch ===
+
 
+
== Debug Platform ==
+
 
+
=== Debug Model ===
+
 
+
=== Debug User Interface ===
+
 
+
=== Debug Controller ===
+
 
+
=== Debug API ===
+
 
+
=== Scalable Debug Manager ===
+

Latest revision as of 14:19, 1 May 2008

Overview

The Parallel Tools Platform (PTP) is a portable, scalable, standards-based integrated development environment specifically suited for application development for parallel computer architectures. The PTP combines existing functionality in the Eclipse Platform, the C/C++ Development Tools, and new services specifically designed to interface with parallel computing systems, to enable the development of parallel programs suitable for a range of scientific, engineering and commercial applications.

This document provides a detailed design description of the major elements of the Parallel Tools Platform version 2.x.

Architecture

The Parallel Tools Platform provides an Eclipse-based environment for supporting the integration of development tools that interact with parallel computer systems. PTP provides pre-installed tools for launching, controlling, monitoring, and debugging parallel applications. A number of services and extension points are also provided to enable other tools to be integrated with Eclipse an fully utilize the PTP functionality.

Unlike traditional computer systems, launching a parallel program is a complicated process. Although there is some standardization in the way to write parallel codes (such as MPI), there is little standardization in how to launch, control and interact with a parallel program. To further complicate matters, many parallel systems employ some form of resource allocation system, such as a job scheduler, and in many cases execution of the parallel program must be managed by the resource allocation system, rather than by direct invocation by the user.

In most parallel computing environments, the parallel computer system is remote from the user's location. This necessitates that the parallel runtime environment be able to communicate with the parallel computer system remotely.

The PTP architecture has been designed to address these requirements. The following diagram provides an overview of the overall architecture.

Ptp20 arch.png

The architecture can be roughly divided into three major components: the runtime platform, the debug platform, and tool integration services. These components are defined in more detail in the following sections.

Runtime Platform

This section describes the runtime monitoring and control features of PTP.

Launch Platform

This section describes the services for launching debug and non-debug jobs.

Debug Platform

This section describes the features and operation of the PTP parallel debugger.

Remote Services

This section describes the remote services framework that PTP uses for communication with remote systems.

Back to the top