Fwd: Upgrade Path Advice Nautilus (CentOS 7) -> Octopus (new OS)
Hello, Looking for a bit of guidance / approach to upgrading from Nautilus to Octopus considering CentOS and Ceph-Ansible. We're presently running a Nautilus cluster (all nodes / daemons 14.2.11 as of this post). - There are 4 monitor-hosts with mon, mgr, and dashboard functions consolidated; - 4 RGW hosts - 4 ODS costs, with 10 OSDs each. This is planned to scale to 7 nodes with additional OSDs and capacity (considering to do this as part of upgrade process) - Currently using ceph-ansible (however it's a process to maintain scripts / configs between playbook versions - although a great framework, not ideal in our case; - All hosts run CentOS 7.x; - dm-crypt in use on LVM OSDs (via ceph-ansible); - Deployment IS NOT containerized. Octopus support on CentOS 7 is limited due to python dependencies, as a result we want to move to CentOS 8 or Ubuntu 20.04. The other outlier is CentOS native Kernel support for LSI2008 (eg. 9211) HBAs which some of our OSD nodes use. Irrespective of OS considerations above, the upgrade will be to an OS that fully supports Octopus. We'd like to make use of ceph orchestrator for on-going cluster management. Here's an upgrade path scenario that is being considered. At a high-level: 1. Deploy a new monitor on CentOS 8. May be Nautilus via established ceph-ansible playbook. 2. Upgrade new monitor to Octopus using dnf / ceph package upgrade. 3. Decommission individual monitor hosts (existing on CentOS 7) and redeploy on CentOS 8 via ceph orchestrator from new monitor node; 4. Repeat until all monitors are on new OS + Octopus (all deployed via Ceph Orchestrator. 5. Add additional OSD nodes / drives / capacity via orchestrator on Octopus; 6. Upgrade existing OSD hosts by keeping OSDs intact, reinstalling new OS (CentOS 8 or Ubuntu 20.04); 7. Deploy ceph octopus on new nodes via orchestrator; 8. Reactivate / rescan in-tact OSDs on newly redeployed node. (i.e. ceph-volume lvm activate --all) 9. Rinse / repeat for remaining Nautilus nodes. 10. Manually upgrade RGW packages on gateway nodes. Thank you.
Looking for a bit of guidance / approach to upgrading from Nautilus to Octopus considering CentOS and Ceph-Ansible.
We're presently running a Nautilus cluster (all nodes / daemons 14.2.11 as of this post). - There are 4 monitor-hosts with mon, mgr, and dashboard functions consolidated;
You want an odd number of mons. Add or remove one.
- 4 RGW hosts - 4 ODS costs, with 10 OSDs each. This is planned to scale to 7 nodes with additional OSDs and capacity (considering to do this as part of upgrade process)
Don’t tempt fate. One thing at a time. Not three.
- Currently using ceph-ansible (however it's a process to maintain scripts / configs between playbook versions - although a great framework, not ideal in our case;
^ Kefu ;)
Octopus support on CentOS 7 is limited due to python dependencies, as a result we want to move to CentOS 8 or Ubuntu 20.04.
Do you have a compelling reason to go to Octopus today?
The other outlier is CentOS native Kernel support for LSI2008 (eg. 9211) HBAs which some of our OSD nodes use.
How is this a factor, do newer kernels drop support for that old HBA?
Here's an upgrade path scenario that is being considered. At a high-level:
I suggest that if you are set on doing this, you do one step at a time and don’t try to get fancy. Especially since you only have one cluster. I believe there are Nautlius packages available for CentOS 8 now, so perhaps: * Update each node — serially — to CentOS 8 + new Ceph packages * Update to Octopus via the documented method * Add your new nodes
On Thu, 27 Aug 2020 at 13:21, Anthony D'Atri <anthony.datri@gmail.com> wrote: > > > > > > Looking for a bit of guidance / approach to upgrading from Nautilus to > > Octopus considering CentOS and Ceph-Ansible. > > > > We're presently running a Nautilus cluster (all nodes / daemons 14.2.11 > as > > of this post). > > - There are 4 monitor-hosts with mon, mgr, and dashboard functions > > consolidated; > > You want an odd number of mons. Add or remove one. > Agreed. Odd number is the target end state. > > > - 4 RGW hosts > > - 4 ODS costs, with 10 OSDs each. This is planned to scale to 7 nodes > > with additional OSDs and capacity (considering to do this as part of > > upgrade process) > > Don’t tempt fate. One thing at a time. Not three. > Never said I was doing all three. One at a time as per suggested proc. We would be upgrading MGRs, MONs in one go given they are collocated on the same nodes. > > > - Currently using ceph-ansible (however it's a process to maintain > scripts > > / configs between playbook versions - although a great framework, not > ideal > > in our case; > > ^ Kefu ;) > ?? Not sure I follow. Our question is around Ceph Orchestrator vs Ansible. The idea of having something managed by the Ceph project vs. a bolt-on. There are valid arguments for both. My comments were not intended to offend. Our objective is to reduce complexity / moving parts in managing ceph as a whole. Given the project has native orchestrator it would be preferred to leverage / transition into that (for our deployment). > > > Octopus support on CentOS 7 is limited due to python dependencies, as a > > result we want to move to CentOS 8 or Ubuntu 20.04. > > Do you have a compelling reason to go to Octopus today? > Is there a compelling reason not to proceed? Is it not the next stable release? 4 updates since release so far. Specifically, I'm after object lock and other performance efficiencies. > > > The other outlier is CentOS native Kernel support for LSI2008 (eg. > 9211) HBAs which some of our > > OSD nodes use. > > How is this a factor, do newer kernels drop support for that old HBA? > It's a RHEL / CentOS thing. Mainline and Ubuntu kernels support is just fine. It's a mature HBA :) extensively deployed and used in scale out storage clusters. > > Here's an upgrade path scenario that is being considered. At a > high-level: > > I suggest that if you are set on doing this, you do one step at a time and > don’t try to get fancy. Especially since you only have one cluster. > Thats the intent. I'm looking for validation / experiences and others from their upgrades. > > I believe there are Nautlius packages available for CentOS 8 now, so > perhaps: > > * Update each node — serially — to CentOS 8 + new Ceph packages > * Update to Octopus via the documented method > * Add your new nodes > > Noted. It's a valid scenario as well.
participants (2)
-
Anthony D'Atri
-
Cloud Guy