Recording of training session: https://drive.google.com/file/d/1C0TryYJPe8U7ofS7spN9rt_BisCdTdsF/view This document focuses specifically on Status fleets.

Owner vs maintainer

We differentiate between a fleet owner and a fleet maintainer.

• The fleet owner is generally the main stakeholder who benefits from the fleet or uses it for their application and therefore commissions the deployment of the fleet for a specific purpose.
• The fleet maintainer is responsible for technical tasks related to the fleet, such as performing deployments, provisioning disk space, fixing networking issues, maintaining monitoring interfaces, accessing logs, etc. The fleet maintainer generally gets their mandate from tasks/goals set by the fleet owner.

With this definition in mind, Status itself would be seen as the Status fleet “owner”, whereas the infra team could be considered the “maintainer”. This document focuses specifically on common responsibilities of the fleet owner.

Note that some responsibilities are shared between both owner and maintainer (such as commissioning upgrade, monitoring fleet health, etc.)

Owner responsibilities

1. Understand purpose of current fleets
2. Commission new fleets when necessary
3. Commission fleet upgrades
4. Monitor fleet health metrics
5. Monitor protocol metrics
6. Monitor logs, or access important logs for debugging
7. Commission fleet config changes

1. Understand purpose of current fleets

Status currently has the following fleets:

status.test "Status test fleet"

• Note: this fleet will be decommissioned when the Communities feature has been migrated to a statically-sharded fleet.
• Purpose: dogfooding/smoke-testing of the latest nwaku features or manually deployed test features without affecting the stability of the status.prodfleet.
• Version: auto-deploys the latest nwaku master on each commit. If a specific feature needs to be tested that's not merged to master yet, the auto-deployment can be paused and a feature branch deployed.
• Traffic: all messages relayed on the default pubsub topic (i.e. the same traffic as relayed in status.prod)