[ovirt-devel] Re: oVirt on Fedora 28 for developers

[Nir Soffer]

On Thu, Jun 28, 2018 at 8:22 PM Greg Sheremeta  wrote:

> On Thu, Jun 28, 2018 at 12:04 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> 2018-06-28 15:42 GMT+02:00 Nir Soffer :
>>
>>> I want to share the current state of oVirt on Fedora 28, hopefully it
>>> will
>>> save time for other developers.
>>>
>>
>> Thanks for the summary!
>>
>
> +1
>
>
>>
>>
>>
>>>
>>>
>>> 1. Why should I run oVirt on Fedora 28?
>>>
>>> - Fedora is the the base for future CentOS. The bugs we find *today* on
>>> Fedora 28
>>> are the bugs that we will not have next year when we try oVirt on CentOS.
>>>
>>> - I want to contribute to projects that require python 3. For example,
>>> virt-v2v
>>>   require python 3.6 in upstream. If you want to contribute you need to
>>> test
>>>   it on Fedora 28.
>>>
>>> - I need to develop with latest libvirt and qemu. One example is
>>> incremental
>>>   backup, you will need Fefora 28 to work on this.
>>>
>>> - CentOS is old and boring, I want to play with the newest bugs :-)
>>>
>>>
>>> 2. How to install oVirt with Fedora 28 hosts
>>>
>>> Warning: ugly hacks bellow!
>>>
>>> - Install ovirt-release-master.rpm on all hosts
>>>
>>> dnf install
>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
>>>
>>> - Install or build engine on CentOS 7.5 (1804)[1]
>>>
>>
> Why have only half the fun? Engine works on fc28.
>

I needed the shortest way to Fedora 28 host. Next time I'll move it to
Fedora :-)


>
>
>>
>>> - When provisioning a host, make sure you have lvm2-2.02.177-5.fc28
>>>   without it, no block storage you[2]
>>>
>>
>> This has been pushed to stable 3 days ago, so just "dnf update
>> --refresh"  should be enough to consume it
>>
>>
>>
>>>
>>> - When adding a host, disable "Configure host firewall" - it does not
>>> work now
>>>   I hope that Sandro team will fix this issue soon.
>>>
>>
>> Tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1381135
>>
>>
>>
>>>
>>> - Adding a host will fail, because without firewall setup, port 54321 is
>>> not reacable.
>>>   to fix this, configure the firewall manually, or disable it
>>>
>>> iptables -F
>>>
>>> This is pretty lame because you have to apply it again after restart,
>>> but it was
>>> good enough for now.
>>>
>>> - Because the host was not reachable, we don't configure the host network
>>>   so the host will be non-operational.
>>>   To fix this, open host > network > setup networks and assign ovirtmgmt
>>>   to the host management nic. The host will become UP after that.
>>>   I hope that Dan team will fix it soon.
>>>
>>> - Adding storage will fail because sanlock selinux issue[3]
>>>   To fix, set selinux to permissive mode:
>>>
>>>   setenforce 0
>>>
>>
>> Please add a custom rule to selinux instead of disabling it while waiting
>> for a fix, so you can catch more selinux issues masked by this.
>>
>>
>>
>>> At this point you should have a working setup.
>>>
>>>
>>> 3. Building and instaling vdsm from source on Fedora 28
>>>
>>> - Install build dependencies using
>>>
>>>   dnf install `cat automation/check-patch.packages.fc28`
>>>
>>> - Clean the source (needed if you rerun ./autogen.sh with different
>>> options)
>>>
>>>   git clean -dxf
>>>
>>> - Configure vdsm with hooks - for some reason 2 hooks are required
>>>   on Fedora but not on EL.
>>>
>>>   ./autogen.sh --system --enable-hooks
>>>
>>> - Build
>>>
>>>   make
>>>   make rpm
>>>
>>> - Install the packages at /home/user/rpmbuild/RPMS/{noarch,x86_64}
>>>
>>> - if vdsm was never installed, you need to configure and enable it
>>>
>>>   vdsm-tool configure --force
>>>   systemctl enable vdsmd
>>>   systemctl start vdsmd
>>>
>>> At this point you can test the new bugs you added to vdsm :-)
>>>
>>>
>>> [1] I did not try to install engine on Fedora 28. I guess engine folks
>>> can
>>> share if there are issues with this.
>>>
>>> [2] https://bugzilla.redhat.com/1575762
>>> LVM team fixed the issue couple of hours after I asked about it in #lvm
>>> We had a build for testing couple of days later.
>>>
>>> [3] https://bugzilla.redhat.com/1593853
>>> We are still waiting for selinux folks response.
>>>
>>> Happy hacking!
>>>
>>> Nir
>>>
>>>
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>>
> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-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/devel@ovirt.org/message/DZTZTRLEEV2BKJ2XCMX2FGQEMPTAE5OG/
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
>
___
Devel 

[ovirt-devel] Re: oVirt on Fedora 28 for developers

[Greg Sheremeta]

On Thu, Jun 28, 2018 at 12:04 PM Sandro Bonazzola 
wrote:

>
>
> 2018-06-28 15:42 GMT+02:00 Nir Soffer :
>
>> I want to share the current state of oVirt on Fedora 28, hopefully it will
>> save time for other developers.
>>
>
> Thanks for the summary!
>

+1


>
>
>
>>
>>
>> 1. Why should I run oVirt on Fedora 28?
>>
>> - Fedora is the the base for future CentOS. The bugs we find *today* on
>> Fedora 28
>> are the bugs that we will not have next year when we try oVirt on CentOS.
>>
>> - I want to contribute to projects that require python 3. For example,
>> virt-v2v
>>   require python 3.6 in upstream. If you want to contribute you need to
>> test
>>   it on Fedora 28.
>>
>> - I need to develop with latest libvirt and qemu. One example is
>> incremental
>>   backup, you will need Fefora 28 to work on this.
>>
>> - CentOS is old and boring, I want to play with the newest bugs :-)
>>
>>
>> 2. How to install oVirt with Fedora 28 hosts
>>
>> Warning: ugly hacks bellow!
>>
>> - Install ovirt-release-master.rpm on all hosts
>>
>> dnf install
>> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
>>
>> - Install or build engine on CentOS 7.5 (1804)[1]
>>
>
Why have only half the fun? Engine works on fc28.


