Jump to: navigation, search

Difference between revisions of "Governance/ElectionsSpring2012/Eoghan Glynn"

 
m (Text replace - "__NOTOC__" to "")
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
__NOTOC__
+
 
 
= Eoghan Glynn =
 
= Eoghan Glynn =
 
 
I'm running for the Glance PTL position.
 
I'm running for the Glance PTL position.
  
 
== Since the last elections, what areas have you focused on and what contributions have you made in order to improve your project? ==
 
== Since the last elections, what areas have you focused on and what contributions have you made in order to improve your project? ==
 +
Since becoming active in the [[OpenStack]] community at the start of this year, I've been completely focussed on the Glance project, mainly around general quality & stability issues (read: hoovering up the bug backlog).
  
Since becoming active in the [[OpenStack]] community at the start of this year, I've been completely focussed on the Glance project, mainly around general quality & stability issues (read: hoovering up the bug backlog).
+
In that time I've rationalized the intertwined core & paste configuration, made glance-control a fully fledged process launcher and also initiated/implemented several blueprints, including performance improvements via pysendfile and support for copying image content from external sources.
 
 
I've also initiated and implemented several blueprints, including performance improvements via pysendfile and support for copying image content from external sources.  
 
  
 
== What are the most pressing/important issues facing your project? ==
 
== What are the most pressing/important issues facing your project? ==
 
 
As a matter of priority, I think we need to get our hands around the v2.0 API. As proposed this includes many advances over v1.1, and I'm sure there are further areas for improvement that will arise as the proposal is built out. I have a particular interest in RESTful API design and implementation, with experience doing this in an [https://fedorahosted.org/rhevm-api open source setting].
 
As a matter of priority, I think we need to get our hands around the v2.0 API. As proposed this includes many advances over v1.1, and I'm sure there are further areas for improvement that will arise as the proposal is built out. I have a particular interest in RESTful API design and implementation, with experience doing this in an [https://fedorahosted.org/rhevm-api open source setting].
  
Line 19: Line 16:
  
 
== What is your relationship to [[OpenStack]] & why is its success important to you and/or your company? ==
 
== What is your relationship to [[OpenStack]] & why is its success important to you and/or your company? ==
 
 
I've been active in the [[OpenStack]] community since the start of 2012, first as a Glance contributor and then latterly as a member of glance-core and glance-drivers.
 
I've been active in the [[OpenStack]] community since the start of 2012, first as a Glance contributor and then latterly as a member of glance-core and glance-drivers.
  

Latest revision as of 23:29, 17 February 2013

Eoghan Glynn

I'm running for the Glance PTL position.

Since the last elections, what areas have you focused on and what contributions have you made in order to improve your project?

Since becoming active in the OpenStack community at the start of this year, I've been completely focussed on the Glance project, mainly around general quality & stability issues (read: hoovering up the bug backlog).

In that time I've rationalized the intertwined core & paste configuration, made glance-control a fully fledged process launcher and also initiated/implemented several blueprints, including performance improvements via pysendfile and support for copying image content from external sources.

What are the most pressing/important issues facing your project?

As a matter of priority, I think we need to get our hands around the v2.0 API. As proposed this includes many advances over v1.1, and I'm sure there are further areas for improvement that will arise as the proposal is built out. I have a particular interest in RESTful API design and implementation, with experience doing this in an open source setting.

We also need to continue to make incremental improvments in Glance code quality. Towards that end, I'd propose an audit of test coverage and a concerted effort to address any weak points uncovered. In addition, I'd like us to focus more on smoking out issues of performance and scalability, that'll require more extensive testing at scale.

Finally, I feel we should be forging a closer relationship with Swift and become more active in testing our storage backends on a routine basis (as opposed to these tests being disabled by default). As the "closest customer" of Swift, the Glance project should be the first point of providing feedback to the Swift team on their API and also on any issues or regressions that may arise.

What is your relationship to OpenStack & why is its success important to you and/or your company?

I've been active in the OpenStack community since the start of 2012, first as a Glance contributor and then latterly as a member of glance-core and glance-drivers.

Having previously worked on both open source virtualization and proprietary cloud infrastructure, I'm convinced that open cloud is the only way to go. OpenStack is clearly the open cloud project with the most momentum and traction in the community, and as such I'm very eager to contribute to its success.

Fortunately my employer, Red Hat, is supportive of this ambition and happy pay my salary while I focus fulltime on upstream work. Yay!