Open Stack

Robert Collins wrote:
> I'm interested in serving on the OpenStack TC.

Confirmed.

> 
> # About me
> 
> I've been working on OpenStack for only a year now, since joining
> Monty's merry gang of reprobates<wink/> at HP. However I've been
> entirely focused on networking and distributed systems since ~2000 -
> having as highlights -core membership in the squid HTTP cache team,
> one of the founders of the Bazaar DVCS project, and a huge mix of
> testing and development efficiency thrown into the mix :). Earlier
> this year I was privileged to become a Python Software Foundation
> member, and I'm keen to see us collaborating more with upstream,
> particularly around testing.
> 
> I live in New Zealand, giving me overlap with the US and with a lot of
> Asia, but talking with Europe requires planning :)
> 
> # Platform
> 
> At the recent TripleO sprint in Seattle I was told I should apply for
> the TC; after some soul searching, I think yes, I should :).
> 
> Three key things occurred to me:
> 
> All of our joint hard work to develop OpenStack is wasted if users
> can't actually obtain and deploy it. This is why we're working on
> making deployment a systematic, rigorous and repeatable upstream
> activity: we need to know as part of the CI gate that what we're
> developing is usable, in real world scenarios. This is a
> multi-component problem: we can't bolt 'be deployable' on after all
> the code is written : and thats why during the last two cycles I've
> been talking about the problems deploying from trunk at the summits,
> and will continue to do so. This cross-program, cross-project effort
> ties into the core of what we do, and it's imperative we have folk on
> the TC that are actually deploying OpenStack (TripleO is running a
> live cloud -https://wiki.openstack.org/wiki/TripleO/TripleOCloud- all
> TripleO devs are helping deploy a production cloud).
> 
> I have a -lot- of testing experience, and ongoing unit and functional
> testing evolution will continue to play a significant role in
> OpenStack quality; the TC can help advise across all projects about
> automated testing; I'd be delighted to assist with that.
> 
> Finally, and I'm going to quote Monty here: "As a TC member, I will
> place OpenStack's interests over the interests of any individual
> project if a conflict between the project and OpenStack, or a project
> with another project should a arise." - I think this is a key attitude
> we should all hold: we're building an industry changing platform, and
> we need to think of the success of the whole platform as being *the*
> primary thing to aim for.
> 
> Thank you for your consideration,
> Rob
> 


-- 
Thierry Carrez (ttx)