IT: Difference between revisions
Avijayaram (talk | contribs) (Change all irc:// URIs to use ircs:// instead, because it's good hygiene) |
|||
| (19 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
= Who we are = | = Who we are = | ||
[https://blog.mozilla.org/it/ Mozilla IT] maintains the computers, networks and Internet presence Mozilla uses to fulfill the [https://www.mozilla.org/about/manifesto.html Mozilla Manifesto], supporting more than 1,000 servers and millions of users. | |||
== [[IT/Mozilla_Rocks_IT|Mozilla Rocks IT]] == | |||
Mozilla IT does many things, found out how [[IT/Mozilla_Rocks_IT|Mozilla Rocks IT]] | |||
= Where can you find us? = | = Where can you find us? = | ||
On IRC, on the server <tt>irc.mozilla.org</tt>: | On IRC, on the server <tt>irc.mozilla.org</tt>: | ||
* <tt>[ | * <tt>[ircs://irc.mozilla.org/%23moc #moc]</tt>: Mozilla Operations Center channel | ||
* <tt>[ | * <tt>[ircs://irc.mozilla.org/%23releng #releng]</tt>: Release Engineering | ||
* <tt>[ | * <tt>[ircs://irc.mozilla.org/%23db #db]</tt>: Database Administration | ||
On the web, our blog is at <tt>[http://blog.mozilla.org/it/ http://blog.mozilla.org/it/]</tt>. | On the web, our blog is at <tt>[http://blog.mozilla.org/it/ http://blog.mozilla.org/it/]</tt>. | ||
| Line 13: | Line 18: | ||
= How to get involved = | = How to get involved = | ||
* [[IT/Community]] | * [[IT/Community]] | ||
* [[IT/CommunitySysadmin]] | * [[IT/CommunitySysadmin]] | ||
* [[IT/AirMozilla]] | * [[IT/AirMozilla]] | ||
* [[IT/WeeklyMinIT]] | |||
= Procedures = | = Procedures = | ||
| Line 23: | Line 28: | ||
= Teams = | = Teams = | ||
== | == End User Services == | ||
The | The Service Desk Team is a globally-distributed team that is dedicated to ensuring Mozilla employees have the hardware and software to further the mission. | ||
Mozilla staff can contact the team [https://mozilla.service-now.com/ here]. | Mozilla staff can contact the team [https://mozilla.service-now.com/ here]. | ||
== | ==Net Ops == | ||
The Network Operations team supports upstream Internet access for Mozilla offices and datacenters. | The Network Operations team supports upstream Internet access for Mozilla offices and datacenters. | ||
== DC Ops == | == DC Ops == | ||
The DataCenter Operations team designs and supports Mozilla's datacenters and Point of Presence (PoP) servers at strategic Internet hubs across the globe. | |||
* [http://www.wired.com/wiredenterprise/2012/10/data-center-servers/ Data Center Servers Suck — But Nobody Knows How Much] - Wired | |||
==Mozilla Operations Center [MOC]== | |||
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 | ==Systems Infrastructure== | ||
Manages the core server infrastructure behind Mozilla including DHCP, DNS, NTP and E-mail. They are responsible for Highly-Critical Infrastructure, and manage the configuration across servers. | |||
Manages the core server infrastructure behind Mozilla including | |||
* [https://www.youtube.com/watch?v=fwedWHzGgno Scaling Puppet or How we do it at Mozilla] - PuppetConf | * [https://www.youtube.com/watch?v=fwedWHzGgno Scaling Puppet or How we do it at Mozilla] - PuppetConf 2012 talk. | ||
* [http://puppetlabs.com/puppet-labs-podcast/7/ Puppet at Mozilla Podcast] | * [http://puppetlabs.com/puppet-labs-podcast/7/ Puppet at Mozilla Podcast] | ||
* [http://www.oscon.com/oscon2011/public/schedule/detail/19130 Moving Day: Migrating Your Big Data from A to B] - OSCON | * [http://www.oscon.com/oscon2011/public/schedule/detail/19130 Moving Day: Migrating Your Big Data from A to B] - OSCON 2012 talk. | ||
== | ==Web Ops == | ||
The Web Operations teams manages more than 1,000 websites for all the past and current Mozilla projects. | The Web Operations teams manages more than 1,000 websites for all the past and current Mozilla projects, including mozilla.org and getfirefox.com. Learn [https://air.mozilla.org/mozilla-webops/ how the Web Operations team works]. | ||
== | ==Data team == | ||
The | The Data Team manages clusters of Postgres and MySQL-like databases and many other data and metrics systems and processes. You can read about their [https://blog.mozilla.org/it/category/itdesktop/databases/ weekly progress]. | ||
== Air Mozilla == | |||
[https://wiki.mozilla.org/IT/AirMozilla Air Mozilla] provides recordings of regular Mozilla Project meetings, MozCamp talks, and other Mozilla gatherings for community members around the world to enjoy. | [https://wiki.mozilla.org/IT/AirMozilla Air Mozilla] provides recordings of regular Mozilla Project meetings, MozCamp talks, and other Mozilla gatherings for community members around the world to enjoy. | ||
Watch them at [https://air.mozilla.org/ https://air.mozilla.org/] | |||
Latest revision as of 16:40, 28 August 2018
Who we are
Mozilla IT maintains the computers, networks and Internet presence Mozilla uses to fulfill the Mozilla Manifesto, supporting more than 1,000 servers and millions of users.
Mozilla Rocks IT
Mozilla IT does many things, found out how Mozilla Rocks IT
Where can you find us?
On IRC, on the server irc.mozilla.org:
On the web, our blog is at http://blog.mozilla.org/it/.
Reach out to us on the at https://lists.mozilla.org/listinfo/it/.
How to get involved
Procedures
Teams
End User Services
The Service Desk Team is a globally-distributed team that is dedicated to ensuring Mozilla employees have the hardware and software to further the mission.
Mozilla staff can contact the team here.
Net Ops
The Network Operations team supports upstream Internet access for Mozilla offices and datacenters.
DC Ops
The DataCenter Operations team designs and supports Mozilla's datacenters and Point of Presence (PoP) servers at strategic Internet hubs across the globe.
Mozilla Operations Center [MOC]
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
Manages the core server infrastructure behind Mozilla including DHCP, DNS, NTP and E-mail. They are responsible for Highly-Critical Infrastructure, and manage the configuration across servers.
- Scaling Puppet or How we do it at Mozilla - PuppetConf 2012 talk.
- Puppet at Mozilla Podcast
- Moving Day: Migrating Your Big Data from A to B - OSCON 2012 talk.
Web Ops
The Web Operations teams manages more than 1,000 websites for all the past and current Mozilla projects, including mozilla.org and getfirefox.com. Learn how the Web Operations team works.
Data team
The Data Team manages clusters of Postgres and MySQL-like databases and many other data and metrics systems and processes. You can read about their weekly progress.
Air Mozilla
Air Mozilla provides recordings of regular Mozilla Project meetings, MozCamp talks, and other Mozilla gatherings for community members around the world to enjoy.
Watch them at https://air.mozilla.org/