©2009 HP Confidential 1 ©2010 HP / Intel / Red Hat restricted 1 Bruno CornecHP, Open Source Profession Lead Jean-Marc AndréOSSI Solution Architect The ProLiant USB Setup Key

©2009 HP Confidential 2 ©2010 HP / Intel / Red Hat restricted 2 Introducing Myself ● Software engineering and Unices since 1988 ● Mostly Configuration Management Systems (CMS), Build systems, quality tools, on multiple commercial Unix systems ● Discover Open Source & Linux (OSL) & first contributions in 1993 ● Full time on OSL since 1995, first as HP reseller ● Currently : ● Master Technology Architect on OSL for the HP/Intel Solution Center, Grenoble ● OSL HP Advocate ● EMEA OSL HP Profession Lead ● Solutions Linux Conference and OWF board member ● MondoRescue, Dploy.org, Project-Builder.org project lead ● LinuxCOE, mrepo, tellico, rinse, fossology, collectl contributor ● FOSSBazaar and OSL Governance enthusiast ● Mandriva, Mageia, Fedora packager

©2009 HP Confidential 3 ©2010 HP / Intel / Red Hat restricted 3 Agenda

©2009 HP Confidential 4 ©2010 HP / Intel / Red Hat restricted 4 Objective and Agenda Objective: To describe HP's Open Source involvement, The HP + Intel + Red Hat initiative (OSSI) and how it can help the respective actors deliver best in class Open Source & Linux (OSL) solutions in ProLiant Setup. Agenda: ● ProLiant USB Setup Key (aka PUSK) ● Project Origins and Choices, ● Project Features, ● Project Status ● Project Future

©2009 HP Confidential 5 ©2010 HP / Intel / Red Hat restricted 5 ProLiant USB Setup Key

©2009 HP Confidential 6 ©2010 HP / Intel / Red Hat restricted 6 PUSK Origins ›Customer request to setup a DL 380 G7 BIOS, Smart Array and iLO without any keyboard, mouse or screen attached to it on a remote site where minimal IT knowledge is available. ›The operator in charge of the configuration just has a laptop (Windows based in most of the cases) to customize the server configuration (IP address, Netmask, Gateway, License Key and Password for iLO). ›It should be as easy as: – Get the server out of the box; – Rack it, plug it and power it on; – Use a bootable device to do the hardware configuration; – Once the configuration is done, the server shuts itself down.

©2009 HP Confidential 7 ©2010 HP / Intel / Red Hat restricted 7 PUSK Choices ›The HP ProLiant USB setup key (PUSK) is a set of tools working together with the HP Smart Start Scripting Tool Kit (SSSTK) and HP Software Depot Repository (SDR) to create a bootable USB key to easily and automatically capture and deploy BIOS, RAID and iLO configurations on HP ProLiant servers. ›The PUSK allows to easily modify configuration on site, while also storing logs of the setup run. ›The PUSK is easily mountable from both a Windows (operator machine) or a Linux (deployed server) environment using a VFAT FS. ›The PUSK is built from a master machine using the running distribution (RHEL 6.1 or 6.2 for this project) and the HP SDR. ›The PUSK provide 1 simple text based config file which has to be configured for iLO setup (generic need). ›The other extracted configurations are also modifiable in XML format, as well as the boot configuration done with syslinux.

©2009 HP Confidential 8 ©2010 HP / Intel / Red Hat restricted 8 PUSK Features ›The HP ProLiant USB setup key (PUSK) provides the following features: – Capture the BIOS, RAID and iLO settings on a 'master' server; – Deploy a previously captured BIOS, RAID and iLO configuration on a target server (iLO settings can be customized); – Deploy a basic iLO configuration; – Upgrade the BIOS, NICs, HBA, Smart Array controllers firmware if needed. – Boot to a shell in order to debug If no boot entry is selected after 30 seconds, the PUSK will boot in deploy mode.

©2009 HP Confidential 9 ©2010 HP / Intel / Red Hat restricted 9 PUSK capture mode ›The PUSK provides a capture mode using the HP SSSTK tools to capture the current BIOS, RAID and iLO configuration on the server. – The BIOS configuration is saved on the USB key under 'data_files/conrep.dat' – The Smart Array controllers configuration is saved under 'data_files/cpqacuxe.dat' – The iLO configuration file is saved under 'data_files/hponcfg.dat' After the captured operations have been performed, the generated logs are saved on the USB key in 'log/capture_YYYYMMDD-HHmm.log', the USB key is unmounted and the server shuts itself down.

©2009 HP Confidential 1010 ©2010 HP / Intel / Red Hat restricted 1010 PUSK deploy mode ›The PUSK provides a deploy mode using the HP SSSTK tools to deply the previously captured BIOS, RAID and iLO configuration on the server from the previously mentioned stored config files. ›iLO IP configuration, License key and password can be easily customized in an editable text file on the USB key (under 'config/ilo'). – This customization uses a python script to inject the modified text data into the hponcfg XML format. ›A basic deploy mode also exists to restore an iLO configuration to a default mode where nothing else works. It uses the 'data_files/ilo.dat' without variable substitution, nor any addition. ›In case.scexe files are present under the 'fw_files' directory, they will be applied, only when newer, using the 'fw' boot entry.

©2009 HP Confidential1 ©2010 HP / Intel / Red Hat restricted1 PUSK architecture ›The PUSK structure looks like the one nearby ›4 Firmware will be potentially applied here ›The syslinux directory contains an initramfs.img file produced by dracut to have all drivers at boot time ›The squashfs.img file produced also by dracut contains the files coming from the original distribution with our customization layer. ›The init script provided by dracut launches at the end of the boot sequence the /etc/rc.d/rc.local script which has been customized to detect the boot command line parameters and launch the relevant script under /ssstk to perform one of the 5 actions mentioned earlier

©2009 HP Confidential 1212 ©2010 HP / Intel / Red Hat restricted 1212 PUSK content ›Content of the PUSK project: ›(Cf: – rpmbootstrap.sh: Create ext3fs.img files with the mini linux distribution (launched first) – mkusbkey.sh : Create the bootable USB key on the device(can be a /dev/sdx or /dev/loop one). Prerequisite build: the system as RHEL and SDR yum access configured – setupkey.spec: SPEC file (build RPM with make rpm) – customized: Customized init scripts, pythin tool and SSSTK scripts – syslinux.cfg: SYSLINUX configuration file – hp-psp.repo: YUM repo pointing to HP SDR – An automake/autoconf structure is also provided

©2009 HP Confidential 1313 ©2010 HP / Intel / Red Hat restricted 1313 PUSK future ›The PUSK as a ProLiant delivery ? ›Make a Gen8 version using latest SDR tools. ›Fusion of this key building and the MondoRescue boot media building into pbmkbm (part of project-builder.org) ›Use of the more generic rpmbootstrap (also part of project-builder.org) to build the environment in a isolated way, instead of the current dedicated script. ›Extend the etree python script to support the other config files ›Sos plugin also developed for the same project to be proposed for SDR and pushed upstream ›Your feature here !!!

©2009 HP Confidential 1414 ©2010 HP / Intel / Red Hat restricted 1414 References Some reference sites : › › › › builder.org/browser/projects/proliantusbkey/0.9.6http://trac.project- builder.org/browser/projects/proliantusbkey/0.9.6 › ›

©2009 HP Confidential 1515 ©2010 HP / Intel / Red Hat restricted 1515

©2009 HP Confidential 1616 ©2010 HP / Intel / Red Hat restricted 1616 Thank you ! Q&A