Ignite-UX Overview. Ignite-UX Key Concepts Ignite-UX Detailed Presentation

  • Published on
    21-Jan-2016

  • View
    224

  • Download
    0

Embed Size (px)

Transcript

  • Ignite-UX

    Overview

  • Ignite-UX

    Key Concepts

  • Ignite-UX

    Detailed Presentation

  • What is Ignite-UX?Process for initial system deploymentTrue client-server model:can install multiple target machines simultaneouslyallows target customization and status monitoringAbility to build and reuse standard configurationsAbility to do site-specific customizationAbility to automate installation processExtensible system manifest capabilityAbility to install software from multiple sources in a single session!

  • What else is Ignite-UX?Process for system re-deployment or SW upgradesAll 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 - bootsysUse the GUI to define what gets loaded or use a golden system imageGUI or command line control

  • Ignite-UX versus Cold Install

    Cold InstallIgnite-UXInstallation MethodsInstall from Local media"Pull" Install from Network ServersInstall from Local media"Pull" Install from Network Servers"Push" Install from Network Servers"Re-deploy" Existing machinesServer CapabilityServes Single Release that Server is RunningCan Serve Multiple Releases (10.01 and forward)User InterfaceTUI running on targetTUI running on TargetGUI running on ServerSoftware FormatsSoftware DistributorSD, cpio, tarMultiple sources in one sessionSystem Attributes Which Can Be SpecifiedA lot!Even more!More script hooksset_parms infoProduce a System ManifestNoYes!

  • Ignite-UX versus SD

    Ignite-UXSDPurposeComplete installs of system software.Manages software on an existing system.Disk space considerationsPerforms disk and file system layout.Complains if it's short on disk space.Objects handledHandles SD and other formats like tar or cpio, and even OS archives.Knows about standard bundles, products and filesets.

  • Ignite-UX: A Tale of Two ToolsIgnite-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.

  • Segmentation of Ignite-UX Users

    HP ManufacturingHigh volumes of pre-installed HW & SWProduction line environment, high throughputHighly automated, no human interactionStandard configurations customizable via SISPTwo-tier distributorsMedium-high volumesSmall unit ordersManual process via GUIMore customized configurationsHigh Volume CustomersSmall set of standard/certified configurationsCustomized to end user requirementsReinstallation of systems rather than updateInventory and IP address managementLow Volume CustomersOften use ignited systemsNo need for standard configurationsInfrequent installs only on "as needed" basisSingle point access of system viewCustomer EngineerComplex system installations at customer siteExtensive use of system diagnosticsHardware and software installation, network connectivityThird-party applications loaded

  • Value Propositions for Ignite-UX UsersHP ManufacturersCapability of high volume, standard OS bundle installsMinimal time per install, multiple simultaneous installsEase of linkage to OPHigh reliabilityTwo-tier DistributorsCapability of high volume, standard OS bundle installsMinimal time per installUse multiple source formatsAdditional post-installation customizationHigh Volume CustomersHigh volume installsCreate and install certified standard configurationsPerform post-installation customizationsQuery process and see configurationLow Volume Customers

    Install from all sources (CD-ROM, DAT, network)Provide one-step installation from default configurationCustomize basic configuration parametersQuery process and see configurationCustomer EngineerInstall from all sources (CD-ROM, DAT, network)Create and install standard configurationsProvide one-step installation from default configurationCustomize basic and advanced configuration parameters

  • Cold Install from Local Media With Ignite-UXBoot from local mediaNo Network RequiredRun UI from the target's consoleTUI version of Server GUI interface (advanced) -or-Guided Tour of Selections (Wizard)Target MachineCDTape

  • Pull Cold Install from Network ServerDo a 'boot lan install' from the client consoleRun UI from target's console (like previous slide)Use previously defined configs on serverTarget MachineServer

  • Welcome to Ignite-UX!Initial screen on system consoleShows summary informationSingle client installationNormal mode is to select Install HP-UX

  • User Interface and Media OptionsPermits choice of source location and user interfaceGuided installation referred to as "wizard mode" which is not available in GUI

  • Basic itool screen: Wizard ModeGuided tour through recommended configuration choicesDoes not allow file system size changes or setting networking parametersGood for novice user

  • Basic itool screen: Advanced ModeObam version of Ignite-UX interfaceTabbed windows look and feel

  • Push Cold Install from Network ServerDo a 'boot lan install' from client console (only interaction needed on client)Run UI at the serverCan do multiple clients at onceTarget MachinesServer

  • Using Ignite-UX Across GatewaysOnly necessary when doing a cold install of an unbootable machine across a gateway from serverBoot helper machine:Must be running 10.*Must install minimum Ignite-UX (Ignite-UX.MinimumRuntime)About 22Mb freePoint to server via instl_admOn target:b lan. installgets install kernel and RAMFS from helper, then connects to serverNot a relay agent"Helper Machine"Target MachineIgnite-UX Server

  • Re-Deploy Existing Machine (bootsys)Useful when target machine is already running HP-UX 9.x or 10.xRun bootsys on server:Copies install kernel, fs down to target disk (uses remsh)Sets up target to boot from install kernelReboots targetTarget boots from disk and connects to serverNo need to ever go to target consoleNetwork topology doesn't matterTarget MachineServerGateway

  • True Client-Server Application ClientTarget CustomizationServerCentral Control and Status Monitoring

  • IUX Server - Main ScreenIcon per client being installedColors used to indicate client statusEasily view status details of any clientEasily see detailed hardware description of any clientReinstall option based on saved install sessionsSort clients by name, status or % completePerforms server configuration tasks

  • IUX Client - Basic ConfigurationFirst screen to install a clientEasy selection of a base configuration from HP supplied defaults or a previously saved sessionProvides for easy selection of basic configuration informationDesigned to provide "GO" option from here

  • IUX Client - Software OptionsEasily choose software packages to installSoftware packages may be SD, tar or cpio formatsCan load multiple packages from multiple sources in a single sessionCan select software category for filtering or easy package locationCategories can be HP or user defined

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

  • IUX Client - File System OptionsRich set of configuration options for setting up disks and file systemsSimpler screen for whole disk file systemsSizes the file systems based on needs of the selected software

  • IUX Client - Advanced OptionsAllows 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

  • Creating your own Customized ConfigurationsSelect a default configuration in UI:e.g. "Default 10.20 Release"Make modifications in the UI to select:How you want disks/file systems allocatedWhat software you want installedWhat scripts you want runetc."Save As" to write your customized config fileOptionally, hand edit the config file to make it hardware independent:Different disk layouts depending on what disks are presentSwap space based on memory sizeetc...

  • The IUX Config FileRecipe for "How to Build a System"Created by UI or by userCan do Conditional Expressions:(memory > 512Mb){init _hp_pri_swap=512Mb}else { init _hp_pri_swap=memory*2}

  • The IUX Index FileDefines a grouping or set of config files

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

  • Chapter 2How to install and configure Ignite-UX

  • Ignite-UX SoftwareThe product is available on the external HP Website located at http://www.software.hp.comProduct numbersB5724AA_APZ (S700)B5725AA_APZ (S800)

  • 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-KERNEL1.09 Installation Boot Kernel for S700/S800 clients B5724AA_APZ.Ignite-UX.BOOT-SERVICES1.09 Network Boot Services for System Installations B5724AA_APZ.Ignite-UX.FILE-SRV-10-011.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.FILE-SRV-10-101.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.FILE-SRV-10-201.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-MAN1.09 Ignite-UX Manual Pages B5724AA_APZ.Ignite-UX.MGMT-TOOLS1.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

  • Ignite-UX Server RequirementsHP 9000 Series computerX11 Display serverHP-UX version 10.01 or higher; 10.20 is preferred version to get DHCP supportNFS ServerActivate tftp service in /etc/inetd.conf75 Mbytes of disk space for entire productFiles are installed under /var/opt/ignite, /opt/ignite and /etc/opt/igniteDepots created under /var/opt/ignite/depots (can increase disk space significantly!)Cannot have both NetInstall and Ignite-UX loaded concurrentlyNetwork access to clientsExport /var/opt/ignite/clients

  • Ignite-UX Minimum Client RequirementsHP 9000 Series computer with PA 1.1 or later.32MB RamDistribution 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.

  • Software InstallationUse swinstall to install softwareswinstall B5724AA_APZControl scripts will:ensure NetInstall is not on systemmodify /etc/inetd.conf to enable tftp and instl_bootps servicesadd /opt/ignite/bin to /etc/PATHadd /opt/ignite/share/man to/etc/MANPATHenable rbootd and start it if necessarypreserve existing INSTALLFS data or initialize it on first installation

  • Ignite-UX Configuration: Server OptionsExecute as root:/opt/ignite/bin/igniteSelect Options->Server ConfigurationSelect Server OptionsSet fields as follows:Default Configuration: HP-UX B.10.20 DefaultDefault Printer: Client Timeouts: 40Run client installation UI on: server

  • Server Customization: IP Address ManagementDuring boot, clients need a temporary IP addressEnter a range of IP addressesPermanent IP addresses are distributed via DHCPCaution if you modify the DHCP class ID or DHCP Addresses are temporaryIf addresses are temporary, they are used only during install phaseEnter a range of IP addresses

  • IUX Configuration: Session OptionsControls the behavior of Ignite-UX for all clientsSome of these are geared towards manufacturers who use Ignite-UX

  • Server CustomizationRun /opt/ignite/bin/igniteAt startup, ignite will try to export /var/opt/ignite/clients.NOTE: This is a typical configuration failure situation. Why?______________________________________________________________________________

    Configure the server optionsSelect "Options->Server Configuration"Configure temporary and permanent IP address for client/target system by selecting "Add booting IP Addresses"

  • Chapter 3Understanding Config files from tree level.

  • 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/*

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

  • /var/opt/ignite/INDEXINDEX 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}/*

  • /var/opt/ignite/INDEXDefault 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"}

  • /opt/ignite/data/Rel_{release}/configHP 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.

  • 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

  • Example of Swap Definitions in /opt/ignite/data/Rel_B.10.20/config

    # default (recommended) swap size is 2 X memoryinit _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...

Recommended

View more >