Repository navigation
Documentation for iowarp(#968) CLIO-S3 benchmark - #22
Open
eDoggo3779 wants to merge 3 commits into
Open
eDoggo3779 wants to merge 3 commits into
eDoggo3779 wants to merge 3 commits into
Conversation
Covers the user-facing configuration surface of iowarp/clio-core#1093 (CLIO-S3 benchmark): the Poco+SigV4 S3 bdev, s3/gcs as CTE storage-tier types, the CAE S3 importer's in-process credential resolution, the cloud environment variables (AWS_*, S3_*, GCS_*), and CLIO_STRICT_RESPONSE_IDENTITY. Adds a dedicated S3 connector page modelled on the Globus one, and fixes the CTE storage-device-type list, which named types that do not exist. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Fold the s3/gcs compose examples into the existing clio_bdev block and drop the separate cloud-bdev section (behavior, bucket creation, build requirements); retarget its links. - Describe hbm/pinned/noop in the bdev_type row. - Drop the cloud-tier paragraph; keep the key-prefix caution. - State why credentials are env-only in two places (CTE storage tiers, CAE S3 page) and remove the other repetitions. - Revert the env-var prefix note; shorten CLIO_STRICT_RESPONSE_IDENTITY; remove the cloud-object-stores preamble. - hpc-cluster: table instead of prose for cloud credentials. - CAE overview/omni: cut factory internals and credential notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eDoggo3779
marked this pull request as ready for review
October 8, 2026 03:40
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the configuration surface added by iowarp/clio-core#1093 (CLIO-S3 benchmark, merge commit 183ab948): S3/GCS cloud block devices and CTE storage tiers, the CAE S3 importer, and a new client env var.
Changes
sdk/context-assimilation-engine/s3.md. The CAE S3 connector, laid out like the Globus page:CAE_ENABLE_S3, spack+s3_cae, renamed from+s3)S3_ENDPOINTcae_s3_toolhelperdeployment/configuration.mdbdev_typenow listss3,gcs,hbm,pinnedandnoop, and the bdev compose example gains commented-out S3/GCS entries.path/bdev_type, an S3 tier in the YAML example, and two cautions (always use a key prefix; credentials come only from the runtime's environment).AWS_*/S3_*/GCS_*variable and which component reads it.CLIO_STRICT_RESPONSE_IDENTITY.deployment/hpc-cluster.md: cloud credential variables table.overview.md/omni.md:s3://andgs://in the factory table and the OMNI examplesAssimilationCtxfieldss3_region/s3_profileCAE_ENABLE_S3/CAE_ENABLE_GCSbuild optionscontext-runtime/.../bdev.md:kS3/kGcsbackends, thepool_nameformat, and when to use a cloud backend.context-transfer-engine/cte.md: the storage-type list nameddev_daxandposix, which the config parser has never accepted. It now matches the validator (core_config.cc) and its test (test_cte_config_errors.cc):file,ram,hbm,pinned,noop,s3,gcs.Notes
context-runtime/config/clio_default.yamlin clio-core is not updated, so the "Shipped Default" copy in these docs is left unchanged to keep the two identical.clio-fs-durability-docsbranch edits the sameconfiguration.mdtables, so whichever of the two merges second may hit conflicts.npm run build) with no broken links or anchors.