Hide Forgot
Description of problem: Need to document the procedure to 'update' to a new build within a release using ceph-ansible's rolling_update. Please add this procedure in the installation guides for both RHEL and Ubuntu. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Looks good to me, I'm not 100% sure, I think the rolling_update.yml is still at the root of ceph-ansible and not in infrastructure-playbooks directory (unless the directory exists)
LGTM Thanks Bara.
Hi Seb, When do we use this ? upgrade_ceph_packages: False Thanks, Tejas
@Tejas, this is only needed for Ceph community versions. With RHCS we don't need this.
@Tejas sorry about what I said, this is also needed by RHCS.
Is this needed to do a rolling update by the customer? I dont see this in any of the docs. Thanks, Tejas
Yes it is crucial to have this set to "True" to perform the upgrade. Can we still update the doc in this BZ?
Hi Bara, In the group_vars/all file on the ansible node, we have the option upgrade_ceph_packages: False , which is commented by default. We need to uncomment it and change to to "True" before running the rolling_update.yml Thanks, Tejas
LGTM Bara! Thanks!
I think we have missed a step. before running rolling_update.yml, we need to modify the " serial: 3" value for the number of MON,OSD,RGW,MDS nodes in the rolling_update.yml file. @Seb, can you confirm. Thanks, Tejas
No for upgrade, serial must be 1, always, we want to go node by node and perform an update one node at a time.
Thanks Seb. Bara, the content looks good. Thanks, Tejas