ptp 1.0 release plan
parallel tools platform subproject
Authors:

Greg Watson
Nathan DeBardeleben
Donny Kurniawan
Clement Chu
Craig Rasmussen

Revision Date: 19 September 2005 - Version: 0.4.0
Change History: 0.1.0 - Document Creation
  0.2.0 - Added SDM features
  0.3.0 - Minor update to FDT test plan
  0.4.0 - Added MPI development tools test plan

This document describes the initial plan for achieving version 1.0 of the PTP.

Release Deliverables

The release deliverables:

Release Milestones

Current versions of PTP are built with Eclipse platform 3.1 and CDT 3.0.

The milestones are:

As of September 2003, we will be progressing through a series of candidate releases as follows:

It is expected that RC3 will become the final release.

Target Operating Environments

Platform support for PTP is complicated by the need to operate closely with a variety of parallel runtime systems and debuggers that may in turn support a wide range of architectures. Because of this complexity, the initial release will only target a single parallel runtime.

PTP Core Supported Platforms
Operating System Processor Architecture Window System Java 2 Platform
Linux (SUSE 9.1 or RHE WS4) i386 GTK Sun Java 2 Standard Edition, version 1.4.2_08 for Linux x86
Linux (SUSE 9.1 or RHE WS4) i386 GTK IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition, Version 1.4.2
Linux (SUSE 9.1 or RHE WS4) x86_64 GTK Sun Java 2 Standard Edition 5.0 Update 4 for Linux x86_64
Mac OS X 10.4 PowerPC Carbon Java 2 Standard Edition 1.4.2 for Mac OS X

 

PTP Supported Runtime Systems
MPI Runtime Processor Architecture Operating System Runtime Platform
Open MPI i386/x86_64 Linux (SUSE 9.1 or RHE WS4) rsh/ssh
Open MPI i386/x86_64 Linux (SUSE 9.1 or RHE WS4) bproc 4
Simulator i386/x86_64 Linux (SUSE 9.1 or RHE WS4) N/A
Simulator PowerPC Mac OS X 10.4 N/A

 

PTP Debugger Supported Systems
Operating System Processor Architecture MPI Runtime
Linux (SUSE 9.1 or RHE WS4) i386/x86_64 Open MPI
Linux (SUSE 9.1 or RHE WS4) i386/x86_64 Simulator
Mac OS X 10.4 PowerPC Simulator

 

Component Features

Core/Runtime

  1. A Parallel Development Perspective which is comprised of a Machines View, Jobs View, Process View, Legend, and includes a Preferences Page.
  2. A Machine's View which displays the status of all the machines the user knows of.
  3. Dynamically updated status of the nodes of machines as those nodes change state (such as 'up', 'down', 'has a job running on it')
  4. A Job's View which displays all the jobs that were started during the current session. This includes job state and a listing of processes comprising the job (including process state).
  5. A Process View which displays the status of a single process (though multiple Process Views may be open concurrently). This includes the stdout of the process and has status and exit code fields that are updated dynamically as the state of the process changes.
  6. Ability to focus on a machine, node, job, or process and display current status of that entity.
  7. A Legend dialog that displays the various icons for nodes and processes that represent the states these entities can undertake.
  8. A Preferences Page which lets the user specify settings for the type of monitoring and control system to use.
  9. A model (series of instantiated data structures) that represents the known universe (machines, nodes, jobs, processes). The model is organized heirarchically and each entity contains attributes (key/value pairs) that represent additional information about the object (such as process state, node ownership, etc.)
  10. An interface to external control and monitoring systems (runtime system components).
  11. Open-MPI control and monitoring systems implementations. These interface to Open-RTE through the Java Native Interface (JNI).
  12. Simulated control and monitoring systems which exercise the runtime system interface, user interface, and allow demonstration in environments without other control/monitoring systems.
  13. Ability to start a job on a specified machine on a specified number of processes.
  14. Ability to terminate a running job.
  15. Ability to create sets of nodes and processes for ease of viewing. Also the ability to delete entries from these sets, add to them, and focus on a given set.

