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/designs/remote/cdt" and "OHF"

< PTP‎ | designs‎ | remote(Difference between pages)
(What is Needed?)
 
(Audit record repository)
 
Line 1: Line 1:
= Adding Remote Build and Remote File System Support to CDT =
+
=== 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.
  
Our [[PTP/designs/remote|objective]] is to provide remote support for the Parallel Tools Project in a way that is natural to the user. The approach we take is to extend the new emerging Eclipse File System (EFS) with support for remote file systems, and use RSE to run commands on the remote machine (see the [[PTP/designs/remote|evaluation]]). Most parallel application development uses either the CDT and Photran components, however neither of these components currently support EFS or remote building.
+
=== Additional OHF sites ===
 +
* [http://www.eclipse.org/ohf/ OHF Project Home Page]
 +
* [http://ohf-dev.blogspot.com/ OHF Committers Blog]
  
The following diagram shows a typical scenario in which a separate file server, build server and compute server are employed. Projects are physically located on the file server. Using EFS and a remote filesystem protocol, project files appear local to Eclipse users. The build server mounts the project from the file server using a standard remote filesystem protocol. When Eclipse needs to index or build the project, it uses RSE to launch a remote command onto the build server. The result of the indexing or building is saved in the project directory and so is then accessible to Eclipse to update it's project view. Once the project has been built it can be launched or debugged on the compute server using RSE to send remote commands. The compute server also mounts the project directory from the file server, so no executable files actually need to be transmitted. Other scenarios in which the build, file and compute servers are combined are also possible.
+
=== Discussions ===
 +
* [[OHF using SCA]]
  
[[Image:Eclipse_remote.pdf]]
+
== OHF Relationship Management (& Current Events etc) ==
  
== The Current Status ==
+
* [[OHF Relationship Management: Java]]
CDT has no support for EFS at all. Even support for locally linked resources, as a special example of EFS, is quite limited. For example, the standard make C project does not support linked files. The following bugs are also identified:
+
* [[OHF Relationship Management: Eclipse]]
* 136136 Build directory should not be restricted to workspace
+
* [[OHF Relationship Management: Open Source Healthcare initiatives]]
* 70491 Invalid Include Path when "Link to Folder in the Filesystem"
+
* [[OHF Relationship Management: Standards Organisations]]
Also see http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg03059.html for a discussion of linked resources.
+
* [[OHF Relationship Management: Corporates]]
  
CDT also assumes that the source files are available locally and uses this fact when running the indexer. The build command is also assumed to run locally and access a local filesystem.
+
=== Public Healthcare Serveices ===
 +
This section contains a list of known public standard healthcare services.  
  
== What is Needed? ==
+
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.
  
The above process abstracts and covers many different cases. Some typical scenarios include, but not limited to:
+
None of the listed services are part of Eclipse or Eclipse OHF.  
* whole project on remote server: if the build machine is the same as the file server, then no replication is necessary; otherwise replicate.
+
The services are publicly avaliable for demos and interoperability
* project with locally linked directories and files (linked to local file system): the files need to be replicated to a local build directory before invoking the build command.
+
tests and they are not part of production environment.
* project with virtual file system (zip, for example): the files has to be replicated to a local build directory.
+
  
This will affect several other related components of CDT. Such components include the Indexer, Managed Make etc.
+
'''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 Filesystem Support for EFS ===
+
====Audit record repository====
   
+
{| style="background-color:#ABCDEF;"
With EFS, projects or its component directories and files can be linked to different file systems, which can be local, remote, or virtual. The files and directories can be physically located at completely diverse places. However, there is currently no support for true remote filesystem protocols (e.g. NFS or V9FS). The only implementation provided is for FTP. Support for these remote filesystem protocols needs to be added, along with UI support for specifying remote hostname, protocol and mount directories.
+
|+Public Healthcare Services
 +
|-
 +
! Vendor !! Service URL !! BSD SYSLOG Port !! Reliable Syslog Port  
 +
|-
 +
! IBM
 +
| ibmod235.dal-ebis.ihost.com || 541 || N/A
 +
|}
  
=== Adding EFS Support to CDT ===
+
== OHF Meetings ==
 
+
* [[Face to Face meeting at EclipseCon]]
To support EFS while keeping the standard make builder, the CDT build has to be modified in the way that the files in the project can, when necessary, be replicated in a build directory (optionally on a remote build server) before the build command is invoked. The existing build directory of the C/C++ Build property can be exteded for this purpose and an additional property of build server can be added (see the picture).
+
** [[Pictures from the meeting]]
 
+
[[Image:Buildserver.jpg]]
+
 
+
=== Adding Remote Indexer and Remote Build Support to CDT ===
+
 
+
== Roadmap to EFS Enablement for CDT ==
+
# Modify the code to allow build directory outside of workspace (fix to bug 136136)
+
# Modify CDT Project Creation/Conversion Wizard for EFS support
+
# Add build server property to the build property tab and modify the code to launch build command on build server
+
# Modify the affected components like Indexer and ManagedMake and fix those components [to be investigated]
+
# Enable file replication before build to support other scenarios
+

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