from:"Lev Veyde"

[ovirt-users] [ANN] oVirt 4.4.6 Third Release Candidate is now available for testing

2021-04-08 Thread Lev Veyde

oVirt 4.4.6 Third Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.6
Third Release Candidate for testing, as of April 8th, 2021.

This update is the sixth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.6 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.6 release highlights:
http://www.ovirt.org/release/4.4.6/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.6/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ODKN6XHBFNWI5ZMPUHNYTYE3SOUKTLXR/

[ovirt-users] [ANN] oVirt 4.4.6 Second Release Candidate is now available for testing

2021-04-01 Thread Lev Veyde

oVirt 4.4.6 Second Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.6
Second Release Candidate for testing, as of April 1st, 2021.

This update is the sixth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.6 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.6 release highlights:
http://www.ovirt.org/release/4.4.6/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.6/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.6 First Release Candidate is now available for testing

2021-03-25 Thread Lev Veyde

oVirt 4.4.6 First Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.6
First Release Candidate for testing, as of March 25th, 2021.

This update is the sixth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.6 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.6 release highlights:
http://www.ovirt.org/release/4.4.6/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.6/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] oVirt 4.4.5 is now generally available

2021-03-18 Thread Lev Veyde

oVirt 4.4.5 is now generally available

The oVirt project is excited to announce the general availability of oVirt
4.4.5 , as of March 18th, 2021.

This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade

Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).

Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.

For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
)
Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download <https://ovirt.org/download/> page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation <https://ovirt.org/documentation/>.
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   <https://ovirt.org/documentation/upgrade_guide/>.
   -

   For a general overview of oVirt, see About oVirt
   <https://ovirt.org/community/about.html>.

What’s new in oVirt 4.4.5 Release?

This update is the fifth in a series of stabilization updates to the 4.4
series.

This release is available now on x86_64 architecture for:

   -

   Red Hat Enterprise Linux 8.3
   -

   CentOS Linux (or similar) 8.3
   -

   CentOS Stream (tech preview)


This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

   -

   Red Hat Enterprise Linux 8.3
   -

   CentOS Linux (or similar) 8.3
   -

   oVirt Node (based on CentOS Linux 8.3)
   -

   CentOS Stream (tech preview)



oVirt Node and Appliance have been updated, including:

   -

   oVirt 4.4.5: https://www.ovirt.org/release/4.4.5/
   -

   Ansible 2.9.18:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-18

   -

   Advanced Virtualization 8.3.1
   -

   Gluster 8.4: https://docs.gluster.org/en/latest/release-notes/8.4/



See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

   -

   oVirt Appliance is already available for CentOS Linux 8
   -

   oVirt Node NG is already available for CentOS Linux 8


Additional resources:

   -

   Read more about the oVirt 4.4.5 release highlights:
   https://www.ovirt.org/release/4.4.5/
   -

   Get more oVirt project updates on Twitter: https://twitter.com/ovirt
   -

   Check out the latest project news on the oVirt blog:
   https://blogs.ovirt.org/


[1] https://www.ovirt.org/release/4.4.5/

[2] https://resources.ovirt.org/pub/ovirt-4.4/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2WJP6BDXLWABBZSEJ6VZIROV2BXBTOF5/

[ovirt-users] [ANN] oVirt 4.4.5 Eighth Release Candidate is now available for testing

2021-03-04 Thread Lev Veyde

oVirt 4.4.5 Eighth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Eighth Release Candidate for testing, as of March 4th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.5 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.5 release highlights:
http://www.ovirt.org/release/4.4.5/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.5/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.5 Seventh Release Candidate is now available for testing

2021-02-25 Thread Lev Veyde

oVirt 4.4.5 Seventh Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Seventh Release Candidate for testing, as of February 25th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.5 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.5 release highlights:
http://www.ovirt.org/release/4.4.5/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.5/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.5 Sixth Release Candidate is now available for testing

2021-02-22 Thread Lev Veyde

oVirt 4.4.5 Sixth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Sixth Release Candidate for testing, as of February 18th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.5 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.5 release highlights:
http://www.ovirt.org/release/4.4.5/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.5/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.5 Fifth Release Candidate is now available for testing

2021-02-11 Thread Lev Veyde

oVirt 4.4.5 Fifth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Fifth Release Candidate for testing, as of February 11th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.5 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.5 release highlights:
http://www.ovirt.org/release/4.4.5/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.5/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] async release for oVirt 4.4.4 is now available

2021-02-08 Thread Lev Veyde

On February 8th the oVirt project released an async update to the following
packages:

   -

   ovirt-release44-4.4.4.1
   -

   ovirt-node-ng-installer ISO 4.4.4.1 (4.4.4-2021020810)
   -

   imgbased-1.2.16


