It’s possible to create remote connections programmatically, but I’m guessing you don’t want to do that. I tried simply copying the preferences into a new workspace and it seemed to be fine. Would that work for you? Otherwise I could add some functionality to load default connections from a text file or something similar.
The contents of the preference file (called org.eclipse.remote.core.prefs) was:
connections/org.eclipse.remote.JSch/Remote+Host/JSCH_ADDRESS_ATTR=localhost connections/org.eclipse.remote.JSch/Remote+Host/JSCH_IS_PASSWORD_ATTR=false connections/org.eclipse.remote.JSch/Remote+Host/JSCH_LOGIN_SHELL_COMMAND_ATTR=/bin/bash -l -c '{0}' connections/org.eclipse.remote.JSch/Remote+Host/JSCH_PORT_ATTR=22 connections/org.eclipse.remote.JSch/Remote+Host/JSCH_TIMEOUT_ATTR=0 connections/org.eclipse.remote.JSch/Remote+Host/JSCH_USERNAME_ATTR=gw6 eclipse.preferences.version=1
The string “Remote+Host” is a URL encoded version of “Remote Host”. I put this file in ${workspace_loc}/.plugins/org.eclipse.core.runtime/.settings
Regards, Greg
Damien,
We can set any default host values that you want. At the risk of sharing too much internal detail, we have a simple API call - addHost() - for this; c.f. line 130 in
However, this method only works if those hosts are static and known at build time. I imagine in your case you want to do it from a configuration file or something, right? That would let you run a script at deployment time that would modify the defaults in the VIBE host table based on the network configuration (or otherwise manually configure it). If that is what you want, I'll get a ticket started and work on it for you. If you know the network topology will be static, then we can just use addHost(). Just let me know what you want to do!
This won't address any of the PTP issues though. We'll have to have Greg Watson look at those. He's out until Monday, but I'll speak to him about it then. He can definitely help with the key issue.
I'm happy to fix this problem for you, but on a side note, is there a reason that you want to run ICE in a VM? It works just fine on Windows, Mac or Linux without a VM. The only reasons I can think of for using a VM are all about special configurations.
Jay
P.S. - Did you join the list? I'll won't add you back to the "To" line if so.
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
1. We have a similar request from OSC to enable default connections, c.f. - https://github.com/eclipse/ice/issues/260 It is similar, but not exactly the same. In that case we are looking at having a file that can be edited outside of ICE to configure the hosts table for when ICE runs. (This is an old idea - we used to support it, but I deleted it years ago.) Damien, will you describe in some more detail what you want and I'll give it some thought?
I’m looking at a scenario where ICE is installed in a container or a VM and the user will start it for the first time. I want to be able to alter the default configuration that he would see when he opens the VIBE Launcher (Host is some remote rather than “localhost” and the execution path is also a bit different). Rather than having both ICE and VIBE live on the same machine, I’d like to separate them (much easier to build/update), run a SSH daemon on the VIBE side, and have ICE launch jobs remotely. Being able to configure the host is essential if I want to keep the user input minimum.
|
