Release Orchestration means the management, direction, and automation of a software release (or Go Live) process.
All the steps, checks, gates and validations a typical software release go through can be managed by a Release Orchestration system like Vamp. Steps can include a certain percentage of visitors, and/or a specific visitor-segment using Layer7 elements like: geo-location, device-type, headers, cookies or IP addresses.
Multiple steps can be chained one after the other. For each step, a Release Orchestration system can validate for both technical and business metrics if the release is still within acceptable quality-range. These ranges are typically defined by a combination of DevOps and SRE “golden metrics”, thresholds, and error-budgets, SLA/SLO based targets, and ML-powered anomaly detection. There can also be rolled-up top-line metrics, like Vamp Health (tm) that give an “early warning signal” when the quality of a release decreases. A Release Orchestration system can orchestrate releases within environments (intra-cluster), and over different environments and clusters (inter-cluster). A Release Orchestration system typically uses traffic-shaping mechanisms like proxies, loadbalancers, ingresses and service-meshes for it’s segmentation.