IT: Difference between revisions

Jump to navigation Jump to search
176 bytes added ,  21 March 2017
Updated the MOC section as things have changed over time. It's now current.
(Teams not under systems any more)
(Updated the MOC section as things have changed over time. It's now current.)
Line 40: Line 40:
* [http://www.wired.com/wiredenterprise/2012/10/data-center-servers/ Data Center Servers Suck — But Nobody Knows How Much] - Wired
* [http://www.wired.com/wiredenterprise/2012/10/data-center-servers/ Data Center Servers Suck — But Nobody Knows How Much] - Wired


==Mozilla Operations Center==
==Mozilla Operations Center [MOC]==
When [http://www.wired.com/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux/ leapsecond bugs confuse servers all over the Internet], the MOC is there to [https://bugzilla.mozilla.org/show_bug.cgi?id=769972 file the bug]. They are Mozilla's first line of defence on the Internet, monitoring servers 24/7.
The Mozilla Operation Center is a 24x7 IT function with a purpose to support Mozilla's critical services. It provides this through standard approaches - incident management and proactive monitoring. The MOC has a single identity and only known as "MOC" across IRC (#moc), email, and Bugzilla. The MOC operates in 4 MozSpaces: San Francisco, Mountain View, Portland, and London. Through rotational shifts between these 4 hubs, the MOC achieves around the clock coverage every day of the year.


==Systems Infrastructure==
==Systems Infrastructure==
1

edit

Navigation menu