| Summary: | Need to document the procedure to 'update' to a build within a release using ceph-ansible's rolling_update | ||
|---|---|---|---|
| Product: | Red Hat Ceph Storage | Reporter: | Harish NV Rao <hnallurv> |
| Component: | Documentation | Assignee: | Bara Ancincova <bancinco> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tejas <tchandra> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.0 | CC: | asriram, kdreyer, seb, tchandra, uboppana |
| Target Milestone: | rc | ||
| Target Release: | 2.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-28 09:38:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Harish NV Rao
2016-09-07 12:05:02 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) 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 |