Specify a "no_write" option for transfers between storages

[elliot-gould]

Hi Team,

Is there a way to specify a no write option when orchestrating transfers between 2 storage nodes?

We're currently initiating transfers as follows:

ascli node upload \
    "/path/to/src..." \
    --preset=preset_1 \
    --to-folder="/path/to/dest..." \
    --transfer=node \
    --transfer-info=@preset:preset_2 \
    --ts=@json:@file:transfer_spec.json 

Where transfer_spec.json contains like:

{
    "create_dir": true,
    "resume_policy": "full_csum",
    "cipher": "aes-128",
    "file_checksum": "md5",
    "target_rate_kbps": 1000000,
    "rate_policy": "fair",
    "precalculate_job_size": true
}

I've tried passing --transfer-info=@json:'{"ascp_args":["--no-write"]}' but this doesn't seem to have any effect, perhaps the ascp_args are only relevant when ascli is calling ascp locally?

[laurent-martin]

Correct.
https://github.com/IBM/aspera-cli

options passed on --transfer-info are specific to the agent specified in --transfer.

and yes, ascp_args is only valid for the direct (default) agent, which spawns directly ascp, and so has the capabilitity to add this special argument.

When using the node agent, the only available transfer parameters (eventually used to start ascp, and so the transfer), are the ones in the node api: POST /ops/transfers

https://developer.ibm.com/apis/catalog/aspera--aspera-node-api/api/API--aspera--ibm-aspera-node-api#post-1331613487

Note that the --no-write option is for test only, as it prevents writing on destination, e.g. to test bandwidth.