[
https://issues.apache.org/jira/browse/HDDS-17533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devesh Kumar Singh updated HDDS-17533:
--------------------------------------
Description:
Inspect forward/reverse S3 class mapping and all relevant S3G operations (PUT,
Copy, MPU, HEAD), determine which classes require new policy semantics, and
guard only those until OM capability is enabled. Avoid regressing old S3 class
behavior.
*Reason:* S3G may translate an S3 header into new OM metadata and must never
claim unsupported placement.
*Acceptance criteria:* New policy requests fail safely on old OM; existing S3
behavior works; classes and metadata consistent through failover/MPU
completion; mapping tests provided.
Reference JIRA: [HDDS-16039|https://issues.apache.org/jira/browse/HDDS-16039]
was:
Trace S3StorageClassResolver and all actual S3 operation callers for
class-to-policy mapping, EC layout selection, class reporting, bucket defaults,
PUT, copy, MPU initiation/completion and HEAD/GET metadata. Check OM capability
whenever a request invokes new policy semantics. Preserve supported legacy
storage-class behavior before finalization; reject newly unhonorable explicit
intent rather than silently substituting default placement. Define expected
error mapping for S3 clients.
*Why:* S3G is a protocol-facing client of OM and must not claim an S3 class was
honored when the backend cannot enforce its Ozone policy. S3G gating does not
replace OM/SCM/DN enforcement.
*Acceptance criteria:* Forward/reverse class outcomes verified; old-OM and
failover handling covered; PUT/Copy/MPU consistent; invalid enum safe; HEAD/GET
reporting matches actual semantics.
Reference JIRA: [HDDS-16039|https://issues.apache.org/jira/browse/HDDS-16039]
Summary: Preserve S3 storage-class semantics through OM finalization
(was: Gate S3 storage-class mapping and PUT/Copy/MPU operations by OM
capability)
> Preserve S3 storage-class semantics through OM finalization
> -----------------------------------------------------------
>
> Key: HDDS-17533
> URL: https://issues.apache.org/jira/browse/HDDS-17533
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Client, Ozone Filesystem
> Reporter: Devesh Kumar Singh
> Priority: Major
>
> Inspect forward/reverse S3 class mapping and all relevant S3G operations
> (PUT, Copy, MPU, HEAD), determine which classes require new policy semantics,
> and guard only those until OM capability is enabled. Avoid regressing old S3
> class behavior.
> *Reason:* S3G may translate an S3 header into new OM metadata and must never
> claim unsupported placement.
> *Acceptance criteria:* New policy requests fail safely on old OM; existing S3
> behavior works; classes and metadata consistent through failover/MPU
> completion; mapping tests provided.
> Reference JIRA: [HDDS-16039|https://issues.apache.org/jira/browse/HDDS-16039]
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