Parallel Debugger

Debug Core

  1. A parallel debug model which consists of 2 packages: ptp.debug.core (PTP Debug Core) and ptp.debug.external (PTP Debug External). It is based on the CDT/CDI Debug Model. PTP Debug Core acts as a bridge between the Platform Debug Model and PTP Debug External which is connected to the external debugger interface.
  2. An extension to CDI called PCDI which is suitable for the parallel debug model is shared between PTP Debug Core and PTP Debug External. With CDI and PCDI, the external component (PTP Debug External) can be further extended or replaced without rewriting the core component (PTP Debug Core).
  3. A process debug model which is inherited from the PTP Core Process Model. All processes in the debug job are listed in the Parallel Debug view. One or more processes can be registered in the usual Debug view for further inspection.
  4. A data structure called BitList that is very similar to java.util.BitSet with the option of further space optimization of the data storage.
  5. A process set debug model to describe a set of processes using BitList as the underlying data structure.
  6. Parallel support for events, breakpoints, and variables (local variables, argument variables, and global variables).
  7. Event management system for multiple processes. Events from multiple processes can be aggregated into one event. The event system utilizes BitList to avoid overwhelming the platform with events.
  8. Breakpoint management system for multiple processes. Unlike in the CDT Debug Model where a breakpoint is associated with a single process, in PTP Debug Model, a breakpoint is associated with the debug session. Thus, a single breakpoint can be applied to a set of processes.
  9. A support to see the variables in the Variable view for selected processes in the Debug view.
  10. A well-defined interface (IDebugger) in PTP Debug External to be used by external debuggers to connect to PTP. The interface is similar to the HPDF standard albeit without command-line support (e.g. command history, debug focus).
  11. A simulated parallel debugger as an example of implementation of IDebugger. The debugger allows users to debug multiple processes (e.g. set breakpoint, resume, terminate) in a simulated environment.

Debug UI

  1. Buttons and shortcuts to create, delete and modify the set by selecting elements in Debug Views.
  2. Ability to name a new set in Debug Views.
  3. Change set button to switch the set for examining the status of the elements in Debug Views.
  4. Parallel Debug view supports mulitple jobs run and ability to switch to specific job to display its processes.
  5. Parallel Debug view supports process registering or unregistering to and from the Standard Debug view.
  6. C/C++ Source Editor in Parallel Debug Perspective allows create, delete, enable and disable parallel breakpoint.
  7. Tooltip display to represent the multiple breakpoints on the same location with different jobs.
  8. Breakpoint represent its status in different sets in different colors.
  9. A set of buttons in the parallel debug view allows to resume, suspend, stop, step into, step over and step return all processes in the current set.
  10. A set of buttons in the debug view allows to control the selected processes in this view.
  11. Parallel Breakpoint Set view in Standard Breakpoint view which groups multiple sets of breakpoints.

Scalable Debug Manager

  1. Debugger launched from UI using normal launch configuration
  2. Support for local or remote debugging (i.e. debugger frontend can be on local or remote machine)
  3. Support for multiple proxy protocols between Eclipse and debug frontend (initial implementation using TCP)
  4. Debugger integration with OpenRTE
  5. Support for basic debug commands (to be extended):
    1. Set line/function breakpoint
    2. Single step
    3. Continue execution
    4. Evaluate expression
    5. List local/global variables
    6. Stackframe manipulation
  6. Debug commands can be applied to all or specific sets of processes.
  7. All debug commands operate asynchronously
  8. Support for three modes of event handling:
    1. wait for events from all processes
    2. wait for events from set of processes
    3. wait for all events within a specified interval
  9. Debugger will automatically coalesce events of the same type

