HC1: OP SIG: Difference between revisions
Jump to navigation
Jump to search
m George moved page HC1: Operations SIG to HC1: OP SIG |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Operations & Performance SIG === | |||
Chair: [[User:0x3639|0x3639]] | Chair: [[User:0x3639|0x3639]] | ||
| Line 17: | Line 18: | ||
== Scope == | == Scope == | ||
The | The OP SIG contributes to software and documentation for running, monitoring, and troubleshooting server software. It also works on performance enhancements. | ||
=== Repos === | === Repos === | ||
* https://github.com/ | * https://github.com/hypercore-one/deployment | ||
== Capabilities == | == Capabilities == | ||
Revision as of 19:23, 30 September 2024
Operations & Performance SIG
Chair: 0x3639
Communications: https://matrix.to/#/#sig-operations: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
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