[HDDS-6390] Facilities for compatibility - umbrella jira

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.0
• Target Version/s: 1.5.0
• Assignee: István Fajth
• Reporter: István Fajth
• Created: 01/Mar/22 13:07
• Updated: 16/Dec/23 23:43

Description

Currently in Ozone we have different ways of handling certain compatibility problems, the main aim of this ticket to gather all the different issues/tasks in this area.

Attached a document about the current problems, and a forward looking proposal to this JIRA that describes the problem and the plans to resolve these problems. The scope might change over time though.
As there are problems that are covered by certain other feature's sub-tasks, some of the tickets belong to here will remain sub-tasks of other features, and are just linked in here. Versioning of client-server communication in Ozone.pdf

Issue Links

• is a parent of: HDDS-6223 Ozone 1.1.0 client listKeys on FSO bucket returns empty list
• is a parent of: HDDS-5909 EC: Onboard EC into upgrade framework
• is a parent of: HDDS-6182 General Purpose Client Versioning
• is a parent of: HDDS-6209 EC: [Forward compatibility issue] New client to older server could fail due to the unavailability for client default replication config
• is a parent of: HDDS-6213 Pluggable OzoneManager request handling hooks
• is a parent of: HDDS-6040 [FSO] Support upgrade for the bucket layout
• is required by: HDDS-3816 Erasure Coding

Sub-Tasks

• ClientVersions and DatanodeVersions class to define an enum with version and description: Resolved
• Introduce OzoneManagerVersion enum: Resolved
• Minor perf optimization in the version enums: Resolved
• Change the OzoneManager ServiceInfo message to carry the int version from OzoneManagerVersions: Resolved
• Add a guideline on how to deal with compatibility problems in components: Open
• Fix Xcompat tests, after 1.3.0: Open
• Support for serialized pre-process validators: Open