I would like to announce my TC candidacy. I work full time for HP where I am the architect and technical lead for the core OpenStack Engineering team, with responsibility for the architecture and deployment of the OpenStack Infrastructure projects (Nova, Neutron, Cinder, Glance, Swift) across a range of HP Products including our Public Cloud, which is one of the largest public deployments and has been tracking upstream trunk for the last 18 months.
I have been working with OpenStack since Diablo, and am continually in awe at what we, as a community, have managed to create over the last few years. I believe that OpenStack has now reached the point of maturity where Operator and Deployer perspectives need to have a strong voice in how the services evolve. My position in HP as the architect for the Infrastructure service of HP's Public Cloud, as well as being an active contributor and reviewer to Nova, puts me in a strong position to provide those perspectives. As an active developer in Nova I have been a strong advocate of bringing improved formality to the Blueprint review process, both to allow other perspectives to be incorporated and to address as early as possible some of the issues that have in the past been overlooked until the final stages of implementation. Although still in its early days, that new process has had very positive feedback, and is an example of the kind of areas where I think the TC should be seeking to make a difference across all projects. While respecting and valuing the rights of each project to have a degree of autonomy, I believe that the TC needs to take a strong role in "joining the dots" and making sure that a change required by one project (such as for example the introduction of the Keystone V3 API) has a supporting plan of how it can be incorporated into the roadmap of other projects - not through dictating to the projects but by working with the PTLs to ensure that there is a smooth and agreed transition plan, and by resolving conflicts in priorities. Each project has its own highly skilled, and to a degree specialized, community and a list of features that they want to introduce, and I want to see the TC play a role in monitoring those changes to look for, and seek to resolve, conflicts and overlaps. This is a role I already play with HP, and I would welcome the opportunity to bring that experience to OpenStack. Thanks Phil Day
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
