Ignite-UX: Fast and Flexible System Deployment Tool

1. Ignite-UX Overview

2. Ignite-UX Key Concepts

3. Ignite-UX Detailed Presentation

4. IUX Target IUX Target IUX Target IUX Server IUX Target IUX Target IUX Target IUX Target IUX Target What is Ignite-UX? • Process for initial system deployment • True client-server model: • can install multiple target machines simultaneously • allows target customization and status monitoring • Ability to build and reuse standard configurations • Ability to do site-specific customization • Ability to automate installation process • Extensible system manifest capability • Ability to install software from multiple sources in a single session!

5. IUX Target IUX Target IUX Target IUX Server IUX Target IUX Target IUX Target IUX Target IUX Target What else is Ignite-UX? • Process for system re-deployment or SW upgrades • All the same capabilities of previous NetInstall deployment model! • With the ability to target a previously installed system on the network and reinstall it. • Target a machine and have it reboot and give control to the install server - bootsys • Use the GUI to define what gets loaded or use a “golden system” image • GUI or command line control

6. Ignite-UX versus Cold Install Cold Install Ignite-UX Installation Methods • Install from Local media • "Pull" Install from Network Servers • Install from Local media • "Pull" Install from Network Servers • "Push" Install from Network Servers • "Re-deploy" Existing machines Server Capability • Serves Single Release that Server is Running • Can Serve Multiple Releases (10.01 and forward) User Interface • TUI running on target • TUI running on Target • GUI running on Server Software Formats • Software Distributor • SD, cpio, tar • Multiple sources in one session System Attributes Which Can Be Specified • A lot! • Even more! • More script hooks • set_parms info Produce a System Manifest • No • Yes!

7. Ignite-UX versus SD Ignite-UX SD Purpose Complete installs of system software. Manages software on an existing system. Complains if it's short on disk space. Disk space considerations Performs disk and file system layout. Handles SD and other formats like tar or cpio, and even OS archives. Knows about standard bundles, products and filesets. Objects handled

8. Ignite-UX: A Tale of Two Tools Ignite-UX is a tool which does the initial configuration and loading of an HP-UX system. At one time there were two different tools which accomplished this same task for different customer segments: • The CHAMP tool was used by HP manufacturers and two-tier distributors • The HP-UX Install program (also known as Cold Install) is used by end customers Ignite-UX is designed as a replacement for both CHAMP and HP-UX Install. It will address the needs of both sets of customers.

9. Segmentation of Ignite-UX Users HP Manufacturing High volumes of pre-installed HW & SW Production line environment, high throughput Highly automated, no human interaction Standard configurations customizable via SISP Two-tier distributors Medium-high volumes Small unit orders Manual process via GUI More customized configurations High Volume Customers Small set of standard/certified configurations Customized to end user requirements Reinstallation of systems rather than update Inventory and IP address management Low Volume Customers Often use ignited systems No need for standard configurations Infrequent installs only on "as needed" basis Single point access of system view Customer Engineer Complex system installations at customer site Extensive use of system diagnostics Hardware and software installation, network connectivity Third-party applications loaded

10. Value Propositions for Ignite-UX Users HP Manufacturers Capability of high volume, standard OS bundle installs Minimal time per install, multiple simultaneous installs Ease of linkage to OP High reliability Two-tier Distributors Capability of high volume, standard OS bundle installs Minimal time per install Use multiple source formats Additional post-installation customization High Volume Customers High volume installs Create and install certified standard configurations Perform post-installation customizations Query process and see configuration Low Volume Customers Install from all sources (CD-ROM, DAT, network) Provide one-step installation from default configuration Customize basic configuration parameters Query process and see configuration Customer Engineer Install from all sources (CD-ROM, DAT, network) Create and install standard configurations Provide one-step installation from default configuration Customize basic and advanced configuration parameters

11. Cold Install from Local Media With Ignite-UX • Boot from local media • No Network Required • Run UI from the target's console • TUI version of Server GUI interface (advanced) -or- • Guided Tour of Selections (Wizard) Target Machine CD Tape

12. Network Pull Cold Install from Network Server Server • Do a 'boot lan install' from the client console • Run UI from target's console (like previous slide) • Use previously defined configs on server Target Machine

13. Welcome to Ignite-UX! • Initial screen on system console • Shows summary information • Single client installation • Normal mode is to select Install HP-UX

14. User Interface and Media Options • Permits choice of source location and user interface • Guided installation referred to as "wizard mode" which is not available in GUI

15. Basic itool screen: Wizard Mode • Guided tour through recommended configuration choices • Does not allow file system size changes or setting networking parameters • Good for novice user

16. Basic itool screen: Advanced Mode • Obam version of Ignite-UX interface • Tabbed windows look and feel

17. Network Push Cold Install from Network Server • Do a 'boot lan install' from client console (only interaction needed on client) • Run UI at the server • Can do multiple clients at once Server Target Machines

18. Subnet Subnet Using Ignite-UX Across Gateways Ignite-UX Server • Only necessary when doing a cold install of an unbootable machine across a gateway from server • Boot helper machine: • Must be running 10.* • Must install minimum Ignite-UX (Ignite-UX.MinimumRuntime) • About 22Mb free • Point to server via instl_adm • On target: • b lan.<helper_ip_address> install • gets install kernel and RAMFS from helper, then connects to server • Not a relay agent "Helper Machine" Target Machine

19. Subnet Subnet Re-Deploy Existing Machine (bootsys) Target Machine • Useful when target machine is already running HP-UX 9.x or 10.x • Run bootsys on server: • Copies install kernel, fs down to target disk (uses remsh) • Sets up target to boot from install kernel • Reboots target • Target boots from disk and connects to server • No need to ever go to target console • Network topology doesn't matter Gateway Server

20. True Client-Server Application Client Target Customization Server Central Control and Status Monitoring

21. IUX Server - Main Screen • Icon per client being installed • Colors used to indicate client status • Easily view status details of any client • Easily see detailed hardware description of any client • Reinstall option based on saved install sessions • Sort clients by name, status or % complete • Performs server configuration tasks

22. IUX Client - Basic Configuration • First screen to install a client • Easy selection of a base configuration from HP supplied defaults or a previously saved session • Provides for easy selection of basic configuration information • Designed to provide "GO" option from here

23. IUX Client - Software Options • Easily choose software packages to install • Software packages may be SD, tar or cpio formats • Can load multiple packages from multiple sources in a single session • Can select software category for filtering or easy package location • Categories can be HP or user defined

24. IUX Client - System Options • Allows easy setting of all system-specific parameters normally set as part of the first boot sequence • Hostname, IP address, date, etc..

25. IUX Client - File System Options • Rich set of configuration options for setting up disks and file systems • Simpler screen for whole disk file systems • Sizes the file systems based on needs of the selected software

26. IUX Client - Advanced Options • Allows easy selection of scripts to run after the installation is complete • Allows for more unique system customization • Even more script hooks available via the config file

27. Select a default configuration in UI: e.g. "Default 10.20 Release" Make modifications in the UI to select: How you want disks/file systems allocated What software you want installed What scripts you want run etc. "Save As" to write your customized config file Optionally, hand edit the config file to make it hardware independent: Different disk layouts depending on what disks are present Swap space based on memory size etc... Save As... Creating your own Customized Configurations

28. System Attributes Disk & FS Layout Command & Script Hooks Software Source Selections System Identity & Network IUX Process Control The IUX Config File • Recipe for "How to Build a System" • Created by UI or by user • Can do Conditional Expressions: (memory > 512Mb){ init _hp_pri_swap=512Mb } else { init _hp_pri_swap=memory*2 }

29. Default Disk and FS layouts SW description of single SD depot or system archive Local config overrides that apply globally User named configs Client-specific configs Boot control & Networking The IUX Index File Defines a grouping or set of config files

30. New Features for 11.0 • System Recovery Tool Now Integrated and on Core Media (Instead of on Support Media) • Tool to Allow Customers To Make Their Own Customized Install Media • Tool to Allow Customers to Make Their Own Customized Recovery Tapes • see make_recovery presentation • Support for Merged SD Depots

31. Chapter 2 • How to install and configure Ignite-UX

32. Ignite-UX Software • The product is available on the external HP Website located at http://www.software.hp.com • Product numbers • B5724AA_APZ (S700) • B5725AA_APZ (S800)

33. Ignite-UX product structure # B5724AA_APZ 1.09 HP-UX Installation Utilities (Ignite-UX - S700 - 10.20) # B5724AA_APZ.Ignite-UX 1.09 HP-UX System Installation Services B5724AA_APZ.Ignite-UX.BOOT-KERNEL 1.09 Installation Boot Kernel for S700/S800 clients B5724AA_APZ.Ignite-UX.BOOT-SERVICES 1.09 Network Boot Services for System Installations B5724AA_APZ.Ignite-UX.FILE-SRV-10-01 1.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.FILE-SRV-10-10 1.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.FILE-SRV-10-20 1.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.IGNITE 1.09 Graphical Ignite User Interface for Installations B5724AA_APZ.Ignite-UX.IGNT-ENG-A-MAN 1.09 Ignite-UX Manual Pages B5724AA_APZ.Ignite-UX.MGMT-TOOLS 1.09 Tools for Managing Data Files on an Ignition Server B5724AA_APZ.Ignite-UX.OBAM-RUN 1.09 User Interface Libraries Needed for Older Systems

34. Ignite-UX Server Requirements • HP 9000 Series computer • X11 Display server • HP-UX version 10.01 or higher; 10.20 is preferred version to get DHCP support • NFS Server • Activate tftp service in /etc/inetd.conf • 75 Mbytes of disk space for entire product • Files are installed under /var/opt/ignite, /opt/ignite and /etc/opt/ignite • Depots created under /var/opt/ignite/depots (can increase disk space significantly!) • Cannot have both NetInstall and Ignite-UX loaded concurrently • Network access to clients • Export /var/opt/ignite/clients

35. Ignite-UX Minimum Client Requirements • HP 9000 Series computer with PA 1.1 or later. • 32MB Ram • Distribution media must be HP-UX 10.01 or greater. • Network connectivity to Ignite-UX server. • If client is across gateway from server, there must be a boot helper on the local lan if the client does not have a running OS.

36. Software Installation • Use swinstall to install software swinstall B5724AA_APZ • Control scripts will: • ensure NetInstall is not on system • modify /etc/inetd.conf to enable tftp and instl_bootps services • add /opt/ignite/bin to /etc/PATH • add /opt/ignite/share/man to/etc/MANPATH • enable rbootd and start it if necessary • preserve existing INSTALLFS data or initialize it on first installation

37. Ignite-UX Configuration: Server Options • Execute as root: /opt/ignite/bin/ignite • Select Options->Server Configuration • Select Server Options • Set fields as follows: Default Configuration: HP-UX B.10.20 Default Default Printer: <select a printer> Client Timeouts: 40 Run client installation UI on: server

38. Server Customization: IP Address Management • During boot, clients need a temporary IP address • Enter a range of IP addresses • Permanent IP addresses are distributed via DHCP • Caution if you modify the DHCP class ID or DHCP Addresses are temporary • If addresses are temporary, they are used only during install phase • Enter a range of IP addresses

39. IUX Configuration: Session Options • Controls the behavior of Ignite-UX for all clients • Some of these are geared towards manufacturers who use Ignite-UX

40. Server Customization • Run /opt/ignite/bin/ignite At startup, ignite will try to export /var/opt/ignite/clients. NOTE: This is a typical configuration failure situation. Why? • _______________________________________ • _______________________________________ • Configure the server options Select "Options->Server Configuration" • Configure temporary and permanent IP address for client/target system by selecting "Add booting IP Addresses"

41. Chapter 3 • Understanding Config files from tree level.

42. The Config Files • /var/opt/ignite/INDEX • /opt/ignite/data/Rel_{release}/config • /var/opt/ignite/data/Rel_{release}/* • /var/opt/ignite/config.local • /opt/ignite/boot/INSTALLFS • /var/opt/ignite/clients/0x{LLA}/config • /var/opt/ignite/saved_cfgs/*

43. >man 4 instl_adm • instl_adm (4) man page is the best place to get configuration file syntax descriptions.

44. /var/opt/ignite/INDEX • INDEX file contains a list of valid configurations. Each configuration is made up of one or more config files located in /var/opt/ignite/data/Rel_{release}/*

45. /var/opt/ignite/INDEX Default Index file for Ignite-UX # /var/opt/ignite/INDEX: Ignite-UX configurations. cfg "HP-UX B.10.20 Default" { description "This selection supplies the default system configuration that HP supplies for the B.10.20 release." "/opt/ignite/data/Rel_B.10.20/config" "/var/opt/ignite/config.local" }= TRUE cfg "HP-UX B.10.10 Default" { description "This selection supplies the default system configuration that HP supplies for the B.10.10 release." "/opt/ignite/data/Rel_B.10.10/config" "/var/opt/ignite/config.local" }

46. /opt/ignite/data/Rel_{release}/config • HP supplied set of disk and filesystem layout defaults for each OS release • {release} is the result of the uname -r command. • e.g. /opt/ignite/data/Rel_B.10.20/config contains the default disk layouts for the HP-UX 10.20 release.

47. Config file example - Disk Layout /opt/ignite/data/Rel_B.10.20/config _hp_disk_layout = { "Whole disk (not LVM) with HFS", "Logical Volume Manager (LVM) with HFS", "Logical Volume Manager (LVM) with VxFS" } _hp_disk_layout == "Whole disk (not LVM) with HFS" { partitioned_disk { physical_volume disk[_hp_root_disk] fs_partition { usage = HFS size = remaining mount_point = "/" disk[_hp_root_disk].size < 300Mb { # For really small disks, tune down minfree # in order to gain some disk space. minfree = 5 } } } } A short excerpt from the file

48. Small excerpt of config file Example of Swap Definitions in /opt/ignite/data/Rel_B.10.20/config # default (recommended) swap size is 2 X memory init _hp_pri_swap = MEMORY * 2 # Put an upper bounds of 512Mb to the default swap size _hp_pri_swap > 512Mb { init _hp_pri_swap = 512Mb } # Use a 128Mb as the default minimum amount of swap configured on any # system. The real swap space will be reduced down to _hp_min_swap if # there is not enough filesystem space. (_hp_pri_swap < 128Mb) { init _hp_pri_swap = 128Mb } # Initialize the swap range minimum to what the default _hp_min_swap = _hp_pri_swap # If the system is limited on resources, then reduce the minimum so # that the OS has a better chance of fitting. The swap size will # sill be set to the recommended value if there is enough disk space. (_hp_min_swap > 192Mb & disk[_hp_root_disk].size < 1800Mb) { _hp_min_swap = 192Mb } (_hp_min_swap > 96Mb & disk[_hp_root_disk].size < 700Mb) { _hp_min_swap = 96Mb } (_hp_min_swap > 68Mb & disk[_hp_root_disk].size < 600Mb) { _hp_min_swap = 68Mb }

49. /var/opt/ignite/data/Rel_{release}/* • Software description of a single SD depot • Describe software available from SD depots are automatically generated via make_config(1m) • One config file per SD depot is created

50. /var/opt/ignite/data/Rel_{release}/* • software description of an archive. • hand-built config file to allow access to non-SD software archives. • archives can either be in tar or cpio format. • example files can be found in /opt/ignite/data/examples