Re: [ovirt-users] oVirt maintence "best practices"

[Sandro Bonazzola]

Il 11/Feb/2017 07:12, "Jim Kusznir"  ha scritto:

hello:

Now that I've had my ovirt cluster running for about a month and a half, I
am realizing I don't necessarily know the best practices for keeping it up.

I've been seeing the notices in the ovirt hosts screen showing that there
are updates waiting for the hosts, and I'll put them in maintence mode one
at a time and apply the updates.

What about the engine itself?  Is it recommended/safe to log into the
engine and just run "yum update"?  Is there other procedures I should be
doing?


I suggest to read oVirt Administration Guide on oVirt website. It's from
4.0 but still relevant. It details upgrade flows.




My oVirt cluster is a 3 node cluster with gluster, running on each node.

Thanks!
--Jim

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Hosted Engine migration problems

[Jim Kusznir]

Hi again:

I thought I had fixed the hosted engine migration that was preventing me
from updating the host the engine was running on.  Today it let me migrate
it from ovirt1 to ovirt2, and perform needed updates on ovirt1.  When I
tried to migrate it back to ovirt1 after the updates, I got errors that it
failed migration.  I tried an auto-migrate, and it claimed that the other
two nodes (including the node it was running on) do not meet minimum
requrements, specifically that they are not HA nodesBut I did
explicitly set them up as HA nodes.

Here's the engine.log output from the command:

2017-02-11 06:12:03,078 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-41)
[252e1f97] Candidate host 'engine1'
('1e182fb9-8057-42ed-abd6-bc5bc343ccc6') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'HA' (correlation id: null)
2017-02-11 06:12:03,078 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-41)
[252e1f97] Candidate host 'engine3'
('bac8ace2-cf7e-48ea-9113-b82343cd87f7') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'HA' (correlation id: null)
2017-02-11 06:12:03,081 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-41)
[252e1f97] Candidate host 'engine2'
('76c075fc-1dfb-479d-98ef-57575ec11787') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration' (correlation id: null)
2017-02-11 06:12:03,081 WARN  [org.ovirt.engine.core.bll.MigrateVmCommand]
(default task-41) [252e1f97] Validation of action 'MigrateVm' failed for
user admin@internal-authz. Reasons:
VAR__ACTION__MIGRATE,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName
engine1,$filterName
HA,VAR__DETAIL__NOT_HE_HOST,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName
engine3,$filterName
HA,VAR__DETAIL__NOT_HE_HOST,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName
engine2,$filterName
Migration,VAR__DETAIL__SAME_HOST,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL

I'm a bit confused by thisI followed the ovirt+gluster howto referenced
from the contributed documentation page.

--Jim
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt maintence "best practices"

[Jim Kusznir]

hello:

Now that I've had my ovirt cluster running for about a month and a half, I
am realizing I don't necessarily know the best practices for keeping it up.

I've been seeing the notices in the ovirt hosts screen showing that there
are updates waiting for the hosts, and I'll put them in maintence mode one
at a time and apply the updates.

What about the engine itself?  Is it recommended/safe to log into the
engine and just run "yum update"?  Is there other procedures I should be
doing?

My oVirt cluster is a 3 node cluster with gluster, running on each node.

Thanks!
--Jim
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Optimizations for VoIP VM

[Jim Kusznir]

Sorry for the delayed response, I finally found where gmail hid this
response... :(

So the application is FusionPBX, a FreeSwitch-based VoIP system, running on
a very unloaded (1% cpu load, 2-4 VMs running) system.  I've been
experiencing intermittent call breakup, for which external support
immediately blamed on the virtualization solution claiming that "You can't
virtualize VoIP systems without causing voice breakup and other call
quality issues".  Previously, I had attempted to run FreePBX
(asterisk-based) on a Hyper-V system, and I did find that to be the case;
moving over to very weak, but dedicated hardware, fixed the problem
immediately.

Since I sent this message, I did extensive testing with my system, and it
appears that the breakup is in fact network related.  I've been able to do
phone to phone calls on the local network for extended durations without
issue, and even have phone to phone calls on external networks without
issue.  However, calls going to my VoIP provider do break up, so it appears
to be the network route to my provider.

So, oVirt does not appear to be to blame (which I didn't think so, but was
hoping for some "expert information" to support this...It appears that I
got that and more with my tests).

Thank you again for your work on such a great product!

--Jim

On Wed, Jan 4, 2017 at 10:08 AM, Chris Adams  wrote:

> Once upon a time, Yaniv Dary  said:
> > Can you please describe the application network requirements?
> > Does it relay on low latency? Pass-through or SR-IOV could help with
> > reducing that.
>
> For VoIP, latency can be an issue, but the amount of latency from adding
> VM networking overhead isn't a big deal (because other network latency
> will have a larger impact).  10ms isn't really a problem for VoIP for
> example.
>
> The bigger network concern for VoIP is jitter; for that, the only
> solution is to not over-provision hardware CPUs or total network
> bandwidth.
>
> --
> Chris Adams 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Storage domain experienced a high latency

[Nir Soffer]

On Fri, Feb 10, 2017 at 9:24 PM, Grundmann, Christian <
christian.grundm...@fabasoft.com> wrote:

> Attached
>

I don't see anything unusual.

Having one path, your system is very sensitive to
errors on the single path.

The default ovirt configuration assume that you have several
paths for each device, and is optimized for fast failover when
a path has an error.

This optimization makes your system more fragile when you
have only one path.

I would use this setting:

no_path_retry 4

This will do 4 retries when all paths are faulty before failing the io.
If you have short outage for some reason, this may hide the issue
on the host.

If you change multipath.conf, you should mark it as private, so
vdsm will not touch this file on upgrades. To mark the file as
private the second line of the file must be:

# VDSM PRIVATE

To check that your file is considered private, you can run:

# vdsm-tool is-configured
Manual override for multipath.conf detected - preserving current
configuration

You should see the message about Manual override.

The real question is why the path failed - did you have anything
in the server logs at that time? did you have issues on other hosts
in the same time?

Nir


>
>
> Thx Christian
>
>
>
> *Von:* Nir Soffer [mailto:nsof...@redhat.com]
> *Gesendet:* Freitag, 10. Februar 2017 17:43
>
> *An:* Grundmann, Christian 
> *Cc:* users@ovirt.org
> *Betreff:* Re: [ovirt-users] Storage domain experienced a high latency
>
>
>
> On Thu, Feb 9, 2017 at 10:03 AM, Grundmann, Christian <
> christian.grundm...@fabasoft.com> wrote:
>
> Hi,
>
> @ Can also be low level issue in kernel, hba, switch, server.
> I have the old storage on the same cable so I don’t think its hba or
> switch related
> On the same Switch I have a few ESXi Server with same storage setup which
> are working without problems.
>
> @multipath
> I use stock ng-node multipath configuration
>
> # VDSM REVISION 1.3
>
> defaults {
> polling_interval5
> no_path_retry   fail
> user_friendly_names no
> flush_on_last_del   yes
> fast_io_fail_tmo5
> dev_loss_tmo30
> max_fds 4096
> }
>
> # Remove devices entries when overrides section is available.
> devices {
> device {
> # These settings overrides built-in devices settings. It does not
> apply
> # to devices without built-in settings (these use the settings in
> the
> # "defaults" section), or to devices defined in the "devices"
> section.
> # Note: This is not available yet on Fedora 21. For more info see
> # https://bugzilla.redhat.com/1253799
> all_devsyes
> no_path_retry   fail
> }
> }
>
> # Enable when this section is available on all supported platforms.
> # Options defined here override device specific options embedded into
> # multipathd.
> #
> # overrides {
> #  no_path_retry   fail
> # }
>
>
> multipath -r v3
> has no output
>
>
>
> My mistake, the correct command is:
>
>
>
> multipath -r -v3
>
>
>
> It creates tons of output, so better redirect to file and attach the file:
>
>
>
> multipath -r -v3 > multiapth-r-v3.out
>
>
>
>
>
> Thx Christian
>
>
> Von: Nir Soffer [mailto:nsof...@redhat.com]
> Gesendet: Mittwoch, 08. Februar 2017 20:44
> An: Grundmann, Christian 
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Storage domain experienced a high latency
>
>
> On Wed, Feb 8, 2017 at 6:11 PM, Grundmann, Christian  christian.grundm...@fabasoft.com> wrote:
> Hi,
> got a new FC Storage (EMC Unity 300F) which is seen by my Hosts additional
> to my old Storage for Migration.
> New Storage has only on PATH until Migration is done.
> I already have a few VMs running on the new Storage without Problem.
> But after starting some VMs (don’t really no whats the difference to
> working ones), the Path for new Storage fails.
>
> Engine tells me: Storage Domain  experienced a high latency
> of 22.4875 seconds from host 
>
> Where can I start looking?
>
> In /var/log/messages I found:
>
> Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760:
> sdd - emc_clariion_checker: Active path is healthy.
> Feb  8 09:03:53 ovirtnode01 multipathd: 8:48: reinstated
> Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760:
> remaining active paths: 1
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 8
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 5833475
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 5833475
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967168
> Feb  8 09:03:53 ovirtnode01 kernel: Buffer I/O error on dev dm-207,
> logical block 97, async page read
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967168
> Feb  8 09:03:53 ovirtn

Re: [ovirt-users] Error attempting to upload an ISO image

[Yaniv Kaul]

On Feb 10, 2017 9:07 PM, "Berger, Sandy"  wrote:

I originally installed a hosted engine on oVirt 4.0.x. Since then I’ve
updated to 4.1. engine-upgrade-check shows no updates available:



[root@waovccm1 ~]# engine-upgrade-check

VERB: queue package ovirt-engine-setup for update

VERB: Building transaction

VERB: Empty transaction

VERB: Transaction Summary:

No upgrade



However, “yum update” shows several updates available (see below) including
python-ovirt-engine-sdk4 x86_64 4.1.0-1.el7.centos. The installed version
of that RPM is currently 4.0.4-1.el7.centos.x86_64. Is it safe to run a yum
update on the hosted engine? Why wouldn’t engine-upgrade-check show a
necessary update like that?


Should be OK to run.
I'm not sure but I think the ISO uploader should depend on a newer
pyhton-ovirt-sdk.
Y.



Thanks much for your assistance!



[root@waovccm1 ~]# yum update

Loaded plugins: fastestmirror, versionlock

Loading mirror speeds from cached hostfile

* base: repos.forethought.net

* extras: centos.mbni.med.umich.edu

* ovirt-4.1: mirrors.ibiblio.org

* ovirt-4.1-epel: mirror.steadfast.net

* updates: mirror.atlanticmetro.net

Resolving Dependencies

--> Running transaction check

---> Package NetworkManager.x86_64 1:1.4.0-13.el7_3 will be updated

---> Package NetworkManager.x86_64 1:1.4.0-14.el7_3 will be an update

---> Package NetworkManager-libnm.x86_64 1:1.4.0-13.el7_3 will be updated

---> Package NetworkManager-libnm.x86_64 1:1.4.0-14.el7_3 will be an update

---> Package NetworkManager-team.x86_64 1:1.4.0-13.el7_3 will be updated

---> Package NetworkManager-team.x86_64 1:1.4.0-14.el7_3 will be an update

---> Package NetworkManager-tui.x86_64 1:1.4.0-13.el7_3 will be updated

---> Package NetworkManager-tui.x86_64 1:1.4.0-14.el7_3 will be an update

---> Package NetworkManager-wifi.x86_64 1:1.4.0-13.el7_3 will be updated

---> Package NetworkManager-wifi.x86_64 1:1.4.0-14.el7_3 will be an update

---> Package antlr-tool.noarch 0:2.7.7-30.el7 will be updated

---> Package antlr-tool.noarch 0:2.7.7-35.el7 will be an update

---> Package bind-libs.x86_64 32:9.9.4-38.el7_3 will be updated

---> Package bind-libs.x86_64 32:9.9.4-38.el7_3.1 will be an update

---> Package bind-libs-lite.x86_64 32:9.9.4-38.el7_3 will be updated

---> Package bind-libs-lite.x86_64 32:9.9.4-38.el7_3.1 will be an update

---> Package bind-license.noarch 32:9.9.4-38.el7_3 will be updated

---> Package bind-license.noarch 32:9.9.4-38.el7_3.1 will be an update

---> Package bind-utils.x86_64 32:9.9.4-38.el7_3 will be updated

---> Package bind-utils.x86_64 32:9.9.4-38.el7_3.1 will be an update

---> Package device-mapper.x86_64 7:1.02.135-1.el7_3.1 will be updated

---> Package device-mapper.x86_64 7:1.02.135-1.el7_3.2 will be an update

---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7_3.1 will be updated

---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7_3.2 will be an
update

---> Package firewalld.noarch 0:0.4.3.2-8.el7 will be updated

---> Package firewalld.noarch 0:0.4.3.2-8.1.el7_3 will be an update

---> Package firewalld-filesystem.noarch 0:0.4.3.2-8.el7 will be updated

---> Package firewalld-filesystem.noarch 0:0.4.3.2-8.1.el7_3 will be an
update

---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.111-2.b15.el7_3 will be
updated

---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.121-0.b13.el7_3 will be an
update

---> Package java-1.8.0-openjdk-devel.x86_64 1:1.8.0.111-2.b15.el7_3 will
be updated

---> Package java-1.8.0-openjdk-devel.x86_64 1:1.8.0.121-0.b13.el7_3 will
be an update

---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.111-2.b15.el7_3
will be updated

---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.el7_3
will be an update

---> Package kernel.x86_64 0:3.10.0-514.6.1.el7 will be installed

---> Package kernel-tools.x86_64 0:3.10.0-514.2.2.el7 will be updated

---> Package kernel-tools.x86_64 0:3.10.0-514.6.1.el7 will be an update

---> Package kernel-tools-libs.x86_64 0:3.10.0-514.2.2.el7 will be updated

---> Package kernel-tools-libs.x86_64 0:3.10.0-514.6.1.el7 will be an update

---> Package kpartx.x86_64 0:0.4.9-99.el7 will be updated

---> Package kpartx.x86_64 0:0.4.9-99.el7_3.1 will be an update

---> Package libnl3.x86_64 0:3.2.28-2.el7 will be updated

---> Package libnl3.x86_64 0:3.2.28-3.el7_3 will be an update

---> Package libnl3-cli.x86_64 0:3.2.28-2.el7 will be updated

---> Package libnl3-cli.x86_64 0:3.2.28-3.el7_3 will be an update

---> Package libpciaccess.x86_64 0:0.13.4-2.el7 will be updated

---> Package libpciaccess.x86_64 0:0.13.4-3.el7_3 will be an update

---> Package libsemanage.x86_64 0:2.5-4.el7 will be updated

---> Package libsemanage.x86_64 0:2.5-5.1.el7_3 will be an update

---> Package libsemanage-python.x86_64 0:2.5-4.el7 will be updated

---> Package libsemanage-python.x86_64 0:2.5-5.1.el7_3 will be an update

---> Package libtiff.x86_64 0:4.0.3-25.el7_2 will be updated

---> Package libtiff.x86_64 0:4.0.3-27.el7_3 will be an update

Re: [ovirt-users] Error attempting to upload an ISO image

[Berger, Sandy]

I originally installed a hosted engine on oVirt 4.0.x. Since then I’ve updated 
to 4.1. engine-upgrade-check shows no updates available:

[root@waovccm1 ~]# engine-upgrade-check
VERB: queue package ovirt-engine-setup for update
VERB: Building transaction
VERB: Empty transaction
VERB: Transaction Summary:
No upgrade

However, “yum update” shows several updates available (see below) including 
python-ovirt-engine-sdk4 x86_64 4.1.0-1.el7.centos. The installed version of 
that RPM is currently 4.0.4-1.el7.centos.x86_64. Is it safe to run a yum update 
on the hosted engine? Why wouldn’t engine-upgrade-check show a necessary update 
like that?

Thanks much for your assistance!

[root@waovccm1 ~]# yum update
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
* base: repos.forethought.net
* extras: centos.mbni.med.umich.edu
* ovirt-4.1: mirrors.ibiblio.org
* ovirt-4.1-epel: mirror.steadfast.net
* updates: mirror.atlanticmetro.net
Resolving Dependencies
--> Running transaction check
---> Package NetworkManager.x86_64 1:1.4.0-13.el7_3 will be updated
---> Package NetworkManager.x86_64 1:1.4.0-14.el7_3 will be an update
---> Package NetworkManager-libnm.x86_64 1:1.4.0-13.el7_3 will be updated
---> Package NetworkManager-libnm.x86_64 1:1.4.0-14.el7_3 will be an update
---> Package NetworkManager-team.x86_64 1:1.4.0-13.el7_3 will be updated
---> Package NetworkManager-team.x86_64 1:1.4.0-14.el7_3 will be an update
---> Package NetworkManager-tui.x86_64 1:1.4.0-13.el7_3 will be updated
---> Package NetworkManager-tui.x86_64 1:1.4.0-14.el7_3 will be an update
---> Package NetworkManager-wifi.x86_64 1:1.4.0-13.el7_3 will be updated
---> Package NetworkManager-wifi.x86_64 1:1.4.0-14.el7_3 will be an update
---> Package antlr-tool.noarch 0:2.7.7-30.el7 will be updated
---> Package antlr-tool.noarch 0:2.7.7-35.el7 will be an update
---> Package bind-libs.x86_64 32:9.9.4-38.el7_3 will be updated
---> Package bind-libs.x86_64 32:9.9.4-38.el7_3.1 will be an update
---> Package bind-libs-lite.x86_64 32:9.9.4-38.el7_3 will be updated
---> Package bind-libs-lite.x86_64 32:9.9.4-38.el7_3.1 will be an update
---> Package bind-license.noarch 32:9.9.4-38.el7_3 will be updated
---> Package bind-license.noarch 32:9.9.4-38.el7_3.1 will be an update
---> Package bind-utils.x86_64 32:9.9.4-38.el7_3 will be updated
---> Package bind-utils.x86_64 32:9.9.4-38.el7_3.1 will be an update
---> Package device-mapper.x86_64 7:1.02.135-1.el7_3.1 will be updated
---> Package device-mapper.x86_64 7:1.02.135-1.el7_3.2 will be an update
---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7_3.1 will be updated
---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7_3.2 will be an update
---> Package firewalld.noarch 0:0.4.3.2-8.el7 will be updated
---> Package firewalld.noarch 0:0.4.3.2-8.1.el7_3 will be an update
---> Package firewalld-filesystem.noarch 0:0.4.3.2-8.el7 will be updated
---> Package firewalld-filesystem.noarch 0:0.4.3.2-8.1.el7_3 will be an update
---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.111-2.b15.el7_3 will be updated
---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.121-0.b13.el7_3 will be an update
---> Package java-1.8.0-openjdk-devel.x86_64 1:1.8.0.111-2.b15.el7_3 will be 
updated
---> Package java-1.8.0-openjdk-devel.x86_64 1:1.8.0.121-0.b13.el7_3 will be an 
update
---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.111-2.b15.el7_3 will be 
updated
---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.el7_3 will be 
an update
---> Package kernel.x86_64 0:3.10.0-514.6.1.el7 will be installed
---> Package kernel-tools.x86_64 0:3.10.0-514.2.2.el7 will be updated
---> Package kernel-tools.x86_64 0:3.10.0-514.6.1.el7 will be an update
---> Package kernel-tools-libs.x86_64 0:3.10.0-514.2.2.el7 will be updated
---> Package kernel-tools-libs.x86_64 0:3.10.0-514.6.1.el7 will be an update
---> Package kpartx.x86_64 0:0.4.9-99.el7 will be updated
---> Package kpartx.x86_64 0:0.4.9-99.el7_3.1 will be an update
---> Package libnl3.x86_64 0:3.2.28-2.el7 will be updated
---> Package libnl3.x86_64 0:3.2.28-3.el7_3 will be an update
---> Package libnl3-cli.x86_64 0:3.2.28-2.el7 will be updated
---> Package libnl3-cli.x86_64 0:3.2.28-3.el7_3 will be an update
---> Package libpciaccess.x86_64 0:0.13.4-2.el7 will be updated
---> Package libpciaccess.x86_64 0:0.13.4-3.el7_3 will be an update
---> Package libsemanage.x86_64 0:2.5-4.el7 will be updated
---> Package libsemanage.x86_64 0:2.5-5.1.el7_3 will be an update
---> Package libsemanage-python.x86_64 0:2.5-4.el7 will be updated
---> Package libsemanage-python.x86_64 0:2.5-5.1.el7_3 will be an update
---> Package libtiff.x86_64 0:4.0.3-25.el7_2 will be updated
---> Package libtiff.x86_64 0:4.0.3-27.el7_3 will be an update
---> Package ntp.x86_64 0:4.2.6p5-25.el7.centos will be updated
---> Package ntp.x86_64 0:4.2.6p5-25.el7.centos.1 will be an update
---> Package ntpdate.x86_64 0:4.2.6p5-25.el7.centos will be updated
---> Package ntpdate.x86_64

