OKRs - 2019 Q1 Infra WG

[momack2]

refs #792

• Score 2018 Q4 OKRs
• Async Retrospective
• 2019 Q1 OKRs Open Planning (this thread)
• Move 2019 Q1 OKRs to 2019 Q1 OKRs Spreadsheet

cc @eefahy @kyledrake @mburns

[momack2]

@magik6k @achingbrain @pgte curious if you have any Q1 infra requests for @eefahy!

[pgte]

This is a general request that I think has to do with providing the best experience to newcomers, and we've all been discussing this for some time in the Browsers, GUI and DDC Working Groups. (/cc @olizilla @lidel).

We would like the first experience with IPFS and related projects to be flawless.
In the browser world the architecture is not so decentralised as one would want. We have to give some help to browsers for them to be able to talk to each other. Some of these services are:

• websocket-star rendezvous server (which serves as a relay and a discovery mechanism)
• peer-base pinner for specific apps (which tracks and participates in collaborations for a specific app and persists the state locally)
  • peer-pad
  • Discussify
  • ...?
• in the future, as an alternative to websocket-star:
  • rendezvous servers
  • circuit-relay endpoints
• ...?

In the future this list of services may increase or change. For instance, we may need to support offline messaging for when a peer wants to send a private message to another peer that is offline (like, for instance, what is currently supported in Textile Cafes).

In this sense, I think it may make sense to untangle what is required in order for the Infrastructure team to support the reliability on these services that can have so much impact on first user experience!

[pgte]

Also, there is a second broad request: To produce, support and document the artefacts required for users to be able to deploy some of these services themselves.

Developers start by using the public infrastructure, but may want to pursue the deployment of their own public or private infrastructure.

This story should have a well known and supported progression.

[olizilla]

Related to @pgte's point, there is a KR for the GUI team to:

Publish a case-study on share.ipfs.io for infrastructure requirements to host your own.

which is there to ensure we do the ground work to figure out and document the code changes, recommended config and infra requirements to run a production service that uses IPFS. This is intended to be a collaboration with core-ipfs, gui and infra, though I'm happy for GUI to drive it through and make the asks of the other teams as we go.

[alanshaw]

JS IPFS has an infra request! (From #799 (comment))

These OKRs have a big ask from infra 🙏 - we'd like a JS IPFS node to be added as one of the nodes that make up the IPFS gateway cluster.

I envisage this to be a process of slow introduction:

1. Initially I want to get JS IPFS running on a macine or vm provisioned in a similar way to the existing nodes, in order for it to be easy to add as a gateway node when the time comes. I suspect this will require some pointers to existing docs or access to a repo where the provisioning scripts are kept so that I can learn how it fits together and replicate it for a JS IPFS node.

2. Run the machine for a suitable period to assess it's stability. Test it's ability to process requests and handle load. I'll need some information from infra about the load that it would be expected to handle so that a suitable stress test can be devised.

3. Use the machine or set or machines as the default gateway in a tool like companion (@lidel will this be possible? - perhaps in the beta channel?) to further test in real world scenarios.

4. Slow introduction to the gateway cluster - can we introduce it and slowly ramp up the load as it proves it's worth?

It would be amazing if infra had an OKR related to helping us achieve this.

[momack2]

Pushing forward the go-ipfs request for "Unit tests and code coverage tests are run efficiently using CI" from last quarter that got dropped: ipfs/infra#441 It'd be great if we can revive this to accelerate our dev velocity! @magik6k who has been pushing on this

[aschmahmann]

Continuing on @pgte and @olizilla 's themes of documenting infrastructure deployments, it may also be good for us to reach out to projects that are currently deploying there own infrastructure (e.g. Textile or a few of the IPFS pinning services) to see if we can pool resources.

[momack2]

Hello Infra folks - it's time to finalize our OKRs for Q1 2019! Our goal is to have this done by EOWeek, since we're already a few weeks into the quarter. =]

There's a quick tutorial at ipfs/roadmap#17 for a simple Roadmap timeline exercise to help identify and reach consensus on the most important Q1 priorities, which we can use as a feedback loop on whether this quarter's OKRs are putting us on the right track. I'm available to answer questions, take part in the timeline exercise (sync or async), and give feedback on iterations - so let me know if anything is unclear! I suggest everyone take a pass at this asynchronously and maybe schedule a meeting for Thursday or Friday to check in synchronously - do folks have thoughts on that plan?

[eefahy]

Updated the spreadsheet and linked to it here - I think we are done here?

[momack2]

Looks great! Do you want to go ahead and merge this @eefahy?