Chapter 2

Workstations

Slide #1
 Topics
1. Machine Lifecycle
2. Automated Installs
3. Updates
4. Network Configuration

Slide #2
Workstation Management

Slide #3
 States of Machines
New
A new machine
Clean
OS installed, but not yet configured for environment.
Configured
Configured correctly for the operating environment.
Unknown
Misconfigured, broken, newly discovered, etc.
Off
Retired/surplussed
Slide #4
 State Transitions
Build
Set up hardware and install OS.
Initialize
Configure for environment; often part of build.
Update
Install new software.
Patch old software.
Change configurations.

Slide #5
 Why Automate Installs?
1. Save time.
Boot the computer, then go do something else.
2. Ensure consistency.
No chance of entering wrong input during install.
Avoid user requests due to mistakes in config.
What works on one desktop, works on all.
3. Fast system recovery.
Rebuild system with auto-install vs. slow tapes.

Slide #6
 Trusting the Vendor Installation
Always reload the OS on new machines.
– You need to configure the host for your env.
– Eventually you’ll reload the OS on a desktop,
leaving you with two platforms to support: the
vendor OS install and your OS install.
– Vendors change their OS images from time to
time, so systems you bought today have a
different OS from systems bought 6 months ago.

Slide #7
 Install Types
1. Hard Disk Imaging
Duplicate hard disk of installed system.
Advantages: fast, simple.
Disadvantages: need identical hardware, leads to
many images, all of which must be updated
manually when you make a change
2. Scripted Installs
Installer accepts input from script.
Advantages: flexible, systems can be different
Disadvantages: more effort to setup initially
Slide #8
 Auto-Install Features
1. Unattended
Requires little or no human interaction.
2. Concurrent
Multiple installs can be performed at once.
3. Scalable
New clients added easily.
4. Flexible
Configurable to do custom install types.

Slide #9
 Auto-Install Components
Boot Component
Media (floppy or CD)
Network (PXE)
Network Configuration
DHCP: IP addresses, netmasks, DNS
Install Configuration
Media (floppy or CD)
Network (tftp, ftp, http, NFS)
Install Data and Programs
Network (tftp, ftp, http, NFS)
Slide #10
 PXE
Preboot eXecution Environment
Intel standard for booting over the network.
PXE BIOS loads kernel over network.
Applications
Diskless clients (use NFS for root disk.)
Booting install program.
How it works
1. Asks DHCP server for config (ip, net, tftp.)
2. Downloads pxelinux from tftp server.
3. Boots pxelinux kernel.
4. Kernel uses tftp’d filesystem image or NFS filesystem.
Slide #11
 Disk Imaging
1. Setup ftp server. 2-3. test client

2. Install OS image on a test

3. Verify test client OS.

5. deployment #2
Slide #12
 Disk Imaging Tools
• Acronis TrueImage
• Clonezilla (free)
• g4u: Ghost for UNIX (free)
• Symantec GHOST
• System Imager (free)

Slide #13
Clonezilla

Slide #14
g4u

Slide #15
 Scripted Install Tools
Red Hat distributions, incl. Centos
– Kickstart
– Cobbler
Debian distributions, incl. Ubuntu
– FAI
– Preseed
Mandriva Linux
– DrakX
Solaris
– Jumpstart
Slide #16
 Kickstart Components
Bootable media
– Small bootstrap kernel and filesystem.
– Uses DHCP server to configure system.
Source machine
– Network server: ftp, http, nfs.
– Kickstart configuration file(s).
– Install files (RPMs).
Target machine
– Machine on which you’re installing.
– Boot with bootable media.
Slide #17
 Kickstart Components

http

DHCP Server Source Machine

Target Machine

Slide #18
 Source Machine Setup
1. Start network service.
2. Copy install media--for each CD:
mount /mnt/cdrom
cp -var /mnt/cdrom/RedHat /usr/local/ks
umount /mnt/cdrom/
3. Create config files.
Store under kickstart subdirectory.

Slide #19
 Kickstart Configuration File
Describes desired system configuration.
Disk partition setup.
Network configuration.
Language and other configuration items.
Package selection.
Pre- and post-install scripts for customization.
Creating a Kickstart file:
Original install (located under /root)
Kickstart Configurator application
Manually

Slide #20
Kickstart Configurator

Slide #21
 Configuration Options
auth
crypt, md5, nis, ldap, smb, krb5
network and firewall
DHCP, static, firewall configuration
part
Create disk partitions: size, maxsize, grow.
c.f. autopart, clearpart, log, raid.
rootpw
xconfig
packages

Slide #22
 Performing a Kickstart Install
1. Boot with install media
RHEL CD #1
Bootable Kickstart media
2. Specify Kickstart file location
Web: ks=http://<server>/<path>
NFS: ks=http://<server>/<path>
Floppy: ks=floppy
PXE: ks

Slide #23
 Software Update Difficulties
No physical access
– Update process should work w/o physical access.
Host may not be in known state
– Prior updates may or may not have happened.
– Sysadmins or users may have reconfigured.
Hosts may not be there
– Portable computers may not be on your network when
you’re updating systems.
Host may have live users
– Some updates require no user access or reboots.
Slide #24
 One, Some, Many
Failed updates break someone’s machine.
Vendor hasn’t tested updates in your env.
One, some, many process mitigates risks
One: Test update on one system first.
Some: Test update on group of test systems that
are representative of the target systems.
Many: Schedule update for a time that limits
disruption and update user systems.

Slide #25
 Network Configuration
What’s so bad about manual net settings?
– It’s only an IP address and netmask.
– What happens if you need to renumber?
Use DHCP instead of manual settings
– Make all changes on a single server.
– Easy to change settings for entire network.
– DHCP can assign static IPs as well as dynamic.

Slide #26
 Key Points
Desktop Lifecycle
– New, clean, configured, unknown states.
Automated Installs
– Why: consistency, fast recovery, saves time.
– Install types: imaging vs. scripted.
– Components: boot, network, config, data.
– Think about how Principles of SA apply.
One, Some, Many approach to updates.

Slide #27