1. So what is Target Management all about?
Remote Computer Systems…
Targets (Locally connected, shared, fielded)
Hosts (Grids, farms, nodes)
… and developing software on them
Build, connect, get status
Download, run, debug, test
Upload
Definition: What is the difference between targets and hosts?
A remote host is typically a multi-user system, general purpose and more powerful than a target. You also build software on it, or run other software tools.
A target is typically reserved for a single user at a time, used for specific purpose. You debug and run software on it, but typically it’s cross-compiled somewhere else.
According to this definition, a massive parallel system is also a target (because its special purpose).
We understand there are grey zones; for us, the important thing is that it’s connected somehow to the machine you’re running Eclipse on.
We’ll call the development terminal “local host” (since it’s general purpose).
Our “sweetspot” is developing software, though our frameworks might eventually be used for other application as well.
An Eclipse Project under DSDP since June 2005.
Release 1.0 planned for October 22, 2006.

2. Subsystems manage resources of a particular kind
Filters select resources dynamically

3. Target Management Architecture
Services
Actions (Download, Reset, Debug, Flash, …)
Launch Sequencer (CBL)
Remote File system
Remote Process List
Remote Shell
Predefined Elements
Filters
Views
Reusable Widgets
Connectivity
Predefined connection types (connector chains)
Connection Configuration (Plumbing)
Property Pages
Wizards
Autodetect
Target Connection Adaptors (aka Connectors)
Data Models
Target Definitions
Connection Groups
Access Control
Persistency
Profiles
Team Sharing
Legend: Existing components in RSE, Design TBD, Analysis TBD, Extension Point, Fixed implementation

4. CDT Remote Launch: Plug-in dependencies
Products
Vendor-specific debuggers, connection types, services, …
(Optional) CDT “Remote Application” Launch
DSDP-TM core
DSDP-TM plug-ins
CDT
Wizards
Views
Reusable Widgets
services
Services (Remote Files, Processes, Shells)
connection types
The CDT “Remote Application” Launch depends on DSDP-TM.
But this doesn’t necessarily mean that products based on CDT have to depend on DSDP-TM.
The optional “Remote Application” Launch will not be loaded if the DSDP-TM is not available.
DSDP provides views, team-shareable connections, and pluggable services.
The arrows mean “depends on”.
Data Models
Eclipse Platform

5. Summary: Plans and Timings
First Release (October 22, on Eclipse 3.2)
RSE – Release 1.0
Includes dstore, ssh, FTP connection types
UI tested on Windows, Linux, Solaris, Mac; targets also AIX, any FTP or SSH server
CDT Remote Launch Integration – Release 1.0
Zeroconf Discovery, EFS Integration – Preview Release
Milestones (Proposed – plan not yet finished)
More Standards based target connections (Telnet, ECF)
Terminal Emulation Framework and View
User-Defined Actions, Import/Export
Component-Based Launching (CBL)
Multi-core / Multi-target support through connection groups
Connection Model for HW Debugging (complex connector setup)
Future
Flexible Target Connector framework, Connector plumbing algorithm
Adapters for Target access control (shared board labs)
SSH tunneling connector

6. Getting Involved RSE is very flexible, with good basic abstractions
An option for your Project?
RSE is a well established product
Still, a lot of community feedback will be needed
Join the dsdp-tm-dev mailing list -
Q & A