Containerize IPFS - Githubissues

rh-impact / pnt-hackathon-2022

4 stars 0 forks source link

Containerize IPFS #2

Open computate opened 2 years ago

computate commented 2 years ago

https://ipfs.io/

enp0s3 commented 1 year ago

@computate Hi! I am a little bit confused with regards to containerize the IPFS binary. IIUC the IPFS is a distributed decentralized file system service. It's P2P design assumes the peers/nodes in the IPFS cluster are persistent rather than ephemeral. From my POV it doesn't fall into the ChRIS cookiecutter pattern, since the IPFS binary needs to run either as a daemon, or it should be utilized via the IPFS library using some RPCs against the IPFS nodes.

Maybe its should be implemented on the infrastructure level (like for example an alternative to Swift in tOpenshift )

Can you please advice? TIA Igor

enp0s3 commented 1 year ago

Maybe we can suggest using IPFS as an experimental data store that will reside on the MOC, and it may optimize the time it take to access some data from different reigns in the MOC.

enp0s3 commented 1 year ago

@computate Maybe we can do something similar to pfioh, it can be a dockerized ephemeral service for file transfer, it will be transferred to an IPFS network that resides on the MOC

computate commented 1 year ago

Hi @enp0s3 , so you are referring to the Massachusetts Open Cloud? I'm working on that too! That would be a great place to demo this. That's great if it is already similar to pfioh. I think you are on the right track regarding being an infrastructure level task to deploy to OpenShift/Kubernetes. Sorry if that threw you off during the hackathon, not fitting into the typical mold of a ChRIS plugin. Thanks for your contributions!

rudolphpienaar commented 1 year ago

Hi all --

Great work getting started on this. AFAICT the repo in the rh-impact org is nothing more than the stub created by the cookiecutter. Is this correct?

A couple of comments.

The idea of an ipfs plugin is simply a plugin (or "app") that is able to "pull" from some ipfs node. It is not meant to participate in an ipfs network or advertise its contents to an ipfs network. See here.

Also, pfioh is a legacy service/component that is no longer used in workflows. Having said that, it could be useful in its own right.

Let me know if this makes sense (or further muddies the waters)!