adjacent community integration, governance
Steven Dake currently serves as an elected Individual Director of the OpenStack Foundation. Steve is also actively involved in bridging communities between the OpenStack's community and adjacent communities.
Steve currently serves as a core reviewer of OpenStack Kolla and contributes to the design and implementation of OpenStack Kolla heavily. Steve previously served as Kolla PTL for Newton, Mitaka, Liberty, Kilo and Juno cycles. Steve was also a Magnum core reviewer at the same time as serving the Kolla community as PTL, and contributed to the definition and implementation of the initial Magnum architecture.
Prior to gaining an interest in container technology, Steve initiated and served as PTL of OpenStack Heat with a small development team while at Red Hat, Inc. During this period, Steve served as Heat PTL for Essex, Folsom, and Grizzly.
Prior to Steve's involvement in OpenStack, Steve was primarily focused on the development of open source high availability technology leading the design and implementation of Corosync, a group communication system, which combined with Pacemaker is the de-facto standard high availability stack for Linux. During this period of his career, Steve also served as a technical community leader for the modern Linux high availability stack.
Steve enjoys Hi-Fidelity analog tube audio, electric RC car racing, and hiking with his wife, daughter, and son.
I'm involved in the following OpenStack projects: Container deployment (Kolla)
I have been working as a developer within OpenStack for roughy six years. I have led a few projects (Kolla, Heat, and co-led Magnum) as PTL for approximately 4 years. My main objective with my involvement in OpenStack over the last several years has been a focus on container integration. My biggest contribution to OpenStack's long-term success has been leading the transition of OpenStack deployment tooling to run inside container infrastructure.
I have served as an individually elected board member for the OpenStack board of directors during 2017. Prior to that effort, I have held several open source community leadership roles in various technology areas. The technology areas I have spent the most time with are related to distributed computing of which I have spent twenty years as a developer or leader.
I have also been involved in various standards bodies including the Linux Foundation's Carrier Grade Linux, Service Availabity Forum, I2O, and USB.
My breadth and depth of technology focus coupled with involvement in various standards bodies, service as a PTL to various OpenStack projects, and my recent board of director service have prepared me for the role of a board member.
The Board's role in OpenStack's success is simply to Protect, Empower, and Promote OpenStack.
Three simple words which I have found infinetely complex to execute during my 2017 OpenStack board of directors service. Fortunately there are many leaders in OpenStack and a significant body of board of director members working together to execute these three roles.
The OpenStack Board should and does serve to consolidate the wisdom and knowledge of our vast community to achieve the OpenStack Board's objectives.
I'm a big believer in the network effect that is created by our communities vast experience to further enhance our adjacent community efforts to deliver on the effort Jonathan Bryce is leading with a large contingent of other OpenStack community members to deliver adjacent community integration.
Steven has already been nominated by: