In this week’s L8ist Sh9y Podcast, we bring on the Digital Rebar team at RackN to discuss several issues they have working on over the past few months:
- Patch Rest APIs and CLI : Scaling Challenges Require Patch
- Swagger API History and Changes : No CLI Generation
- Integrations to Existing Tools up the Stack
Topic Time (Minutes.Seconds)
Introduction 0.0 – 0.42
Intro to Digital Rebar Project 0.42 – 1.58
Patch in Rest APIs 1.58 – 4.02 (Reference: JsonPatch.com)
Why not use PUT? 4.02 – 4.53
CLI use Reference Objects 4.53 – 6.28
Examples of How Use This 6.28 – 10.55
Patch Synchronous Question 10.55 – 12.32
Swagger Built into API 12.32 – 15.44 (Reference: https://swagger.io/)
Operator view of CLI w/out Swagger 15.44 – 18.30
2 Key Points on Swagger Change 18.30 – 20.22
Integration to Other Systems 20.22 – 28.13 (Grumpy Operators Syndrome)
Learn More About Digital Rebar 28.13 – END (Digital Rebar Online Meetup Community)
Guest Podcast Attendees
- Greg Althaus, Co-Founder, CTO RackN
- Victor Lowther, Sr. Software Engineering, RackN
- Shane Gibson, Sr. Architect and Community Evangelist, RackN
Digital Rebar is the open, fast and simple data center provisioning and control scaffolding designed with a cloud native architecture. Sponsored by RackN, this community is building an extensible stand-alone DCHP/PXE/IPXE service with minimal overhead offering a quick 5 minutes to provisioning solution.
Community Mission: Embrace the Heterogeneous Nature of Data Center Operations while Eliminating Complexity and Manual Steps.




Our architectural plans for
This works for several reasons. First, much of the Digital Rebar value is delivered as content instead of in the scaffolding. Each content package has it’s own version cycle and is not tied to Digital Rebar versions. Second, many Digital Rebar features are relatively small, incremental additions. Faster releases allows content creators and operators to access that buttery goodness more quickly without trying to manage the less stable development tip.




