I. Node to Node Transfers with a Cluster Setup

The following examples give step-by-step procedures for setting up and executing transfers with a cluster setup.

Cluster-to-cluster, with access key as token

  1. Create a remote access key on cluster 2: call is authenticated using the Node API user (user1).
  2. Generate the basic token using the remote access key generated for cluster 2.
  3. Create a local access key for cluster 1: this one will be used to authenticate the HTTP request /ops/transfer in order to submit the transfer.
  4. Create a transfer on cluster 1 -- the remote destination root and remote user are already encoded in the remote access key as /home/xfer/test, and then in the basic token.
    
    

Cluster-to-cluster, with authorization token

  1. Create remote access key for cluster 2 : call is authenticated using Node API user.
  2. Create a token using /files/upload_setup on cluster 2; request is authenticated using the access key generated in the first step.
  3. Create local access key on cluster 1. This key is used to authenticate the HTTP request /ops/transfers for submitting the transfer.
  4. Create a transfer on cluster 1. The remote destination root and remote user are already encoded in the remote access key as /home/xfer/test and in the basic token; elements for the JSON request bodey for the transfer are taken from the /files/*_setup response.

Cluster-to-non-cluster Enterprise Server, uploading from Enterprise Server to cluster

In the example below, the following is true:

  • Transfer user configured for token (SSH key + token encryption key in aspera.conf)
  • Configuration file sshd_conf sets parameters to allow SSH connection on port 33001
  1. Create remote access key on the cluster.
  2. Create a token using /files/upload_setup on the regular Enterprise Server.
  3. Create a transfer on the cluster (elements for the transfer JSON are taken from the /files/*_setup response)


II. Monitoring Transfers


Get All Transfers

  • Authenticationing Node API user or access key:
  • Authentication with user or access key:

The GET /ops/transfers and /ops/transfers/{ID} return a link in the header which contains an iteration token. The iteration token can be used in the next query as shown in the following section.


  

Get Transfers with an Iteration Token

Authentication with a Node API user or access key. For every call a link is returned in its header which may be used to make the next query.


 	
Video player

Video

×