Fortran Development Tools

  1. Modifications to the CDT to provide a user interface that is language independent and less focused on C and C++. These modifications include:
    1. Modify the CDT C/C++ perspective to a "Make Projects" perspective.
    2. Create "Managed Make" and "Standard Make" projects types and associated wizards to create them.
    3. Modify CDT icons to reflect changes to the CDT.
  2. Additions to the CDT to provide an IDE for Fortran. These additions include:
    1. A Fortran language model.
    2. A Fortran editor with syntax highlighting.
    3. Recognition of Fortran file extensions.
    4. Mixed language toolchains including C, C++, Fortran compilers.
    5. Toolchain support for IBM, Intel, and GNU Fortran compilers.
    6. Error parsers for IBM, Intel, and GNU Fortran compilers.
    7. Dependency analysis enhancements to the Managed Make System to allow projects with multiple Fortran files to be built in the correct order.
    8. Capability to launch Fortran applications

MPI Development Tools

  1. Static analysis of one or more C/C++ source files to identify the location of MPI artifacts
  2. Preference page for setting up MPI header file location and other configuration information.
  3. Eclipse toolbar buttons for initiating static analysis for artifact identification, and clearing existing artifact markers.
  4. Identification of "MPI artifacts" from C/C++ code in an Eclipse view listing API name, source file name and line number, artifact type (function or constant), etc. - linked with markers to source code locations.
  5. Markers on each artifact to identify in source file, and allow navigation to the source line containing each artifact
  6. Content Assist (Ctrl-space) shows possible completions of arbitrary partial API names in C source files. Mouse or cursor selection aids entry and reduces typing while improving accuracy.
  7. Context-sensitive help on each identified API in C source files: mouse hover shows API name, brief description, argument types, and MPI types as exemplary fulfillments of argument types (instead of generic C type. e.g. 'MPI_Comm' instead of 'int')
  8. Help view via F1 on each identified API in C source files - shows more detailed descriptions.
  9. Help plug-in includes setup, examples, and walk-thru of usage of all features including screen shots.

Component Test Plans

Core/Runtime

SETUP:

  1. Start on a bproc machine.
  2. Make sure Open-MPI is setup and working (not part of this test, just required to utilize Open-MPI).
  3. Start with a fresh Eclipse install (including workspace).
  4. Install PTP.
  5. Compile the PTP Open-MPI JNI library.
  6. Acquire some set of nodes for a long period for testing.
  7. Launch Eclipse and then launch a new Eclipse with the PTP plugins running.

TEST PLAN:

  1. Using the Parallel Development Preferences Page select the Simulated runtime system.
  2. Using the menuing system, open the Machines View and Jobs View.
  3. Confirm that the Jobs View shows no jobs since it is a clean start.
  4. Confirm that the Machines View displays the current state of the machines. Use the drop-down menus to observe other machines that are known and confirm they too display the current machine state.
  5. Create a set of nodes using the user interface and name the set.
  6. Confirm that the user can switch between (focus on) the full set of nodes for the given machine and the newly created set.
  7. Add a few more nodes to the new set.
  8. Focus on a different machine and confirm that the set is no longer visible (since it pertains to the original machine).
  9. Create a new C project.
  10. Create a new C-MPI source file in the project. The source file will have each process producing periodic output and run for a few minutes (so that the tests can be performed on a running job).
  11. Compile the C-MPI application.
  12. Create a new Run Configuration for this project, utilizing the Parallel Development configuration to specify the number of processes for this run and a chosen simulated machine.
  13. Run the job (under simulated control).
  14. Confirm that the appropriate node's change state in the Machines View to specify they contain a running job and that the job starts on the correct machine.
  15. Focus on a node where one of the processes has been assigned. Confirm that the Machines View displays the processes on that node, including which job the process belongs to.
  16. Double-click on one of the processes in the Machine View to bring up the Process View. Confirm that the MPI rank, node number, job number, and status are correct.
  17. Observe process output in the output section of the Process View.
  18. Wait for job to terminate.
  19. Observe that the process state and exit code correctly display in the Process View, Machine View (for the appropriate node), and Jobs View (for the appropriate Job).
  20. Bring the Jobs View to the foreground.
  21. Confirm the Job previously run, as well as the processes contained within it, are listed and is shown as terminated.
  22. Re-run the same job. Confirm the Job View displays the job as running and the processes as well.
  23. Double-click on a process of the job, opening the Process View. Confirm the running state.
  24. Terminate the job by using the terminate icon.
  25. Confirm the Job View updates to show the terminated state.
  26. Confirm the Process View updates to show the terminated state, including an exit-code.
  27. Using the Parallel Development Preferences Page select the Open-MPI runtime system.
  28. Using the Open MPI Preferences Page under the Parallel Development Preferences Page set the path and arguments to the ORTE daemon (ORTEd).
  29. Run the same job from step #12 (under OMPI control).
  30. Repeat steps #14 through #26 for this second runtime system (Open-MPI as opposed to simulation).
  31. Switch back to the Machine View.
  32. Using another terminal change the state of one of the nodes (reboot it, change ownership, etc) and confirm that the node's status changes in the Machine View (both the icon to match the legend as well as the detailed text information to display the new change(s)).

