On 2024/3/19 20:57, 余润杰 wrote: > Thank you for your suggestion. > > For the first point, I will update this in the proposal with an exact goal > for each storage system type. For the second point, I assume this cache is > shared by all VMs running in the same host OS. > > Regarding cloud documents, I think this is a very good suggestion. Yes, I > need to create and maintain a cloud document. This is not only easy to > browse, but by updating and maintaining this document during the GSoC cycle, > it helps us focus on our goals and demonstrate the phased results of > development. > > For now, I will create a Google Docs tomorrow to display the content of the > existing proposal. > > Thanks again for your advice! > > Manjusaka <[email protected] <mailto:[email protected]>> 于2024年3月19日周二 > 17:48写道： > > On 2024/3/19 16:58, 余润杰 wrote: > > Hi, Xuanwo and Manjusaka. > > > > I hope this email didn’t bother you! > > > > Applications for GSoC 2024 contributors opened today, and I hope to > join the GSoC project in Apache OpenDAL as a candidate. I have added you to > the list of mentors for the ovfsproject proposal and hope to have the > opportunity to be mentored by you! > > > > /Project Mentors: Xuanwo ([email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>), Manjusaka > ([email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>)/ > > > > I have supplemented and modified some of the content based on previous > proposal, mainly including the following points: > > > > 1) Based on the discussion in the previous email, the name of the > project was changed from ovirtiofs to ovfs. > > > > 2) Added explanation of ovfs design philosophy. > > > > 3) Avoid ovfs persisting any metadata. > > > > 4) Added potential application scenarios. > > > > 5) Added project deliverables. > > > > 6) Added Why Me And Why Do I Wish To Take Part In GSoC 2024 section. > > > > I hope to submit the proposal this week. I'd like to know if there are > still areas that need to be revised or discussed before the proposal is > formally submitted. > > > > Have a nice day! > > Hi Runjie > > Glad to hear from you! > > Nice proposal! BTW maybe you can upload the document to a website like > Google Docs, Gist, so other people can preview the docs online(LOL > > Most LGTM about this version proposal, I may have some issues/suggestions > > 1. We can make our target to implement only one service backend for each > category of the service(like S3 for blob, HDFS for file like, KV storage is > not in the plan). This will help us to focus on the function, not the corner > behavior. > It would also can help us to reach the full-fuction tested target(I think > it's important for us) > > 2. About the cache, I would like to ask: Is the cache shared by all the > VM? or each VM would have their own cache > > > Thanks for your nice proposal, have a nice day > > Best > > Manjusaka >
Sorry, I forget something in the previous email About the cache, I have another suggestion. I think we should split it into two parts: the read cache and the write cache. The people can choose to enable the cache base on their circumstance For example, if the user mount a S3 bucket as backend which is modified in high frequency(modified by other serivce), the people shouldn't enable the read cache. I think this is would good for the production usage. Best Manjusaka
