Confirmed users
66
edits
Web Operations/Reference Specification: Difference between revisions
Jump to navigation
Jump to search
Web Operations/Reference Specification (view source)
Revision as of 22:22, 24 July 2014
, 24 July 2014Add working model
(Add working model) |
|||
| Line 1: | Line 1: | ||
== Working Model == | |||
This is currently a rough draft document that is being developed by a small working group within the WebOps team. We are working on an iteration model where each iteration will open the discussion to a wider audience. As soon as we have progressed to a defined point we will open this discussion up to the next wider audience based on an iteration plan. Please keep in mind that this is a fluid plan and quite subject to change. Finally, we do not currently have a time-line other than we are working as fast as we can. | |||
=== Iteration plan === | |||
# Working group | |||
#* We will move to the next iteration as soon as we have is a working, repeatable prototype application. | |||
# The WebOps team | |||
#* We will move on as soon as the team reaches a consensus on the general layout and direction. | |||
#* This should be a quick iteration as the team will be consulted heavily during the first iteration. | |||
# Other teams within IT | |||
#* During this iteration we will be working with various teams within IT to help us solve technical problems for which they are the subject matter experts. | |||
#* We will be solving numerous technical problems such as: | |||
#** Automatic provisioning of VMs | |||
#** Automation of firewall rules (netflows) | |||
#** Designing a backup solution (or working with an existing solution if it is defined by that time) | |||
# Web developers within MoCo | |||
#* Our primary goal here is to ensure that we are developing a system that will serve the needs of our developers while providing them a framework they are willing (and hopefully happy) to work in. | |||
# All Mozillians | |||
#* We will open the entire plan for comment to the community. While we are currently unaware of how our decisions and actions here will affect community contributers we want to be sure that we are not overlooking anything. | |||
#* Further, we are hopeful that this project might provide some in-rodes for community contributers to take a more active roll within IT. Specifically: | |||
#** We are striving to use open source solutions | |||
#** We are developing everything possible in the open | |||
#** This entire project is documented on the Mozilla wiki (where you are now!) | |||
#** The entire Puppet tree is available on Github [https://github.com/uberj/refspec-puppet here] (will be relocated to Mozilla GitHub URL pre-production) | |||
== Overview == | == Overview == | ||
This document is designed to construct a framework which will drive automation and address the process and technology issues faced by Mozilla IT in general and the WebOps team specifically. This document is broken into three distinct sections; section one identifies the problems we are trying to solve; section two delineates decisions around how we intend to solve these problems; section three identifies the technical solutions we are choosing to implement the decisions. This document is primarily concerned with the first two sections, however there are a number of problems with ready made technical solutions. Therefore there will be a number of technical solutions presented herein. | This document is designed to construct a framework which will drive automation and address the process and technology issues faced by Mozilla IT in general and the WebOps team specifically. This document is broken into three distinct sections; section one identifies the problems we are trying to solve; section two delineates decisions around how we intend to solve these problems; section three identifies the technical solutions we are choosing to implement the decisions. This document is primarily concerned with the first two sections, however there are a number of problems with ready made technical solutions. Therefore there will be a number of technical solutions presented herein. | ||