Re: [ovirt-users] Manually starting VMs via vdsClient (HE offline)

[Yaniv Kaul]

On Feb 10, 2017 3:21 PM, "Nathanaël Blanchet"  wrote:



Le 09/02/2017 à 19:48, Yaniv Kaul a écrit :



On Thu, Feb 9, 2017 at 6:00 PM, Doug Ingham  wrote:

>
>
> On 9 February 2017 at 12:03, Dan Yasny  wrote:
>
>>
>> On Thu, Feb 9, 2017 at 9:55 AM, Doug Ingham  wrote:
>>
>>> Hi Dan,
>>>
>>> On 8 February 2017 at 18:26, Dan Yasny  wrote:


 But seriously, above all, I'd recommend you backup the engine (it comes
 with a utility) often and well. I do it via cron every hour in production,
 keeping a rotation of hourly and daily backups, just in case. It doesn't
 take much space or resources, but it's more than just best practice - that
 database is the summary of the entire setup.


>>> If you don't mind, may I ask what process you use for backing up your
>>> engine? If you use HE, do you keep one server dedicated to just that VM?
>>> I've not had that particular issue in the restore process yet, however I
>>> read that it's recommended the HE host is free of virtual load before the
>>> backup takes place. And as they need to be done frequently, I'm reading
>>> that as a dedicated host...
>>>
>>>
>> If you use a dedicated host, you might as well abandon self hosted. HE is
>> nice for small setups with the HA built in for extra fun, but once you
>> scale, it might not be able to cope and you'll need real hardware. You're
>> running a heavy-ish java engine plus two databases after all.
>>
> I'd be interested to know what type of scale needs a real hardware for
engine, rather 100 vms or 1000 vms? it may be about the hosts number?


It depends on many factors. Just saw someone who is running the engine as a
VM on a hefty hardware, and his setup had 50 hosts and 2500 VMs. I don't
know all the details and specifically what I'd be interested to know is the
underlying storage performance and how it's connected.
In any case, as you scale up the system you will need more vCPUs and
memory.

Lastly, in 4.1 we've made various improvements to the engine and its
database usage, so I expect somewhat improved performance and scale.
Y.



>> So as I said, all I do is add the engine-backup command to cron on the
>> engine, and then my backup server comes in and pulls out the files via scp,
>> also through cron. Nothing fancy really, but it lets me sleep at night
>>
>
> This particular project has 10 new maxed out servers to back it, and I
> don't see it outgrowing that for at least a year or so. It's hardly a full
> DC.
> I presume the DB will become the heaviest part of the load, and I'm
> already planning a separate high I/O environment for dedicated HA DB hosts.
>
> See the top section of this page:
> http://www.ovirt.org/documentation/self-hosted/chap-Backing_
> up_and_Restoring_an_EL-Based_Self-Hosted_Environment
>
> It seems that I'll always have to keep at least one host free to be able
> to avoid restore problems. If not, and I were to keep hourly backups, then
> migrating VMs off the host every hour would just be a pain.
>

I don't see the point in an hourly backup. Of what? The DB? The VM? What
storage will it be based on?
I suggest revising the strategy.


>
>
> --
> Doug
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


___
Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users


-- 
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14blanc...@abes.fr


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error attempting to upload an ISO image

[Yaniv Kaul]

On Feb 10, 2017 6:47 PM, "Berger, Sandy"  wrote:

After the 4.1 upgrade, I’m getting the following results attempting to
upload an ISO image:



[root@waovccm1 ~]# ovirt-iso-uploader --iso-domain=waISOLibrary upload
slb.iso

Please provide the REST API password for the admin@internal oVirt Engine
user (CTRL+D to abort):

ERROR: v4 is not a valid StorageFormat


Can you ensure the 4.1 python SDK is installed?
I think it is 4.1.24 and above that has it.
Y.

INFO: Use the -h option to see usage.



I was able to manually copy the file to the correct directory on the NFS
server but can’t get the utility to work properly.



*Sandy Berger *

*IT - EUX*



Quad/Graphics

*Performance* through *Innovation*



Sussex, Wisconsin

414.566.2123 <(414)%20566-2123> phone

414.566.4010 <(414)%20566-4010>/2123 pager/PIN



sandy.ber...@qg.com

www.QG.com 


Follow Us: Facebook  | Twitter
 | LinkedIn  | YouTube


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] libvirtError: Cannot get interface MTU

[Tyson Landon]

I created a new cluster using the legacy switch type and added two fresh hosts. 
Then I shut off a VM selected the new cluster in its settings and booted it. It 
will now live migrate between hosts on the new cluster. Thanks for the help.
>>> Edward Haas  02/09/17 7:26 AM >>>


On Thu, Feb 9, 2017 at 4:07 PM, Tyson Landon  wrote:


My engine version is 4.0.5.5-1.el7.centos. The first host is using 
vdsm-4.18.21-1.el7.centos and the second is using vdsm-4.18.15.3-1.el7.centos. 
I am trying to migrate guests off host2 to run updates. The Switch type is OVS 
so are there any pitfalls related to changing that to legacy?

I would recommend starting from scratch, do not attempt to move from OVS to 
legacy on that version. 



>>> Edward Haas  02/09/17 12:55 AM >>>
Please share the versions you are using (VDSM and Engine).
Have you configured at the cluster level the switch type as OVS? If so, note it 
is experimental
and we have not supported migration over OVS in early 4.1 versions.

On Wed, Feb 8, 2017 at 10:27 PM, Tyson Landon  wrote:


I am new to Ovirt and have a test cluster running with 2 hosts. I have errors 
when live migrating that started after I installed a new NIC in one host. Live 
migrate was working fine before the changes. The vdsm log shows the errors 
below depending on if i am migrating from host1 or host2. Running ovs-vsctl 
list-br shows that the bridge exists. Ip a shows the interface is down. I do 
not know what a vdsm bridge is for or if the server just needs to restart a 
service to get things in order again. Have any of you seen this error before 
and were able to fix it?

HOST 1
libvirtError: Cannot get interface MTU on 'vdsmbr_TK4cSEjh': No such device

HOST 2
libvirtError: Cannot get interface MTU on 'vdsmbr_vqqOTlrR': No such device


HOST 1
ovs-vsctl list-br
vdsmbr_3fDBsCCF
vdsmbr_TK4cSEjh
vdsmbr_VWhs9soF

HOST2
ovs-vsctl list-br
vdsmbr_YBtJDFGg
vdsmbr_qf3gXZdq
vdsmbr_vqqOTlrR

Thanks
Tyson

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] FreeIPA with ovirt 4.1

[Slava Bendersky]

Hello Ondra, 
I tried increase logging and command fail 

"outcome" => "failed", 
"failure-description" => "WFLYCTL0216: Management resource '[ 
(\"subsystem\" => \"logging\"), 
(\"logger\" => \"org.ovirt.engine.core.sso\") 
]' not found", 
"rolled-back" => true 
} 


Slava, 


From: "Ondra Machacek"  
To: "Slava Bendersky"  
Cc: "users"  
Sent: Thursday, February 9, 2017 2:31:16 PM 
Subject: Re: [ovirt-users] FreeIPA with ovirt 4.1 

Can you please enable DEBUG log of the SSO package and try login and 
then share the logs, please? 

You can enable the debug log as following (use admin@internal password): 

/usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh 
--controller=127.0.0.1:8706 --connect --user=admin@internal 
"/subsystem=logging/logger=org.ovirt.engine.core.sso:add" && 
/usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh 
--controller=127.0.0.1:8706 --connect --user=admin@internal 
"/subsystem=logging/logger=org.ovirt.engine.core.sso:write-attribute(name=level,value=DEBUG)"
 

After tests you can disable it later as follows: 

$ /usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh 
--controller=127.0.0.1:8706 --connect --user=admin@internal 
"/subsystem=logging/logger=org.ovirt.engine.core.sso:remove" 

On Thu, Feb 9, 2017 at 3:08 PM, Slava Bendersky  wrote: 
> Hello Everyone, 
> Anything else possible to check ? 
> 
> Slava. 
> 
>  
> From: "Slava Bendersky"  
> To: "Ondra Machacek"  
> Cc: "users"  
> Sent: Saturday, February 4, 2017 2:27:31 PM 
> 
> Subject: Re: [ovirt-users] FreeIPA with ovirt 4.1 
> 
> Hello Ondra, 
> Log is empty 
> 
> [root@vhe00 ~]# ls -la /var/log/httpd/ssl_error_log 
> -rw-r--r--. 1 root root 0 Feb 2 04:45 /var/log/httpd/ssl_error_log 
> 
> Slava. 
> 
>  
> From: "Ondra Machacek"  
> To: "Slava Bendersky"  
> Cc: "users" , "Ravi"  
> Sent: Saturday, February 4, 2017 10:35:31 AM 
> Subject: Re: [ovirt-users] FreeIPA with ovirt 4.1 
> 
> 
> 
> On Feb 4, 2017 1:21 AM, "Slava Bendersky"  wrote: 
> 
> Hello Everyone, 
> Having trouble implement FreeIPA authentication with GSSAPI SSO and ovirt 
> 4.1. I ran setup and it finished OK then it wrote the files bellow. Next I 
> log to web admin with internal user and added FeeIPA user as SuperUser role. 
> Also I added under System FreeIPA group authorized to login on any attempt 
> to login with FreeIPA credentials getting message 
> 
> 
> 2017-02-04 00:03:08,464Z ERROR 
> [org.ovirt.engine.core.sso.servlets.InteractiveAuthServlet] (default task-6) 
> [] Internal Server Error: Unsupported command 
> 2017-02-04 00:03:08,464Z ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] 
> (default task-6) [] Unsupported command 
> 2017-02-04 00:03:08,659Z ERROR 
> [org.ovirt.engine.core.aaa.servlet.SsoPostLoginServlet] (default task-3) [] 
> server_error: Unsupported command 
> 
> 
> Ravi, do you know what this can cause? 
> 
> 
> 
> Also when in extensions.d directory contain the following files. If I remove 
> mydomain.lan-authn.properties then in web ui FreeIPA domain not showing up 
> in drop down list. Any http don't have influence on this. 
> 
> 
> That is correct behavior, we dont show profiles, which uses http for authn. 
> 
> 
> [root@vhe00 extensions.d]# pwd 
> /etc/ovirt-engine/extensions.d 
> 
> [root@vhe00 extensions.d]# ls 
> mydomain.lan-authn.properties mydomain.lan-http-authn.properties 
> mydomain.lan.properties internal-authz.properties 
> mydomain.lan-authz.properties mydomain.lan-http-mapping.properties 
> internal-authn.properties 
> [root@vhe00 extensions.d]# 
> 
> 
> If possible clarify how it should be and what is possible issue. 
> 
> 
> Can you please take a look to /var/log/httpd/ssl_error_log if any errors 
> there? 
> 
> 
> 
> 
> Slava. 
> 
> ___ 
> Users mailing list 
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
> 
> 
> ___ 
> Users mailing list 
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Current state of UI brick management when using dedicated interfaces for ovirtmgmt & gluster?

[Doug Ingham]

Hey Guys,
 I currently use dedicated interfaces & hostnames to separate gluster
traffic on my "hyperconverged" hosts.

For example, the first node uses "v0" for its management interface & "s0"
for its gluster interface.

With this setup, I notice that all functions under the "Volumes" tab work,
however I'm unable to import storage domains with "Use managed gluster",
and hosts' bricks aren't listed under the "Hosts" tab.

My engine log is also full of entries such as this...

2017-02-10 03:25:07,155-03 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn]
(DefaultQuartzScheduler3) [78aef637] Could not add brick
's0:/gluster/data-novo/brick' to volume
'bded65c7-e79e-4bc9-9630-36a69ad2e684' - server uuid
'a9d062c6-7d01-404f-ab0c-3ed468e60c91' not found in cluster
'0002-0002-0002-0002-017a'
2017-02-10 03:25:09,157-03 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesHealInfoReturn]
(DefaultQuartzScheduler10) [6828f9a7] Could not fetch heal info for brick
's0:/gluster/data-novo/brick' - server uuid
'a9d062c6-7d01-404f-ab0c-3ed468e60c91' not found

I'm wondering whether the different hostnames used to configure each of the
interfaces is casuing the confusion?
So...is there something wrong, or is this still an unsupported
configuration?

Cheers,
-- 
Doug
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Network issues

[Bryan Sockel]

Need some help.  I was doing some work on one of my ovirt hosts, removed it 
from cluster, and re-added it to the cluster to bring it back into my 
working cluster.  I got a messege that my network's where out of sync.  I 
accidentally sync'd up my working network, now neither of my hosts will 
bring launch my hosted engine appliance.  While machines aren't currently 
mission critical, i do need to get these machines backup up and running.


The network configuration is supposed to be 6 nics forming a bond network, 
my vlan's hanging off that bond, including my ovirtmgmt network.




Feb 10 11:17:22 vm-host-altn-2.altn.int kernel: tg3 :81:00.1 p1p2: Flow 
control is off for TX and off for RX
Feb 10 11:17:22 vm-host-altn-2.altn.int kernel: tg3 :81:00.1 p1p2: EEE 
is disabled
Feb 10 11:17:22 vm-host-altn-2.altn.int kernel: bond0: link status 
definitely up for interface p1p2, 1000 Mbps full duplex
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: Bringing up interface 
bond0.102:  [  OK  ]
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: Bringing up interface 
bond0.20:  can't add bond0.20 to bridge DMZ: Operation not supported
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: [  OK  ]
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: Bringing up interface 
bond0.30:  can't add bond0.30 to bridge Devel: Operation not supported
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: [  OK  ]
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: Bringing up interface 
bond0.40:  can't add bond0.40 to bridge Lab: Operation not supported
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: [  OK  ]
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: Bringing up interface 
bond0.50:  can't add bond0.50 to bridge Workstation: Operation not supported
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: [  OK  ]
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: Bringing up interface 
Workstation:  device Workstation already exists; can't create bridge with 
the sa
Feb 10 11:17:26 vm-host-altn-2.altn.int network[1522]: [FAILED]
Feb 10 11:17:26 vm-host-altn-2.altn.int systemd[1]: network.service: control 
process exited, code=exited status=1
Feb 10 11:17:26 vm-host-altn-2.altn.int systemd[1]: Failed to start LSB: 
Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has failed.


..


Thanks___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error attempting to upload an ISO image

[Nelson Lameiras]

hello, 

I can also confirm this bug. 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 



From: "Berger, Sandy"  
To: users@ovirt.org 
Sent: Friday, February 10, 2017 5:14:18 PM 
Subject: [ovirt-users] Error attempting to upload an ISO image 



After the 4.1 upgrade, I’m getting the following results attempting to upload 
an ISO image: 



[root@waovccm1 ~]# ovirt-iso-uploader --iso-domain=waISOLibrary upload slb.iso 

Please provide the REST API password for the admin@internal oVirt Engine user 
(CTRL+D to abort): 

ERROR: v4 is not a valid StorageFormat 

INFO: Use the -h option to see usage. 



I was able to manually copy the file to the correct directory on the NFS server 
but can’t get the utility to work properly. 



Sandy Berger 

IT - EUX 



Quad/Graphics 

Performance through Innovation 



Sussex, Wisconsin 

414.566.2123 phone 

414.566.4010/2123 pager/PIN 



sandy.ber...@qg.com 

www.QG.com 


Follow Us: Facebook | Twitter | LinkedIn | YouTube 
___ 
Users mailing list 
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] high number of IOPS from ovirt hosts

[Andrea Fagiani]

Hi Andrea,

thanks for the insight; no I wasn't able to pinpoint the issue to a 
single host, the load seems to be evenly spread.
We have another cluster running 4.0.6 on a compellent as well and we 
haven't experienced any similar issues.


Thanks,
Andrea


On 10/02/2017 17:17, Andrea Ghelardi wrote:

Hello Andrea,
I saw that happening on my HE hosts connected to a COMPELLENT SC040 when I was 
running Ovirt 3.5

All HE hosts were hammering the SAN with 2~4k IOPS each

Upgrading to 4.0.5 solved my case.
Are you able to check if IOPS are generated from a particular host or rather 
spread among all nodes?

Cheers
AG


-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
Andrea Fagiani
Sent: Friday, February 10, 2017 12:47 PM
To: users@ovirt.org
Subject: [ovirt-users] high number of IOPS from ovirt hosts

Hi,

We've got a 8-host cluster running oVirt 4.1; each host is connected via iscsi 
to a EQL 4100 storage (2x).
Most of the VMs use barely any IOPS, however on our storage controller we've 
noticed a constant steam of reads, about 2000 IOPS; any idea what might cause 
the ovirt hosts to hammer on the storage so much?

Looking at iotop, it seems that systemd-udevd is being activated every few 
seconds (and its IO% is usually fairly high) so I assume this might be somehow 
related.

Thanks,
Andrea
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Error attempting to upload an ISO image

[Berger, Sandy]

After the 4.1 upgrade, I'm getting the following results attempting to upload 
an ISO image:

