IT/ChangeControl: Difference between revisions

From MozillaWiki
< IT
Jump to navigation Jump to search
(Created page with "{| class="fullwidth-table" |- ! Document Status ! Last Reviewed |- | <font color=red>DRAFT</font> || Aug 13 2012 |} =Introduction= As Mozilla's Infrastructure has grown, so has ...")
 
(Removed outdated information, updated remaining stub information and added a link to the correct docs for the process.)
 
(36 intermediate revisions by 8 users not shown)
Line 4: Line 4:
! Last Reviewed
! Last Reviewed
|-
|-
| <font color=red>DRAFT</font> || Aug 13 2012
| Published || Oct 20 2016
|}
|}


=Introduction=
=Introduction=
As Mozilla's Infrastructure has grown, so has the complexity of the systems.  It is apparent that we need to be more proactive about regular system updates and maintenance so we can continue supporting the Mozilla Mission.
As Mozilla's Infrastructure has grown, so has the complexity of the systems.  We need to be proactive about regular system updates and maintenance so we can continue supporting the Mozilla Mission.


To address these needs, Mozilla has established a Change Control Policy and regular Maintenance Windows.
To address these needs, Mozilla has a Change Advisory Board whose mandate is to manage the Change Control Policy and manage Scheduled Maintenance Approvals.
 
During these windows we will be performing routine system updates and other maintenance activities.  We will provide separate individual notices based on the schedules detailed below on the expected impacts of the work being performed.


=Change Advisory Board=
=Change Advisory Board=
Line 19: Line 17:


The CAB is comprised of the relevant stakeholders of each critical IT/Infrastructure service. These stakeholders are the people who can best make decisions about changes because of their understanding of the business goals, as well as technical and operational risks.
The CAB is comprised of the relevant stakeholders of each critical IT/Infrastructure service. These stakeholders are the people who can best make decisions about changes because of their understanding of the business goals, as well as technical and operational risks.
==Core CAB Members==
* Director IT/Operations (:mrz)
* Mozilla SRE/Oncall, Manager (:mrz)
* Systems, Manager (cshields)
* Netops, Manager (rpina)
* Release Engineering, Director (joduinn)
* Services Ops Director (mmayo)
* Security Assurance, Director (mcoates)
== CAB Meeting Schedule==
The CAB will meet every week to review proposed Change/Maintenance Requests.  The meeting will be chaired by Director of IT/Operations and the SRE Manager.
Meeting details:
* Tuesday 3:00p Pacifific (2300 UTC)
* Video: mrz's vidyo room (x219)
* Audio: +1 800 707 2533, pin 369, conf 9219#


=Change Management Process=
=Change Management Process=
Mozilla IT/Operations & Service Operations has the responsibility to design, manage, and maintain an infrastructure that provides the highest levels of availability, reliability, performance, and service in support of the Mozilla Mission.  
Mozilla IT/Operations & Service Operations has the responsibility to design, manage, and maintain an infrastructure that provides the highest levels of availability, reliability, performance, and service in support of the Mozilla Mission.  


An effective Change Management Process is an integral part of a comprehensive strategy to meet this responsibility.
For more information on this process, please see the [https://mana.mozilla.org/wiki/display/MOC/Change+Advisory+Board CAB documentation].
 
It is the responsibility of the Change Advisory Board to implement a change control process that will provide management of all actions and modifications that may affect the stability of any production network, system, or service.
 
The six steps for the Change Control Process will be followed when any modification is required within the production environment:
 
# Planning
# Testing
# Approval
# Communications
# Executing the Change
# Documentation
 
==Submitting a Change Request==
 
Proposed changes need to be submitted by Monday EOB Pacific time using the following Bugzilla form <font color=red><b>need form</b></font>.
 
== CAB Approval Process==
 
The CAB will follow the following process to approve change work:
* Stakeholders will add an "approved" comment in the bug
* The CAB chairperson will use the <tt>cab-approved</tt> flag to indicate this work has been approved
* The CAB chairperson will indicate this work has been schedule in the whiteboard

Latest revision as of 13:46, 20 October 2016

Document Status Last Reviewed
Published Oct 20 2016

Introduction

As Mozilla's Infrastructure has grown, so has the complexity of the systems. We need to be proactive about regular system updates and maintenance so we can continue supporting the Mozilla Mission.

To address these needs, Mozilla has a Change Advisory Board whose mandate is to manage the Change Control Policy and manage Scheduled Maintenance Approvals.

Change Advisory Board

The Change Advisory Board (CAB) is the entity that defines, and owns, Mozilla's Schedule Maintenance & Change Control Policies.

The CAB is comprised of the relevant stakeholders of each critical IT/Infrastructure service. These stakeholders are the people who can best make decisions about changes because of their understanding of the business goals, as well as technical and operational risks.

Change Management Process

Mozilla IT/Operations & Service Operations has the responsibility to design, manage, and maintain an infrastructure that provides the highest levels of availability, reliability, performance, and service in support of the Mozilla Mission.

For more information on this process, please see the CAB documentation.