greenwich commented on PR #6989: URL: https://github.com/apache/ozone/pull/6989#issuecomment-3947561978
@errose28 Thanks for looking! I am very sorry for the noise my PR caused; it wasn't intended to be public (My bad - I haven't set it to Draft when I created it). Let me explain my motivation. 1. My team **needs** a storage policy and tiering support for Ozone. Unfortunately, reality is tough, and if we don't have it this year (ideally H1), then the Ozone might be deprioritised because we use other Ozone competitors in the company. 2. The patch attached to this pull request doesn't seem to be up to date with the master or even 2.0 or 2.1 releases. 3. As I can see, there has been no work on this PR since Nov 2025. 4. Plus, I might be wrong, but I got an impression that we want a perfect design and implementation here before we start coding. 5. My approach is different - I want to design and build it **incrementally** because that's the simplest way to adopt it in my team, start using it and collect the feedback from others. So - I analysed the current state, reviewed the contents of the patch in this pull request, and created a small roadmap of the features I want in storage tiering. - I prioritised them and split them into small releases. I called them MVP-1, MVP-2, etc. Each MVP should take me around 1 week to implement. - Each MVP should have a complete set of features that work e2e. At the moment, I work on MVP-1. - I planned to test MVPs on our PROD environment, and if it works as expected, then go back to the Ozone community and share what I have. 6. As I haven't created any Jira tickets because I thought of implementing and testing my MVP first. However, each independent feature is pushed as a separate commit, so it might later be retrofitted into different ASF jira tickeets (if needed). 7. The last thing, using Apache Ozone's PR feature is very useful for me because it triggers the whole CI and whatnot and allows seeing diff with the master to make my branch in sync. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
