canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
QA/Infrastructure/Automation Servers: Difference between revisions
QA/Infrastructure/Automation Servers (view source)
Revision as of 10:38, 11 July 2012
, 11 July 2012no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
The Project Overview has moved to [[QA/Infrastructure/Automation_Servers/Project_Overview]]. | The Project Overview has moved to [[QA/Infrastructure/Automation_Servers/Project_Overview]]. | ||
= Server Overview = | |||
The automation infrastructure is the set of machines available for Mozmill-based update and release testing for Firefox. | The automation infrastructure is the set of machines available for Mozmill-based update and release testing for Firefox. | ||
This is divided into the following sets of machines which all live in the QA vlan in Mountain View (accessible as .qa.mtv1.mozilla.com). | This is divided into the following sets of machines which all live in the QA vlan in Mountain View (accessible as .qa.mtv1.mozilla.com). | ||
== Mac Pros == | |||
[[File:Mac Pros.png]] | [[File:Mac Pros.png]] | ||
| Line 21: | Line 20: | ||
All machines have an administrator account with the username, 'mozillaqa'. Access can be done over SSH or Apple Remote Desktop/VNC. | All machines have an administrator account with the username, 'mozillaqa'. Access can be done over SSH or Apple Remote Desktop/VNC. | ||
== Mac Minis == | |||
[[File:QA_Automation_Mac_Minis.png]] | [[File:QA_Automation_Mac_Minis.png]] | ||
| Line 61: | Line 60: | ||
** release8-osx-107.qa.mtv1.mozilla.com (Todo: install 10.8) | ** release8-osx-107.qa.mtv1.mozilla.com (Todo: install 10.8) | ||
== QA Mountain View ESX Cluster (HP 1230 Racked Servers) == | |||
These servers run ESXi and have a series of Windows and Linux virtual machines running within each. | These servers run ESXi and have a series of Windows and Linux virtual machines running within each. | ||
| Line 88: | Line 87: | ||
These are controlled as a unified vCenter ESX cluster. This is accessible via vSphere as vc1.qa.mtv1.mozilla.com. Download the appropriate vSphere client from: https://vc1.qa.mtv1.mozilla.com/client/VMware-viclient.exe You can try the web client at https://vc1.qa.mtv1.mozilla.com/vsphere-client/. You will need an account created on vc1 if you wish to be an administrator on it. This is controlled by Dan Parsons (:lerxst) and should be done through an IT request bug. | These are controlled as a unified vCenter ESX cluster. This is accessible via vSphere as vc1.qa.mtv1.mozilla.com. Download the appropriate vSphere client from: https://vc1.qa.mtv1.mozilla.com/client/VMware-viclient.exe You can try the web client at https://vc1.qa.mtv1.mozilla.com/vsphere-client/. You will need an account created on vc1 if you wish to be an administrator on it. This is controlled by Dan Parsons (:lerxst) and should be done through an IT request bug. | ||
=== Handling of the ESX cluster === | |||
To ensure that new and existent VMs and templates are handled correctly you can find some details below. This part only affects administrators of the ESX cluster. Others should file a Mozilla QA / Infrastructure bug to get issues solved. | To ensure that new and existent VMs and templates are handled correctly you can find some details below. This part only affects administrators of the ESX cluster. Others should file a Mozilla QA / Infrastructure bug to get issues solved. | ||
==== Host usage ==== | |||
; release11.qa.mtv1.mozilla.com | ; release11.qa.mtv1.mozilla.com | ||
* vSphere client (ESX administration) | * vSphere client (ESX administration) | ||
| Line 97: | Line 96: | ||
* Creating and updating VM templates (For details see templates section below) | * Creating and updating VM templates (For details see templates section below) | ||
==== Templates ==== | |||
All templates for VMs have been created to be run on release11. Their data storage has been set to fs2-qa1. That means no data is stored on the VM itself but on the shared 1TB network drive instead. Those data should remain on this disk and this storage has to be used for newly created templates. That allows us to share the templates across the different machines in the ESX cluster. | All templates for VMs have been created to be run on release11. Their data storage has been set to fs2-qa1. That means no data is stored on the VM itself but on the shared 1TB network drive instead. Those data should remain on this disk and this storage has to be used for newly created templates. That allows us to share the templates across the different machines in the ESX cluster. | ||