[ovirt-devel] Really slow VDSM on F21

2014-12-02 Thread Petr Horacek 
Hello,

has anyone else noticed VDSM's problems on Fedora 21?

The problem is that when I start vdsmd via systemd, it takes
about a minute to start the listener (returning Connection
to 0.0.0.0:54321 refused) and next few minutes it returns
'Recovering from crash or Initializing'. After that, `getVdsCaps`
takes cca 20 secs to finish.

I tried to change niceness in vdsmd.service but it's still the same.

When I start vdsm directly (/usr/share/vdsm/vdsm as vdsm user) it
starts within a second as it should.

Have you an idea why this happens?

Best regards,
Petr
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Really slow VDSM on F21

2014-12-03 Thread Petr Horacek 
Cc: Dan.

- Original Message -
 From: Petr Horacek phora...@redhat.com
 To: devel@ovirt.org, Francesco Romani from...@redhat.com
 Sent: Tuesday, 2 December, 2014 12:39:58 PM
 Subject: Really slow VDSM on F21
 
 Hello,
 
 has anyone else noticed VDSM's problems on Fedora 21?
 
 The problem is that when I start vdsmd via systemd, it takes
 about a minute to start the listener (returning Connection
 to 0.0.0.0:54321 refused) and next few minutes it returns
 'Recovering from crash or Initializing'. After that, `getVdsCaps`
 takes cca 20 secs to finish.
 
 I tried to change niceness in vdsmd.service but it's still the same.
 
 When I start vdsm directly (/usr/share/vdsm/vdsm as vdsm user) it
 starts within a second as it should.
 
 Have you an idea why this happens?
 
 Best regards,
 Petr
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Really slow VDSM on F21

2014-12-11 Thread Petr Horacek 
Hello Ido,

thanks for your response! I installed the latest Fedora 21 Server on a VM,
builded VDSM's master branch and now it works as it should :)

Petr

- Original Message -
 From: Ido Barkan ibar...@redhat.com
 To: Petr Horacek phora...@redhat.com
 Cc: devel@ovirt.org, Francesco Romani from...@redhat.com
 Sent: Thursday, December 11, 2014 2:21:58 PM
 Subject: Re: [ovirt-devel] Really slow VDSM on F21
 
 Hey Petr,
 
 I have just ran a few functional tests on my laptop after upgrading it to
 F21. Both 'service vdsmd stop  sudo service vdsmd start' and
 'systemctl vdsmd restart' return fast and succeed.
 
 Also, running the entire networkTest suite takes about 628 sec which is
 reasonable compared to F20 on the same laptop.
 
 I think that hints in the direction of the Jenkins instance is a VM.
 
 Ido
 
 - Original Message -
 From: Petr Horacek phora...@redhat.com
 To: devel@ovirt.org, Francesco Romani from...@redhat.com
 Sent: Wednesday, December 3, 2014 11:09:03 AM
 Subject: Re: [ovirt-devel] Really slow VDSM on F21
 
 Cc: Dan.
 
 - Original Message -
  From: Petr Horacek phora...@redhat.com
  To: devel@ovirt.org, Francesco Romani from...@redhat.com
  Sent: Tuesday, 2 December, 2014 12:39:58 PM
  Subject: Really slow VDSM on F21
  
  Hello,
  
  has anyone else noticed VDSM's problems on Fedora 21?
  
  The problem is that when I start vdsmd via systemd, it takes
  about a minute to start the listener (returning Connection
  to 0.0.0.0:54321 refused) and next few minutes it returns
  'Recovering from crash or Initializing'. After that, `getVdsCaps`
  takes cca 20 secs to finish.
  
  I tried to change niceness in vdsmd.service but it's still the same.
  
  When I start vdsm directly (/usr/share/vdsm/vdsm as vdsm user) it
  starts within a second as it should.
  
  Have you an idea why this happens?
  
  Best regards,
  Petr
 ___
 Devel mailing list
 Devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel
 
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.6.0 status

2015-10-15 Thread Petr Horacek 
Hi, we think this bug is caused by systemd bug [1], which was solved in
systemd v220,
unfortunately, this version is not available for EL7. As soon as we proof
the issue, we
should ask systemd guys for backporting the solution.

[1] https://bugs.freedesktop.org/show_bug.cgi?id=86520

2015-10-06 15:11 GMT+02:00 Dan Kenigsberg :

> On Sun, Oct 04, 2015 at 02:37:35PM +0200, Sven Kieske wrote:
> > On 02.10.2015 13:19, Dan Kenigsberg wrote:
> > > Annoys automated QA, but not seen in manual checks. I'm not sure it
> > > should block ovirt-3.6.0. I'd love to hear if a lot of ovirt users use
> > > automated scripts with no retries to setup host networking.
> >
> > Yes, of course I do.
> >
> > And I don't see a reason to retry a failed automatic setup
> > automatically. this way lies madness.
>
> Point taken!
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] VDSM Broken dependencies on master

2015-09-17 Thread Petr Horacek 
Hello,

I tried
https://repos.fedorapeople.org/repos/openstack/openstack-liberty/testing/el7/
but it seems like there is no openvswitch in it.

However, openstack-kilo is ok.

Petr



2015-09-17 13:47 GMT+02:00 Sandro Bonazzola :

>
>
> On Thu, Sep 17, 2015 at 1:11 PM, Dan Kenigsberg  wrote:
>
>> On Thu, Sep 17, 2015 at 09:17:55AM +0200, Sandro Bonazzola wrote:
>> > *Hi:*
>> >
>> > *06:37:41* package: vdsm-hook-ovs-4.17.2-142.git932c120.el7.noarch
>> > from check-custom-el7
>> >
>> > *06:37:41*   unresolved deps:
>> >
>> > *06:37:41*  openvswitch >= 0:2
>> >
>> >
>> >
>> http://jenkins.ovirt.org/job/repos_master_check-closure_merged/DISTRIBUTION=centos7/707/console
>> >
>> > Please provide the missing dependency or drop it ASAP.
>>
>> Petr, we've forgotten about this job, apparently.
>>
>> Sandro, can we exclude vdsm-hook-ovs from the closure job? It is still
>> rather a step-offstpring of Vdsm which is less acute to test.
>>
>> However, can we instead add
>> https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/
>> to the repos available to this job?
>>
>>
> Juno? Aren't we using Kilo? And being master, what about Liberty?
>
>
>
>> https://gerrit.ovirt.org/#/c/46135/3/automation/check-patch.repos.el7
>> attempts to do so to the per-patch rpm installation job.
>>
>> Dan.
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Automation CI for vdsm

2015-12-17 Thread Petr Horacek 
Hi,

OVSNetworkTest requires vdsm-hook-ovs installed (tests are not skipped
if the package is not installed) and openvswitch service running (not
started automatically). NetworkTest are not able to run together with
OVSNetworkTest since we are doing ugly inheritance hacking there. My
apologize for network tests difficulties, it will be resolved soon. If
you want your life easier, temporary skip OVSNetworkTest suite and it
should be OK.

Best regards,
Petr

2015-12-16 17:25 GMT+01:00 Yaniv Bronheim :
> exactly - just posted a patch again that sings all fails as broken .
> we'll get the report soon and I'll publish it as well. hope the run will
> take less time now
>
> On Wed, Dec 16, 2015 at 6:19 PM, Nir Soffer  wrote:
>>
>> Nice, but we cannot enable this until all the tests pass or disabled.
>>
>> There is no point in broken or flaky functional tests.
>>
>> On Wed, Dec 16, 2015 at 5:34 PM, Yaniv Bronheim 
>> wrote:
>> > So its not stable. It won't block merges and at least give us report
>> > after
>> > each merge. It takes really long time to run it (because of the tests
>> > themselves. Lago things takes maximum 15minutes, but the run last for
>> > more
>> > than 2hrs right now and I suspect functional/storageTests.py gets stuck)
>> >
>> > Bellow you can see where we stand (before I added python-rtslib
>> > package).
>> >
>> > Now, I still want to merge the patch https://gerrit.ovirt.org/#/c/48268/
>> > -
>> > which enables this run after merges, and I still want you to consider
>> > the
>> > addition of Automation CI flag to our gerrit so that developer will be
>> > able
>> > to use it as a trigger for the check-merged.sh script run, just to see
>> > if
>> > their patch fixes\brakes something realted to the functional tests
>> >
>> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1480/ -
>> > is
>> > an example of how the run looks like. I still work to improve the output
>> >
>> >
>> > Please reply and let me know if the idea around the automation flag is
>> > acceptable by you.. and please review the patch for comments and acks.
>> > We can ask dcaro to add the flag until Friday, otherwise we'll need to
>> > delay
>> > this effort after the holiday..
>> >
>> >
>> > functional.sosPluginTests.SosPluginTest
>> > testSosPlugin   OK
>> > functional.vmRecoveryTests.RecoveryTests
>> > test_vm_recoveryFAIL
>> > functional.vmQoSTests.VMQosTests
>> > testSmallVMBallooning   FAIL
>> > functional.virtTests.VirtTest
>> > testComplexVm   FAIL
>> > testHeadlessVm  OK
>> > testSimpleVmFAIL
>> > testVmDefinitionGraphics('spice')   FAIL
>> > testVmDefinitionGraphics('vnc') OK
>> > testVmDefinitionLegacyGraphics('qxl')   FAIL
>> > testVmDefinitionLegacyGraphics('vnc')   OK
>> > testVmDefinitionMultipleGraphics('spice', 'vnc')FAIL
>> > testVmDefinitionMultipleGraphics('vnc', 'spice')FAIL
>> > testVmWithCdrom('self') FAIL
>> > testVmWithCdrom('specParams')   FAIL
>> > testVmWithCdrom('vmPayload')FAIL
>> > testVmWithDevice('hotplugDisk') FAIL
>> > testVmWithDevice('hotplugNic')  FAIL
>> > testVmWithDevice('smartcard')   FAIL
>> > testVmWithDevice('virtioNic')   FAIL
>> > testVmWithDevice('virtioRng')   FAIL
>> > testVmWithSla   FAIL
>> > testVmWithStorage('iscsi')  SKIP:
>> > python-rtslib is not installed.
>> > testVmWithStorage('localfs')FAIL
>> > testVmWithStorage('nfs')FAIL
>> > functional.storageTests.StorageTest
>> > testCreatePoolErrorsOK
>> > testStorage('glusterfs', 0) ERROR
>> > testStorage('glusterfs', 3) ERROR
>> > testStorage('iscsi', 0) SKIP:
>> > python-rtslib is not installed.
>> > testStorage('iscsi', 3) SKIP:
>> > python-rtslib is not installed.
>> > testStorage('localfs', 0)   FAIL
>> > testStorage('localfs', 3)   FAIL
>> > testStorage('nfs', 0)   FAIL
>> > testStorage('nfs', 3)

Re: [ovirt-devel] VDSM dependency broken on 3.6 branch

2015-12-19 Thread Petr Horacek 
Hello,

we have to backport https://gerrit.ovirt.org/#/c/46594/, reason is
described there:

"In CentOS, where Epoch is not used, >= 2 is interpreted as >= 0:2,
that is causing dependency problems This patch changes it to >= 2.0.0"

Petr

2015-12-19 11:03 GMT+01:00 Oved Ourfali :
> CC-ing Dan.
> However, note that this is a dependency of a hook, and hooks aren't
> mandatory for installation of VDSM.
>
> Regards,
> Oved
>
> On Dec 18, 2015 18:23, "Sandro Bonazzola"  wrote:
>>
>> 06:49:19 package: vdsm-hook-ovs-4.17.13-31.git8bb3de9.el7.centos.noarch
>> from check-custom-el7
>> 06:49:19   unresolved deps:
>> 06:49:19  openvswitch >= 0:2
>> 06:49:19 package: vdsm-hook-ovs-4.17.13-33.git6fb5413.el7.centos.noarch
>> from check-custom-el7
>> 06:49:19   unresolved deps:
>> 06:49:19  openvswitch >= 0:2
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ovirt-users] How to add ovs-based VM in version 4.0.2? Thank you

2016-08-02 Thread Petr Horacek 
Clean == host that has just NICs, like right after system installation
(no networks created by VDSM, bridges, bonds, vlans). Anyway, VDSM OVS
is not able to acquire external NICs yet (the patch is under review
and will be merged to master soon [1]).

I would recommend you to wait for VDSM with mentioned patch merged. If
you cannot wait, you can try to setup ovirtmgmt network manually via
console (turn down NIC, setup OVS network on top of it). Not sure if
this would help you.

[1] https://gerrit.ovirt.org/#/c/60404/29

2016-08-02 13:30 GMT+02:00 lifuqiong <lifuqi...@cncloudsec.com>:
> Hi Petr,
> Thank you for your advice. But what does "Clean hosts" mean, as I 
> know now, When you add a clean Host to ovirt engine, the vdsm or ovirt node 
> will create a Network named ovirtmgmt, which is an Linux bridge network,
> How do I clean the network? Just delete the linux bridge and reset the linux 
> bridge binding's physical Nic?
>
> Hope to get your help as sonn as possible.
> Thank you.
>     Mark
>
> -邮件原件-
> 发件人: Petr Horacek [mailto:phora...@redhat.com]
> 发送时间: 2016年8月2日 18:29
> 收件人: lifuqiong
> 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; users
> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version 4.0.2? 
> Thank you
>
> If the host was a part of legacy cluster you must do manual cleanup of all 
> networks. Currently VDSM cannot change Linux bridges into OVS ones (this will 
> be implemented soon). Make sure that you are adding clean hosts (with NIC 
> interface/s only) to OVS cluster.
>
> Regards,
> Petr
>
> 2016-08-02 10:01 GMT+02:00 Michael Burman <mbur...@redhat.com>:
>> Hi ,
>>
>> Did you synced network/s after you moved the host to the ovs type cluster?
>> It seems like you didn't..)
>> Go to 'Hosts' main tab' and choose the host, go to 'Network
>> Interfaces' sub tab and press the 'Sync All Networks' , now the
>> networks should be synced to host as ovs switch type.
>> Run the vm and check the xml.
>> It should look something like this:
>>
>> 
>>   
>>
>> thanks
>>
>>
>> On Tue, Aug 2, 2016 at 9:37 AM, Meni Yakove <myak...@redhat.com> wrote:
>>>
>>>
>>>
>>> On Tue, Aug 2, 2016 at 7:12 AM, lifuqiong <lifuqi...@cncloudsec.com>
>>> wrote:
>>>>
>>>> I create a cluster which already enabled ovs network as you
>>>> mentioned , but when I create vm in this cluster,  I can only using
>>>> ovirtmgmt/ovirtmgmt vNIC profile, which is still a Linux bridge.
>>>>
>>>> I found no way to add a OVS vNIC profile,  I have to chose
>>>> ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the vm
>>>> is still using Linux bridge to communicate with outside, not the ovs.
>>>>
>>>>
>>>>
>>>> Need I to create a ovs bridge or vport and bind it to physical NIC
>>>> in vdsm manually?
>>>>
>>>>
>>>>
>>>> Hope your reply as soon as possible.
>>>>
>>>> Thank you
>>>>
>>>> Mark
>>>>
>>>>
>>>>
>>>> 发件人: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] 代表
>>>> Meni Yakove
>>>> 发送时间: 2016年8月1日 16:42
>>>> 收件人: Dan Kenigsberg
>>>> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in
>>>> version 4.0.2? Thank you
>>>>
>>>>
>>>>
>>>> On Mon, Aug 1, 2016 at 11:07 AM, Dan Kenigsberg <dan...@redhat.com>
>>>> wrote:
>>>>
>>>> On Mon, Aug 01, 2016 at 02:02:52PM +0800, lifuqiong wrote:
>>>> > Hi, I upgrade my ovirt to version 4.0.2.2, how to using ovs in
>>>> > this version?
>>>> > Is there any instruction? Thank you
>>>>
>>>> Please note and note well: OVS is not production-grade yet. It is
>>>> only a preliminary tech preview, under active development.
>>>>
>>>> However, we'd be very happy to get your help in testing it (and
>>>> possibly fixing it, too).
>>>>
>>>> When defining a new cluster, you should see a check box, letting you
>>>> select OVS for that cluster.
>>>>
>>>>
>>>>
>>>> To be precise, this is not a check box. In the Edit Cluster dialog,
>>>> look at the "switch
>>>>
>>>> type" option, and change "LEGACY" to "OVS".
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> After being checked, each VM network that is defined in your cluster
>>>> would be implemented with OVS instead of Linux bridge.
>>>>
>>>> As aluded before, there are plenty of known definciencies (e.g., no
>>>> persistence of ip config on VM network, no live migration, not all
>>>> bond modes, etc etc). But do not hesitate to raise other issues with
>>>> the devel mailing list.
>>>>
>>>> Happy testing!
>>>>
>>>> Dan.
>>>> ___
>>>> Devel mailing list
>>>> Devel@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Michael Burman
>> RedHat Israel, RHEV-M QE Network Team
>>
>> Mobile: 054-5355725
>> IRC: mburman
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ovirt-users] How to add ovs-based VM in version 4.0.2? Thank you

2016-08-03 Thread Petr Horacek 
Hello,

don't forget you still need latest patches which are not part of
ovirt-release40 nor ovirt-release-master.

Network setup is handled by supervdsmd.service, logs are located in
/var/log/vdsm/supervdsm.log. Network API entrypoint is in
/usr/lib/python2.7/site-packages/vdsm/network/api.py.

2016-08-03 9:58 GMT+02:00 lifuqiong <lifuqi...@cncloudsec.com>:
> Hi petr,
> I followed your instruction last mail, re-install an Centos 7.2 
> 1503(ip:192.168.0.117), and executing 'yum install 
> http://plain.resources.ovirt.org/pub/ovirt-4.0-pre/rpm/el7/noarch/ovirt-release40-pre.rpm'
>  On the new system.
>
> Creating an cluster using ovs-based network, and install 
> vdsm(192.168.0.117); deploy log shows that meeting an error as follows: But I 
> cann't find out the code which implements the function of setupNetworks,
>
> Just find the setupNetwork() function was defined in API.py, what does this 
> function do actually, where is the code ? and how to fix this error?
>
> jsonrpc.Executor/4::ERROR::2016-08-02 
> 22:35:03,321::__init__::549::jsonrpc.JsonRpcServer::(_handle_request) 
> Internal server error
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 544, in 
> _handle_request
> res = method(**params)
>   File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 195, in 
> _dynamicMethod
> result = fn(*methodArgs)
>   File "/usr/share/vdsm/API.py", line 1465, in setupNetworks
> supervdsm.getProxy().setupNetworks(networks, bondings, options)
>   File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in 
> __call__
> return callMethod()
>   File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in 
> 
> **kwargs)
>   File "", line 2, in setupNetworks
>   File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in 
> _callmethod
>     raise convert_to_error(kind, result)
> IPRoute2Error: ['RTNETLINK answers: File exists']
>
>
> Hope get your help asp.
> Thank you
> Mark
>
>
> -邮件原件-
> 发件人: Petr Horacek [mailto:phora...@redhat.com]
> 发送时间: 2016年8月3日 1:50
> 收件人: lifuqiong
> 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; devel
> 主题: Re: 答复: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version 
> 4.0.2? Thank you
>
> If everything goes well, it will be in master this week. I don't know when it 
> will be part of 4.0.
>
> I installed master VDSM patched with
> https://gerrit.ovirt.org/#/q/topic:ovs_acquire on my host (Fedora 23 with 
> disabled NetworkManager) and it worked OK. You can try to build it on your 
> own [1]. If you hit any problem, feel free to ask.
>
> We'd like to go that way, but nothing specific yet.
>
> [1] http://www.ovirt.org/develop/developer-guide/vdsm/developers/
>
> 2016-08-02 14:15 GMT+02:00 lifuqiong <lifuqi...@cncloudsec.com>:
>> Hi Petr,
>>     Thank you
>> When the patch will merge to master? And when will the vdsm will 
>> release a version with this patch?
>> Btw, do you have a plan to support ovs with dpdk or vhost-user port? 
>>  If so, what's the pipeline?
>>
>> Thank you
>>
>> -邮件原件-
>> 发件人: Petr Horacek [mailto:phora...@redhat.com]
>> 发送时间: 2016年8月2日 19:53
>> 收件人: lifuqiong
>> 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; devel
>> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version
>> 4.0.2? Thank you
>>
>> Clean == host that has just NICs, like right after system installation (no 
>> networks created by VDSM, bridges, bonds, vlans). Anyway, VDSM OVS is not 
>> able to acquire external NICs yet (the patch is under review and will be 
>> merged to master soon [1]).
>>
>> I would recommend you to wait for VDSM with mentioned patch merged. If you 
>> cannot wait, you can try to setup ovirtmgmt network manually via console 
>> (turn down NIC, setup OVS network on top of it). Not sure if this would help 
>> you.
>>
>> [1] https://gerrit.ovirt.org/#/c/60404/29
>>
>> 2016-08-02 13:30 GMT+02:00 lifuqiong <lifuqi...@cncloudsec.com>:
>>> Hi Petr,
>>> Thank you for your advice. But what does "Clean hosts" mean,
>>> as I know now, When you add a clean Host to ovirt engine, the vdsm or ovirt 
>>> node will create a Network named ovirtmgmt, which is an Linux bridge 
>>> network, How do I clean the network? Just delete the linux bridge and reset 
>>> the linux bridge binding's physical Nic?
>>>
>>> Hope to get your help as sonn as possible.

Re: [ovirt-devel] 答复: [ovirt-users] How to add ovs-based VM in version 4.0.2? Thank you

2016-08-02 Thread Petr Horacek 
If everything goes well, it will be in master this week. I don't know
when it will be part of 4.0.

I installed master VDSM patched with
https://gerrit.ovirt.org/#/q/topic:ovs_acquire on my host (Fedora 23
with disabled NetworkManager) and it worked OK. You can try to build
it on your own [1]. If you hit any problem, feel free to ask.

We'd like to go that way, but nothing specific yet.

[1] http://www.ovirt.org/develop/developer-guide/vdsm/developers/

