Re: Migrate VM from oVirt to oVirt
by Strahil
You will need a storage that will be your 'USB stick' . For example you can attach NFS-based storage domain, migrate the disks of the VM to that storage.
Then power off that VM, set the storage to maintenance and then detach it from first oVirt engine.
Then you attach and activate that NFS storage in your new oVirt engine. After Activation, there will be an 'Import VMs/templates' tab . Click on it and import the VM in a cluster.
Last step is to migrate your VM's disks from that NFS to their permanent storage.
Best Regards,
Strahil NikolovOn Nov 12, 2019 04:39, adrianquintero(a)gmail.com wrote: > > Hello, > What would be the procedure to migrate a VM from oVirt to oVirt? > > Migrate from oVirt 4.2 running on Site A to oVirt 4.3 Site B. > > thanks! > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4OTOXXGYWL2...
4 years, 5 months
restore
by suporte＠logicworks.pt
Hi,
I did a backup of engine like this
# engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name
In a newly installed machine try to restore it:
# yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
# yum update
# yum install ovirt-engine
# engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions
but get this error:
Start of engine-backup with mode 'restore'
scope: all
archive file: file_name
log file: log_file_name
Preparing to restore:
- Unpacking file 'file_name'
Restoring:
- Files
Provisioning PostgreSQL users/databases:
- user 'engine', database 'engine'
Restoring:
FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'.
I'm running ovirt Version:4.3.4.3-1.el7
If I run
# engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --no-restore-permissions
still the same error
Any idea?
Many Thanks
--
Jose Ferradeira
http://www.logicworks.pt
4 years, 5 months
Does ovirt support sshfs?
by TomK
Hi All,
Does ovirt support sshfs for mount locally accessible LUN's instead of NFS?
--
Thx,
TK.
4 years, 5 months
SHE with multipath on multiple iSCSI targets
by Francesco Castellano
Dear sirs,
we're trying to install an SHE oVirt 4.3.6 using an iSCSI SAN that provides
us multiple targets (8) over 4 different portals. Following 5.1 of "RHV
installation using Cockpit" we set up iscsi and multipath ahead with a 90GB
LUN to be used for the engine VM. Unfortunately, even if the node OS sees
correctly the LUN, e.g.:
# multipath -ll
> 36000d31004235a000000000000000018 dm-34 COMPELNT,Compellent Vol
> size=90G features='1 queue_if_no_path' hwhandler='0' wp=rw
> `-+- policy='service-time 0' prio=1 status=active
> |- 16:0:0:3 sdu 65:64 active ready running
> |- 24:0:0:3 sdt 65:48 active ready running
> |- 17:0:0:3 sds 65:32 active ready running
> |- 25:0:0:3 sdv 65:80 active ready running
> |- 15:0:0:3 sdx 65:112 active ready running
> |- 29:0:0:3 sdw 65:96 active ready running
> |- 28:0:0:3 sdy 65:128 active ready running
> |- 20:0:0:3 sdz 65:144 active ready running
> `- 21:0:0:3 sdaa 65:160 active ready running
# lsscsi -ist | grep 36000d31004235a000000000000000018
> [15:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a43,t,0x0
> /dev/sdx 36000d31004235a000000000000000018 96.6GB
> [16:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a43,t,0x0
> /dev/sdu 36000d31004235a000000000000000018 96.6GB
> [17:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a44,t,0x0
> /dev/sds 36000d31004235a000000000000000018 96.6GB
> [20:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235243,t,0x0
> /dev/sdz 36000d31004235a000000000000000018 96.6GB
> [21:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235244,t,0x0
> /dev/sdaa 36000d31004235a000000000000000018 96.6GB
> [24:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a48,t,0x0
> /dev/sdt 36000d31004235a000000000000000018 96.6GB
> [25:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a49,t,0x0
> /dev/sdv 36000d31004235a000000000000000018 96.6GB
> [28:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235248,t,0x0
> /dev/sdy 36000d31004235a000000000000000018 96.6GB
> [29:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235249,t,0x0
> /dev/sdw 36000d31004235a000000000000000018 96.6GB
>
# iscsiadm -m session | grep -E '[a2]4[3489]' | sort -k 3.8
> tcp: [1] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a43
> (non-flash)
> tcp: [2] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a43
> (non-flash)
> tcp: [3] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a44
> (non-flash)
> tcp: [6] 10.201.204.20:3260,0 iqn.2002-03.com.compellent:5000d31004235243
> (non-flash)
> tcp: [7] 10.201.204.20:3260,0 iqn.2002-03.com.compellent:5000d31004235244
> (non-flash)
> tcp: [10] 10.201.205.10:3260,0
> iqn.2002-03.com.compellent:5000d31004235a48 (non-flash)
> tcp: [11] 10.201.205.10:3260,0
> iqn.2002-03.com.compellent:5000d31004235a49 (non-flash)
> tcp: [14] 10.201.205.20:3260,0
> iqn.2002-03.com.compellent:5000d31004235248 (non-flash)
> tcp: [15] 10.201.205.20:3260,0
> iqn.2002-03.com.compellent:5000d31004235249 (non-flash)
>
during the engine deploy neither via cockpit nor with "hosted-engine
--deploy" it was able to see any LUN.
Having a lot of portals (4) and each having 4 targets (two of which being
independents path to the LUN), we chose a portal to discover, it proposed
us 4 targets, and we had to choose a target to log in, but in the end, no
LUN was proposed.
After a few attempts, we found that, if we logged out from any targets (and
clean up the open-iscsi database), after the login in an appropriate
target, the installer proposed us the LUN, and we successfully deployed the
SHE.
But unfortunately, such an installation doesn't track effectively all the 8
paths over 8 different targets, but just the one chosen during the
installation (this is different, for example, with respect to other LUNs
for data domains that we attached afterwards). Thus we miss the HA we aimed
to for the engine data domain.
I said this, because when I ask for /ovirt-engine/api/storagedomains,
whilst a second LUN has 8 children with different targets
below storage_domain/${another data
domain}/storage/volume_group/logical_units/logical_unit/, for the
hosted_storage I just have one.
My questions are:
a) is there a way to add the other targets/paths consistently (even through
the REST interface)?
b) is there another installation, or recovery, procedure to get the engine
data domain in high availability on our iSCSI topology?
Thank you so much for your suggestions, they are really appreciated,
Best regards,
Francesco Castellano
4 years, 5 months
Quick question regarding FQDN
by Christian Reiss
Hey folks,
for production use quality it is recommended to have backend (storage)
and front end seperated. Let' assume:
- 85.0.0.0/24 public IP block
- 10.100.0.0/24 private IPs for DC internal usage
- 10.200.0.0/24 private IPs for storage only LAN
and running, as per recommendation 3 nodes:
- node01:
- fqdn: node01.dc-example.com
- fqdn storage: node02.storage.example.com
- no public IP
- 10.100.0.1 primary IP
- 10.200.0.1 storage IP
- node02:
- fqdn: node02.dc-example.com
- fqdn storage: node02.storage.example.com
- no public IP
- 10.100.0.2 primary IP
- 10.200.0.2 storage IP
- node03:
- fqdn: node03.dc-example.com
- fqdn storage: node02.storage.example.com
- no public IP
- 10.100.0.3 primary IP
- 10.200.0.3 storage IP
The storage network is its own physical network with 10gig that only
connects those three servers. How can I specify which IP to use for
storage, which for frontend traffic?
I am assuming this as the controller and all admins should be able to
reach the nodes via frontend, which is not the storage one.
Okay, I am lost. Whats the real solution here?
Or is "frontend" no-ip, just VM traffic and "backend" is the 10gig
storage "Only" where all the FQDN reside?
Thanks for clarification,
-Chris.
--
Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon
support(a)alpha-labs.net \ / Campaign
X against HTML
WEB alpha-labs.net / \ in eMails
GPG Retrieval https://gpg.christian-reiss.de
GPG ID ABCD43C5, 0x44E29126ABCD43C5
GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5
"It's better to reign in hell than to serve in heaven.",
John Milton, Paradise lost.
4 years, 5 months
I want to configure an web server
by Istiaque Islam
Hi there,
I have installed oVirt on a server and related ISO and Data domains.
I can create Virtual Machines and that machine get access to internet to
download things.
What I want to do now :
1. create an web server using centos and access that webserver from
anywhere with internet connection
2. Then I shall configure a domain name for that webserver hosted in oVirt
Virtual Machine.
My Question :
How to configure the virtual machine in oVirt so that when I enter my
specified domain name/IP it will hit that particular virtual machine?
As it is a virtual machine, it will not get any public IP, so how should i
configure the virtual machine set up so that it can be used as an web
server.
Thanks in advance.
--
With Regards,
*Mohammed Istiaque Islam*
*Contact no *: *+8801745723593*
Email : jisan6347(a)gmail.com
LinkedIn Profile : Profile_Linkedin_Istiaque
<http://www.linkedin.com/in/mohammed-istiaque-islam-59541866>
4 years, 5 months
Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by Yedidyah Bar David
On Mon, Nov 11, 2019 at 12:26 PM Staniforth, Paul
<P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
>
> Thanks,
> I should have been clearer, what I meant was could you install 4.3.5 and restore to that, then run engine-setup --offline?
Of course, this should work.
The only point is that once 4.3.6 is released, it's not that easy to
install 4.3.5, because yum generally tries to install the latest
versions of stuff - and in theory, there might be issues with
installing stuff from 4.3.6 repo with a 4.3.5 engine, so if you want
an exact replicate of a 4.3.5 engine, you have to check all relevant
packages, not just the engine.
>
> Regards,
> Paul S.
> ________________________________
> From: Yedidyah Bar David <didi(a)redhat.com>
> Sent: 11 November 2019 10:19
> To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
> Cc: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com>; users <users(a)ovirt.org>
> Subject: Re: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
>
> On Mon, Nov 11, 2019 at 12:12 PM Staniforth, Paul
> <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
> >
> > I haven't tried it but doesn't engine-setup --offline stop it upgrading minor releases.
>
> It prevents only the packager component.
>
> If you already have 4.3.6 installed, which was the original question,
> then engine-setup will still update the database schema. And if it
> didn't, the 4.3.6 engine might fail working correctly with a 3.4.5.5
> database. In particular:
>
> The documentation for engine-backup always stated that you must run
> engine-setup immediately after restore. But at some points in time,
> and under certain conditions, this was actually optional. You could
> have done a restore, and immediately start the engine, and it would
> have worked. But this isn't the case if your restored db is older than
> the installed engine. Then, you must run engine-setup before starting
> the engine.
>
> Best regards,
>
> >
> > Regards,
> > Paul S.
> > ________________________________
> > From: Yedidyah Bar David <didi(a)redhat.com>
> > Sent: 11 November 2019 07:57
> > To: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com>
> > Cc: users <users(a)ovirt.org>
> > Subject: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
> >
> > On Tue, Oct 29, 2019 at 11:55 AM <wangyu13476969128(a)126.com> wrote:
> > >
> > > The current version of ovirt-engine in production environment is 4.3.5.5.
> > > In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link:
> > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.o...
> > >
> > > I backed it up using the command:
> > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name
> > >
> > > I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes.
> > >
> > > According to the relevant links:
> > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.o...
> > >
> > > The ovirt-engine is installed on the standby machine.
> > >
> > > After I have executed these three commands:
> > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresource...
> > >
> > > 2. yum update
> > >
> > > 3. yum install ovirt-engine
> > >
> > > I found that the ovirt-engine version of the standby machine is 4.3.6
> > >
> > > So my question is:
> > >
> > > 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine:
> > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name
> > >
> > > Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)?
> >
> > In principle it should be ok. After you restore with above command,
> > you should run 'engine-setup', and this will update your restored
> > database schema to 4.3.6.
> > This is not routinely tested explicitly, though, but I expect that
> > people often do this, perhaps even unknowingly, when they restore from
> > a backup taken with a somewhat-old version.
> >
> > >
> > > 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5?
> > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresource...
> > > 2. yum update
> > > 3. yum install ovirt-engine
> >
> > In theory you can change last one to 'yum install
> > ovirt-engine-4.3.5.5'. I didn't try that, and you are quite likely to
> > run into complex dependencies you'll have to satisfy by yourself.
> >
> > I think the best solution for you, if you care about active and
> > standby to be identical, is to upgrade your active one as well, and
> > keep them same version going forward.
> >
> > I'd also like to note that maintaining a standby engine and using it
> > the way you intend to, is not in the scope of oVirt. People do similar
> > things, but have to manually work around this and be careful. One very
> > important issue is that if for any reason you allow both of them to be
> > up at the same time, and manage the same hosts, they will not know
> > about each other, and you'll see lots of confusion and errors.
> >
> > You might also want to check:
> >
> > 1. Hosted-engine setup with more than one host as hosted-engine host.
> > There, you only have a single engine vm, but it can run on any of your
> > hosts. You still have a single VM disk/image, and if that's corrupted,
> > you have no HA and have to somehow reinstall/restore/etc.
> >
> > 2. https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> >
> > Best regards,
> > --
> > Didi
> > _______________________________________________
> > Users mailing list -- users(a)ovirt.org
> > To unsubscribe send an email to users-leave(a)ovirt.org
> > Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> > oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> > List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...
> > To view the terms under which this email is distributed, please go to:-
> > http://leedsbeckett.ac.uk/disclaimer/email/
>
>
>
> --
> Didi
>
> To view the terms under which this email is distributed, please go to:-
> http://leedsbeckett.ac.uk/disclaimer/email/
--
Didi
4 years, 5 months
