date:20160112

Re: [ovirt-users] Blog on Hyperconverged Infrastructure using oVirt and Gluster

2016-01-12 Thread Nathanaël Blanchet




Le 12/01/2016 12:40, Ramesh Nachimuthu a écrit :

Hi Folks,

  Have you ever wondered about Hyperconverged Ovirt and Gluster Setup. 
Here is an answer[1]. I wrote a blog explaining how to setup oVirt in 
a hyper-converged mode with Gluster.


[1] 
http://blogs-ramesh.blogspot.in/2016/01/ovirt-and-gluster-hyperconvergence.htm
Interesting but should be better with .html extension to prevent from 
dead link :)

*
*Regards,
Ramesh


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


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

Re: [ovirt-users] how to get infos about dev of ovirt 4.0

2016-01-12 Thread Nathanaël Blanchet

Hello,

Le 10/01/2016 09:21, Yaniv Kaul a écrit :
On Fri, Jan 8, 2016 at 1:22 PM, Nathanaël Blanchet > wrote:

Since meetings have been canceled (and reports), I find it
difficult for community to get informations about the development
state of ovirt.
How and where can we follow the release management, in particular
for 4.0, i.e. the new integrated features, the blocking bugs,
etc... I didn't find any documents like the one that was used for
previous release (http://goo.gl/9X3G49)

Hi Nathanaël,

Are you looking for specific information?
The planning is, as always has been, in Bugzilla and while many work
on 3.6.x still, there has been some work on 4.0 items already (mainly
in the mast branch of oVirt).
I'm using [1] as a Bugzilla query to look at all open RFEs. Those with
4.0.0 are the ones currently targeted for 4.0 - but I assume more will
be added/removed to the list.

Which meetings and reports are you missing?

HTH,
Y.

[1]
https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&list_id=4419697&namedcmd=RHEVM%2FoVirt%20open%20FutureFeatures
(Let me know if you can't see the results - I'm trying to see which
group has the highest visibility wrt sharing saved searches.)
Sorry, but your link leads me to "The search named /RHEVM/oVirt open
FutureFeatures/ does not exist." with my bugzilla account.

--
Nathanaël Blanchet

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

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

Re: [ovirt-users] NFS IO timeout configuration

2016-01-12 Thread Markus Stockhausen

>> Von: Yaniv Kaul [yk...@redhat.com]
>> Gesendet: Dienstag, 12. Januar 2016 13:15
>> An: Markus Stockhausen
>> Cc: users@ovirt.org; Mike Hildebrandt
>> Betreff: Re: [ovirt-users] NFS IO timeout configuration
>> 
>> On Tue, Jan 12, 2016 at 9:32 AM, Markus Stockhausen stockhau...@collogia.de> 
>> wrote:
>> Hi there,
>> 
>> we got a nasty situation yesterday in our OVirt 3.5.6 environment.
>> We ran a LSM that failed during the cleanup operation. To be precise
>> when the process deleted an image on the source NFS storage.
>
> Can you share with us your NFS server details? 
>Is the NFS connection healthy (can be seen with nfsstat)
>Generally, delete on NFS should be a pretty quick operation. 
> Y.

Hi Yaniv,

we usually have no problems with our NFS server. From our observations we 
only have issues when deleting files with many extents. This applies to all 
OVirt images files. Several of them have more than 50.000 extents, a few 
even more than 300.000.

> xfs_bmap 1cb5906f-65d8-4174-99b1-74f5b3cbc537
...
52976: [629122144..629130335]: 10986198592..10986206783
52977: [629130336..629130343]: 10986403456..10986403463
52978: [629130344..629138535]: 10986206792..10986214983
52979: [629138536..629138543]: 10986411656..10986411663
52980: [629138544..629145471]: 10986214992..10986221919
52981: [629145472..629145575]: 10809903560..10809903663
52982: [629145576..629145599]: 10737615056..10737615079

Our XFS is mounted with:

/dev/mapper/vg00-lvdata on /var/nas4 type xfs 
(rw,noatime,nodiratime,allocsize=16m)

Why we use allocsize=16M? We once started with allocize=512MB. This
led to sparse files that did not save much bytes. Because a single byte written
resulted in a 512MB allocation. Thin allocation of these files resulted in long 
runtimes
for formatting disks inside the VMS. So we reduced to 16MB as a balanced config

This works quite well but not for remove operations.

Better ideas?

Markus

Diese E-Mail enthÃ¤lt vertrauliche und/oder rechtlich geschÃ¼tzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtÃ¼mlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

Ãber das Internet versandte E-Mails kÃ¶nnen unter fremden Namen erstellt oder
manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine
rechtsverbindliche WillenserklÃ¤rung.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 KÃ¶ln

Vorstand:
Kadir Akin
Dr. Michael HÃ¶hnerbach

Vorsitzender des Aufsichtsrates:
Hans Kristian Langva

Registergericht: Amtsgericht KÃ¶ln
Registernummer: HRB 52 497

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

e-mails sent over the internet may have been written under a wrong name or
been manipulated. That is why this message sent as an e-mail is not a
legally binding declaration of intention.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 KÃ¶ln

executive board:
Kadir Akin
Dr. Michael HÃ¶hnerbach

President of the supervisory board:
Hans Kristian Langva

Registry office: district court Cologne
Register number: HRB 52 497

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

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville

Perfect.

Thanks.

De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 20:51
À : Jean-Pierre Ribeauville
Cc : Gianluca Cecchi; users@ovirt.org
Objet : Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues



On Tue, Jan 12, 2016 at 2:35 PM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:
Hi,

What I did from the beginning of this affair :


1)  Chown and chmod of  myhook.py

2)  Don’t try to run it from shell

3)  Up to now,  I may avoid to play with custom properties.
( BTW,  do you know how , within myhook.py , one may retrieve this custom 
property
   that will indicate if the hook has to be go further or must exist without 
doing anything ?)


This is documented on the hooks wiki page and in github. The basic idea is to 
add a custom property to a VM with specific text, and check for it in the hook. 
If you detect it, apply hook to VM, if not - pass

What’s remaining :

1) debug the .py
2) check wether, by migrating the Guest , the hook is also called on the target 
host  ( maybe you know the answer ?)

before_vm_migrate_source and before_vm_migrate_destination - also documented in 
the wiki.

Generally, just follow an existing hook, it should have everything


That’s all.

Regards,

J.P.

De : Gianluca Cecchi 
[mailto:gianluca.cec...@gmail.com]
Envoyé : mardi 12 janvier 2016 19:42
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

On Tue, Jan 12, 2016 at 5:32 PM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:
Hi,

My vdsm hook is now invoked.

Up to me to debug it.

Thanks a lot.

J.P.

I don't understand at the end what you had to change: from your previous 
messages it resulted that all things requested were in place already
Thanks,
Gianluca

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

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

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

2016-01-12 Thread Dan Yasny

On Tue, Jan 12, 2016 at 2:35 PM, Jean-Pierre Ribeauville <
jpribeauvi...@axway.com> wrote:

> Hi,
>
>
>
> What I did from the beginning of this affair :
>
>
>
> 1)  Chown and chmod of  myhook.py
>
> 2)  Don’t try to run it from shell
>
> 3)  Up to now,  I may avoid to play with custom properties.
> ( BTW,  do you know how , within myhook.py , one may retrieve this custom
> property
>that will indicate if the hook has to be go further or must exist
> without doing anything ?)
>
>
>
This is documented on the hooks wiki page and in github. The basic idea is
to add a custom property to a VM with specific text, and check for it in
the hook. If you detect it, apply hook to VM, if not - pass


> What’s remaining :
>
> 1) debug the .py
>
> 2) check wether, by migrating the Guest , the hook is also called on the
> target host  ( maybe you know the answer ?)
>

before_vm_migrate_source and before_vm_migrate_destination - also
documented in the wiki.

Generally, just follow an existing hook, it should have everything


>
>
> That’s all.
>
>
>
> Regards,
>
>
>
> J.P.
>
>
>
> *De :* Gianluca Cecchi [mailto:gianluca.cec...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 19:42
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook
> issues
>
>
>
> On Tue, Jan 12, 2016 at 5:32 PM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
> Hi,
>
> My vdsm hook is now invoked.
>
> Up to me to debug it.
>
> Thanks a lot.
>
> J.P.
>
>
>
> I don't understand at the end what you had to change: from your previous
> messages it resulted that all things requested were in place already
>
> Thanks,
>
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] API Importing a VM from an export domain fails

2016-01-12 Thread Tim Bielawa

Hello virt folks,

Background:

I'm using the REST API to import a VM from an attached export domain. The
VM was imported using the virt-v2v tool. I've tried this with cURL and with
the python SDK, both yield the same error message.

RHEVM Version: 3.5.6.0-1
Python SDK Version: 3.5.6.0-1

According to the documentation, importing should follow this syntax:

> POST /ovirt-engine
/api/storagedomains/{storagedomain:id}/vms/{vm:id}/import

With a small  body attached. In theory (by the documentation and
bug tracker [1]) either of these XML documents (both in the same paste)
should work:

http://fpaste.org/309944/52627148/

However, this fails with the following error message (full response in [2])

> Cannot import VM. Storage Domain type not specified.


Steps to reproduce:

1. Import a VM into an export storage domain
2. Create an XML document with an action like this (filling in the correct
values for the ID variables)


>   
>   
> export
>   
>   True
>   
> IMPORTED_VM
>   
> 


3. POST to the import location (again, substitute the correct ID variables
in the location)

/ovirt-engine/api/storagedomains//vms//import



Where is this storage domain type supposed to be defined, if not inside of
the storage_domain element as demonstrated in the documentation?

I would appreciate any advice you can offer or pointers to useful
resources/documentation.

Thanks!


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1147011#c13
[2] http://fpaste.org/309949/14526274/

-- 
Tim Bielawa
1BA0 4FAB 4C13 FBA0 A036  4958 AD05 E75E 0333 AE37
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville

Hi,

