2019-10-07 Meeting notes

• RC0 is out, please vote when you get a chance.

• We discussed the interface renaming and refactoring issue at great depth. 
• Please see the link to understand the decisions made, we will file JIRAs based on these
• We can continue discussion in JIRAs, where more finer feedback will be possible.

We discussed the proposal from Sanjay in depth. There are few things that Clay mentioned.

He likes the like losing the bucket and volume for the following reasons.

1. If the system is purely DNS driven,  and not config driven, then creates a dependency that deployments need Dynamic DNS.
2. His more important point was that this makes write code against FileSystem object much easier. You can create one FileSystem object and write into any bucket. That is a huge  win from the programming perspective.
3. Xiaoyu asked if we are planning to support the .trash feature with OzoneFS at all? We think it is simpler and easier to have a server side delete policy under Ozone.
4. pifta wanted to make sure that Hive and other applications can work correctly.
5. He pointed out that one of the issues is that user will get an error if they try to write a file right under the volume.
6. Clay pointed out that it might be a "good" feature to have for a file system with Ozone's scale. The fact that you cannot write to a volume should make managing the FS easier.

Clay wanted to bring in FailSafe like API into Ratis. We discussed how Ozone handles failures when a Ratis pipeline hangs. Ozone just discards those pipelines, and open up other pipelines in the cluster. But we would like to have failsafe like API.