[root@waovccm1 ~]# ovirt-iso-uploader --iso-domain=waISOLibrary upload slb.iso
Please provide the REST API password for the admin@internal oVirt Engine user 
(CTRL+D to abort):
ERROR: v4 is not a valid StorageFormat
INFO: Use the -h option to see usage.

I was able to manually copy the file to the correct directory on the NFS server 
but can't get the utility to work properly.

Sandy Berger
IT - EUX

Quad/Graphics
Performance through Innovation

Sussex, Wisconsin
414.566.2123 phone
414.566.4010/2123 pager/PIN

sandy.ber...@qg.com
www.QG.com

Follow Us: Facebook | 
Twitter | LinkedIn | 
YouTube
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Storage domain experienced a high latency

[Nir Soffer]

On Thu, Feb 9, 2017 at 10:03 AM, Grundmann, Christian <
christian.grundm...@fabasoft.com> wrote:

> Hi,
>
> @ Can also be low level issue in kernel, hba, switch, server.
> I have the old storage on the same cable so I don’t think its hba or
> switch related
> On the same Switch I have a few ESXi Server with same storage setup which
> are working without problems.
>
> @multipath
> I use stock ng-node multipath configuration
>
> # VDSM REVISION 1.3
>
> defaults {
> polling_interval5
> no_path_retry   fail
> user_friendly_names no
> flush_on_last_del   yes
> fast_io_fail_tmo5
> dev_loss_tmo30
> max_fds 4096
> }
>
> # Remove devices entries when overrides section is available.
> devices {
> device {
> # These settings overrides built-in devices settings. It does not
> apply
> # to devices without built-in settings (these use the settings in
> the
> # "defaults" section), or to devices defined in the "devices"
> section.
> # Note: This is not available yet on Fedora 21. For more info see
> # https://bugzilla.redhat.com/1253799
> all_devsyes
> no_path_retry   fail
> }
> }
>
> # Enable when this section is available on all supported platforms.
> # Options defined here override device specific options embedded into
> # multipathd.
> #
> # overrides {
> #  no_path_retry   fail
> # }
>
>
> multipath -r v3
> has no output
>

My mistake, the correct command is:

multipath -r -v3

It creates tons of output, so better redirect to file and attach the file:

multipath -r -v3 > multiapth-r-v3.out


>
>
> Thx Christian
>
>
> Von: Nir Soffer [mailto:nsof...@redhat.com]
> Gesendet: Mittwoch, 08. Februar 2017 20:44
> An: Grundmann, Christian 
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Storage domain experienced a high latency
>
> On Wed, Feb 8, 2017 at 6:11 PM, Grundmann, Christian  christian.grundm...@fabasoft.com> wrote:
> Hi,
> got a new FC Storage (EMC Unity 300F) which is seen by my Hosts additional
> to my old Storage for Migration.
> New Storage has only on PATH until Migration is done.
> I already have a few VMs running on the new Storage without Problem.
> But after starting some VMs (don’t really no whats the difference to
> working ones), the Path for new Storage fails.
>
> Engine tells me: Storage Domain  experienced a high latency
> of 22.4875 seconds from host 
>
> Where can I start looking?
>
> In /var/log/messages I found:
>
> Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760:
> sdd - emc_clariion_checker: Active path is healthy.
> Feb  8 09:03:53 ovirtnode01 multipathd: 8:48: reinstated
> Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760:
> remaining active paths: 1
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 8
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 5833475
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 5833475
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967168
> Feb  8 09:03:53 ovirtnode01 kernel: Buffer I/O error on dev dm-207,
> logical block 97, async page read
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967168
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967280
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967280
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 0
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 0
> Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev
> dm-10, sector 4294967168
> Feb  8 09:03:53 ovirtnode01 kernel: device-mapper: multipath: Reinstating
> path 8:48.
> Feb  8 09:03:53 ovirtnode01 kernel: sd 3:0:0:22: alua: port group 01 state
> A preferred supports tolUsNA
> Feb  8 09:03:53 ovirtnode01 sanlock[5192]: 2017-02-08 09:03:53+0100 151809
> [11772]: s59 add_lockspace fail result -202
> Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: remove map (uevent)
> Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: devmap not registered,
> can't remove
> Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: remove map (uevent)
> Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: remove map (uevent)
> Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: devmap not registered,
> can't remove
> Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: remove map (uevent)
> Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: remove map (uevent)
> Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: devmap not registered,
> can't remove
> Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: remove map (uevent)
> Feb  8 09:04:08 ovirtnode01 kernel: dd: sending 

Re: [ovirt-users] high number of IOPS from ovirt hosts

[Andrea Ghelardi]

Hello Andrea,
I saw that happening on my HE hosts connected to a COMPELLENT SC040 when I was 
running Ovirt 3.5

All HE hosts were hammering the SAN with 2~4k IOPS each

Upgrading to 4.0.5 solved my case.
Are you able to check if IOPS are generated from a particular host or rather 
spread among all nodes?

Cheers
AG


-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
Andrea Fagiani
Sent: Friday, February 10, 2017 12:47 PM
To: users@ovirt.org
Subject: [ovirt-users] high number of IOPS from ovirt hosts

Hi,

We've got a 8-host cluster running oVirt 4.1; each host is connected via iscsi 
to a EQL 4100 storage (2x).
Most of the VMs use barely any IOPS, however on our storage controller we've 
noticed a constant steam of reads, about 2000 IOPS; any idea what might cause 
the ovirt hosts to hammer on the storage so much?

Looking at iotop, it seems that systemd-udevd is being activated every few 
seconds (and its IO% is usually fairly high) so I assume this might be somehow 
related.

Thanks,
Andrea
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Guest Agent Running unconfined on Centos 7

[Alan Griffiths]

Hi,

I'm running ovirt-guest-agent from Centos 7 EPEL and I notice that it's
running unconfined rather than within its own domain.

I see there is a rhev_agentd_exec_t type, which I attempted to assign to
ovirt-guest-agent.py but it still starts up as unconfined. Is there a
supported process for getting ovirt-guest into its own domain? Or a reason
why it's not possible?

Thanks,

Alan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manually starting VMs via vdsClient (HE offline)

[Dan Yasny]

On Fri, Feb 10, 2017 at 8:20 AM, Nathanaël Blanchet 
wrote:

>
>>> If you use a dedicated host, you might as well abandon self hosted. HE
>>> is nice for small setups with the HA built in for extra fun, but once you
>>> scale, it might not be able to cope and you'll need real hardware. You're
>>> running a heavy-ish java engine plus two databases after all.
>>>
>> I'd be interested to know what type of scale needs a real hardware for
> engine, rather 100 vms or 1000 vms? it may be about the hosts number?
>

YMMV of course. But it only stands to reason, that a certain amount of load
is going to overwhelm a single VM. VMWare also have a scale limitation on
the VM based vcenter btw
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Best way to shutdown and restart hypervisor?

[Martin Perina]

On Fri, Feb 10, 2017 at 2:56 PM, Gianluca Cecchi 
wrote:

> On Fri, Feb 10, 2017 at 2:27 PM, Martin Perina  wrote:
>
>> Hi Gianluca,
>>
>> so generally speaking when host is in Maintenance status, engine doesn't
>> communicate with this host, so you can do pretty much anything about it.
>>
>
> Thanks for the detailed answer, Martin.
> It seemed to me that in the past I did a reboot at the host OS level while
> in maintenance and this generated a series of fencing/reboots of the host
> itself, so I wanted to be sure.
> It is possible that at that time I also used "Confirm host has been
> rebooted" button, as initially I misunderstood its target and it was
> that action to generate fencing loops (2 or 3 I don't remember).
> Then in Admin manual for 4.0 I saw that instead it is only to be used in
> case of unresponsive host, correct?
>
> "
> If a host unpredictably goes into a non-responsive state, for example, due
> to a hardware failure;
> it can significantly affect the performance of the environment. If you do
> not have a power
> management device, or it is incorrectly configured, you can reboot the
> host manually.
>
> Do not use the Confirm host has been rebooted option unless you have
> manually
> rebooted the host. Using this option while the host is still running can
> lead to a virtual
> machine image corruption.
>
> Procedure 7.20. Manually fencing or isolating a non-responsive host
> 1. On the Hosts tab, select the host. The status must display as
> non-responsive.
> 2. Manually reboot the host. This could mean physically entering the lab
> and rebooting the
> host.
> 3. On the Administration Portal, right-click the host entry and select the
> Confirm Host has
> been rebooted button.
> 4. A message displays prompting you to ensure that the host has been shut
> down or
> rebooted. Select the Approve Operation check box and click OK.
> "
>
> Initially I misread and kept focus only to the "Manually fencing" and
> "Manually reboot" but point 1. seems quite clear:
> The status must display as non-responsive.
> So no other use for "Confirm Host has been rebooted"
> I will verify again the workflow
>

​Right, by executing "Confirm Host has been rebooted" you take the
responsibility and tell engine, that everything running on the host is
really turned off. After that engine can change VM statuses do Down and
restart HA VMs. But this option has to be used really carefully, otherwise
you could cause data loss or even split brain. IMO this option should be
used only if your hosts does not support Power Management (in this case you
cannot have HA VMs) or you have some hardware failure which prevents power
management to turn off the host.
​


>
>
>
>
>>
>> About the upgrade flow (host 4.0 -> 4.1), here's proper way(s) how to
>> achieve that:
>>
>
> Yes, my question was in general, eg when I'm going to pass from 4.1.0.4 to
> 4.1.1
>
>
>>
>> 1. Put host to Maintenance
>> 2. Add 4.1 repositories to the host
>> 3. Upgrade the host - you have 2 options here:
>> a. UI
>> - Go to Hosts tab in webadmin
>> - Select host and click on Reinstall inside Installation menu
>> b. Command line
>> - Connect to the host using SSH and upgrade using yum
>>
>
> Sometimes at this point I could have a new kernel to boot, due to the
> update just completed, so the point 4. is not what I would like to do right
> now.
>

​Yes, but this is OS upgrade, which should be done only manually via SSH
and only when host is in Maintenance. ​

​By "host upgrade​" in oVirt terms we usually mean only upgrade of VDSM and
dependent packages like libvirt or qemu-kvm ...


>
>> 4. Activate the host
>>
>
>> The main difference between UI and command line options is, that with UI
>> option only necessary packages like VDSM and it's dependencies are upgraded.
>>
>> ​Now regarding restart:
>> 1. If host is in Maintenance, restart using SSH and shutdown/reboot
>> execution is no problem​. But if host is Up, then executing shutdown/reboot
>> using SSH will make host NonResponsive and fencing will be executed
>>
>> 2. If you select Restart using SSH from Maintenance menu, it just
>> connect using SSH and execute shutdown same way as it's done manually
>>
>> 3. If you select Restart using Power Management from Maintenance
>> menu, it will execute restart using PM device and further actions are
>> hardware dependent. On some servers it will send shutdown signal to OS
>> similarly as if you execute reboot and afterwards it turns off power of the
>> server (so the result may be the same as using shutdown from command line).
>> But on different hardware it can just turn off power of the server.
>>
>> So for planned restart using SSH restart either from UI or from command
>> line is preferred way.
>>
>
>
> Ok, so a normal reboot is ok as point 4..
> And then after reboot
> 5. Activate (and not "Confirm Host Has Rebooted"... ;-)
>

​Right
​


>
>
> Regarding Power Mgmt ---> Restart
> I thought that in general I should 

Re: [ovirt-users] Best way to shutdown and restart hypervisor?

[Gianluca Cecchi]

On Fri, Feb 10, 2017 at 2:27 PM, Martin Perina  wrote:

> Hi Gianluca,
>
> so generally speaking when host is in Maintenance status, engine doesn't
> communicate with this host, so you can do pretty much anything about it.
>

Thanks for the detailed answer, Martin.
It seemed to me that in the past I did a reboot at the host OS level while
in maintenance and this generated a series of fencing/reboots of the host
itself, so I wanted to be sure.
It is possible that at that time I also used "Confirm host has been
rebooted" button, as initially I misunderstood its target and it was
that action to generate fencing loops (2 or 3 I don't remember).
Then in Admin manual for 4.0 I saw that instead it is only to be used in
case of unresponsive host, correct?

"
If a host unpredictably goes into a non-responsive state, for example, due
to a hardware failure;
it can significantly affect the performance of the environment. If you do
not have a power
management device, or it is incorrectly configured, you can reboot the host
manually.

Do not use the Confirm host has been rebooted option unless you have
manually
rebooted the host. Using this option while the host is still running can
lead to a virtual
machine image corruption.

Procedure 7.20. Manually fencing or isolating a non-responsive host
1. On the Hosts tab, select the host. The status must display as
non-responsive.
2. Manually reboot the host. This could mean physically entering the lab
and rebooting the
host.
3. On the Administration Portal, right-click the host entry and select the
Confirm Host has
been rebooted button.
4. A message displays prompting you to ensure that the host has been shut
down or
rebooted. Select the Approve Operation check box and click OK.
"

Initially I misread and kept focus only to the "Manually fencing" and
"Manually reboot" but point 1. seems quite clear:
The status must display as non-responsive.
So no other use for "Confirm Host has been rebooted"
I will verify again the workflow




>
> About the upgrade flow (host 4.0 -> 4.1), here's proper way(s) how to
> achieve that:
>

Yes, my question was in general, eg when I'm going to pass from 4.1.0.4 to
4.1.1


>
> 1. Put host to Maintenance
> 2. Add 4.1 repositories to the host
> 3. Upgrade the host - you have 2 options here:
> a. UI
> - Go to Hosts tab in webadmin
> - Select host and click on Reinstall inside Installation menu
> b. Command line
> - Connect to the host using SSH and upgrade using yum
>

Sometimes at this point I could have a new kernel to boot, due to the
update just completed, so the point 4. is not what I would like to do right
now.


> 4. Activate the host
>

> The main difference between UI and command line options is, that with UI
> option only necessary packages like VDSM and it's dependencies are upgraded.
>
> ​Now regarding restart:
> 1. If host is in Maintenance, restart using SSH and shutdown/reboot
> execution is no problem​. But if host is Up, then executing shutdown/reboot
> using SSH will make host NonResponsive and fencing will be executed
>
> 2. If you select Restart using SSH from Maintenance menu, it just
> connect using SSH and execute shutdown same way as it's done manually
>
> 3. If you select Restart using Power Management from Maintenance menu,
> it will execute restart using PM device and further actions are hardware
> dependent. On some servers it will send shutdown signal to OS similarly as
> if you execute reboot and afterwards it turns off power of the server (so
> the result may be the same as using shutdown from command line). But on
> different hardware it can just turn off power of the server.
>
> So for planned restart using SSH restart either from UI or from command
> line is preferred way.
>


Ok, so a normal reboot is ok as point 4..
And then after reboot
5. Activate (and not "Confirm Host Has Rebooted"... ;-)


Regarding Power Mgmt ---> Restart
I thought that in general I should completely disable on the host the
feature to initiate shutdown in case of power button pressed, like in RHCS
or similar targeted environments:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/s2-acpi-disable-boot-CA.html

Is it not the case in oVirt? I think in case of fencing, it is necessary to
have the host down as soon as possible
My initial question was the confirmation about Power Mgmt --> Restart : if
it implied power Off / Power On by design or any other workflow

Thanks in advance,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Best way to shutdown and restart hypervisor?

[Martin Perina]

Hi Gianluca,

so generally speaking when host is in Maintenance status, engine doesn't
communicate with this host, so you can do pretty much anything about it.

About the upgrade flow (host 4.0 -> 4.1), here's proper way(s) how to
achieve that:

1. Put host to Maintenance
2. Add 4.1 repositories to the host
3. Upgrade the host - you have 2 options here:
a. UI
- Go to Hosts tab in webadmin
- Select host and click on Reinstall inside Installation menu
b. Command line
- Connect to the host using SSH and upgrade using yum
4. Activate the host

The main difference between UI and command line options is, that with UI
option only necessary packages like VDSM and it's dependencies are upgraded.

​Now regarding restart:
1. If host is in Maintenance, restart using SSH and shutdown/reboot
execution is no problem​. But if host is Up, then executing shutdown/reboot
using SSH will make host NonResponsive and fencing will be executed

2. If you select Restart using SSH from Maintenance menu, it just
connect using SSH and execute shutdown same way as it's done manually

3. If you select Restart using Power Management from Maintenance menu,
it will execute restart using PM device and further actions are hardware
dependent. On some servers it will send shutdown signal to OS similarly as
if you execute reboot and afterwards it turns off power of the server (so
the result may be the same as using shutdown from command line). But on
different hardware it can just turn off power of the server.

So for planned restart using SSH restart either from UI or from command
line is preferred way.

​Martin​


On Fri, Feb 10, 2017 at 1:57 PM, Sandro Bonazzola 
wrote:

> Adding some people
>
> On Thu, Feb 9, 2017 at 2:08 PM, Gianluca Cecchi  > wrote:
>
>> On Wed, Feb 8, 2017 at 10:59 AM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> Hello,
>>> what is considered the best way to shutdown and restart an hypervisor,
>>> supposing plain CentOS 7 host?
>>>
>>> For example to cover these scenarios:
>>> 1) update host from 4.0 to 4.1
>>> 2) planned maintenance to the cabinet where the server is located and
>>> take the opportunity to update also OS packages
>>>
>>> My supposed workflow:
>>>
>>> - put host into maintenance
>>> - yum update on host
>>> - shutdown os from inside host (because from power mgmt it is brutal
>>> power off / power on)
>>> --> should I get any warning from web admin gui in this case, even if
>>> the host was in maintenance mode?
>>> - power mgmt -> start from webadmin gui
>>> (or power on button/virtual button at host side?)
>>>
>>> Would be advisable to put inside power mgmt functionality some logic
>>> about os mgmt, so for example, if action is restart, first try to shutdown
>>> OS and only in case of failure power off/power on?
>>>
>>> Thanks in advance,
>>> Gianluca
>>>
>>
>> I see that one of the new features of 4.1 is Host restart through SSH
>> Power Mgmt --> SSH Mgmt --> Restart
>>
>> How does it fit in question above?
>> Can I choose this way after having run "yum update" on host?
>> Thanks
>> Gianluca
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Best way to shutdown and restart hypervisor?

[Doug Ingham]

On 9 February 2017 at 10:08, Gianluca Cecchi 
wrote:

> On Wed, Feb 8, 2017 at 10:59 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Hello,
>> what is considered the best way to shutdown and restart an hypervisor,
>> supposing plain CentOS 7 host?
>>
>> For example to cover these scenarios:
>> 1) update host from 4.0 to 4.1
>> 2) planned maintenance to the cabinet where the server is located and
>> take the opportunity to update also OS packages
>>
>> My supposed workflow:
>>
>> - put host into maintenance
>> - yum update on host
>> - shutdown os from inside host (because from power mgmt it is brutal
>> power off / power on)
>> --> should I get any warning from web admin gui in this case, even if the
>> host was in maintenance mode?
>> - power mgmt -> start from webadmin gui
>> (or power on button/virtual button at host side?)
>>
>
I'd add one more step at the beginning, update the cluster's scheduling
policy to InClusterUpgrade. That will automatically migrate your VMs to the
most up-to-date host, freeing your other hosts for a rolling upgrade of the
cluster.


