-
Notifications
You must be signed in to change notification settings - Fork 96
Conversation
Ok so, I've added a draft of the Bifrost team Q4 objectives and key results. All feedback welcome! I'm particularly interested in how we can carefully use the gateways to get feedback on changes in go-ipfs as a stop-gap while the testbed work is in progress... that and making sure all the critical pieces of the ipfs public infrastrucure are cleaned up and consolidated. Again, feedback is encouraged! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing I'm missing is "pretty error pages". Even if not pretty, there should be an explanation on why a 502 happened and what to do about it.
|
||
### IPFS infrastructure informs and improves core ipfs development | ||
|
||
- **P0** - Traffic is mirrored to staging gateway running latest go-ipfs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go-ipfs needs an automatically nightly-deployed gateway too
- **P1** - Ansible tower manages our deployments | ||
- Running ansible from CI gets us so far, but will cause friction as preload/bootstrappers are brought into the bifrost-infra | ||
- **P1** - 4 new DNS Bootstrap nodes are provisioned, monitored, and documented. | ||
- **P2** - 8 Solarnet Bootstrap nodes are rebuilt and monitored or decommissioned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would decommission from DO directly and deploy on Packer. Must salvage at least some peer IDs.
@hsanjuan already got you covered on the "pretty error pages"... https://github.com/ipfs/team-mgmt/pull/1037/files#diff-d954df61065b5dfa07f5e49151ffef14R52 |
👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look great! Good work team!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
||
### IPFS infrastructure informs and improves core ipfs development | ||
|
||
- **P0** - Traffic is mirrored to staging gateway running latest go-ipfs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any chance we could get a nightly bootstrapper too? 😍.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
- companion is in brave now, so we need to ready for increased usage from js-ipfs | ||
- **P1** - Ansible tower manages our deployments | ||
- Running ansible from CI gets us so far, but will cause friction as preload/bootstrappers are brought into the bifrost-infra | ||
- **P1** - 4 new DNS Bootstrap nodes are provisioned, monitored, and documented. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this be a good opportunity to dogfood /dns
multiaddrs (supporting both ip4 and ip6)?
Ref. multiformats/go-multiaddr-dns#17
refs #1033