2016-08-02 14:15 GMT+02:00 lifuqiong <lifuqi...@cncloudsec.com>:
> Hi Petr,
> Thank you
> When the patch will merge to master? And when will the vdsm will 
> release a version with this patch?
> Btw, do you have a plan to support ovs with dpdk or vhost-user port?  
> If so, what's the pipeline?
>
> Thank you
>
> -邮件原件-
> 发件人: Petr Horacek [mailto:phora...@redhat.com]
> 发送时间: 2016年8月2日 19:53
> 收件人: lifuqiong
> 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; devel
> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version 4.0.2? 
> Thank you
>
> Clean == host that has just NICs, like right after system installation (no 
> networks created by VDSM, bridges, bonds, vlans). Anyway, VDSM OVS is not 
> able to acquire external NICs yet (the patch is under review and will be 
> merged to master soon [1]).
>
> I would recommend you to wait for VDSM with mentioned patch merged. If you 
> cannot wait, you can try to setup ovirtmgmt network manually via console 
> (turn down NIC, setup OVS network on top of it). Not sure if this would help 
> you.
>
> [1] https://gerrit.ovirt.org/#/c/60404/29
>
> 2016-08-02 13:30 GMT+02:00 lifuqiong <lifuqi...@cncloudsec.com>:
>> Hi Petr,
>> Thank you for your advice. But what does "Clean hosts" mean,
>> as I know now, When you add a clean Host to ovirt engine, the vdsm or ovirt 
>> node will create a Network named ovirtmgmt, which is an Linux bridge 
>> network, How do I clean the network? Just delete the linux bridge and reset 
>> the linux bridge binding's physical Nic?
>>
>> Hope to get your help as sonn as possible.
>> Thank you.
>> Mark
>>
>> -邮件原件-
>> 发件人: Petr Horacek [mailto:phora...@redhat.com]
>> 发送时间: 2016年8月2日 18:29
>> 收件人: lifuqiong
>> 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; users
>> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version
>> 4.0.2? Thank you
>>
>> If the host was a part of legacy cluster you must do manual cleanup of all 
>> networks. Currently VDSM cannot change Linux bridges into OVS ones (this 
>> will be implemented soon). Make sure that you are adding clean hosts (with 
>> NIC interface/s only) to OVS cluster.
>>
>> Regards,
>> Petr
>>
>> 2016-08-02 10:01 GMT+02:00 Michael Burman <mbur...@redhat.com>:
>>> Hi ,
>>>
>>> Did you synced network/s after you moved the host to the ovs type cluster?
>>> It seems like you didn't..)
>>> Go to 'Hosts' main tab' and choose the host, go to 'Network
>>> Interfaces' sub tab and press the 'Sync All Networks' , now the
>>> networks should be synced to host as ovs switch type.
>>> Run the vm and check the xml.
>>> It should look something like this:
>>>
>>> 
>>>   
>>>
>>> thanks
>>>
>>>
>>> On Tue, Aug 2, 2016 at 9:37 AM, Meni Yakove <myak...@redhat.com> wrote:
>>>>
>>>>
>>>>
>>>> On Tue, Aug 2, 2016 at 7:12 AM, lifuqiong <lifuqi...@cncloudsec.com>
>>>> wrote:
>>>>>
>>>>> I create a cluster which already enabled ovs network as you
>>>>> mentioned , but when I create vm in this cluster,  I can only using
>>>>> ovirtmgmt/ovirtmgmt vNIC profile, which is still a Linux bridge.
>>>>>
>>>>> I found no way to add a OVS vNIC profile,  I have to chose
>>>>> ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the vm
>>>>> is still using Linux bridge to communicate with outside, not the ovs.
>>>>>
>>>>>
>>>>>
>>>>> Need I to create a ovs bridge or vport and bind it to physical NIC
>>>>> in vdsm manually?
>>>>>
>>>>>
>>>>>
>>>>> Hope your reply as soon as possible.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Mark
>>>>>
>>>>>
>>>>>
>>>>> 发件人: users-boun...@ovirt.org

Re: [ovirt-devel] Publicly available REST documentation

2017-01-03 Thread Petr Horacek 
Hi, I've been hacking public API docs yesterday, and I think it will
work in GitHub-Travis combination. Now I am waiting if Gerrit-GitHub
mirroring will remove branch created directly on GitHub, if not, then
my approach would be following:

