2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-06-11 17:28:49 +00:00

Add RHEV KVM documentation

This commit is contained in:
Mark Gurevich
2016-10-17 16:09:27 -04:00
parent aedd75c8a6
commit 701477eaaf
2 changed files with 69 additions and 15 deletions
@@ -1,20 +1,21 @@
Setup PowerKVM Hypervisor
=========================
Setup Hypervisor
================
Provision Hypervisor with PowerKVM
----------------------------------
Provision Hypervisor
--------------------
Please follow the :ref:`Diskful Installation <diskful_installation>` to provision kvm hypervisor with PowerKVM, several customization steps should be taken into consideration.
Follow the :ref:`Diskful Installation <diskful_installation>` to provision kvm hypervisor for PowerKVM or RHEV.
To demonstrate the brief steps on hypervisor provision, take **ibm-powerkvm-3.1.0.0-39.0-ppc64le-gold-201511041419.iso** for example here:
#. Obtain a PowerKVM iso and create PowerKVM osimages with it: ::
* **[PowerKVM]**
Obtain a PowerKVM iso and create PowerKVM osimages with it: ::
copycds ibm-powerkvm-3.1.0.0-39.0-ppc64le-gold-201511041419.iso
The following PowerKVM osimage will be created on success ::
The following PowerKVM osimage will be created ::
# lsdef -t osimage -o pkvm3.1-ppc64le-install-compute
Object name: pkvm3.1-ppc64le-install-compute
@@ -29,9 +30,52 @@ To demonstrate the brief steps on hypervisor provision, take **ibm-powerkvm-3.1.
provmethod=install
template=/opt/xcat/share/xcat/install/pkvm/compute.pkvm3.ppc64le.tmpl
* **[RHEV]**
At the time of this writing there is no ISO image availabe for RHEV. Individual RPM packages need to be downloaded.
* Download *Management-Agent-Power-7* and *Power_Tools-7* RPMs from RedHat to the xCAT management node. Steps below assume all RPMs were downloaded to */install/post/otherpkgs/rhels7.3/ppc64le/RHEV4/4.0-GA* directory.
* Run ``createrepo .`` in the */install/post/otherpkgs/rhels7.3/ppc64le/RHEV4/4.0-GA* directory.
* Create new osimage definition based on an existing RH7 osimage definition ::
mkdef -t osimage -o rhels7.3-ppc64le-RHEV4-install-compute --template rhels7.3-ppc64le-install-compute
* Modify ``otherpkgdir`` attribute to point to the package directory with downloaded RPMs ::
chdef -t osimage rhels7.3-ppc64le-RHEV4-install-compute otherpkgdir=/install/post/otherpkgs/rhels7.3/ppc64le/RHEV4/4.0-GA
* Create a new file */opt/xcat/share/xcat/install/rh/other.pkglist* to list required packages ::
libvirt
qemu-kvm-rhev
qemu-kvm-tools-rhev
virt-manager-common
virt-install
* Modify ``otherpkglist`` attribute to point to the file from the step above ::
chdef -t osimage rhels7.3-snap3-ppc64le-RHEV4-install-compute otherpkglist=/opt/xcat/share/xcat/install/rh/other.pkglist
* The RHEV osimage should look similar to: ::
Object name: rhels7.3-ppc64le-RHEV4-install-compute
imagetype=linux
osarch=ppc64le
osdistroname=rhels7.3-ppc64le
osname=Linux
osvers=rhels7.3
otherpkgdir=/install/post/otherpkgs/rhels7.3/ppc64le/RHEV4/4.0-GA
otherpkglist=/opt/xcat/share/xcat/install/rh/other.pkglist
pkgdir=/install/rhels7.3/ppc64le
pkglist=/install/custom/install/rh/compute.rhels7.ppc64le.pkglist
profile=compute
provmethod=install
template=/opt/xcat/share/xcat/install/rh/compute.rhels7.tmpl
#. Customize the hypervisor node definition to create network bridge
xCAT ships a postscript **xHRM** to create a network bridge on kvm host during installation/netbooting. Please specify the **xHRM** with appropriate parameters in **postscripts** attibute. Here is some examples on this:
xCAT ships a postscript **xHRM** to create a network bridge on kvm host during installation/netbooting. Specify the **xHRM** with appropriate parameters in **postscripts** attibute. Here is some examples on this:
To create a bridge with default name 'default' against the installation network device which was specified by **installnic** attribute ::
@@ -65,16 +109,16 @@ To demonstrate the brief steps on hypervisor provision, take **ibm-powerkvm-3.1.
chmod 755 /install/postscripts/mountvms
chdef kvmhost1 -p postscripts=mountvms
#. Provision the hypervisor node with the PowerKVM osimage ::
#. Provision the hypervisor node with the osimage ::
nodeset kvmhost1 osimage=pkvm3.1-ppc64le-install-compute
nodeset kvmhost1 osimage=<osimage_name>
rpower kvmhost1 boot
Create network bridge on hypervisor
------------------------------------
To launch VMs, a network bridge must be created on the PowerKVM hypervisors.
To launch VMs, a network bridge must be created on the KVM hypervisor.
If the hypervisor is provisioned successfully according to the steps described above, a network bridge will be created and attached to a physical interface. This can be checked by running ``brctl show`` on the hypervisor to show the network bridge information, please make sure a network bridge has been created and configured according to the parameters passed to postscript "xHRM" ::
@@ -83,10 +127,20 @@ If the hypervisor is provisioned successfully according to the steps described a
br0 8000.000000000000 no eth0
If the network bridge is not created or configured successfully, please run "xHRM" with **updatenode** on managememt node to create it manually:::
If the network bridge is not created or configured successfully, run "xHRM" with **updatenode** on managememt node to create it manually:::
updatenode kvmhost1 -P "xHRM bridgeprereq eth0:br0"
Start libvirtd service
----------------------
Verify **libvirtd** service is running: ::
systemctl status libvirtd
If service is not running, it can be started with: ::
systemctl start libvirtd
.. [1] Every standard libvirt installation provides NAT based connectivity to virtual machines out of the box using the "virtual bridge" interfaces (virbr0, virbr1, etc) Those will be created by default.
@@ -32,6 +32,6 @@ This section introduces the steps of management node preparation, KVM hypervisor
:maxdepth: 2
kvmMN.rst
powerKVM.rst
hypervisorKVM.rst
manage_vms.rst
FAQ.rst