Rolling updates for controlled rollout of changes

Registered by Clint Byrum on 2013-02-06

While managing a large group of instances, I may want to roll out changes in topology and/or configuration to a limited percentage of these instances and then wait to see if those initial rollouts produced failures or successes before deploying a larger percentage. This is known as a "canary" deployment strategy, after the old mining practice of carrying a canary in a lantern to test for air quality.

Blueprint information

Status:
Complete
Approver:
Steven Hardy
Priority:
Medium
Drafter:
Clint Byrum
Direction:
Approved
Assignee:
Clint Byrum
Definition:
Drafting
Series goal:
Accepted for future
Implementation:
Implemented
Milestone target:
None
Started by
Rico Lin on 2017-02-24
Completed by
Rico Lin on 2017-02-24

Related branches

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.