Both 4.0 and 4.1 branches will have .travis.yml in them that will run
the build and then push generated pages to gh-pages branch (authorized
via GitHub deploy key). For now I have a working demo on my fork
(https://github.com/phoracek/ovirt-engine-api-model/blob/master/.travis.yml),
this one does not use deploy keys, but token instead.

Hope I'm not breaking your work.

2017-01-03 14:49 GMT+01:00 Vojtech Szocs :
>
>
> - Original Message -
>> From: "Rafael Martins" 
>> To: "Vojtech Szocs" 
>> Cc: "Juan Hernández" , "Michal Skrivanek" 
>> , "devel" 
>> Sent: Tuesday, January 3, 2017 2:28:30 PM
>> Subject: Re: [ovirt-devel] Publicly available REST documentation
>>
>>
>>
>> - Original Message -
>> > From: "Vojtech Szocs" 
>> > To: "Rafael Martins" 
>> > Cc: "Juan Hernández" , "Michal Skrivanek"
>> > , "devel" 
>> > Sent: Tuesday, January 3, 2017 2:24:22 PM
>> > Subject: Re: [ovirt-devel] Publicly available REST documentation
>> >
>> >
>> >
>> > - Original Message -
>> > > From: "Rafael Martins" 
>> > > To: "Vojtech Szocs" 
>> > > Cc: "Juan Hernández" , "Michal Skrivanek"
>> > > , "devel" 
>> > > Sent: Tuesday, January 3, 2017 2:17:49 PM
>> > > Subject: Re: [ovirt-devel] Publicly available REST documentation
>> > >
>> > > - Original Message -
>> > > > From: "Vojtech Szocs" 
>> > > > To: "Juan Hernández" 
>> > > > Cc: "Michal Skrivanek" , "devel" 
>> > > > Sent: Tuesday, January 3, 2017 2:11:06 PM
>> > > > Subject: Re: [ovirt-devel] Publicly available REST documentation
>> > > >
>> > > >
>> > > >
>> > > > - Original Message -
>> > > > > From: "Juan Hernández" 
>> > > > > To: "Jakub Niedermertl" 
>> > > > > Cc: "devel" , "Michal Skrivanek"
>> > > > > 
>> > > > > Sent: Monday, January 2, 2017 10:48:53 PM
>> > > > > Subject: Re: [ovirt-devel] Publicly available REST documentation
>> > > > >
>> > > > > On 01/02/2017 10:13 PM, Jakub Niedermertl wrote:
>> > > > > > Hi Juan,
>> > > > > >
>> > > > > > from time to time I'd like the REST doc to be available on some
>> > > > > > public
>> > > > > > site. It would allow us to
>> > > > > > * check the documentation without searching for running engine
>> > > > > > * be able to easily link documentations in irc/mails
>> > > > > > * link rest doc from ovirt.org site doc
>> > > > > > Recently I've also heard similar request from other guys (cc-ed).
>> > > > > > Would it be possible to for example publish generated doc of merged
>> > > > > > patches of ovirt-engine-api-model project? Maybe github project
>> > > > > > pages
>> > > > > > [1] of project mirror [2] could be used for hosting.
>> > > > > >
>> > > > > > Regards
>> > > > > > Jakub
>> > > > > >
>> > > > > > [1]
>> > > > > > https://help.github.com/articles/user-organization-and-project-pages/#project-pages
>> > > > > > [2] https://github.com/oVirt/ovirt-engine-api-model
>> > > > > >
>> > > > >
>> > > > > Yes, we can publish the documentation using gh-pages. I just created
>> > > > > and
>> > > > > populated the 'gh-branch' with some initial content, and requested
>> > > > > the
>> > > > > activation of the feature in Github. I will inform you when it is
>> > > > > ready.
>> > > >
>> > > > Alternatively, you could use readthedocs.org which supports webhooks:
>> > > > a push to GitHub (mirror) project [syncing Gerrit with GitHub] would
>> > > > regenerate the project's documentation available at
>> > > >
>> > > >   .readthedocs.io
>> > > >
>> > > > which would allow to separate the GitHub project from its docs, given
>> > > > the source comes from Gerrit.
>> > >
>> > > ReadTheDocs relies on sphinx and/or mkdocs to rebuild the docs when
>> > > called
>> > > by
>> > > the webhook, and we use something else. We just need some hosting for
>> > > static
>> > > files, then github-pages is a better solution.
>> >
>> > Hm, and what about pushing to https://github.com/oVirt/ovirt-site directly,
>> > instead of pushing to GitHub (mirror) project pages?
>>
>> there's no real need to mess with the ovirt-site repo. we can have a
>> separated repo, that can be freely updated by a jenkins job, for example,
>> and include it on ovirt-site using a sub-repository, like it is done for
>> data/events today. The good thing of this approach is that we can have
>> "unstable" docs in the separated repo,

Re: [ovirt-devel] Publicly available REST documentation

2017-01-04 Thread Petr Horacek 
Hello again, built master documentation is available on [1], latest
4.1 and 4.0 tags on [2] and [3] (these two were created manually,
automated build will be triggered by a next tag).

[1] http://ovirt.github.io/ovirt-engine-api-model/master/
[2] http://ovirt.github.io/ovirt-engine-api-model/4.1/
[3] http://ovirt.github.io/ovirt-engine-api-model/4.0/

2017-01-03 15:22 GMT+01:00 Juan Hernández <jhern...@redhat.com>:
> On 01/03/2017 03:20 PM, Petr Horacek wrote:
>> Hi, I've been hacking public API docs yesterday, and I think it will
>> work in GitHub-Travis combination. Now I am waiting if Gerrit-GitHub
>> mirroring will remove branch created directly on GitHub, if not, then
>> my approach would be following:
>>
>> Both 4.0 and 4.1 branches will have .travis.yml in them that will run
>> the build and then push generated pages to gh-pages branch (authorized
>> via GitHub deploy key). For now I have a working demo on my fork
>> (https://github.com/phoracek/ovirt-engine-api-model/blob/master/.travis.yml),
>> this one does not use deploy keys, but token instead.
>>
>> Hope I'm not breaking your work.
>>
>
> Excellent! Please go ahead.
>
>> 2017-01-03 14:49 GMT+01:00 Vojtech Szocs <vsz...@redhat.com>:
>>>
>>>
>>> - Original Message -
>>>> From: "Rafael Martins" <rmart...@redhat.com>
>>>> To: "Vojtech Szocs" <vsz...@redhat.com>
>>>> Cc: "Juan Hernández" <jhern...@redhat.com>, "Michal Skrivanek" 
>>>> <mskri...@redhat.com>, "devel" <devel@ovirt.org>
>>>> Sent: Tuesday, January 3, 2017 2:28:30 PM
>>>> Subject: Re: [ovirt-devel] Publicly available REST documentation
>>>>
>>>>
>>>>
>>>> - Original Message -
>>>>> From: "Vojtech Szocs" <vsz...@redhat.com>
>>>>> To: "Rafael Martins" <rmart...@redhat.com>
>>>>> Cc: "Juan Hernández" <jhern...@redhat.com>, "Michal Skrivanek"
>>>>> <mskri...@redhat.com>, "devel" <devel@ovirt.org>
>>>>> Sent: Tuesday, January 3, 2017 2:24:22 PM
>>>>> Subject: Re: [ovirt-devel] Publicly available REST documentation
>>>>>
>>>>>
>>>>>
>>>>> - Original Message -
>>>>>> From: "Rafael Martins" <rmart...@redhat.com>
>>>>>> To: "Vojtech Szocs" <vsz...@redhat.com>
>>>>>> Cc: "Juan Hernández" <jhern...@redhat.com>, "Michal Skrivanek"
>>>>>> <mskri...@redhat.com>, "devel" <devel@ovirt.org>
>>>>>> Sent: Tuesday, January 3, 2017 2:17:49 PM
>>>>>> Subject: Re: [ovirt-devel] Publicly available REST documentation
>>>>>>
>>>>>> - Original Message -
>>>>>>> From: "Vojtech Szocs" <vsz...@redhat.com>
>>>>>>> To: "Juan Hernández" <jhern...@redhat.com>
>>>>>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, "devel" <devel@ovirt.org>
>>>>>>> Sent: Tuesday, January 3, 2017 2:11:06 PM
>>>>>>> Subject: Re: [ovirt-devel] Publicly available REST documentation
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> - Original Message -
>>>>>>>> From: "Juan Hernández" <jhern...@redhat.com>
>>>>>>>> To: "Jakub Niedermertl" <jnied...@redhat.com>
>>>>>>>> Cc: "devel" <devel@ovirt.org>, "Michal Skrivanek"
>>>>>>>> <mskri...@redhat.com>
>>>>>>>> Sent: Monday, January 2, 2017 10:48:53 PM
>>>>>>>> Subject: Re: [ovirt-devel] Publicly available REST documentation
>>>>>>>>
>>>>>>>> On 01/02/2017 10:13 PM, Jakub Niedermertl wrote:
>>>>>>>>> Hi Juan,
>>>>>>>>>
>>>>>>>>> from time to time I'd like the REST doc to be available on some
>>>>>>>>> public
>>>>>>>>> site. It would allow us to
>>>>>>>>> * check the documentation without searching for running engine
>>>>>>>>> * be able to easily link documentations in irc/mails
>>>>>>>>> * l

Re: [ovirt-devel] [OST] [HC] HE VM fails to start

2017-04-04 Thread Petr Horacek 
Hello Sahina,

I think I have a fix for that. Can I somehow trigger the test with
VDSM refspec/custom RPMs?

Thanks,
Petr

2017-04-04 8:52 GMT+02:00 Dan Kenigsberg :
> On Tue, Apr 4, 2017 at 9:28 AM, Sahina Bose  wrote:
>> Job's still failing on master.
>> Could this be related to network patches that got merged on Mar 28, for
>> instance https://gerrit.ovirt.org/#/c/74390/ ?
>>
>> On Thu, Mar 30, 2017 at 11:41 AM, Sahina Bose  wrote:
>>>
>>> The error in vdsm.log
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/share/vdsm/virt/vm.py", line 2016, in _setup_devices
>>> dev_object.setup()
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/graphics.py",
>>> line 63, in setup
>>> net_api.create_libvirt_network(display_network, self.conf['vmId'])
>>>   File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 90, in
>>> create_libvirt_network
>>> libvirt.create_network(netname, user_reference)
>>>   File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line
>>> 94, in create_network
>>> if not is_libvirt_network(netname):
>>>   File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line
>>> 159, in is_libvirt_network
>>> netname = LIBVIRT_NET_PREFIX + netname
>>> TypeError: cannot concatenate 'str' and 'NoneType' objects
>>> 2017-03-29 22:58:39,559-0400 ERROR (vm/d71bdf4e) [virt.vm]
>>> (vmId='d71bdf4e-1eb3-4762-bd0e-05bb9f5e43ef') The vm start process failed
>>> (vm:659)
>>>
>>> The tests last passed on Mar 28. Did a recent patch break this?
>>>
>>> The full build logs at
>>> http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/52/artifact/exported-artifacts/test_logs/
>>>
>>> thanks
>>> sahina
>
> Sorry Sahina for having missed your email. Indeed, it seems that
> Eddy's topic branch of creating libvirt networks just-in-time causes
> the failure.
> Do note that the topic branch is quite long, and reverting parts of it
> might take a little while.
>
> Petr,  can you make hc-system-tests green again?
>
> Regards,
> Dan.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [proposal] deprecate VDSM ping in favor of ping2 and confirmConnectivity

2017-08-09 Thread Petr Horacek 
Method with saved caller's IP address is an option, but it would
require rewriting of network's connectivity check mechanism. We would
need to introduce some extra IPC between supervdsm and vdsm for this
IIUIC.

The reason for ping2 is backward compatibility. It is undocumented,
but Engine still depends on it and older versions will probably stay
like that. In case we remove the side-effect and old Engine calls new
ping1 it would never confirm network connectivity.

2017-08-08 15:19 GMT+02:00 Martin Sivak <msi...@redhat.com>:
>>> A ping that has no side effects and a "watchdog" mechanism to confirm
>>> connectivity.
>>
>> This sounds as exactly the right solution right now.
>
> Just to clarify: Removing the undocumented side effects from ping. Not
> introducing ping2.
>
> Martin
>
> On Tue, Aug 8, 2017 at 10:47 AM, Martin Sivak <msi...@redhat.com> wrote:
>>> The proposed solution is focused on making sure a command does one thing and
>>> not two:
>>> A ping that has no side effects and a "watchdog" mechanism to confirm
>>> connectivity.
>>
>> This sounds as exactly the right solution right now.
>>
>>>>> Still someone could call conirmConnectivity, no?
>>
>> We do not protect any other endpoints that can cause the host to go
>> wild (storage or even setupNetworks). I agree with Edward it is the
>> responsibility of the caller to do the right thing. You need to be
>> root or have the certificate to talk to VDSM anyway.
>>
>> Martin
>>
>> On Tue, Aug 8, 2017 at 8:24 AM, Edward Haas <eh...@redhat.com> wrote:
>>>
>>>
>>> On Mon, Aug 7, 2017 at 11:06 PM, Nir Soffer <nsof...@redhat.com> wrote:
>>>>
>>>> On Mon, Aug 7, 2017 at 5:28 PM Roy Golan <rgo...@redhat.com> wrote:
>>>>>
>>>>> Still someone could call conirmConnectivity, no? so the state isn't
>>>>> guarded from localhost tinkering anyhow. If you really need a solution you
>>>>> can acuire a token for this operation by setupNetworks, and confirm
>>>>> connectivity with this token passed back.
>>>>>
>>>>> I'm not sure about the severity of the problem here, I'll let other
>>>>> reply, but I'm against this kind of solution.
>>>>>
>>>>>
>>>>>
>>>>> On Mon, 7 Aug 2017 at 15:32 Petr Horacek <phora...@redhat.com> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> current VDSM ping verb has a problem - it confirms network
>>>>>> connectivity as a side-effect. After Engine calls setupNetwork it
>>>>>> pings VDSM host to confirm that external network connectivity is not
>>>>>> broken. This prohibits other users to call ping from localhost since
>>>>>> it would confirm connectivity even though networking could be broken.
>>>>
>>>>
>>>> Vdsm can save the client ip setting up the network. Getting a ping from
>>>> this
>>>> client can confirm that the connectivity was restored. pings from other
>>>> hosts
>>>> can be ignored.
>>>>
>>>> The client address is available in a thread local variable
>>>> (context.client_host)
>>>> during all api calls. see vdsm.common.api.context_string() for example
>>>> usage.
>>>>
>>>> This infrastructure is available in 4.1.
>>>
>>>
>>> The proposed solution is focused on making sure a command does one thing and
>>> not two:
>>> A ping that has no side effects and a "watchdog" mechanism to confirm
>>> connectivity.
>>>
>>> Does it make sense to confirm connectivity from localhost? In many cases it
>>> probably does not,
>>> but there may be cases where it does make sense... it is not the
>>> functionality to determine what
>>> makes sense or not, it is the usage of it who has the responsibility to use
>>> it correctly.
>>>
>>>>
>>>> Nir
>>>>
>>>>>>
>>>>>>
>>>>>> In order to fix this problem ping should be split to ping2 (which just
>>>>>> returns Success with no side-effect) and confirmConnectivity. Change
>>>>>> on VDSM side was introduced in [1], we still need to expose new verbs
>>>>>> in Engine.
>>>>>>
>>>>>> Regards,
>>>>>> Petr
>>>>>>
>>>>>> [1] https://gerrit.ovirt.org/#/c/80119/
>>>>>> ___
>>>>>> Devel mailing list
>>>>>> Devel@ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>>
>>>>> ___
>>>>> Devel mailing list
>>>>> Devel@ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>>
>>>> ___
>>>> Devel mailing list
>>>> Devel@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>>
>>> ___
>>> Devel mailing list
>>> Devel@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [proposal] deprecate VDSM ping in favor of ping2 and confirmConnectivity

2017-08-07 Thread Petr Horacek 
Hello,

current VDSM ping verb has a problem - it confirms network
connectivity as a side-effect. After Engine calls setupNetwork it
pings VDSM host to confirm that external network connectivity is not
broken. This prohibits other users to call ping from localhost since
it would confirm connectivity even though networking could be broken.

In order to fix this problem ping should be split to ping2 (which just
returns Success with no side-effect) and confirmConnectivity. Change
on VDSM side was introduced in [1], we still need to expose new verbs
in Engine.

Regards,
Petr

[1] https://gerrit.ovirt.org/#/c/80119/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Trouble in switch type to OVS process

2018-01-18 Thread Petr Horacek 
Dmitry,

could you please share you vdsm.log and engine.log as well?

Thanks,
Petr

2018-01-16 12:22 GMT+01:00 Petr Horacek <phora...@redhat.com>:

> 2018-01-16 11:05 GMT+01:00 Dmitry Semenov <ze...@ya.ru>:
>
>> 16.01.2018, 11:39, "Dan Kenigsberg" <dan...@redhat.com>:
>> > On Tue, Jan 16, 2018 at 10:22 AM, Sandro Bonazzola <sbona...@redhat.com>
>> wrote:
>> >> Adding some relevant people
>> >>
>> >> 2018-01-15 23:13 GMT+01:00 Dmitry Semenov:
>> >>> Hi everyone!
>> >>>
>> >>> I have installed oVirt ver 4.2 on three nodes with shared storage
>> (FC) and linux bridge setting:
>> >>> - node01
>> >>>
>> >>> - node02 (self-hosted Engine host)
>> >>>
>> >>> - node03 (self-hosted Engine host)
>> >>>
>> >>> I wanted to set cluster network switch type to OVS (for OVN)
>> >>>
>> >>> (followed this instruction https://ovirt.org/develop/rele
>> ase-management/features/network/provider-physical-network/)
>> >
>> > Please note that OVN overlays work just fine with Linux Bridge
>> switchtype. You need to move to OVS only if you want OVN on non-overlays.
>> >
>> Dan,
>> if I catch you right, I dont need to switch to OVS for creation of
>> internal networks with DHCP (for vms) and their routing to external
>> networks. Thats true?
>>
> Yes. You can use default Linux bridge networks. Create an OVN overlay
> network with subnet for VMs. Then create a "router" VM that is connected to
> both overlay and a physical network, configure routing there.
>
>>
>> >>> After this step “Set OVS networking on all vdsm hosts. For each host,
>> enable Maintenance mode, Sync All Networks” - my node01 disappeared. I
>> don’t know what to do further.
>> >
>> > In "disappeared" do you mean it became non-responsive? Would you share
>> with us your supervdsm.log from the disappearing host?
>> >
>> After launch of network synchronization all settings of ovirtmgmt
>> interface disappeared on node, after that node became unavailable.
>>
>> supervdsm.log: https://pastebin.com/eW0UpB6j
>
> Thanks, will take a look.
>
>>
>>
>> >>> For the rest 2 nodes (node02 and node03) i didn’t check this step.
>> >>>
>> >>> Each node has bond (from 2 NIC), and each bond has configuration with
>> 3 VLANS for: ovirtmgmt, migration, display.
>> >>>
>> >>> How can I return node01 to cluster with OVS and switch other nodes to
>> OVS?
>> >>>
>> >>> Best regards,
>> >>>
>> >>> ___
>> >>> Devel mailing list
>> >>> Devel@ovirt.org
>> >>> http://lists.ovirt.org/mailman/listinfo/devel
>> >>
>> >> --
>> >>
>> >> SANDRO BONAZZOLA
>> >>
>> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
>> >>
>> >> Red Hat EMEA
>> >>
>> >> TRIED. TESTED. TRUSTED.
>>
>>
>> --
>> Best regards
>>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Trouble in switch type to OVS process

2018-01-16 Thread Petr Horacek 
2018-01-16 11:05 GMT+01:00 Dmitry Semenov :

> 16.01.2018, 11:39, "Dan Kenigsberg" :
> > On Tue, Jan 16, 2018 at 10:22 AM, Sandro Bonazzola 
> wrote:
> >> Adding some relevant people
> >>
> >> 2018-01-15 23:13 GMT+01:00 Dmitry Semenov:
> >>> Hi everyone!
> >>>
> >>> I have installed oVirt ver 4.2 on three nodes with shared storage (FC)
> and linux bridge setting:
> >>> - node01
> >>>
> >>> - node02 (self-hosted Engine host)
> >>>
> >>> - node03 (self-hosted Engine host)
> >>>
> >>> I wanted to set cluster network switch type to OVS (for OVN)
> >>>
> >>> (followed this instruction https://ovirt.org/develop/
> release-management/features/network/provider-physical-network/)
> >
> > Please note that OVN overlays work just fine with Linux Bridge
> switchtype. You need to move to OVS only if you want OVN on non-overlays.
> >
> Dan,
> if I catch you right, I dont need to switch to OVS for creation of
> internal networks with DHCP (for vms) and their routing to external
> networks. Thats true?
>
Yes. You can use default Linux bridge networks. Create an OVN overlay
network with subnet for VMs. Then create a "router" VM that is connected to
both overlay and a physical network, configure routing there.

>
> >>> After this step “Set OVS networking on all vdsm hosts. For each host,
> enable Maintenance mode, Sync All Networks” - my node01 disappeared. I
> don’t know what to do further.
> >
> > In "disappeared" do you mean it became non-responsive? Would you share
> with us your supervdsm.log from the disappearing host?
> >
> After launch of network synchronization all settings of ovirtmgmt
> interface disappeared on node, after that node became unavailable.
>
> supervdsm.log: https://pastebin.com/eW0UpB6j

Thanks, will take a look.

>
>
> >>> For the rest 2 nodes (node02 and node03) i didn’t check this step.
> >>>
> >>> Each node has bond (from 2 NIC), and each bond has configuration with
> 3 VLANS for: ovirtmgmt, migration, display.
> >>>
> >>> How can I return node01 to cluster with OVS and switch other nodes to
> OVS?
> >>>
> >>> Best regards,
> >>>
> >>> ___
> >>> Devel mailing list
> >>> Devel@ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/devel
> >>
> >> --
> >>
> >> SANDRO BONAZZOLA
> >>
> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> >>
> >> Red Hat EMEA
> >>
> >> TRIED. TESTED. TRUSTED.
>
>
> --
> Best regards
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Re: issue in vdsm monitoring

2018-09-11 Thread Petr Horacek 
vdsm.log is the same issue, supervdsm.log seems unrelated.

2018-09-11 11:59 GMT+02:00 Dominik Holler :

> On Tue, 11 Sep 2018 10:26:02 +0100
> Dafna Ron  wrote:
>
> > Hi,
> >
> > I have been seeing random failures of tests in different projects
> > caused by vdsm monitoring.
> >
> > I need someone from vdsm to please help debug this issue.
> >
>
> Petr, is this the same problem like yesterday in
>
> [ovirt-devel] failure in ost test - Invalid argument - help in debugging
> issue
>
> > From what I can see, the test suspend/resume vm failed because we
> > could not query the status of the vm on the host.
> >
> > you can see full log from failed tests here:
> >
> > https://jenkins.ovirt.org/job/ovirt-master_change-queue-
> tester/10208/artifact/basic-suite.el7.x86_64/test_logs/
> basic-suite-master/post-004_basic_sanity.py/
> >
> > Here are the errors that I can see in the vdsm which seem to suggest
> > that there is an issue getting stats on the vm which was suspended
> > and caused the failure of the test:
> >
> >
> >
> > 2018-09-11 00:40:05,896-0400 INFO  (monitor/c1fe6e6)
> > [storage.StorageDomain] Removing remnants of deleted images []
> > (fileSD:734) 2018-09-11 00:40:07,957-0400 DEBUG (qgapoller/1) [vds]
> > Not sending QEMU-GA command 'guest-get-users' to
> > vm_id='8214433a-f233-4aaa-aeda-2ce1d31c78dc', command is not
> > supported (qemuguestagent:192) 2018-09-11 00:40:08,068-0400 DEBUG
> > (periodic/3) [virt.sampling.VMBulkstatsMonitor] sampled timestamp
> > 4296118.49 elapsed 0.010 acquired True domains all (sampling:443)
> > 2018-09-11 00:40:08,271-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer]
> > Calling 'Image.prepare' in bridge with {u'allowIllegal': True,
> > u'storagepoolID': u'e80a56d9-74da-498a-b010-4a9df287f11d', u'imageID':
> > u'd4c831e6-02d2-4d89-b516-0ec4597
> > 5e024', u'volumeID': u'15b07af1-625b-42e3-b62a-8e7c7a120a56',
> > u'storagedomainID': u'f1744940-41b6-4d35-b7bf-870c4e07d995'}
> > (__init__:329)
> >
> >
> > 2018-09-11 00:40:10,846-0400 DEBUG (vmchannels) [virt.vm]
> > (vmId='8214433a-f233-4aaa-aeda-2ce1d31c78dc') Guest connection timed
> > out (guestagent:556)
> > 2018-09-11 00:40:11,637-0400 DEBUG (jsonrpc/5) [jsonrpc.JsonRpcServer]
> > Calling 'Host.getStats' in bridge with {} (__init__:329)
> > 2018-09-11 00:40:11,637-0400 INFO  (jsonrpc/5) [api.host] START
> > getStats() from=:::192.168.201.4,49184 (api:47)
> > 2018-09-11 00:40:11,643-0400 DEBUG (jsonrpc/5) [root] cannot read eth0
> > speed (nic:42)
> > 2018-09-11 00:40:11,645-0400 DEBUG (jsonrpc/5) [root] cannot read eth1
> > speed (nic:42)
> > 2018-09-11 00:40:11,647-0400 DEBUG (jsonrpc/5) [root] cannot read eth2
> > speed (nic:42)
> > 2018-09-11 00:40:11,649-0400 DEBUG (jsonrpc/5) [root] cannot read eth3
> > speed (nic:42)
> > 2018-09-11 00:40:11,667-0400 INFO  (jsonrpc/5) [api.host] FINISH
> > getStats error=[Errno 22] Invalid argument
> > from=:::192.168.201.4,49184 (api:51) 2018-09-11 00:40:11,667-0400
> > ERROR (jsonrpc/5) [jsonrpc.JsonRpcServer] Internal server error
> > (__init__:350) Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line
> > 345, in _handle_request
> > res = method(**params)
> >   File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line
> > 202, in _dynamicMethod
> > result = fn(*methodArgs)
> >   File "", line 2, in getStats
> >   File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line
> > 49, in method
> > ret = func(*args, **kwargs)
> >   File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1407, in
> > getStats
> > multipath=True)}
> >   File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 49,
> > in get_stats
> > decStats = stats.produce(first_sample, last_sample)
> >   File "/usr/lib/python2.7/site-packages/vdsm/host/stats.py", line
> > 71, in produce
> > stats.update(get_interfaces_stats())
> >   File "/usr/lib/python2.7/site-packages/vdsm/host/stats.py", line
> > 153, in get_interfaces_stats
> > return net_api.network_stats()
> >   File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line
> > 63, in network_stats
> > return netstats.report()
> >   File "/usr/lib/python2.7/site-packages/vdsm/network/netstats.py",
> > line 31, in report
> > stats = link_stats.report()
> >   File "/usr/lib/python2.7/site-packages/vdsm/network/link/stats.py",
> > line 41, in report
> > speed = vlan.speed(i.device)
> >   File "/usr/lib/python2.7/site-packages/vdsm/network/link/vlan.py",
> > line 36, in speed
> > dev_speed = nic.read_speed_using_sysfs(dev_name)
> >   File "/usr/lib/python2.7/site-packages/vdsm/network/link/nic.py",
> > line 48, in read_speed_using_sysfs
> > s = int(f.read())
> > IOError: [Errno 22] Invalid argument
> > 2018-09-11 00:40:11,669-0400 INFO  (jsonrpc/5)
> > [jsonrpc.JsonRpcServer] RPC call Host.getStats failed (error -32603)
> > in 0.03 seconds (__init__:312) 2018-09-11 00:40:14,656-0400 DEBUG
> > (jsonrpc/2)

