Apache Ozone 2.0 release plan

[jojochuang]

Hi community,

I started a thread to initiate the 2.0 release plan in the mailing list, and I'd just like to copy the discussion over to GitHub disucssion so I can get a wider audience & feedbacks.

I've captured the comments and also reviewed recent feature developments in the JIRA, and took a stab at a release plan:
https://docs.google.com/document/d/1-OLE3IUKZH4zVsPVlUxwNho7MVuoBUwbAgbLMPzouMc/edit?usp=sharing

Let's say
Timeline:

• End of August: Draft release plan
• Mid-September: Scope freeze
• September 30: Code freeze and branching
• October 7-10: Release Candidate 0 (coinciding with Community Over Code NA)
• October 31: Release Candidate 1
• November 22: General Availability (before Thanksgiving week)

The payload of the release is documented at the scope doc: https://docs.google.com/document/d/19QG0fJb5YqvkezUnzV0cJH9VuI8lw4GYfTOyrGpk-Fg/edit?usp=sharing

In the newer release, we will be adding the following features or improvements

• HBase support
• Recon UI revamp
• Website v2
• JDK17 support
• Snapshot improvement

And deprecate or dropping the following features

• Drop/deprecate Hadoop2 support
• Deprecate legacy bucket type
• Remove STAND_ALONE replication type HDDS-6218
• Proto2 to Proto3 migration
• Deprecate o3fs
• Reject creating new LEGACY buckets

• Helm chart HDDS-11027 is a new feature coming out soon but is not part of the main Ozone binary.

Thoughts? Please feel free to comment/edit on the release plan and scope doc, or post the comments below.

[kerneltime]

If I understand correctly, we are not doing proto2 to proto3 migration ? or is it a deprecation of proto2?

[jojochuang]

I feel like we won't have enough bandwidth for it right now. We should deprecate it (not sure how)

[errose28]

Thanks for driving this Wei-Chiu.

• I don't think website v2 will be ready in time and should probably be removed from the scope.
• I think the concept of o3fs only exists on the client side. Can we simply replace that code with an error message that it is no longer supported in 2.x clients?
• I think we should aim to support downgrades from 2.x to 1.x, but not necessarily client/server cross compatibility. This depends on the effects of proto 3 migration though.

[ivandika3]

@jojochuang Thanks for drafting the release plan. I'm curious what changes makes this release a "Major" release (1.4.0 -> 2.0.0) instead of a "Minor" release (1.4.0 -> 1.5.0)? Is it because of the deprecation of features?

[errose28]

Yes this is the biggest reason. In the cases listed so far we should be able to do this with minimal disruption, even though they are technically breaking changes. I also don't think we are aiming to support 1.x <-> 2.x client server cross compatibility. Server side upgrade should be doable without manual migration steps like rewriting data though.

[ivandika3]

@errose28 Thanks for the info.

[errose28]

As discussed in this week's US community sync, we would like to add two more items to the 2.0 release plan:

• HDDS-11754: Drop support for non-Ratis OM and SCM
• HDDS-11753: Remove file per chunk layout from datanode code

Each Jira is open with more details so feel free to comment questions or concerns there.

[errose28]

Can we also remove the LegacyReplicationManager and associated code/configs as part of Ozone 2.0 @sodonnel @siddhantsangwan?

[sodonnel]

It would make sense to remove Legacy RM, as we don't plan to use it or update it any further. There is no point in carrying both versions going forward.

[adoroszlai]

Created HDDS-11759