Re: Octopus: conversion from ceph-ansible to Cephadm causes unexpected 15.2.15→.13 downgrade for MDSs and RGWs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 16/12/2021 14:46, Sebastian Wagner wrote:
Hi Florian, hi Guillaume

Am 16.12.21 um 14:18 schrieb Florian Haas:
Hello everyone,

my colleagues and I just ran into an interesting situation updating our Ceph training course. That course's labs cover deploying a Nautilus cluster with ceph-ansible, upgrading it to Octopus (also with ceph-ansible), and then converting it to Cephadm before proceeding with the upgrade to Pacific.

I'd go a different route actually.

 1. convert the nautilus cluster to be containerized
 2. upgrade the containerized cluster to Pacific using ceph-ansible
 3. run the adopt playbook.

Not because this path is better or worse, but because it's better tested.

That's a fine recommendation, thank you, but it's not really an answer to the question at hand. :)

To clarify: I'd like to understand how to tell "ceph orch apply" to tell Cephadm to use a specific version, while staying on Octopus.

Cheers,
Florian
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux