Merge "Elaborate on the business value of infra admins"
This commit is contained in:
commit
24cfdbc971
|
@ -116,7 +116,8 @@ PTL or the Technical Committee sponsor for this item (dhellmann).
|
|||
2. Community Infrastructure Sysadmins
|
||||
=====================================
|
||||
|
||||
*TC Sponsor: Jeremy Stanley (fungi)*
|
||||
Description
|
||||
-----------
|
||||
|
||||
The :ref:`project-infrastructure` team is responsible for designing,
|
||||
building and maintaining the systems that are used in the day to day
|
||||
|
@ -158,10 +159,51 @@ substantial opportunity both for people who have experience in those
|
|||
technologies as well as anyone wishing to gain more familiarity with
|
||||
them.
|
||||
|
||||
Join the #openstack-infra channel on the Freenode IRC network or
|
||||
reach out through the openstack-infra mailing lists on
|
||||
lists.openstack.org if you would like to get involved. It's a
|
||||
rewarding chance to learn and help others, but most of all it's fun!
|
||||
Value
|
||||
-----
|
||||
|
||||
Reusability
|
||||
~~~~~~~~~~~
|
||||
|
||||
The infrastructure team leverages resources donated from companies operating
|
||||
OpenStack services and manages their own OpenStack deployment. The community
|
||||
uses the software it produces as a tool for testing it. Every day, contributors
|
||||
submit thousands of patches for review. Infrastructure tools deploy each patch
|
||||
and test it against thousands of tests and scenarios. This volume provides an
|
||||
opportunity to improve the software we write by giving us first-hand experience
|
||||
with issues at scale. The benefit of fixing these issues for the OpenStack CI
|
||||
system is two-fold:
|
||||
|
||||
1. It makes the test platform more stable and robust
|
||||
2. Products or services benefits from the fix being applied upstream
|
||||
|
||||
Don't Repeat Yourself or Your Testing (DRY)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The culture built around extensive testing in OpenStack makes it easier for us
|
||||
to trust patches proposed for review. We've integrated this culture into our
|
||||
review process. Duplicating a social and technical CI system of this size takes
|
||||
incredible amounts of time, people, and patience. Bolstering the CI system we
|
||||
already have in place allows you to focus on testing that is specific to your
|
||||
product or service.
|
||||
|
||||
Immediate Feedback
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The OpenStack CI system is the backbone of feedback for contributors and
|
||||
operators. Users get this feedback early, ideally before the patch lands.
|
||||
Ensuring early feedback through a robust CI system and testing means fewer
|
||||
surprises down the road when you attempt to integrate your product into a new
|
||||
release or deploy a new version of a service.
|
||||
|
||||
Contact
|
||||
-------
|
||||
|
||||
Join the #openstack-infra channel on the Freenode IRC network or reach out
|
||||
through the openstack-infra mailing lists on lists.openstack.org if you would
|
||||
like to get involved. It’s a rewarding chance to learn and help others, but
|
||||
most of all it’s fun! The Technical Committee sponsor for this initiative is
|
||||
Jeremy Stanley (fungi).
|
||||
|
||||
3. Designate Contributors
|
||||
=========================
|
||||
|
|
Loading…
Reference in New Issue