Thanks for letting us know, Greg - looking forward to seeing and
trying this out!
Jay
From:
ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx] On Behalf
Of Greg Watson
Sent: Thursday, October 22, 2009 10:27 AM
To: Parallel Tools Platform general developers
Subject: Re: [ptp-dev] About PTP support for Remote Developement
I'm working on auto launching a dstore server over a Remote
Tools ssh tunnel. This will only require you to set up a single remote tools
connection and all services (file, indexing, build, launch, debug) will all run
across the connection, so should greatly simplify the configuration. I have a
prototype mostly working now.
I will update bug #285209 with a patch once I have things
working properly. Don't bother trying the patch that is currently there as it
is old.
Greg
On Oct 22, 2009, at 11:13 AM, 邹园斌
wrote:
I can't agree more. It's quite confusing to new a remote MPI
project.
2009/10/22 JiangJie <yangtzj@xxxxxxxxxxx>
Hi Greg,
Recently, I have been testing the PTP remote function based on RSE.
Following is some potential problems with current remote support of PTP .
By the way, my configuration is PTP 2.1 with RSE-SDK-3.0.
1. The PLDT tool is not availble to remote users since the MPI/OpenMP Artifacts
analysis depends on the availabity of MPI/OpenMP header file installed in
system.
Unfortunately, Windows users will lack these files on their systems.
2. To establish a remote connection, a rdt server must be running on remote
server node. The wiki says that there are two ways to start the remote server,
e.g, manual staring or start as daemon. However, only the manual start works
for me, and the daemon mode fails to work as expected.
Here are some outputs of the daemon servers:
#cd /home/usr/rdt-server
# perl ./daemon.pl 4725
10000-10010
Daemon running on: node1, port:4725
launched new server on 10000
On my remote PTP, when trying to open "My Home" directory after
connection established, it blocks while fetching children of "My
home".
It seems that the connection has established but fetching remote files failed.
3. After establishing remote connection with remote server manually started, it
also blocks while trying to import projects from remote filesystem.
4. The process and steps for remote development are so complex that it
may frustrate many new(even professional) users.
For example, before creating a new remote project, one has to create remote
connection first, which also involves many steps.
And the project creation itself requires complex and confusing configuration
like choosing the remote connection, etc.
To be really useful, I think the necessary steps must be simple and short.
Is there anyone here considering these issues?
Or can PTP 3.0 plus RSE 3.1 solve most of them?
In my humble opinion, the remote function is quite attractive and helpful for
non-professional HPC users, especially those coming from Windows community. I
think the remote application is very important to the application and success
for PTP.
How about PTP's plan for further support for remote development?
Maybe we should pay more attention to it.
Regards,
Jie
Messenger保护盾2.0,更安全可靠的Messenger聊天! 现在就下载!
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
|