Run the following playbook, ensuring that you specify only your UEFI SLES nodes using the nodelist. This playbook will reconfigure Cobbler for the nodes listed.

ardana > cd ~/scratch/ansible/next/ardana/ansible
ardana > ansible-playbook prepare-sles-grub2.yml -e nodelist=node1[,node2,node3]

Re-image the node(s), ensuring that you only specify your UEFI SLES nodes using the nodelist.

ardana > cd ~/openstack/ardana/ansible
ardana > ansible-playbook -i hosts/localhost bm-reimage.yml \
-e nodelist=node1[,node2,node3]

Back up the grub.cfg-* files in /srv/tftpboot/ as they will be overwritten when running the cobbler-deploy playbook on the next step. You will need these files if you need to reimage the nodes in the future.

Run the cobbler-deploy.yml playbook, which will reset Cobbler back to the default values:

ardana > cd ~/openstack/ardana/ansible
ardana > ansible-playbook -i hosts/localhost cobbler-deploy.yml

Take note of the IP address of the Cloud Lifecycle Manager node. It will be used below during Section 19.4.6, “Add zypper repository”.

Mount or copy the contents of SLE-12-SP3-Server-DVD-x86_64-GM-DVD1.iso to /srv/www/suse-12.3/x86_64/repos/ardana/sles12/zypper/OS/

Boot the SUSE Linux Enterprise Server 12 SP3 ISO.

Agree to the license

Edit the network settings, enter the the management network IP address recorded earlier. It is not necessary to enter a Hostname/. For product registration to work correctly, you must provide a DNS server. Enter the Name Server IP address and the Default IPv4 Gateway.

Additional System Probing will occur.

On the Registration page, you can skip registration if the database server does not have a external interface or if there is no SMT server on the MGMT LAN.

No Add On Products are needed.

For System Role, select Default System. Do not select KVM Virtualization Host.

Partitioning

1. Select Expert Partitioner and Rescan Devices to clear Proposed Settings.

2. Delete all Volume Groups.

3. Under the root of the directory tree, delete /dev/sda.

4. Delete any other partitions on any other drives.

5. Add Partition under sda, called ardana, with a Custom Size of 250MB.

6. Add an EFI Boot Partition. Partition should be formatted as FAT and mounted at /boot/efi.

7. Add Partition with all the remaining space (Maximum Size). The role for this partition is Raw Volume (unformatted). It should not be mounted. It should not be formatted.

8. Select Volume Management and add a volume group to /dev/sda2 called ardana-vg.

9. Add an LV to ardana-vg called root, Type of Normal Volume, Custom Size of 50GB, Raw Volume (unformatted). Format as Ext4 File System and mount at /.

10. Acknowledge the warning about having no swap partition.

11. Press Next on the Suggested Partitioning page.

Pick your Time Zone and check Hardware Clock Set to UTC.

Create a user named ardana and a password for system administrator. Do not check Automatic Login.

On the Installation Settings page:

Press Install and Confirm Installation with the Install button.

Installation will begin and the system will reboot automatically when installation is complete.

When the system is booted, log in as root, using the system administrator set during installation.

Set up the ardana user and add ardana to the sudoers group.

root # useradd -s /bin/bash -d /var/lib/ardana -m
    ardana
root # passwd ardana

Enter and retype the password for user ardana.

root # echo "ardana ALL=(ALL) NOPASSWD:ALL" | sudo tee -a \
    /etc/sudoers.d/ardana

Add an ardana group (id 1000) and change group owner to ardana.

root # groupadd --gid 1000 ardana
root # chown -R ardana:ardana /var/lib/ardana

Disconnect the installation ISO. List repositories and remove the repository that was used for the installation.

root # zypper lr

Identify the Name of the repository to remove.

root # zypper rr REPOSITORY_NAME

Copy the SSH key from the Cloud Lifecycle Manager.

root # ssh-copy-id ardana@DEPLOYER_IP_ADDRESS

Log in to the SLES via SSH.

Continue with the site.yml playbook to scale out the node.

Use the ip addr command to find out what network devices are on your system:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether f0:92:1c:05:89:70 brd ff:ff:ff:ff:ff:ff
    inet 10.13.111.178/26 brd 10.13.111.191 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::f292:1cff:fe05:8970/64 scope link
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether f0:92:1c:05:89:74 brd ff:ff:ff:ff:ff:ff

Identify the one that matches the MAC address of your server and edit the corresponding config file in /etc/sysconfig/network-scripts.

vi /etc/sysconfig/network-scripts/ifcfg-eno1

Edit the IPADDR and NETMASK values to match your environment. Note that the IPADDR is used in the corresponding stanza in servers.yml. You may also need to set BOOTPROTO to none.

TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=eno1
UUID=36060f7a-12da-469b-a1da-ee730a3b1d7c
DEVICE=eno1
ONBOOT=yes
NETMASK=255.255.255.192
IPADDR=10.13.111.14

[OPTIONAL] Reboot your SLES node and ensure that it can be accessed from the Cloud Lifecycle Manager.