Bug 1042205 - [RFE][heat]: Rolling updates for controlled rollout of changes
Summary: [RFE][heat]: Rolling updates for controlled rollout of changes
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:22 UTC by RHOS Integration
Modified: 2017-02-25 05:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:32:32 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 21:22:06 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/rolling-updates.

Description:

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.

Specification URL (additional information):

http://wiki.openstack.org/Heat/Blueprints/RollingUpdates
Note You need to log in before you can comment on or make changes to this bug.