Patch or upgrade Fuel

Registered by David J. Easter

Currently, Fuel is tied to a single version of a distribution. To upgrade Fuel to enable deployment of a newer version of a distribution, the Fuel Master Node needs to be re-installed, losing all knowledge and management of previously deployed environments. The goal of this item is to create an ability to upgrade of Fuel to then enable deployment of a newer version of a distribution without losing the ability to manage versions previously deployed through that Fuel Master Node.

Blueprint information

Status:
Complete
Approver:
Mike Scherbakov
Priority:
Essential
Drafter:
Evgeniy L
Direction:
Approved
Assignee:
Evgeniy L
Definition:
Approved
Series goal:
Accepted for 5.0.x
Implementation:
Implemented
Milestone target:
milestone icon 5.0
Started by
Evgeniy L
Completed by
Mike Scherbakov

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/82081
    Created command line interface 'fuel_upgrade' for master node upgrading

Addressed by: https://review.openstack.org/82087
    Created command line interface 'fuel_update_downloader' for update downloading

Addressed by: https://review.openstack.org/82508
    Several stylistic fixes for upgarde system

Addressed by: https://review.openstack.org/86097
    Implementation of docker manager for upgrade system

Addressed by: https://review.openstack.org/86296
    Fuel upgrade

Addressed by: https://review.openstack.org/87326
    Add OpenStack upgrader to fuel-upgrade

Addressed by: https://review.openstack.org/87503
    Update packages repository source(ubuntu && centos)

Addressed by: https://review.openstack.org/87722
    Add entities for Fuel upgrade

Addressed by: https://review.openstack.org/90186
    Add api version to versions.yaml

Addressed by: https://review.openstack.org/90190
    Add repodata.yaml file on the master node

Addressed by: https://review.openstack.org/96179
    Implementation of docker based upgrade system

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.