What I did from the beginning of this affair :


1)  Chown and chmod of  myhook.py


2)  Don’t try to run it from shell


3)  Up to now,  I may avoid to play with custom properties.
( BTW,  do you know how , within myhook.py , one may retrieve this custom 
property
   that will indicate if the hook has to be go further or must exist without 
doing anything ?)

What’s remaining :

1) debug the .py
2) check wether, by migrating the Guest , the hook is also called on the target 
host  ( maybe you know the answer ?)

That’s all.

Regards,

J.P.

De : Gianluca Cecchi [mailto:gianluca.cec...@gmail.com]
Envoyé : mardi 12 janvier 2016 19:42
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

On Tue, Jan 12, 2016 at 5:32 PM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:
Hi,

My vdsm hook is now invoked.

Up to me to debug it.

Thanks a lot.

J.P.


I don't understand at the end what you had to change: from your previous 
messages it resulted that all things requested were in place already
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt supported thinclient appliance

2016-01-12 Thread René Koch

Hi, 

There aren't too many thin clients out there which support oVirt/RHEV. 

I did a few VDI projects with oVirt and RHEV and I can recommend the Igel UD5 
Thin Client: 
https://www.igel.com/en/products/igel-thin-clients/ud5-series.html 

It's not the cheapest one and not the smallest one, but has good performance 
and the management software for these thin clients is great. 


Regards, 
René 


From: "RK RK"  
To: "users"  
Sent: Tuesday, January 12, 2016 5:06:13 PM 
Subject: [ovirt-users] Ovirt supported thinclient appliance 

Hi all, 

I am planning to setup oVirt 3.6.1 Virtualization setup for 100 desktop users 
in my software development company. 

Anyone please suggest me a good and cost-effective thinclient 
appliance(available in india) to use with my oVirt environment with support for 
SPICE protocol. 

-- 

With Regards, 
RK, 
+91 9840483044 

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

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

2016-01-12 Thread Gianluca Cecchi

On Tue, Jan 12, 2016 at 5:32 PM, Jean-Pierre Ribeauville <
jpribeauvi...@axway.com> wrote:

> Hi,
>
> My vdsm hook is now invoked.
>
> Up to me to debug it.
>
> Thanks a lot.
>
> J.P.
>
>
>
I don't understand at the end what you had to change: from your previous
messages it resulted that all things requested were in place already
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville

t; 16)   '''
>
> 17)
>
> 18)   channel = domxml.createElement('channel')
>
> 19)   disk.setAttribute('type', 'unix')
>
> 20)
>
> 21)   source = domxml.createElement('source')
>
> 22)   source.setAttribute('mode', 'bind')
>
> 23)
>
> 24)   # find  domain name
>
> 25)   domainame = domxml.getElementsByTagName('name')
>
> 26)
>
> 27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' +
> domainame + '_omnivision_1.agent')
>
> 28)   disk.appendChild(source)
>
> 29)
>
> 30)   target = domxml.createElement('target')
>
> 31)   target.setAttribute('type', 'virtio')
>
> 32)   target.setAttribute('name', 'omnivision_1.agent')
>
> 33)   disk.appendChild(target)
>
> 34)
>
> 35)   return channel
>
> 36)
>
> 37)   try:
>
> 38)  domxml = hooking.read_domxml()
>
> 39)  devices = domxml.getElementsByTagName('devices')[0]
>
> 40)  channeldev = createChannelElement(domxml)
>
> 41)  sys.stderr.write('createChannel: adding xml: %s\n' %
> channeldev.toxml())
>
> 42)  devices.appendChild(channeldev)
>
> 43)
>
> 44)  hooking.write_domxml(domxml)
>
> 45)   except:
>
> 46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %
>
> 47)  traceback.format_exc())
>
> 48)  sys.exit(2)
>
>
>
>
>
>
>
> Thx for help.
>
>
>
> Regards,
>
>
>
> J.P.
>
>
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com] *Envoy? :* mardi 12 janvier 
> 2016 16:23 *? :* Jean-Pierre Ribeauville *Cc :* users@ovirt.org *Objet 
> :* Re: [ovirt-users] vdsm hook issues
>
>
>
> 1. Are you using a full OS or a node?
>
> 2. rpm -qa |grep vdsm
>
> 3. if possible, post the hook code
>
>
>
> Thanks
>
>
>
> On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
>
>
> Hi,
>
>
>
> 1)  is it enough to add a hook.py in
> /usr/libexec/vdsm/hooks/before_vm_start directory , and then shut down and
> reboot a guest to
>
> see this hook.py invoked ?
>
>
>
> 2) when running manually my hook.py, I got following error :
>
>  ImportError: No module named hooking
>
>
>
> Do I have to install anything to solve this issue ?
>
>
>
> Thanks for help.
>
>
>
>
>
> Regards,
>
>
>
>
>
>
>
> *J.P. Ribeauville*
>
>
>
> P: +33.(0).1.47.17.20.49
>
> .
>
> Puteaux 3 Etage 5  Bureau 4
>
>
>
> *jpribeauvi...@axway.com *
> http://www.axway.com
>
>
>
>
>
> P Pensez ? l?environnement avant d?imprimer.
>
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.ovirt.org/pipermail/users/attachments/20160112/45a10a2a/attachment.html>

--

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


End of Users Digest, Vol 52, Issue 72
*
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Dan Yasny

So, to make is work, you need to chown 36:36 and chmod +x for 36:36 of
course.

As for logging, since the hook is run under the vdsm context, you can tap
right into the logging of vdsm, or you can write your own log file,
whatever you prefer to code.

See
https://github.com/oVirt/vdsm/blob/master/vdsm_hooks/vmfex/before_vm_start.py
line 197 - sys.stderr.write will actually dump into the vdsm log.

On Tue, Jan 12, 2016 at 10:55 AM, Jean-Pierre Ribeauville <
jpribeauvi...@axway.com> wrote:

> Hi,
>
>
>
> /usr/share/vdsm/hooking.py  is present on my host.
>
>
>
> I placed my test_hook.py  in /usr/libexec/vdsm/hooks/before_vm_start
>
>
>
> As I want to have it invoked for every started VM ,  I don’t need custom
> property ; Am I right ?
>
>
>
> Remains the point “make it accessible to vdsm:kvm”  what do you mean ?
>
>
>
> BTW , are vdsm hooks log infos located in /var/log/vdsm/vdsm.log  ?
>
>
>
> Thx for help.
>
>
>
> J.P.
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 16:48
>
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] vdsm hook issues
>
>
>
> OK, so the hooking module is included in the vdsm package itself. Please
> make sure you have /usr/share/vdsm/hooking.py on the host.
>
>
>
> The manual run fails, because it is not running in the vdsm context, and
> so the modules imported are the python site-packages and not the submodules
> under vdsm.
>
>
>
> To make a hook work, you need to place it on the host, make it accessible
> to vdsm:kvm, and maybe define a custom property, if you don't want the hook
> to just run on every started VM.
>
>
>
> On Tue, Jan 12, 2016 at 10:35 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
> Hi,
>
>
>
> 1°  It’s a full RHEL7 OS.
> 2°
> vdsm-python-zombiereaper-4.16.27-0.el7.centos.noarch
>
> vdsm-python-4.16.27-0.el7.centos.noarch
>
> vdsm-yajsonrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-xmlrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-cli-4.16.27-0.el7.centos.noarch
>
> vdsm-jsonrpc-java-1.0.15-1.el7.noarch
>
> vdsm-jsonrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-4.16.27-0.el7.centos.x86_64
>
> 3°
>
> #!/usr/bin/python
>
> 1)
>
> 2)  import os
>
> 3)  import sys
>
> 4)  import grp
>
> 5)  import pwd
>
> 6)  import traceback
>
> 7)
>
> 8)  import hooking
>
> 9)
>
> 10)   def createChannelElement(domxml):
>
> 11)   '''
>
> 12)   
>
> 13)  path='//var/lib/libvirt/qemu/VM_RHEL7-1_omnivision_1.agent'/>
>
> 14) 
>
> 15)   
>
> 16)   '''
>
> 17)
>
> 18)   channel = domxml.createElement('channel')
>
> 19)   disk.setAttribute('type', 'unix')
>
> 20)
>
> 21)   source = domxml.createElement('source')
>
> 22)   source.setAttribute('mode', 'bind')
>
> 23)
>
> 24)   # find  domain name
>
> 25)   domainame = domxml.getElementsByTagName('name')
>
> 26)
>
> 27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' +
> domainame + '_omnivision_1.agent')
>
> 28)   disk.appendChild(source)
>
> 29)
>
> 30)   target = domxml.createElement('target')
>
> 31)   target.setAttribute('type', 'virtio')
>
> 32)   target.setAttribute('name', 'omnivision_1.agent')
>
> 33)   disk.appendChild(target)
>
> 34)
>
> 35)   return channel
>
> 36)
>
> 37)   try:
>
> 38)  domxml = hooking.read_domxml()
>
> 39)  devices = domxml.getElementsByTagName('devices')[0]
>
> 40)  channeldev = createChannelElement(domxml)
>
> 41)  sys.stderr.write('createChannel: adding xml: %s\n' %
> channeldev.toxml())
>
> 42)  devices.appendChild(channeldev)
>
> 43)
>
> 44)  hooking.write_domxml(domxml)
>
> 45)   except:
>
> 46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %
>
> 47)  traceback.format_exc())
>
> 48)  sys.exit(2)
>
>
>
>
>
>
>
> Thx for help.
>
>
>
> Regards,
>
>
>
> J.P.
>
>
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 16:23
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] vdsm hook issues
>
>
>
> 1. Are you using a full OS or a node?
>
> 2. rpm -qa |grep vdsm
>
> 3. if possible, post the hook code
>
>
>
> Thanks
>
>
>
> On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
>
>
> Hi,
>
>
>
> 1)  is it enough to add a hook.py in
> /usr/libexec/vdsm/hooks/before_vm_start directory , and then shut down and
> reboot a guest to
>
> see this hook.py invoked ?
>
>
>
> 2) when running manually my hook.py, I got following error :
>
>  ImportError: No module named hooking
>
>
>
> Do I have to install anything to solve this issue ?
>
>
>
> Thanks for help.
>
>
>
>
>
> Regards,
>
>
>
>
>
>
>
> *J.P. Ribeauville*
>
>
>
> P: +33.(0).1.47.17.20.49
>
> .
>
> Puteaux 3 Etage 5  Bureau 4
>
>
>
> *jpribeauvi...@axway.com *
> http://www.axway.com
>
>
>
>
>
> P Pensez à l’environnement avant d’imprimer.
>
>
>
>
>
>
> __

[ovirt-users] Ovirt supported thinclient appliance

2016-01-12 Thread RK RK

Hi all,

I am planning to setup oVirt 3.6.1 Virtualization setup for 100 desktop
users in my software development company.

Anyone please suggest me a good and cost-effective thinclient
appliance(available in india) to use with my oVirt environment with support
for SPICE protocol.

-- 

With Regards,
RK,
+91 9840483044
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] User with SuperAdmin Role has not MANIPULATE_STORAGE_DOMAIN

2016-01-12 Thread Maor Lipchuk


- Original Message -
> From: "Kevin COUSIN" 
> To: "Maor Lipchuk" 
> Cc: "users" , "Oved Ourfali" 
> Sent: Tuesday, January 12, 2016 5:06:22 PM
> Subject: Re: [ovirt-users] User with SuperAdmin Role has not 
> MANIPULATE_STORAGE_DOMAIN
> 
> I set SuperAdmin Role on a group.
> It dosen't work with StorageAdmin role.
> I can't add set roles with my directory account, I need to use admin@internal
> account.


Which DC are you trying to attach the Storage Domain?
From the attached print screens it looks like the DC you have permissions on 
are infra and local.
Also, Which oVirt version are you using?
If it is possible can you please send print screens with the permissions of the 
user and the permissions on the Data Center?

Thanks,
Maor


> 
> 
> 
>COUSIN Kevin
> 
> - Mail original -
> > De: "Maor Lipchuk" 
> > À: "Kevin C" 
> > Cc: "users" , "Oved Ourfali" 
> > Envoyé: Mardi 12 Janvier 2016 13:57:16
> > Objet: Re: [ovirt-users] User with SuperAdmin Role has not
> > MANIPULATE_STORAGE_DOMAIN
> 
> > - Original Message -
> >> From: "Kevin C" 
> >> To: "Maor Lipchuk" 
> >> Cc: "users" , "Oved Ourfali" 
> >> Sent: Monday, January 11, 2016 11:04:11 AM
> >> Subject: Re: [ovirt-users] User with SuperAdmin Role has not
> >> MANIPULATE_STORAGE_DOMAIN
> >> 
> >> 
> >> 
> >> Le 09/01/2016 16:09, Maor Lipchuk a écrit :
> >> > Hi Kevin,
> >> >
> >> > Does it still reproduce after the permissions were set?
> >> >
> >> > Regards,
> >> > Maor
> >> >
> >> Hi Maor,
> >> 
> >> Yes it does, I just try it with another Domain.
> >> 
> >> Regards
> > 
> > 
> > Which role have you added to your user? Can u please try to edit the role
> > which
> > you have added to your user, does the role "Configure Storage Domain" is
> > marked
> > (See attached screenshot).
> > Can you please try to add to the user the role StorageAdmin (See second
> > attached
> > screenshot)
> > 
> > Regards,
> > Maor
> > 
> >> 
> >> ---
> >> 
> >> Kevin C
> >> 
> >> 
> >> > - Original Message -
> >> >> From: "Oved Ourfali" 
> >> >> To: "Kevin C" 
> >> >> Cc: "users" 
> >> >> Sent: Friday, January 8, 2016 1:20:53 PM
> >> >> Subject: Re: [ovirt-users] User with SuperAdmin Role has not
> >> >> MANIPULATE_STORAGE_DOMAIN
> >> >>
> >> >>
> >> >>
> >> >> CC-ing someone from the storage team to take a look.
> >> >> On Jan 7, 2016 6:43 PM, "Kevin C" < ke...@famillecousin.fr > wrote:
> >> >>
> >> >>
> >> >>
> >> >> Hi,
> >> >>
> >> >> I set it on "system" level, on right upper side.
> >> >>
> >> >> Regards,
> >> >>
> >> >> Le 07/01/2016 17:39, Oved Ourfali a écrit :
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Permissions in ovirt are composed of the role, user/group, and object.
> >> >>
> >> >> I guess you refer to the SuperUser role. Question is what object you've
> >> >> granted it on.
> >> >>
> >> >> In order to have a permission on "system" level, you gave to go to the
> >> >> configure dialog (see right upper side of your screen).
> >> >>
> >> >> Regards,
> >> >> Oved Ourfali
> >> >> Hi list,
> >> >>
> >> >> I set the SuperAdmin Role on a AD group. I use my account in this group
> >> >> to
> >> >> use oVirt. I try today to add an Export Domain but I failed with this
> >> >> error
> >> >> in log :
> >> >>
> >> >> 2016-01-07 16:46:28,883 INFO
> >> >> [org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand]
> >> >> (default task-1) [68d5410a] No permission found for user
> >> >> '8ac67747-110c-4125-86f1-1f52ca0e7705' or one of the groups he is
> >> >> member
> >> >> of,
> >> >> when running action 'AttachStorageDomainToPool', Required permissions
> >> >> are:
> >> >> Action type: 'ADMIN' Action group: 'MANIPULATE_STORAGE_DOMAIN' Object
> >> >> type:
> >> >> 'Storage' Object ID: 'c7dee64d-a27e-446e-8656-cef2d8ea42a6'.
> >> >>
> >> >>
> >> >> Where can I set the good permission ?
> >> >>
> >> >> Thanks a lot
> >> >> ---
> >> >> Kevin C
> >> >> ___
> >> >> Users mailing list
> >> >> Users@ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> ___
> >> >> Users mailing list
> >> >> Users@ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> >>
> >> 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Dan Yasny

yup. Now add the sys.stderr.write line somewhere, with a marker you can
grep for, and try, then check the vdsm.log file for the marker. I'd also
add an external log dump for the development testing, and comment it out
before going into production

On Tue, Jan 12, 2016 at 11:02 AM, Jean-Pierre Ribeauville <
jpribeauvi...@axway.com> wrote:

> Hi,
>
>
>
> 173078 4 -rwxrwxrwx. 1 vdsm kvm 1292 Jan 12 15:51 test_hook.py
>
>
>
>
>
> Looks fine , isn’t ?
>
>
>
> J.P.
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 17:00
>
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] vdsm hook issues
>
>
>
> So, to make is work, you need to chown 36:36 and chmod +x for 36:36 of
> course.
>
>
>
> As for logging, since the hook is run under the vdsm context, you can tap
> right into the logging of vdsm, or you can write your own log file,
> whatever you prefer to code.
>
>
>
> See
> https://github.com/oVirt/vdsm/blob/master/vdsm_hooks/vmfex/before_vm_start.py
> line 197 - sys.stderr.write will actually dump into the vdsm log.
>
>
>
> On Tue, Jan 12, 2016 at 10:55 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
> Hi,
>
>
>
> /usr/share/vdsm/hooking.py  is present on my host.
>
>
>
> I placed my test_hook.py  in /usr/libexec/vdsm/hooks/before_vm_start
>
>
>
> As I want to have it invoked for every started VM ,  I don’t need custom
> property ; Am I right ?
>
>
>
> Remains the point “make it accessible to vdsm:kvm”  what do you mean ?
>
>
>
> BTW , are vdsm hooks log infos located in /var/log/vdsm/vdsm.log  ?
>
>
>
> Thx for help.
>
>
>
> J.P.
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 16:48
>
>
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] vdsm hook issues
>
>
>
> OK, so the hooking module is included in the vdsm package itself. Please
> make sure you have /usr/share/vdsm/hooking.py on the host.
>
>
>
> The manual run fails, because it is not running in the vdsm context, and
> so the modules imported are the python site-packages and not the submodules
> under vdsm.
>
>
>
> To make a hook work, you need to place it on the host, make it accessible
> to vdsm:kvm, and maybe define a custom property, if you don't want the hook
> to just run on every started VM.
>
>
>
> On Tue, Jan 12, 2016 at 10:35 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
> Hi,
>
>
>
> 1°  It’s a full RHEL7 OS.
> 2°
> vdsm-python-zombiereaper-4.16.27-0.el7.centos.noarch
>
> vdsm-python-4.16.27-0.el7.centos.noarch
>
> vdsm-yajsonrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-xmlrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-cli-4.16.27-0.el7.centos.noarch
>
> vdsm-jsonrpc-java-1.0.15-1.el7.noarch
>
> vdsm-jsonrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-4.16.27-0.el7.centos.x86_64
>
> 3°
>
> #!/usr/bin/python
>
> 1)
>
> 2)  import os
>
> 3)  import sys
>
> 4)  import grp
>
> 5)  import pwd
>
> 6)  import traceback
>
> 7)
>
> 8)  import hooking
>
> 9)
>
> 10)   def createChannelElement(domxml):
>
> 11)   '''
>
> 12)   
>
> 13)  path='//var/lib/libvirt/qemu/VM_RHEL7-1_omnivision_1.agent'/>
>
> 14) 
>
> 15)   
>
> 16)   '''
>
> 17)
>
> 18)   channel = domxml.createElement('channel')
>
> 19)   disk.setAttribute('type', 'unix')
>
> 20)
>
> 21)   source = domxml.createElement('source')
>
> 22)   source.setAttribute('mode', 'bind')
>
> 23)
>
> 24)   # find  domain name
>
> 25)   domainame = domxml.getElementsByTagName('name')
>
> 26)
>
> 27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' +
> domainame + '_omnivision_1.agent')
>
> 28)   disk.appendChild(source)
>
> 29)
>
> 30)   target = domxml.createElement('target')
>
> 31)   target.setAttribute('type', 'virtio')
>
> 32)   target.setAttribute('name', 'omnivision_1.agent')
>
> 33)   disk.appendChild(target)
>
> 34)
>
> 35)   return channel
>
> 36)
>
> 37)   try:
>
> 38)  domxml = hooking.read_domxml()
>
> 39)  devices = domxml.getElementsByTagName('devices')[0]
>
> 40)  channeldev = createChannelElement(domxml)
>
> 41)  sys.stderr.write('createChannel: adding xml: %s\n' %
> channeldev.toxml())
>
> 42)  devices.appendChild(channeldev)
>
> 43)
>
> 44)  hooking.write_domxml(domxml)
>
> 45)   except:
>
> 46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %
>
> 47)  traceback.format_exc())
>
> 48)  sys.exit(2)
>
>
>
>
>
>
>
> Thx for help.
>
>
>
> Regards,
>
>
>
> J.P.
>
>
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 16:23
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] vdsm hook issues
>
>
>
> 1. Are you using a full OS or a node?
>
> 2. rpm -qa |grep vdsm
>
> 3. if possible, post the hook code
>
>
>
> Thanks
>
>
>
> On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.c

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville

Hi,

173078 4 -rwxrwxrwx. 1 vdsm kvm 1292 Jan 12 15:51 test_hook.py


Looks fine , isn’t ?

J.P.

De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 17:00
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] vdsm hook issues

So, to make is work, you need to chown 36:36 and chmod +x for 36:36 of course.

As for logging, since the hook is run under the vdsm context, you can tap right 
into the logging of vdsm, or you can write your own log file, whatever you 
prefer to code.

See 
https://github.com/oVirt/vdsm/blob/master/vdsm_hooks/vmfex/before_vm_start.py 
line 197 - sys.stderr.write will actually dump into the vdsm log.

On Tue, Jan 12, 2016 at 10:55 AM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:
Hi,

/usr/share/vdsm/hooking.py  is present on my host.

I placed my test_hook.py  in /usr/libexec/vdsm/hooks/before_vm_start

As I want to have it invoked for every started VM ,  I don’t need custom 
property ; Am I right ?

Remains the point “make it accessible to vdsm:kvm”  what do you mean ?

BTW , are vdsm hooks log infos located in /var/log/vdsm/vdsm.log  ?

Thx for help.

J.P.

De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 16:48

À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] vdsm hook issues

OK, so the hooking module is included in the vdsm package itself. Please make 
sure you have /usr/share/vdsm/hooking.py on the host.

The manual run fails, because it is not running in the vdsm context, and so the 
modules imported are the python site-packages and not the submodules under vdsm.

To make a hook work, you need to place it on the host, make it accessible to 
vdsm:kvm, and maybe define a custom property, if you don't want the hook to 
just run on every started VM.

On Tue, Jan 12, 2016 at 10:35 AM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:
Hi,


1°  It’s a full RHEL7 OS.
2°
vdsm-python-zombiereaper-4.16.27-0.el7.centos.noarch

vdsm-python-4.16.27-0.el7.centos.noarch

vdsm-yajsonrpc-4.16.27-0.el7.centos.noarch

vdsm-xmlrpc-4.16.27-0.el7.centos.noarch

vdsm-cli-4.16.27-0.el7.centos.noarch

vdsm-jsonrpc-java-1.0.15-1.el7.noarch

vdsm-jsonrpc-4.16.27-0.el7.centos.noarch

vdsm-4.16.27-0.el7.centos.x86_64
3°
#!/usr/bin/python

1)

2)  import os

3)  import sys

4)  import grp

5)  import pwd

6)  import traceback

7)

8)  import hooking

9)

10)   def createChannelElement(domxml):

11)   '''

