Excerpt |
---|
This page describes how to create a Linux base image. |
These instructions should work regardless of the provisioning engine being used. If you are using these instructions to create an xCAT bare metal image, ignore the sections with titles beginning with VMware Only:. This document assumes familiarity with xCAT and VMware.Terminology
- Management node: Linux server with the following components installed:
- Compute node: Refers to the target blade or virtual machine on which Windows is installed.
- Provisioning engine: Software which is able to interact with the compute node making it possible to install an OS on it
- VCL can utilize several different provisioning engines including xCAT, VMware Server, VMware ESX, and VMware ESXi. xCAT is a cluster management tool used to install images on bare metal blades.\
- The provisioning engine may be a hypervisor if the compute nodes are virtual machines (VMware)
- The provisioning engine may interact with the BladeCenter's management module if the compute nodes are IBM blades (xCAT)
- The provisioning engine may utilize IMPI if the compute nodes support it (xCAT)
Requirements
You will need the following:
Requirements
- Computer being captured has Compute node has already been added to the VCL database
- Compute node Computer has been installed with Linux distro, distro's currently supported are
- CentOS,Redhat AS,Fedora core, Ubuntu
- Two network adapters are enabled on compute node OS, i.e. eth0, eth1the computer:
- eth0 - connected to the private network
- eth1 - connected to the public network
- The ability to log in as root via SSH using an Ability to login as root via ssh identity key on the private network from management node
Configure SSH Identity Key Authentication
- On the Linux computer being captured, create a /root/.
...
- ssh directory:
- On the management node, copy the public SSH identity key to the authorized_keys file on the Linux computer being captured:
Tip |
---|
scp /etc/vcl/vcl.key.pub <hostname or IP address>:/root/.ssh/authorized_keys |
...
- Or replace the above two steps with the following on the
...
- management node:
Tip |
---|
ssh-copy-id -i /etc/vcl/vcl.key <hostname or IP address> |
- Make sure you can login from the management node to the Linux computer being captured using the identity key:
Tip |
---|
ssh -i /etc/vcl/vcl.key <hostname or IP address> |
Configure the ifcfg-* Files
- Navigate to the network-scripts directory:
Tip |
---|
cd /etc/sysconfig/network-scripts |
- Delete any ifcfg-*.bak files:
Tip |
---|
rm -f /etc/sysconfig/network-scripts/ifcfg-*.bak |
- Edit every ifcfg-eth* file in the network-scripts directory. Remove the HWADDRESS= line: The ifcfg-eth0 file should contain the following:
No Format |
---|
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
|
The ifcfg-eth1 file should contain the following: No Format |
---|
DEVICE=eth1
BOOTPROTO=dhcp
ONBOOT=yes
|
- Reboot the computer:
- Check the ifcfg-eth* files to make sure there are no ifcfg-eth* files and that the HWADDRESS= lines have not been automatically added back:
Tip |
---|
ls /etc/sysconfig/network-scripts |
Tip |
---|
cat /etc/sysconfig/network-scripts/ifcfg-eth0 |
Tip |
---|
cat /etc/sysconfig/network-scripts/ifcfg-eth1 |
Include Page |
---|
| Capture A Base Image |
---|
| Capture A Base Image |
---|
|
Setting up the OS for VCL
The main dependency for linux OS's is that the vcl management node has to login as root over ssh using an ssh identity key on the private network, which is normally eth0. This means there are two distinct ssh services, one for the private network and one for the external public network.
...
- Purpose is to listen only on the private IP address and allows root access from the management node only using an ssh identity key
...