Open Stack

I would also like to nominate myself for the role of Tuskar PTL.

I am a senior engineer at Red Hat where I have been part of the core 
Tuskar engineering team since its inception, participating in the 
various discussions and technical decisions for the initial Tuskar proof 
of concept. I helped define our integration points with existing 
OpenStack projects which required understanding of Triple O, Heat and 
Nova Bare Metal.

Over the past few years I have been involved with building cross cloud 
management tools (Aeolus, Deltacloud). I chaired the Aeolus technical 
cabal and led efforts on the Template and Image Management tool 'TIM'. 
During this time I also designed and implemented a number REST APIs and 
recently contributed the initial Ironic REST API design spec. I have 
experience integrating with a number of other OpenStack projects: 
Glance, Keystone and Horizon from building out a proof of concept for an 
OpenStack image building service: 
http://www.youtube.com/watch?v=MdBM4HA3QUk. I have a good overall 
understanding of what each project offers and how we can utilize them to 
achieve our goal in Tuskar.

I am convinced that the right approach with Tuskar is to act as a 
consumer of existing OpenStack projects, utilizing the services these 
projects offer as much as possible.  This should allow us to keep a 
tight focus on our main goal of 'Deploying and managing OpenStack at 
large scales'. To achieve this we'll need to be heavily involved in the 
OpenStack community at large and actively contributing features to 
upstream projects when necessary.

I am very excited about the Tuskar project and becoming more involved 
with the OpenStack community at large, watching Tuskar grow over the 6 
months should be very interesting.

Regards
Martyn


On 22/08/13 14:54, Dolph Mathews wrote:

>
> On Thu, Aug 22, 2013 at 8:38 AM, Don Schenck 
> <don.schenck at rackspace.com <mailto:don.schenck at rackspace.com>> wrote:
>
>     Help a newbie: "PTL"??
>
>
> "Project Technical Leads (PTLs) lead individual projects. A PTL is 
> ultimately responsible for the direction for each project, makes tough 
> calls when needed, organizes the work and teams in the project and 
> determines if other forms of project leadership are needed. The PTL 
> for a project is elected by the body of contributors to that 
> particular project."
>   - https://wiki.openstack.org/wiki/Governance/Foundation/Structure
>
>
>     -----Original Message-----
>     From: Tomas Sedovic [mailto:tsedovic at redhat.com
>     <mailto:tsedovic at redhat.com>]
>     Sent: Thursday, August 22, 2013 8:55 AM
>     To: openstack-dev at lists.openstack.org
>     <mailto:openstack-dev at lists.openstack.org>
>     Subject: [openstack-dev] Tuskar PTL candidacy
>
>     I would like to nominate myself for the role of Tuskar PTL.
>
>     While not senior by any stretch of imagination, I did QA
>     automation for three years and development for another three
>     (professionally; I've been coding on my own since I was 13) so I'm
>     familiar with both sides of the table.
>
>     I've helped with the development of the Heat project during its
>     first six months and got one of the early releases out the door
>     (pre-incubation iirc). I'm familiar with the OpenStack processes,
>     I'd attended weekly Heat meetings and been helping my colleagues
>     with the transition from a Ruby on Rails github workflow to the
>     OpenStack way of development.
>
>     I'll freely admit I'm not the most knowledgeable person around.
>     But I'm not afraid to ask questions or admit being wrong and I
>     tend to learn quickly.
>
>     Apart from more features and stability, I'll push Tuskar towards
>     clear documentation and friendliness to newcomers.
>
>     --
>     Tomas Sedovic
>
>     _______________________________________________
>     OpenStack-dev mailing list
>     OpenStack-dev at lists.openstack.org
>     <mailto:OpenStack-dev at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>     _______________________________________________
>     OpenStack-dev mailing list
>     OpenStack-dev at lists.openstack.org
>     <mailto:OpenStack-dev at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> -- 
>
> -Dolph
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130823/b352e436/attachment.html>