Bug 1373908 - Need to document the procedure to 'update' to a build within a release using ceph-ansible's rolling_update
Summary: Need to document the procedure to 'update' to a build within a release using ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 2.1
Assignee: Bara Ancincova
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-07 12:05 UTC by Harish NV Rao
Modified: 2016-11-28 09:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-28 09:38:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Harish NV Rao 2016-09-07 12:05:02 UTC
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:

Comment 4 seb 2016-10-18 13:39:26 UTC
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)

Comment 6 seb 2016-10-25 08:55:03 UTC
LGTM
Thanks Bara.

Comment 7 Tejas 2016-11-07 11:08:16 UTC
Hi Seb,

   When do we use this ?
upgrade_ceph_packages: False

Thanks,
Tejas

Comment 8 seb 2016-11-08 11:24:31 UTC
@Tejas, this is only needed for Ceph community versions. With RHCS we don't need this.

Comment 9 seb 2016-11-08 11:25:47 UTC
@Tejas sorry about what I said, this is also needed by RHCS.

Comment 10 Tejas 2016-11-08 11:28:03 UTC
Is this needed to do a rolling update by the customer? I dont see this in any of the docs.

Thanks,
Tejas

Comment 11 seb 2016-11-08 11:30:06 UTC
Yes it is crucial to have this set to "True" to perform the upgrade. Can we still update the doc in this BZ?

Comment 13 Tejas 2016-11-08 13:44:09 UTC
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

Comment 15 seb 2016-11-08 15:41:42 UTC
LGTM Bara! Thanks!

Comment 16 Tejas 2016-11-09 09:36:45 UTC
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

Comment 17 seb 2016-11-09 11:01:32 UTC
No for upgrade, serial must be 1, always, we want to go node by node and perform an update one node at a time.

Comment 18 Tejas 2016-11-09 11:18:55 UTC
Thanks Seb.

Bara, the content looks good.

Thanks,
Tejas


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