Thank you for your suggestion. Yes, I also think it will be necessary to include code submission into the opendal PR process as early as possible. I will start this process after building the MVP.
On Sun, May 19, 2024 at 8:28 PM Xuanwo <[email protected]> wrote: > It's up to zjregee to decide; I'm willing to help review and set up the > necessary infrastructure. > > On Sun, May 19, 2024, at 20:25, Manjusaka wrote: > > Maybe we can start a PR process to opendal repo after a MVP process > > about S3 read and write? > > > > On 2024/5/19 20:18, Xuanwo wrote: > >> Bravo work! > >> > >> Here are some ideas after reviewing the progress. I hope you find them > helpful. > >> > >> - It's better to integrate into the opendal repo early so our community > can participate from the start. Merging a big project into opendal at the > end of this program could be challenging. > >> - I suggest developing ovfs by targeting S3 to better align with most > of OpenDAL's behavior. > >> - I suggest building an MVP that allows us to read from and write data > into S3 using OVFS, rather than focusing on edge cases like metadata > handling or readdir. > >> > >> On Sun, May 19, 2024, at 18:12, Manjusaka wrote: > >>> On 2024/5/19 下午3:43, Runjie Yu wrote: > >>>> ### Overview for Week 1 05.12-05.19 > >>>> Since the basic framework of ovfs is difficult to express with little > code, > >>>> we plan to do some local development under [this repository]( > >>>> https://github.com/zjregee/ovfs) first. > >>>> > >>>> The implementation of virtiofsd includes a built-in small file system > (used > >>>> to forward requests to the local file system) and a lot of code that > >>>> encapsulates the small file system into virtiofs. From a simple > reading, > >>>> the implementation of these two parts, virtiofsd, is relatively > decoupled > >>>> and defines some common data structures and traits. > >>>> > >>>> Regarding the first goal for now, we current plan is to re-implement > the > >>>> small file system built into virtiofsd through opendal and re-use the > >>>> encapsulation code of virtiofsd to try to run it, and then continue to > >>>> delete unnecessary code to make a minimum version of ovfs. > >>>> > >>>> #### Task List > >>>> - [x] Add file system related functions based on opendal, such as > mkdir, > >>>> rmdir, create, read, write, etc. > >>>> - [x] Implement `FileSystem` trait defined by vritiofsd for ovfs. > >>>> - [x] Implement `FileReadWriteAtVolatile` trait for opendal buffer to > >>>> support read and write interaction with the memory in VMs through > opendal > >>>> buffer. > >>>> > >>>> #### Plan For Near Future > >>>> - [ ] Run virtiofsd. > >>>> - [ ] Replace the file system implementation in virtiofsd with ovfs > and try > >>>> to re-run virtiofsd. > >>>> > >>>> Potential completion time: 05.26. > >>>> > >>> > >>> Good Job! Feel free to ask in the maillist/channel when you get some > problems > >>> > >>> Best > >>> > >>> Manjusaka > >> > > -- > Xuanwo >
