Cinder User Messages
summary
Block Storage returns HTTP 202 (Accepted) for long operations and the User Messages API exposes a project-level list explaining failures so you can do a volume-show and then fetch the message. Messages are produced by the volume manager, kept generic (no vendor-specific details), and are available via the python sender client today but not yet integrated into the OpenStack client. Roadmap items: add messages for top-five failure hotspots like volume migration and verify i18n via standard translation headers.
AI-written summary · about
chapters (8)
- 0:00Introduction and live session
- 1:25Client API message integration
- 3:54Session attendance and PTG plans
- 6:06Internationalization of messages
- 8:04Project communication channels
- 9:57Closing remarks and next session
- 10:21Technical issues with platform
- 12:42Post-session Q&A and wrap-up
related talks
17mOpenStack Block Storage differs from traditional block storage
41mDesign (Failures) Case Study
36mKubernetes SIG Storage Deep Dive
44mWhat's New in Cloud Foundry Volume Services
39mCloud Native Storage: Storage TAG intro, Projects, Landscape & T...
38mCloud Native Storage: The CNCF Storage TAG, Projects, Technology & Landscape
50mOverview of the Linux Storage Stack
25mDeciphering Cassandra’s Prophecy: Preventing the Fall of Your Application