Fixing the following security issues:

   -

   [BZ 1917684 <https://bugzilla.redhat.com/show_bug.cgi?id=1917684>] -
   CVE-2021-3156 <https://access.redhat.com/security/cve/CVE-2021-3156>
   sudo: Heap buffer overflow in argument parsing
   -

   [RHSA-2021:0150 <https://access.redhat.com/errata/RHSA-2021:0150>] -
   Multiple vulnerabilities within dnsmasq


As well as, fixing the following bugs:

   -

   [BZ 1903777 <https://bugzilla.redhat.com/1903777>] - chronyd is disabled
   after upgrading RHV-H 4.4.2 -> 4.4.3
   -

   [BZ 1909782 <https://bugzilla.redhat.com/1909782>] - /etc/openvswitch
   permissions broken after upgrade
   -

   [BZ 1921553 <https://bugzilla.redhat.com/1921553>] - RHVH upgrade to the
   latest 4.4.4-1 build will fail due to FileNotFoundError


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WRMYQCKJAVVJRIFMMN7XXAK5LI5KOFDW/

[ovirt-users] [ANN] oVirt 4.4.5 Fourth Release Candidate is now available for testing

2021-02-05 Thread Lev Veyde

oVirt 4.4.5 Fourth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Fourth Release Candidate for testing, as of February 4th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.5 Node and Appliance on CentOS Linux.

Additional Resources:

* Read more about the oVirt 4.4.5 release highlights:
http://www.ovirt.org/release/4.4.5/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.5/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.5 First Release Candidate is now available for testing

2021-01-14 Thread Lev Veyde

oVirt 4.4.5 First Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
First Release Candidate for testing, as of January 14th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.5 release highlights:
http://www.ovirt.org/release/4.4.5/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.5/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.4 Sixth Release Candidate is now available for testing

2020-12-17 Thread Lev Veyde

oVirt 4.4.4 Sixth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.4
Sixth Release Candidate for testing, as of December 17th, 2020.

This update is the fourth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.4 release highlights:
http://www.ovirt.org/release/4.4.4/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.4/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.4 Fourth Release Candidate is now available for testing

2020-12-03 Thread Lev Veyde

oVirt 4.4.4 Fourth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.4
Fourth Release Candidate for testing, as of December 3rd, 2020.

This update is the fourth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.4 release highlights:
http://www.ovirt.org/release/4.4.4/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.4/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] oVirt 4.4.3 async is now generally available

2020-12-01 Thread Lev Veyde

The oVirt project just released an oVirt 4.4.3 async , as of December 1st,
2020.

This release fixes the following bugs:

1850939 Hosted engine deployment does not properly show iSCSI LUN errors

1895553 Add pre-flight in cockpit deployment flow to check for disk block
sizes used for bricks and LV cache to be identical

1895277 [DR] Remote data sync to the secondary site never completes

1895762 cockpit ovirt(downstream) docs links point to upstream docs

1835685 [Hosted-Engine] "Installation Guide" and "RHV Documents" didn't
jump to the correct pages in hosted engine page

1858248 Volume creation with 6 or more nodes in cluster, should allow users
to select the hosts for brick creation

1895356 Upgrade to 4.4.2 will fail due to dangling symlinks

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2XKKX2O763XKYUTHLDY5NON6ZUCE6Y3V/

[ovirt-users] [ANN] oVirt 4.4.4 Second Release Candidate is now available for testing

2020-11-19 Thread Lev Veyde

oVirt 4.4.4 Second Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.4
Second Release Candidate for testing, as of November 19th, 2020.

This update is the fourth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.4 release highlights:
http://www.ovirt.org/release/4.4.4/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.4/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.4 First Release Candidate is now available for testing

2020-11-12 Thread Lev Veyde

oVirt 4.4.4 First Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.4
First Release Candidate for testing, as of November 12th, 2020.

This update is the fourth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.4 release highlights:
http://www.ovirt.org/release/4.4.4/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.4/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 Eighth Release Candidate is now available for testing

2020-11-05 Thread Lev Veyde

oVirt 4.4.3 Eighth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Eighth Release Candidate for testing, as of November 5th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.

You can hit:

Problem: cannot install the best update candidate for package
ovirt-engine-metrics-1.4.1.1-1.el8.noarch

- nothing provides rhel-system-roles >= 1.0-19 needed by
ovirt-engine-metrics-1.4.2-1.el8.noarch

in order to get rhel-system-roles >= 1.0-19 you need
https://buildlogs.centos.org/centos/8/virt/x86_64/ovirt-44/ repo since that
package can be promoted to release only at 4.4.3 GA.

Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 Seventh Release Candidate is now available for testing

2020-10-29 Thread Lev Veyde

oVirt 4.4.3 Seventh Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Seventh Release Candidate for testing, as of October 29th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.

You can hit:

Problem: cannot install the best update candidate for package
ovirt-engine-metrics-1.4.1.1-1.el8.noarch

- nothing provides rhel-system-roles >= 1.0-19 needed by
ovirt-engine-metrics-1.4.2-1.el8.noarch

in order to get rhel-system-roles >= 1.0-19 you need
https://buildlogs.centos.org/centos/8/virt/x86_64/ovirt-44/ repo since that
package can be promoted to release only at 4.4.3 GA.

Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-19 Thread Lev Veyde

oVirt 4.4.3 Fifth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Fifth Release Candidate for testing, as of October 16th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 Fourth Release Candidate is now available for testing

2020-10-08 Thread Lev Veyde

oVirt 4.4.3 Fourth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Fourth Release Candidate for testing, as of October 8th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 Third Release Candidate is now available for testing

2020-10-01 Thread Lev Veyde

oVirt 4.4.3 Third Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Third Release Candidate for testing, as of October 1st, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 Second Release Candidate is now available for testing

2020-09-25 Thread Lev Veyde

oVirt 4.4.3 Second Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Second Release Candidate for testing, as of September 25th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.

Reboot.
3.

Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
4.

Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.

Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.

Reboot.

Documentation

If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-

For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-

For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-

For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

[ovirt-users] [ANN] oVirt 4.4.3 First Release Candidate is now available for testing

2020-09-17 Thread Lev Veyde

oVirt 4.4.3 First Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
First Release Candidate for testing, as of September 17th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG will be available soon for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/22PFKSPEDUBF76QDDGSUQDPUNSAGQKUO/

[ovirt-users] oVirt 4.4.2 is now generally available

2020-09-17 Thread Lev Veyde

The oVirt project is excited to announce the general availability of oVirt
4.4.2 , as of September 17th, 2020.

This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade

Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).

Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.

For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
)
Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download <https://ovirt.org/download/> page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation <https://ovirt.org/documentation/>.
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   <https://ovirt.org/documentation/upgrade_guide/>.
   -

   For a general overview of oVirt, see About oVirt
   <https://ovirt.org/community/about.html>.

What’s new in oVirt 4.4.2 Release?

This update is the second in a series of stabilization updates to the 4.4
series.

This release is available now on x86_64 architecture for:

   -

   Red Hat Enterprise Linux 8.2
   -

   CentOS Linux (or similar) 8.2
   -

   CentOS Stream (tech preview)


This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

   -

   Red Hat Enterprise Linux 8.2
   -

   CentOS Linux (or similar) 8.2
   -

   CentOS Stream (tech preview)


oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) will
be released separately due to a blocker issue (Bug 1837864
<https://bugzilla.redhat.com/show_bug.cgi?id=1837864>).

oVirt Node and Appliance have been updated, including:

   -

   oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/
   -

   Ansible 2.9.13:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-13

   -

   Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/



See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

   -

   oVirt Appliance is already available for CentOS Linux 8
   -

   oVirt Node NG will be available soon for CentOS Linux 8


Additional resources:

   -

   Read more about the oVirt 4.4.2 release highlights:
   http://www.ovirt.org/release/4.4.2/
   -

   Get more oVirt project updates on Twitter: https://twitter.com/ovirt
   -

   Check out the latest project news on the oVirt blog:
   http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RJPA24GLCBFTFNGQCWHH2IXQ5CNJF745/

[ovirt-users] Re: [ANN] oVirt 4.4.2 Fifth Release Candidate is now available for testing

2020-08-27 Thread Lev Veyde

Hi Gianluca,

As Didi already mentioned you can check the updates to the 4.4.2 release
notes history, if you want to see what changed specifically between i.e.
RC4 and RC5.

The specific commit is this one:
https://github.com/oVirt/ovirt-site/commit/f021f5d204712dff237c6beec664e498f1188341#diff-539ead6dd4f7c8834254b1ef4f854d15

Thanks in advance,

On Thu, Aug 27, 2020 at 12:41 PM Yedidyah Bar David  wrote:

> On Thu, Aug 27, 2020 at 12:33 PM Gianluca Cecchi
>  wrote:
> >
> >
> >
> > On Thu, Aug 27, 2020 at 11:06 AM Lev Veyde  wrote:
> >>
> >> oVirt 4.4.2 Fifth Release Candidate is now available for testing
> >>
> >>
> >> The oVirt Project is pleased to announce the availability of oVirt
> 4.4.2 Fifth Release Candidate for testing, as of August 27th, 2020.
> >>
> >>
> >> This update is the second in a series of stabilization updates to the
> 4.4 series.
> >>
> >>
> >>
> >
> > Hi Lev, thanks for this update.
> > Is there a tracking to understand the need of this 5thrc and so a
> tracking of things fixed/enhanced from rc4 (that I'm testing) and rc5, so
> that I can address only those specific things in further tests after
> installing rc5?
>
> You can see what Lev changed in the release notes page:
>
>
> https://github.com/oVirt/ovirt-site/commits/master/source/release/4.4.2/index.md
>
> This page is generated by a script, you can try reading/adapting it
> and query bugzilla/git yourself:
>
> https://github.com/oVirt/releng-tools/blob/master/release_notes_git.py
>
> Best regards,
> --
> Didi
>
>

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q3N4NTRHQM34WGUMABHM6FNKYA5ORWRU/

[ovirt-users] [ANN] oVirt 4.4.2 Fifth Release Candidate is now available for testing

2020-08-27 Thread Lev Veyde

oVirt 4.4.2 Fifth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.2
Fifth Release Candidate for testing, as of August 27th, 2020.

This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLLKJNX3KN4YPISJ6KFCMFW77I3DNBAE/

[ovirt-users] [ANN] oVirt 4.4.2 Fourth Release Candidate is now available for testing

2020-08-20 Thread Lev Veyde

oVirt 4.4.2 Fourth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.2
Fourth Release Candidate for testing, as of August 20th, 2020.

This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BXFM5M454S66VLEAUXY34BB2X7MRKBTP/

[ovirt-users] [ANN] oVirt 4.4.2 Third Release Candidate is now available for testing

2020-08-13 Thread Lev Veyde

oVirt 4.4.2 Third Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.2
Third Release Candidate for testing, as of August 13th, 2020.

This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WL3U4WFCPG6TLT2XETP4QWPE6GMHVSRP/

[ovirt-users] [ANN] oVirt 4.4.2 Second Release Candidate is now available for testing

2020-08-06 Thread Lev Veyde

oVirt 4.4.2 Second Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.2
Second Release Candidate for testing, as of August 6th, 2020.

This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 8.2 minimal from:

https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-minimal.iso

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- dnf module enable -y javapackages-tools pki-deps postgresql:12

- dnf install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8.2 from

https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-minimal.iso
; select minimal installation

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- Attach the host to the engine and let it be deployed.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GAYKPI6NOVZ6XRS75UYMY65JKZBGB4XG/

[ovirt-users] Subject: [ANN] Updated oVirt release 4.4.1.5

2020-08-05 Thread Lev Veyde

The oVirt Team has just released a new version of oVirt Node package that
fixes oVirt Hyperconverged deployment related issue:

Bug 1862588 <https://bugzilla.redhat.com/show_bug.cgi?id=1862588> - Update
to gluster-7.7 with ovirt-ng node 4.4.1

Updated ovirt-node-ng-installer had been built and a new torrent for this
ISO is now available at
https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.1-2020080418/el8/

Relevant changes compared to previous version:

   -

   Gluster 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/
   -

   Ansible 2.9.11:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-11
   -

   Boot Hole vulnerability in grub2 (CVE-2020-1073) fix:
   https://blog.centos.org/2020/08/centos-community-newsletter-august-2020-2008/


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BYQMHO2FCO4A4UMAHI4B72TUOSKYBBZO/

[ovirt-users] [ANN] oVirt 4.4.2 First Release Candidate is now available for testing

2020-07-30 Thread Lev Veyde

oVirt 4.4.2 First Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.2
First Release Candidate for testing, as of July 30h, 2020.

This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 8.2 minimal from:

https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-minimal.iso

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- dnf module enable -y javapackages-tools pki-deps postgresql:12

- dnf install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8.2 from

https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-minimal.iso
; select minimal installation

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- Attach the host to the engine and let it be deployed.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YPUKLEEKBKTIC7UA7YGL4QEYTLNSCVUS/

[ovirt-users] [ANN] Updated oVirt release 4.4.1.1

2020-07-13 Thread Lev Veyde

The oVirt Team has just released a new version of ovirt-ansible-engine-setup
(1.1.6) package that fixes oVirt Hyperconverged deployment related issue.[1]

Updated ovirt-node-ng-installer and ovirt-appliance have been built.
Also a new torrent for this new ovirt-node-ng-installer ISO is now
available.

https://bugzilla.redhat.com/show_bug.cgi?id=1855164
-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KW5B7BOAO2Y5JCLXVCLQWCRBAP474QXB/

[ovirt-users] [ANN] oVirt 4.4.1 is now generally available

2020-07-08 Thread Lev Veyde

oVirt 4.4.1 is now generally available

The oVirt project is excited to announce the general availability of oVirt
4.4.1 , as of July 8th, 2020.

This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade

Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).

Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.

For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
)
Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download <https://ovirt.org/download/> page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation <https://ovirt.org/documentation/>.
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   <https://ovirt.org/documentation/upgrade_guide/>.
   -

   For a general overview of oVirt, see About oVirt
   <https://ovirt.org/community/about.html>.

What’s new in oVirt 4.4.1 Release?

This update is the first in a series of stabilization updates to the 4.4
series.

This release introduces a new monitoring solution that provides a user
interface to oVirt DWH collected data using Grafana. This allows admins to
track inventory, monitor performance and capacity trends, and easily
identify and troubleshoot resources issues. Grafana is installed and
configured during engine-setup and includes pre-built dashboards that are
based on the data collected by the ovirt_engine_history PostgreSQL Data
Warehouse database (BZ#1777877
<https://bugzilla.redhat.com/show_bug.cgi?id=1777877>).

In oVirt 4.4.1 the maximum memory size for 64-bit x86_64 and ppc64/ppc64le
VMs is now 6TB. For x86_64 this limit is applied also to VMs in 4.2 and 4.3
Cluster Levels.

You can now use CentOS Stream as an alternative to CentOS Linux on
non-production systems.

This release is available now on x86_64 architecture for:

   -

   Red Hat Enterprise Linux 8.2
   -

   CentOS Linux (or similar) 8.2
   -

   CentOS Stream (tech preview)


This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

   -

   Red Hat Enterprise Linux 8.2
   -

   CentOS Linux (or similar) 8.2
   -

   CentOS Stream (tech preview)
   -

   oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)


oVirt Node and Appliance have been updated, including:

   -

   oVirt 4.4.1: http://www.ovirt.org/release/4.4.1/
   -

   CentOS Linux 8.2.2004:
   https://lists.centos.org/pipermail/centos-announce/2020-June/035756.html
   -

   CentOS Virt SIG updates including Advanced Virtualization 8.2 (qemu-kvm
   4.2 <https://www.qemu.org/2019/12/13/qemu-4-2-0/>, libvirt 6.0.0
   <https://libvirt.org/news.html#v6-0-0-2020-01-15>)
   -

   Wildfly 19.1.0:
   https://wildfly.org/news/2020/05/04/WildFly-1910-Released/
   -

   Ansible 2.9.10:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-10
   -

   Glusterfs 7.6: https://docs.gluster.org/en/latest/release-notes/7.6/



See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

   -

   oVirt Appliance is already available for CentOS Linux 8
   -

   oVirt Node NG is already available for CentOS Linux 8


Additional resources:

   -

   Read more about the oVirt 4.4.1 release highlights:
   http://www.ovirt.org/release/4.4.1/
   -

   Get more oVirt project updates on Twitter: https://twitter.com/ovirt
   -

   Check out the latest project news on the oVirt blog:
   http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.1/

[2] http://resources.ovirt.org/pub/ovirt-4.4/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FB3WEFVK2XFK7WAWAN75DQBD4BXERU7O/

[ovirt-users] Re: VMs shutdown mysteriously

2020-06-29 Thread Lev Veyde

Hi Bobby,

Can you please share the engine logs as well?
It could help to understand what happened there.

Right now, looking at the pieces of the logs you sent I couldn't spot
anything unusual.

Thanks in advance,

On Mon, Jun 29, 2020 at 10:40 PM Bobby  wrote:

> Hello,
>
> All 4 VMs on one of my oVirt cluster node shutdown for an unknown reason
> almost simultaneously.
> Please help me to find the root cause.
> Thanks.
>
> Please note the host seems doing fine and never crash or hangs and I can
> migrate VMs back to it later.
> Here is the exact timeline of all the related events combined from the
> host and the VM(s):
>
> On oVirt host:
> /var/log/vdsm/vdsm.log:
> 2020-06-25 15:25:16,944-0500 WARN  (qgapoller/3)
> [virt.periodic.VmDispatcher] could not run  at
> 0x7f4ed2f9f5f0> on ['e0257b06-28fd-4d41-83a9-adf1904d3622'] (periodic:289)
> 2020-06-25 15:25:19,203-0500 WARN  (libvirt/events) [root] File:
> /var/lib/libvirt/qemu/channels/e0257b06-28fd-4d41-83a9-adf1904d3622.ovirt-guest-agent.0
> already removed (fileutils:54)
> 2020-06-25 15:25:19,203-0500 WARN  (libvirt/events) [root] File:
> /var/lib/libvirt/qemu/channels/e0257b06-28fd-4d41-83a9-adf1904d3622.org.qemu.guest_agent.0
> already removed (fileutils:54)
>
> [root@athos log]# journalctl -u NetworkManager --since=today
> -- Logs begin at Wed 2020-05-20 22:07:33 CDT, end at Thu 2020-06-25
> 16:36:05 CDT. --
> Jun 25 15:25:18 athos NetworkManager[1600]:   [1593116718.1136]
> device (vnet0): state change: disconnected -> unmanaged (reason
> 'unmanaged', sys-iface-state: 'removed')
> Jun 25 15:25:18 athos NetworkManager[1600]:   [1593116718.1146]
> device (vnet0): released from master device SRV-VL
>
> /var/log/messages:
> Jun 25 15:25:18 athos kernel: SRV-VL: port 2(vnet0) entered disabled state
> Jun 25 15:25:18 athos NetworkManager[1600]:   [1593116718.1136]
> device (vnet0): state change: disconnected -> unmanaged (reason
> 'unmanaged', sys-iface-state: 'removed')
> Jun 25 15:25:18 athos NetworkManager[1600]:   [1593116718.1146]
> device (vnet0): released from master device SRV-VL
> Jun 25 15:25:18 athos libvirtd: 2020-06-25 20:25:18.122+: 2713: error
> : qemuMonitorIO:718 : internal error: End of file from qemu monitor
>
> /var/log/libvirt/qemu/aries.log:
> 2020-06-25T20:25:28.353975Z qemu-kvm: terminating on signal 15 from pid
> 2713 (/usr/sbin/libvirtd)
> 2020-06-25 20:25:28.584+: shutting down, reason=shutdown
>
>
> =
> On the first VM effected (same thing on others):
> /var/log/ovirt-guest-agent/ovirt-guest-agent.log:
> MainThread::INFO::2020-06-25
> 15:25:20,270::ovirt-guest-agent::104::root::Stopping oVirt guest agent
> CredServer::INFO::2020-06-25
> 15:25:20,626::CredServer::262::root::CredServer has stopped.
> MainThread::INFO::2020-06-25
> 15:25:21,150::ovirt-guest-agent::78::root::oVirt guest agent is down.
>
>
> =
> Packages version installated:
> Host OS version: CentOS 7.7.1908:
> ovirt-hosted-engine-ha-2.3.5-1.el7.noarch
> ovirt-provider-ovn-driver-1.2.22-1.el7.noarch
> ovirt-release43-4.3.6-1.el7.noarch
> ovirt-imageio-daemon-1.5.2-0.el7.noarch
> ovirt-vmconsole-1.0.7-2.el7.noarch
> ovirt-imageio-common-1.5.2-0.el7.x86_64
> ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
> ovirt-vmconsole-host-1.0.7-2.el7.noarch
> ovirt-host-4.3.4-1.el7.x86_64
> libvirt-4.5.0-23.el7_7.1.x86_64
> libvirt-daemon-4.5.0-23.el7_7.1.x86_6
> qemu-kvm-ev-2.12.0-33.1.el7.x86_64
> qemu-kvm-common-ev-2.12.0-33.1.el7.x86_64
>
> On guest VM:
> ovirt-guest-agent-1.0.13-1.el6.noarch
> qemu-guest-agent-0.12.1.2-2.491.el6_8.3.x86_64
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LGQSLTNG37VZDJM2GYXRVHPSLWOLOKSC/
>


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EJA44VI5GHUDEBCK4DWBXWIQMRIPIAPU/

[ovirt-users] [ANN] oVirt 4.4.1 Third Release Candidate is now available for testing

2020-06-04 Thread Lev Veyde

oVirt 4.4.1 Third Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.1
Third Release Candidate for testing, as of June 4th, 2020.

This update is the first in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.

Some of the features included in oVirt 4.4.1 Release Candidate require
content that will be available in CentOS Linux 8.2 but can’t be tested on
RHEL 8.2 yet due to some incompatibility in openvswitch package shipped in
CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2.
Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 8 minimal from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- dnf module enable -y javapackages-tools pki-deps postgresql:12

- dnf install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8 from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso
; select minimal installation

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- Attach the host to engine and let it be deployed.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.1 or newer

* CentOS Linux (or similar) 8.1 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.1 or newer

* CentOS Linux (or similar) 8.1 or newer

* oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.1 release highlights:
http://www.ovirt.org/release/4.4.1/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.1/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
[image: image.png]
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WF5H4LTUNXTY4JK4L5N7MNBXVTPNBOWS/

[ovirt-users] [ANN] oVirt 4.3.10 is now generally available

2020-06-03 Thread Lev Veyde

The oVirt Project is pleased to announce the general availability of oVirt
4.3.10 as of June 3rd, 2020.



This update is the tenth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.8 or later (but < 8)

* CentOS Linux (or similar) 7.8 or later (but < 8)



This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 7.8 or later (but < 8)

* CentOS Linux (or similar) 7.8 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.



Notes:

- oVirt Appliance will be available soon

- oVirt Node is already available[2]

oVirt Node and Appliance have been updated including:

- oVirt 4.3.10: http://www.ovirt.org/release/4.3.10/

- Latest CentOS 7.8 updates

- latest CentOS Virt, OpsTools and Storage SIG updates

Additional Resources:

* Read more about the oVirt 4.3.10 release highlights:
http://www.ovirt.org/release/4.3.10/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/



[1] http://www.ovirt.org/release/4.3.10/

[2] http://resources.ovirt.org/pub/ovirt-4.3/iso/


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XKYRNKUUVGRG3H3QLIS5BCLEFCR4SOOG/

[ovirt-users] [ANN] oVirt 4.4.1 First Release Candidate is now available for testing

2020-05-25 Thread Lev Veyde

oVirt 4.4.1 First Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.1
First Release Candidate for testing, as of May 25th, 2020.

This update is the first in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.

Some of the features included in oVirt 4.4.1 Release Candidate require
content that will be available in CentOS Linux 8.2 but can’t be tested on
RHEL 8.2 beta yet due to some incompatibility in openvswitch package
shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of
CentOS 8.2.
Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 8 minimal from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- dnf module enable -y javapackages-tools pki-deps postgresql:12

- dnf install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8 from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso
; select minimal installation

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- Attach the host to engine and let it be deployed.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.1 or newer

* CentOS Linux (or similar) 8.1 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.1 or newer

* CentOS Linux (or similar) 8.1 or newer

* oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

If you manage more than one oVirt instance, OKD or RDO we also recommend to
try ManageIQ <http://manageiq.org/>.

In such a case, please be sure  to take the qc2 image and not the ova image.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.1 release highlights:
http://www.ovirt.org/release/4.4.1/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.1/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PXN5LOQ4B5IZMQQJY6TME5OO4YUIAH7V/

[ovirt-users] [ANN] oVirt 4.3.10 Fifth Release Candidate is now available for testing

2020-05-22 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of oVirt 4.3.10
Fifth Release Candidate for testing as of May 22nd, 2020.

This update is the tenth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


Additional Resources:

* Read more about the oVirt 4.3.10 release highlights:
http://www.ovirt.org/release/4.3.10/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/



[1] http://www.ovirt.org/release/4.3.10/

[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/O4D3FBGS4P3T47PGWXEWVGY7IQIXD5P6/

[ovirt-users] [ANN] oVirt 4.4.0 Second Release Candidate is now available for testing

2020-05-15 Thread Lev Veyde

oVirt 4.4.0 Second Release Candidate is now available for testing

The oVirt Project is excited to announce the availability of oVirt 4.4.0
Second Release Candidate for testing, as of May 15th, 2020

This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics on top of oVirt 4.3.

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not to be used in production.

Some of the features included in oVirt 4.4.0 Release Candidate require
content that will be available in CentOS Linux 8.2 but can’t be tested on
RHEL 8.2 beta yet due to some incompatibility in openvswitch package
shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of
CentOS 8.2.
Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 8 minimal from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- dnf module enable -y javapackages-tools pki-deps postgresql:12 389-ds

- dnf install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8 from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso
; select minimal installation

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- Attach the host to engine and let it be deployed.

What’s new in oVirt 4.4.0?

   -

   Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8),
   for both oVirt Node and standalone CentOS Linux hosts
   -

   Easier network management and configuration flexibility with
   NetworkManager
   -

   VMs based on a more modern Q35 chipset with legacy seabios and UEFI
   firmware
   -

   Support for direct passthrough of local host disks to VMs
   -

   Live migration improvements for High Performance guests.
   -

   New Windows Guest tools installer based on WiX framework now moved to
   VirtioWin project
   -

   Dropped support for cluster level prior to 4.2
   -

   Dropped SDK3 support
   -

   4K disks support
   -

   Exporting a VM to a data domain
   -

   Editing of floating disks
   -

   Integrating ansible-runner into engine, which allows a more detailed
   monitoring of playbooks executed from engine
   -

   Adding/reinstalling hosts are now completely based on Ansible
   -

   The OpenStack Neutron Agent cannot be configured by oVirt anymore, it
   should be configured by TripleO instead


This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.1 or newer

* CentOS Linux (or similar) 8.1 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.1 or newer

* CentOS Linux (or similar) 8.1 or newer

* oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

If you manage more than one oVirt instance, OKD or RDO we also recommend to
try ManageIQ <http://manageiq.org/>.

In such a case, please be sure  to take the qc2 image and not the ova image.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.0 release highlights:
http://www.ovirt.org/release/4.4.0/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.0/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MZ7Z4W33KQMTH563IT62GH7TMHSCDTY2/

[ovirt-users] [ANN] oVirt 4.3.10 Fourth Release Candidate is now available for testing

2020-05-14 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of oVirt 4.3.10
Fourth Release Candidate for testing as of May 14th, 2020.

This update is the tenth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


Additional Resources:

* Read more about the oVirt 4.3.10 release highlights:
http://www.ovirt.org/release/4.3.10/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/



[1] http://www.ovirt.org/release/4.3.10/

[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LXEQMORFHUMJ3UUQQLPJTYX5EXSMRXCW/

[ovirt-users] Re: Can't add freshly installed node.. host has no default route

2020-05-12 Thread Lev Veyde

   found some
> >  > > bug.. this is the first time i had so many troubles
> > adding a
> >  > new host..
> >  > > so I decided to share my experience with the list..
> >  > >
> >  > >
> >  > > Thanks for raising this.
> >  > >
> >  > > On adding the host there is an error about
> > vdsm-hook-nestedvt which I
> >  > > cannot interprete, maybe someone else can do.
> >  > > In vdsm.log I noticed a strange behavior of setupNetworks,
> > can you
> >  > > please share the corresponding supervdsm.log, too?
> >  > >
> >  > >
> >  > >
> >  > > Cheers
> >  > > --
> >  > > gb
> >  > >
> >  > > PGP Key: http://pgp.mit.edu/
> >  > > Primary key fingerprint: C510 0765 943E EBED A4F2 69D3
> > 16CC DC90
> >  > > B9CB 0F34
> >  > > ___
> >  > > Users mailing list -- users@ovirt.org
> > <mailto:users@ovirt.org> <mailto:users@ovirt.org
> > <mailto:users@ovirt.org>>
> >  > <mailto:users@ovirt.org <mailto:users@ovirt.org>
> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>
> >  > > To unsubscribe send an email to users-le...@ovirt.org
> > <mailto:users-le...@ovirt.org>
> >  > <mailto:users-le...@ovirt.org <mailto:users-le...@ovirt.org>>
> >  > > <mailto:users-le...@ovirt.org
> > <mailto:users-le...@ovirt.org> <mailto:users-le...@ovirt.org
> > <mailto:users-le...@ovirt.org>>>
> >  > > Privacy Statement:
> > https://www.ovirt.org/privacy-policy.html
> >  > > oVirt Code of Conduct:
> >  > > https://www.ovirt.org/community/about/community-guidelines/
> >  > > List Archives:
> >  > >
> >  >
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6JTU3HB4WCI27WSLGEOSLMPYFU22EX5H/
> >  > >
> >  > Hi,
> >  > I don't think that the missing vdsm-hook-nestedvt is a
> > problem, in our
> >  > environment we have one engine but multiple clusters and that
> > hook is
> >  > only needed on one cluster to enable nested virtualization.
> >  >
> >  > See attachment for supervdsm.log.
> >  >
> >  >
> >  > Thanks, network config flows looked fine.
> >  >
> >  > Maybe
> >  > https://bugzilla.redhat.com/1794485
> >  > is the root for this issue?
> >  >
> >  >
> >  > Regards
> >  > --
> >  > gb
> >  >
> >  > PGP Key: http://pgp.mit.edu/
> >  > Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC
> DC90
> >  > B9CB 0F34
> >  >
> >
> > I removed the file
> >
>  
> /usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/vdsmhooks/packages.d/vdsm-hook-nestedvt.centos
> > from the engine host ( the content of the file was
> "vdsm-hook-nestedvt"
> > ) and reinstalled another host and now the installation works
> correctly.
> >
> >
> > This is a great hint. Do you have an idea where this file comes from?
>
> Yes, it was a change made by another member of our staff to automate the
> installation of that hook.. as far as I know this is the correct way to
> add additional packages during the host installation, but I still have
> no idea why the required package can not be found, even via yum install
> as I wrote before.
>
> So now the real question is: why can't I install vdsm-hook-nestedvt via
> yum?
>
> And even if it's now clear that this is the reason why the installation
> process fails I wasn't expecting such a big failure.. the hook itself
> it's not strictly necessary to have a working host.. I was expecting a
> warning more than a fail..
>
> But at least I'm glad I've found the cause of the failure
>
> >
> > So the problem is that during the host installation
> vdsm-hook-nestedvt
> > cannot be found/downloaded from the repos and this, somehow, breaks
> the
> > installation process, the certificate enrollment and so on..
> >
> > As a matter of fact if I try:
> >
> > [root@cn127 ~]# yum install vdsm-hook-nestedvt
> > Loaded plugins: enabled_repos_upload, fastestmirror,
> imgbased-persist,
> > package_upload, product-id,
> >: search-disabled-repos, subscription-manager,
> > vdsmupgrade, versionlock
> > This system is not registered with an entitlement server. You can use
> > subscription-manager to register.
> > Loading mirror speeds from cached hostfile
> >   * ovirt-4.3-epel: epel.mirror.far.fi <http://epel.mirror.far.fi>
> > No package vdsm-hook-nestedvt available.
> > Error: Nothing to do
> > Uploading Enabled Repositories Report
> > Cannot upload enabled repos report, is this client registered?
> >
> > Thanks for the support.
> >
> > --
> > gb
> >
> > PGP Key: http://pgp.mit.edu/
> > Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90
> > B9CB 0F34
> >
>
> --
> gb
>
> PGP Key: http://pgp.mit.edu/
> Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
>
>

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JGC5WRSC56XJH3RLGRLKMM4627VEDUVR/

[ovirt-users] [ANN] oVirt 4.3.10 Third Release Candidate is now available for testing

2020-05-07 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of oVirt 4.3.10
Third Release Candidate for testing as of May 6th, 2020.

This update is the tenth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


Additional Resources:

* Read more about the oVirt 4.3.10 release highlights:
http://www.ovirt.org/release/4.3.10/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/



[1] http://www.ovirt.org/release/4.3.10/

[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/


-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PX72TIQQQ2TG6CXG6GWMLKTJ2PW5U2UJ/

[ovirt-users] [ANN] oVirt 4.3.10 Second Release Candidate is now available for testing

2020-04-28 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of oVirt 4.3.10
Second Release Candidate for testing as of April 28th, 2020.



This update is the tenth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


Additional Resources:

* Read more about the oVirt 4.3.10 release highlights:
http://www.ovirt.org/release/4.3.10/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/



[1] http://www.ovirt.org/release/4.3.10/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4A6CT52MMBAYUJ7M3VY73E5UWK5BTEJY/

[ovirt-users] [ANN] oVirt 4.3.10 First Release Candidate is now available for testing

2020-04-24 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of oVirt 4.3.10
First Release Candidate for testing as of April 25th, 2020.



This update is the tenth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


Additional Resources:

* Read more about the oVirt 4.3.10 release highlights:
http://www.ovirt.org/release/4.3.10/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/



[1] http://www.ovirt.org/release/4.3.10/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/L6LJTTFL2BIW6VVNJGZX5OHX4G2PF7G7/

[ovirt-users] [ANN] oVirt 4.3.9 Fourth Release Candidate is now available for testing

2020-03-11 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.3.9 Fourth Release Candidate for testing, as of March 11th, 2020.

This update is a release candidate of the ninth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only) has been built consuming
CentOS 7.7 Release

See the release notes [1] for known issues, new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available

Additional Resources:
* Read more about the oVirt 4.3.9 release highlights:
http://www.ovirt.org/release/4.3.9/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.3.9/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BO7X2WXVMKE6AZXWXICSPJBC7NYAYB74/

[ovirt-users] [ANN] oVirt 4.3.9 Third Release Candidate is now available for testing

2020-03-05 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.3.9 Third Release Candidate for testing, as of March 5th, 2020.

This update is a release candidate of the ninth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only) has been built consuming
CentOS 7.7 Release

See the release notes [1] for known issues, new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available

Additional Resources:
* Read more about the oVirt 4.3.9 release highlights:
http://www.ovirt.org/release/4.3.9/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.3.9/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RAU7ZN6RN7SKXSQIIEDNWCKEVM5KLRTZ/

[ovirt-users] [ANN] oVirt 4.3.9 Second Release Candidate is now available for testing

2020-02-20 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.3.9 Second Release Candidate for testing, as of February 20th, 2020.

This update is a release candidate of the ninth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only) has been built consuming
CentOS 7.7 Release

See the release notes [1] for known issues, new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available

Additional Resources:
* Read more about the oVirt 4.3.9 release highlights:
http://www.ovirt.org/release/4.3.9/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.3.9/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VTDIH744COLJ2LHXCTCZUAT4QGMUSFG6/

[ovirt-users] [ANN] oVirt 4.3.8 Third Release Candidate is now available for testing

2020-01-08 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.3.8 Third Release Candidate for testing, as of January 8th, 2020.

This update is a release candidate of the eighth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only) has been built consuming
CentOS 7.7 Release

See the release notes [1] for known issues, new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available

Additional Resources:
* Read more about the oVirt 4.3.8 release highlights:
http://www.ovirt.org/release/4.3.8/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.3.8/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/AD3F7XGNLOBJFEV3KONUTGJGOU52WZUJ/

[ovirt-users] [ovirt-announce] [ANN] oVirt 4.3.8 Second Release Candidate is now available for testing

2019-12-11 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.3.8 Second Release Candidate for testing, as of December 11th, 2019.

This update is a release candidate of the eighth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only) has been built consuming
CentOS 7.7 Release

