Firmware lifecycle & CMDB

A fleet of bare metal servers means dozens of platforms, each with several firmware components, each with a history of versions, fixes and validations. Without a source of truth, there is no quick answer to “which version runs where, and since when?”.

What I built

• Lifecycle tracking tools: from the candidate version supplied by the vendor to the deployed version, including the intermediate qualification steps.
• A contribution to the architecture of a firmware-oriented CMDB (Configuration Management Database): data model, inventory, traceability and version management.
• Integrations with validation tools and RUN operations so that the CMDB reflects what is really in the field.

Why it matters

Traceability makes incident analysis, update campaigns and supplier discussions easier. It also makes onboarding simpler: the knowledge lives in the tool, not only in people's heads.