¶ 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
InidFile, select the local file. -
Target container
Paste the Container URL (for example,https://<swift-endpoint>/v1/AUTH_<project>/<container>). -
Credentials
FilluserName,pw, andtenantName(your OpenStack project/tenant).
If your environment uses application credentials or tokens, put them in the appropriate secure fields (thepwfield is secret-aware). -
(Optional) Remote name
SetidFileRemoteif 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 ≤
chunkSz(MB): a single PUT is performed. - If the file size is >
chunkSz: the file is split into segments ofchunkSzMB 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
storeSeparate= 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 tonRetrytimes. 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.
¶ Parameters (field-by-field)
| Id | Description | Notes |
|---|---|---|
| idFile | File to upload | Opens a file picker for a local file. |
| idFileRemote | Optional object name on the remote side | Leave blank to keep the local filename. |
| chunkSz | Segment size (MB) | Default 50 MB. Controls segment length for large-object uploads. |
| storeSeparate | Store large file segments in a separate container (<container>_segments) |
OFF = segments in same container under a reserved prefix. |
| containerURL | Container URL | Full Swift container path (e.g., …/v1/AUTH_<project>/<container>). |
| userName | Login / user | OpenStack user (or application credential ID if used). |
| pw | Password | Secret field. Supports tokens/app creds depending on your setup. |
| tenantName | Tenant (Project) name | Use the exact Keystone project/tenant name. |
| idDebug | Debug information level: nothing | basic | verbose |
Higher levels print cURL/HTTP traces in logs. |
| idOptional | Optional extra parameters for cURL | Advanced: pass flags like timeouts, proxies, etc. |
| nRetry | Number of retries on connection error | Default 10. Applies to network failures/timeouts. |
| idErrorManagement | Error policy: abort pipeline execution with error | continue with status ERROR |
Choose how the pipeline reacts on final failure. |
¶ Operational guidance & best practices
-
Choosing
chunkSz- 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
IfstoreSeparateis 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
Keeppwin secure storage (parameter vault). Restrict logs tobasicunless you actively troubleshoot. -
Performance tips
- Reliable networks: you can increase
chunkSzto reduce calls. - Unstable networks: keep
chunkSzmoderate and increasenRetry.
- 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
chunkSz. - Timeouts: raise
nRetryor add cURL options inidOptional(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.
