Skip to content
Snippets Groups Projects
  1. Feb 25, 2015
  2. Feb 14, 2015
  3. Feb 13, 2015
  4. Feb 09, 2015
  5. Jan 27, 2015
  6. Nov 20, 2014
  7. Nov 17, 2014
  8. Nov 12, 2014
  9. Nov 11, 2014
  10. Nov 10, 2014
  11. Oct 30, 2014
  12. Oct 25, 2014
  13. Oct 24, 2014
  14. Oct 18, 2014
  15. Oct 16, 2014
    • Eric Rasche's avatar
      Docs update · 1cd30520
      Eric Rasche authored
      1cd30520
    • Eric Rasche's avatar
      Merge branch 'generic_ssh' into rsync · 29c4fb3f
      Eric Rasche authored
      29c4fb3f
    • Eric Rasche's avatar
      SCP Transport Implemented · f0be5318
      Eric Rasche authored
      Galaxy file_actions.yaml:
      
          paths:
              - path: /home/vagrant/
                action: remote_scp_transfer
      
      Behaves identically to rsync
      f0be5318
    • Eric Rasche's avatar
      9079c7de
    • Eric Rasche's avatar
      SSH Transport Implemented · 961006d7
      Eric Rasche authored
      Provides the file action "remote_rsync_transfer". This currently
      *requires* you to use a `file_action_config` on the Galaxy side, as
      extra configuration is required.
      
      Galaxy job_conf.xml:
      
          <destination ...>
              <param id="file_action_config">file_actions.yaml</param>
      
      Galaxy file_actions.yaml:
      
          paths:
              - path: /home/vagrant/
                action: remote_rsync_transfer
                ssh_user: vagrant
                ssh_host: my.fqdn
                ssh_port: 2222
                ssh_key: |
                  -----BEGIN RSA PRIVATE KEY-----
                  MIIEowIBAAKCAQEAwWYGEOhiJgbWv8eBV2LJp0MCSgrAPeX9FbsGn1I+UC110PPW
      
      This passes configuration information in every message to Pulsar. While
      suboptimal in terms of message size (ssh key is ~3x the size of a normal
      message), it opens the door to multiple galaxies connecting to a single pulsar,
      still using rsync. Additionally it lets the Galaxy admin reconfigure the SSH
      parameters without any interaction on the Pulsar admin's part (with the
      exception of `ssh_key`, as of now). This will be very beneficial if the two
      groups do not have a close working relationship.
      961006d7
  16. Oct 15, 2014
Loading