Model

The overall CMS model is that no live permanent data should be stored on any machine in production. This empowers systems administration to quickly and reliably install and/or rebuild production compute resources, since there is no important data to recover from a faulty machine and subsequently restore after the machine is repaired.

The underlying policy is that permanent production data will be stored on the central file server, which is snapshot and backed up to tape in the event of a disaster.

The CMS model allows workstations to be installed uniformly in such that needed software is not customized to any one particular machine, but is installed on all similar machines. Likewise, should a new software need arise for any specific workstation or user, the new software is installed globally to further benefit every other user. Sometimes this is not an easy task as not all software is able to fit within this model, but it is important to keep in mind that the CMS systems administrators do not simply install software for users -- they attempt to solve problems, so asking for specific software will not always solve a particular problem most efficiently.

Method

Depending on operating system and platform, the method for automated installation differs, but the overall concept and end result is the same: a machine built to a consistent reliable state that suits the needs of its user.

For specific operating systems, we will explain in detail the technical procedure in achieving automated installation consistent with the CMS model.

Linux

The chosen Linux distribution for implementation is currently OpenSUSE. OpenSUSE employs an automated installation method, "AutoYaST", that is easily customizable and extendible, which is similar to other distributions' methods such as RedHat's "kickstart", and Mandriva's "auto_inst".

The concept is that a machine is booted with lightweight installation media and appended such that an automated install construction set is retrieved for the host. After the auto-install instructions are downloaded, the installation commenses without human intervention. Upon completion of the installation, configuration information is applied to the newly installed machine that is consistent with the CMS model. Afterward, typically a reboot is performed to bring the machine to a known state in which all software has been installed and configuration has been applied such that it very closely resembles other hosts within the CMS department.

Normally, an automated Linux installation will take up to 90 minutes, depending on network traffic.

In essence, Linux automated installs are seperated into two components:

1. installtion instructions (list of software, options, misc configuration info)
2. installation media that will act on automated installation instructions.

Linux Install for OpenSUSE are in the form of an AutoYaST XML file, editable with any text editor, and maintained in a version control repository.

Windows

The Windows installation is based upon Windows 10, 64bit. Currently we have one image, Lenovo.wim, which is usable with some minor configuration edits on all of the Lenovo laptops deployed to the administrative staff. The installation uses Sysprep, WindowsPE, a batch file that sets up UEFI-aware partitions on the hard drive, and the image copy process.

The image file is located on both domain controllers, in E:\WINDFS\Images. The Windows Automated Deployment Kit files are also in this location.

To deploy an image to a new machine matching the Lenovo architecture:

(a) Locate the USB stick labeled

-- DavidLeBlanc - 2019-10-07