During the Rocky Project Teams Gathering (Feburary/March 2018), The contributors in the room at that time took a few minutes to write out each contributor’s vision of where they see ironic in five years time.
After everyone had a chance to spend a few minutes writing, we went around the room and gave every contributor the chance to read their vision and allow other contributors to ask questions to better understand what each individual contributor wrote. While we were doing that, we also took time to capture the common themes.
This entire exercise did result in some laughs and a common set of words, and truly helped to ensure that the entire team proceeded to use the same “words” to describe various aspects as the sessions progressed during the week. We also agreed that we should write a shared vision, to have something to reference and remind us of where we want to go as a community.
Below is an entirely unscientific summary of common themes that arose during the discussion among fourteen contributors.
The year is 2022. We’re meeting to plan the Z release of Ironic. We stopped to reflect upon the last few years of Ironic’s growth, how we had come such a long way to become the defacto open source baremetal deployment technology. How we had grown our use cases, and support for consumers such as containers, and users who wished to managed specialized fleets of composed machines.
New contributors and their different use cases have brought us closer to parity with virtual machines. Everyday we’re gaining word of more operators adopting the ironic community’s CMDB integration to leverage hardware discovery. We’ve heard of operators deploying racks upon racks of new hardware by just connecting the power and network cables, and from there the operators have discovered time to write the world’s greatest operator novel with the time saved in commissioning new racks of hardware.
Time has brought us closer and taught us to be more collaborative across the community, and we look forward to our next release together.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.