upgrade from RHEV 3.4 to RHV 4.1

Latest response

hi,

we are planning to upgrade from RHEV 3.4 to RHV 4.1

in current system, we got RHEV-Manager 3.4 & two hypervisors (RHEL 6.6), and we got many virtual machines running on this cluster

what will be the best way to upgrade to RHV 4.1 ? we want to achieve minimum downtime; all existing virtual machines shall be able to run on the new RHV 4.1 platform

YZ
Log in to join the conversation

Responses

Siem Korteweg's picture Guru 1450 points
5 February 2018 8:25 AM

There is not much information in https://access.redhat.com/articles/3198302.

Please refer to: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/upgrade_guide/chap-upgrading_to_red_hat_virtualization_4.0

YZ Community Member 40 points
5 February 2018 10:25 AM

@Siem,

i knew that there is no upgrade path from 3.4 to 4.*, have to reach 3.6 level first, that's very tedious & could be troublesome

instead of upgrading, actually i am planning to just take one hypervisor out from the existing RHEV 3.4 system, install RHEL 7 on this hypervisor & then install RHV 4.1 self-hosted engine on this same hypervisor, then detach data storage domains from the old RHEV 3.4 environment, then just import the existing storage domain into the new RHV 4.1 Manager

I personally think this would work, but needs to test it out

Siem Korteweg's picture Guru 1450 points
5 February 2018 10:31 AM

The contents of the 3.6 storage domain are compatible with 4.1. You cannot import directly a 3.[45] storage domain into 4.1.

YZ Community Member 40 points
5 February 2018 10:49 AM

yes, i think you are right, i forgot that one, according to RHV-M compatibility matrix, RHV 4.1 is compatible with "Compatibility levels" 4.1 & 4.0 & 3.6, i just checked, 3.4 is not listed there

so I plan to just upgrade 3.4 to 3.6 first.. then detach all data storage domains from 3.6 environment, then attach them to 4.1 environment; hopefully it will work smoothly

YZ Community Member 40 points
6 February 2018 8:57 AM

did a quick test in RHEV-M 3.4, detaching a non-empty data storage domain is not allowed!

while in RHV 4.1 Administration guide, "chapter 8 Storage" says: ---clip--- The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disk images, and templates can then be uploaded from the imported storage domain to the attached data center. See Section 8.6, “Importing Existing Storage Domains” for information on importing storage domains. ---clap---

i thought data storage domain could be detached & reattached to another RHV environment?

Siem Korteweg's picture Guru 1450 points
6 February 2018 12:52 PM

When you compare the Administrators Guides for several versions, you will notice that the supported actions on storage domains change. In the 3.5/3.6 releases you will see disks named OVF_STORE that contain the metadata to detach/attach storage domains.

JB Red Hat Community Member 80 points
6 February 2018 1:17 PM

4.2-beta administration guide mentions that importing an existing SD can be done with a SD which is minimum from 3.5 env, see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html/administration_guide/sect-Importing_Existing_Storage_Domains

YZ Community Member 40 points
6 February 2018 1:46 PM

@Jiri Belka,

so you mean, once i upgrade from 3.4 to 3.5, then in 3.5 environment, i will be able to detach a non-empty SD ??

as mentioned, it's NOT allowed to detach a non-empty SD in 3.4 environment

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.