Open Tianpingan opened 11 months ago
- I don’t see that the s3info-related RPC request uses your newly added storageclass parameter. What is its function?
- Is the storage class configured at the file system level or the fuse client level? I saw that the storageclass parameter was added to the rpc parameters of your s3info, but the persistent storage operation was not seen on the mds side. How to use it later? In addition, I see that there is also a configuration item analysis of this parameter. What is the relationship between the two?
- Our goal is to configure it at the file system level. Each file system configures the storage class it wants to use.
Q2&3 s3info is part of fsinfo in etcd
need set storageclass when createfs. maybe related changes
need set storageclass when createfs. maybe related changes
- tool
- createfs rpc
Got it. since the storage class is already part of S3info, so i decide to use the existing createfs rpc for tools, simply adding the storage class parameter.
need set storageclass when createfs. maybe related changes
- tool
- createfs rpc
i have updated the tool in createfs/src/tools and tools-v2 to support storage class
cicheck
cicheck
cicheck
cicheck
cicheck
cicheck
cicheck
cicheck
What problem does this PR solve?
Issue Number: #2783
Problem Summary:
What is changed and how it works?
What's Changed:
How it Works:
When creating a request, the configuration for storage class is encompassed within the PutObjectOptions, applied alongside both PutObject and PutObjectAsync methods. This allows us to employ PutObjectOptions to construct the S3 request, including the storage class information.
Side effects(Breaking backward compatibility? Performance regression?):
Check List