>
>> - When provisioning a host, make sure you have lvm2-2.02.177-5.fc28
>>   without it, no block storage you[2]
>>
>
> This has been pushed to stable 3 days ago, so just "dnf update --refresh"
> should be enough to consume it
>
>
>
>>
>> - When adding a host, disable "Configure host firewall" - it does not
>> work now
>>   I hope that Sandro team will fix this issue soon.
>>
>
> Tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1381135
>
>
>
>>
>> - Adding a host will fail, because without firewall setup, port 54321 is
>> not reacable.
>>   to fix this, configure the firewall manually, or disable it
>>
>> iptables -F
>>
>> This is pretty lame because you have to apply it again after restart, but
>> it was
>> good enough for now.
>>
>> - Because the host was not reachable, we don't configure the host network
>>   so the host will be non-operational.
>>   To fix this, open host > network > setup networks and assign ovirtmgmt
>>   to the host management nic. The host will become UP after that.
>>   I hope that Dan team will fix it soon.
>>
>> - Adding storage will fail because sanlock selinux issue[3]
>>   To fix, set selinux to permissive mode:
>>
>>   setenforce 0
>>
>
> Please add a custom rule to selinux instead of disabling it while waiting
> for a fix, so you can catch more selinux issues masked by this.
>
>
>
>> At this point you should have a working setup.
>>
>>
>> 3. Building and instaling vdsm from source on Fedora 28
>>
>> - Install build dependencies using
>>
>>   dnf install `cat automation/check-patch.packages.fc28`
>>
>> - Clean the source (needed if you rerun ./autogen.sh with different
>> options)
>>
>>   git clean -dxf
>>
>> - Configure vdsm with hooks - for some reason 2 hooks are required
>>   on Fedora but not on EL.
>>
>>   ./autogen.sh --system --enable-hooks
>>
>> - Build
>>
>>   make
>>   make rpm
>>
>> - Install the packages at /home/user/rpmbuild/RPMS/{noarch,x86_64}
>>
>> - if vdsm was never installed, you need to configure and enable it
>>
>>   vdsm-tool configure --force
>>   systemctl enable vdsmd
>>   systemctl start vdsmd
>>
>> At this point you can test the new bugs you added to vdsm :-)
>>
>>
>> [1] I did not try to install engine on Fedora 28. I guess engine folks can
>> share if there are issues with this.
>>
>> [2] https://bugzilla.redhat.com/1575762
>> LVM team fixed the issue couple of hours after I asked about it in #lvm
>> We had a build for testing couple of days later.
>>
>> [3] https://bugzilla.redhat.com/1593853
>> We are still waiting for selinux folks response.
>>
>> Happy hacking!
>>
>> Nir
>>
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-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/devel@ovirt.org/message/DZTZTRLEEV2BKJ2XCMX2FGQEMPTAE5OG/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/IMOA6LV6EM2KGIM45UJ6XS2EBZVTEBVB/

[ovirt-devel] Re: oVirt on Fedora 28 for developers

[Sandro Bonazzola]

2018-06-28 15:42 GMT+02:00 Nir Soffer :

> I want to share the current state of oVirt on Fedora 28, hopefully it will
> save time for other developers.
>

Thanks for the summary!



>
>
> 1. Why should I run oVirt on Fedora 28?
>
> - Fedora is the the base for future CentOS. The bugs we find *today* on
> Fedora 28
> are the bugs that we will not have next year when we try oVirt on CentOS.
>
> - I want to contribute to projects that require python 3. For example,
> virt-v2v
>   require python 3.6 in upstream. If you want to contribute you need to
> test
>   it on Fedora 28.
>
> - I need to develop with latest libvirt and qemu. One example is
> incremental
>   backup, you will need Fefora 28 to work on this.
>
> - CentOS is old and boring, I want to play with the newest bugs :-)
>
>
> 2. How to install oVirt with Fedora 28 hosts
>
> Warning: ugly hacks bellow!
>
> - Install ovirt-release-master.rpm on all hosts
>
> dnf install http://resources.ovirt.org/pub/yum-repo/ovirt-release-
> master.rpm
>
> - Install or build engine on CentOS 7.5 (1804)[1]
>
> - When provisioning a host, make sure you have lvm2-2.02.177-5.fc28
>   without it, no block storage you[2]
>

This has been pushed to stable 3 days ago, so just "dnf update --refresh"
should be enough to consume it



>
> - When adding a host, disable "Configure host firewall" - it does not work
> now
>   I hope that Sandro team will fix this issue soon.
>

Tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1381135



>
> - Adding a host will fail, because without firewall setup, port 54321 is
> not reacable.
>   to fix this, configure the firewall manually, or disable it
>
> iptables -F
>
> This is pretty lame because you have to apply it again after restart, but
> it was
> good enough for now.
>
> - Because the host was not reachable, we don't configure the host network
>   so the host will be non-operational.
>   To fix this, open host > network > setup networks and assign ovirtmgmt
>   to the host management nic. The host will become UP after that.
>   I hope that Dan team will fix it soon.
>
> - Adding storage will fail because sanlock selinux issue[3]
>   To fix, set selinux to permissive mode:
>
>   setenforce 0
>

Please add a custom rule to selinux instead of disabling it while waiting
for a fix, so you can catch more selinux issues masked by this.



> At this point you should have a working setup.
>
>
> 3. Building and instaling vdsm from source on Fedora 28
>
> - Install build dependencies using
>
>   dnf install `cat automation/check-patch.packages.fc28`
>
> - Clean the source (needed if you rerun ./autogen.sh with different
> options)
>
>   git clean -dxf
>
> - Configure vdsm with hooks - for some reason 2 hooks are required
>   on Fedora but not on EL.
>
>   ./autogen.sh --system --enable-hooks
>
> - Build
>
>   make
>   make rpm
>
> - Install the packages at /home/user/rpmbuild/RPMS/{noarch,x86_64}
>
> - if vdsm was never installed, you need to configure and enable it
>
>   vdsm-tool configure --force
>   systemctl enable vdsmd
>   systemctl start vdsmd
>
> At this point you can test the new bugs you added to vdsm :-)
>
>
> [1] I did not try to install engine on Fedora 28. I guess engine folks can
> share if there are issues with this.
>
> [2] https://bugzilla.redhat.com/1575762
> LVM team fixed the issue couple of hours after I asked about it in #lvm
> We had a build for testing couple of days later.
>
> [3] https://bugzilla.redhat.com/1593853
> We are still waiting for selinux folks response.
>
> Happy hacking!
>
> Nir
>
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/DZTZTRLEEV2BKJ2XCMX2FGQEMPTAE5OG/

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]

[Dafna Ron]

vdsm also failing on the same issue:

https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8407/

Thanks,
Dafna


On Thu, Jun 28, 2018 at 11:11 AM, Dafna Ron  wrote:

> Thanks Alona,
> Can you please update me once you have a fix?
>
> Thanks,
> Dafna
>
>
> On Thu, Jun 28, 2018 at 10:28 AM, Alona Kaplan 
> wrote:
>
>> Hi,
>> I'm aware to the error. Francesco and me are working on it.
>>
>> Thank,
>> Alona.
>>
>> On Thu, Jun 28, 2018, 12:23 Dafna Ron  wrote:
>>
>>> ovirt-hosted-engine-ha failed on the same issue as well.
>>>
>>> On Thu, Jun 28, 2018 at 10:07 AM, Dafna Ron  wrote:
>>>
 Hi,

 We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider.

 Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/9
 2567/ - packaging: Add python-netaddr requirement  I actually think
 from the error its because of changes made to multiqueues

 https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to
 consider vmBase.multiQueuesEnabled attribute
 https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for
 calculating how many queues asign per vnic
 https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled
 to VmBase
 https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues
 Enabled' to the relevant mappers
 https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues
 Enabled' to vm dialog

 Alona, can you please take a look?


 *Link to Job:*




 *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/
 Link
 to all
 logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifact/exported-artifacts/basic-suit.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/
 (Relevant)
 error snippet from the log: *
 *eng**ine: *

 2018-06-27 13:59:25,976-04 ERROR [org.ovirt.engine.core.vdsbrok
 er.vdsbroker.GetAllVmStatsVDSCommand] 
 (EE-ManagedThreadFactory-engineScheduled-Thread-80)
 [] Command 'GetAllVmStatsVDSCommand(HostName =
 lago-basic-suite-master-host-1, VdsIdVDSCommandParametersBase:
 {hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})' execution failed:
 VDSGenericException: VDSNetworkException: Broken pipe
 2018-06-27 13:59:25,977-04 DEBUG 
 [org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil]
 (EE-ManagedThreadFactory-engine-Thread-442) [] Executing task:
 EE-ManagedThreadFactory-engine-Thread-442
 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.common.
 di.interceptor.DebugLoggingInterceptor] 
 (EE-ManagedThreadFactory-engine-Thread-442)
 [] method: getVdsManager, params: [d9094c95-3275-4616-b4c2-815e753bcfed],
 timeElapsed: 0ms
 2018-06-27 13:59:25,977-04 WARN  
 [org.ovirt.engine.core.vdsbroker.VdsManager]
 (EE-ManagedThreadFactory-engine-Thread-442) [] Host
 'lago-basic-suite-master-host-1' is not responding.
 2018-06-27 13:59:25,979-04 ERROR [org.ovirt.engine.core.dal.dbb
 roker.auditloghandling.AuditLogDirector] 
 (EE-ManagedThreadFactory-engineScheduled-Thread-63)
 [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM
 lago-basic-suite-master-host-1 command GetStatsAsyncVDS failed: Broken pipe
 2018-06-27 13:59:25,976-04 DEBUG [org.ovirt.engine.core.vdsbrok
 er.vdsbroker.GetAllVmStatsVDSCommand] 
 (EE-ManagedThreadFactory-engineScheduled-Thread-80)
 [] Exception: org.ovirt.engine.core.vdsbroke
 r.vdsbroker.VDSNetworkException: VDSGenericException:
 VDSNetworkException: Broken pipe
 at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.
 proceedProxyReturnValue(BrokerCommandBase.java:189) [vdsbroker.jar:]
 at org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCo
 mmand.executeVdsBrokerCommand(GetAllVmStatsVDSCommand.java:23)
 [vdsbroker.jar:]
 at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.e
 xecuteVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
 [vdsbroker.jar:]
 at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.e
 xecuteVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:]
 at 
 org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65)
 [vdsbroker.jar:]
 at 
 org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31)
 [dal.jar:]
 at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandE
 xecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:]
 at 
 

[ovirt-devel] oVirt on Fedora 28 for developers

[Nir Soffer]

I want to share the current state of oVirt on Fedora 28, hopefully it will
save time for other developers.


1. Why should I run oVirt on Fedora 28?

- Fedora is the the base for future CentOS. The bugs we find *today* on
Fedora 28
are the bugs that we will not have next year when we try oVirt on CentOS.

- I want to contribute to projects that require python 3. For example,
virt-v2v
  require python 3.6 in upstream. If you want to contribute you need to test
  it on Fedora 28.

- I need to develop with latest libvirt and qemu. One example is incremental
  backup, you will need Fefora 28 to work on this.

- CentOS is old and boring, I want to play with the newest bugs :-)


2. How to install oVirt with Fedora 28 hosts

Warning: ugly hacks bellow!

- Install ovirt-release-master.rpm on all hosts

dnf install http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm

- Install or build engine on CentOS 7.5 (1804)[1]

- When provisioning a host, make sure you have lvm2-2.02.177-5.fc28
  without it, no block storage you[2]

- When adding a host, disable "Configure host firewall" - it does not work
now
  I hope that Sandro team will fix this issue soon.

- Adding a host will fail, because without firewall setup, port 54321 is
not reacable.
  to fix this, configure the firewall manually, or disable it

iptables -F

This is pretty lame because you have to apply it again after restart, but
it was
good enough for now.

- Because the host was not reachable, we don't configure the host network
  so the host will be non-operational.
  To fix this, open host > network > setup networks and assign ovirtmgmt
  to the host management nic. The host will become UP after that.
  I hope that Dan team will fix it soon.

- Adding storage will fail because sanlock selinux issue[3]
  To fix, set selinux to permissive mode:

  setenforce 0

At this point you should have a working setup.


3. Building and instaling vdsm from source on Fedora 28

- Install build dependencies using

  dnf install `cat automation/check-patch.packages.fc28`

- Clean the source (needed if you rerun ./autogen.sh with different options)

  git clean -dxf

- Configure vdsm with hooks - for some reason 2 hooks are required
  on Fedora but not on EL.

  ./autogen.sh --system --enable-hooks

- Build

  make
  make rpm

- Install the packages at /home/user/rpmbuild/RPMS/{noarch,x86_64}

- if vdsm was never installed, you need to configure and enable it

  vdsm-tool configure --force
  systemctl enable vdsmd
  systemctl start vdsmd

At this point you can test the new bugs you added to vdsm :-)


[1] I did not try to install engine on Fedora 28. I guess engine folks can
share if there are issues with this.

[2] https://bugzilla.redhat.com/1575762
LVM team fixed the issue couple of hours after I asked about it in #lvm
We had a build for testing couple of days later.

[3] https://bugzilla.redhat.com/1593853
We are still waiting for selinux folks response.

Happy hacking!

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/VZGOW5BWNY3DZJ7SUZFAWL7XB3FADF63/

[ovirt-devel] CVE-2018-3639 qemu-kvm-ev-2.10.0-21.el7_5.4.1 is now available for testing

[Sandro Bonazzola]

Hi, qemu-kvm-ev-2.10.0-21.el7_5.4.1 has been tagged for testing.
If nothing shows up, I'll tag it for release on Monday July 2nd.

Here's the changelog:

* Thu Jun 28 2018 Sandro Bonazzola  -
ev-2.10.0-21.el7_5.4.1
- Removing RH branding from package name

* Sat Jun 09 2018 Miroslav Rezanina  -
rhev-2.10.0-21.el7_5.4
- kvm-scsi-disk-allow-customizing-the-SCSI-version.patch [bz#1571370]
- kvm-hw-scsi-support-SCSI-2-passthrough-without-PI.patch [bz#1571370]
- kvm-i386-Define-the-Virt-SSBD-MSR-and-handling-of-it-CVE.patch
[bz#1584370]
- kvm-i386-define-the-AMD-virt-ssbd-CPUID-feature-bit-CVE-.patch
[bz#1584370]
- kvm-cpus-Fix-event-order-on-resume-of-stopped-guest.patch [bz#1582122]
- kvm-spec-Enable-Native-Ceph-support-on-all-architectures.patch
[bz#1588001]
- Resolves: bz#1571370
  (Pegas1.1 Alpha: SCSI pass-thru of aacraid RAID1 is inaccessible
(qemu-kvm-rhev) [rhel-7.5.z])
- Resolves: bz#1582122
  (IOERROR pause code lost after resuming a VM while I/O error is still
present [rhel-7.5.z])
- Resolves: bz#1584370
  (CVE-2018-3639 qemu-kvm-rhev: hw: cpu: AMD: speculative store bypass
[rhel-7.5.z])
- Resolves: bz#1588001
  (Enable Native Ceph support on non x86_64 CPUs [rhel-7.5.z])

For testing:

 $ sudo yum install centos-release-qemu-ev
 $ sudo yum-config-manager --enable centos-qemu-ev-test
 $ sudo yum update "qemu-kvm-ev*"

and use it as usual.


Thanks,
-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/3HECB2GMFXAA35EKLVZQGU24RQ6ZNHIF/

[ovirt-devel] Re: [VDSM] test_echo(1024, False) (stomp_test.StompTests) fails

[Piotr Kliczewski]

Nir,

It looks like we have a race condition where request arrive sooner than
subscribe frame:

*16:19:02* 2018-06-27 14:17:54,653 INFO  (jsonrpc/0)
[jsonrpc.JsonRpcServer] RPC call echo succeeded in 0.01 seconds
(__init__:311)*16:19:02* 2018-06-27 14:17:54,661 INFO  (Detector
thread) [Broker.StompAdapter] Subscribe command received
(stompserver:123)

Thanks for reporting I will push a patch to fix it.

Thanks,
Piotr


On Wed, Jun 27, 2018 at 5:40 PM, Piotr Kliczewski 
wrote:

> Ok, I'll take a look.
>
> śr., 27 cze 2018, 17:36 użytkownik Nir Soffer 
> napisał:
>
>> On Wed, Jun 27, 2018 at 6:13 PM Piotr Kliczewski 
>> wrote:
>>
>>> On Wed, Jun 27, 2018 at 5:01 PM, Nir Soffer  wrote:
>>>
 This tests used to fail in the past, but since we fixed it or the code

 it never failed.


 Maybe the slave was overloaded?


>>> Very possible. Can you paste a link to the job which failed?
>>>
>>
>> Here: https://jenkins.ovirt.org/job/vdsm_master_check-
>> patch-el7-x86_64/24130/
>>
>> The next build passed.
>>
>> Maybe we need to solve the flakiness of some tests by running a flaky test
>> again, and let the build fail only if a test failed twice. I wonder if
>> there is some
>> pytest plugin doing this.
>>
>>
>>>
>>>

 *14:19:02* 
 ==*14:19:02*
  ERROR:

 *14:19:02* 
 --*14:19:02*
  Traceback (most recent call last):*14:19:02*   File 
 "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testlib.py",
  line 143, in wrapper*14:19:02* return f(self, *args)*14:19:02*   File 
 "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/stomp_test.py",
  line 95, in test_echo*14:19:02* str(uuid4())),*14:19:02*   File 
 "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/lib/yajsonrpc/jsonrpcclient.py",
  line 77, in callMethod*14:19:02* raise 
 exception.JsonRpcNoResponseError(method=methodName)*14:19:02* 
 JsonRpcNoResponseError: No response for JSON-RPC request: {'method': 
 'echo'}*14:19:02*  >> begin captured logging << 
 *14:19:02* 2018-06-27 14:17:54,524 DEBUG (MainThread) 
 [vds.MultiProtocolAcceptor] Creating socket (host='::1', port=0, 
 family=10, socketype=1, proto=6) (protocoldetector:225)*14:19:02* 
 2018-06-27 14:17:54,526 INFO  (MainThread) [vds.MultiProtocolAcceptor] 
 Listening at ::1:36713 (protocoldetector:183)*14:19:02* 2018-06-27 
 14:17:54,535 DEBUG (MainThread) [Scheduler] Starting scheduler 
 test.Scheduler (schedule:98)*14:19:02* 2018-06-27 14:17:54,537 DEBUG 
 (test.Scheduler) [Scheduler] START thread >>> daemon 140562082535168)> (func=>>> >, args=(), kwargs={}) 
 (concurrent:193)*14:19:02* 2018-06-27 14:17:54,538 DEBUG (test.Scheduler) 
 [Scheduler] started (schedule:140)*14:19:02* 2018-06-27 14:17:54,546 DEBUG 
 (JsonRpc (StompReactor)) [root] START thread >>> (StompReactor), started daemon 140562629256960)> (func=>>> StompReactor.process_requests of >>> object at 0x7fd74ca006d0>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 
 2018-06-27 14:17:54,547 DEBUG (MainThread) [Executor] Starting executor 
 (executor:128)*14:19:02* 2018-06-27 14:17:54,549 DEBUG (MainThread) 
 [Executor] Starting worker jsonrpc/0 (executor:286)*14:19:02* 2018-06-27 
 14:17:54,553 DEBUG (jsonrpc/0) [Executor] START thread >>> started daemon 140562612471552)> (func=>>> >, args=(), 
 kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,554 DEBUG 
 (jsonrpc/0) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 
 14:17:54,557 DEBUG (MainThread) [Executor] Starting worker jsonrpc/1 
 (executor:286)*14:19:02* 2018-06-27 14:17:54,558 DEBUG (MainThread) 
 [Executor] Starting worker jsonrpc/2 (executor:286)*14:19:02* 2018-06-27 
 14:17:54,559 DEBUG (jsonrpc/2) [Executor] START thread >>> started daemon 140562620864256)> (func=>>> >, args=(), 
 kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,560 DEBUG 
 (jsonrpc/2) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 
 14:17:54,561 DEBUG (MainThread) [Executor] Starting worker jsonrpc/3 
 (executor:286)*14:19:02* 2018-06-27 14:17:54,562 DEBUG (jsonrpc/3) 
 [Executor] START thread >>> 140562124498688)> (func=>>> name=jsonrpc/3 waiting task#=0 at 0x7fd74bc80290>>, args=(), kwargs={}) 
 (concurrent:193)*14:19:02* 2018-06-27 14:17:54,563 DEBUG (jsonrpc/3) 
 [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,564 
 DEBUG (MainThread) [Executor] Starting worker jsonrpc/4 
 (executor:286)*14:19:02* 2018-06-27 14:17:54,565 DEBUG (jsonrpc/4) 
 [Executor] START thread >>> 140562116105984)> (func=>>> name=jsonrpc/4 waiting task#=0 at 0x7fd74bc80790>>, args=(), kwargs={}) 
 

[ovirt-devel] Re: [VDSM] Why hooks are required for installing vdsm?

[Nir Soffer]

On Thu, Jun 28, 2018 at 2:17 PM Dan Kenigsberg  wrote:

> On Thu, Jun 28, 2018 at 12:52 PM, Nir Soffer  wrote:
> > Trying to update vdsm master, my update script fail with:
> >
> > installing...
> > error: Failed dependencies:
> > vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
> > vdsm-hook-fcoe-4.30.0-429.git05bfb8731.fc28.noarch
> > vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
> > vdsm-hook-ethtool-options-4.30.0-429.git05bfb8731.fc28.noarch
> >
> > I tried to remove these hooks, since I'm not interested in any of them,
> but
> > removing them try to remove 136 packages including libvirt.
> >
> > Why do we have these dependencies? hook should be optional.
> >
> > Who owns these hooks?
>
> git log can tell you the usual answer: I'm to blame.
>
> These hooks implement documented features. I suspect that something
> very basic - such as the ovirt-host package - requires them to ensure
> that they exist on each host.
>

If the these hooks are required, we need to include them in the build
always - without using --enable-hooks. I think we did this with vmfex
hook.

We need an easy way to build vdsm from git and install it
on any decent platfrom. We can start by documenting the process.

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/4KZ645S7D6RO5FPFNXDWHFBJLEDPQKQQ/

[ovirt-devel] Re: [VDSM] Why hooks are required for installing vdsm?

[Dan Kenigsberg]

On Thu, Jun 28, 2018 at 12:52 PM, Nir Soffer  wrote:
> Trying to update vdsm master, my update script fail with:
>
> installing...
> error: Failed dependencies:
> vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
> vdsm-hook-fcoe-4.30.0-429.git05bfb8731.fc28.noarch
> vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
> vdsm-hook-ethtool-options-4.30.0-429.git05bfb8731.fc28.noarch
>
> I tried to remove these hooks, since I'm not interested in any of them, but
> removing them try to remove 136 packages including libvirt.
>
> Why do we have these dependencies? hook should be optional.
>
> Who owns these hooks?

git log can tell you the usual answer: I'm to blame.

These hooks implement documented features. I suspect that something
very basic - such as the ovirt-host package - requires them to ensure
that they exist on each host.

The motivation for having ovirt-host is to make sure all ovirt host
have "everything" they need. It makes installation errors and
questions less frequent, but it also makes it hard to tweak hosts and
to make them slimmer.


>
> Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/JUH4Z2KBXJGAJYLZTRWOV4KD5MKLBFAX/

[ovirt-devel] Re: [VDSM] Why hooks are required for installing vdsm?

[Nir Soffer]

On Thu, Jun 28, 2018 at 1:16 PM Nir Soffer  wrote:

> On Thu, Jun 28, 2018 at 12:52 PM Nir Soffer  wrote:
>
>> Trying to update vdsm master, my update script fail with:
>>
>> installing...
>> error: Failed dependencies:
>> vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
>> vdsm-hook-fcoe-4.30.0-429.git05bfb8731.fc28.noarch
>> vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
>> vdsm-hook-ethtool-options-4.30.0-429.git05bfb8731.fc28.noarch
>>
>> I tried to remove these hooks, since I'm not interested in any of them,
>> but
>> removing them try to remove 136 packages including libvirt.
>>
>> Why do we have these dependencies? hook should be optional.
>>
>> Who owns these hooks?
>>
>
> Strangely, the fcoe hook is not built by "make rpm":
>
> $ ls -1 noarch/
> vdsm-api-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-client-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-common-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-cpuflags-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-ethtool-options-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-faqemu-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-ipv6-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-localdisk-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-macspoof-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-openstacknet-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-qemucmdline-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-vfio-mdev-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-hook-vmfex-dev-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-http-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-jsonrpc-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-python-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-tests-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
> vdsm-yajsonrpc-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
>
> $ cat contrib/koji_build.sh
> echo 'Please run this script from vdsm main folder'
> echo ''
>
> make distclean
> ./autogen.sh \
> --system \
> --disable-ovirt-imageio \
> --disable-ovirt-vmconsole \
> --enable-vhostmd \
> --enable-hooks \
> --enable-containers \
> --with-data-center='/run/vdsm/data-center'
> make srpm
>
> echo
> echo 'Finish to compile VDSM for koji Fedora build'
> echo 'Use output srp.rpm to import fedpkg'
>
> Should be build for fedora using --enable-hooks?
>

Answering - --enable-hooks is required on Fedora.

In summary this is how to build vdsm for Fedora 28:

git clean -dxf
./autogen.sh --system --enable-hooks
make
make rpm

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/NYOG7FDEFB5LUXJWDV3DP4MAACPQENGL/

[ovirt-devel] Re: [VDSM] Why hooks are required for installing vdsm?

[Nir Soffer]

On Thu, Jun 28, 2018 at 12:52 PM Nir Soffer  wrote:

> Trying to update vdsm master, my update script fail with:
>
> installing...
> error: Failed dependencies:
> vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
> vdsm-hook-fcoe-4.30.0-429.git05bfb8731.fc28.noarch
> vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
> vdsm-hook-ethtool-options-4.30.0-429.git05bfb8731.fc28.noarch
>
> I tried to remove these hooks, since I'm not interested in any of them, but
> removing them try to remove 136 packages including libvirt.
>
> Why do we have these dependencies? hook should be optional.
>
> Who owns these hooks?
>

Strangely, the fcoe hook is not built by "make rpm":

$ ls -1 noarch/
vdsm-api-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-client-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-common-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-cpuflags-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-ethtool-options-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-faqemu-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-ipv6-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-localdisk-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-macspoof-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-openstacknet-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-qemucmdline-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-vfio-mdev-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-hook-vmfex-dev-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-http-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-jsonrpc-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-python-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-tests-4.30.0-435.git1fe2027bd.fc28.noarch.rpm
vdsm-yajsonrpc-4.30.0-435.git1fe2027bd.fc28.noarch.rpm

$ cat contrib/koji_build.sh
echo 'Please run this script from vdsm main folder'
echo ''

make distclean
./autogen.sh \
--system \
--disable-ovirt-imageio \
--disable-ovirt-vmconsole \
--enable-vhostmd \
--enable-hooks \
--enable-containers \
--with-data-center='/run/vdsm/data-center'
make srpm

echo
echo 'Finish to compile VDSM for koji Fedora build'
echo 'Use output srp.rpm to import fedpkg'

Should be build for fedora using --enable-hooks?

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/QTI4LQHSE3Z5442NPBBZL36AZP4X66ME/

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]

[Dafna Ron]

Thanks Alona,
Can you please update me once you have a fix?

Thanks,
Dafna


On Thu, Jun 28, 2018 at 10:28 AM, Alona Kaplan  wrote:

> Hi,
> I'm aware to the error. Francesco and me are working on it.
>
> Thank,
> Alona.
>
> On Thu, Jun 28, 2018, 12:23 Dafna Ron  wrote:
>
>> ovirt-hosted-engine-ha failed on the same issue as well.
>>
>> On Thu, Jun 28, 2018 at 10:07 AM, Dafna Ron  wrote:
>>
>>> Hi,
>>>
>>> We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider.
>>>
>>> Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/
>>> 92567/ - packaging: Add python-netaddr requirement  I actually think
>>> from the error its because of changes made to multiqueues
>>>
>>> https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to
>>> consider vmBase.multiQueuesEnabled attribute
>>> https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for
>>> calculating how many queues asign per vnic
>>> https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to
>>> VmBase
>>> https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues
>>> Enabled' to the relevant mappers
>>> https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues
>>> Enabled' to vm dialog
>>>
>>> Alona, can you please take a look?
>>>
>>>
>>> *Link to Job:*
>>>
>>>
>>>
>>>
>>> *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/
>>> Link
>>> to all
>>> logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifact/exported-artifacts/basic-suit.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/
>>> (Relevant)
>>> error snippet from the log: *
>>> *eng**ine: *
>>>
>>> 2018-06-27 13:59:25,976-04 ERROR [org.ovirt.engine.core.
>>> vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] 
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-80)
>>> [] Command 'GetAllVmStatsVDSCommand(HostName =
>>> lago-basic-suite-master-host-1, VdsIdVDSCommandParametersBase:
>>> {hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})' execution failed:
>>> VDSGenericException: VDSNetworkException: Broken pipe
>>> 2018-06-27 13:59:25,977-04 DEBUG 
>>> [org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil]
>>> (EE-ManagedThreadFactory-engine-Thread-442) [] Executing task:
>>> EE-ManagedThreadFactory-engine-Thread-442
>>> 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.common.
>>> di.interceptor.DebugLoggingInterceptor] 
>>> (EE-ManagedThreadFactory-engine-Thread-442)
>>> [] method: getVdsManager, params: [d9094c95-3275-4616-b4c2-815e753bcfed],
>>> timeElapsed: 0ms
>>> 2018-06-27 13:59:25,977-04 WARN  
>>> [org.ovirt.engine.core.vdsbroker.VdsManager]
>>> (EE-ManagedThreadFactory-engine-Thread-442) [] Host
>>> 'lago-basic-suite-master-host-1' is not responding.
>>> 2018-06-27 13:59:25,979-04 ERROR [org.ovirt.engine.core.dal.
>>> dbbroker.auditloghandling.AuditLogDirector] 
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-63)
>>> [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM
>>> lago-basic-suite-master-host-1 command GetStatsAsyncVDS failed: Broken pipe
>>> 2018-06-27 13:59:25,976-04 DEBUG [org.ovirt.engine.core.
>>> vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] 
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-80)
>>> [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
>>> VDSGenericException: VDSNetworkException: Broken pipe
>>> at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.
>>> proceedProxyReturnValue(BrokerCommandBase.java:189) [vdsbroker.jar:]
>>> at org.ovirt.engine.core.vdsbroker.vdsbroker.
>>> GetAllVmStatsVDSCommand.executeVdsBrokerCommand(
>>> GetAllVmStatsVDSCommand.java:23) [vdsbroker.jar:]
>>> at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.
>>> executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
>>> [vdsbroker.jar:]
>>> at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.
>>> executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:]
>>> at org.ovirt.engine.core.vdsbroker.VDSCommandBase.
>>> executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:]
>>> at 
>>> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31)
>>> [dal.jar:]
>>> at org.ovirt.engine.core.vdsbroker.vdsbroker.
>>> DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14)
>>> [vdsbroker.jar:]
>>> at org.ovirt.engine.core.vdsbroker.ResourceManager.
>>> runVdsCommand(ResourceManager.java:399) [vdsbroker.jar:]
>>> at org.ovirt.engine.core.vdsbroker.ResourceManager$
>>> Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source)
>>> [vdsbroker.jar:]
>>> at sun.reflect.GeneratedMethodAccessor270.invoke(Unknown
>>> Source) [:1.8.0_171]
>>> at 

[ovirt-devel] [VDSM] Why hooks are required for installing vdsm?

[Nir Soffer]

Trying to update vdsm master, my update script fail with:

installing...
error: Failed dependencies:
vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
vdsm-hook-fcoe-4.30.0-429.git05bfb8731.fc28.noarch
vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed)
vdsm-hook-ethtool-options-4.30.0-429.git05bfb8731.fc28.noarch

I tried to remove these hooks, since I'm not interested in any of them, but
removing them try to remove 136 packages including libvirt.

Why do we have these dependencies? hook should be optional.

Who owns these hooks?

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/NECJPEHOR6MHJYEPFYCHIGRVHOMGDTWL/

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]

[Alona Kaplan]

Hi,
I'm aware to the error. Francesco and me are working on it.

Thank,
Alona.

On Thu, Jun 28, 2018, 12:23 Dafna Ron  wrote:

> ovirt-hosted-engine-ha failed on the same issue as well.
>
> On Thu, Jun 28, 2018 at 10:07 AM, Dafna Ron  wrote:
>
>> Hi,
>>
>> We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider.
>>
>> Although CQ is pointing to this change:
>> https://gerrit.ovirt.org/#/c/92567/ - packaging: Add python-netaddr
>> requirement  I actually think from the error its because of changes made to
>> multiqueues
>>
>> https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to
>> consider vmBase.multiQueuesEnabled attribute
>> https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for
>> calculating how many queues asign per vnic
>> https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to
>> VmBase
>> https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues
>> Enabled' to the relevant mappers
>> https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues
>> Enabled' to vm dialog
>>
>> Alona, can you please take a look?
>>
>>
>> *Link to Job:*
>>
>>
>>
>>
>> *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/
>> Link
>> to all
>> logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifact/exported-artifacts/basic-suit.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/
>> (Relevant)
>> error snippet from the log: *
>> *eng**ine: *
>>
>> 2018-06-27 13:59:25,976-04 ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Command
>> 'GetAllVmStatsVDSCommand(HostName = lago-basic-suite-master-host-1,
>> VdsIdVDSCommandParametersBase:{hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})'
>> execution failed: VDSGenericException: VDSNetworkException: Broken pipe
>> 2018-06-27 13:59:25,977-04 DEBUG
>> [org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil]
>> (EE-ManagedThreadFactory-engine-Thread-442) [] Executing task:
>> EE-ManagedThreadFactory-engine-Thread-442
>> 2018-06-27 13:59:25,977-04 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (EE-ManagedThreadFactory-engine-Thread-442) [] method: getVdsManager,
>> params: [d9094c95-3275-4616-b4c2-815e753bcfed], timeElapsed: 0ms
>> 2018-06-27 13:59:25,977-04 WARN
>> [org.ovirt.engine.core.vdsbroker.VdsManager]
>> (EE-ManagedThreadFactory-engine-Thread-442) [] Host
>> 'lago-basic-suite-master-host-1' is not responding.
>> 2018-06-27 13:59:25,979-04 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] EVENT_ID:
>> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM lago-basic-suite-master-host-1
>> command GetStatsAsyncVDS failed: Broken pipe
>> 2018-06-27 13:59:25,976-04 DEBUG
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Exception:
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
>> VDSGenericException: VDSNetworkException: Broken pipe
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:189)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand.executeVdsBrokerCommand(GetAllVmStatsVDSCommand.java:23)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31)
>> [dal.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:399)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown
>> Source) [vdsbroker.jar:]
>> at sun.reflect.GeneratedMethodAccessor270.invoke(Unknown Source)
>> [:1.8.0_171]
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> [rt.jar:1.8.0_171]
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> [rt.jar:1.8.0_171]
>> at
>> 

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]

[Dafna Ron]

ovirt-hosted-engine-ha failed on the same issue as well.

On Thu, Jun 28, 2018 at 10:07 AM, Dafna Ron  wrote:

> Hi,
>
> We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider.
>
> Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/
> 92567/ - packaging: Add python-netaddr requirement  I actually think from
> the error its because of changes made to multiqueues
>
> https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to
> consider vmBase.multiQueuesEnabled attribute
> https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for
> calculating how many queues asign per vnic
> https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to
> VmBase
> https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled'
> to the relevant mappers
> https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues
> Enabled' to vm dialog
>
> Alona, can you please take a look?
>
>
> *Link to Job:*
>
>
>
>
> *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/
> Link
> to all
> logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifact/exported-artifacts/basic-suit.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/
> (Relevant)
> error snippet from the log: *
> *eng**ine: *
>
> 2018-06-27 13:59:25,976-04 ERROR [org.ovirt.engine.core.
> vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-80)
> [] Command 'GetAllVmStatsVDSCommand(HostName =
> lago-basic-suite-master-host-1, VdsIdVDSCommandParametersBase:
> {hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})' execution failed:
> VDSGenericException: VDSNetworkException: Broken pipe
> 2018-06-27 13:59:25,977-04 DEBUG 
> [org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil]
> (EE-ManagedThreadFactory-engine-Thread-442) [] Executing task:
> EE-ManagedThreadFactory-engine-Thread-442
> 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.common.
> di.interceptor.DebugLoggingInterceptor] 
> (EE-ManagedThreadFactory-engine-Thread-442)
> [] method: getVdsManager, params: [d9094c95-3275-4616-b4c2-815e753bcfed],
> timeElapsed: 0ms
> 2018-06-27 13:59:25,977-04 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager]
> (EE-ManagedThreadFactory-engine-Thread-442) [] Host
> 'lago-basic-suite-master-host-1' is not responding.
> 2018-06-27 13:59:25,979-04 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-63)
> [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM
> lago-basic-suite-master-host-1 command GetStatsAsyncVDS failed: Broken pipe
> 2018-06-27 13:59:25,976-04 DEBUG [org.ovirt.engine.core.
> vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-80)
> [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> VDSGenericException: VDSNetworkException: Broken pipe
> at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.
> proceedProxyReturnValue(BrokerCommandBase.java:189) [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbroker.vdsbroker.
> GetAllVmStatsVDSCommand.executeVdsBrokerCommand(
> GetAllVmStatsVDSCommand.java:23) [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.
> executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
> [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.
> executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbroker.VDSCommandBase.
> executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:]
> at 
> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31)
> [dal.jar:]
> at org.ovirt.engine.core.vdsbroker.vdsbroker.
> DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14)
> [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbroker.ResourceManager.
> runVdsCommand(ResourceManager.java:399) [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbroker.ResourceManager$
> Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source)
> [vdsbroker.jar:]
> at sun.reflect.GeneratedMethodAccessor270.invoke(Unknown Source)
> [:1.8.0_171]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171]
> at java.lang.reflect.Method.invoke(Method.java:498)
> [rt.jar:1.8.0_171]
> at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocation
> Context.proceedInternal(TerminalAroundInvokeInvocationContext.java:49)
> [weld-core-impl-2.4.3.Final.jar:2.4.3.Final]
> at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.
> 

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]

[Dafna Ron]

Hi,

We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider.

Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/92567/
- packaging: Add python-netaddr requirement  I actually think from the
error its because of changes made to multiqueues

https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to
consider vmBase.multiQueuesEnabled attribute
https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for
calculating how many queues asign per vnic
https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to
VmBase
https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled'
to the relevant mappers
https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues Enabled'
to vm dialog

Alona, can you please take a look?


*Link to Job:*




*http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/
Link
to all
logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifact/exported-artifacts/basic-suit.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/
(Relevant)
error snippet from the log: *
*eng**ine: *

2018-06-27 13:59:25,976-04 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Command
'GetAllVmStatsVDSCommand(HostName = lago-basic-suite-master-host-1,
VdsIdVDSCommandParametersBase:{hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})'
execution failed: VDSGenericException: VDSNetworkException: Broken pipe
2018-06-27 13:59:25,977-04 DEBUG
[org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil]
(EE-ManagedThreadFactory-engine-Thread-442) [] Executing task:
EE-ManagedThreadFactory-engine-Thread-442
2018-06-27 13:59:25,977-04 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(EE-ManagedThreadFactory-engine-Thread-442) [] method: getVdsManager,
params: [d9094c95-3275-4616-b4c2-815e753bcfed], timeElapsed: 0ms
2018-06-27 13:59:25,977-04 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(EE-ManagedThreadFactory-engine-Thread-442) [] Host
'lago-basic-suite-master-host-1' is not responding.
2018-06-27 13:59:25,979-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-63) [] EVENT_ID:
VDS_BROKER_COMMAND_FAILURE(10,802), VDSM lago-basic-suite-master-host-1
command GetStatsAsyncVDS failed: Broken pipe
2018-06-27 13:59:25,976-04 DEBUG
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Exception:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Broken pipe
at
org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:189)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand.executeVdsBrokerCommand(GetAllVmStatsVDSCommand.java:23)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65)
[vdsbroker.jar:]
at
org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31)
[dal.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:399)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown
Source) [vdsbroker.jar:]
at sun.reflect.GeneratedMethodAccessor270.invoke(Unknown Source)
[:1.8.0_171]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_171]
at java.lang.reflect.Method.invoke(Method.java:498)
[rt.jar:1.8.0_171]
at
org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49)
[weld-core-impl-2.4.3.Final.jar:2.4.3.Final]
at
org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77)
[weld-core-impl-2.4.3.Final.jar:2.4.3.Final]
at
org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12)
[common.jar:]
at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
[:1.8.0_171]
at

