31
edits
ReleaseEngineering/worker configuration/2008: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/worker configuration/2008 (view source)
Revision as of 19:00, 20 August 2015
, 20 August 2015Saving WIP
Mcornmesser (talk | contribs) (Created page with "== Windows 2008 Build Slave Configuration == === Overview === === Starting Operating System === The process is begun with Windows Server 2008 R2 SP1 iso (en_windows_server_200...") |
Mcornmesser (talk | contribs) (Saving WIP) |
||
| Line 1: | Line 1: | ||
=== Overview === | === Overview === | ||
The building of the 2008 builder slave image uses both the Microsoft Deployment Workbench (MDT) and Puppet configuration software. In the case of AWS instances the Amazon EC2 service is also utilized. <br /> | |||
The initial steps is building a base image in MDT. The base image is comprised of large applications that will seldom change, Microsoft SDKs, applications that may aid in deployment, and Windows Server Update Service (WSUS) components. <br /> | |||
The second portion of this differs according to datacenter deployment or cloud deployment. Differences are documented below.However, in both cases the image has Puppet installed, and the image is prep to be ran against the PuppetAgain. As well a configurations that Puppet needs to run or at the time made more sense to be done through MDT.<br /> | |||
General MDT documentation: https://mana.mozilla.org/wiki/display/SYSADMIN/Microsoft+Deployment+Toolkit+2012+Update+1+General+Documentation | |||
== Windows 2008 Build Slave Configuration Managed by Microsoft Deployment Workbench Configuration == | |||
=== Starting Operating System === | === Starting Operating System === | ||
The process is begun with Windows Server 2008 R2 SP1 iso (en_windows_server_2008_r2_with_sp1_vl_build_x64_dvd_617403.iso). The iso file is mounted, in our case, using Virtual CloneDrive. Once the iso file is mounted it is then imported into the Microsoft Deployment Workbench (MDT). | The process is begun with Windows Server 2008 R2 SP1 iso (en_windows_server_2008_r2_with_sp1_vl_build_x64_dvd_617403.iso). The iso file is mounted, in our case, using Virtual CloneDrive. Once the iso file is mounted it is then imported into the Microsoft Deployment Workbench (MDT). | ||
| Line 6: | Line 14: | ||
The modification here is found under tasks sequence steps -> State Restore -> Custom Tasks -> Mozilla Custom. | The modification here is found under tasks sequence steps -> State Restore -> Custom Tasks -> Mozilla Custom. | ||
===== Applications ===== | ===== Applications ===== | ||
Microsoft Visual Studio 2010 | Microsoft Visual Studio 2010<br /> | ||
Microsoft Visual Studio 2013 Update 3 | * This application install has been customized. | ||
Microsoft Windows Windows 8 SDK | |||
Microsoft Windows Windows | Microsoft Visual Studio 2013 Update 3<br /> | ||
Microsoft Windows Windows 8 SDK<br /> | |||
Microsoft Windows Windows Direct X SDK<br /> | |||
Microsoft Net Framework 3.5 <br /> | |||
=== Configuration === | |||
WSUS Updates | |||
=== Data Center Deployment Configuration (MDT Task Sequence SW2008_DPLY_001)=== | |||
=== Cloud Deploy Configuration Capture (MDT Task Sequence ID W2008_CLD_002)=== | |||
== Windows 2008 Build Slave Configuration Managed by Puppet == | |||