>
>
>> Would be advisable to put inside power mgmt functionality some logic
>> about os mgmt, so for example, if action is restart, first try to shutdown
>> OS and only in case of failure power off/power on?
>>
>> Thanks in advance,
>> Gianluca
>>
>
> I see that one of the new features of 4.1 is Host restart through SSH
> Power Mgmt --> SSH Mgmt --> Restart
>
> How does it fit in question above?
> Can I choose this way after having run "yum update" on host?
>

Features are made available only after you update all of the hosts in the
cluster & the (Hosted-)Engine to the same version. Then you can update the
Compatibility Version of the cluster.

http://www.ovirt.org/documentation/self-hosted/chap-Maintenance_and_Upgrading_Resources/

-- 
Doug
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manually starting VMs via vdsClient (HE offline)

[Nathanaël Blanchet]

Le 09/02/2017 à 19:48, Yaniv Kaul a écrit :



On Thu, Feb 9, 2017 at 6:00 PM, Doug Ingham > wrote:




On 9 February 2017 at 12:03, Dan Yasny mailto:dya...@gmail.com>> wrote:


On Thu, Feb 9, 2017 at 9:55 AM, Doug Ingham mailto:dou...@gmail.com>> wrote:

Hi Dan,

On 8 February 2017 at 18:26, Dan Yasny mailto:dya...@gmail.com>> wrote:


But seriously, above all, I'd recommend you backup the
engine (it comes with a utility) often and well. I do
it via cron every hour in production, keeping a
rotation of hourly and daily backups, just in case. It
doesn't take much space or resources, but it's more
than just best practice - that database is the summary
of the entire setup.


If you don't mind, may I ask what process you use for
backing up your engine? If you use HE, do you keep one
server dedicated to just that VM?
I've not had that particular issue in the restore process
yet, however I read that it's recommended the HE host is
free of virtual load before the backup takes place. And as
they need to be done frequently, I'm reading that as a
dedicated host...


If you use a dedicated host, you might as well abandon self
hosted. HE is nice for small setups with the HA built in for
extra fun, but once you scale, it might not be able to cope
and you'll need real hardware. You're running a heavy-ish java
engine plus two databases after all.

I'd be interested to know what type of scale needs a real hardware for 
engine, rather 100 vms or 1000 vms? it may be about the hosts number?



So as I said, all I do is add the engine-backup command to
cron on the engine, and then my backup server comes in and
pulls out the files via scp, also through cron. Nothing fancy
really, but it lets me sleep at night


This particular project has 10 new maxed out servers to back it,
and I don't see it outgrowing that for at least a year or so. It's
hardly a full DC.
I presume the DB will become the heaviest part of the load, and
I'm already planning a separate high I/O environment for dedicated
HA DB hosts.

See the top section of this page:

http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment



It seems that I'll always have to keep at least one host free to
be able to avoid restore problems. If not, and I were to keep
hourly backups, then migrating VMs off the host every hour would
just be a pain.


I don't see the point in an hourly backup. Of what? The DB? The VM? 
What storage will it be based on?

I suggest revising the strategy.



-- 
Doug


___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Getting error while trying to add VmPool using ovirtsdk4 version of the python api

[Juan Hernández]

On 02/10/2017 01:43 PM, Manuel Luis Aznar wrote:
> Hello there,
> 
> I am trying to add a VmPool to oVirt using the python ovirtSDK4 with
> following lines:
> 
> I am omitting the import packages lines and connection lines.
> 
> 
> 
> system_service = connection.system_service()
> 
> vm_pools_service = system_service.vm_pools_service()
> 
> templates_service = system_service.templates_service()
> 
> clusters_service = system_service.clusters_service()
> 
> tplist = templates_service.list(search='name=prueba')
> 
> tpl=None
> biggest=-1
> fort intplist:
>  ver = t.version
>  ifver.version_number > biggest:
>  biggest = ver.version_number
>  tid = t.id 
>  tpl = t  
> 
> c = None
> forcluster inclusters_service.list():
> ifcluster.name  == 'Pruebacluster':
> c = cluster
> 
> pool =
> ovirtsdk4.types.VmPool(name='PRUEBA',size=1,type=ovirtsdk4.types.VmPoolType('manual'),template=tpl,cluster=c)
>  
> vm_pools_service.add(pool=pool)
> 
> 
> 
> I am getting the following error:
> 
>Fault reason is "Request syntactically incorrect.". Fault detail is
> "For correct usage, see:
> https://ovirt.example.com/ovirt-engine/api/v4/model#services/vm-pools/methods/add";.
> HTTP  response code is 400.
> 
> I am a newbie in using this version of the API, suppose this is quite
> easy problem.
> 
> Thanks for all the answers to come,
> Manuel
> 

This look like this bug, fixed in version 4.1 of the SDK:

  Importing a VM using the SDK fails
  https://bugzilla.redhat.com/1408839

However there is a good practice that I recommend you to apply, which
will probably avoid the issue. That good practice is avoid sending to
the server the complete objects that you got from other requests. For
example, in this case you are sending to the server the complethe 'tpl'
and 'c' clusters that you got from other requests. Instead of that, try
to send only what is required:

  pool = ovirttsdk4.types.VmPool(
name='PRUEBA',
size=1,
type=ovirtsdk4.types.VmPoolType.MANUAL,
template=ovirtsdk4.types.Template(id=tpl.id),
cluster=ovirtsdk4.types.Cluster(id=c.id)
  )
  vm_pools_servcie.add(pool=pool)

The key point here is creating new 'Template' and 'Cluster' objects that
only contain the 'id', as that is all what the server needs. If you send
the complete template and cluster you are wasting resources, and
exposing yourself to bugs like the mentioned above.

Please try that and let us know if it solves your issue.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Best way to shutdown and restart hypervisor?

[Sandro Bonazzola]

Adding some people

On Thu, Feb 9, 2017 at 2:08 PM, Gianluca Cecchi 
wrote:

> On Wed, Feb 8, 2017 at 10:59 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Hello,
>> what is considered the best way to shutdown and restart an hypervisor,
>> supposing plain CentOS 7 host?
>>
>> For example to cover these scenarios:
>> 1) update host from 4.0 to 4.1
>> 2) planned maintenance to the cabinet where the server is located and
>> take the opportunity to update also OS packages
>>
>> My supposed workflow:
>>
>> - put host into maintenance
>> - yum update on host
>> - shutdown os from inside host (because from power mgmt it is brutal
>> power off / power on)
>> --> should I get any warning from web admin gui in this case, even if the
>> host was in maintenance mode?
>> - power mgmt -> start from webadmin gui
>> (or power on button/virtual button at host side?)
>>
>> Would be advisable to put inside power mgmt functionality some logic
>> about os mgmt, so for example, if action is restart, first try to shutdown
>> OS and only in case of failure power off/power on?
>>
>> Thanks in advance,
>> Gianluca
>>
>
> I see that one of the new features of 4.1 is Host restart through SSH
> Power Mgmt --> SSH Mgmt --> Restart
>
> How does it fit in question above?
> Can I choose this way after having run "yum update" on host?
> Thanks
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Getting error while trying to add VmPool using ovirtsdk4 version of the python api

[Manuel Luis Aznar]

Hello there,

I am trying to add a VmPool to oVirt using the python ovirtSDK4 with
following lines:

I am omitting the import packages lines and connection lines.



system_service = connection.system_service()

vm_pools_service = system_service.vm_pools_service()

templates_service = system_service.templates_service()

clusters_service = system_service.clusters_service()

tplist = templates_service.list(search='name=prueba')

tpl=None
biggest=-1
for t in tplist:
 ver = t.version
 if ver.version_number > biggest:
 biggest = ver.version_number
 tid = t.id
 tpl = t

c = None
for cluster in clusters_service.list():
if cluster.name == 'Pruebacluster':
c = cluster

pool = ovirtsdk4.types.VmPool(name='PRUEBA',size=1,type
=ovirtsdk4.types.VmPoolType('manual'),template=tpl,cluster=c)
vm_pools_service.add(pool=pool)



I am getting the following error:

   Fault reason is "Request syntactically incorrect.". Fault detail is "For
correct usage, see:
https://ovirt.example.com/ovirt-engine/api/v4/model#services/vm-pools/methods/add";.
HTTP  response code is 400.

I am a newbie in using this version of the API, suppose this is quite easy
problem.

Thanks for all the answers to come,
Manuel
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VDAgent

[Sandro Bonazzola]

On Thu, Feb 9, 2017 at 4:33 PM, Fernando Fuentes 
wrote:

> Sandro,
>
> Just wanted to report that after the full host upgrade everything return
> to normal.
>

Thanks!