[ovirt-devel] Re: [ovirt-users] oVirt HCI point-to-point interconnection

[Stefano Zappa]

Hi Yaniv,
no, the final purpose is not to save a couple of ports.

The benefit is the trend to convergence and consolidation of the networking, as 
already done for the storage.
The external interconnection is a critical element of the HCI solution, a 
configuration without switches would give more soundness and more independence.

If we think about HCI as the transition of IT infrastructure from 
hardware-defined to software-defined, the first step was virtualization of the 
servers, the second step was storage virtualization, the third step will be 
virtualization of networking.

Of course this also has an economic benefit, reduce the total cost of ownership 
and traditional data-center inefficiencies.

We suppose a very traditional and simple external uplink, we can use the 
interfaces integrated into the motherboard.
This will not be critical for the integrity of the our HCI solution, this will 
not require broad bandwidth and low latency, this will be used exclusively to 
interconnect the solution with the outside world, then with a traditional 
ethernet switch.

We suppose to give more attention to the point-to-point interconnection of the 
three nodes, using 100 or 200 GbE cards for direct interconnection without 
switches.
The hypothetical purchase of these 3 cards will not be cheaper, sure, but it 
will be twenty times less than introducing expensive switches that will 
certainly have more ports than necessary.

Thanks for your attention,
Stefano.




