Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.9.2
-
None
Description
Work in progress
As of now
- YADE can transfer files from Source/Target (via Jump host) over Proxies.
- Proxy can be;
- Source proxy
- Target proxy
- Jump proxy
- All the proxies are considered e.g. source/target/jump from point of view of YADE Client.
- When YADE transfers files from source to target via proxies JADE profile has settings e.g.
- for operation copytointernet
- Source-settings
- Jump-proxy-settings
- Jump-Host-settings
- Target-settings
- for operation copyfrominternet
- Source-settings
- Jump-Host-settings
- target-proxy-settings
- Target-settings
- for operation copytointernet
- For YADE Client proxy to connect with Jumphost should always be the Jumproxy
- Please see the diagram
Profile
[copyfrominternet] file_spec = .*\.txt$ operation = copyfrominternet ;; target_dir = c:\sandbox\target target_host = localhost target_protocol = local ;; jump_proxy_host = homer.sos jump_proxy_user = sos jump_proxy_password = sos jump_proxy_port = 1080 jump_proxy_protocol = socks5 ;; jump_host = uk.sos-berlin.com jump_protocol = sftp jump_port = 22 jump_user = london jump_ssh_auth_method = publickey jump_ssh_auth_file = /home/sos/.ssh/id_rsalondon jump_command = /home/london/sos-berlin.com/jade_client/jade_snapshots/jade_client.1.9.3-SNAPSHOT/bin/jade.sh ;; source_dir = /home/tokyo/data/from_tokyo source_host = japan.sos-berlin.com source_protocol = sftp source_port = 22 source_user = tokyo source_ssh_auth_method = publickey source_ssh_auth_file = /home/london/.ssh/id_rsatokyo
Session Log
- See the attached file jade-322.log
Desired Behavior
- YADE should accept jump-proxy for both the operations e.g. copytointernet and copyfrominternet
