[ceph-users] Ensure Hammer client compatibility

[Kees Meijs]

Good afternoon Cephers,

While I'm fixing our upgrade-semi-broken cluster (see thread Upgrade to
Infernalis: failed to pick suitable auth object) I'm wondering about
ensuring client compatibility.

My end goal is BlueStore (i.e. running Luminous) and unfortunately I'm
obliged to offer Hammer client compatibility.

Any pointers on how to ensure this configuration-wise?

Thanks!

Regards,
Kees
--
https://nefos.nl/contact

Nefos IT bv
Ambachtsweg 25 (industrienummer 4217)
5627 BZ Eindhoven
Nederland

KvK 66494931

/Aanwezig op maandag, dinsdag, woensdag en vrijdag/

[Lincoln Bryant]

Hi Kees,

What interfaces do your Hammer clients need? If you're looking at
CephFS, we have had reasonable success moving our older clients (EL6)
to NFS Ganesha with the Ceph FSAL.

--Lincoln

Post by Kees Meijs
Good afternoon Cephers,
While I'm fixing our upgrade-semi-broken cluster (see thread Upgrade
to Infernalis: failed to pick suitable auth object) I'm wondering
about ensuring client compatibility.
My end goal is BlueStore (i.e. running Luminous) and unfortunately
I'm obliged to offer Hammer client compatibility.
Any pointers on how to ensure this configuration-wise?
Thanks!
Regards,
Kees
-- 
https://nefos.nl/contact 
Nefos IT bv
Ambachtsweg 25 (industrienummer 4217)
5627 BZ Eindhoven
Nederland
KvK 66494931
Aanwezig op maandag, dinsdag, woensdag en vrijdag
_______________________________________________
ceph-users mailing list
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Kees Meijs]

Hi Lincoln,

We're looking at (now existing) RBD support using KVM/QEMU, so this is
an upgrade path.

Regards,
Kees

Post by Lincoln Bryant
What interfaces do your Hammer clients need? If you're looking at
CephFS, we have had reasonable success moving our older clients (EL6)
to NFS Ganesha with the Ceph FSAL.

[Kees Meijs]

Hi list,

Having finished our adventures with Infernalis we're now finally running
Jewel (10.2.11) on all Ceph nodes. Woohoo!

However, there's still KVM production boxes with block-rbd.so being
linked to librados 0.94.10 which is Hammer.

     health HEALTH_WARN
            crush map has legacy tunables (require bobtail, min is
firefly)
            no legacy OSD present but 'sortbitwise' flag is not set

Obviously we would like go to HEALTH_OK again without the warnings
mentioned maintaining Hammer client support.

Running ceph osd set require_jewel_osds seemed harmless in terms of
client compatibility so that's done already.

However, what about sortbitwise and tunables?

Thanks,
Kees

We're looking at (now existing) RBD support using KVM/QEMU, so this is
an upgrade path.

[Kees Meijs]

Hi again,

I just read (and reread, and again) the chapter of Ceph Cookbook on
upgrades and
http://docs.ceph.com/docs/jewel/rados/operations/crush-map/#tunables and
figured there's a way back if needed.

The sortbitwise flag is set (repeering was almost instant) and tunables
to "hammer".

There's a lot of data shuffling going on now, so fingers crossed.

Cheers,
Kees

Post by Kees Meijs
However, what about sortbitwise and tunables?