Red HatGregory CharotAnnouncement
Lightbits is now certified for Red Hat OpenStack Services on OpenShift
Summary
Lightbits is now a certified Cinder driver for Red Hat OpenStack Services on OpenShift, tested on release 18.0.22 with driver version 2.3.12. Certification means that if an issue involves the partner component, Red Hat provides standard support and SLA while collaborating with the partner, rather than bouncing the customer back to the storage vendor. The driver ships from upstream OpenStack without forking or patching, and deployment uses standard OpenStackControlPlane custom resources and a discovery client on each compute node. New features covered include boot from volume, create volume from image, snapshot, backup, retype, and multi-attach. Retype is expected to be the most common operation for adopting Lightbits, allowing volume migration across backends using standard Cinder calls.
Context
Red Hat OpenStack Services on OpenShift is increasingly adopted by telecommunications providers (for NFV/4G/5G) and now by enterprise and public-sector customers, especially those requiring data sovereignty. These environments need storage that is integrated and supported as part of the platform, not alongside it.
Approach / What changed
Lightbits obtained certification by having its Cinder driver accepted in upstream OpenStack, shipping it as part of Red Hat’s build without forking or patching, and deploying it using standard OpenStack Services on OpenShift mechanisms (OpenStackControlPlane custom resource and a discovery client on each EDPM compute node). The CSI driver installation creates a discovery client container that mounts Cinder volumes directly to OpenStack pods.
Takeaways
Certification ensures that if a partner component is involved in a support issue, Red Hat provides standard support and SLA and collaborates with the partner, rather than redirecting the customer.
The Lightbits Cinder driver ships from upstream OpenStack without forking or patching; deployment uses standard OpenStackControlPlane custom resources and a discovery client on each EDPM compute node.
Retype is the operation expected to be used most when adopting Lightbits, allowing volume migration across backends (e.g., from existing storage onto Lightbits) using standard Cinder calls.
FAQ
What happens if a certified component causes a support issue?
If a certified partner component is involved in an issue, Red Hat provides standard support and SLA and collaborates with the partner. If the component is not certified, the customer is asked to reproduce the issue on a certified product or directed to the third-party vendor.
How do snapshots and backups differ in this setup?
Snapshots stay on the Lightbits cluster for fast cloning or rollback. Backups are written by the Cinder backup service to a separate target, protecting data if primary storage is lost. A sound data protection plan uses both.
What is required for multi-attach to work safely?
Multi-attach allows several instances to attach the same volume at once, but the instances need a clustered filesystem or an application that coordinates writes (e.g., a clustered database). Without that, concurrent writes will corrupt data.
Source and freshness
- Source
- developers.redhat.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.