Skip to content
Snippets Groups Projects
Commit 37dc5ecb authored by Jedrzej Rybicki's avatar Jedrzej Rybicki
Browse files

api requests for image transfer

parent 4e3c871b
No related branches found
No related tags found
No related merge requests found
Pipeline #96048 passed
...@@ -112,6 +112,18 @@ curl -X POST -u USER:PASS -H "Content-Type: application/json" \ ...@@ -112,6 +112,18 @@ curl -X POST -u USER:PASS -H "Content-Type: application/json" \
---- ----
=== Image transfer example ===
To transfer images from eFlows4HPC image build service use dag defined in +dags/image_transfer.py+ (transfer_image). It requires two parameters +image_id+ name of the image in the image
build service (e.g. "wordcount_skylake.sif") and +target+ which defines a path on the system where the image will be transfered to.
The parameters should be passed along the credentials as described in <<credentials>>. The target directory will be created with ``mkdir -p`` on the target machine. The image is streamed directly to the target location (no local copy on DLS worker).
----
curl -X POST -u USER:PASS -H "Content-Type: application/json" \
--data '{"conf": {"image_id": imageID, "target": PATH}}' \
$DLS/dags/transfer_image/dagRuns
----
=== Comments === === Comments ===
I could image that a name of DLS pipeline (+taskflow_example+) can change and needs to be passed as parameter to YORC. I could image that a name of DLS pipeline (+taskflow_example+) can change and needs to be passed as parameter to YORC.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment