Presentation is loading. Please wait.

Presentation is loading. Please wait.

© 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Scot Bean & Michael Roberts Software.

Similar presentations


Presentation on theme: "© 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Scot Bean & Michael Roberts Software."— Presentation transcript:

1 © 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Scot Bean & Michael Roberts Software Engineers, HP Ignite-UX: Automatic HP-UX Installs

2 HPTF 2005 Ignite-UX: Automatic HP-UX Installs2 Agenda Ignite-UX Overview Automated HP-UX Install Methods −Cold Install −Golden Image Detailed Setup Steps Traps & Tips Customization & Maintenance

3 HPTF 2005 Ignite-UX: Automatic HP-UX Installs3 What is Ignite-UX? Free installation & deployment utility for HP-UX Aliases −“Ignite” −“Instant Ignition” −“IUX” History −Released in June 1997 with HP-UX 10.30, version 1.02 −Current version: C , May 2005 Where to get it: −swinstall from any HP-UX install or application media −Download via

4 HPTF 2005 Ignite-UX: Automatic HP-UX Installs4 Ignite Server GUI

5 HPTF 2005 Ignite-UX: Automatic HP-UX Installs5 Ignite Client TUI

6 HPTF 2005 Ignite-UX: Automatic HP-UX Installs6 LAN Install Process Ignite Server Target (or Client) Machine 1. Install Kernel: (W|I)INSTALL files, via tftp Reboot #1: boots the install kernel 2. Content Files: via SD, NFS, FTP or remsh Reboot #2: boots to new kernel 3. Final Configuration machine-specific setup Reboot #3: ready to use

7 HPTF 2005 Ignite-UX: Automatic HP-UX Installs7 Why Automate Installs? ManualAutomated many complex menu decisions“canned” scripts & config files requires sys admin console time“hands-off” execution subject to human errorrepeatable results navigating the menus is slowerfaster installs OK for one or two machinesmultiple, concurrent installs flexible for custom single installscan customize once, then reuse can initialize an empty machineworks only for operational targets

8 HPTF 2005 Ignite-UX: Automatic HP-UX Installs8 Two Automation Methods “Cold Install”“Golden Image” standard install built from original HP-UX media sources install image is “cloned” from another machine install files reside in SD depots: bundles, products, patches install files are a gzip’ed archive slower: individual items installfaster: archive is copied over 3 rd party applications may require manual install afterwards application bits are already there less initial setup timemore detailed setup & configuration more flexible: depot maintenancemore rigid, but more repeatable uses IUX make_depots cmduses IUX make_sys_image cmd both use the IUX bootsys command to autostart the install

9 HPTF 2005 Ignite-UX: Automatic HP-UX Installs9 Performance Study

10 HPTF 2005 Ignite-UX: Automatic HP-UX Installs10 Which Method is Right for Me? Consider Cold Install when: −all infrastructure and target platforms are new & fast −install baselines change often −your sys admin staff is new to HP-UX Consider Golden Image when: −you have the need for speed −you still support older, slower platforms −install baselines are static, to justify longer setup time −your sys admin staff has some experience −legal auditing requirements demand consistent SW Also, could use both methods, or a hybrid setup

11 HPTF 2005 Ignite-UX: Automatic HP-UX Installs11 Case Studies HP manufacturing: −uses a hybrid setup to pre-install shipped HP-UX software −common, core Golden Image laid down first −custom Cold Install depots added, per customer order Major university: −wipes student machines at the end of the semester −fast Golden Image resets student lab to clean baseline Software partners with test suites: −some use Golden Image for a fast, repeatable baseline −others use Cold Install because they always want the latest releases, with a frequently changing baseline

12 HPTF 2005 Ignite-UX: Automatic HP-UX Installs12 Cold Install Setup Steps 1. Copy install media to ignite server, use the make_depots command 2. Update the Ignite configuration, use the make_config command

13 HPTF 2005 Ignite-UX: Automatic HP-UX Installs13 1. make_depots a)Insert media in CD / DVD drive b)make_depots –r B –s /dev/dsk/c0t0d0 Standard HP-UX install depot copied to /var/opt/ignite/depots/Rel_B.11.11/core Ignite Server

14 HPTF 2005 Ignite-UX: Automatic HP-UX Installs14 2. make_config make_config –r B sw_source "core" { description = "HP-UX Core Software" source_format = SD sd_server = " " sd_depot_dir = "/var/opt/ignite/depots/Rel_B.11.11/core" source_type = "NET" load_order = 0 } … New configuration file created in /var/opt/ignite/data/Rel_B.11.11/core_cfg cfg "HP-UX B Default" { description “Default system configuration for B " "/opt/ignite/data/Rel_B.11.11/config" "/opt/ignite/data/Rel_B.11.11/hw_patches_cfg" "/var/opt/ignite/data/Rel_B.11.11/core_cfg" "/var/opt/ignite/config.local" } “HP-UX B Default” updated in master /var/opt/ignite/INDEX config file

15 HPTF 2005 Ignite-UX: Automatic HP-UX Installs15 Cold Install Run bootsys –a –f –i “ HP-UX B Default” mytarget

16 HPTF 2005 Ignite-UX: Automatic HP-UX Installs16 Golden Image Setup Steps 1. Setup NFS export area 2. Prepare clone machine 3. Create the Golden Image, use the make_sys_image command 4. Create a custom configuration file 5. Create a new INDEX entry

17 HPTF 2005 Ignite-UX: Automatic HP-UX Installs17 Ignite allows 3 different LAN protocols to transfer the Golden Image: −NFS: most popular −FTP: good second choice −remsh: last resort, possible security concerns here Let’s setup an NFS area for Golden Images −mkdir /var/opt/ignite/My_Golden_Images −echo “/var/opt/ignite/My_Golden_Images -ro,anon=2” >> /etc/exports −exportfs -av 1. Setup NFS export area

18 HPTF 2005 Ignite-UX: Automatic HP-UX Installs18 a) installs, updates? ensure clone machine has any required applications and drivers installed check the HP-UX patch level, and consider: swinstalling the latest SD patch swinstalling a recent QPK bundle run check_patches to verify patch installations b) kernel parameters? consider tuning the default parms to be more generic c) machine in use? intrusive to live operations DON’T try the next step on your live web server, it may go offline stop running applications, we need a quiet clone 2. Prepare clone machine

19 HPTF 2005 Ignite-UX: Automatic HP-UX Installs19 3. Create the Golden Image a)login to clone machine b)ftp /opt/ignite/data/scripts/make_sys_image from the Ignite server to /tmp c)/tmp/make_sys_image -s iserver -d /var/opt/ignite/My_Golden_Images Ignite Server Clone Machine generic gzip archive

20 HPTF 2005 Ignite-UX: Automatic HP-UX Installs20 4. Custom configuration file a)Back on ignite server now b)Copy the Golden Image template config file cp /opt/ignite/data/examples/core11.cfg /var/opt/ignite/data/Rel_B.11.11/golden_cfg c)Customize golden_cfg parameters for your image: 1.description: “My Golden Image” 2.nfs_source: IP address of Ignite server & full path to image (or ftp_source or remsh_source) 3.sw_sel: edit appropriate “bitness” section (32/64, IA/PA) 4.archive_path: myclone.gz 5.impacts: image filesystem space requirements run /opt/ignite/lbin/archive_impact –t –g myclone.gz replace existing impacts lines with this output

21 HPTF 2005 Ignite-UX: Automatic HP-UX Installs21 sw_source "core archive" { description = "My Golden Image" load_order = 0 source_format = archive source_type="NET" nfs_source = " :/var/opt/ignite/My_Golden_Images” } init sw_sel "my_golden_image" { description = "English HP-UX CDE – 64 – Bit OS” sw_source = "core archive" sw_category = "HPUXEnvironments" archive_type = gzip tar archive_path = “myclone.gz" impacts = "/" 110Kb impacts = "/dev" 15Kb impacts = "/etc" 46385Kb impacts = "/home" 1Kb impacts = "/opt" Kb impacts = "/sbin" 37231Kb impacts = "/stand" 1091Kb impacts = "/usr" Kb impacts = "/var" Kb visible_if = can_run_64bit } = (can_run_64bit) _hp_os_bitness = "64“ Custom configuration file (cont.)

22 HPTF 2005 Ignite-UX: Automatic HP-UX Installs22 5. New INDEX entry a)Copy an existing stanza in /var/opt/ignite/INDEX b)Customize INDEX parameters for your image: … cfg “my_golden_image” { description “My Golden Image” "/opt/ignite/data/Rel_B.11.11/config" "/var/opt/ignite/data/Rel_B.11.11/golden_cfg" "/var/opt/ignite/config.local" } … The manage_index command can also do this for you

23 HPTF 2005 Ignite-UX: Automatic HP-UX Installs23 Golden Image Run bootsys –a –f –i my_golden_image mytarget

24 HPTF 2005 Ignite-UX: Automatic HP-UX Installs24 Automation: Traps & Tips General Traps & Tips Cold Install specific Golden Image specific

