logos-blockchain/logos-blockchain-testing

mirror of https://github.com/logos-blockchain/logos-blockchain-testing.git synced 2026-02-18 12:13:07 +00:00

Hansie Odendaal b3d54125ea

* Add node config overrides (#14)

* chore: merge master into dev and update configs after merge (#17)

* Sdp config structs from logos blockchain (#15)

* Update configs after main repo merge

---------

Co-authored-by: gusto <bacv@users.noreply.github.com>

* Local deployer allows to stop and restart nodes (#16)

* Unify local node control and restart support

* Add local stop-node support

* Use node names for restart/stop control

* merge

---------

Co-authored-by: hansieodendaal <hansie.odendaal@gmail.com>

* Add orphan manual cluster test utilities

* Update node rev and align consensus/wallet config

* Update node rev and align wallet/KMS configs

* Update main repo ref (#23)

* Fix genesis utxos and scale leader stake

* Document leader stake constants

* feat: add custom persistent dir option for working files (#26)

* chore: config and naming updates (#27)

* Update config and crate naming

- Updated configs to the lates main repo configs.
- Updated all main repo crate namings to be same as the main repo.
- Added `create_dir_all` to `pub(crate) fn create_tempdir(custom_work_dir: Option<PathBuf>) -> std::io::Result<TempDir> {`.
- Wired in optional `persist_dir` when using the local deployer.
- Update `time` vulnerability

**Note:** Unsure about the `service_params` mapping in `pub(crate) fn cryptarchia_deployment(config: &GeneralConfig) -> CryptarchiaDeploymentSettings {`

* fix ntp server config

---------

Co-authored-by: Andrus Salumets <andrus@status.im>
Co-authored-by: gusto <bacv@users.noreply.github.com>
Co-authored-by: andrussal <salumets.andrus@gmail.com>

2026-02-09 14:12:26 +02:00

3.8 KiB

Raw Blame History

Operations & Deployment Overview

Operational readiness focuses on prerequisites, environment fit, and clear signals that ensure your test scenarios run reliably across different deployment targets.

Core Principles

Prerequisites First: Ensure all required files, binaries, and assets are in place before attempting to run scenarios
Environment Fit: Choose the right deployment target (host, compose, k8s) based on your isolation, reproducibility, and resource needs
Clear Signals: Verify runners report node readiness before starting workloads to avoid false negatives
Failure Triage: Map failures to specific causes—missing prerequisites, platform issues, or unmet expectations

Key Operational Concerns

Prerequisites:

versions.env file at repository root (required by helper scripts)
Node binaries (logos-blockchain-node) available or built on demand
Platform requirements met (Docker for compose, cluster access for k8s)
Circuit assets for proof generation

Artifacts:

Circuit parameters required by the node binary
Docker images for compose/k8s deployments
Binary bundles for reproducible builds

Environment Configuration:

Logging configured via LOGOS_BLOCKCHAIN_LOG_* variables
Observability endpoints (Prometheus, Grafana) optional but useful

Readiness & Health:

Runners verify node readiness before starting workloads
Health checks prevent premature workload execution
Consensus liveness expectations validate basic operation

Runner-Agnostic Design

The framework is intentionally runner-agnostic: the same scenario plan runs across all deployment targets. Understanding which operational concerns apply to each runner helps you choose the right fit.

Concern	Host	Compose	Kubernetes
Topology	Full support	Full support	Full support
Workloads	All workloads	All workloads	All workloads
Expectations	All expectations	All expectations	All expectations
Chaos / Node Control	Not supported	Supported	Not yet
Metrics / Observability	Manual setup	External stack	Cluster-wide
Log Collection	Temp files	Container logs	Pod logs
Isolation	Process-level	Container	Pod + namespace
Setup Time	< 1 min	2-5 min	5-10 min
CI Recommended?	Smoke tests	Primary	Large-scale only

Key insight: Operational concerns (prerequisites, environment variables) are largely consistent across runners, while deployment-specific concerns (isolation, chaos support) vary by backend.

Operational Workflow

flowchart LR
    Setup[Prerequisites & Setup] --> Run[Run Scenarios]
    Run --> Monitor[Monitor & Observe]
    Monitor --> Debug{Success?}
    Debug -->|No| Triage[Failure Triage]
    Triage --> Setup
    Debug -->|Yes| Done[Complete]

Setup: Verify prerequisites, configure environment, prepare assets
Run: Execute scenarios using appropriate runner (host/compose/k8s)
Monitor: Collect logs, metrics, and observability signals
Triage: When failures occur, map to root causes and fix prerequisites

Documentation Structure

This Operations & Deployment section covers:

Prerequisites & Setup — Required files, binaries, and environment setup
Running Examples — How to run scenarios across different runners
CI Integration — Automating tests in continuous integration pipelines
Environment Variables — Complete reference of configuration variables
Logging & Observability — Log collection, metrics, and debugging

Philosophy: Treat operational hygiene—assets present, prerequisites satisfied, observability reachable—as the first step to reliable scenario outcomes.

3.8 KiB Raw Blame History