Skip to main content

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.

Jump to: navigation, search

Difference between pages "PTP/planning/remote" and "OHF"

< PTP‎ | planning(Difference between pages)
(Future)
 
(Audit record repository)
 
Line 1: Line 1:
= Evaluation of Related Works for Remote Service Support =
+
=== About OHF ===
 +
This is the Eclipse Open Healthcare Framework (OHF) wiki. The OHF project addresses part of an need to improve the levels of interoperability between applications and systems within and across healthcare organizations – corporate and regions.
  
List of Authors:
+
=== Additional OHF sites ===
    Tianchao Li (lit@in.tum.de)
+
* [http://www.eclipse.org/ohf/ OHF Project Home Page]
    Greg Watson (gwatson@lanl.gov)
+
* [http://ohf-dev.blogspot.com/ OHF Committers Blog]
    (future authors)
+
  
== Background ==
+
=== Discussions ===
 +
* [[OHF using SCA]]
  
=== The Need for Remote Compile, Launch and Debug ===
+
== OHF Relationship Management (& Current Events etc) ==
The current implementation of PTP (v1.0) provides basic support for the coding, compiling, launching and debugging of parallel jobs on a local parallel machine. However, a more typical situation involves one or more of these activities ocurring on a remote machine. In a practical configuration, the development of parallel programs often involves four environments:
+
  
; User desktop : the user environment that supports coding and provides UI for compiling, launching and debugging
+
* [[OHF Relationship Management: Java]]
; File server : the machine on which the project files reside
+
* [[OHF Relationship Management: Eclipse]]
; Build environment : the machine on which the program is to be built, which provides an environment with the same libraries and services available on the parallel machine
+
* [[OHF Relationship Management: Open Source Healthcare initiatives]]
; Parallel machine : the machine on which the program is executed and debugged
+
* [[OHF Relationship Management: Standards Organisations]]
 +
* [[OHF Relationship Management: Corporates]]
  
It is possible that any combination of these machines may be physically remote, however it is normal for the user's desktop to be remote from the other machines. PTP must be able to support this range of configurations if it is to meet the needs of application developers.
+
=== Public Healthcare Serveices ===
 +
This section contains a list of known public standard healthcare services.  
  
=== Project Configuration Alternatives ===
+
The listed services are actors on one of the [http://www.ihe.net IHE] profiles. OHF implements components that interacts with these services. The purpose of the list is to help developers test the plugins they develop, to validate full interoperability across vendors, and to validate comliance with the standard.
  
There are three different possible ways that projects may be hosted in Eclipse:
+
None of the listed services are part of Eclipse or Eclipse OHF.
 +
The services are publicly avaliable for demos and interoperability
 +
tests and they are not part of production environment.
  
; Local Project : the project and all code of the parallel program is stored in the local file system of the user's desktop.
+
'''We welcome any service providor that have a public standard based healthcare service to contact us in order to add new services to the list'''
; Remote Project : the project and all code is physically located on a remote machine  (either a dedicated machine or one of the build machine or parallel machine).
+
; Hybrid Project : the user desktop physically holds the project (in particular the project configuration information) but some or all of the code is physically located on a remote machine.
+
  
The process of building, launching and debugging applications differs for each combination of local and remote resources.
+
====Audit record repository====
 +
{| style="background-color:#ABCDEF;"
 +
|+Public Healthcare Services
 +
|-
 +
! Vendor !! Service URL !! BSD SYSLOG Port !! Reliable Syslog Port 
 +
|-
 +
! IBM
 +
| ibmod235.dal-ebis.ihost.com || 541 || N/A
 +
|}
  
==== Local Project ====
+
== OHF Meetings ==
 
+
* [[Face to Face meeting at EclipseCon]]
In the case where the user's desktop is the central location where the whole project is physically located, the following capabilities are required to support remote build, launch and debug:
+
** [[Pictures from the meeting]]
 
+
'''Remote Build'''
+
 
+
# The code and build information (e.g. Makefiles) must be first transferred to the build machine (possibly through project export).
+
# The build command is invoked on the build machine.
+
# The build log is transferred back to the local machine and used to update the local models and views (problem view, marker view etc).
+
# The binary is transferred back to the local machine.
+
 
+
'''Remote Launch & Debug '''
+
 
+
# The control/monitoring/resource management system is invoked on the parallel machine.
+
# The binary is transferred to the parallel machine.
+
# Input data files are transferred to the parallel machine.
+
# The launch command is invoked on the parallel machine.
+
# The user desktop can then control the execution and debugging of the program.
+
# The stdio and stderr is trapped and sent back to the user desktop.
+
# Any output data files are transferred back to the user desktop.
+
 
+
==== Remote Project ====
+
 
+
In the case that a remote machine physically holds the project code, the following capabilities are required to support remote build, launch and debug:
+
 
+
'''Code Edit'''
+
# The user environment accesses the project files through the remote file system.
+
 
+
'''Remote Build'''
+
 
+
# The code and build information (e.g. Makefiles) should be transferred to the build machine (possibly through project export), if the build machine is different from the machine that physically holds the project.
+
# The build command is invoked on the build machine.
+
# The build log is transferred back to the local machine and updates local models and views (problem view, marker view etc).
+
# The binary is transferred to the remote machine that holds the project.
+
 
+
'''Remote Launch & Debug '''
+
 
+
# The control/monitoring/resource management system is invoked on the parallel machine.
+
# The binary is transferred to the parallel machine, if different from build machine.
+
# Input data files are transferred to the parallel machine, if different from build machine.
+
# The launch command is invoked on the parallel machine.
+
# The user desktop can then control the execution and debugging of the program.
+
# The stdio and stderr is trapped and sent back to the user desktop.
+
# Any output data files are transferred back to the build machine, if necessary.
+
 
+
==== Hybrid Project ====
+
 
+
If some project files reside on the user's desktop and some on a remote fileserver, then both sets of files need to be reconciled prior to building and/or launching. Once the files have been reconciled, the hybrid project can be treated as a remote project.
+
 
+
=== Required Functionality ===
+
 
+
Additional functionality is required to handle each of the project configuration cases:
+
 
+
==== Local Project ====
+
 
+
# File transfer between local machine and remote machine (replicate project to remote machine and update project with remote changes, using import/export or team synchronization)
+
# Execute commands on remote machines
+
# Access services on the remote machine (proxy via standard TCP/IP)
+
 
+
==== Remote Project ====
+
 
+
# Create project on remote file system
+
# Initiate transfer of files between remote machines from the local machine
+
# Execute commands on remote machines
+
# Access services on the remote machine (proxy via standard TCP/IP)
+
 
+
==== Hybrid Project ====
+
 
+
# Transfer files between local and remote machine and initiate transfer between remote machines
+
# Otherwise, same as remote project
+
 
+
== Related Work ==
+
 
+
There is already some work in both the Eclipse platform and the DSDP project that is relevant to PTP. Almost all of this work is still at a relatively primitive stage however, and we summarize below both their current status and proposed future development targets.
+
 
+
=== Alternate File System ===
+
The ability to support alternative file systems within Eclipse, including non local file systems, has already been requested by a number of people from different areas. Some work has already been undertaken to provide this support.
+
 
+
==== Status ====
+
Starting from Eclipse 3.2 M5, alternative file system support has been partially added. There are two extension points involved:
+
 
+
* org.eclipse.core.filesystem (defined in org.eclipse.core.filesystem plugin) - core support for file system
+
* org.eclipse.ui.ide.filesystemSupport (defined in org.eclipes.ui.ide plugin) - ui support for file system
+
 
+
Existing implementations provided by the Eclipse core for file system include: local, zip, memory.
+
The work on FTP file system seems to be going but the current code in the CVS is broken.
+
 
+
There is currently no UI extension for FTP file system. The UI support for memory file system is also not working. The UI support for zip file system is not complete. Bugs (137878, 137879) have been submitted.
+
 
+
For more information about the alternate file system, please reference http://www.eclipse.org/eclipse/platform-core/documents/3.2/flexible_workspaces/ and bug item 106176 and 109194.
+
 
+
RSE has also provided an extension to the org.eclipse.core.filesystem extension point, which is a wrapper of its remote file subsystem. However, no extension to org.eclipse.ui.ide.filesystemSupport has been provided and thus it is not possible to use it directly.
+
 
+
Projects and Linked Resources can now be created with alternative file systems (unfortunately only the zip file system is merely operable).
+
 
+
The 3.2 M5 release notes say that JDT has support non local file systems. However, no actual support is seen in the distribution. And bug 113373 indicates that the work is actually pending.
+
 
+
==== Future ====
+
I expect that the final release of Eclipse 3.2 and future 3.3 will provide better support for alternative file systems in both the platform level and the JDT level. However, other projects might need some time to catch up with such a change. Fundamental efforts might even be necessary to provide full support for some of the projects, like CDT, Photran etc.
+
 
+
=== Remote System Explorer ===
+
More specifically, RSE provides UI and API support for browsing and manipulating files on remote systems, execute commands on remote systems, monitoring processes on remote systems and searching
+
 
+
==== Status ====
+
The code currently in the CVS are solely those contributed by IBM. Many of the IDs are still prefixed by "com.ibm.rse". An experiment of the RSE shows that it basically works as it claimed. However, it does not meet our needs and possibly also does not meet the need of DSDP project:
+
 
+
# As the name suggests, the RSE is intended to be an explorer (or shell). The whole infrastructure is designed toward this aim. So, instead of trying to integrate and contribute to the underlying Eclipse platform, the RSE sets up a closed environment that are divided into a core and different subsystems. The design of UI components also towards the same target.
+
# The file subsystem and search subsystem of RSE are actually a duplicate functionality with the emerge of alternate file system support from the Eclipse core. Although a wrapper is implemented that exposes RSE file system, its implementation is not complete. Also, no UI integration has been provided.
+
 
+
Besides, there are also other drawbacks in the current implementation of RSE:
+
# The datastore feature is unlikely to be of interest to us, as it requires a specific datastore service to be started on the remote machine.
+
# The support for remote file and remote shell based on SSH is not currently available.
+
# The current code in the CVS combines the core model and UI implementation together in org.eclipse.rse.ui, and thus is difficult to read and understand.
+
 
+
Another possibility to improve RSE is to separate its dependency on the IDE into another plug-in. This will be helpful to use it within RCP programs.
+
 
+
==== Future ====
+
I'm expecting that the file subsystem and search subsystem of RSE should be faded out. The shell subsystem of RSE for remote execution is something also useful for remote file system support in the Eclipse core. So, I'll expect that part be adapted and finally become part of the Eclipse platform. And, only the UI part remains in RSE.
+
RSE is now part of the Target Management subproject of DSDP. Because of the similar challenge for both the PTP and the DSDP, I'm expecting that RSE will be adapted and extended to better support the need of target management for both embedded devices and parallel machines. We will have to collaborate with the developers from DSDP to speed up this process.
+
 
+
== Roadmap to PTP Remote Service Support ==
+
 
+
Based on the current status of Alternative File System and RSE, the following development tasks have been identified:
+
 
+
# Extend RSE to support remote execution via SSH [on hold while the status of similar projects is determined]
+
# Provide a remote file system implementation for core.filesystem. Initial implementation will use the 9P2000 protocol.
+
# Extend Eclipse platform to support project export to remote file system.
+
# Extend Eclipse platform to support project update from remote file system.
+
# Make sure the runtime and debug proxy implementations are appropriate for remote invocation.
+
# Modify CDT and Photran project build to support remote build [to be detailed]
+
# Modify PTP launch to support remote launch [to be detailed]
+
# Modify PTP debug to support remote debug [to be detailed]
+
 
+
== Summary ==
+
 
+
RSE can be a potential platform to enable remote service support for PTP. However, huge efforts are still demanded.
+
Collaborative development is also necessary to get the CDT and Photran prepared for remote building and launching.
+
 
+
== Open Issues ==
+
 
+
Resource management is being designed and developed in PTP, how does remote services support fits into the design remains to be discssed.
+

Revision as of 18:08, 4 May 2006

About OHF

This is the Eclipse Open Healthcare Framework (OHF) wiki. The OHF project addresses part of an need to improve the levels of interoperability between applications and systems within and across healthcare organizations – corporate and regions.

Additional OHF sites

Discussions

OHF Relationship Management (& Current Events etc)

Public Healthcare Serveices

This section contains a list of known public standard healthcare services.

The listed services are actors on one of the IHE profiles. OHF implements components that interacts with these services. The purpose of the list is to help developers test the plugins they develop, to validate full interoperability across vendors, and to validate comliance with the standard.

None of the listed services are part of Eclipse or Eclipse OHF. 
The services are publicly avaliable for demos and interoperability 
tests and they are not part of production environment.

We welcome any service providor that have a public standard based healthcare service to contact us in order to add new services to the list

Audit record repository

Public Healthcare Services
Vendor Service URL BSD SYSLOG Port Reliable Syslog Port
IBM ibmod235.dal-ebis.ihost.com 541 N/A

OHF Meetings

Back to the top