See the release notes [1] for known issues, new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available

Additional Resources:
* Read more about the oVirt 4.3.8 release highlights:
http://www.ovirt.org/release/4.3.8/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.3.8/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DXQ6SU6NETGVYZIJSBDGJST4TVM3XN27/

[ovirt-users] Re: Windows Sluggish Performance

2019-12-03 Thread Lev Veyde

Hi Vijay,

Have you tried to run something in the VM?
I want to understand if the performance of the VM is slow, or just the
console access seems to be slow.

Thanks in advance,

On Tue, Dec 3, 2019 at 9:31 PM Vijay Sachdeva 
wrote:

> Anyone?
>
> On Tue, 3 Dec 2019 at 11:21 PM, Vijay Sachdeva 
> wrote:
>
>> Hello Everyone,
>>
>> I managed to install Windows Server 2016 server on Ovirt node using ovirt
>> engine.All virtio-Win drivers also installed, but the performance of
>> Windows using console is very sluggish and mouse pointer is not at all
>> responsive.
>>
>> Can anyone let me know, what could be the reason. Not able to to even add
>> IP to VM as mouse doesn’t work at all.
>>
>> Thanks
>>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/GG2L2K3QDGURBZ37HPQAEF64BSUTTWCN/
>

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GMDAPSUJG5D7FD7R6BQA3DDPGWCZVJRC/

