attach bare metal node to OpenShift

Description

We want to use ephemeral openshift pods as Jenkins slaves and to be able to test virtualization capabilities we need to make sure we have a bare metal node for those pods.

Activity

Show:

Eyal Edri December 25, 2018 at 9:38 AM

closing this as we already have multiple openshift nodes on the cluster and we continue to handle it on a regular basis

Former user November 5, 2018 at 4:26 PM

The problem was caused by stale mounts from back when our storages changed IPs - this was causing ansible to fail.

After cleaning up the mess I was able to add the node to the cluster with zone=ci tag

The preparation steps (for next nodes) were:
1) deploy node via foreman. I used the jenkins-slave group as that one sets up nested KVM. Also ensure "LVM on sda" partitioning scheme is selected to ensure there's space available for containers

2) log in to host and configure docker storage using the existing LVM VG:

echo "VG=vg01" > /etc/sysconfig/docker-storage-setup
docker-storage-setup

3) ensure SSH works from shift-m01 as it's needed by ansible

4) log in to shift-m01 and add the new host into /etc/ansible/hosts under [new_nodes] section
5) run the playbook
cd /root/openshift-ansible
ansible-playbook playbooks/openshift-node/scaleup.yml
6) after the process finishes, move the node to the [nodes] section in /etc/ansible/hosts

could you please check if we can make use of this new node now or some other changes are needed?

Former user November 5, 2018 at 3:54 PM

ovirt-srv08 rebuilt yet the ansible scale-up playbook is failing due to some sort of issue on existing nodes. Investigating to move forward.

Fixed

Details

Assignee

Reporter

Components

Priority

Created November 5, 2018 at 1:59 PM
Updated August 29, 2019 at 2:12 PM
Resolved December 25, 2018 at 9:38 AM