12)   

13) 

14) 

15)   

16)   '''

17)

18)   channel = domxml.createElement('channel')

19)   disk.setAttribute('type', 'unix')

20)

21)   source = domxml.createElement('source')

22)   source.setAttribute('mode', 'bind')

23)

24)   # find  domain name

25)   domainame = domxml.getElementsByTagName('name')

26)

27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' + domainame + 
'_omnivision_1.agent')

28)   disk.appendChild(source)

29)

30)   target = domxml.createElement('target')

31)   target.setAttribute('type', 'virtio')

32)   target.setAttribute('name', 'omnivision_1.agent')

33)   disk.appendChild(target)

34)

35)   return channel

36)

37)   try:

38)  domxml = hooking.read_domxml()

39)  devices = domxml.getElementsByTagName('devices')[0]

40)  channeldev = createChannelElement(domxml)

41)  sys.stderr.write('createChannel: adding xml: %s\n' % 
channeldev.toxml())

42)  devices.appendChild(channeldev)

43)

44)  hooking.write_domxml(domxml)

45)   except:

46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %

47)  traceback.format_exc())

48)  sys.exit(2)



Thx for help.

Regards,

J.P.


De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 16:23
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] vdsm hook issues

1. Are you using a full OS or a node?
2. rpm -qa |grep vdsm
3. if possible, post the hook code

Thanks

On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:

Hi,

1)  is it enough to add a hook.py in  /usr/libexec/vdsm/hooks/before_vm_start 
directory , and then shut down and reboot a guest to
see this hook.py invoked ?

2) when running manually my hook.py, I got following error :
 ImportError: No module named hooking

Do I have to install anything to solve this issue ?

Thanks for help.


Regards,



J.P. Ribeauville


P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5  Bureau 4

jpribeauvi...@axway.com
http://www.axway.com



P Pensez à l’environnement avant d’imprimer.




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



__

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville

Hi,

/usr/share/vdsm/hooking.py  is present on my host.

I placed my test_hook.py  in /usr/libexec/vdsm/hooks/before_vm_start

As I want to have it invoked for every started VM ,  I don’t need custom 
property ; Am I right ?

Remains the point “make it accessible to vdsm:kvm”  what do you mean ?

BTW , are vdsm hooks log infos located in /var/log/vdsm/vdsm.log  ?

Thx for help.

J.P.

De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 16:48
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] vdsm hook issues

OK, so the hooking module is included in the vdsm package itself. Please make 
sure you have /usr/share/vdsm/hooking.py on the host.

The manual run fails, because it is not running in the vdsm context, and so the 
modules imported are the python site-packages and not the submodules under vdsm.

To make a hook work, you need to place it on the host, make it accessible to 
vdsm:kvm, and maybe define a custom property, if you don't want the hook to 
just run on every started VM.

On Tue, Jan 12, 2016 at 10:35 AM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:
Hi,


1°  It’s a full RHEL7 OS.
2°
vdsm-python-zombiereaper-4.16.27-0.el7.centos.noarch

vdsm-python-4.16.27-0.el7.centos.noarch

vdsm-yajsonrpc-4.16.27-0.el7.centos.noarch

vdsm-xmlrpc-4.16.27-0.el7.centos.noarch

vdsm-cli-4.16.27-0.el7.centos.noarch

vdsm-jsonrpc-java-1.0.15-1.el7.noarch

vdsm-jsonrpc-4.16.27-0.el7.centos.noarch

vdsm-4.16.27-0.el7.centos.x86_64
3°
#!/usr/bin/python

1)

2)  import os

3)  import sys

4)  import grp

5)  import pwd

6)  import traceback

7)

8)  import hooking

9)

10)   def createChannelElement(domxml):

11)   '''

12)   

13) 

14) 

15)   

16)   '''

17)

18)   channel = domxml.createElement('channel')

19)   disk.setAttribute('type', 'unix')

20)

21)   source = domxml.createElement('source')

22)   source.setAttribute('mode', 'bind')

23)

24)   # find  domain name

25)   domainame = domxml.getElementsByTagName('name')

26)

27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' + domainame + 
'_omnivision_1.agent')

28)   disk.appendChild(source)

29)

30)   target = domxml.createElement('target')

31)   target.setAttribute('type', 'virtio')

32)   target.setAttribute('name', 'omnivision_1.agent')

33)   disk.appendChild(target)

34)

35)   return channel

36)

37)   try:

38)  domxml = hooking.read_domxml()

39)  devices = domxml.getElementsByTagName('devices')[0]

40)  channeldev = createChannelElement(domxml)

41)  sys.stderr.write('createChannel: adding xml: %s\n' % 
channeldev.toxml())

42)  devices.appendChild(channeldev)

43)

44)  hooking.write_domxml(domxml)

45)   except:

46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %

47)  traceback.format_exc())

48)  sys.exit(2)



Thx for help.

Regards,

J.P.


De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 16:23
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] vdsm hook issues

1. Are you using a full OS or a node?
2. rpm -qa |grep vdsm
3. if possible, post the hook code

Thanks

On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:

Hi,

1)  is it enough to add a hook.py in  /usr/libexec/vdsm/hooks/before_vm_start 
directory , and then shut down and reboot a guest to
see this hook.py invoked ?

2) when running manually my hook.py, I got following error :
 ImportError: No module named hooking

Do I have to install anything to solve this issue ?

Thanks for help.


Regards,



J.P. Ribeauville


P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5  Bureau 4

jpribeauvi...@axway.com
http://www.axway.com



P Pensez à l’environnement avant d’imprimer.




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


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

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Dan Yasny

OK, so the hooking module is included in the vdsm package itself. Please
make sure you have /usr/share/vdsm/hooking.py on the host.

The manual run fails, because it is not running in the vdsm context, and so
the modules imported are the python site-packages and not the submodules
under vdsm.

To make a hook work, you need to place it on the host, make it accessible
to vdsm:kvm, and maybe define a custom property, if you don't want the hook
to just run on every started VM.

On Tue, Jan 12, 2016 at 10:35 AM, Jean-Pierre Ribeauville <
jpribeauvi...@axway.com> wrote:

> Hi,
>
>
>
> 1°  It’s a full RHEL7 OS.
> 2°
> vdsm-python-zombiereaper-4.16.27-0.el7.centos.noarch
>
> vdsm-python-4.16.27-0.el7.centos.noarch
>
> vdsm-yajsonrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-xmlrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-cli-4.16.27-0.el7.centos.noarch
>
> vdsm-jsonrpc-java-1.0.15-1.el7.noarch
>
> vdsm-jsonrpc-4.16.27-0.el7.centos.noarch
>
> vdsm-4.16.27-0.el7.centos.x86_64
>
> 3°
>
> #!/usr/bin/python
>
> 1)
>
> 2)  import os
>
> 3)  import sys
>
> 4)  import grp
>
> 5)  import pwd
>
> 6)  import traceback
>
> 7)
>
> 8)  import hooking
>
> 9)
>
> 10)   def createChannelElement(domxml):
>
> 11)   '''
>
> 12)   
>
> 13)  path='//var/lib/libvirt/qemu/VM_RHEL7-1_omnivision_1.agent'/>
>
> 14) 
>
> 15)   
>
> 16)   '''
>
> 17)
>
> 18)   channel = domxml.createElement('channel')
>
> 19)   disk.setAttribute('type', 'unix')
>
> 20)
>
> 21)   source = domxml.createElement('source')
>
> 22)   source.setAttribute('mode', 'bind')
>
> 23)
>
> 24)   # find  domain name
>
> 25)   domainame = domxml.getElementsByTagName('name')
>
> 26)
>
> 27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' +
> domainame + '_omnivision_1.agent')
>
> 28)   disk.appendChild(source)
>
> 29)
>
> 30)   target = domxml.createElement('target')
>
> 31)   target.setAttribute('type', 'virtio')
>
> 32)   target.setAttribute('name', 'omnivision_1.agent')
>
> 33)   disk.appendChild(target)
>
> 34)
>
> 35)   return channel
>
> 36)
>
> 37)   try:
>
> 38)  domxml = hooking.read_domxml()
>
> 39)  devices = domxml.getElementsByTagName('devices')[0]
>
> 40)  channeldev = createChannelElement(domxml)
>
> 41)  sys.stderr.write('createChannel: adding xml: %s\n' %
> channeldev.toxml())
>
> 42)  devices.appendChild(channeldev)
>
> 43)
>
> 44)  hooking.write_domxml(domxml)
>
> 45)   except:
>
> 46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %
>
> 47)  traceback.format_exc())
>
> 48)  sys.exit(2)
>
>
>
>
>
>
>
> Thx for help.
>
>
>
> Regards,
>
>
>
> J.P.
>
>
>
>
>
> *De :* Dan Yasny [mailto:dya...@gmail.com]
> *Envoyé :* mardi 12 janvier 2016 16:23
> *À :* Jean-Pierre Ribeauville
> *Cc :* users@ovirt.org
> *Objet :* Re: [ovirt-users] vdsm hook issues
>
>
>
> 1. Are you using a full OS or a node?
>
> 2. rpm -qa |grep vdsm
>
> 3. if possible, post the hook code
>
>
>
> Thanks
>
>
>
> On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville <
> jpribeauvi...@axway.com> wrote:
>
>
>
> Hi,
>
>
>
> 1)  is it enough to add a hook.py in
> /usr/libexec/vdsm/hooks/before_vm_start directory , and then shut down and
> reboot a guest to
>
> see this hook.py invoked ?
>
>
>
> 2) when running manually my hook.py, I got following error :
>
>  ImportError: No module named hooking
>
>
>
> Do I have to install anything to solve this issue ?
>
>
>
> Thanks for help.
>
>
>
>
>
> Regards,
>
>
>
>
>
>
>
> *J.P. Ribeauville*
>
>
>
> P: +33.(0).1.47.17.20.49
>
> .
>
> Puteaux 3 Etage 5  Bureau 4
>
>
>
> *jpribeauvi...@axway.com *
> http://www.axway.com
>
>
>
>
>
> P Pensez à l’environnement avant d’imprimer.
>
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville

Hi,


1°  It’s a full RHEL7 OS.
2°
vdsm-python-zombiereaper-4.16.27-0.el7.centos.noarch

vdsm-python-4.16.27-0.el7.centos.noarch

vdsm-yajsonrpc-4.16.27-0.el7.centos.noarch

vdsm-xmlrpc-4.16.27-0.el7.centos.noarch

vdsm-cli-4.16.27-0.el7.centos.noarch

vdsm-jsonrpc-java-1.0.15-1.el7.noarch

vdsm-jsonrpc-4.16.27-0.el7.centos.noarch

vdsm-4.16.27-0.el7.centos.x86_64
3°
#!/usr/bin/python

1)

2)  import os

3)  import sys

4)  import grp

5)  import pwd

6)  import traceback

7)

8)  import hooking

9)

10)   def createChannelElement(domxml):

11)   '''

12)   

13) 

14) 

15)   

16)   '''

17)

18)   channel = domxml.createElement('channel')

19)   disk.setAttribute('type', 'unix')

20)

21)   source = domxml.createElement('source')

22)   source.setAttribute('mode', 'bind')

23)

24)   # find  domain name

25)   domainame = domxml.getElementsByTagName('name')

26)

27)   source.setAttribute('path', '//var/lib/libvirt/qemu/' + domainame + 
'_omnivision_1.agent')

28)   disk.appendChild(source)

29)

30)   target = domxml.createElement('target')

31)   target.setAttribute('type', 'virtio')

32)   target.setAttribute('name', 'omnivision_1.agent')

33)   disk.appendChild(target)

34)

35)   return channel

36)

37)   try:

38)  domxml = hooking.read_domxml()

39)  devices = domxml.getElementsByTagName('devices')[0]

40)  channeldev = createChannelElement(domxml)

41)  sys.stderr.write('createChannel: adding xml: %s\n' % 
channeldev.toxml())

42)  devices.appendChild(channeldev)

43)

44)  hooking.write_domxml(domxml)

45)   except:

46)  sys.stderr.write('createChannel: [unexpected error]: %s\n' %

47)  traceback.format_exc())

48)  sys.exit(2)



Thx for help.

Regards,

J.P.


De : Dan Yasny [mailto:dya...@gmail.com]
Envoyé : mardi 12 janvier 2016 16:23
À : Jean-Pierre Ribeauville
Cc : users@ovirt.org
Objet : Re: [ovirt-users] vdsm hook issues

1. Are you using a full OS or a node?
2. rpm -qa |grep vdsm
3. if possible, post the hook code

Thanks

On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville 
mailto:jpribeauvi...@axway.com>> wrote:

Hi,

1)  is it enough to add a hook.py in  /usr/libexec/vdsm/hooks/before_vm_start 
directory , and then shut down and reboot a guest to
see this hook.py invoked ?

2) when running manually my hook.py, I got following error :
 ImportError: No module named hooking

Do I have to install anything to solve this issue ?

Thanks for help.


Regards,



J.P. Ribeauville


P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5  Bureau 4

jpribeauvi...@axway.com
http://www.axway.com



P Pensez à l’environnement avant d’imprimer.




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

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

Re: [ovirt-users] vdsm hook issues

2016-01-12 Thread Dan Yasny

1. Are you using a full OS or a node?
2. rpm -qa |grep vdsm
3. if possible, post the hook code

Thanks

On Tue, Jan 12, 2016 at 10:17 AM, Jean-Pierre Ribeauville <
jpribeauvi...@axway.com> wrote:

>
>
> Hi,
>
>
>
> 1)  is it enough to add a hook.py in
> /usr/libexec/vdsm/hooks/before_vm_start directory , and then shut down and
> reboot a guest to
>
> see this hook.py invoked ?
>
>
>
> 2) when running manually my hook.py, I got following error :
>
>  ImportError: No module named hooking
>
>
>
> Do I have to install anything to solve this issue ?
>
>
>
> Thanks for help.
>
>
>
>
>
> Regards,
>
>
>
>
>
>
>
> *J.P. Ribeauville*
>
>
>
> P: +33.(0).1.47.17.20.49
>
> .
>
> Puteaux 3 Etage 5  Bureau 4
>
>
>
> *jpribeauvi...@axway.com *
> http://www.axway.com
>
>
>
>
>
> P Pensez à l’environnement avant d’imprimer.
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] vdsm hook issues

2016-01-12 Thread Jean-Pierre Ribeauville


Hi,

1)  is it enough to add a hook.py in  /usr/libexec/vdsm/hooks/before_vm_start 
directory , and then shut down and reboot a guest to
see this hook.py invoked ?

2) when running manually my hook.py, I got following error :
 ImportError: No module named hooking

Do I have to install anything to solve this issue ?

Thanks for help.


Regards,



J.P. Ribeauville


P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5  Bureau 4

jpribeauvi...@axway.com
http://www.axway.com



P Pensez à l'environnement avant d'imprimer.



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

Re: [ovirt-users] User with SuperAdmin Role has not MANIPULATE_STORAGE_DOMAIN

2016-01-12 Thread Kevin COUSIN

I set SuperAdmin Role on a group. 
It dosen't work with StorageAdmin role.
I can't add set roles with my directory account, I need to use admin@internal 
account.



   COUSIN Kevin

- Mail original -
> De: "Maor Lipchuk" 
> À: "Kevin C" 
> Cc: "users" , "Oved Ourfali" 
> Envoyé: Mardi 12 Janvier 2016 13:57:16
> Objet: Re: [ovirt-users] User with SuperAdmin Role has not 
> MANIPULATE_STORAGE_DOMAIN

> - Original Message -
>> From: "Kevin C" 
>> To: "Maor Lipchuk" 
>> Cc: "users" , "Oved Ourfali" 
>> Sent: Monday, January 11, 2016 11:04:11 AM
>> Subject: Re: [ovirt-users] User with SuperAdmin Role has not
>> MANIPULATE_STORAGE_DOMAIN
>> 
>> 
>> 
>> Le 09/01/2016 16:09, Maor Lipchuk a écrit :
>> > Hi Kevin,
>> >
>> > Does it still reproduce after the permissions were set?
>> >
>> > Regards,
>> > Maor
>> >
>> Hi Maor,
>> 
>> Yes it does, I just try it with another Domain.
>> 
>> Regards
> 
> 
> Which role have you added to your user? Can u please try to edit the role 
> which
> you have added to your user, does the role "Configure Storage Domain" is 
> marked
> (See attached screenshot).
> Can you please try to add to the user the role StorageAdmin (See second 
> attached
> screenshot)
> 
> Regards,
> Maor
> 
>> 
>> ---
>> 
>> Kevin C
>> 
>> 
>> > - Original Message -
>> >> From: "Oved Ourfali" 
>> >> To: "Kevin C" 
>> >> Cc: "users" 
>> >> Sent: Friday, January 8, 2016 1:20:53 PM
>> >> Subject: Re: [ovirt-users] User with SuperAdmin Role has not
>> >>   MANIPULATE_STORAGE_DOMAIN
>> >>
>> >>
>> >>
>> >> CC-ing someone from the storage team to take a look.
>> >> On Jan 7, 2016 6:43 PM, "Kevin C" < ke...@famillecousin.fr > wrote:
>> >>
>> >>
>> >>
>> >> Hi,
>> >>
>> >> I set it on "system" level, on right upper side.
>> >>
>> >> Regards,
>> >>
>> >> Le 07/01/2016 17:39, Oved Ourfali a écrit :
>> >>
>> >>
>> >>
>> >>
>> >> Permissions in ovirt are composed of the role, user/group, and object.
>> >>
>> >> I guess you refer to the SuperUser role. Question is what object you've
>> >> granted it on.
>> >>
>> >> In order to have a permission on "system" level, you gave to go to the
>> >> configure dialog (see right upper side of your screen).
>> >>
>> >> Regards,
>> >> Oved Ourfali
>> >> Hi list,
>> >>
>> >> I set the SuperAdmin Role on a AD group. I use my account in this group to
>> >> use oVirt. I try today to add an Export Domain but I failed with this
>> >> error
>> >> in log :
>> >>
>> >> 2016-01-07 16:46:28,883 INFO
>> >> [org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand]
>> >> (default task-1) [68d5410a] No permission found for user
>> >> '8ac67747-110c-4125-86f1-1f52ca0e7705' or one of the groups he is member
>> >> of,
>> >> when running action 'AttachStorageDomainToPool', Required permissions are:
>> >> Action type: 'ADMIN' Action group: 'MANIPULATE_STORAGE_DOMAIN' Object
>> >> type:
>> >> 'Storage' Object ID: 'c7dee64d-a27e-446e-8656-cef2d8ea42a6'.
>> >>
>> >>
>> >> Where can I set the good permission ?
>> >>
>> >> Thanks a lot
>> >> ---
>> >> Kevin C
>> >> ___
>> >> Users mailing list
>> >> Users@ovirt.org
>> >> http://lists.ovirt.org/mailman/listinfo/users
>> >>
>> >>
>> >>
>> >>
>> >> ___
>> >> Users mailing list
>> >> Users@ovirt.org
>> >> http://lists.ovirt.org/mailman/listinfo/users
>> >>
>> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Still not possible to resize hosted engine disk?

2016-01-12 Thread Simone Tiraboschi

On Tue, Jan 12, 2016 at 2:36 PM, Cristian Mammoli  wrote:

> Hi, I'm using 3.6.2 pre and using hosted engine over iscsi. The appliance
> provisioned a 10GB virtual disk, even if the LUN is 100GB. How can I extend
> the vm disk? From the gui it doesn't seem to be possible (VM is not managed
> by the engine).
>
>
Not from hosted-engine-setup ad deploy stage.
Adding Roy to discuss about extending it from the engine.



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

[ovirt-users] Still not possible to resize hosted engine disk?

2016-01-12 Thread Cristian Mammoli

Hi, I'm using 3.6.2 pre and using hosted engine over iscsi. The 
appliance provisioned a 10GB virtual disk, even if the LUN is 100GB. How 
can I extend the vm disk? From the gui it doesn't seem to be possible 
(VM is not managed by the engine).


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

Re: [ovirt-users] User with SuperAdmin Role has not MANIPULATE_STORAGE_DOMAIN

2016-01-12 Thread Maor Lipchuk





- Original Message -
> From: "Kevin C" 
> To: "Maor Lipchuk" 
> Cc: "users" , "Oved Ourfali" 
> Sent: Monday, January 11, 2016 11:04:11 AM
> Subject: Re: [ovirt-users] User with SuperAdmin Role has not 
> MANIPULATE_STORAGE_DOMAIN
> 
> 
> 
> Le 09/01/2016 16:09, Maor Lipchuk a écrit :
> > Hi Kevin,
> >
> > Does it still reproduce after the permissions were set?
> >
> > Regards,
> > Maor
> >
> Hi Maor,
> 
> Yes it does, I just try it with another Domain.
> 
> Regards


Which role have you added to your user? Can u please try to edit the role which 
you have added to your user, does the role "Configure Storage Domain" is marked 
(See attached screenshot).
Can you please try to add to the user the role StorageAdmin (See second 
attached screenshot)

Regards,
Maor

> 
> ---
> 
> Kevin C
> 
> 
> > - Original Message -
> >> From: "Oved Ourfali" 
> >> To: "Kevin C" 
> >> Cc: "users" 
> >> Sent: Friday, January 8, 2016 1:20:53 PM
> >> Subject: Re: [ovirt-users] User with SuperAdmin Role has not
> >>MANIPULATE_STORAGE_DOMAIN
> >>
> >>
> >>
> >> CC-ing someone from the storage team to take a look.
> >> On Jan 7, 2016 6:43 PM, "Kevin C" < ke...@famillecousin.fr > wrote:
> >>
> >>
> >>
> >> Hi,
> >>
> >> I set it on "system" level, on right upper side.
> >>
> >> Regards,
> >>
> >> Le 07/01/2016 17:39, Oved Ourfali a écrit :
> >>
> >>
> >>
> >>
> >> Permissions in ovirt are composed of the role, user/group, and object.
> >>
> >> I guess you refer to the SuperUser role. Question is what object you've
> >> granted it on.
> >>
> >> In order to have a permission on "system" level, you gave to go to the
> >> configure dialog (see right upper side of your screen).
> >>
> >> Regards,
> >> Oved Ourfali
> >> Hi list,
> >>
> >> I set the SuperAdmin Role on a AD group. I use my account in this group to
> >> use oVirt. I try today to add an Export Domain but I failed with this
> >> error
> >> in log :
> >>
> >> 2016-01-07 16:46:28,883 INFO
> >> [org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand]
> >> (default task-1) [68d5410a] No permission found for user
> >> '8ac67747-110c-4125-86f1-1f52ca0e7705' or one of the groups he is member
> >> of,
> >> when running action 'AttachStorageDomainToPool', Required permissions are:
> >> Action type: 'ADMIN' Action group: 'MANIPULATE_STORAGE_DOMAIN' Object
> >> type:
> >> 'Storage' Object ID: 'c7dee64d-a27e-446e-8656-cef2d8ea42a6'.
> >>
> >>
> >> Where can I set the good permission ?
> >>
> >> Thanks a lot
> >> ---
> >> Kevin C
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
> >>
> >>
> >>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
> 
>___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Gluster-users] Blog on Hyperconverged Infrastructure using oVirt and Gluster

2016-01-12 Thread Lindsay Mathieson


On 12/01/2016 9:40 PM, Ramesh Nachimuthu wrote:
[1] 
http://blogs-ramesh.blogspot.in/2016/01/ovirt-and-gluster-hyperconvergence.htm

*
*



Missing the last 'l'

http://blogs-ramesh.blogspot.in/2016/01/ovirt-and-gluster-hyperconvergence.html

--
Lindsay Mathieson

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

Re: [ovirt-users] NFS IO timeout configuration

2016-01-12 Thread Yaniv Kaul

On Tue, Jan 12, 2016 at 9:32 AM, Markus Stockhausen  wrote:

> Hi there,
>
> we got a nasty situation yesterday in our OVirt 3.5.6 environment.
> We ran a LSM that failed during the cleanup operation. To be precise
> when the process deleted an image on the source NFS storage.
>

Can you share with us your NFS server details?
Is the NFS connection healthy (can be seen with nfsstat)
Generally, delete on NFS should be a pretty quick operation.
Y.


>
> Engine log gives:
>
> 2016-01-11 20:49:45,120 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand]
> (org.ovirt.thread.pool-8-thread-14) [77277f0] START,
> DeleteImageGroupVDSCommand( storagePoolId =
> 94ed7a19-fade-4bd6-83f2-2cbb2f730b95, ignoreFailoverLimit = false,
> storageDomainId = 272ec473-6041-42ee-bd1a-732789dd18d4, imageGroupId =
> aed132ef-703a-44d0-b875-db8c0d2c1a92, postZeros = false, forceDelete =
> false), log id: b52d59c
> ...
> 2016-01-11 20:50:45,206 ERROR
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand]
> (org.ovirt.thread.pool-8-thread-14) [77277f0] Failed in DeleteImageGroupVDS
> method
>
> VDSM (SPM) log gives:
>
> Thread-97::DEBUG::2016-01-11
> 20:49:45,737::fileSD::384::Storage.StorageDomain::(deleteImage) Removing
> file: /rhev/data-center/mnt/1.2.3.4:
> _var_nas2_OVirtIB/272ec473-6041-42ee-bd1a-732789dd18d4/images/_remojzBd1r/0d623afb-291e-4f4c-acba-caecb125c4ed
> ...
> Thread-97::ERROR::2016-01-11
> 20:50:45,737::task::866::Storage.TaskManager.Task::(_setError)
> Task=`cd477878-47b4-44b1-85a3-b5da19543a5e`::Unexpected error
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 873, in _run
> return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
> res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 1549, in deleteImage
> pool.deleteImage(dom, imgUUID, volsByImg)
>   File "/usr/share/vdsm/storage/securable.py", line 77, in wrapper
> return method(self, *args, **kwargs)
>   File "/usr/share/vdsm/storage/sp.py", line 1884, in deleteImage
> domain.deleteImage(domain.sdUUID, imgUUID, volsByImg)
>   File "/usr/share/vdsm/storage/fileSD.py", line 385, in deleteImage
> self.oop.os.remove(volPath)
>   File "/usr/share/vdsm/storage/outOfProcess.py", line 245, in remove
> self._iop.unlink(path)
>   File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 455,
> in unlink
> return self._sendCommand("unlink", {"path": path}, self.timeout)
>   File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 385,
> in _sendCommand
> raise Timeout(os.strerror(errno.ETIMEDOUT))
> Timeout: Connection timed out
>
> Reading the docs I got the idea that vdsm default 60 second timeout
> for IO operations might be changed within /etc/vdsm/vdsm.conf
>
> [irs]
> process_pool_timeout = 180
>
> Can anyone confirm that this will solve the problem?
>
> Markus
>
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to start nor to migrate vm

2016-01-12 Thread Arsène Gschwind


Hi,

I've just restarted libvirtd on all nodes and now it seems to work 
again. Libvirtd was running before I've restarted it but for some reason 
it could not communicate with other services.

Libvirt is the latest from RH7.2 update and qemu-kvm-ev from ovirt repo.

Thanks a lot for your help.
rgds,
Arsène

On 01/12/2016 12:11 PM, Michal Skrivanek wrote:


On 11 Jan 2016, at 18:33, Arsène Gschwind > wrote:


Please find logs attached

rgds,
Arsène

On 01/11/2016 05:52 PM, Yaniv Dary wrote:

Please attach logs.

Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 
Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : 
+972 (9) 7692306 8272306 Email: yd...@redhat.com 
 IRC : ydary


On Mon, Jan 11, 2016 at 6:31 PM, Arsène Gschwind 
mailto:arsene.gschw...@unibas.ch>> wrote:


Hi,

I'm having trouble with our ovirt environment, i'm not able to
start VMs nor to migrate running ones, i'm getting the following
error:

libvirtError: error from service: ListActivatableNames: Did not
receive a reply. Possible causes include: the remote application
did not send a reply, the message bus security policy blocked
the reply, the reply timeout expired, or the network connection
was broken.



Hi,
libvirt is latest from 7.2 updates?
qemu-kvm-ev from ovirt repo?
anything wrong with systemd or libvirt? seem like when libvirt talks 
to systemd it can’t.


Thanks,
michal



Any idea what causes this error?

oVirt (oVirt Engine Version: 3.5.6.2-1.el7.centos) running on:
CentOS Linux release 7.2.1511
kernel : 3.10.0-327.4.4.el7.x86_64

Nodes:
Red Hat Enterprise Linux Server release 7.2 (Maipo)
vdsm-python-4.16.30-0.el7.centos.noarch
vdsm-cli-4.16.30-0.el7.centos.noarch
vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch
vdsm-xmlrpc-4.16.30-0.el7.centos.noarch
vdsm-hook-vmdisk-4.16.30-0.el7.centos.noarch
vdsm-jsonrpc-4.16.30-0.el7.centos.noarch
vdsm-hook-floppy-4.16.30-0.el7.centos.noarch
vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch
vdsm-4.16.30-0.el7.centos.x86_64
vdsm-hook-vhostmd-4.16.30-0.el7.centos.noarch

Thanks for any hint/help.
rgds,
Arsène
___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users




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




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

[ovirt-users] Blog on Hyperconverged Infrastructure using oVirt and Gluster

2016-01-12 Thread Ramesh Nachimuthu


Hi Folks,

  Have you ever wondered about Hyperconverged Ovirt and Gluster Setup. 
Here is an answer[1]. I wrote a blog explaining how to setup oVirt in a 
hyper-converged mode with Gluster.


[1] 
http://blogs-ramesh.blogspot.in/2016/01/ovirt-and-gluster-hyperconvergence.htm 


*
*Regards,
Ramesh
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to start nor to migrate vm

2016-01-12 Thread Michal Skrivanek


> On 11 Jan 2016, at 18:33, Arsène Gschwind  wrote:
> 
> Please find logs attached
> 
> rgds,
> Arsène
> 
> On 01/11/2016 05:52 PM, Yaniv Dary wrote:
>> Please attach logs.
>> 
>> Yaniv Dary
>> Technical Product Manager
>> Red Hat Israel Ltd.
>> 34 Jerusalem Road
>> Building A, 4th floor
>> Ra'anana, Israel 4350109
>> 
>> Tel : +972 (9) 7692306
>> 8272306
>> Email: yd...@redhat.com 
>> IRC : ydary
>> 
>> On Mon, Jan 11, 2016 at 6:31 PM, Arsène Gschwind > > wrote:
>> Hi,
>> 
>> I'm having trouble with our ovirt environment, i'm not able to start VMs nor 
>> to migrate running ones, i'm getting the following error:
>> 
>> libvirtError: error from service: ListActivatableNames: Did not receive a 
>> reply. Possible causes include: the remote application did not send a reply, 
>> the message bus security policy blocked the reply, the reply timeout 
>> expired, or the network connection was broken.

Hi,
libvirt is latest from 7.2 updates?
qemu-kvm-ev from ovirt repo?
anything wrong with systemd or libvirt? seem like when libvirt talks to systemd 
it can’t.

Thanks,
michal
>> 
>> Any idea what causes this error?
>> 
>> oVirt (oVirt Engine Version: 3.5.6.2-1.el7.centos) running on:
>> CentOS Linux release 7.2.1511
>> kernel : 3.10.0-327.4.4.el7.x86_64
>> 
>> Nodes:
>> Red Hat Enterprise Linux Server release 7.2 (Maipo)
>> vdsm-python-4.16.30-0.el7.centos.noarch
>> vdsm-cli-4.16.30-0.el7.centos.noarch
>> vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch
>> vdsm-xmlrpc-4.16.30-0.el7.centos.noarch
>> vdsm-hook-vmdisk-4.16.30-0.el7.centos.noarch
>> vdsm-jsonrpc-4.16.30-0.el7.centos.noarch
>> vdsm-hook-floppy-4.16.30-0.el7.centos.noarch
>> vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch
>> vdsm-4.16.30-0.el7.centos.x86_64
>> vdsm-hook-vhostmd-4.16.30-0.el7.centos.noarch
>> 
>> Thanks for any hint/help.
>> rgds,
>> Arsène
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users 
>> 
>> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

Re: [ovirt-users] NFS IO timeout configuration

2016-01-12 Thread Nir Soffer

On Tue, Jan 12, 2016 at 9:32 AM, Markus Stockhausen
 wrote:
> Hi there,
>
> we got a nasty situation yesterday in our OVirt 3.5.6 environment.
> We ran a LSM that failed during the cleanup operation. To be precise
> when the process deleted an image on the source NFS storage.
>
> Engine log gives:
>
> 2016-01-11 20:49:45,120 INFO  
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] 
> (org.ovirt.thread.pool-8-thread-14) [77277f0] START, 
> DeleteImageGroupVDSCommand( storagePoolId = 
> 94ed7a19-fade-4bd6-83f2-2cbb2f730b95, ignoreFailoverLimit = false, 
> storageDomainId = 272ec473-6041-42ee-bd1a-732789dd18d4, imageGroupId = 
> aed132ef-703a-44d0-b875-db8c0d2c1a92, postZeros = false, forceDelete = 
> false), log id: b52d59c
> ...
> 2016-01-11 20:50:45,206 ERROR 
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] 
> (org.ovirt.thread.pool-8-thread-14) [77277f0] Failed in DeleteImageGroupVDS 
> method
>
> VDSM (SPM) log gives:
>
> Thread-97::DEBUG::2016-01-11 
> 20:49:45,737::fileSD::384::Storage.StorageDomain::(deleteImage) Removing 
> file: 
> /rhev/data-center/mnt/1.2.3.4:_var_nas2_OVirtIB/272ec473-6041-42ee-bd1a-732789dd18d4/images/_remojzBd1r/0d623afb-291e-4f4c-acba-caecb125c4ed
> ...
> Thread-97::ERROR::2016-01-11 
> 20:50:45,737::task::866::Storage.TaskManager.Task::(_setError) 
> Task=`cd477878-47b4-44b1-85a3-b5da19543a5e`::Unexpected error
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 873, in _run
> return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
> res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 1549, in deleteImage
> pool.deleteImage(dom, imgUUID, volsByImg)
>   File "/usr/share/vdsm/storage/securable.py", line 77, in wrapper
> return method(self, *args, **kwargs)
>   File "/usr/share/vdsm/storage/sp.py", line 1884, in deleteImage
> domain.deleteImage(domain.sdUUID, imgUUID, volsByImg)
>   File "/usr/share/vdsm/storage/fileSD.py", line 385, in deleteImage
> self.oop.os.remove(volPath)
>   File "/usr/share/vdsm/storage/outOfProcess.py", line 245, in remove
> self._iop.unlink(path)
>   File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 455, in 
> unlink
> return self._sendCommand("unlink", {"path": path}, self.timeout)
>   File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 385, in 
> _sendCommand
> raise Timeout(os.strerror(errno.ETIMEDOUT))
> Timeout: Connection timed out

You stumbled into  https://bugzilla.redhat.com/1270220

>
> Reading the docs I got the idea that vdsm default 60 second timeout
> for IO operations might be changed within /etc/vdsm/vdsm.conf
>
> [irs]
> process_pool_timeout = 180
>
> Can anyone confirm that this will solve the problem?

Yes, this is the correct option.

But note that deleting an image on nfs means 3 unlink operations per volume.
If you have an image with one snapshot, that means 2 volumes, and 6
unlink calls.

If unlink takes 70 seconds (timing out with current 60 seconds
timeout), deleting
the image with one snaphost will take 420 seconds.

On the engine side, engine wait until deleteImage finish, or until vdsTimeout
expired (by default 180 seconds), so you may need to increase the engine
timeout as well.

While engine wait for deleteImage to finish, no other spm operation can run.

So increasing the timeout is not the correct solution. You should check why your
storage needs more then 60 seconds to perform unlink operation and change
your setup so unlink works in a timely manner.

As a start, it would be useful to see the results of nfsstat on the
host experiencing
the slow deletes.

In master we perform now the delteImage operation in a background task, so
slow unlink should not effect the engine side, and you can increase
process_pool_timeout
as needed.
See 
https://github.com/oVirt/vdsm/commit/3239e74d1a9087352fca454926224f47272da6c5

We don't plan to backport this change to 3.6 since it is risky and
does not fix the root
cause, which is the slow nfs server, but if you want to test it, I can
make a patch for 3.6.

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

Re: [ovirt-users] NFS IO timeout configuration

2016-01-12 Thread Vinzenz Feenstra


> On Jan 12, 2016, at 9:11 AM, Markus Stockhausen  
> wrote:
> 
>> Von: Vinzenz Feenstra [vfeen...@redhat.com]
>> Gesendet: Dienstag, 12. Januar 2016 09:00
>> An: Markus Stockhausen
>> Cc: users@ovirt.org; Mike Hildebrandt
>> Betreff: Re: [ovirt-users] NFS IO timeout configuration
>>> Hi there,
>>> 
>>> we got a nasty situation yesterday in our OVirt 3.5.6 environment. 
>>> We ran a LSM that failed during the cleanup operation. To be precise 
>>> when the process deleted an image on the source NFS storage. 
>>> 
> ...
>>> 
>>> Reading the docs I got the idea that vdsm default 60 second timeout
>>> for IO operations might be changed within /etc/vdsm/vdsm.conf
>>> 
>>> [irs]
>>> process_pool_timeout = 180
>>> 
>>> Can anyone confirm that this will solve the problem?
>> 
>> Well it will increase the time to 3 minutes and takes effect after 
>> restarting vdsm and supervdsm - If that is enough that might depend on your 
>> setup.
>> 
> 
> Thanks Vinzenz,
> 
> maybe my question was not 100% correct. I need to know, if this parameter 
> really influences the described timeout behaviour. The best value of the 
> parameter must be checked of course.

Well I might be wrong, but from what I can see that is the right value to 
configure this.

> 
> Markus

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

Re: [ovirt-users] NFS IO timeout configuration

2016-01-12 Thread Markus Stockhausen

> Von: Vinzenz Feenstra [vfeen...@redhat.com]
> Gesendet: Dienstag, 12. Januar 2016 09:00
> An: Markus Stockhausen
> Cc: users@ovirt.org; Mike Hildebrandt
> Betreff: Re: [ovirt-users] NFS IO timeout configuration
> > Hi there,
> > 
> > we got a nasty situation yesterday in our OVirt 3.5.6 environment. 
> > We ran a LSM that failed during the cleanup operation. To be precise 
> > when the process deleted an image on the source NFS storage. 
> > 
...
> >
> > Reading the docs I got the idea that vdsm default 60 second timeout
> > for IO operations might be changed within /etc/vdsm/vdsm.conf
> >
> > [irs]
> > process_pool_timeout = 180
> >
> > Can anyone confirm that this will solve the problem?
> 
> Well it will increase the time to 3 minutes and takes effect after restarting 
> vdsm and supervdsm - If that is enough that might depend on your setup.
> 

Thanks Vinzenz,

maybe my question was not 100% correct. I need to know, if this parameter 
really influences the described timeout behaviour. The best value of the 
parameter must be checked of course.

Markus
Diese E-Mail enthÃ¤lt vertrauliche und/oder rechtlich geschÃ¼tzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtÃ¼mlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

Ãber das Internet versandte E-Mails kÃ¶nnen unter fremden Namen erstellt oder
manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine
rechtsverbindliche WillenserklÃ¤rung.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 KÃ¶ln

Vorstand:
Kadir Akin
Dr. Michael HÃ¶hnerbach

Vorsitzender des Aufsichtsrates:
Hans Kristian Langva

Registergericht: Amtsgericht KÃ¶ln
Registernummer: HRB 52 497

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

e-mails sent over the internet may have been written under a wrong name or
been manipulated. That is why this message sent as an e-mail is not a
legally binding declaration of intention.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 KÃ¶ln

executive board:
Kadir Akin
Dr. Michael HÃ¶hnerbach

President of the supervisory board:
Hans Kristian Langva

Registry office: district court Cologne
Register number: HRB 52 497


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

Re: [ovirt-users] NFS IO timeout configuration

2016-01-12 Thread Vinzenz Feenstra


> On Jan 12, 2016, at 8:32 AM, Markus Stockhausen  
> wrote:
> 
> Hi there,
> 
> we got a nasty situation yesterday in our OVirt 3.5.6 environment. 
> We ran a LSM that failed during the cleanup operation. To be precise 
> when the process deleted an image on the source NFS storage. 
> 
> Engine log gives:
> 
> 2016-01-11 20:49:45,120 INFO  
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] 
> (org.ovirt.thread.pool-8-thread-14) [77277f0] START, 
> DeleteImageGroupVDSCommand( storagePoolId = 
> 94ed7a19-fade-4bd6-83f2-2cbb2f730b95, ignoreFailoverLimit = false, 
> storageDomainId = 272ec473-6041-42ee-bd1a-732789dd18d4, imageGroupId = 
> aed132ef-703a-44d0-b875-db8c0d2c1a92, postZeros = false, forceDelete = 
> false), log id: b52d59c
> ...
> 2016-01-11 20:50:45,206 ERROR 
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] 
> (org.ovirt.thread.pool-8-thread-14) [77277f0] Failed in DeleteImageGroupVDS 
> method
> 
> VDSM (SPM) log gives:
> 
> Thread-97::DEBUG::2016-01-11 
> 20:49:45,737::fileSD::384::Storage.StorageDomain::(deleteImage) Removing 
> file: 
> /rhev/data-center/mnt/1.2.3.4:_var_nas2_OVirtIB/272ec473-6041-42ee-bd1a-732789dd18d4/images/_remojzBd1r/0d623afb-291e-4f4c-acba-caecb125c4ed
> ...
> Thread-97::ERROR::2016-01-11 
> 20:50:45,737::task::866::Storage.TaskManager.Task::(_setError) 
> Task=`cd477878-47b4-44b1-85a3-b5da19543a5e`::Unexpected error
> Traceback (most recent call last):
>  File "/usr/share/vdsm/storage/task.py", line 873, in _run
>return fn(*args, **kargs)
>  File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
>res = f(*args, **kwargs)
>  File "/usr/share/vdsm/storage/hsm.py", line 1549, in deleteImage
>pool.deleteImage(dom, imgUUID, volsByImg)
>  File "/usr/share/vdsm/storage/securable.py", line 77, in wrapper
>return method(self, *args, **kwargs)
>  File "/usr/share/vdsm/storage/sp.py", line 1884, in deleteImage
>domain.deleteImage(domain.sdUUID, imgUUID, volsByImg)
>  File "/usr/share/vdsm/storage/fileSD.py", line 385, in deleteImage
>self.oop.os.remove(volPath)
>  File "/usr/share/vdsm/storage/outOfProcess.py", line 245, in remove
>self._iop.unlink(path)
>  File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 455, in 
> unlink
>return self._sendCommand("unlink", {"path": path}, self.timeout)
>  File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 385, in 
> _sendCommand
>raise Timeout(os.strerror(errno.ETIMEDOUT))
> Timeout: Connection timed out
> 
> Reading the docs I got the idea that vdsm default 60 second timeout
> for IO operations might be changed within /etc/vdsm/vdsm.conf
> 
> [irs]
> process_pool_timeout = 180
> 
> Can anyone confirm that this will solve the problem?

Well it will increase the time to 3 minutes and takes effect after restarting 
vdsm and supervdsm - If that is enough that might depend on your setup.

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

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

Re: [ovirt-users] Blog on Hyperconverged Infrastructure using oVirt and Gluster

Re: [ovirt-users] how to get infos about dev of ovirt 4.0

Re: [ovirt-users] NFS IO timeout configuration

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

[ovirt-users] API Importing a VM from an export domain fails

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

Re: [ovirt-users] Ovirt supported thinclient appliance

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

Re: [ovirt-users] Users Digest, Vol 52, Issue 72 vdsm hook issues

Re: [ovirt-users] vdsm hook issues

[ovirt-users] Ovirt supported thinclient appliance

Re: [ovirt-users] User with SuperAdmin Role has not MANIPULATE_STORAGE_DOMAIN

Re: [ovirt-users] vdsm hook issues

Re: [ovirt-users] vdsm hook issues

Re: [ovirt-users] vdsm hook issues

Re: [ovirt-users] vdsm hook issues

Re: [ovirt-users] vdsm hook issues

Re: [ovirt-users] vdsm hook issues

[ovirt-users] vdsm hook issues

Re: [ovirt-users] User with SuperAdmin Role has not MANIPULATE_STORAGE_DOMAIN

Re: [ovirt-users] Still not possible to resize hosted engine disk?

[ovirt-users] Still not possible to resize hosted engine disk?

Re: [ovirt-users] User with SuperAdmin Role has not MANIPULATE_STORAGE_DOMAIN

Re: [ovirt-users] [Gluster-users] Blog on Hyperconverged Infrastructure using oVirt and Gluster

Re: [ovirt-users] NFS IO timeout configuration

Re: [ovirt-users] Unable to start nor to migrate vm

[ovirt-users] Blog on Hyperconverged Infrastructure using oVirt and Gluster

Re: [ovirt-users] Unable to start nor to migrate vm

Re: [ovirt-users] NFS IO timeout configuration

Re: [ovirt-users] NFS IO timeout configuration

Re: [ovirt-users] NFS IO timeout configuration

Re: [ovirt-users] NFS IO timeout configuration

33 matches

Site Navigation

Mail list logo

Footer information