ayurishchevandClaude Sonnet 5.5 c0e300f71c Run per-validator OpenStack work in parallel so all validators start at once ...

The orchestrator claimed idle validators one by one and associated each
floating IP synchronously (~30 s per address), so 20 validators started
about 30 s apart. Aggregation/disassociation and lease reclaim were
sequential in the same way.

The slow OpenStack calls now run in one goroutine per address, guarded by
an in-flight set against duplicates. control-api runs Tick in Async mode
(Tick does not wait); tests keep the waiting mode.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-01 20:37:32 +03:00

..

admin-dashboard

Scan floating IPs in the background, page by page, so thousands of addresses work

2026-10-01 19:31:11 +03:00

control-api

Run per-validator OpenStack work in parallel so all validators start at once

2026-10-01 20:37:32 +03:00

prober

Scan floating IPs in the background, page by page, so thousands of addresses work

2026-10-01 19:31:11 +03:00

SHA256SUMS

Run per-validator OpenStack work in parallel so all validators start at once

2026-10-01 20:37:32 +03:00

validator-agent

Scan floating IPs in the background, page by page, so thousands of addresses work

2026-10-01 19:31:11 +03:00