Messenger V2: The New Ceph Wire Protocol
summary
Ceph ships a redesigned wire protocol, Messenger V2, implemented for Nautilus that adds extensibility, pluggable authentication and optional on‑the‑wire encryption while staying compatible with legacy clients. Control frames use a preamble/payload/epilogue layout with integrity checks via CRC32, encryption uses AES-128-GCM, and session resumption uses reconnect cookies plus message sequence numbers. Monitors listen for v2 on port 3300 by default while v1 remains for kernel modules; admins toggle v2 with ms_bind_messenger2 and an explicit mon enable step after upgrade.
AI-written summary · about
chapters (14)
- 0:00Introduction to Messenger V2
- 1:08What is Safe Messenger
- 4:23Why Messenger V2 was needed
- 6:44Messenger V2 protocol design
- 8:52Protocol phases overview
- 12:14Banner exchange phase
- 13:42Authentication phase
- 17:14Session establishment
- 20:26Reconnection handling
- 22:16Message exchange
- 23:22On-wire encryption
- 24:50Administering Messenger V2
- 30:19Upgrading to Messenger V2
- 32:15Q&A session
related talks
17mCeph Messenger Situation and Optimization
36mCeph Notification at Scale: Notification V2, an Enterprise-Level Feature
36mCeph Security BoF
38mHiding A Secret Distributed Chat System In 802.11 Management Frames
30mData Security: Theoretical and Real World Approache...
34mNVMeoF in Ceph - What's New and Performance Best Practices
33mBringing fscrypt Encryption to CephFS Userspace
23mSMB Keeping - Clients, Clusters & Clouds