Development, deployment, automation, and Integration
I'm involved in the following OpenStack projects: Deploys OpenStack using OpenStack itself (Tripleo),OpenStack Networking integration for containers (Kuryr),Command-line interface for all OpenStack services (Openstackclient),Ansible playbooks to deploy OpenStack (Openstack-ansible),Ansible playbooks and roles for deployment (OpenStackAnsible)
What is your relationship to OpenInfra, and why is its success important to you?
My relationship with OpenInfra is akin to that of a dedicated gardener: nurturing, occasionally pulling weeds, but always aiming for a thriving ecosystem. I have been kneedeep in OpenStack for a long time, contributing code, shaping architectural decisions, and championing its adoption in the enterprise sphere. OpenInfra's success matters to me because it's about leveling the playing field, breaking the stranglehold of proprietary solutions and proving that open source isn't just for weekend hobbyists but is the backbone of serious, scalable infrastructure.
What would you say is your biggest contribution to OpenInfra and/or OpenStack's success to date?
Convincing a risk-averse enterprise to abandon their gold-plated, vendor-locked infrastructure in favor of Open-Infrastructure, specifically OpenStack. Along this enterprise meets open-source journey, I've penned some code, launched a couple projects, and worked on delivering large systems for global products.
My experience with non-profits outside of OpenInfra is about as extensive as a snowman's experience with summer, practically none. However, within the OpenInfra ecosystem, I've been deeply entrenched throughout the years. I've served on various committees and working groups, and served on the Technical Committee.
My hands on experience has equipped me with the skills necessary for a board member role. I've mastered the art of herding cats and navigating the labyrinth of open-source governance, which is its own unique adventure. I believe my experience is key in striking a balance between passionate community contributors and balancing diverse interests to achieve common goals. So, while I may not have a Rolodex full of non-profit board positions, I bring a wealth of relevant experience from the heart of OpenInfra itself.
The Board serves as the strategic compass for OpenInfra, guiding the organization toward its mission of fostering open-source infrastructure innovation. Its role is to provide governance, oversight, and strategic direction, ensuring that the community's efforts align with broader objectives. By setting policies, allocating resources, and facilitating collaboration among stakeholders, the Board helps maintain the health and growth of projects like OpenStack. Ultimately, the Board's leadership is essential for sustaining a vibrant ecosystem that continues to drive technological advancement and meets the evolving needs of users worldwide.
Over the next year, the Board's top priority should be to ensure that OpenInfra doesn't just stay relevant but leads the charge in open-source infrastructure innovation. This means cutting through the noise and focusing on delivering tangible value to the community, enhancing scalability, simplifying systems, improving interoperability across platforms, and highlighting how different open infra projects can be leveraged to meet the goals of enterprises large and small. Let's prioritize initiatives that empower users and developers alike. In essence, the Board should steer the ship with a clear, strategic vision that propels OpenInfra forward, not just keeps it afloat.
Kevin has already been nominated by: