Difference between revisions of "Release Notes 7.1"

From LEAP Wiki
Jump to: navigation, search
(Installation)
m (Installation)
Line 46: Line 46:
 
<li>Add the following options to the dhcp server's dhcpd.conf (It might be advisable to create a new group in the conf file for LEAP installations):  
 
<li>Add the following options to the dhcp server's dhcpd.conf (It might be advisable to create a new group in the conf file for LEAP installations):  
 
<pre>next-server [ip-address-of-tftp-server];  
 
<pre>next-server [ip-address-of-tftp-server];  
filename "leap/bootaa64.efi"; </pre> </li>
+
filename "leap/BOOTAA64.EFI"; </pre> </li>
  
 
<li>Download this file and extract it in the root directory of the TFTP server: http://dl.leapproject.ca/7/leap-tftp-files-20150717.tgz </li>
 
<li>Download this file and extract it in the root directory of the TFTP server: http://dl.leapproject.ca/7/leap-tftp-files-20150717.tgz </li>

Revision as of 22:48, 17 July 2015

Important.png
This is a draft only!
It is still under construction and content may change. Do not rely on this information.

LEAP 7.1

Release Date: July 17th 2015
Kernel Version: 4.1.0
Architecture: ARMv8a/AArch64

== Introduction The LEAP (Linux for Enterprise ARM Platforms) Project is a Linux software distribution specifically intended to showcase the capabilities of emerging 64-bit Enterprise ARM Server platforms under a variety of workloads. It has as its foundation an ARMv8/AArch64 build of the CentOS 7.1 sources, with various patches, backports, and package up-versioning as appropriate, plus additional benchmarking packages to enable the effective evaluation and demonstration of AArch64 server systems.

The LEAP software environment is very similar to enterprise Linux systems on traditional x86_64 servers, simplifying the task of transitioning workloads to ARM64 servers for evaluation.

Supported Hardware

APM X-Gene X-C1

  • UEFI firmware
  • 1G (1GBase-T) network interface

AMD Overdrive Seattle (Bx)

  • UEFI firmware
  • 1G (1GBase-T) network interface
  • 10G (10GBase-KR) network interface

Installation

Supported installation methods:

  • PXE Boot with a Kickstart file (Default)
  • PXE Boot with the text mode installer
  • PXE Boot with the VNC GUI installer
  • Network installations via HTTP, FTP or NFS

WARNING: The default Kickstart file uses the entire first SATA disk (/dev/sda) and will wipe out any pre-existing partions.

PXE Boot

The requirements to enable a PXE Boot installation are as follows:

  • A DHCP Server
  • A TFTP Server

Instructions as to how these two servers can be set up and more generally how PXE Booting is set up can be found in Fedora's PXE boot documentation.

After the set up of the above servers proceed as follows:

  1. Add the following options to the dhcp server's dhcpd.conf (It might be advisable to create a new group in the conf file for LEAP installations):
    next-server [ip-address-of-tftp-server]; 
    filename "leap/BOOTAA64.EFI"; 
  2. Download this file and extract it in the root directory of the TFTP server: http://dl.leapproject.ca/7/leap-tftp-files-20150717.tgz
  3. This file structure will be produced:
    leap 
    ├── BOOTAA64.EFI
    ├── EFI
    │   ├── BOOT
    │   │   ├── BOOTAA64.EFI 
    │   │   └── fonts
    │   │       └── unicode.pf2
    │   └── leap
    │       ├── initrd.img
    │       └── vmlinuz
    ├── fonts
    │   └── unicode.pf2
    ├── grubaa64.efi
    ├── grub.cfg
    └── MokManager.efi
    
  4. Start up the TFTP and DHCP server.
  5. On the APM X-GENE X-C1 via serial console:
    1. Make sure this machine is being served by the DHCP server.
    2. Go into the UEFI boot menu.
    3. Add a new boot option with the Boot Device Manager.
    4. Select the PXE boot option where the MAC Address matches the respective entry for this X-C1 in the dhcpd.conf file on the DHCP server.
    5. Name the option "PXE Boot".
    6. When asked for additional arguments, there are none required.
    7. Boot from this new "PXE Boot" option.
    8. The installer should now start. Proceed with the installion through kickstart, VNC or text mode.
    9. When the installation is complete, it will reboot into the installed LEAP system
  6. On the AMD Overdrive Seattle via serial console:
    1. Make sure this machine is being served by the dhcp server.
    2. Go into the UEFI boot menu.
    3. Select the network interface boot option where the MAC Address matches the respective entry for this Seattle in the dhcpd.conf file on the DHCP server.
    4. The installer should now start. Proceed with the installion through kickstart, VNC or text mode.
    5. When the installation is complete, it will reboot into the installed LEAP system

Installing with an Alternate Kickstart Configuration

The Kickstart file controls the installation: it determines the partitioning, root password, network configuration, software installed, and more.

To use an alternate Kickstart configuration file:

  1. Download the file http://dl.leapproject.ca/7/os/aarch64/kickstart/leap.ks
  2. Modify that file as desired.
  3. Install the Kickstart file on a location accessible via http to the target machine.
  4. Edit the grub.cfg file on your tftp server: change the URL in the boot argument 'ks=http://dl.leapproject.ca/7/os/aarch64/kickstart/leap.ks' to point to your edited Kickstart file.

For assistance on customizing your Kickstart file, documentation on how Kickstart installations work as well as the variety of installation options available can be found on the official github page for pykickstart.

Non-Kickstart Installation

To allow for Non-Kickstart installations edit the grub.cfg file on your tftp server and change the boot argument 'ks=http://dl.leapproject.ca/7/os/aarch64/kickstart/leap.ks' to 'inst.repo={URL of the repo}'.

For more information on Anaconda boot arguments to customize your installation, refer to the Anaconda github.io page.

Post Installation

Logging In after a Kickstart Installation

One may log into the newly installed LEAP server through serial connection or ssh. Using the default Kickstart file the following root user is created:

   Username: root
   Password: leap

Obviously, public-facing systems should be secured against root login via ssh.

Updating and Installing Additional Software

To update the system to include all current updates (this should be run periodically):

   yum update 

To install additional software, use standard yum commands:

   yum list pattern # lists packages with pattern in the package name
   yum install package # installs the named package
   yum install --skip-broken @group # installs the named group of packages
   yum remove package # removes the named package
   yum info package # provides information about uninstalled package
   rpm -qi package # provides information about installed package

Known Issues

  • UEFI secure boot features are not used to authenticate the kernel.
  • The 10G SFP+ interface is currently disabled on the APM X-C1 with this kernel. This will be addressed in a kernel update.

Additional Tools

These benchmarking tools have been added to the initial release of LEAP:

  • Iozone
  • Fio
  • Bonnie++

Communicating with the LEAP Team and Community