Stefano Zappa
IT Specialist CAE - TT-3
Technical Department

Industrie Saleri Italo S.p.A.
Phone:+39 0308250480
Fax:+39 0308250466

This message contains confidential information and is intended only for 
yk...@redhat.com, sab...@redhat.com, sbona...@redhat.com, devel@ovirt.org, 
us...@ovirt.org. If you are not yk...@redhat.com, sab...@redhat.com, 
sbona...@redhat.com, devel@ovirt.org, us...@ovirt.org you should not 
disseminate, distribute or copy this e-mail. Please notify 
stefano.za...@saleri.it immediately by e-mail if you have received this e-mail 
by mistake and delete this e-mail from your system. E-mail transmission cannot 
be guaranteed to be secure or error-free as information could be intercepted, 
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
Stefano Zappa therefore does not accept liability for any errors or omissions 
in the contents of this message, which arise as a result of e-mail 
transmission. If verification is required please request a hard-copy version.

Da: Yaniv Kaul 
Inviato: mercoledì 27 giugno 2018 16:20
A: Stefano Zappa
Cc: Sahina Bose; Sandro Bonazzola; devel@ovirt.org; us...@ovirt.org
Oggetto: Re: [ovirt-devel] Re: [ovirt-users] oVirt HCI point-to-point 
interconnection

On Wed, Jun 27, 2018 at 11:26 AM, Stefano Zappa 
mailto:stefano.za...@saleri.it>> wrote:
The final purpose is strictly targeted to your HCI solution with 3-node gluster 
replication.

Can you explain to me what the benefit is? You need a switch anyway (for 
uplink), so the 'cost saving' is that you can use a 4 port (?) switch and do 
not need 6 ports?
Y.





Stefano Zappa
IT Specialist CAE - TT-3
Technical Department

Industrie Saleri Italo S.p.A.
Phone:+39 0308250480
Fax:+39 0308250466

This message contains confidential information and is intended only for 
sab...@redhat.com, 
sbona...@redhat.com, 
stira...@redhat.com, 
us...@ovirt.org, 
devel@ovirt.org. If you are not 
sab...@redhat.com, 
sbona...@redhat.com, 
stira...@redhat.com, 
us...@ovirt.org, 
devel@ovirt.org you should not disseminate, distribute 
or copy this e-mail. Please notify 
stefano.za...@saleri.it immediately by e-mail 
if you have received this e-mail by mistake and delete this e-mail from your 
system. E-mail transmission cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Stefano Zappa therefore does not accept 
liability for any errors or omissions in the contents of this message, which 
arise as a result of e-mail transmission. If verification is required please 
request a hard-copy version.

Da: Sahina Bose mailto:sab...@redhat.com>>
Inviato: mercoledì 27 giugno 2018 10:15
A: Sandro Bonazzola
Cc: Stefano Zappa; Simone Tiraboschi; us...@ovirt.org; 
devel@ovirt.org
Oggetto: Re: [ovirt-users] oVirt HCI point-to-point interconnection

The point to point interconnect is something we have not explored - I think 
this limits the solution from scaling out to more nodes.

On Wed, Jun 27, 2018 at 1:22 PM, Sandro Bonazzola