25 HPTF 2005 Ignite-UX: Automatic HP-UX Installs25 General: Traps & Tips instl_adm –T : verify your config files! Maximize /var/opt/ignite/config.local −Put all common configuration parameters here: −Network settings, keyboards, etc. bootsys command −Use the –a option, or Ignite will wait for console input −Use the –f option, or Ignite can use previous defaults −Use touch /.bootsys_block to protect non-install machines! −Automate bootsys calls via cron, or your own front-end Run test Ignites on a variety of target platforms Examine /var/opt/ignite/logs/* to troubleshoot Use CM when editing your custom IUX config files

26 HPTF 2005 Ignite-UX: Automatic HP-UX Installs26 Cold Install: Traps & Tips Avoid global localization: init sw_sel "Global" = FALSE init sw_sel "English" = TRUE Control custom installs with bootsys options: bootsys … -l HPUX11i-OE-MC=true … Customize and maintain install depots with swcopy Create a new depot when adding a new release

27 HPTF 2005 Ignite-UX: Automatic HP-UX Installs27 Golden Image: Traps & Tips How many images? −Itanium vs. PA-RISC, 32 bit vs. 64 bit, server vs. workstation? −one per model / role, or one for many models /roles? Select the best machine to clone: −one-to-one image: select the one with the most disparate I/O cards −one-to-many image: select the oldest model possible Consider some custom pre-image cleanups on the clone: − rm /var/adm/sw/*.log /var/adm/syslog/*.log /var/mail/* − crontab –e Keep the clone machine handy until image tests pass Use /tmp for image creation scripts and tools: NOT cloned Add other-model firmware patches to clone with override: touch /tmp/force_patch_install

28 HPTF 2005 Ignite-UX: Automatic HP-UX Installs28 Customization & Maintenance Ignite-UX has a rich configuration file syntax −Most users underutilize this syntax code −See man 4 instl_adm for all of the details (50 pages!) −See these examples of config file syntax in action: /opt/ignite/data/Rel_B.11.11/config /opt/ignite/data/examples/* What we’ll cover here: −Common customizations −Shortcut to syntax with the save_config command −Sample custom config file −Add some patches to your image

29 HPTF 2005 Ignite-UX: Automatic HP-UX Installs29 Common Customizations 4 custom script types: − post_config_script += " /var/opt/ignite/scripts/setup_NFS " − pre_load_script post_load_script final_script 4 custom command types: − pre_load_cmd += " echo In Preload " − post_load_cmd post_config_cmd final_cmd If / Else logic: ( system_name == "nopasswd" ) { root_password="" } else { root_password="\AxycAGJg16Dc" } Kernel parameters: set_kernel += " maxfiles 100 " mod_kernel += " tunable maxfiles 200 "

30 HPTF 2005 Ignite-UX: Automatic HP-UX Installs30 save_config command Take a shortcut when creating config files: 1.Find a machine you would like to copy or recreate 2.Login and 3.ftp /opt/ignite/bin/save_config to the machine (* see notes) 4.save_config –f myconfig myconfig has all of the Ignite syntax describing this machine Use pieces of this syntax to customize your configs Wildcards & variables can replace specific objects: −disk[*] −physical_volume_disk[*=_hp_root_group_disks]

31 HPTF 2005 Ignite-UX: Automatic HP-UX Installs31 ### My /var/opt/ignite/config.local file ### Decide on number of root disks to use (disk[_hp_root_disk].size > 8192MB) # current root disk > 8GB { init _hp_root_grp_disks=1 # large disk drives here, need only 1 } else { ( system_name == "harry" | system_name == "moe" | system_name == “curly" ) { init _hp_root_grp_disks=3 # these older systems need 3 drives } ### Network settings dns_domain="acme.com" dns_nameserver[0] = " “ final route_gateway[0]=" " nis_domain="acme" ### Post-Ignite script # this sets up a nice default shell environment post_config_script += "/var/opt/ignite/scripts/fix_profile" Sample custom config file

32 HPTF 2005 Ignite-UX: Automatic HP-UX Installs32 Add Patches to Your Image 1. swcopy the patches you need to /var/opt/ignite/depots/Rel_B.11.11/my_patches 2. Use make_bundles, if needed, to create one bundle 3. Use make_config on the new depot, my_patches 4. Insert the new patch config into the INDEX file … cfg “my_golden_image” { description “My Golden Image” "/opt/ignite/data/Rel_B.11.11/config" "/var/opt/ignite/data/Rel_B.11.11/golden_cfg" "/var/opt/ignite/data/Rel_B.11.11/my_patches_cfg" "/var/opt/ignite/config.local" } …

33 HPTF 2005 Ignite-UX: Automatic HP-UX Installs33 References Web Docs −Main Ignite-UX website: −Latest Ignite-UX Admin Guide (edition 19, June 2005): −Latest HP-UX Install Guide (edition 4, May 2005): −Latest Enablement Matrix (required Ignite revisions) Man Pages −Basic Ignite server setup: man 5 ignite −Ignite configuration file syntax reference: man 4 instl_adm


Download ppt "© 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Scot Bean & Michael Roberts Software."

Similar presentations


Ads by Google