¶ Description
Upload files to a container in an Cloud Object Blob Storage.
¶ Parameters
¶ Parameters tab
Parameters:
- File to upload
- Optional: filename on remote server
- Segment size (MB)
- Store large file segments in separate container (containerName_segments)
- Container URL
- Login/user
- Password
- tenant name
- Debug Level Information
- Optional: extra parameters for cURL
- Number of retries on connection error
- Error Management
¶ Description tab
Parameters:
- Script name
- Short description
- Revision
- Decription
¶ Configuration tab
See dedicated page for more information.
¶ About
ostUpload uploads a local file into an OpenStack Swift–compatible object storage container.
It supports single-part uploads for small files and segmented (large object) uploads for big files using a configurable segment size (MB). When segmentation is enabled, the action creates a manifest object and pushes the data in fixed-size segments; optionally, segments can be stored in a separate “_segments” container.
The action authenticates to Swift with your user / password / tenant (project) and targets a Container URL you provide.
¶ Where it works (clouds & endpoints)
Use ostUpload with any storage that exposes the OpenStack Swift API (Keystone-authenticated or pre-scoped storage URLs), including but not limited to:
- OVHcloud Object Storage (Public Cloud)
- Cleura / City Cloud Object Storage
- Selectel, Scaleway Elements (Swift API), Aruba Cloud, and most OpenStack providers
- Self-hosted OpenStack Swift clusters
- Ceph RADOS Gateway when the Swift API is enabled
Tip: If you’re unsure of your Container URL, run the companion actions
ostListContainersorostListFilesto navigate and copy the correct endpoint.
¶ Minimal setup (quick start)
-
Pick the file to upload
InFile to upload, select the local file. -
Target container
Paste the Container URL (for example,https://<swift-endpoint>/v1/AUTH_<project>/<container>). -
Credentials
FilluserName,Password, andtenantName(your OpenStack project/tenant).
If your environment uses application credentials or tokens, put them in the appropriate secure fields (thePasswordfield is secret-aware). -
(Optional) Remote name
SetOptional: filename on remote serverif you want the object stored under a different name than the local filename. -
Run
Click Preview/Run. The process log shows progress and the resulting status.
This is sufficient for small and medium files. For very large files, adjust Segment size and (optionally) enable Store segments in a separate container.
¶ How it works (under the hood)
-
Authentication & target resolution
The action validates the Container URL and authenticates against the Swift endpoint using your credentials and tenant. -
Upload strategy selection
- If the file size is ≤
Segment size(MB): a single PUT is performed. - If the file size is >
Segment size (MB): the file is split into segments ofSegment size (MB)and uploaded as a Static Large Object (SLO). A manifest object is created at the final path that virtually concatenates the segments.
- If the file size is ≤
-
Segment placement
- If
Store large file segments in separate container (containerName_segments)= ON: segments go to a companion container named<container>_segments. - If OFF: segments are stored in the same target container under an internal prefix.
- If
-
Retries & error policy
Transient network failures are retried up toNumber of retries on connection errortimes. Final behavior depends on Error Management: abort the pipeline or continue with an ERROR status. -
Result
The target object is available immediately in Swift; you can verify withostListFilesor any Swift client.
¶ Operational guidance & best practices
-
Choosing
Segment size (MB)- 50–100 MB works well for most networks.
- Large segments reduce manifest size but can be harder to retry; small segments increase API calls.
-
Segments container hygiene
IfStore large file segments in separate container (containerName_segments)is ON, you’ll see a<container>_segmentscontainer appear. Do not delete segment objects unless you also remove or re-write the manifest object. -
Credentials & security
KeepPasswordin secure storage (parameter vault). Restrict logs tobasicunless you actively troubleshoot. -
Performance tips
- Reliable networks: you can increase
Segment size (MB)to reduce calls. - Unstable networks: keep
Segment size (MB)moderate and increaseNumber of retries on connection error.
- Reliable networks: you can increase
-
Verifying uploads
After the run, useostListFiles(or a Swift client) to confirm the object and its size. For large objects, listing segments/manifest is visible in detailed views. -
Common errors
- 401/403: wrong credentials/tenant or insufficient rights on the container.
- 404 container: Container URL misspelled or you lack access.
- 413/Request Entity Too Large: endpoint policy limits; reduce
Segment size (MB). - Timeouts: raise
Number of retries on connection erroror add cURL options inOptional: extra parameters for cURL(e.g., connect/read timeouts).
¶ Typical workflow with the Swift boxes
- Discover containers with
ostListContainers. - Upload content with
ostUpload. - List/Verify uploaded files with
ostListFiles. - (Optional) Download/Delete using
ostDownload/ostDelete.
This trio covers the full lifecycle of objects in OpenStack Swift directly from your pipeline.
