MDN Web Docs infrastructure
This repo is maintained by the MDN Web Docs operations team, which includes MDN developers, Mozilla IT, and Mozilla Marketing Engineering and Operations (MozMEAO) site reliability engineers (SREs).
It was originally established and maintained by MozMEAO during the AWS update in 2017-2018. In 2018, MDN engineering moved to Emerging Technologies, and this repo was forked from mozmeao/infra to the MDN org.
Tools we use
Automation and infrastructure tools:
- Docker
- software containerization
- Amazon Web Services
- our primary cloud services platform
- Jenkins
- including Groovy scripting
- Terraform
- declarative infrastructure provisioning
- Python
- including boto
- jq
- json transformations and queries
Container technologies:
- Kubernetes
- container orchestration in the cloud
- see this page for more info.
- DockerHub
- public image registry
Monitoring tools:
- New Relic
- performance monitoring
- Papertrail
- centralized logging
- FluentD
- collecting logs from Kubernetes pods
How we manage our work
Our goal is to use the same principle as open source development for infrastructure management. We try to keep the planning, discussions, code, documentation, and processes open to the community. Operational access is limited to staff, but working in the open allows more staff members to take on tasks, and helps new staff get up to speed quickly.
Some data, such as API keys, are sensitive. These items are stored elsewhere and applied in production. Sensitive issues are discussed in confidential Bugzilla issues.
The MDN team uses 3-week sprints to break up work into manageable milestones. The MDN team work is tracked in GitHub issues and milestones using ZenHub. See the sprints wiki for more information.
Contributing
If you'd like to make a contribution, or you've found an issue with our work, please submit an issue and/or pull request. We're happy to take a look, however, a timeframe for review cannot be guaranteed.
Contacting us
We're in the #mdndev
channel on IRC.