<aside> ℹ️ The Bifrost Roadmap and OKRs are available below.

</aside>


<aside> ⚠️ The content below should be considered to be outdated and obsolete. Please refer to the roadmap and objectives pages linked above for future reference.

</aside>

This page serves as a place to discuss the team's OKRs and propose new ones. We’ll aim to keep a mirror of the Objectives here, but not the Key Results/Milestones, for simplicity and not creating unnecessary duplication. For the official view of our OKRs, please refer to our roadmap at:

https://github.com/protocol/netops/issues/52


Q4 2022

🔴 Running Ansible Automation Platform (AAP)

AAP (ex Ansible Tower) replace the flaky Circle CI playbooks. Bring a robust and stable process for deploying our changes fully. AAP’s RBAC feature enables developers to deploy custom Kubo or ipfs-cluster builds to select servers as self-service.

🟡 Badbits denylist web service

Allow better collaboration and publishing of badbits lists and minimize disruption when deploying updates to the blocking service. Badbits denylist will be served from web service with proper metrics and better code hygiene.

🟢 Clean up / reduce alert noise

Create runbooks for all critical alerts and link to them, and eliminate unactionable critical/non-critical alerts (e.g. replace Pingdom with the Synthetic Monitor).

⚪ Implement Reframe support in the Gateways

Have delegated reframe queries from all gateways to the indexers.


2023 H1

🟢  Theme: Support the migration to Saturn

https://github.com/protocol/netops/issues/60

This thread of work focuses on the tasks necessary to support the migration to Saturn as well as the Decentralised Gateway efforts as they relate to this.

🟢  Theme: Transition to being the Gateway Technologies Team

https://github.com/protocol/netops/issues/61

This thread of work focuses on the tasks necessary for the team to begin transitioning from a team that “runs the gateways” to a team that works with various gateway technologies. And furthermore, has identified other streams of work that add value to PL and the wider ecosystem, beyond just running infrastructure.

⚪ Theme: Legacy Tech Maintenance

https://github.com/protocol/netops/issues/62

This thread of work focuses on the tasks necessary for the team to standardise and simplify more of our offerings. To reduce operational overhead, make these offerings more applicable to the wider community, create more opportunities for sharing and reuse with the community, among other aspects.

⚪ Theme: Team KPIs & Visibility

https://github.com/protocol/netops/issues/63

This thread of work focuses on the tasks necessary for the team to improve the monitoring and observability story of the services that we manage. From both an operational and a business metrics perspective.