[ovirt-users] Re: Windows VirtIO drivers

2019-12-03 Thread Lev Veyde

Hi Vijay,

Have you tried to load them from the VirtIO-Win ISO ?

Thanks in advance,

On Tue, Dec 3, 2019 at 3:30 PM Vijay Sachdeva 
wrote:

> Hi Gal,
>
>
>
> I have downloaded the virtio-win_x86.vfd  and uploaded to ISO domain. Used
> Run Once and attached the floppy drive, while looking for drivers in A
> drive it gives below error:
>
>
>
>
>
> I followed all the steps as per the guidelines shared in the document.
> Don’t know what I am missing.
>
>
>
> Thanks
>
>
>
> Vijay Sachdeva
>
>
>
>
>
> *From: *Gal Zaidman 
> *Date: *Tuesday, 3 December 2019 at 6:44 PM
> *To: *Vijay Sachdeva , 
> *Subject: *Re: [ovirt-users] Windows VirtIO drivers
>
>
>
> Going back to the user list, just in case it will be relevant to others
>
>
>
> On Tue, Dec 3, 2019 at 3:02 PM Vijay Sachdeva 
> wrote:
>
> Hi Gal,
>
>
>
> Thank you so much for replying, can you please a steps to do that. Right
> now what I am doing is:
>
>
>
>1. Installed Windows 2016 using IDE interface, but performance is very
>bad and it’ really hard to install any further .exe into it.
>
>
>
> I never used the IDE interface so I can't say from personal experience,
> but I don't think that should be the behavior, please open a bug on that so
> that we can examin.
>
>
>
>
>1.
>2. Other option I see attaching the floppy drive when we use “Run
>Once”, but problem is when pointing to floppy drive while loading drivers.
>It says no drivers detected.
>
>
>
> Using Run Once is the preferred option, see
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/chap-installing_windows_virtual_machines
>
> Make sure that you attach the latest virtio-win vdf (the link I sent
> earlier should be ok) and select the relevant drivers, if there is a
> problem then please open a bug on virtio-win project and send me the url so
> I will track it, thanks.
>
>
>
>
>
> Please share let me know the best way to perform this action as need to
> deliver the Ovirt infra to one of my customer and really stuck on this
> driver installation.
>
>
>
> Appreciate your quick response.!!
>
>
>
> Vijay Sachdeva
>
>
>
>
>
> *From: *Gal Zaidman 
> *Date: *Tuesday, 3 December 2019 at 6:22 PM
> *To: *Vijay Sachdeva 
> *Subject: *Re: [ovirt-users] Windows VirtIO drivers
>
>
>
> HI Vijay,
>
>
>
> There a package on fedora:
>
> virtio-win-0.1.173-2
>
> which contains an MSI installer for the drivers and the ovirt agent (which
> is disabled on a normal installation, so please enable it when you install).
>
>
>
> This installer should replace the ovirt-wgt that we have currently on the
> next versions,
>
> and it is new, so please give us feedback once you used it.
>
>
>
> P.S
>
> the installer installs the drivers normally so if the regular drivers from
> virtio-win fail to install, then using the installer will not change much
> probably, and it means that you have a deeper problem.
>
> In case the installation fails then please generate logs but running the
> installer through cmd.exe "msiexec /i {installer} /l*v {path to log}" (
> https://www.advancedinstaller.com/user-guide/qa-log.html)
>
> and open a bug/reply here and I will try and help
>
>
>
> Thanks
>
>
>
> On Tue, Dec 3, 2019 at 2:11 PM Vijay Sachdeva 
> wrote:
>
> Dear Team,
>
>
>
> How can we install virtIO windows drivers to Windows 2016. As of now I
> tried to attach floppy drive with virtio-win.vfd image but while installing
> drivers didn’t get loaded.
>
>
>
> Please guide or let me know the proper way to install drivers.
>
>
>
>
>
> Vijay Sachdeva
>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/5XBYY54K62BYJGVDLJOQNEMKT6GIAZE7/
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/2K4WHKA6I4BVNHYM24INGVBEH63R5OOU/
>


-- 

Lev Veyde

Seni

[ovirt-users] Re: Windows Server 2019: Driver Signature Enforcement

2019-06-13 Thread Lev Veyde

Hi,

I think that it's expected behaviour.

In secure mode only WHQL'd drivers are allowed to be loaded into the OS
kernel, and while RHEV/RHV provides WHQL'd drivers, oVirt users receive RH
signed ones, which from the OS standpoint are basically not certified.

Thanks in advance,

On Thu, Jun 13, 2019 at 1:12 PM Yedidyah Bar David  wrote:

> On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <
> fer...@versatushpc.com.br> wrote:
>
>> RHV drivers works.
>> oVirt drivers does not.
>>
>> Checked this now.
>>
>> I’m not sure if this is intended or not. But oVirt drivers aren’t signed
>> for Windows.
>>
>
> oVirt's drivers are simply copied from virtio-win repositories.
>
> Adding Vadim from virtio-win team.
>
> Best regards,
>
>
>>
>> > On 29 May 2019, at 21:41, mich...@wanderingmad.com wrote:
>> >
>> > I'm running server 2012R2, 2016, and 2019 with no issue using the
>> Redhat signed drivers from RHEV.
>> > ___
>> > Users mailing list -- users@ovirt.org
>> > To unsubscribe send an email to users-le...@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/GBQEMLOW5DCSW7XSLNZKNX532BQHRFUB/
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/PNZWHYEWW23N4GQKHMJ2RUSQR363NSYH/
>>
>
>
> --
> Didi
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/OIBSOZEBGSF65JEVMNMPOCAB6ICTVKIU/
>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GNOKAGJHYUYUYH4SOGYBI26C2OOP23WW/

[ovirt-users] Re: Creating a static route

2019-02-20 Thread Lev Veyde

Hi Edward,

Thanks for your feedback on the issue.

I still think that we do need to to add a note to the documentation, so
that customers/integrators who want to add custom static routes will be
aware of the issue.
As previously discussed we should note of course, that this feature is
currently not officially supported, and adding the routes manually is a
workaround.

Thanks in advance,

On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:

> As mentioned in this thread oVirt currently does not support customized
> routes.
> It supports only a host level default route and per network gateways
> (default route per network).
>
> If someone understands well the Linux network details, workarounds may be
> applied to overcome oVirt limitations.
> With that said, as oVirt manages the host network details, the community
> and future development cannot take into account such workarounds.
>
> To solve this problem correctly, oVirt needs to support customize routes.
> From my perspective, this workaround should not be formally documented.
>
> Thanks,
> Edy.
>
> On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:
>
>> Hi Doug,
>>
>> Thanks for the update, I'm glad that we could help and everything
>> worked out just fine!
>>
>> I also opened a BZ, asking to add a note in the documentation regarding
>> this issue.
>>
>> Thanks in advance,
>>
>> On Mon, Feb 18, 2019 at 7:15 PM Doug Maxfield 
>> wrote:
>>
>>> Lev,
>>>
>>> Just wanted to update you on the progress.  We created the persistent
>>> static routes and rules and the data is routing correctly over the required
>>> gateway.
>>>
>>>
>>>
>>> Thank you for all of your help!!!
>>>
>>>
>>>
>>> [image: Count On EMC] <http://www.emcins.com/>
>>>
>>> *Doug Maxfield *| Senior Operating Systems Analyst
>>>
>>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>>> Tel: 515.345.4507 | Fax: 866.331.1522
>>> doug.l.maxfi...@emcins.com | www.emcins.com
>>>
>>>
>>>
>>>
>>>
>>> *From:* Lev Veyde 
>>> *Sent:* Thursday, February 14, 2019 9:14 AM
>>> *To:* Doug Maxfield 
>>> *Cc:* users 
>>> *Subject:* Re: [ovirt-users] Creating a static route
>>>
>>>
>>>
>>> Hi Doug,
>>>
>>> Just one more thing that I forgot to mention, even though it may be
>>> obvious - you can use subnets in both rules and routes.
>>>
>>> So if all the IPs you want to route sit in the same subnet then you can
>>> contain them with a single command e.g. "to 172.22.20.0/24 priority
>>> 32764"
>>>
>>> Thanks in advance,
>>>
>>>
>>>
>>> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>>>
>>> Hi Doug,
>>>
>>> Sure, np.
>>>
>>>
>>>
>>> >> 1. - yes it is the priority setting of the specific rule. Basically
>>> you put in the file the post "ip rule add" part of the command e.g. for "ip
>>> rule add to 172.22.20.31 priority 32764" you need to put a line of "to
>>> 172.22.20.31 priority 32764"
>>>
>>> >> 2. - yes, the same priority can be used for all of them. E.g. if you
>>> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
>>> add:
>>>
>>> to 172.22.20.31 priority 32764
>>> to 172.22.34.56 priority 32764
>>> to 172.22.67.89 priority 32764
>>>
>>> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>>>
>>>
>>>
>>> Please note that you will also need to add the static route for each one
>>> of these as well w/ "ip route add ... " command e.g. "ip route add
>>> 172.22.20.31 via 172.21.12.61".
>>>
>>> You can also use the route- putting just the route info
>>> part, similar to the "ip rule" e.g. for equivalent of "ip route add
>>> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
>>> content "172.22.20.31 via 172.21.12.61".
>>>
>>> For routes it's important to use specifically the route-ovirtmgmt file
>>> since the script automatically adds the device to the route command i.e.
>>> you can put the following lines into your route-ovirtmgmt file:
>>>
>>> 172.22.20.31 via 172.21.12.61
>>> 172.22.34.56 via 172.21.12.61
>>> 172.22.67.89 via 172.21.12.68
>>>

[ovirt-users] Re: Creating a static route

2019-02-18 Thread Lev Veyde

Hi Doug,

Thanks for the update, I'm glad that we could help and everything
worked out just fine!

I also opened a BZ, asking to add a note in the documentation regarding
this issue.

Thanks in advance,

On Mon, Feb 18, 2019 at 7:15 PM Doug Maxfield 
wrote:

> Lev,
>
> Just wanted to update you on the progress.  We created the persistent
> static routes and rules and the data is routing correctly over the required
> gateway.
>
>
>
> Thank you for all of your help!!!
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Thursday, February 14, 2019 9:14 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Just one more thing that I forgot to mention, even though it may be
> obvious - you can use subnets in both rules and routes.
>
> So if all the IPs you want to route sit in the same subnet then you can
> contain them with a single command e.g. "to 172.22.20.0/24 priority 32764"
>
> Thanks in advance,
>
>
>
> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>
> Hi Doug,
>
> Sure, np.
>
>
>
> >> 1. - yes it is the priority setting of the specific rule. Basically you
> put in the file the post "ip rule add" part of the command e.g. for "ip
> rule add to 172.22.20.31 priority 32764" you need to put a line of "to
> 172.22.20.31 priority 32764"
>
> >> 2. - yes, the same priority can be used for all of them. E.g. if you
> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
> add:
>
> to 172.22.20.31 priority 32764
> to 172.22.34.56 priority 32764
> to 172.22.67.89 priority 32764
>
> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>
>
>
> Please note that you will also need to add the static route for each one
> of these as well w/ "ip route add ... " command e.g. "ip route add
> 172.22.20.31 via 172.21.12.61".
>
> You can also use the route- putting just the route info
> part, similar to the "ip rule" e.g. for equivalent of "ip route add
> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
> content "172.22.20.31 via 172.21.12.61".
>
> For routes it's important to use specifically the route-ovirtmgmt file
> since the script automatically adds the device to the route command i.e.
> you can put the following lines into your route-ovirtmgmt file:
>
> 172.22.20.31 via 172.21.12.61
> 172.22.34.56 via 172.21.12.61
> 172.22.67.89 via 172.21.12.68
>
> (In case the first 2 of the mentioned IPs should be routed through the
> 172.21.12.61 gateway, and the last one should be routed through the
> 172.21.12.68 gateway).
>
>
>
> For the reference you can take a look at the
> /etc/sysconfig/network-scripts/ifup-routes script.
> It does the actual processing of both "route" and "rule" files for all
> network interfaces on a system.
>
>
>
> Please feel free to contact if you have further questions.
>
>
>
> Thanks in advance,
>
>
>
> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Thanks for the response.  I was just getting ready to contact you about
> this.  I do have 2 follow-up questions, if you don’t mind.
>
>
>
>1. When we were talking about creating the route that would be enabled
>again after a reboot, you said to modify “the
>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt or
>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>priority 32764 for the ip rule command?
>2. If I have multiple IPs that I would need to create a static route,
>would the priority be 32764 for all of them?
>
>
>
> Once again, thank you for all of your help with this!!
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Thursday, February 14, 2019 3:19 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Sorry that it took a bit of time to get back to you.
> Managed to catch today somebody from the oVirt

[ovirt-users] Re: Creating a static route

2019-02-14 Thread Lev Veyde

Hi Doug,

Just one more thing that I forgot to mention, even though it may be obvious
- you can use subnets in both rules and routes.
So if all the IPs you want to route sit in the same subnet then you can
contain them with a single command e.g. "to 172.22.20.0/24 priority 32764"

Thanks in advance,

On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:

> Hi Doug,
>
> Sure, np.
>
> >> 1. - yes it is the priority setting of the specific rule. Basically you
> put in the file the post "ip rule add" part of the command e.g. for "ip
> rule add to 172.22.20.31 priority 32764" you need to put a line of "to
> 172.22.20.31 priority 32764"
>
> >> 2. - yes, the same priority can be used for all of them. E.g. if you
> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
> add:
>
> to 172.22.20.31 priority 32764
> to 172.22.34.56 priority 32764
> to 172.22.67.89 priority 32764
>
> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>
> Please note that you will also need to add the static route for each one
> of these as well w/ "ip route add ... " command e.g. "ip route add
> 172.22.20.31 via 172.21.12.61".
>
> You can also use the route- putting just the route info
> part, similar to the "ip rule" e.g. for equivalent of "ip route add
> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
> content "172.22.20.31 via 172.21.12.61".
> For routes it's important to use specifically the route-ovirtmgmt file
> since the script automatically adds the device to the route command i.e.
> you can put the following lines into your route-ovirtmgmt file:
>
> 172.22.20.31 via 172.21.12.61
> 172.22.34.56 via 172.21.12.61
> 172.22.67.89 via 172.21.12.68
>
> (In case the first 2 of the mentioned IPs should be routed through the
> 172.21.12.61 gateway, and the last one should be routed through the
> 172.21.12.68 gateway).
>
> For the reference you can take a look at the
> /etc/sysconfig/network-scripts/ifup-routes script.
> It does the actual processing of both "route" and "rule" files for all
> network interfaces on a system.
>
> Please feel free to contact if you have further questions.
>
> Thanks in advance,
>
> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
> wrote:
>
>> Lev,
>>
>> Thanks for the response.  I was just getting ready to contact you about
>> this.  I do have 2 follow-up questions, if you don’t mind.
>>
>>
>>
>>1. When we were talking about creating the route that would be
>>enabled again after a reboot, you said to modify “the
>>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt 
>> or
>>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>>priority 32764 for the ip rule command?
>>2. If I have multiple IPs that I would need to create a static route,
>>would the priority be 32764 for all of them?
>>
>>
>>
>> Once again, thank you for all of your help with this!!
>>
>>
>>
>> [image: Count On EMC] <http://www.emcins.com/>
>>
>> *Doug Maxfield *| Senior Operating Systems Analyst
>>
>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>> Tel: 515.345.4507 | Fax: 866.331.1522
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Thursday, February 14, 2019 3:19 AM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> Hi Doug,
>>
>> Sorry that it took a bit of time to get back to you.
>> Managed to catch today somebody from the oVirt/RHV network team to
>> discuss the issue.
>>
>> It seems that we don't currently support custom static routes on the
>> hosts, so the workaround that I suggested is the way to do it.
>>
>> Thanks in advance,
>>
>>
>>
>> On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield <
>> doug.l.maxfi...@emcins.com> wrote:
>>
>> Will do.  Thanks again for all your help!!  Looking forward to a
>> confirmation of the fix or a different solution.  Either way, I know I have
>> a working fix.
>>
>>
>>
>> [image: Count On EMC] <http://www.emcins.com/>
>>
>> *Doug Maxfield *| Senior Operating Systems Analyst
>>
>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>> Tel: 515.345.4507 | Fax: 866.331.1522
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>

[ovirt-users] Re: Creating a static route

2019-02-14 Thread Lev Veyde

Hi Doug,

Sure, np.

>> 1. - yes it is the priority setting of the specific rule. Basically you
put in the file the post "ip rule add" part of the command e.g. for "ip
rule add to 172.22.20.31 priority 32764" you need to put a line of "to
172.22.20.31 priority 32764"

>> 2. - yes, the same priority can be used for all of them. E.g. if you
want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
add:

to 172.22.20.31 priority 32764
to 172.22.34.56 priority 32764
to 172.22.67.89 priority 32764

into the rule- file e.g. rule-ovirtmgmt or rule-eno3.

Please note that you will also need to add the static route for each one of
these as well w/ "ip route add ... " command e.g. "ip route add
172.22.20.31 via 172.21.12.61".

You can also use the route- putting just the route info
part, similar to the "ip rule" e.g. for equivalent of "ip route add
172.22.20.31 via 172.21.12.61" you need put in the file a line with the
content "172.22.20.31 via 172.21.12.61".
For routes it's important to use specifically the route-ovirtmgmt file
since the script automatically adds the device to the route command i.e.
you can put the following lines into your route-ovirtmgmt file:

172.22.20.31 via 172.21.12.61
172.22.34.56 via 172.21.12.61
172.22.67.89 via 172.21.12.68

(In case the first 2 of the mentioned IPs should be routed through the
172.21.12.61 gateway, and the last one should be routed through the
172.21.12.68 gateway).

For the reference you can take a look at the
/etc/sysconfig/network-scripts/ifup-routes script.
It does the actual processing of both "route" and "rule" files for all
network interfaces on a system.

Please feel free to contact if you have further questions.

Thanks in advance,

On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
wrote:

> Lev,
>
> Thanks for the response.  I was just getting ready to contact you about
> this.  I do have 2 follow-up questions, if you don’t mind.
>
>
>
>1. When we were talking about creating the route that would be enabled
>again after a reboot, you said to modify “the
>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt or
>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>priority 32764 for the ip rule command?
>2. If I have multiple IPs that I would need to create a static route,
>would the priority be 32764 for all of them?
>
>
>
> Once again, thank you for all of your help with this!!
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Thursday, February 14, 2019 3:19 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Sorry that it took a bit of time to get back to you.
> Managed to catch today somebody from the oVirt/RHV network team to discuss
> the issue.
>
> It seems that we don't currently support custom static routes on the
> hosts, so the workaround that I suggested is the way to do it.
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield 
> wrote:
>
> Will do.  Thanks again for all your help!!  Looking forward to a
> confirmation of the fix or a different solution.  Either way, I know I have
> a working fix.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 3:09 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Just a small note - the commands in the rc.local should be placed *before*
> the very last line (the touch ... command).
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:56 PM Lev Veyde  wrote:
>
> Hi Doug,
>
> Thanks, you're welcome!
>
> It's generally possible to add persistent rules by either using the legacy
> /etc/rc.d/rc.local boot script (chmod +x /etc/rc.d/rc.local and put the
> relevant commands at the end of the file, that way you can actually run any
> commands) or by using the /etc/sysconfig/network-scripts/rule- name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
> 172.22.20.31 priority 32764" - without quotes), however of c

[ovirt-users] Re: Creating a static route

2019-02-14 Thread Lev Veyde

Hi Doug,

Sorry that it took a bit of time to get back to you.
Managed to catch today somebody from the oVirt/RHV network team to discuss
the issue.
It seems that we don't currently support custom static routes on the hosts,
so the workaround that I suggested is the way to do it.

Thanks in advance,

On Tue, Feb 12, 2019 at 11:12 PM Doug Maxfield 
wrote:

> Will do.  Thanks again for all your help!!  Looking forward to a
> confirmation of the fix or a different solution.  Either way, I know I have
> a working fix.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 3:09 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Just a small note - the commands in the rc.local should be placed *before*
> the very last line (the touch ... command).
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:56 PM Lev Veyde  wrote:
>
> Hi Doug,
>
> Thanks, you're welcome!
>
> It's generally possible to add persistent rules by either using the legacy
> /etc/rc.d/rc.local boot script (chmod +x /etc/rc.d/rc.local and put the
> relevant commands at the end of the file, that way you can actually run any
> commands) or by using the /etc/sysconfig/network-scripts/rule- name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
> 172.22.20.31 priority 32764" - without quotes), however of course this
> needs to be tested to verify that it works.
>
> I forwarded the issue to the network team and hopefully they will update
> soon.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> You have no idea how helpful you have been!!  I’ve been having this
> issue for over 2 months and starting to cause major problems.
>
>
>
> Please let me know if you find a better solution.  I’m going to wait to
> hear back from you before implementing.
>
>
>
> If we go with this workaround, is there a way to add the ip rule so it’s
> persistent?  I know how to make the ip route add persistent.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:14 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Yes, it looks like it did.
>
> I'll try to catch somebody from my local oVirt/RHV networking team to take
> a look at this issue, maybe there is a better solution for that issue than
> my workaround.
>
>
>
> But meanwhile you can use this workaround (ip route add + ip rule add),
> just please be aware that these should be run after each host reboot, since
> these commands are not persistent.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Here’s the results.  It appears to fix the issue!!
>
>
>
> From non-working system:
>
>
>
> -bash-4.2# ip rule add to 172.22.20.31 priority 32764
>
>
>
> -bash-4.2# traceroute 172.22.20.31
>
> traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets
>
> 1  CenteraAmesAN1.emcins.com (172.21.12.61)  0.487 ms  1.082 ms  1.313 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:01 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> OK, I think that I have a guess of what may have happened here...
>
> Can you please run the following command on the (non-working) host:
>
> ip rule add to 172.22.20.31 priority 32764
>
>
>
> This needs to be run in addition to the ip route add ..

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

Just a small note - the commands in the rc.local should be placed *before*
the very last line (the touch ... command).

Thanks in advance,

On Tue, Feb 12, 2019 at 10:56 PM Lev Veyde  wrote:

> Hi Doug,
>
> Thanks, you're welcome!
>
> It's generally possible to add persistent rules by either using the legacy
> /etc/rc.d/rc.local boot script (chmod +x /etc/rc.d/rc.local and put the
> relevant commands at the end of the file, that way you can actually run any
> commands) or by using the /etc/sysconfig/network-scripts/rule- name> e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
> 172.22.20.31 priority 32764" - without quotes), however of course this
> needs to be tested to verify that it works.
>
> I forwarded the issue to the network team and hopefully they will update
> soon.
>
> Thanks in advance,
>
> On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
> wrote:
>
>> Lev,
>>
>> You have no idea how helpful you have been!!  I’ve been having this
>> issue for over 2 months and starting to cause major problems.
>>
>>
>>
>> Please let me know if you find a better solution.  I’m going to wait to
>> hear back from you before implementing.
>>
>>
>>
>> If we go with this workaround, is there a way to add the ip rule so it’s
>> persistent?  I know how to make the ip route add persistent.
>>
>>
>>
>> [image: Count On EMC] <http://www.emcins.com/>
>>
>> *Doug Maxfield *| Senior Operating Systems Analyst
>>
>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>> Tel: 515.345.4507 | Fax: 866.331.1522
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Tuesday, February 12, 2019 2:14 PM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> Hi Doug,
>>
>> Yes, it looks like it did.
>>
>> I'll try to catch somebody from my local oVirt/RHV networking team to
>> take a look at this issue, maybe there is a better solution for that issue
>> than my workaround.
>>
>>
>>
>> But meanwhile you can use this workaround (ip route add + ip rule add),
>> just please be aware that these should be run after each host reboot, since
>> these commands are not persistent.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield <
>> doug.l.maxfi...@emcins.com> wrote:
>>
>> Lev,
>>
>> Here’s the results.  It appears to fix the issue!!
>>
>>
>>
>> From non-working system:
>>
>>
>>
>> -bash-4.2# ip rule add to 172.22.20.31 priority 32764
>>
>>
>>
>> -bash-4.2# traceroute 172.22.20.31
>>
>> traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets
>>
>> 1  CenteraAmesAN1.emcins.com (172.21.12.61)  0.487 ms  1.082 ms  1.313 ms
>>
>> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>>
>> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>>
>>
>>
>> [image: Count On EMC] <http://www.emcins.com/>
>>
>> *Doug Maxfield *| Senior Operating Systems Analyst
>>
>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>> Tel: 515.345.4507 | Fax: 866.331.1522
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Tuesday, February 12, 2019 2:01 PM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> Hi Doug,
>>
>> OK, I think that I have a guess of what may have happened here...
>>
>> Can you please run the following command on the (non-working) host:
>>
>> ip rule add to 172.22.20.31 priority 32764
>>
>>
>>
>> This needs to be run in addition to the ip route add ... command.
>>
>>
>>
>> And then please run the traceroute command and let me know if that fixed
>> the issue.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
>> wrote:
>>
>> Lev,
>>
>> Here you go.
>>
>>
>>
>> From non-working system
>>
>>
>>
>> -bash-4.2# ip rule
>>
>> 0:  from all lookup local
>>
>> 32764:  from all to 172.21.0.0/16 iif ovirtmgmt lookup 2887058719
>>
&

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

Thanks, you're welcome!

It's generally possible to add persistent rules by either using the legacy
/etc/rc.d/rc.local boot script (chmod +x /etc/rc.d/rc.local and put the
relevant commands at the end of the file, that way you can actually run any
commands) or by using the /etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt or rule-eno3 (just put in the file "to
172.22.20.31 priority 32764" - without quotes), however of course this
needs to be tested to verify that it works.

I forwarded the issue to the network team and hopefully they will update
soon.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:17 PM Doug Maxfield 
wrote:

> Lev,
>
> You have no idea how helpful you have been!!  I’ve been having this
> issue for over 2 months and starting to cause major problems.
>
>
>
> Please let me know if you find a better solution.  I’m going to wait to
> hear back from you before implementing.
>
>
>
> If we go with this workaround, is there a way to add the ip rule so it’s
> persistent?  I know how to make the ip route add persistent.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:14 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> Yes, it looks like it did.
>
> I'll try to catch somebody from my local oVirt/RHV networking team to take
> a look at this issue, maybe there is a better solution for that issue than
> my workaround.
>
>
>
> But meanwhile you can use this workaround (ip route add + ip rule add),
> just please be aware that these should be run after each host reboot, since
> these commands are not persistent.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Here’s the results.  It appears to fix the issue!!
>
>
>
> From non-working system:
>
>
>
> -bash-4.2# ip rule add to 172.22.20.31 priority 32764
>
>
>
> -bash-4.2# traceroute 172.22.20.31
>
> traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets
>
> 1  CenteraAmesAN1.emcins.com (172.21.12.61)  0.487 ms  1.082 ms  1.313 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:01 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> OK, I think that I have a guess of what may have happened here...
>
> Can you please run the following command on the (non-working) host:
>
> ip rule add to 172.22.20.31 priority 32764
>
>
>
> This needs to be run in addition to the ip route add ... command.
>
>
>
> And then please run the traceroute command and let me know if that fixed
> the issue.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Here you go.
>
>
>
> From non-working system
>
>
>
> -bash-4.2# ip rule
>
> 0:  from all lookup local
>
> 32764:  from all to 172.21.0.0/16 iif ovirtmgmt lookup 2887058719
>
> 32765:  from 172.21.0.0/16 lookup 2887058719
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
>
>
> From working system
>
>
>
> [root@paputopcomm04 ~]# ip rule
>
> 0:  from all lookup local
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 12:35 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> That shouldn't really matter, since ovir

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

Yes, it looks like it did.

I'll try to catch somebody from my local oVirt/RHV networking team to take
a look at this issue, maybe there is a better solution for that issue than
my workaround.

But meanwhile you can use this workaround (ip route add + ip rule add),
just please be aware that these should be run after each host reboot, since
these commands are not persistent.

Thanks in advance,

On Tue, Feb 12, 2019 at 10:07 PM Doug Maxfield 
wrote:

> Lev,
>
> Here’s the results.  It appears to fix the issue!!
>
>
>
> From non-working system:
>
>
>
> -bash-4.2# ip rule add to 172.22.20.31 priority 32764
>
>
>
> -bash-4.2# traceroute 172.22.20.31
>
> traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets
>
> 1  CenteraAmesAN1.emcins.com (172.21.12.61)  0.487 ms  1.082 ms  1.313 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.507 ms  2.090 ms  2.294 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.403 ms  1.401 ms  1.348 ms
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 2:01 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> OK, I think that I have a guess of what may have happened here...
>
> Can you please run the following command on the (non-working) host:
>
> ip rule add to 172.22.20.31 priority 32764
>
>
>
> This needs to be run in addition to the ip route add ... command.
>
>
>
> And then please run the traceroute command and let me know if that fixed
> the issue.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Here you go.
>
>
>
> From non-working system
>
>
>
> -bash-4.2# ip rule
>
> 0:  from all lookup local
>
> 32764:  from all to 172.21.0.0/16 iif ovirtmgmt lookup 2887058719
>
> 32765:  from 172.21.0.0/16 lookup 2887058719
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
>
>
> From working system
>
>
>
> [root@paputopcomm04 ~]# ip rule
>
> 0:  from all lookup local
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 12:35 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> That shouldn't really matter, since ovirtmgmt is just a bridged interface,
> and unless I'm missing something it shouldn't really affect routing.
>
> Can you please also provide the output of "ip rule" from both working and
> non-working hosts ?
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 8:01 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Here’s the ip route from the server that worked and didn’t work
>
>
>
> IP Route from server that worked
>
>
>
> [root@paputopcomm04 ~]# ip route
>
> default via 172.21.0.250 dev eno3
>
> 169.254.0.0/16 dev eno3 scope link metric 1002
>
> 169.254.0.0/16 dev eno4 scope link metric 1005
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> *172.22.20.31 via 172.21.12.61 dev eno3*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
>
>
>
>
>
>
> IP Route from server that didn't work
>
>
>
> -bash-4.2# ip route
>
> default via 172.21.0.250 dev ovirtmgmt
>
> 169.254.0.0/16 dev eno4 scope link metric 1004
>
> 169.254.0.0/16 dev ovirtmgmt scope link metric 1021
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.15
>
> 172.21.0.0/16 dev ovirtmgmt proto kernel scope link src 172.21.5.31
>
> *172.22.20.31 via 172.21.12.61 dev ovirtmgmt*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
>
>
>
> We have had our network team look and they don’t know.  As I said, the was
> setup by Commvault.  It’s almost like the ovirtmgmt interface will not
> allow a route add due to the wa

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

OK, I think that I have a guess of what may have happened here...

Can you please run the following command on the (non-working) host:

ip rule add to 172.22.20.31 priority 32764

This needs to be run in addition to the ip route add ... command.

And then please run the traceroute command and let me know if that fixed
the issue.

Thanks in advance,

On Tue, Feb 12, 2019 at 9:30 PM Doug Maxfield 
wrote:

> Lev,
>
> Here you go.
>
>
>
> From non-working system
>
>
>
> -bash-4.2# ip rule
>
> 0:  from all lookup local
>
> 32764:  from all to 172.21.0.0/16 iif ovirtmgmt lookup 2887058719
>
> 32765:  from 172.21.0.0/16 lookup 2887058719
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
>
>
> From working system
>
>
>
> [root@paputopcomm04 ~]# ip rule
>
> 0:  from all lookup local
>
> 32766:  from all lookup main
>
> 32767:  from all lookup default
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 12:35 PM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> That shouldn't really matter, since ovirtmgmt is just a bridged interface,
> and unless I'm missing something it shouldn't really affect routing.
>
> Can you please also provide the output of "ip rule" from both working and
> non-working hosts ?
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 8:01 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Here’s the ip route from the server that worked and didn’t work
>
>
>
> IP Route from server that worked
>
>
>
> [root@paputopcomm04 ~]# ip route
>
> default via 172.21.0.250 dev eno3
>
> 169.254.0.0/16 dev eno3 scope link metric 1002
>
> 169.254.0.0/16 dev eno4 scope link metric 1005
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> *172.22.20.31 via 172.21.12.61 dev eno3*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
>
>
>
>
>
>
> IP Route from server that didn't work
>
>
>
> -bash-4.2# ip route
>
> default via 172.21.0.250 dev ovirtmgmt
>
> 169.254.0.0/16 dev eno4 scope link metric 1004
>
> 169.254.0.0/16 dev ovirtmgmt scope link metric 1021
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.15
>
> 172.21.0.0/16 dev ovirtmgmt proto kernel scope link src 172.21.5.31
>
> *172.22.20.31 via 172.21.12.61 dev ovirtmgmt*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
>
>
>
> We have had our network team look and they don’t know.  As I said, the was
> setup by Commvault.  It’s almost like the ovirtmgmt interface will not
> allow a route add due to the way it’s configured?   They, Commvault, are
> trying different things within their software to get this working, but it’s
> causing us more problems.  I figured I would take a shot and see if
> someone, who works with the oVirt software, would have any ideas.
>
>
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 11:51 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> This is indeed quite weird...
>
> It looks like the OS for some reason disregards the static route that you
> have added.
>
> BTW, have you verified that it's indeed was added by running "ip route"
> following the "ip route add ..." command ?
>
> Maybe somebody from the network team has an idea of what may be the cause
> of this issue...
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> I’m showing you the same outputs (ip a, ip route, traceroute, ip route
> add, and traceroute) from another server in this group that doesn’t use the
> ovirtmgmt for it’s default interface.
>
>
>
> [root@paputopcomm04 ~]# ip a
>
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
>
>

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

That shouldn't really matter, since ovirtmgmt is just a bridged interface,
and unless I'm missing something it shouldn't really affect routing.

Can you please also provide the output of "ip rule" from both working and
non-working hosts ?

Thanks in advance,

On Tue, Feb 12, 2019 at 8:01 PM Doug Maxfield 
wrote:

> Lev,
>
> Here’s the ip route from the server that worked and didn’t work
>
>
>
> IP Route from server that worked
>
>
>
> [root@paputopcomm04 ~]# ip route
>
> default via 172.21.0.250 dev eno3
>
> 169.254.0.0/16 dev eno3 scope link metric 1002
>
> 169.254.0.0/16 dev eno4 scope link metric 1005
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> *172.22.20.31 via 172.21.12.61 dev eno3*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
>
>
>
>
>
>
> IP Route from server that didn't work
>
>
>
> -bash-4.2# ip route
>
> default via 172.21.0.250 dev ovirtmgmt
>
> 169.254.0.0/16 dev eno4 scope link metric 1004
>
> 169.254.0.0/16 dev ovirtmgmt scope link metric 1021
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.15
>
> 172.21.0.0/16 dev ovirtmgmt proto kernel scope link src 172.21.5.31
>
> *172.22.20.31 via 172.21.12.61 dev ovirtmgmt*
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.31
>
>
>
> We have had our network team look and they don’t know.  As I said, the was
> setup by Commvault.  It’s almost like the ovirtmgmt interface will not
> allow a route add due to the way it’s configured?   They, Commvault, are
> trying different things within their software to get this working, but it’s
> causing us more problems.  I figured I would take a shot and see if
> someone, who works with the oVirt software, would have any ideas.
>
>
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 11:51 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> This is indeed quite weird...
>
> It looks like the OS for some reason disregards the static route that you
> have added.
>
> BTW, have you verified that it's indeed was added by running "ip route"
> following the "ip route add ..." command ?
>
> Maybe somebody from the network team has an idea of what may be the cause
> of this issue...
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> I’m showing you the same outputs (ip a, ip route, traceroute, ip route
> add, and traceroute) from another server in this group that doesn’t use the
> ovirtmgmt for it’s default interface.
>
>
>
> [root@paputopcomm04 ~]# ip a
>
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>
> inet 127.0.0.1/8 scope host lo
>
>valid_lft forever preferred_lft forever
>
> inet6 ::1/128 scope host
>
>valid_lft forever preferred_lft forever
>
> 2: eno3:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
>
> inet 172.21.5.34/16 brd 172.21.255.255 scope global eno3
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc0/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 3: eno1:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
>
> inet 172.26.5.34/16 brd 172.26.255.255 scope global eno1
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fee8:da03/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 4: eno2:  mtu 1500 qdisc mq state DOWN
> qlen 1000
>
> link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff
>
> 5: eno4:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff
>
> inet 172.17.53.18/16 brd 172.17.255.255 scope global eno4
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc1/64 scope link
>
>valid_lft forever preferred_lft forever
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

This is indeed quite weird...
It looks like the OS for some reason disregards the static route that you
have added.

BTW, have you verified that it's indeed was added by running "ip route"
following the "ip route add ..." command ?

Maybe somebody from the network team has an idea of what may be the cause
of this issue...

Thanks in advance,

On Tue, Feb 12, 2019 at 7:36 PM Doug Maxfield 
wrote:

> Lev,
>
> I’m showing you the same outputs (ip a, ip route, traceroute, ip route
> add, and traceroute) from another server in this group that doesn’t use the
> ovirtmgmt for it’s default interface.
>
>
>
> [root@paputopcomm04 ~]# ip a
>
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>
> inet 127.0.0.1/8 scope host lo
>
>valid_lft forever preferred_lft forever
>
> inet6 ::1/128 scope host
>
>valid_lft forever preferred_lft forever
>
> 2: eno3:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c0 brd ff:ff:ff:ff:ff:ff
>
> inet 172.21.5.34/16 brd 172.21.255.255 scope global eno3
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc0/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 3: eno1:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:e8:da:03 brd ff:ff:ff:ff:ff:ff
>
> inet 172.26.5.34/16 brd 172.26.255.255 scope global eno1
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fee8:da03/64 scope link
>
>valid_lft forever preferred_lft forever
>
> 4: eno2:  mtu 1500 qdisc mq state DOWN
> qlen 1000
>
> link/ether 90:1b:0e:e8:da:04 brd ff:ff:ff:ff:ff:ff
>
> 5: eno4:  mtu 1500 qdisc mq state UP qlen
> 1000
>
> link/ether 90:1b:0e:db:bc:c1 brd ff:ff:ff:ff:ff:ff
>
> inet 172.17.53.18/16 brd 172.17.255.255 scope global eno4
>
>valid_lft forever preferred_lft forever
>
> inet6 fe80::921b:eff:fedb:bcc1/64 scope link
>
>valid_lft forever preferred_lft forever
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# ip route
>
> default via 172.21.0.250 dev eno3
>
> 169.254.0.0/16 dev eno3 scope link metric 1002
>
> 169.254.0.0/16 dev eno4 scope link metric 1005
>
> 172.17.0.0/16 dev eno4 proto kernel scope link src 172.17.53.18
>
> 172.21.0.0/16 dev eno3 proto kernel scope link src 172.21.5.34
>
> 172.26.0.0/16 dev eno1 proto kernel scope link src 172.26.5.34
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# traceroute 172.22.20.31
>
> traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets
>
> 1  ames-acc1-agg-1.emcins.com (172.21.0.246)  1.081 ms  1.816 ms  1.832 ms
>
> 2  192.168.200.30 (192.168.200.30)  0.639 ms 192.168.200.14
> (192.168.200.14)  1.063 ms  1.577 ms
>
> 3  192.168.200.101 (192.168.200.101)  3.110 ms ames-sw-wanrtr.emcins.com
> (192.168.200.97)  3.191 ms  3.277 ms
>
> 4  192.168.100.26 (192.168.100.26)  4.146 ms  4.273 ms  4.394 ms
>
> 5  192.168.100.98 (192.168.100.98)  1.893 ms  2.364 ms  2.397 ms
>
> 6  192.168.100.50 (192.168.100.50)  5.707 ms 192.168.100.33
> (192.168.100.33)  5.134 ms 192.168.100.50 (192.168.100.50)  4.105 ms
>
> 7  pdputopcomm01.emcins.com (172.22.20.31)  1.359 ms  1.374 ms  1.351 ms
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# ip route add 172.22.20.31 via 172.21.12.61
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]#
>
> [root@paputopcomm04 ~]# traceroute 172.22.20.31
>
> traceroute to 172.22.20.31 (172.22.20.31), 30 hops max, 60 byte packets
>
> 1  CenteraAmesAN1.emcins.com (172.21.12.61)  6.184 ms  6.475 ms  6.686 ms
>
> 2  192.168.90.9 (192.168.90.9)  1.770 ms  1.979 ms  2.189 ms
>
> 3  pdputopcomm01.emcins.com (172.22.20.31)  1.405 ms *  1.354 ms
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 11:07 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> In most cases it should not be required, especially as my guess (again it
> would be easier if y

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

In most cases it should not be required, especially as my guess (again it
would be easier if you could post the output of the "ip a" and "ip route")
is that the eno1 is part of the ovirtmgmt bridge.

What is the output of the "traceroute 172.22.20.31" that you get on the
host after you have added the static route?

Thanks in advance,


On Tue, Feb 12, 2019 at 6:58 PM Doug Maxfield 
wrote:

> Lev,
>
> One other question, since there are multiple enabled interfaces (ovirtmgmt
> and eno1), do I need to specify an interface for the route add.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 10:50 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> What do you mean by "static route is refused"?
>
> What is the error message(s) you see?
>
>
>
> Can you please try to add the route with the following command:
>
> ip route add 172.22.20.31 via 172.21.12.61
>
>
>
> If that doesn't work, then please provide more details, i.e. what is the
> exact error message(s) you see, the version of your OS and oVirt, output of
> "ip a" and "ip route" on your host(s), so that it will be easier to help
> you.
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 6:43 PM Doug Maxfield 
> wrote:
>
> Lev,
>
> Thanks for your response.
>
>
>
> If I attempt to manually add the route using route add:
>
>
>
> route add -net 172.22.20.31 netmask 255.255.255.255 gw 172.21.12.61 dev
> ovirtmgmt
>
>
>
> This static route is refused and all traffic is routed over the default
> gateway.
>
>
>
> But if I use a server that doesn’t use the ovirtmgmt interface and set the
> same static route, the required data is routed correctly over that static
> route.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 10:34 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> What is the exact problem you are having while attempting to add a static
> route on the hosts?
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 5:23 PM  wrote:
>
> Good Morning,
> New to oVirt.  We are using this with a backup solution from Commvault.
> The issue that we are having is that we need to setup a static route for
> specific data between 2 remote sites.  The ovirtmgmt is configured with the
> correct IP and gateway for the server.  We need to route data over a
> different gateway so that we don't "max out" the default network connection
> between the 2 sites.  Example below
>
> Ovirtmgmt IP - 172.21.5.31
> Gateway IP - 172.21.0.250
>
> We need any traffic with a destination of 172.22.20.31(Remote site) to
> route over this gateway, 172.21.12.61
>
> There are multiple servers in this configuration.  Servers that are not
> using the ovirtmgmt interface for their default, we are able to route the
> data.  The only problem is with attempting to setup a different static
> route on the ovirtmgmt interfaces.
>
> Thanks in advance for any help!!!
>
> Doug
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/WGXSLHAP3X5OT7DOXX3PMRLIMZBKTHR7/
>
>
>
> --
>
>
>
> *Lev Veyde*
>
> Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> <https://www.redhat.com>
>
> l...@redhat.com | lve...@redhat.com
>
> <https://red.ht/sig>
>
> *TRIED. TESTED. TRUSTED.* <https://redhat.com/trusted>
>
>
> NOTICE:  This message (including any attachments) is intended for a
> specific individual and may contain information that is either confidential
> or legally protected.  I

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

What do you mean by "static route is refused"?
What is the error message(s) you see?

Can you please try to add the route with the following command:

ip route add 172.22.20.31 via 172.21.12.61

If that doesn't work, then please provide more details, i.e. what is the
exact error message(s) you see, the version of your OS and oVirt, output of
"ip a" and "ip route" on your host(s), so that it will be easier to help
you.

Thanks in advance,

On Tue, Feb 12, 2019 at 6:43 PM Doug Maxfield 
wrote:

> Lev,
>
> Thanks for your response.
>
>
>
> If I attempt to manually add the route using route add:
>
>
>
> route add -net 172.22.20.31 netmask 255.255.255.255 gw 172.21.12.61 dev
> ovirtmgmt
>
>
>
> This static route is refused and all traffic is routed over the default
> gateway.
>
>
>
> But if I use a server that doesn’t use the ovirtmgmt interface and set the
> same static route, the required data is routed correctly over that static
> route.
>
>
>
> [image: Count On EMC] <http://www.emcins.com/>
>
> *Doug Maxfield *| Senior Operating Systems Analyst
>
> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
> Tel: 515.345.4507 | Fax: 866.331.1522
> doug.l.maxfi...@emcins.com | www.emcins.com
>
>
>
>
>
> *From:* Lev Veyde 
> *Sent:* Tuesday, February 12, 2019 10:34 AM
> *To:* Doug Maxfield 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] Creating a static route
>
>
>
> Hi Doug,
>
> What is the exact problem you are having while attempting to add a static
> route on the hosts?
>
>
>
> Thanks in advance,
>
>
>
> On Tue, Feb 12, 2019 at 5:23 PM  wrote:
>
> Good Morning,
> New to oVirt.  We are using this with a backup solution from Commvault.
> The issue that we are having is that we need to setup a static route for
> specific data between 2 remote sites.  The ovirtmgmt is configured with the
> correct IP and gateway for the server.  We need to route data over a
> different gateway so that we don't "max out" the default network connection
> between the 2 sites.  Example below
>
> Ovirtmgmt IP - 172.21.5.31
> Gateway IP - 172.21.0.250
>
> We need any traffic with a destination of 172.22.20.31(Remote site) to
> route over this gateway, 172.21.12.61
>
> There are multiple servers in this configuration.  Servers that are not
> using the ovirtmgmt interface for their default, we are able to route the
> data.  The only problem is with attempting to setup a different static
> route on the ovirtmgmt interfaces.
>
> Thanks in advance for any help!!!
>
> Doug
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/WGXSLHAP3X5OT7DOXX3PMRLIMZBKTHR7/
>
>
>
> --
>
>
>
> *Lev Veyde*
>
> Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> <https://www.redhat.com>
>
> l...@redhat.com | lve...@redhat.com
>
> <https://red.ht/sig>
>
> *TRIED. TESTED. TRUSTED.* <https://redhat.com/trusted>
>
>
> NOTICE:  This message (including any attachments) is intended for a
> specific individual and may contain information that is either confidential
> or legally protected.  If you believe that it has been sent to you in
> error, please reply to the sender that you have received the message in
> error, then delete it.  If you are not the intended recipient, you are
> hereby notified that any retention, dissemination, distribution, or copying
> of this communication is strictly prohibited.  Thank you.  EMC071856
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VSRTKE2I26JZZNPCAGO4NXK22F4632YW/

[ovirt-users] Re: Creating a static route

2019-02-12 Thread Lev Veyde

Hi Doug,

What is the exact problem you are having while attempting to add a static
route on the hosts?

Thanks in advance,

On Tue, Feb 12, 2019 at 5:23 PM  wrote:

> Good Morning,
> New to oVirt.  We are using this with a backup solution from Commvault.
> The issue that we are having is that we need to setup a static route for
> specific data between 2 remote sites.  The ovirtmgmt is configured with the
> correct IP and gateway for the server.  We need to route data over a
> different gateway so that we don't "max out" the default network connection
> between the 2 sites.  Example below
>
> Ovirtmgmt IP - 172.21.5.31
> Gateway IP - 172.21.0.250
>
> We need any traffic with a destination of 172.22.20.31(Remote site) to
> route over this gateway, 172.21.12.61
>
> There are multiple servers in this configuration.  Servers that are not
> using the ovirtmgmt interface for their default, we are able to route the
> data.  The only problem is with attempting to setup a different static
> route on the ovirtmgmt interfaces.
>
> Thanks in advance for any help!!!
>
> Doug
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/WGXSLHAP3X5OT7DOXX3PMRLIMZBKTHR7/
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SDDEUFJ63LKLUR6TVJWM7YSWXD46AFUD/

[ovirt-users] Re: Win10 0x80300001

2019-01-01 Thread Lev Veyde

Hi Greg,

In theory I would expect Windows to handle it more gracefully, (i.e. detect
that the disk is missing and ask for it) but in practice you should
understand that you're pulling the carpet under the Windows installer, and
it may potentially cause issues.

The preferred way to supply the drivers is to provide them on a separate
drive.
For instance, one can use USB DOK redirection.

Thanks in advance,

On Tue, Jan 1, 2019 at 10:29 PM Greg Sheremeta  wrote:

> Should that throw a BSOD though? It doesn't in Windows 8.1.
>
> I also got this error in Windows 10 in virt-manager (not ovirt) when
> trying to get virtio working. For my last Windows 8.1 install, I used 2 DVD
> drives so I didn't have to do the DVD swap dance, and that worked out quite
> nicely. Point the drivers search at E: and D: is left alone. I'll try that
> for my next Windows 10 attempt.
>
> On Tue, Jan 1, 2019 at 7:32 AM Lev Veyde  wrote:
>
>> Hi,
>>
>> If you're using the same DVD drive to mount the drivers ISO, then you
>> need to change back (remount) the Windows DVD, after you finished loading
>> the drivers.
>>
>> Thanks in advance,
>>
>> On Thu, Dec 27, 2018 at 9:29 PM  wrote:
>>
>>> Hi,
>>>
>>> I'm trying to install win10 pro, but when I load the disk driver
>>> vioscsi, it recognizes the disk but with this error: 0x8031
>>> oVirt 4.2.7.5-1.el7
>>> Disk Interface: VirtIO-SCSI
>>>
>>> Any idea?
>>>
>>> Thanks
>>> --
>>> --
>>> Jose Ferradeira
>>> http://www.logicworks.pt
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@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/GRGPZCABF7S6RME3B3MOPX25WWKR36AV/
>>>
>>
>>
>> --
>>
>> Lev Veyde
>>
>> Software Engineer, RHCE | RHCVA | MCITP
>>
>> Red Hat Israel
>>
>> <https://www.redhat.com>
>>
>> l...@redhat.com | lve...@redhat.com
>> <https://red.ht/sig>
>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/F7J65CVZNTOZLULVY6GKB4PBEQGJ62HA/
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> <https://www.redhat.com/>
>
> gsher...@redhat.comIRC: gshereme
> <https://red.ht/sig>
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4SCERR2E5SE3W7RNBELRRAOKQQQLMMFN/

[ovirt-users] Re: Win10 0x80300001

2019-01-01 Thread Lev Veyde

Hi,

If you're using the same DVD drive to mount the drivers ISO, then you need
to change back (remount) the Windows DVD, after you finished loading the
drivers.

Thanks in advance,

On Thu, Dec 27, 2018 at 9:29 PM  wrote:

> Hi,
>
> I'm trying to install win10 pro, but when I load the disk driver vioscsi,
> it recognizes the disk but with this error: 0x8031
> oVirt 4.2.7.5-1.el7
> Disk Interface: VirtIO-SCSI
>
> Any idea?
>
> Thanks
> --
> --
> Jose Ferradeira
> http://www.logicworks.pt
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/GRGPZCABF7S6RME3B3MOPX25WWKR36AV/
>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/F7J65CVZNTOZLULVY6GKB4PBEQGJ62HA/

[ovirt-users] Re: Try to add Host to cluster: Command returned failure code 1 during SSH session

2018-12-09 Thread Lev Veyde

f8b0-ee35-4c08-a416-1f0427dd2e9e.log'.
>
> 2018-12-09 14:48:28,295+01 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (VdsDeploy) [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] EVENT_ID:
> VDS_INSTALL_IN_PROGRESS(509), Installing Host kvm380. Stage: Termination.
>
>
>
> 2018-12-09 14:48:28,389+01 ERROR
> [org.ovirt.engine.core.uutils.ssh.SSHDialog]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] SSH error running command
> root@kvm380.durchhalten.intern:'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-deploy DIALOG/dialect=str:machine
> DIALOG/customization=bool:True': IOException: Command returned failure code
> 1 during SSH session 'root@kvm380.durchhalten.intern'
>
>
>
> 2018-12-09 14:48:28,389+01 ERROR
> [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] Error during host
> kvm380.durchhalten.intern install
>
> 2018-12-09 14:48:28,391+01 ERROR
> [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] Host installation failed for host
> 'c06e2a1b-7d94-45f7-aaab-21da6703d6fc', 'kvm380': Command returned failure
> code 1 during SSH session 'root@kvm380.durchhalten.intern'
>
> 2018-12-09 14:48:28,393+01 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] START,
> SetVdsStatusVDSCommand(HostName = kvm380,
> SetVdsStatusVDSCommandParameters:{hostId='c06e2a1b-7d94-45f7-aaab-21da6703d6fc',
> status='InstallFailed', nonOperationalReason='NONE',
> stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 29ddff69
>
> 2018-12-09 14:48:28,395+01 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] FINISH, SetVdsStatusVDSCommand, log
> id: 29ddff69
>
> 2018-12-09 14:48:28,414+01 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] EVENT_ID: VDS_INSTALL_FAILED(505),
> Host kvm380 installation failed. Command returned failure code 1 during SSH
> session 'root@kvm380.durchhalten.intern'.
>
> 2018-12-09 14:48:28,418+01 INFO
> [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
> (EE-ManagedThreadFactory-engine-Thread-1942)
> [f097f8b0-ee35-4c08-a416-1f0427dd2e9e] Lock freed to object
> 'EngineLock:{exclusiveLocks='[c06e2a1b-7d94-45f7-aaab-21da6703d6fc=VDS]',
> sharedLocks=''}'
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/TC2CT2AWKTXYYRBHUSEZELNINHLDSG7D/
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7S2C7O5UC2ECT6WETMJLFR3AESLE2ZRX/