Parallel Debugger

Debug Core

SETUP:

  1. Make sure that the correct version of CDT and Eclipse are installed.
  2. Check out these packages from dev.eclipse.org:/cvsroot/tools/org.eclipse.ptp:
  3. Run the Eclipse Application
  4. Create a simple Managed Make C Project with the name: "TestC"
  5. Create the main program file with the name: "main.c"
  6. Fill in "main.c" with any code since the Debug Simulator will not interpret the source code (it only gets the line number). Edit the file so that it contains only 20 lines.
  7. Create the PTP Launch Configuration and fill in the necessary configuration, including the number of processes.

TEST PLAN:

  1. Switch to the Parallel Debug Perspective.
  2. Double click the ruler at any line in the source code window to set the breakpoint, set another breakpoint after the first breakpoint.
  3. Verify that the breakpoints have been set by looking at the Breakpoints view.
  4. Click the debug button for the created PTP Launch Configuration.
  5. Process 0 will be registered automatically in the Debug view, 2 Console views will also be opened (one for process 0, and the other for the debugger output).
  6. After printing the output for process 0, which can be verified by opening the Console view for process 0, all processes (process 0 and others) will break at the first breakpoint (since the breakpoint applies for all processes).
  7. Verify this by looking at the Debug view and see that process 0 is suspended. Look at the Parallel Debug view, all processes should change to yellow. Look at the Console view for process 0, the output should stop. Look at the Console view for the debugger, there should be text saying that BreakpointEvent has been received.
  8. Double click process 1 in the Parallel Debug view to register it to the Debug view. Look at the Debug view and see that process 1 has been registered and in the suspended state. Look at the Console view and verify that Console view for process 1 has been created.
  9. Select process 0 and click the Step Over button in the Debug view. Look at the Console view for process 0 to verify that the action has been executed successfully. Repeat and verify this action several time
  10. Select process 1 and click the Step Into button in the Debug view. Look at the Debug view and see that the number of stackframes for process 1 increases by one. Click Step Into to increase the stackframe and click Step Finish to decrease the stackframe. Repeat and verify this action several times. The maximum number of stackframes is 5.
  11. Select the stackframe of process 0 and open the Variables view. Verify that there are 2 argument variables and 2 local variables.
  12. Select process 0 and click the Resume button, it will then hit the second breakpoint. Click the Resume button again to run process 0 until completion (it prints 20 lines and then exits). Look at the Debug view and the Console view and verify that process 0 has exited.
  13. Select process 1 and click the Terminate button. Look at the Debug view and the Console view and verify that process 1 has been terminated.

Debug UI

SETUP

  1. Create a C/C++ Project named as "TestC"
  2. reate a file called "main.c"
  3. Open it and write any coding
  4. Switch to Debug Parallel Perspective
  5. Add any breakpoint on "main.c" file by double click on ruler. OR double click anywhere on source editor and then double click on ruler again.
  6. Click launch button to create parallel configuration and then adding the project name, filename and the number of processes.
  7. Click debug button to launch this program.