>
> Thanks!
>
> Regards,
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
> On Mon, Feb 6, 2017, at 05:03 AM, Sandro Bonazzola wrote:
>
>
>
> On Sat, Feb 4, 2017 at 9:59 PM, Fernando Fuentes 
> wrote:
>
>
> Hello Sandro,
> Thanks for your reply!
>
> I will do that. I want to make sure though that updating the host will not
> make my guests loose the ability to use spice and nor will it create a
> problem with my oVirt Manager been on 4.0.X branch?
>
>
> Adding some people that may confirm but I think there shouldn't be any
> regression on it.
>
>
>
>
> Thanks!
>
>
> Regards,
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
>
> On Fri, Feb 3, 2017, at 01:11 PM, Sandro Bonazzola wrote:
>
>
>
> Il 30/Gen/2017 09:56 PM, "Fernando Fuentes"  ha
> scritto:
>
>
> Sandro,
>
> I did the update from the hosts tab on ovirt:
> The ovirt version is: oVirt Engine Version: 4.0.2.6-1.el7.centos
>
>
>
> Sorry Fernando I missed your email.
> I would suggest to update your hosts to centos 7.3 and oVirt 4.1.
> If you don't want to upgrade to 4.1 please upgrade at least to latest 4.0
> which is 4.0.6.
>
>
>
>
>
> All of my hosts are Cent7 x86_64
> [root@ogias ~]# uname -a
> Linux ogias.aasteel.net 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23
> 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [root@ogias ~]# cat /etc/redhat-release
> CentOS Linux release 7.2.1511 (Core)
> [root@ogias ~]#
>
> I am trying to email you the sos report but it exceeds our mail server
> size limit :(
>
> Regards,
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
> On Sat, Jan 28, 2017, at 12:29 PM, Sandro Bonazzola wrote:
>
>
>
> Il 27/Gen/2017 16:51, "Fernando Fuentes"  ha
> scritto:
>
> Team,
>
> After a host update on my cluster, All of my Windows vm's running the
> vdagent from the ovirt tools are running at 100% CPU utilization.
>
> Any ideas why would this happen?
>
>
> Hi,
> Can you please share details about the update?
> Which distribution? What has been updated? Can you share a sos report from
> the host?
>
>
>
>
> Regards,
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] high number of IOPS from ovirt hosts

[Andrea Fagiani]

Hi,

We've got a 8-host cluster running oVirt 4.1; each host is connected via 
iscsi to a EQL 4100 storage (2x).
Most of the VMs use barely any IOPS, however on our storage controller 
we've noticed a constant steam of reads, about 2000 IOPS; any idea what 
might cause the ovirt hosts to hammer on the storage so much?


Looking at iotop, it seems that systemd-udevd is being activated every 
few seconds (and its IO% is usually fairly high) so I assume this might 
be somehow related.


Thanks,
Andrea
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] "epel-release preventing host update."

[Arman Khalatyan]

After upgrade to ovirt 4.1 the epel has an conflicts in the collectd part:
if you disable epel from the hosts it is ok.

the hosts are not able to check or update because of this:

017-02-10 11:51:17,056+01 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.EvenGuestDistributionBalancePolicyUnit]
(DefaultQuartzScheduler6) [a13d0a89-a1d4-495c-9ed4-5e30aae11ae8] There is
no host with more than 10 running guests, no balancing is needed
2017-02-10 11:51:17,069+01 WARN
[org.ovirt.engine.core.bll.scheduling.policyunits.CpuAndMemoryBalancingPolicyUnit]
(DefaultQuartzScheduler6) [a13d0a89-a1d4-495c-9ed4-5e30aae11ae8] All
candidate hosts have been filtered, can't balance the cluster 'clei' based
on the CPU usage, will try memory based approach
2017-02-10 11:51:17,099+01 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.PowerSavingBalancePolicyUnit]
(DefaultQuartzScheduler6) [a13d0a89-a1d4-495c-9ed4-5e30aae11ae8] Automatic
power management is disabled for cluster 'clei'.
2017-02-10 11:51:27,278+01 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Yum: [u'collectd-write_http-5.7.0-2.el7.x86_64 requires collectd(x86-64) =
5.7.0-2.el7', u'collectd-disk-5.7.0-2.el7.x86_64 requires collectd(x86-64)
= 5.7.0-2.el7']
2017-02-10 11:51:27,278+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Yum: Performing yum transaction rollback
2017-02-10 11:51:27,281+01 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Failed to execute stage 'Package installation':
[u'collectd-write_http-5.7.0-2.el7.x86_64 requires collectd(x86-64) =
5.7.0-2.el7', u'collectd-disk-5.7.0-2.el7.x86_64 requires collectd(x86-64)
= 5.7.0-2.el7']
2017-02-10 11:51:27,281+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Yum Performing yum transaction rollback
2017-02-10 11:51:27,378+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Stage: Pre-termination
2017-02-10 11:51:27,400+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Retrieving installation logs to:
'/var/log/ovirt-engine/host-deploy/ovirt-host-mgmt-20170210115127-clei36.cls-a9265eb.log'
2017-02-10 11:51:27,533+01 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [a9265eb]
Stage: Termination
2017-02-10 11:51:27,708+01 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog] (pool-5-thread-3) [a9265eb]
SSH error running command r...@clei36.cls:'umask 0077;
MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XX)"; trap
"chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" >
/dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x &&
"${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
DIALOG/customization=bool:True': Command returned failure code 1 during SSH
session 'r...@clei36.cls'
2017-02-10 11:51:27,708+01 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog] (pool-5-thread-3) [a9265eb]
Exception: java.io.IOException: Command returned failure code 1 during SSH
session 'r...@clei36.cls'
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] What is the libcacard-ev.x86_64 ??

[Arman Khalatyan]

I have a host which was updated since 3.6
libcacard is disappeared from ovirt4.1 but it has a many dependencies which
stops to remove it:

[root@clei36 ~]# yum list installed | grep ovirt| grep 4.0
libcacard-ev.x86_6410:2.3.0-31.el7.16.1
@ovirt-4.0

yum update libcacard-ev
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.fau.de
 * epel: ftp.fau.de
 * extras: ftp.fau.de
 * ovirt-4.1: ftp.nluug.nl
 * ovirt-4.1-epel: ftp.fau.de
 * updates: mirror.eu.oneandone.net
No packages marked for update

yum remove  libcacard-ev.x86_64
Loaded plugins: fastestmirror
Resolving Dependencies
--> Running transaction check
---> Package libcacard-ev.x86_64 10:2.3.0-31.el7.16.1 will be erased
--> Processing Dependency: libcacard.so.0()(64bit) for package:
10:qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64
--> Running transaction check
---> Package qemu-kvm-ev.x86_64 10:2.6.0-28.el7_3.3.1 will be erased
--> Processing Dependency: qemu-kvm >= 1.5.3-92.el7 for package:
1:virt-v2v-1.32.7-3.el7.centos.2.x86_64
--> Processing Dependency: qemu-kvm for package:
libvirt-daemon-kvm-2.0.0-10.el7_3.4.x86_64
--> Processing Dependency: qemu-kvm-rhev >= 10:2.6.0-2 for package:
vdsm-4.19.4-1.el7.centos.x86_64
--> Running transaction check
---> Package libvirt-daemon-kvm.x86_64 0:2.0.0-10.el7_3.4 will be erased
--> Processing Dependency: libvirt-daemon-kvm >= 1.2.8-3 for package:
1:libguestfs-1.32.7-3.el7.centos.2.x86_64
---> Package vdsm.x86_64 0:4.19.4-1.el7.centos will be erased
--> Processing Dependency: vdsm = 4.19.4-1.el7.centos for package:
vdsm-hook-vmfex-dev-4.19.4-1.el7.centos.noarch
---> Package virt-v2v.x86_64 1:1.32.7-3.el7.centos.2 will be erased
--> Processing Dependency: virt-v2v for package: safelease-1.0-7.el7.x86_64
--> Running transaction check
---> Package libguestfs.x86_64 1:1.32.7-3.el7.centos.2 will be erased
--> Processing Dependency: libguestfs = 1:1.32.7-3.el7.centos.2 for
package: 1:libguestfs-tools-c-1.32.7-3.el7.centos.2.x86_64
--> Processing Dependency: libguestfs >= 1:1.28.1 for package:
libguestfs-winsupport-7.2-1.el7.x86_64
--> Processing Dependency: libguestfs.so.0()(64bit) for package:
1:libguestfs-tools-c-1.32.7-3.el7.centos.2.x86_64
---> Package safelease.x86_64 0:1.0-7.el7 will be erased
---> Package vdsm-hook-vmfex-dev.noarch 0:4.19.4-1.el7.centos will be erased
--> Running transaction check
---> Package libguestfs-tools-c.x86_64 1:1.32.7-3.el7.centos.2 will be
erased
---> Package libguestfs-winsupport.x86_64 0:7.2-1.el7 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

==
 Package
Arch
Version
Repository   Size
==
Removing:
 libcacard-ev
x86_64
10:2.3.0-31.el7.16.1
@ovirt-4.0   47 k
Removing for dependencies:
 libguestfs
x86_64
1:1.32.7-3.el7.centos.2
@updates3.8 M
 libguestfs-tools-c
x86_64
1:1.32.7-3.el7.centos.2
@updates 14 M
 libguestfs-winsupport
x86_64
7.2-1.el7
@base   2.2 M
 libvirt-daemon-kvm
x86_64
2.0.0-10.el7_3.4
@updates0.0
 qemu-kvm-ev
x86_64
10:2.6.0-28.el7_3.3.1
@ovirt-4.1  9.6 M
 safelease
x86_64
1.0-7.el7
@centos-ovirt41-candidate43 k
 vdsm
x86_64
4.19.4-1.el7.centos
@ovirt-4.1  2.5 M
 vdsm-hook-vmfex-dev
noarch
4.19.4-1.el7.centos
@ovirt-4.1   21 k
 virt-v2v
x86_64
1:1.32.7-3.el7.centos.2
@updates 16 M

Transaction Summary
==
Remove  1 Package (+9 Dependent packages)

Installed size: 49 M
Is this ok [y/N]: n
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Exporting VM as ova

[Benjamin Alfery]

Hi,

I'm using ovirt 4.0 and was wondering if it is possible to export an
existing VM to ova format (via the gui). If it's not possible via GUI,
is that possible at all?


Best Regards
Benjamin
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users