[ovirt-users] [ANN] oVirt 4.2.7 Third Release Candidate is now available

2018-10-18 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.7 Third Release Candidate, as of October 18th, 2018.

This update is a release candidate of the seventh in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.7 release highlights:
http://www.ovirt.org/release/4.2.7/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.7/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZOL4HUPLU5UV6REFNMFERZPRCHQW7FCZ/

[ovirt-users] [ANN] oVirt 4.2.5 is now generally available (fixed links)

2018-07-30 Thread Lev Veyde

The oVirt Project is pleased to announce the general availability of oVirt
4.2.5 as of July 30th, 2018

This update is the fifth release in a series of stabilization updates to
the 4.2 series.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.5 release highlights:
http://www.ovirt.org/release/4.2.5/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.5/
[2] http://resources.ovirt.org/pub/ovirt-4.2/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/EGN3FG2UCHLFEPI65VH7UIQVPC2TI3XD/

[ovirt-users] [ANN] oVirt 4.2.5 is now generally available

2018-07-30 Thread Lev Veyde

The oVirt Project is pleased to announce the general availability of oVirt
4.2.5 as of July 30th, 2018

This update is the fifth release in a series of stabilization updates to
the 4.2 series.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.3 release highlights:
http://www.ovirt.org/release/4.2.3/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.3/
[2] http://resources.ovirt.org/pub/ovirt-4.2/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SFYRQ6VOVW4OZANS6YPAB5PACB2JRU3E/