TEST PLAN:

  1. Starting:
    1. Parallel Debug View displays the status of processes after launching a parallel program in debug mode.
    2. Debug icon of the job represent that it is in debug mode.
    3. The new job will be selected at the start up and the all processes of this job will be displayed.
    4. Unselected the job, the process view will be cleared.
  2. View:
    1. Drag across a rectangular region to select some processes. Hold down the left mouse button, move the mouse, and release the button when the desired process is selected.
    2. Click with the left mouse button while holding down the Shift key will extent selection.
    3. Click with the left mouse button while holding down the Ctrl key will continue selection.
    4. A dialog box will popup when press the Create set button. After enter set name, the view will change from root set to created set.
    5. There is a validation to check whether a new set name already exist or not. If exists, the ok button will be disabled.
    6. Only set can be created after the job is launched.
    7. Press Ctrl-A key can select all the processes.
    8. Press Page-up key can go up one page.
    9. Press Page-down key can go down one page.
    10. Auto scrolling while dragging further up or down the views.
  3. Breakpoint:
    1. The parallel breakpoint is created when double click on ruler of the C/C++ source editor.
    2. If the parallel breakpoint is created in the condition that is no job running or unselected all the jobs, this breakpoint will belong to be global for all the jobs and there is an additional overlayered image on the breakpoint.
    3. Tooltips displaying details of breakpoint (job name, set name, file name and line number) will appear when mouse hovers on the breakpoint.
    4. Color of a breakpoint will change to green when it is created in the current set's process.
    5. Color of a breakpoint will change to yellow when it does not exist in any of the set's process.
    6. Color of a breakpoint will change to blue when it exists in one of the process in the current set but is not created in this set.
    7. Double on the created breakpoint on ruler, the breakpoint will be removed.
    8. The global breakpoint only can be created or removed when there is no job selected.
    9. Multiple breakpoints can be created in the same source file and the same line number with different jobs.
  4. Breakpoint view:
    1. All breakpoints will be displayed ordered by the set name when clicking the drop down menu in the breakpoint view and then the parallel breakpoint set.
    2. Unchecked the breapoint in Breakpoint View, the breakpoint will be disabled. Check it again, it will be enabled again.
    3. Right click on the breakpoint in Breakpoint View and select Goto Set action, the parallel debug view will change to the job and the set indicated in the selected breakpoint.
  5. Register / Unregister:
    1. Double click on the process in parallel debug view and the process will be registered into the debug view. A registered process is presented by a black rectangle.
    2. Selecting multiple processes in the parallel debug view and then click the register button will register all of them in the debug view.
    3. If more than 10 processes have been selected to register, a dialog will popup and ask for confirmation.
    4. Double click on the registered process will unregister it from the debug view. The black rectangle representing the registration will be removed.
    5. Selecting multiple registered processes in the parallel debug view and then click the unregister button will unregister all of them in the debug view.
    6. The debug view will only display registered processes which is according to the current job and current set.
  6. Annotation
    1. If a breakpoint location contains multiple markers, annotations for both these markers will be overlapped when the breakpoint is hit. The registered process marker should appear on top. Tooltips will display process task id of each marker set in this location, grouped by its marker.
    2. The annotation will change to another color(not created) when switch to another set.
    3. The process icon appears in yellow process is in suspended mode.
    4. The process icon appears in green when in running mode.
    5. The process icon appears in red when in terminate mode.
    6. The resume button and all step buttons in the parallel debug view will only be enabled when one of the processes is suspended.
    7. The suspend button in the parallel debug view will only be enabled when one of the processes is running.
    8. The terminate button in the parallel debug view will only be enabled when one othe processes is either running or suspended.
    9. Resume button in the parallel debug view resumes all suspended processes in the current set.
    10. Suspend button in the parallel debug view pauses all running processes in the current set.
    11. Terminate button in the parallel debug view stops all suspended and running processes in the current set.
    12. Step buttons in the parallel debug view can step into, step over and step return all suspended processes in the current set.
    13. Resume button in the debug view can resume selected suspended process(es).
    14. Suspend button in the debug view can pause selected running process(es).
    15. Terminate button in the parallel debug view can stop any suspended or running process(es).
    16. Step buttons in the debug view can step into, step over and step return any suspended process(es).