Re: [ovirt-devel] [vdsm] network test failure

2018-03-21 Thread Petr Horacek 
I tried to retrigger the build several times, it was always executed on el7
machine, maybe it picks fc26 only when all other machines are taken?

Shouldn't be "Permission denied" problem detected in
link_bond_test.py:setup_module()? It runs "check_sysfs_bond_permission".

2018-03-20 18:12 GMT+01:00 Edward Haas :

> The tests ran on a fc26 slave and our bond option default map is in sync
> with the el7 kernel.
> It looks like we MUST generate a bond default map on every run.
>
> I'm a bit surprised it never happened until now, perhaps I'm not
> interpreting correctly the tests helper  code? Petr?
> Assuming I'm correct here, I'll try to post a fix.
>
> Thanks,
> Edy.
>
> On Tue, Mar 20, 2018 at 12:14 PM, Dan Kenigsberg 
> wrote:
>
>> +Petr
>>
>> On Tue, Mar 20, 2018 at 11:07 AM, Francesco Romani 
>> wrote:
>> > Hi all,
>> >
>> >
>> > we had a bogus failure on CI again, some network test failed and it
>> > seems totally unrelated to the patch being tested:
>> >
>> >
>> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86
>> _64/22410/consoleFull
>> >
>> >
>> > could someone please have a look?
>> >
>> >
>> > Bests,
>> >
>> > --
>> > Francesco Romani
>> > Senior SW Eng., Virtualization R
>> > Red Hat
>> > IRC: fromani github: @fromanirh
>> >
>>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] vdsm has been tagged (v4.30.29)

