Integrate Pumphouse with Fuel

Registered by Christopher Aedo

Feature Lead: Andrew Woodward
Mandatory Design Reviewers: Dmitry Borodaenko, Christopher Aedo
Developers: Andrew Woodward, Ryan Moe
QA: Anastasia Urlapova

Upgrading an OpenStack environment to the latest release often involves significant downtime and high risk, as rolling-back the in-place upgrade may not be possible. Using Fuel and Pumphouse, the user could evacuate some compute nodes on their existing environment and use those nodes as the start of a new cloud. This new cloud can be validated in order to ensure it provides the expected functionality. Then Pumphouse can migrate the workload on a tenant-by-tenant basis from the original cloud to the new cloud.

In order to cleanly integrate Pumphouse with Fuel, some additional functionality will be needed from Fuel. We plan to avoid functionality duplication between Fuel and Pumphouse. Pumphouse should not depend on Fuel, though Fuel can depend on Pumphouse.

Blueprint information

Status:
Complete
Approver:
Dmitry Borodaenko
Priority:
Not
Drafter:
Christopher Aedo
Direction:
Needs approval
Assignee:
Andrew Woodward
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
milestone icon next
Completed by
Andrew Woodward

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/fuel-pumphouse-integration,n,z

Addressed by: https://review.openstack.org/131527
    Add spec for fuel-pumphouse-integration blueprint

[Dmitry Borodaenko 2014-10-28]
Related blueprint on alternative longer-term approach with in-place upgrades: https://blueprints.launchpad.net/fuel/+spec/upgrade-major-openstack-environment

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.