Bugzilla:Infrastructure: Difference between revisions
(→Servers: Sync with reality (hostname changes and landfill services have been migrated a long time ago)) |
m (→Servers: Moved build service to infra and updated cg-bugs01 info) |
||
Line 23: | Line 23: | ||
==== oracle.bugzilla.org ==== | ==== oracle.bugzilla.org ==== | ||
A virtual server for testing Oracle database support. Currently unused. | A virtual server for testing Oracle database support. Currently unused and unprovisioned. For more information see {{bug|831158}}. | ||
=== bugzilla1.community.scl3.mozilla.com AKA cg-bugs01.bugzilla.lan === | === bugzilla1.community.scl3.mozilla.com AKA cg-bugs01.bugzilla.lan === | ||
Line 29: | Line 29: | ||
A RHEL 6 server that runs automated tests for the Bugzilla software. | A RHEL 6 server that runs automated tests for the Bugzilla software. | ||
*Uses Tinderbox Client v2. | *Uses Tinderbox Client v2.05 to run Perl, Docs, QA, Xt and checksetup Bugzilla test suites. | ||
*Reports test results to the Tinderbox Server maintained by Mozilla. See [http://tinderbox.mozilla.org/Bugzilla/ tinderbox.mozilla.org/Bugzilla/] for latest results. | *Reports test results to the Tinderbox Server maintained by Mozilla. See [http://tinderbox.mozilla.org/Bugzilla/ tinderbox.mozilla.org/Bugzilla/] for latest results. | ||
*Current activity of the tests can be viewed by attaching to a screen session running under the ''tinderbox'' user. There's two sessions, one for QA tests (named ''qa'') and one for all the other tests (named ''tbox''). Use commands '''screen -r qa''' or '''screen -r tbox''' to attach. | *Current activity of the tests can be viewed by attaching to a screen session running under the ''tinderbox'' user. There's two sessions, one for QA tests (named ''qa'') and one for all the other tests (named ''tbox''). Use commands '''screen -r qa''' or '''screen -r tbox''' to attach. | ||
*Selenium Server v2. | *Selenium Server v2.37.0, Test::WWW::Selenium Perl module v1.24 and Firefox v24 are used by the QA tests. Be careful when updating these so that the trees won't burn unnecessarily. | ||
*Selenium Server is manually installed to the '''/usr/local/share/selenium-server/''' directory. Scripts to start it and to list related processes are in the '''/usr/local/bin/''' directory. | *Selenium Server is manually installed to the '''/usr/local/share/selenium-server/''' directory. Scripts to start it and to list related processes are in the '''/usr/local/bin/''' directory. | ||
*Firefox | *Firefox at '''/usr/lib64/firefox/firefox''' is referenced from Selenium start scripts and is installed from standard RHEL repositories. | ||
*The perl-Test-WWW-Selenium package is installed/updated from Repoforge (previously known as RPMforge) but is excluded from normal yum updates so it needs to be manually updated (use '''yum update --disableexcludes=rpmforge perl-Test-WWW-Selenium''' command) when needed. | *The perl-Test-WWW-Selenium package is installed/updated from Repoforge (previously known as RPMforge) but is excluded from normal yum updates so it needs to be manually updated (use '''yum update --disableexcludes=rpmforge perl-Test-WWW-Selenium''' command) when needed. | ||
* | *Replicates bugs_tip, bugs_bugzilla4_4_branch, bugs_bugzilla4_2_branch and bugs_bugzilla4_0_branch databases from landfill to be used in the checksetup update testing. | ||
*Uses various locally built RPM packages from [[#infra.bugzilla.org|a local repository]]) defined in the '''/etc/yum.repos.d/bz.repo''' repository configuration file. | |||
=== bugzilla2.community.scl3.mozilla.com AKA cg-bugs02.bugzilla.lan === | === bugzilla2.community.scl3.mozilla.com AKA cg-bugs02.bugzilla.lan === | ||
Line 67: | Line 68: | ||
**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. | **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 '''mradm01.mozilla.org''', '''ns2.globalnetoptex.com''' or '''ns2.lax01.mzima.net''' but will fall back to resolving requests directly by itself if none of the forwarders are available. | **Forwards all external name requests to '''mradm01.mozilla.org''', '''ns2.globalnetoptex.com''' or '''ns2.lax01.mzima.net''' 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. | |||
=== bugzilla3.scl3.mozilla.com AKA cg-bugs03.bugzilla.lan === | === bugzilla3.scl3.mozilla.com AKA cg-bugs03.bugzilla.lan === | ||
Line 74: | Line 78: | ||
*Hosts demo.bugzilla.org service. | *Hosts demo.bugzilla.org service. | ||
*Uses local MySQL database for the installations. | *Uses local MySQL database for the installations. | ||
*Replicates bugs_tip from landfill that | *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. | ||
[[Category:Bugzilla]] | [[Category:Bugzilla]] |
Revision as of 13:54, 18 January 2014
Servers
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.
landfill.bugzilla.org
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.org.
- Please read master DNS description for other configuration details.
windows.bugzilla.org
A virtual server for testing Windows support. Currently unused.
oracle.bugzilla.org
A virtual server for testing Oracle database support. Currently unused and unprovisioned. For more information see bug 831158.
bugzilla1.community.scl3.mozilla.com AKA cg-bugs01.bugzilla.lan
A RHEL 6 server that runs automated tests for the Bugzilla software.
- Uses Tinderbox Client v2.05 to run Perl, Docs, QA, Xt and checksetup Bugzilla test suites.
- Reports test results to the Tinderbox Server maintained by Mozilla. See tinderbox.mozilla.org/Bugzilla/ for latest results.
- Current activity of the tests can be viewed by attaching to a screen session running under the tinderbox user. There's two sessions, one for QA tests (named qa) and one for all the other tests (named tbox). Use commands screen -r qa or screen -r tbox to attach.
- Selenium Server v2.37.0, Test::WWW::Selenium Perl module v1.24 and Firefox v24 are used by the QA tests. Be careful when updating these so that the trees won't burn unnecessarily.
- Selenium Server is manually installed to the /usr/local/share/selenium-server/ directory. Scripts to start it and to list related processes are in the /usr/local/bin/ directory.
- Firefox at /usr/lib64/firefox/firefox is referenced from Selenium start scripts and is installed from standard RHEL repositories.
- The perl-Test-WWW-Selenium package is installed/updated from Repoforge (previously known as RPMforge) but is excluded from normal yum updates so it needs to be manually updated (use yum update --disableexcludes=rpmforge perl-Test-WWW-Selenium command) when needed.
- Replicates bugs_tip, bugs_bugzilla4_4_branch, bugs_bugzilla4_2_branch and bugs_bugzilla4_0_branch databases from landfill to be used in the checksetup update testing.
- Uses various locally built RPM packages from a local repository) defined in the /etc/yum.repos.d/bz.repo repository configuration file.
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
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.
bots.bugzilla.org
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.
infra.bugzilla.org
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 mradm01.mozilla.org, ns2.globalnetoptex.com or ns2.lax01.mzima.net 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.
bugzilla3.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.