2019-08-20 Thread Petr Horacek 

___
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/PR7IPT4NJQGDYHBTUS6VI37D66ZLP7UH/

[ovirt-devel] vdsm has been tagged (v4.30.28)

2019-08-14 Thread Petr Horacek 

___
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/DIV5RGMXUVSK4C6YFKE7K5FGP7MV7SG7/

[ovirt-devel] vdsm has been tagged (v4.30.35)

2019-10-30 Thread Petr Horacek 

___
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/G234EBVC3X54EEA4W5LMI6EWOYQKMGCO/

[ovirt-devel] Re: Pushing container to dockerhub using podman

2019-11-14 Thread Petr Horacek 
On Thu, 14 Nov 2019, 21:33 Edward Haas,  wrote:

>
>
> On Thu, Nov 14, 2019 at 10:24 PM Nir Soffer  wrote:
>
>> On Thu, Nov 14, 2019 at 9:29 PM Edward Haas  wrote:
>> >
>> > Hi All,
>> >
>> > I'm trying to push an image to dockerhub using podman.
>> > Unfortunately, it does not work, giving me the following error:
>> >
>> > ```
>> > $ sudo podman push 2dfe3d835f08 ovirtorg/vdsm-test-func-network-centos-8
>> > Getting image source signatures
>> > Error: Error copying image to the remote destination: Error trying to
>> reuse blob
>> sha256:9e607bb861a7d58bece26dd2c02874beedd6a097c1b6eca5255d5eb0d2236983 at
>> destination: Error checking whether a blob
>> sha256:9e607bb861a7d58bece26dd2c02874beedd6a097c1b6eca5255d5eb0d2236983
>> exists in docker.io/ovirtorg/vdsm-test-func-network-centos-8: errors:
>> > denied: requested access to the resource is denied
>> > error parsing HTTP 401 response body: unexpected end of JSON input: ""
>> > ```
>> > (podman login docker.io works fine)
>> > Has anyone encounter something like this?
>>
>> Maybe the issue is that we have to create the repository first.
>>
>> I created it here:
>>
>> https://hub.docker.com/repository/docker/ovirtorg/vdsm-test-func-network-centos-8
>>
>> Try to push again.
>>
>> I think you should be able to create new repositories.
>>
>> Nir
>>
>> Now I get something else:
>
> $ sudo podman push 2dfe3d835f08 ovirtorg/vdsm-test-func-network-centos-8
> Getting image source signatures
> Copying blob 55ac6f41bab4 done
> Copying blob 140282e4f2a3 done
> Copying blob 9f892f5760ee done
> Copying blob 602715c702c3 done
> Copying blob 9e607bb861a7 done
> Error: Error copying image to the remote destination: Error writing blob:
> Error initiating layer upload to
> /v2/ovirtorg/vdsm-test-func-network-centos-8/blobs/uploads/ in
> registry-1.docker.io: errors:
> denied: requested access to the resource is denied
> unauthorized: authentication required
>
docker login

