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

Update ipfs-cluster to 0.10.1 #49

Merged
greg merged 1 commits from chore/48-ipfs-cluster_0.10.1 into master 2019-05-02 09:16:51 +00:00
Conversation 2 Commits 1 Files Changed 2 +2 -2
greg commented 2019-04-30 11:01:37 +00:00
Owner
Copy Link

ipfs-cluster-ctl commands such as pin rm now work. This is running on dev and andromeda, can be merged

Closes #48

On andromeda:

Remove itself from the old cluster

ipfs@andromeda:~$ ipfs-cluster-ctl peers rm QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1

Run chef-solo with this change, to update ipfs-cluster

On dev

Stop ipfs-cluster

kare@dev:~$ sudo systemctl stop ipfs-cluster

Move the old /home/ipfs/.ipfs-cluster dir

ipfs@dev:~$ mv .ipfs-cluster .ipfs-cluster.old

Run chef-solo, stop the daemon, join andromeda:

kare@dev:~$ sudo systemctl stop ipfs-cluster
kare@dev:~$ sudo su - ipfs
ipfs@dev:~$ ipfs-cluster-service daemon --bootstrap "/ip4/46.4.18.160/tcp/9096/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1"

Check dev has joined the cluster (confirmed by checking the output of the following command on andromeda):

ipfs@andromeda:~$ ipfs-cluster-ctl peers ls
QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1 | andromeda.kosmos.org | Sees 1 other peers
  > Addresses:
    - /ip4/127.0.0.1/tcp/9096/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1
    - /ip4/46.4.18.160/tcp/9096/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1
    - /p2p-circuit/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1
  > IPFS: QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7
    - /ip4/127.0.0.1/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7
    - /ip4/46.4.18.160/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7
    - /ip6/2a01:4f8:221:39c1::2/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7
    - /ip6/::1/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7
QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V | dev | Sees 1 other peers
  > Addresses:
    - /ip4/127.0.0.1/tcp/9096/ipfs/QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V
    - /ip4/144.76.39.171/tcp/9096/ipfs/QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V
    - /p2p-circuit/ipfs/QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V
  > IPFS: QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb
    - /ip4/127.0.0.1/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb
    - /ip4/144.76.39.171/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb
    - /ip6/2a01:4f8:191:40aa::2/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb
    - /ip6/::1/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb

Now we can ctrl+c the daemon, and start the Systemd unit:

kare@dev:~$ sudo systemctl restart ipfs

I have also added a test document, then removed the pin to make sure everything works:

ipfs@dev:~$ echo "ENS instance deployed at 0x5f6f7e8cc7346a11ca2def8f827b7a0b612c56a1" > test
ipfs@dev:~$ ipfs-cluster-ctl add test
ipfs@dev:~$ ipfs pin rm QmVnQbvvCxCMppY7Q7CS7zi7ovipWcqowBNq2MyZxUnE89
ipfs-cluster-ctl commands such as `pin rm` now work. This is running on dev and andromeda, can be merged Closes #48 ## On andromeda: Remove itself from the old cluster ``` ipfs@andromeda:~$ ipfs-cluster-ctl peers rm QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1 ``` Run chef-solo with this change, to update ipfs-cluster ## On dev Stop ipfs-cluster ``` kare@dev:~$ sudo systemctl stop ipfs-cluster ``` Move the old `/home/ipfs/.ipfs-cluster` dir ``` ipfs@dev:~$ mv .ipfs-cluster .ipfs-cluster.old ``` Run chef-solo, stop the daemon, join andromeda: ``` kare@dev:~$ sudo systemctl stop ipfs-cluster kare@dev:~$ sudo su - ipfs ipfs@dev:~$ ipfs-cluster-service daemon --bootstrap "/ip4/46.4.18.160/tcp/9096/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1" ``` Check dev has joined the cluster (confirmed by checking the output of the following command on andromeda): ``` ipfs@andromeda:~$ ipfs-cluster-ctl peers ls QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1 | andromeda.kosmos.org | Sees 1 other peers > Addresses: - /ip4/127.0.0.1/tcp/9096/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1 - /ip4/46.4.18.160/tcp/9096/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1 - /p2p-circuit/ipfs/QmNVfAhxJrmkqkCHdoD6iZgJJaWkhehskeWWZ9cNZxNwo1 > IPFS: QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7 - /ip4/127.0.0.1/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7 - /ip4/46.4.18.160/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7 - /ip6/2a01:4f8:221:39c1::2/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7 - /ip6/::1/tcp/4001/ipfs/QmZ4Lpzhz8bafbTYvEMMCmrbrMM4JfyHDR23WbCSAd9bo7 QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V | dev | Sees 1 other peers > Addresses: - /ip4/127.0.0.1/tcp/9096/ipfs/QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V - /ip4/144.76.39.171/tcp/9096/ipfs/QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V - /p2p-circuit/ipfs/QmTVC6eguRWoS2W18QnPHt64h8t5yQmYRhvoZcdgr4Ax2V > IPFS: QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb - /ip4/127.0.0.1/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb - /ip4/144.76.39.171/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb - /ip6/2a01:4f8:191:40aa::2/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb - /ip6/::1/tcp/4001/ipfs/QmWY7vNysM1jgHFBuSr9Y2ayG5tUeKmGBjwjN9x6pEVxRb ``` Now we can ctrl+c the daemon, and start the Systemd unit: ``` kare@dev:~$ sudo systemctl restart ipfs ``` I have also added a test document, then removed the pin to make sure everything works: ``` ipfs@dev:~$ echo "ENS instance deployed at 0x5f6f7e8cc7346a11ca2def8f827b7a0b612c56a1" > test ipfs@dev:~$ ipfs-cluster-ctl add test ipfs@dev:~$ ipfs pin rm QmVnQbvvCxCMppY7Q7CS7zi7ovipWcqowBNq2MyZxUnE89 ```
raucao commented 2019-04-30 11:20:31 +00:00
Owner
Copy Link

I'd suggest to document here what you actually did to update the cluster, because that's not visible from a changed attribute in this PR.

Also, are you sure the entire cluster upgrade research+process was actually a small and not a medium contribution?

I'd suggest to document here what you actually did to update the cluster, because that's not visible from a changed attribute in this PR. Also, are you sure the entire cluster upgrade research+process was actually a small and not a medium contribution?
greg commented 2019-04-30 12:50:25 +00:00
Author
Owner
Copy Link

I have updated the PR description above with the commands I used, and updated the contribution to a medium one

I have updated the PR description above with the commands I used, and updated the contribution to a medium one
greg closed this pull request 2019-05-02 09:16:51 +00:00
greg deleted branch chore/48-ipfs-cluster_0.10.1 2019-05-02 09:16:59 +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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#49
No description provided.
Delete Branch "chore/48-ipfs-cluster_0.10.1"

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?