Best effort
The one-replica, lowest-cost path starts the replacement first and rolls back failures, without promising uninterrupted traffic.
Four tools, clear responsibilities
TOAD composes mature open tools instead of hiding the cloud behind another permanent control plane. Each layer has one job and one recovery story.
Small but complete
The same routing, certificates, monitoring and application contract on the smallest practical footprint.
Networks, security groups, servers, floating IPs, load balancing, and delegated DNS remain declared in OpenStack.
Docker installation, hardening, Swarm membership, ingress, and monitoring use narrow idempotent playbooks.
A small orchestration surface provides rolling updates, secrets, configs, placement, health, and rollback.
Labels become HTTPS routes through one shared overlay, without direct application ports.
The one-replica, lowest-cost path starts the replacement first and rolls back failures, without promising uninterrupted traffic.
TOAD requires two replicas, a health check, one-at-a-time start-first replacement, and a monitored automatic rollback.
Single-owner and local-state services declare a stop-first interruption instead of hiding it behind a zero-downtime claim.
For an existing healthy public service, deployment continuously probes every declared endpoint while Swarm updates it and saves timestamped JSON evidence. Rolling acceptance fails if any request fails. Traefik keeps the HTTPS route while Swarm's virtual IP owns changing backend membership. Protecting against a server failure additionally requires replicas on independent nodes.
Traefik OSS uses one certificate-state writer. Managers and Octavia are resilient; that task is not active/active.
Named volumes are single-node state. Availability comes from an explicit storage profile and tested encrypted recovery.
In-cluster monitoring cannot see a total cloud failure. A credential-free external probe runs elsewhere.