Milestone 3 Report

[nrutledge]

This issue is meant to track progress on the acceptance criteria and evidence of milestone completion for M3.

Acceptance Criteria

The following is a breakdown of the acceptance criteria for M3, along with explanation as to how each have been satisfied.

The testnet remains accessible throughout the duration of this milestone (first 3 months of the 6-month maintenance period) with at least 99% uptime for this 3 month period.

The congested testnet has been hosted continuously since January of this year. The average uptime over the last 90 days is greater than 99% (details below).

The testnet remains stable and operating as expected.

At this point the testnet has mainly been used internally but no issues regarding the stability or operation have been reported thus far.

Any major issues reported by the community are triaged and dealt with according to importance/severity.

No issues have been reported by the community thus far. For status on internally reported issues, please see below.

Evidence of Milestone completion

Public issues tab in the https://github.com/mlabs-haskell/congested-testnet repo showing current status of all issues that have been reported.

Issues can be reported and viewed by anyone using the following link: https://github.com/mlabs-haskell/congested-testnet/issues

PDF (or Gitbook) showing uptime for the duration of this milestone as well as progress on issues (issue names, current status, links to PRs with fixes, and reasons for any not addressed).

Due to the limited number of issues reported thus far, a separate PDF or Gitbook is unecessary. Below are the uptime and issue details:

Uptime

Uptime for the congested testnet is being tracked using Prometheus. The following URL will show the average uptime over the 90 day period prior to 2024/06/06:

Congested Testnet 90 Day Avg. Uptime

The average uptime for the two nodes which currently comprise the congested testnet are as follows:

• node-relay-1 - 100% uptime
• node-spo-1 - 99.99992947508005% uptime

Issue Progress

Below is a current breakdown of issues by status as of 2024/06/06.

Backlog

• Uptime reports #5
  • Uptime history is currently accessible through Prometheus
  • We may add a dedicated uptime reports page in the future
• Add another instance / increase spammer capacity #7
  • Options for improving behavior of the testnet are still being considered (we may not need to increase capacity)
• Downtime alerts #8
  • Downtime alerts will be useful but are not strictly necessary yet due to limited usage

Completed

• Milestone 3: Improvements and Maintenance #6

Relevant PRs/Commits (Improving Stability/Availability)

• Maxim/new spo #9
  • Fix kes period bug, which can stop spo node
• Commits from 2c3696b to 5e4db76 in master branch
  • Added restapi with cardano-cli wrapper to get testnet state, such as current slot number and etc.
• Commit 29e792f
  • Change prometheus config to store testnet logs for longer period