The raft logs on dev appear to be broken, commands like ipfs-cluster-ctl pin ls $HASH result in "cluster: the state on this node is not consistent", so we probably need to bootstrap the node again before we can upgrade: https://cluster.ipfs.io/documentation/upgrades/#troubleshooting-upgrades
https://github.com/ipfs/ipfs-cluster/blob/v0.10.1/CHANGELOG.md#v0101---2019-04-10
0.10.0 switched away from raft
The raft logs on dev appear to be broken, commands like `ipfs-cluster-ctl pin ls $HASH` result in "cluster: the state on this node is not consistent", so we probably need to bootstrap the node again before we can upgrade: https://cluster.ipfs.io/documentation/upgrades/#troubleshooting-upgrades
Switch the nginx vhost for ipfs.kosmos.org to port 5001 temporarily (connect to ipfs instead of the ipfs-cluster daemon)
Remove andromeda from the current cluster, leaving dev the only member
Update ipfs-cluster to 0.10.1 on andromeda, initialize a new cluster on andromeda
Stop the current cluster on dev, update ipfs-cluster to 0.10.1, join andromeda's new cluster
I have a battle plan:
- Switch the nginx vhost for ipfs.kosmos.org to port 5001 temporarily (connect to ipfs instead of the ipfs-cluster daemon)
- Remove andromeda from the current cluster, leaving dev the only member
- Update ipfs-cluster to 0.10.1 on andromeda, initialize a new cluster on andromeda
- Stop the current cluster on dev, update ipfs-cluster to 0.10.1, join andromeda's new cluster
You do realize that we want to move away from dev in the first place, right? Hence, we have a whole new machine to play with (barnard.kosmos.org), which will contain both hal and ipfs.
You do realize that we want to move away from dev in the first place, right? Hence, we have a whole new machine to play with (barnard.kosmos.org), which will contain both hal and ipfs.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://github.com/ipfs/ipfs-cluster/blob/v0.10.1/CHANGELOG.md#v0101---2019-04-10
0.10.0 switched away from raft
The raft logs on dev appear to be broken, commands like
ipfs-cluster-ctl pin ls $HASHresult in "cluster: the state on this node is not consistent", so we probably need to bootstrap the node again before we can upgrade: https://cluster.ipfs.io/documentation/upgrades/#troubleshooting-upgradesI have a battle plan:
You do realize that we want to move away from dev in the first place, right? Hence, we have a whole new machine to play with (barnard.kosmos.org), which will contain both hal and ipfs.
Oh, and also we want to deploy a new XMPP hal and move hubot-kredits over to that instead of the IRC one...
Yes, I realize that, but that doesn't mean we should do multiple things at the same time
Why not? It actually makes this upgrade much easier if we don't have to mess around with the existing node that is in use.
Hasn't this been finished?
Closed by #49