search

Joystream / storage-node-joystream

Colossus - Storage node for Joystream
GNU General Public License v3.0
4 stars 7 forks source link

Use a Dockerfile approach for building and configuring nodes #67

Open jfinkhaeuser opened 5 years ago

jfinkhaeuser commented 5 years ago
  1. Storage nodes are also full substrate nodes.
  2. Need to configure storage nodes with regards to staking for roles/tranches.
  3. Must include Let's Encrypt proxy
    • Optionally own SSL certs
  4. Must also include a go-ipfs node.

This will be based on the effort in #61

mnaamani commented 5 years ago

I think docker-compose will make it easy to orchestrate multiple services that make up the storage node

jfinkhaeuser commented 5 years ago

I'm not a big fan of it, personally - I used it in the past, and it turned out to be very hard to use compared to other systems.

I'm inclined to instead provide ansible scripts for each component, and use a Dockerfile that runs a playbook putting them together.

mnaamani commented 5 years ago

Sure I don’t have strong opinion on this, I only suggested it because you are recommending docker.

It will be interesting to see ansible in action.

On Thu, May 16, 2019 at 7:55 PM Jens Finkhaeuser notifications@github.com wrote:

I'm not a big fan of it, personally - I used it in the past, and it turned out to be very hard to use compared to other systems.

I'm inclined to instead provide ansible https://www.ansible.com/ scripts for each component, and use a Dockerfile that runs a playbook putting them together.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Joystream/storage-node-joystream/issues/67?email_source=notifications&email_token=AAMLYFBUXO7HEL3TEOOCNCLPVWGZ5A5CNFSM4HMBYZA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVSNTEA#issuecomment-493148560, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMLYFCZ5SMRYOMNG3KXLOLPVWGZ5ANCNFSM4HMBYZAQ .

jfinkhaeuser commented 5 years ago

Well, docker seems to be what people want to use. And for running a single image it's good.

docker-compose orchestrates multiple images, which I guess is good if you need the isolation between them. I'm not sure that's a strong requirement for us - at least not for now. So if we provide a Dockerfile for running everything in one image, but each service is configured with its own ansible script, I think we leave the door open for someone to docker-compose it all, but we also have a quick start for anyone wanting to join.