[ovirt-users] [ANN] oVirt 4.2.5 Third Release Candidate is now available

2018-07-24 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.5 Third Release Candidate, as of July 24th, 2018.

This update is a release candidate of the fifth in a series of
stabilization updates to the 4.2 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.5 release highlights:
http://www.ovirt.org/release/4.2.5/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.5/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4ICPJH6QH2P273XZU3CBQQWKXA6Q6EEM/

[ovirt-users] [ANN] oVirt 4.2.5 Second Release Candidate is now available

2018-07-15 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.5 Second Release Candidate, as of July 15th, 2018.

This update is a release candidate of the fifth in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.5 release highlights:
http://www.ovirt.org/release/4.2.5/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.5/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/U2VPEOX4F35IR5TASKQKG7RIQEKZQAOR/

[ovirt-users] [ANN] oVirt 4.2.4 Fifth Release Candidate is now available

2018-06-20 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.4 Fifth Release Candidate, as of June 20th, 2018.

This update is a release candidate of the fourth in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.4 release highlights:
http://www.ovirt.org/release/4.2.4/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.4/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QS2ADLQWRDJ5YKPTYJ3EHMUTFTNFPPEE/

[ovirt-users] [ANN] oVirt 4.2.4 Third Release Candidate is now available

2018-06-07 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.4 Third Release Candidate, as of June 7th, 2018.

