Sunday, August 21, 2016

RHEV host and Self hosted engine upgrade to RHEV 3.6


RHEL Host (RHEV) upgrade:
====================

Applying RHEV updates on Red Hat Enterprise Linux 6


Enable Repos:

#subscription-manager repos --disable=*

#subscription-manager repos --enable=rhel-6-server-rpms

#subscription-manager repos --enable=rhel-6-server-optional-rpms

#subscription-manager repos --enable=rhel-6-server-rhev-mgmt-agent-rpms

#subscription-manager repos –enable=rhel-6-server-supplementary-rpms




Set hosted-engine status to maintenance:

#hosted-engine --vm-status

#hosted-engine --set-maintenance --mode=global


Before installing an update, make sure all previously released errata relevant to the system have been applied.
To access updates when using Red Hat Enterprise Linux 6, launch the graphical update tool through System -> Administration -> Software Update, or from the command line via the following command:
# gpk-update-viewer 
For a command line interface, use the following command to update the operating system:
# yum update
To install a specific package, such as vsftpd, use the following command:
# yum install vsftpd

 UPGRADING RED HAT ENTERPRISE VIRTUALIZATION MANAGER 3.6



The following procedure outlines the process for upgrading Red Hat Enterprise Virtualization Manager 3.5 to Red Hat Enterprise Virtualization Manager 3.6. This procedure assumes that the system on which the Manager is installed is subscribed to the entitlements for receiving Red Hat Enterprise Virtualization 3.5 packages at the start of the procedure.
IMPORTANT
If the upgrade fails, the engine-setup command will attempt to roll your Red Hat Enterprise Virtualization Manager installation back to its previous state. For this reason, the repositories required by Red Hat Enterprise Virtualization 3.5 must not be removed until after the upgrade is complete as outlined below. If the upgrade fails, detailed instructions display that explain how to restore your installation.
Procedure 3.1. Upgrading to Red Hat Enterprise Virtualization Manager 3.6
  1. Subscribe the system on which the Red Hat Enterprise Virtualization Manager is installed to the required entitlements for receiving Red Hat Enterprise Virtualization Manager 3.6 packages:
    • With RHN Classic:
# rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.6
    • With Subscription Manager:
# subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
  1. Update the rhevm setup packages:
# yum update rhevm\*setup\*
  1. Run the following command and follow the prompts to upgrade the Red Hat Enterprise Virtualization Manager:
# engine-setup
  1. Remove or disable the Red Hat Enterprise Virtualization Manager 3.5 channel to ensure the system does not use any Red Hat Enterprise Virtualization Manager 3.5 packages:
    • With RHN Classic:
# rhn-channel --remove --channel=rhel-x86_64-server-6-rhevm-3.5
    • With Subscription Manager:
# subscription-manager repos --disable=rhel-6-server-rhevm-3.5-rpms
  1. Update the base operating system:
# yum update





Friday, August 19, 2016

How to Use Rsync to Sync New or Changed/Modified Files in Linux

How to Use Rsync to Sync New or Changed/Modified Files in Linux


Sunday, August 14, 2016

Migrating VMWARE Image (OVA) to RHEV 3.5 as a VM


I would like to share with you this secret way of migrating any VM from any hypervisor to RHEV. Red Hat has not mentioned this anywhere on the internet so I would recommend you to do this only on test environments:

1) Extract the OVA image using: tar xvf CFusion-server.ova
2) Convert the extracted VMDK disk file to raw lvm image using: qemu-img convert -f vmdk CFusion-server-disk1.vmdk -O raw CFusion-server-disk1.img
3) SCP the image (.img file) to you NFS exports server (also, Check the VM size)
4) In RHEVM, create a VM with same sized disk (preallocated)
5) Export that VM (to export NFS) and delete the newly created VM
6) Check the export VM image in images folder on NFS export location
7) Put export in maintenance mode and on nfs server, use dd command to write the main exported disk file under images folder
8) Now, activate the export again
9) Create a VM with THIN disk from exported image


You can see that VM is ready for its first run!