Bug 1441664 - [Docs][RFE][Upgrade] Document migration from RHEV-H 3 (7.3) to RHVH 4 (7.3) with a local storage domain
Summary: [Docs][RFE][Upgrade] Document migration from RHEV-H 3 (7.3) to RHVH 4 (7.3) w...
Keywords:
Status: CLOSED DUPLICATE of bug 1421437
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On: 1320556
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-12 12:23 UTC by Emma Heftman
Modified: 2019-05-07 13:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-24 07:41:34 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Emma Heftman 2017-04-12 12:23:31 UTC
There is a requirement to document this procedure. See discussion in 1320556. This bug differs from 1415666 as this is for local storage.

Comment 1 Emma Heftman 2017-04-23 10:56:45 UTC
From 1320556
My suggestion is use the comment#4 to create the documentation and the
comment#6 is about showing how the kickstart file was created but it's not
needed as you already documented here:

http://file.tlv.redhat.com/~eheftman/bz1369874/html-single/#Automating_RHVH_Deployment


"""

Users that contain local storage environment are able to migrate from RHEV
Hypervisor 3.6 to RHV Hypervisor 4.

Tip: In case advanced installation (kickstart) is used to redeploy the machine
with RHV 4, keep in mind to not overwrite your data, example:

  To autoinstall and avoid erase any file in /dev/sdb, use the following in the
kickstart:

    "clearpart --all --drives=sda"


* After RHV Hypervisor is installed (*Keep in mind to leave your local storage
data intact)

Create directory /data to recover your previous environment
#2 mkdir /data

Mount the previous local storage in /data
#3 mount /dev/sdX1 /data

Set permissions to /data
#4 chown -R 36:36 /data
   chmod -R 0755 /data


To automount the partition in /data (in case the server requires a reboot), use
the following example:

Example:
   # blkid | grep -i sdX1
   /dev/sdX1: UUID="a81a6879-3764-48d0-8b21-2898c318ef7c" TYPE="ext4"

   # vi /etc/fstab
   UUID="a81a6879-3764-48d0-8b21-2898c318ef7c" /data     ext4          defaults
    0       0


Importing the local storage into RHVM:

#5 Create DataCenter for Local Storage
#6 Create Cluster for Local Storage
#7 On Storage Tab, use a different dir than /data to create your initial local
storage for later import your previous environment, example: /localfs

   On RHV Hypervisor:
     mkdir -p /localfs
     chown 36:36 /localfs
     chmod -R 0755 /localfs

   On RHV-M add the local storage in the Storage Tab:
   Name: localfs
   Path: /localfs

#9 After localfs storage is UP, let's import the existing local storage:

   Storage tab, Import Domain

   Name: Data
   Storage type: Local on Host
   Path: /data


Confirm the following:
"""
  Storage Domain(s) are already attached to a Data Center. Approving this
operation might cause data corruption if both Data Centers are active.
"""

To active your data storage:
  In the datacenter tab, go to storage sub-tab and active the data storage
domain just imported (Data and local-fs should be UP)

To import the virtual machines:
  In the Storage Tab, select the data (imported domain) and go to sub-tab 'Vm
Import' and select the vm and click import
 (It should import the vm and disk)

Finally, after virtual machines and disks were imported and tested, in the
datacenter tab you can put the localfs storage in maintenance (as it won't be
used)

"""

Comment 2 Yaniv Lavi 2017-04-24 07:41:34 UTC

*** This bug has been marked as a duplicate of bug 1421437 ***


Note You need to log in before you can comment on or make changes to this bug.