openstack team mailing list archive
Mailing list archive
I'd like to announce my candidacy for a seat on the OpenStack
- General background -
I have over 15 years of experience designing and building distributed
systems. I am currently a Senior Software Developer at Rackspace,
where I have been for a 2 and a half years now. Most of my time
at Rackspace has been spent working on OpenStack as both a developer and
a technical leader. My first week at Rackspace was spent at the very first
OpenStack Design Summit in Austin where the project was announced.
Prior to working at Rackspace, I held various roles over 14 years
at Concentric Network Corporation/XO Communications including Senior
Software Architect and eventually Director of Engineering. My main
focus there was on an award winning web/email hosting platform which
we'd built to be extremely scalable and fault tolerant. While my
name is not on this patent, I was heavily involved with the development
and design that led to US6611861.
- Why am I interested? -
I have strong feelings for OpenStack and I want to help take it to
the next level. I have a lot of technical knowledge and experience
building scalable distributed systems.
During most of my past experience, I haven't had the luxury of having
access to a lot extremely fast hardware, so it's been important to
make software as performant as possible. I've also had to put lots of
effort into having 0 downtime, meaning code can be updated seamlessly
without dropping clients. I've also been one to lead host and software
security efforts so I have a lot of strong feelings in this area.
I am extremely interested in using this experience to make OpenStack
perform well, be secure, be more easily pluggable, and easy to use!
- OpenStack contributions -
As I mentioned above, I was at the very first design summit, so
I've been involved with the project from the beginning. I started
the initial work for nova-scheduler shortly after the project was
opened. I also implemented the RPC support for kombu, making sure
to properly support reconnecting and so forth which didn't work
quite so well with the carrot code. I've contributed a number of
improvements designed to make nova-api more performant. I've worked on
the filter scheduler as well as designing and implementing the
first version of the Zones replacement that we named 'Cells'.
I'm currently looking forward to restructuring our use of DB API to better
support upgrades w/ schema changes as well as committing an alternative
DB backend implementation for mysql that significantly reduces how long
we block on DB API calls compared to sqlalchemy.
- Summary -
I feel my years of experience contributing to and leading large scale
technical projects along with my knowledge of the OpenStack projects
will provide a good foundation for technical leadership.