Jewel -> Luminous upgrade actions: filestore -> bluestore and msgr1 -> msgr2 upgrade path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Ceph OSD Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Given the fact that Ceph Luminous will be shipped with the Pike Ubuntu Cloud Archive, a natural question is how to upgrade to Pike not only in terms of OpenStack packages but also for the ceph package as well.
http://
ceph 12.1.2-0ubuntu2
There are several major changes coming, including:
* a change of a wire protocol
https:/
TYPE_LEGACY = 1, ///< legacy msgr1 protocol (ceph jewel and older)
TYPE_MSGR2 = 2, ///< msgr2 protocol (new in ceph kraken)
http://
* a change of a default backing store from FileStore to BlueStore
there are several migration strategies available but it is possible to run a cluster in a mixed FileStore & BlueStore mode and perform a rolling upgrade
https:/
The upgrade procedure from Jewel or Kraken is described in a link below and includes steps that would be good to incorporate into charm actions that would later be used in a more complex upgrade script.
http://
"1. Ensure that the sortbitwise flag is enabled:
# ceph osd set sortbitwise
...
5. Set the noout flag for the duration of the upgrade. (Optional but recommended.):
# ceph osd set noout
...
6. Upgrade monitors by installing the new packages and restarting the monitor daemons. Note that, unlike prior releases, the ceph-mon daemons must be upgraded first <---- !!!
..."
Changed in charm-ceph-osd: | |
status: | New → Incomplete |
Changed in charm-ceph-mon: | |
status: | New → Incomplete |
Changed in charm-ceph-mon: | |
status: | New → Triaged |
Changed in charm-ceph-osd: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in charm-ceph-mon: | |
importance: | Undecided → Wishlist |
tags: |
added: cpe-onsite removed: cpec |
tags: | added: ceph-upgrade |
For a converged architecture where nova-compute resides on the same host as ceph-osd there is another potential problem: if nova-compute is upgraded before ceph-osd, ceph packages will get upgraded as well due to `apt upgrade` before ceph-mons are upgraded on other units (although an osd process might still be running with an old version unless explicitly restarted).
The same applies to charm-neutron- gateway and charm-ceph-osd if they are collocated on the same logical host.
Even though this is not directly related to the ceph-osd charm it is an important side-effect to remember about.