From MozillaWiki
Jump to: navigation, search


Bugzilla Project maintains several servers to run services needed by the project. Some of these are also used by other projects. Bugzilla Project also utilizes various services that are hosted and maintained by Mozilla.

Bugzilla uses CentOS 5 and Red Hat Enterprise Linux (RHEL) 6 servers that are updated to latest minor releases. Current versions are CentOS 5.10 and RHEL 6.5 (Dec 2013).

Mozilla-hosted ESX

  • VMware ESX platform is maintained by Mozilla in the SCL3 colo.


A virtual CentOS 5 server for shared development environment including development Bugzilla installations.

  • Slave DNS for internal zones.
    • All zones are transferred from master DNS infra.bugzilla.lan.
    • Please read master DNS description for other configuration details.


A virtual server for testing Windows support. Currently unused.


A virtual server for testing Oracle database support. Currently unused.

bugzilla1.community.scl3.mozilla.com AKA cg-bugs01.bugzilla.lan

A RHEL 6 server that hosts MySQL and PostgreSQL database servers for internal use by other servers.

bugzilla2.community.scl3.mozilla.com AKA cg-bugs02.bugzilla.lan

A RHEL 6 server that hosts virtual servers.

  • Uses qemu+kvm virtualization to run up to four (4) RHEL 6 virtual servers.

updates.bugzilla.org AKA update.bugzilla.lan

A virtual RHEL 6 server for Bugzilla update services.

  • Delivers Bugzilla version information XML to Bugzilla instances all around the world.
  • Uses nginx as a high performance web server.


A virtual RHEL 6 server for IRC bots.

  • Infobot word that connects to various channels in irc.mozilla.org IRC server to deliver factoids.
  • Supybot bugbot that keeps an eye on bugs in various major Bugzilla installations.
    • Receives bugmail from various major Bugzilla installations.
    • Maintains a presence on Freenode, Mozilla and GNOME IRC networks on various channels for announcing bug changes and fetching bug information.


A virtual RHEL 6 server for basic infrastructure services.

  • Master DNS for internal zones.
    • Zones include bugzilla.lan, 99.168.192.in-addr.arpa, 122.168.192.in-addr.arpa and bugzilla.jp that are accessible only internally by Bugzilla servers. Additionally, includes standard zones required to be in every DNS.
    • Forwards all external name requests to google-public-dns-a.google.com and google-public-dns-b.google.com but will fall back to resolving requests directly by itself if none of the forwarders are available.
  • Local RPM building and hosting.
    • Log in as build user to build/update RPMs because that user has a correctly configured RPM build environment.
    • Hosts repo.bugzilla.lan yum repository that provides all the locally built packages. Copy repository configuration file found at http://repo/bz.repo to /etc/yum.repos.d/ to use the local repository in a local server.
    • Save new RPMs to server in /usr/share/nginx/published-rpms directory and run ./update-repo.sh script as build user to update repository metadata.
  • Puppet Master to automate configuration of other Bugzilla Project servers.

bugzilla3.community.scl3.mozilla.com AKA cg-bugs03.bugzilla.lan

A RHEL 6 server for hosting automated Bugzilla demo installations.

  • Hosts demo.bugzilla.org service.
  • Uses local MySQL database for the installations.
  • Replicates bugs_tip, bugs_bugzilla4_4_branch, bugs_bugzilla4_2_branch and bugs_bugzilla4_0_branch databases from landfill that are used as a basis for the new installations.