This update is a release candidate of the fourth in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.4 release highlights:
http://www.ovirt.org/release/4.2.4/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.4/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QI2HUZEOHZM7SP73P4FNVAZGZSJ2PZ5P/

[ovirt-users] [ANN] oVirt 4.2.4 Second Release Candidate is now available

2018-05-31 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.4 Second Release Candidate, as of May 31st, 2018

This update is a release candidate of the fourth in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.4 release highlights:
http://www.ovirt.org/release/4.2.4/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.4/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CY3IG345HHJPTRCJUTKJ44JLK4MFP2OB/

[ovirt-users] Updated ovirt-engine packages were released for oVirt 4.2

2018-05-29 Thread Lev Veyde

Hi,

We have added an updated oVirt engine (4.2.3.8) to the oVirt 4.2 stable yum
repo.

It fixes BZ#1582483 [1].

[1] https://bugzilla.redhat.com/1582483

Thanks in advance,
-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QAYJ7TSOP2LMWXHAZYYA7MCIXJBQTZUD/

[ovirt-users] [ANN] oVirt 4.2.3 Fourth Release Candidate is now available

2018-05-03 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.3 Fourth Release Candidate, as of May 3rd, 2018

This update is a release candidate of the third in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.3 release highlights:
http://www.ovirt.org/release/4.2.3/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.3/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.3 Third Release Candidate is now available

2018-04-26 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.3 Third Release Candidate, as of April 26th, 2018

This update is a release candidate of the third in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.3 release highlights:
http://www.ovirt.org/release/4.2.3/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.3/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Announcing oVirt Orb

2018-04-16 Thread Lev Veyde

oVirt project is happy to announce the oVirt Orb.

oVirt Orb is a project that allows anyone to easily take an oVirt for a
ride, test and play with it.

Please take a look at the documentation at:
https://ovirt.org/documentation/ovirt-orb/

Thanks in advance,
-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.3 First Release Candidate is now available

2018-04-12 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.3 First
Release Candidate, as of April 12th, 2018

This update is a release candidate of the third in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.3 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.3/>2
<http://www.ovirt.org/release/4.2.3/>. <http://www.ovirt.org/release/4.2.3/>
3 <http://www.ovirt.org/release/4.2.3/>/
<http://www.ovirt.org/release/4.2.3/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.3/>2
<http://www.ovirt.org/release/4.2.3/>. <http://www.ovirt.org/release/4.2.3/>
3 <http://www.ovirt.org/release/4.2.3/>/
<http://www.ovirt.org/release/4.2.3/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.2 GA Release is now available

2018-03-28 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt 4.2.2 GA
release, as of March 28th, 2018.

This update is a GA release of the second in a series of stabilization
updates to the 4.2
series.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.2 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2/iso/>2
<http://resources.ovirt.org/pub/ovirt-4.2/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.2 FifthRelease Candidate is now available

2018-03-22 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.2 Fifth
Release Candidate, as of March 22nd, 2018

This update is a release candidate of the second in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.2 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.2 Fourth Release Candidate is now available

2018-03-15 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.2 Fourth
Release Candidate, as of March 15th, 2018

This update is a release candidate of the second in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance will be available soon
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.2 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.2 Second Release Candidate is now available

2018-02-21 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.2 Second
Release Candidate, as of February 21th, 2018

This update is a release candidate of the second in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.2 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.2 First Release Candidate is now available

2018-02-15 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.2 First
Release Candidate, as of February 15th, 2018

This update is a release candidate of the second in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.2 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.2/>2
<http://www.ovirt.org/release/4.2.2/>. <http://www.ovirt.org/release/4.2.2/>
2 <http://www.ovirt.org/release/4.2.2/>/
<http://www.ovirt.org/release/4.2.2/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.1 Release is now available

2018-02-12 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt 4.2.1
Release, as of February 12th, 2018

This update is a release of the first in a series of stabilization updates
to the 4.2
series.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available [2]

Additional Resources:
* Read more about the oVirt 4.2.1 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2/iso/>2
<http://resources.ovirt.org/pub/ovirt-4.2/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.1 Sixth Release Candidate is now available

2018-02-07 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.1 Sixth
Release Candidate, as of February 7th, 2018

This update is a release candidate of the first in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.1 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>



-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.1 Fourth Release Candidate is now available

2018-01-30 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.1 Fourth
Release Candidate, as of January 30th, 2017

This update is a release candidate of the first in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.1 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.1 Third Release Candidate is now available

2018-01-25 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.2.1 Third
Release Candidate, as of January 25th, 2017

This update is a release candidate of the first in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.1 release highlights:
http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2
<http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/>
1 <http://www.ovirt.org/release/4.2.1/>/
<http://www.ovirt.org/release/4.2.1/>
[2] http://resources.ovirt.org/pub/ovirt-4.
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/
<http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.9 Release is now available

2018-01-24 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.1.9 release, as of January 24th, 2017

This update is the ninth in a series of stabilization updates to the 4.1
series.

Please note that no further updates will be issued for the 4.1 series.
We encourage users to upgrade to 4.2 series to receive new features and
updates.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available [2]
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.1.9 release highlights:
http://www.ovirt.org/release/4.1.9/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.1.9/
[2] http://resources.ovirt.org/pub/ovirt-4.1/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.9 Second Release Candidate is now available

2018-01-17 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.1.9 RC2 release, as of January 17th, 2017

This update is the ninth in a series of stabilization updates to the 4.1
series.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available [2]
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.1.9 release highlights:
http://www.ovirt.org/release/4.1.9/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.1.9/
[2] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.9 First Release Candidate is now available

2018-01-11 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the oVirt
4.1.9 First
Release Candidate, as of January 11th, 2017

This update is the nineth in a series of stabilization updates to the 4.1
series.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available [2]
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.1.9 release highlights:
http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.9/>9
<http://www.ovirt.org/release/4.1.9/>/ <http://www.ovirt.org/release/4.1.9/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.9/>9
<http://www.ovirt.org/release/4.1.9/>/ <http://www.ovirt.org/release/4.1.9/>
[2] http://resources.ovirt.org/pub/ovirt-4.1/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.8 Fourth Release Candidate is now available

2017-12-01 Thread Lev Veyde

Hi Fernando,

>> BZ 1448831 - Issues with automating the configuration of VMs
(cloud-init) - https://bugzilla.redhat.com/show_bug.cgi?id=1448831
That was already fixed in 4.1.3.5.

>> BZ 1464043 - Cloud-init network configuraton doesn't work -
https://bugzilla.redhat.com/show_bug.cgi?id=1464043
AFAIK it's fixed only in the 4.2.

Thanks in advance,

On Fri, Dec 1, 2017 at 1:58 PM, FERNANDO FREDIANI <fernando.fredi...@upx.com
> wrote:

> Thanks Simone.
>
> Let me ask about a two bugfixes I am eagerly waiting for 4.1.x and they
> are already on the 4.2.0 release notes.
>
> BZ 1448831 - Issues with automating the configuration of VMs (cloud-init)
> - https://bugzilla.redhat.com/show_bug.cgi?id=1448831
> BZ 1464043 - Cloud-init network configuraton doesn't work -
> https://bugzilla.redhat.com/show_bug.cgi?id=1464043
>
> Have they been included in 4.1.8 or any other previous versions ? I have
> searched through the release notes and couldn't find anything related. And
> if not will it be at some point ?
>
> Thanks
> Fernando
>
>
>
> On 01/12/2017 07:18, Simone Tiraboschi wrote:
>
> The oVirt Project is pleased to announce the availability of the Fourth
> Release Candidate of oVirt 4.1.8, as of November 30th, 2017
>
> This update is the eighth in a series of stabilization updates to the 4.1
> series.
>
> Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a
> real performance boost for ovirt when using GlusterFS .
> Due  to a known issue [6], using this will break live storage migration.
> This is expected to be fixed soon. If you do not use live storage
> migration you can give it a try. Use [7] for more details on how to  enable
> it.
>
> This release is available now for:
> * Red Hat Enterprise Linux 7.4 or later
> * CentOS Linux (or similar) 7.4 or later
>
> This release supports Hypervisor Hosts running:
> * Red Hat Enterprise Linux 7.4 or later
> * CentOS Linux (or similar) 7.4 or later
> * oVirt Node 4.1
>
> See the release notes draft [3] for installation / upgrade instructions and
> a list of new features and bugs fixed.
>
> Notes:
> * oVirt Appliance is already available
> * oVirt Live is already available[4]
> * oVirt Node is already available[4]
>
> Additional Resources:
> * Read more about the oVirt 4.1.8 release highlights:http://www.ovirt.
> org/release/4.1.8/
> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
> * Check out the latest project news on the oVirt blog:
> http://www.ovirt.org/blog/
>
> [1] https://www.ovirt.org/community/
> [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
> [3] http://www.ovirt.org/release/4.1.8/
> [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
> [5] http://staged-gluster-docs.readthedocs.io/en/release3.7.
> 0beta1/Features/libgfapi/
> [6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562
> [7] http://www.ovirt.org/develop/release-management/features/
> storage/glusterfs-storage-domain/
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.8 Third Release Candidate is now available

2017-11-26 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the Third Release
Candidate of oVirt 4.1.8, as of November 26th, 2017

This update is the eighth in a series of stabilization updates to the 4.1
series.

Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a
real performance boost for ovirt when using GlusterFS .
Due  to a known issue [6], using this will break live storage migration.
This is expected to be fixed soon. If you do not use live storage
migration you can give it a try. Use [7] for more details on how to  enable
it.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available[4]
- oVirt Node is already available[4]

Additional Resources:
* Read more about the oVirt 4.1.8 release highlights:
http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.8/>8
<http://www.ovirt.org/release/4.1.8/>/ <http://www.ovirt.org/release/4.1.8/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.8/>8
<http://www.ovirt.org/release/4.1.8/>/ <http://www.ovirt.org/release/4.1.8/>
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
[5]
http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/libgfapi/
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562
[7]
http://www.ovirt.org/develop/release-management/features/storage/glusterfs-storage-domain/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.8 Second Release Candidate is now available

2017-11-23 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the Second Release
Candidate of oVirt 4.1.8, as of November 23rd, 2017

This update is the eighth in a series of stabilization updates to the 4.1
series.

Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a
real performance boost for ovirt when using GlusterFS .
Due  to a known issue [6], using this will break live storage migration.
This is expected to be fixed soon. If you do not use live storage
migration you can give it a try. Use [7] for more details on how to  enable
it.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available[4]
- oVirt Node is already available[4]

Additional Resources:
* Read more about the oVirt 4.1.8 release highlights:
http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.8/>8
<http://www.ovirt.org/release/4.1.8/>/ <http://www.ovirt.org/release/4.1.8/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.8/>8
<http://www.ovirt.org/release/4.1.8/>/ <http://www.ovirt.org/release/4.1.8/>
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
[5]
http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/libgfapi/
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562
[7]
http://www.ovirt.org/develop/release-management/features/storage/glusterfs-storage-domain/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.8 First Release Candidate is now available

2017-11-16 Thread Lev Veyde

The oVirt Project is pleased to announce the availability of the First Release
Candidate of oVirt 4.1.8, as of November 16th, 2017

This update is the eighth in a series of stabilization updates to the 4.1
series.

Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a
real performance boost for ovirt when using GlusterFS .
Due  to a known issue [6], using this will break live storage migration.
This is expected to be fixed soon. If you do not use live storage
migration you can give it a try. Use [7] for more details on how to  enable
it.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available[4]
- oVirt Node is already available[4]

Additional Resources:
* Read more about the oVirt 4.1.8 release highlights:
http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.8/>8
<http://www.ovirt.org/release/4.1.8/>/ <http://www.ovirt.org/release/4.1.8/>
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.8/>8
<http://www.ovirt.org/release/4.1.8/>/ <http://www.ovirt.org/release/4.1.8/>
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
[5]
http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/libgfapi/
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562
[7]
http://www.ovirt.org/develop/release-management/features/storage/glusterfs-storage-domain/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Fixed ovirt-node-ng packages

2017-11-09 Thread Lev Veyde

Hi Fernando,

The issue fixed is : https://bugzilla.redhat.com/show_bug.cgi?id=1510858

So it doesn't look related, but regardless if the issue returns can you
please open a bug with all the details?

Thanks in advance,

On Thu, Nov 9, 2017 at 6:14 PM, FERNANDO FREDIANI <fernando.fredi...@upx.com
> wrote:

> Thanks Lev. Could you please mention in a short sentence what this
> critical issue is related to ?
>
> Coincidently or not today I had a major issue in our node related to
> network which only resolved after I live migrated all VMs out from a node
> and rebooted it. It seems this network issue was happening on all hosts not
> only this rebooted.
>
> Fernando
>
> On 09/11/2017 12:54, Lev Veyde wrote:
>
> Unfortunately shortly after the oVirt 4.1.7 release we discovered a
> critical issue with ovirt-node-ng.
>
> The issue was promptly handled, and fixed packages were pushed into the
> repo.
> Also the ovirt-node-ng-installer ISO was rebuilt.
>
> Please make sure to update your repo and use the fixed
> ovirt-node-ng-installer ISO:
>
> http://plain.resources.ovirt.org/pub/ovirt-4.1/iso/ovirt-
> node-ng-installer-ovirt/4.1-2017110820/ovirt-node-ng-installer-ovirt-4.1-
> 2017110820.iso
>
> --
>
> Lev Veyde
>
> Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> <https://www.redhat.com>
>
> l...@redhat.com | lve...@redhat.com
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Fixed ovirt-node-ng packages

2017-11-09 Thread Lev Veyde

Unfortunately shortly after the oVirt 4.1.7 release we discovered a
critical issue with ovirt-node-ng.

The issue was promptly handled, and fixed packages were pushed into the
repo.
Also the ovirt-node-ng-installer ISO was rebuilt.

Please make sure to update your repo and use the fixed
ovirt-node-ng-installer ISO:

http://plain.resources.ovirt.org/pub/ovirt-4.1/iso/ovirt-node-ng-installer-ovirt/4.1-2017110820/ovirt-node-ng-installer-ovirt-4.1-2017110820.iso

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

<https://www.redhat.com>

l...@redhat.com | lve...@redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

1 2 >

1 - 100 of 141 matches

Mail list logo