Upgrade ipfs-cluster to v1 #1184
Labels
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
Comments
olizilla
added
kind/enhancement
|
Currently the staging api writes to the prod ipfs-cluster. This was convenient, but to be able to deploy an api change to cluster and test it, we are now going to need a staging cluster that we can update to v1 while leaving prod on v0.x |
dchoi27
added
P1
|
@thattommyhall is setting up a staging cluster for us https://github.com/protocol/bifrost-infra/issues/1791 |
|
ETA today! |
olizilla
added a commit
that referenced
this issue
Apr 7, 2022
The IPFS Cluster v1 release has much improved perf, and some breaking API changes. In this PR we upgrade the ipfs-cluster client and local test environment to work with the v1 cluster API. When this PR is merged to main, the staging API credentials must be updated. The production release of this PR needs to be coordinated with the upgrade of the ipfs-cluster binaries on the prod cluster. There will be a second PR to update the pins cron, which should be merged to main once the prod cluster is upgraded. see: #1184 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <[email protected]>
olizilla
added a commit
that referenced
this issue
Apr 7, 2022
Adopt the new ipfs-cluster client to be ready for the ipfs cluster v1 roll out. Should be merged to main **after** the production cluster is upgraded to v1 see: #1184 see: #1227 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <[email protected]>
olizilla
added a commit
that referenced
this issue
Apr 8, 2022
The IPFS Cluster v1 release has much improved perf, and some breaking API changes. In this PR we upgrade the ipfs-cluster client and local test environment to work with the v1 cluster API. ### Testing it - Our integration tests have been updated to use the v1 cluster and now pass with this changeset. - This PR is also tested locally by pointing a dev api at the `nft.storage.ipfscluster.io` cluster which is now used for QA and is running [email protected] - The staging deployment should be tested when this PR is merged to main. ### Deploying it The **staging API cluster credentials must be updated** on Cloudflare after this PR is merged to main. To deploy to production we need to: - Put the API into READ-ONLY (check, do we read from cluster in read-only? if so do we hit any api that has changed? - Deploy [email protected] to the production web3 cluster - Merge the API release PR and wait for the API deployment to complete. - Merge the #1228 PR, to update the affected cron jobs - Put the API back into RW mode and monitor. - FIN see: #1184 see: https://github.com/nftstorage/ipfs-cluster/releases/tag/v5.0.0 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <[email protected]>
olizilla
added a commit
that referenced
this issue
Apr 8, 2022
Adopt the new ipfs-cluster client to be ready for the ipfs cluster v1 roll out. Should be merged to main **after** the production cluster is upgraded to v1 see: #1184 see: #1227 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <[email protected]>
vasco-santos
pushed a commit
that referenced
this issue
Apr 11, 2022
Adopt the new ipfs-cluster client to be ready for the ipfs cluster v1 roll out. Should be merged to main **after** the production cluster is upgraded to v1 see: #1184 see: #1227 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cluster v1 has breaking changes, and significant perf improvements
Before we can use it we need to:
From @hsanjuan: Updating web3.storage ipfs-cluster to v1.0.0-rc3 will take approximately 2 hours, but the part where writes are disabled should be short. The suggested deployment steps are:
The text was updated successfully, but these errors were encountered: