The 0-fs need to support the 0-stor cluster as storage backend.
A new implementation of the Storage interface as to be implemented.
It will use the 0-stor client API to talk to the 0-stor cluster of the 0-hub.
As describe in https://github.com/zero-os/0-hub/issues/29#issuecomment-353952336, the flist format will be modified a bit to support all the information for 0-stor backend.
The storage implementation will need to rebuild a 0-stor metadata object from the flist and use it in the Read call of the 0-stor client.
0-fs will need to keep support for ardb backend.
So based on the url scheme of the data backend, 0-fs will know which storage implementation to use to get to the files data.
zaibon
commented
6 years ago
Issue migrated from [https://api.github.com/repos/zero-os/0-fs/issues/22](), opened by @zaibon
This is related to https://github.com/zero-os/0-hub/issues/29#issuecomment-353952336. As describe in the issue, the 0-hub will change its backend from ardb to 0-stor cluster.
The 0-fs need to support the 0-stor cluster as storage backend. A new implementation of the Storage interface as to be implemented. It will use the 0-stor client API to talk to the 0-stor cluster of the 0-hub. As describe in https://github.com/zero-os/0-hub/issues/29#issuecomment-353952336, the flist format will be modified a bit to support all the information for 0-stor backend. The storage implementation will need to rebuild a 0-stor metadata object from the flist and use it in the Read call of the 0-stor client.
0-fs will need to keep support for ardb backend. So based on the url scheme of the data backend, 0-fs will know which storage implementation to use to get to the files data.