Scalable Debug Manager

TBD

Fortran Development Tools

  1. In a new workspace, check out the following CDT components from dev.eclipse.org:/home/tools
  2. Next check out the FDT components from dev.eclipse.org:/cvsroot/tools
  3. From a shell, cd to Eclipse workspace and execute the shell script cdt_changes/install
  4. Select org.eclipse.cdt.* projects one by one and refresh them.
  5. Verify that workspace builds correctly without any errors.
  6. Create Eclipse Application launch configuration (FDT) and run it.
  7. Examine icons (set left of debug icon) and make sure that project, folder, and file wizard icons are "M" based not "C" based. Also check that there is a "Make" perspective and a "Make Projects" window.
  8. Examine menus corresponding to these icons and make sure they don't have C/C++ in labels.
  9. Right click in "Make Project" window and examine icons and menu labels as in #6 and #7 above.
  10. Use menu in project icon to create a new "Managed Make" project, name it HelloWorld (check icon). Select Gnu Fortran for project type and click Finish.
  11. Use menu in file icon to create a new source file. Name it hello.f90; make sure the file extension is acceptable and check icon and click Finish.
  12. Check that new file is automatically opened.
  13. Copy contents of org.eclipse.fdt.managedbuilder.tests/src/HelloWorld/hello.f90 into the new file and save the file.
  14. Check console to see that "Build complete for project HelloWorld"
  15. Create new "Local Application" Run target. Ensure that label in the configurations window is "Local Application" and icon has an "M". Name the configuration HelloWorld and set the Project and Application fields. Set a debugger and click Run.
  16. Check that "Hello from Fortran Main." is printed in the console window. Select the HelloWorld target from the Run menu and check console output again.
  17. Redo steps 9-15 for the directory, org.eclipse.fdt.managedbuilder.tests/src/Components. That is, create a Managed Make project named Components and build an application the files.
    1. Open Debug/subdir.mk and ensure the dependencies are as follows:
      • Driver.o: MonteCarloIntegrator.o
      • MonteCarloIntegrator.o: LinearFunction.o
      • MonteCarloIntegrator.o: RandNumGenerator.o
    2. Make sure the project will build and run.
  18. Redo steps 9-15 for the directory, org.eclipse.fdt.managedbuilder.tests/src/Mixed. That is, create a Managed Make project named Mixed and build an application the files.
    1. Make sure the mixed language project will build and run

MPI Development Tools

(See help files in the plug-in for more details on these)

  1. Launch eclipse with PTP (incl. CDT)
  2. Help -> Help Contents, PTP MPI Tools
  3. Follow instructions in "Setup for PTP MPI tools". Basically, create a CDT project, a source file with MPI apis (a sample is included in help), and use Preferences to locate MPI header files.
  4. Follow instructions in "Running PTP MPI tools" to set up Open MPI artifacts view (Do we need to explicitly add the actions to the toolbar?)
  5. select source vile in Navigator, then select MPI action to run analysis.
  6. MPI artifact view should be populated with markers, listing API name, source file name and line number, and artifact type (function or constant)
  7. Double-click on any artifact, this should take you to the source file and line locating the artifact.
  8. In source file, icon should be in marker bar, and squiggles should be under the artifact (e.g. function name)
  9. Click on column headings in artifact view to sort by values in that column.
  10. Command completion: In editor, type e.g. MPI_ and hit ctrl-space. Possible completions should appear. Continue to type a few characters; possible completions should diminish to match string. Hitting ENTER or double-clicking on any choice should insert the completed API into the file.
  11. Hover help: Hover on any MPI API, see yellow popup info on API and arguments.
  12. F1 help: click on any MPI API and hit F1 to see Help view appear; click on API in that view and see detailed info on that API.