HC1: OP SIG: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 16: | Line 16: | ||
[[Operations SIG 21 Oct 2024|21-Oct-2024]] | [[Operations SIG 21 Oct 2024|21-Oct-2024]] | ||
[[Operations SIG 18 Nov 2024|18-Nov-2024]] | |||
== Scope == | == Scope == | ||
| Line 23: | Line 25: | ||
* https://github.com/hypercore-one/deployment | * https://github.com/hypercore-one/deployment | ||
== Work Packages == | |||
[[HC1: OP SIG WP-1|Work Package 1]] | |||
== Capabilities == | == Capabilities == | ||
Latest revision as of 19:57, 4 November 2024
Operations & Performance SIG
Chair: 0x3639
Communications: https://matrix.to/#/#sig-op:hc1.chat
Meetings
Scope
The OP SIG contributes to software and documentation for running, monitoring, and troubleshooting server software. It also works on performance enhancements.
Repos
Work Packages
Capabilities
"1-click" znnd node installation
As a node operator, I want an easy way to install a full node so that I can validate the network and its transactions in a trustless way.
This includes:
- resource and hardware recommendations
- installation scripts
- configuration management
- containerization & orchestration
Observability
As a node operator, I want to have operational data about my node so that I can anticipate, observe, and understand its performance.
This includes:
- 4 Golden Signals (Latency, Traffic, Errors, Saturation)
- metric and log aggregation and reporting
- third party tooling integration
Community Support
As a node operator, I want to be able to create and share diagnostic reports so that issues I run into can be addressed by the community.
This includes:
- issue/bug trackers and templates
- FAQ & documentation for known issues and fixes