Slides and content from Alex's FOSDEM '25 talk about OpenBao's usage at GitLab.
For a video, see our official YouTube channel or on the FOSDEM video mirror.
Hello everyone! I'm Alex Scheel, a Staff Backend Engineer at GitLab and Chair of the OpenBao Technical Steering Committee. I'm here to talk about OpenBao and its usage at GitLab.
OpenBao returns from FOSDEM '25 and OpenUK's State of Open Con this week, reflecting on the travels and activities of the events.
Many thanks to Fatima for running the community calls in our absence!
photo credit: nicolas; pictured: alex
FOSDEM '25 was Alex's first time speaking at a conference and we are happy to report it was a success! The details of the talk were saved and will be published in a follow-up blog along with the recording when it is made available from the conference. It was great to meet so many people interested in identity and access management and OpenBao's role in solving secrets management problems, at GitLab and beyond.
Follow along with OpenBao's travels this week as we attend FOSDEM '25 and State of Open Con!
Check out Alex's talk at FOSDEM, on Sunday, February 2nd, at 2:05 PM GMT+1 in room UA2.118 (Henriot) as part of the Identity and Access Management track.
If you can't attend in person, it will also be live streamed.
From snowy Minnesota, BaoBao took its first ride to London Heathrow to begin its voyage to FOSDEM '25. With a brief layover, it explored King's Cross and the Coal Drops Yard. Rich with history, this area has long been used as a rail hub for the UK and now is connected to Europe via the Channel Tunnel.
I'm happy to share that OpenBao will be present at two conferences in February: FOSDEM '25 in Brussels and State of Open Con 2025 in London!
The second half of 2024 saw several fabulous RFCs from different contributors to OpenBao. Here's a few worth highlighting and how you can get involved!
We are thrilled to announce the availability of OpenBao v2.1.0, focused on safety and scalability improvements!
This release spent some time laying the groundwork for safety and scalability improvements for releases to come. With the help of the community, OpenBao will now take advantage of transactional storage semantics from its underlying data store, giving operators and plugin developers confidence in the consistency of storage writes. This storage safety allows us to focus on alternative storage layouts for improving scalability, for instance, increasing the maximum number of mount table entries past the single-entry limit.
This release also features contributions from many new and repeat contributors; thank you all!
OpenBao, like its upstream, favors the raft internal storage engine.
While more complex than relying on a database for replication, this storage
engine allows us to have lower latency on read operations, because it uses
a local K/V implementation based on B+-trees. For workloads
with low writes but high reads (typical of most uses of K/V secrets), this
trade off allows for the best performance.
An earlier blog post talked about the availability of
transactions in the main branch, this post will focus on
the technical details of implementing transactions.
Hey everyone! I’m Fatima and I’m excited to share how my OpenBao journey started! I had been working on app development but was eager to break into the cybersecurity world. So I browsed through various open-source projects and stumbled upon OpenBao. The project’s purpose caught my interest and, of course, the little bao mascot sealed the deal so I decided to dive in and set it up.
While running OpenBao tests on my Mac, I ran into a minor compatibility error. Instead of getting frustrated, I saw it as an opportunity to contribute. I submitted my first issue to the OpenBao repository, worked on a fix, and a few days later, my pull request (PR) was approved! The excitement of having my first merged PR got me motivated to try out another issue, which also got merged later! After lurking around the repo for a few days, my mentor, Alex reached out to me with this wonderful opportunity and that is how my OpenBao journey began!
Recently we merged the last of the transactional storage pull requests, including PostgreSQL support!
I'm pleased to announce that our first direction and roadmap document has been approved by the TSC!
This represents a major commitment to openness for this project. Historically, upstream hasn't published an open roadmap or collaborated with the community on a shared vision and direction for their project.