>
> ___
> 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/AU2NG5NWCTLAJQFUVMO5IBDFMIGBK7XS/
>
___
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/NPUJZK2GLGN74HHWQXTTFFWG4Q5H3OPD/

[ovirt-devel] Re: How to remove ovirtmgmt network interface in centOS

2019-10-23 Thread Petr Horacek 
st 23. 10. 2019 v 15:05 odesílatel Trunet 
napsal:

> Hello Prajith,
>
> Can you elaborate better what are you trying to achieve?
>
> ifdown brings the interface down but it will not remove it. ovirtmgmt is a
> bridge "interface". list your bridges with `brctl show`.
>
> You can remove this bridge using `brctl delbr ovirtmgmt`. And yes, network
> connectivity will be gone because the IP is on the bridge as you can see on
> your output.
>
> You can configure your regular interface (eth0) with the IP that's on the
> bridge now, and that should do the trick. nmcli/nmtui are your friends or
> edit /etc/sysconfig/network-scripts/ifcfg-* files manually.
>
> Best regards,
> Wagner Sartori Junior
>
>
> --
> *From: *"Prajith Kesava Prasad" 
> *To: *devel@ovirt.org
> *Sent: *Wednesday, October 23, 2019 2:45:33 PM
> *Subject: *[ovirt-devel] How to remove ovirtmgmt network interface in
> centOS
>
> Hey everyone,
> Could someone please point me in the right direction?.
>
> Im unable to remove network interface ovirtmgmt, commands like ifdown
> results in a state where the ip is unreachable and a manual network restart
> had to be done to bring it back to normal.
>
It has been configured via VDSM and you should use VSDM to remove it.
Otherwise there could be leftover configuration in the system. If VDSM is
still running on the node, you can do the following:

echo '{"networks": {"ovirtmgmt": {"remove": true}}, "bondings": {},
"options": {"connectivityCheck": false}}' | vdsm-client -f - Host
setupNetworks
vdsm-client Host setSafeNetworkConfig


> could someone help me with removing ovirtmgmt network in centos?
> ___
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1000
> 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: eth0:  mtu 1500 qdisc mq master
> ovirtmgmt state UP group default qlen 1000
> link/ether 00:1a:4a:16:01:9c brd ff:ff:ff:ff:ff:ff
> 23: ;vdsmdummy;:  mtu 1500 qdisc noop state DOWN
> group default qlen 1000
> link/ether 66:66:f1:c4:52:c7 brd ff:ff:ff:ff:ff:ff
> 24: ovs-system:  mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether fe:aa:a4:0d:7a:31 brd ff:ff:ff:ff:ff:ff
> 25: br-int:  mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether ba:fd:da:db:29:44 brd ff:ff:ff:ff:ff:ff
> 147: ovirtmgmt:  mtu 1500 qdisc noqueue
> state UP group default qlen 1000
> link/ether 00:1a:4a:16:01:9c brd ff:ff:ff:ff:ff:ff
> inet 10.70.43.190/22 brd 10.70.43.255 scope global dynamic ovirtmgmt
>valid_lft 85952sec preferred_lft 85952sec
> inet6 2620:52:0:4628:21a:4aff:fe16:19c/64 scope global mngtmpaddr
> dynamic
>valid_lft 2591937sec preferred_lft 604737sec
> inet6 fe80::21a:4aff:fe16:19c/64 scope link
>valid_lft forever preferred_lft forever
> _
>
>
> Thanks,
> Prajith
>
> ___
> 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/FRRYN3Z36ZYSOWPV7RV3ZQ6ZHEAL2DGI/
> ___
> 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/3SPNNDRGG4HCFBCZPIAAPR3GIVJ32SCK/
>
___
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/RN7U2NKJFQ4UYFXMW27L3TS57REXVC6J/

[ovirt-devel] Re: Proposing Ales Musil as VDSM network maintainer

2020-06-23 Thread Petr Horacek 
út 23. 6. 2020 v 13:32 odesílatel Nir Soffer  napsal:

> On Mon, Jun 22, 2020 at 1:13 PM Marcin Sobczyk 
> wrote:
> > On 6/22/20 11:00 AM, Edward Haas wrote:
> >
> > Hello to all VDSM maintainers,
>
> These discussions should be public.
> Adding devel@ovirt.org
>
> > I hope I did not miss any active maintainers.
> >
> > I'd like to nominate Ales Musil to formally take over the vdsm-network
> vertical as a maintainer
> > after acting as such in the last period.
> >
> > Would you approve adding him to the vdsm-master-maintainers
> > https://gerrit.ovirt.org/#/admin/groups/106,members list,
> > so he will not be blocked on my availability?
> >
> > +1
>
> I don't see any problem, so +1.
>

+1, well deserved.


>
> Let's wait a few days for more feedback on devel.
>
> Nir
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-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/devel@ovirt.org/message/UH3YAS67MICAL34RHH6QZVC5Y3PRZ3OF/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/V62Z27EJJQJB5PXMZSKQVQZ6RXRJNBCE/