kosmos/chef
kosmos/chef
8
3
Fork 0
Code Issues 29 Pull Requests 2 Projects 2 Activity

Add initial instructions for joining the IPFS cluster #50

Merged
raucao merged 2 commits from doc/4-join_ipfs_cluster into master 2019-07-02 11:41:59 +00:00
Conversation 6 Commits 2 Files Changed 1 +53
greg commented 2019-04-30 15:19:22 +00:00
Owner
Copy Link

Refs #4

Refs #4
greg commented 2019-04-30 15:43:41 +00:00
Author
Owner
Copy Link

Now I'm figuring out how to pin the documents on a new peer that joined the cluster (just tried it on barnard, it didn't get the pins from the cluster)

Now I'm figuring out how to pin the documents on a new peer that joined the cluster (just tried it on barnard, it didn't get the pins from the cluster)
greg changed title from Add initial instructions for joining the IPFS cluster to WIP: Add initial instructions for joining the IPFS cluster 2019-04-30 15:43:48 +00:00
greg commented 2019-04-30 16:01:42 +00:00
Author
Owner
Copy Link

Something was missing, the documents were not pinned for the cluster, only for the ipfs daemon. I have pinned the contributors again through the cluster (ipfs-cluster-ctl pin add $CID) and now barnard has the contributors docs pinned and ipfs-cluster-ctl pin ls on all peers confirms it. Now doing the same for contributions

Something was missing, the documents were not pinned for the cluster, only for the ipfs daemon. I have pinned the contributors again through the cluster (`ipfs-cluster-ctl pin add $CID`) and now barnard has the contributors docs pinned and `ipfs-cluster-ctl pin ls` on all peers confirms it. Now doing the same for contributions
raucao commented 2019-04-30 16:12:07 +00:00
Owner
Copy Link

So #49 wasn't actually complete?

So https://gitea.kosmos.org/kosmos/chef/pulls/49 wasn't actually complete?
greg commented 2019-04-30 16:45:15 +00:00
Author
Owner
Copy Link

I thought it was complete, but since the ipfs-cluster-ctl pin ls returned nothing on the previous version of the cluster I couldn't see there was an issue with the pins in the cluster. The documents were pinned in the ipfs daemons on both dev and andromeda, but not on the cluster. Our cluster now includes the 41 documents from kredits.kosmos.org (5 contributors and 36 contributions) as pins, so new peers should get them automatically now

I thought it was complete, but since the `ipfs-cluster-ctl pin ls` returned nothing on the previous version of the cluster I couldn't see there was an issue with the pins in the cluster. The documents were pinned in the ipfs daemons on both dev and andromeda, but not on the cluster. Our cluster now includes the 41 documents from kredits.kosmos.org (5 contributors and 36 contributions) as pins, so new peers should get them automatically now
greg changed title from WIP: Add initial instructions for joining the IPFS cluster to Add initial instructions for joining the IPFS cluster 2019-04-30 16:45:29 +00:00
raucao reviewed 2019-05-01 12:09:44 +00:00
raucao left a comment
Owner
Copy Link

Nice!

Nice!
doc/ipfs_cluster.md
@ -0,0 +14,4 @@
WARNING: The encrypted_data_bag_secret option defined in knife.rb was overriden by the command line.
id: ipfs_cluster
secret: *SECRET*
```
raucao commented 2019-05-01 12:08:14 +00:00
Owner
Copy Link

This is seems like a huge first step for merely acquiring the secret. If the person doesn't use Chef, then why make them install Ruby and Chef and everything?

This is seems like a huge first step for merely acquiring the secret. If the person doesn't use Chef, then why make them install Ruby and Chef and everything?
greg commented 2019-05-28 11:07:15 +00:00
Author
Owner
Copy Link

Good point, I have updated the instructions

Good point, I have updated the instructions
galfert commented 2019-06-25 12:54:29 +00:00
Owner
Copy Link

This was understandable for me 👍

This was understandable for me :+1:
raucao closed this pull request 2019-07-02 11:41:59 +00:00
raucao deleted branch doc/4-join_ipfs_cluster 2019-07-02 11:42:05 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
service
accounts
Kosmos Accounts
service
discourse
Kosmos Community Forums
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
bug
Something is not working
design
Graphic/visual design
dev environment
Config, builds, CI, deployment, etc.
docs
Documentation
duplicate
This issue or pull request already exists
enhancement
Improving existing functionality
feature
New functionality
good first issue
Dive in, and start contributing
idea
Something to consider
invalid
Not a bug
kredits-1
Small contribution
kredits-2
Medium contribution
kredits-3
Large contribution
on hold
Currently not actionable
ops
Manual IT ops activities
question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
ui/ux
User interface, process design, etc.
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#50
No description provided.
Delete Branch "doc/4-join_ipfs_cluster"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?