Bug 1585554 - [2.x] RFE - ceph-ansible rolling update for containerized cluster
Summary: [2.x] RFE - ceph-ansible rolling update for containerized cluster
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 2.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 2.*
Assignee: Sébastien Han
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1572368
TreeView+ depends on / blocked
 
Reported: 2018-06-04 05:23 UTC by Vasishta
Modified: 2019-01-23 14:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-23 14:15:04 UTC
Embargoed:

Attachments (Terms of Use)

Description Vasishta 2018-06-04 05:23:46 UTC 
Description of problem:

Currently recommended way of upgrading a containerized cluster from 2.x to 2.y is manual way of upgrading which involves stopping the service, pulling new image, replacing old image name with new one in service name, reload the daemon and restart the service for each daemon on each node.

It would be great if rolling update is supported as existing manual way decreases usability if cluster has more nodes. As rolling update is supported  for upgrading a containerized cluster from 2.x to 3.x or from 3.x to 3.y, and ceph-ansible.3.z is being shipped with 2.x latest ceph, it seems like rolling-update can be supported for 2.x containerized cluster.

Version-Release number of selected component (if applicable):
ceph-ansible - 3.0.25-1.el7cp
Comment 4 Christina Meno 2018-06-13 15:24:05 UTC 
We won't consider adding this feature in a Z stream
Comment 5 Yaniv Kaul 2019-01-23 14:15:04 UTC 
(In reply to Gregory Meno from comment #4)
> We won't consider adding this feature in a Z stream

Therefore, closing.
Note You need to log in before you can comment on or make changes to this bug.