Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1499711

Summary: [Doc] - Container Guide - New section describing ceph-ansible way of rolling update is needed
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: DocumentationAssignee: Bara Ancincova <bancinco>
Status: CLOSED CURRENTRELEASE QA Contact: Parikshith <pbyregow>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: anharris, asriram, hnallurv, kdreyer, pbyregow, shan
Target Milestone: rc   
Target Release: 3.0   
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: 2017-12-26 03:41:08 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1496210    

Description Vasishta 2017-10-09 09:42:25 UTC
Description of problem:
As rolling update of containerized ceph is supported from latest 2.x to 3.0, we need to add a doc section in container guide having steps to update containerized ceph using ceph-ansible.

Comment 3 Sébastien Han 2017-10-09 15:14:54 UTC
The draft looks good.
Correct the playbook does that for you so you don't need these procedures anymore.

Yes, you can run an async update.

Comment 5 Vasishta 2017-10-10 12:28:27 UTC
Hi,

As we support update from 2.x to 3, I think we need to add a step/NOTE explaining migration of yml files to the newer versions before running playbook.

Example - in 2.x we used to have a variable called mon_containerized_deployment and we had suggested in doc to set the above variable to true. But in 3.x all.yml file will not be having any variable with that particular name.

Moving back to ASSIGNED state, please let me know if there are any concerns.

Regards,
Vasishta

Comment 7 Sébastien Han 2017-10-11 14:15:13 UTC
Bara, for the table with also have:


* ceph_rhcs became ceph_origin: repository and ceph_repository: rhcs, however, these are enabled by default in all.yml now.

* ceph_rhcs_cdn_install: true and ceph_rhcs_iso_install: true became ceph_repository_type: cdn or iso

Thanks!

Comment 9 Sébastien Han 2017-10-11 14:28:54 UTC
Sorry there is also:

* raw_journal_devices became dedicated_devices

And for dmcrypt_dedicated_journal + dmcrytpt_journal_collocation they actually became:

dmcrytpt_journal_collocation now is dmcrypt + osd_scenario: collocated
dmcrypt_dedicated_journal now is dmcrypt + osd_scenario: non-collocated

Thanks!

Comment 11 Sébastien Han 2017-10-11 15:13:56 UTC
lgtm thanks!

Comment 13 Sébastien Han 2017-10-27 13:17:08 UTC
You're right Parikshith, after the upgrade to 3.0 it's recommended to use the variables from the new group_vars/ files. So we should clarify the doc with that regard, we already have a table that maps the old and new options (above).