date:20130523

On 05/23/2013 03:53 PM, Karli Sjöberg wrote:
> tor 2013-05-23 klockan 15:10 +0300 skrev Michael Pasternak:
>> Hi Karli,
>>
>> On 05/23/2013 12:35 PM, Karli Sjöberg wrote:
>> > Hi!
>> > 
>> > We´re in the process of building an orderportal where our customers will 
>> > be able to log in, select a virtual machine template, type in a desired 
>> > hostname and it will be
>> > automatically created, and they recieve a mail explaining what they´ve 
>> > gotten themselves into:). For this I figured the PythonSDK would be the 
>> > best choice but I´m having
>> > trouble using it. What we´ve done so far is:
>> > 
>> > 1) Create a new VM from a template; OK. I found an example and it worked 
>> > OOTB
>> > 2) Rename the new VM´s disk from ${TemplateName}_Disk1 to ${VMName}_Disk1; 
>> > Not OK. I found an example of how to change the name of a VMNic and that 
>> > works, but using the
>> > same method to change VMDisk´s name does not (FYI, the VM only has one 
>> > VNic and VDisk):
>>  from ovirtsdk.xml import params
>>  from ovirtsdk.api import API
>>  api = API(url='https://${ENGINE}:443/api', 
>>   ca_file='${CACERT}', 
>>  username='admin@internal ', password='letmein!')
>>  vm = api.vms.get(name='VMName')
>> > 
>>  vmnic = vm.nics.get(name='*')
>>  vmnic.name
>> > 'nic1'
>>  api.vms.get(name='VMName').nics.get(name='*')
>> > 'nic1'
>>  vmnic.name='nic2'
>>  vmnic.update()
>>  api.vms.get(name='VMName').nics.get(name='*')
>> > 'nic2'
>>  vmnic.name
>> > 'nic2'
>> > 
>>  vmdisk = vm.disks.get(name='*')
>>  vmdisk.name
>> > 'TemplateName_Disk1'
>>  api.vms.get(name='VMName').disks.get(name='*')
>>
>> this kind of call is not efficient, by fetching the disk
>> you also fetch the vm,
>>
>> i'd suggest fetch vm, store it in local variable and then
>> reuse it for any sub-collection manipulations.
> 
> Could you please show me example of that, my Pythonjourney started only 
> yesterday:)?

api = API(...)

myvm = api.vms.get(name='VMName')

myvm.disks.get(name='...')
myvm.nics.get(name='...')

myvm.disks.add()
myvm.disks.list()


> 
>>
>>
>> > 'TemplateName_Disk1'
>>  vmdisk.name='VMName_Disk1'
>>  vmdisk.update()
>>  vmdisk.name
>> > 'VMName_Disk1'
>>  api.vms.get(name='VMName').disks.get(name='*')
>> > 'TemplateName_Disk1'
>> > 
>> > See? Am I holding it wrong?
>>
>> disk.name is deprecated, please use 'alias' instead.
> 
 print api.vms.get(name='VMName').disks.get(name='*').name
> TemplateName_Disk1
 print api.vms.get(name='VMName').disks.get(name='*').alias
> None
> 
> So that doesn´t seem to work either?
> 
> /Karli
> 
>>
>> > 
>> > 3) Create a snapshot called "Origin", so if a customer calls in and says 
>> > they´ve borked it completely, we´ll just revert to it´s "Origin" and 
>> > they´re up and running again;
>> > OK, found another OOTB example, thank you.
>> > 4) Add the customer to VM´s Permissions with an appropriate role; Not OK. 
>> > I have found no examples on how to do this and just don´t know where to 
>> > start looking. BTW,
>> > creating a new VM with Python results in Permissions completely empty, no 
>> > inheritance either. Don´t know if that is intended...
>>
>> elena, ilia,
>>
>> guys, do you have any permission related code to share?
>>
>> > 
>> > client# rpm -qa | grep ovirt
>> > ovirt-engine-cli-3.2.0.11-1.fc17.noarch
>> > ovirt-engine-sdk-3.2.0.10-1.fc17.noarch
>> > 
>> > engine# rpm -qa | grep ovirt
>> > ovirt-engine-config-3.1.0-4.fc17.noarch
>> > ovirt-engine-dbscripts-3.1.0-4.fc17.noarch
>> > ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
>> > ovirt-engine-restapi-3.1.0-4.fc17.noarch
>> > ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
>> > ovirt-engine-genericapi-3.1.0-4.fc17.noarch
>> > ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
>> > ovirt-engine-webadmin-portal-3.1.0-4.fc17.noarch
>> > ovirt-engine-setup-3.1.0-4.fc17.noarch
>> > ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
>> > ovirt-engine-backend-3.1.0-4.fc17.noarch
>> > ovirt-engine-tools-common-3.1.0-4.fc17.noarch
>> > ovirt-engine-3.1.0-4.fc17.noarch
>> > ovirt-engine-userportal-3.1.0-4.fc17.noarch
>> > ovirt-engine-notification-service-3.1.0-4.fc17.noarch
>> > 
>> > -- 
>> > 
>> > Best Regards
>> > ---
>> > Karli Sjöberg
>> > Swedish University of Agricultural Sciences
>> > Box 7079 (Visiting Address Kronåsvägen 8)
>> > S-750 07 Uppsala, Sweden
>> > Phone:  +46-(0)18-67 15 66
>> > karli.sjob...@slu.se  
>> > 
>> > 
>> > 
>> > 
>> > ___
>> > Users mailing list
>> > Users@ovirt.org 
>> > http://lists.ovirt.org/mailman/listinfo/users
>> > 
>>
>>
> 
> -- 
> 
> Med Vänliga Hälsningar
> ---
> Karli Sjöberg
> Swedish University

[Users] Can host hooks be used to implement the following policy to avoid "boot storm"?

2013-05-23 Thread lofyer

Can host hooks be used to implement the following policy to avoid "boot 
storm"?


1.count and sort VMs awaiting for boot.
2.If the count is less than or equal to, for example 5, then boot all 
VMs and exit the script.

3.Otherwise, boot and dequeue vm0 to vm4, and minus the count by 5.
4.Sleep some time, and go to step 2.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released

2013-05-23 Thread Sasha Chuzhoy


On 05/23/2013 11:07 AM, René Koch (ovido) wrote:

On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:

On 05/22/2013 05:18 PM, Itamar Heim wrote:

On 05/22/2013 03:55 PM, René Koch (ovido) wrote:

On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:

 Original Message 
Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
Date: Thu, 16 May 2013 16:31:24 +0200
From: René Koch
To: users

I'm happy to announce version 1.2 of check_rhev3.

check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
which is
used to monitor datacenters, clusters, hosts, vms, vm pools and
storage
domains
of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
environments.

The download locations are
 *
https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
 *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm


 *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm



For further information on how to install this plugin visit:

https://github.com/ovido/check_rhev3/wiki/Installation-Documentation

A detailed usage documentation can be found here:
https://github.com/ovido/check_rhev3/wiki/Usage-Documentation


Changelog:

- General:
-   Moved project to github: https://github.com/ovido/check_rhev3

- New features:
-   Verify RHEV-M certificate
-   Allow authentication sessions for authentication in RHEV>= 3.1
and
oVirt>= 3.1
-   Use option -n  to check a specific nic

- Bugs fixed:
-   Performance data issue with check_multi


If you have any questions or ideas, please drop me an email: 
r.k...@ovido.at.

Thank you for using check_rhev3.




Hi Rene,

we deployed the plugin and noticed its flooding the event log with
login
events for the user its using via the REST API.
can you please add persistent session to the REST API calls so login
will happen only once and won't flood the log?

http://www.ovirt.org/Features/RESTSessionManagement


It's one of the features in the latest version (1.2):

   -o, --cookie
  Use cookie based authenticated sessions (requires RHEV>= 3.1)


I implemented it in the following way:
- Plugin checks if file with session cookie exists (per default
in /var/tmp)
- If not: login with username and password (that's why you need to
specify auth pair or authfile) and fetch JSESSIONID
-- Writes ID into session cookie file
- If cookie file is found: login using JSESSIONID and ignore username
and password. So you can change username/password and login will still
work.
- If login using session ID fails and cookie file exists, it will be
deleted and a login with username and password is tried the next time
the plugin is executed

If you start the script with -vvv you can see if login is down with auth
session or with username/password...

I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.

well, we are trying it with next version of RHEV actually :)
sasha - can you please start the script with -vvv to provide the log
for login behavior?


Here is all (I hope) the relevant data:
[V] Starting the main script.
[V] Checking which component to monitor.
[D] check_host: Called function check_host.
[V] Host: Checking host .
[V] Host: No subcheck is specified, checking memory usage.
[D] check_statistics: Called function check_statistics.
[V] Statistics: Checking statistics of hosts.
[D] check_statistics: Input parameter $component: hosts
[D] check_statistics: Input parameter $search:
[D] check_statistics: Input parameter $statistics: memory
[D] check_statistics: Converting variables.
[D] check_statistics: Converted variable $url: hosts
[D] get_result: Called function get_result.
[D] get_result: Input parameter $_[0]: /hosts?search=
[D] get_result: Input parameter $xml: hosts
[D] get_result: Input parameter $search: id
[D] rhev_connect: Called function rhev_connect.
[V] REST-API: Connecting to REST-API.
[D] rhev_connect: Input parameter: /hosts?search=.
[V] REST-API: RHEVM-API URL: https://:8443/api/hosts?search=
[V] REST-API: RHEVM-API User:
[V] REST-API: RHEVM-API Password:
[V] REST-API: cookie filename:
bm90dDA0LmVuZy5sYWIudGx2LnJlZGhhdC5jb20tdmlld2VyQG5vdHQwNC5lbmcubGFiLnRsdi5y
ZWRoYXQuY29tCg==
[D] rhev_connect: Using username and password authentication.
[V] REST-API: Cache-Control: no-cache
Connection: close
Date: Thu, 23 May 2013 07:50:33 GMT
Pragma: No-cache
Server: Apache-Coyote/1.1
Content-Type: application/xml
Expires: Thu, 01 Jan 1970 02:00:00 IST
Client-Date: Thu, 23 May 2013 07:50:33 GMT
Client-Peer: 10.35.16.97:8443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=Red Hat TLV/CN=CA-.31149
Client-SSL-Cert-Subject: /C=US/O=Red Hat TLV/CN=
Client-SSL-Cipher: DHE-RSA-AES256-SHA
Client-SSL-Warning: Peer certificate not verified
Set-Cookie: JSESSIONID=8gUbxG1-uk8HOi2tq4krw7tq; Path=/api; Secure
[D] rhev_connect:

# The output is truncated 


It seems to me that you did start the plugin without "-o" option...

Without -o plugin uses use

Re: [Users] Problems using the PythonSDK

2013-05-23 Thread Karli Sjöberg

tor 2013-05-23 klockan 15:10 +0300 skrev Michael Pasternak:


Hi Karli,

On 05/23/2013 12:35 PM, Karli Sjöberg wrote:
> Hi!
>
> We´re in the process of building an orderportal where our customers will be 
> able to log in, select a virtual machine template, type in a desired hostname 
> and it will be
> automatically created, and they recieve a mail explaining what they´ve gotten 
> themselves into:). For this I figured the PythonSDK would be the best choice 
> but I´m having
> trouble using it. What we´ve done so far is:
>
> 1) Create a new VM from a template; OK. I found an example and it worked OOTB
> 2) Rename the new VM´s disk from ${TemplateName}_Disk1 to ${VMName}_Disk1; 
> Not OK. I found an example of how to change the name of a VMNic and that 
> works, but using the
> same method to change VMDisk´s name does not (FYI, the VM only has one VNic 
> and VDisk):
 from ovirtsdk.xml import params
 from ovirtsdk.api import API
 api = API(url='https://${ENGINE}:443/api', 
  ca_file='${CACERT}', 
 username='admin@internal ', password='letmein!')
 vm = api.vms.get(name='VMName')
>
 vmnic = vm.nics.get(name='*')
 vmnic.name
> 'nic1'
 api.vms.get(name='VMName').nics.get(name='*')
> 'nic1'
 vmnic.name='nic2'
 vmnic.update()
 api.vms.get(name='VMName').nics.get(name='*')
> 'nic2'
 vmnic.name
> 'nic2'
>
 vmdisk = vm.disks.get(name='*')
 vmdisk.name
> 'TemplateName_Disk1'
 api.vms.get(name='VMName').disks.get(name='*')

this kind of call is not efficient, by fetching the disk
you also fetch the vm,

i'd suggest fetch vm, store it in local variable and then
reuse it for any sub-collection manipulations.


Could you please show me example of that, my Pythonjourney started only 
yesterday:)?





> 'TemplateName_Disk1'
 vmdisk.name='VMName_Disk1'
 vmdisk.update()
 vmdisk.name
> 'VMName_Disk1'
 api.vms.get(name='VMName').disks.get(name='*')
> 'TemplateName_Disk1'
>
> See? Am I holding it wrong?

disk.name is deprecated, please use 'alias' instead.


>>> print api.vms.get(name='VMName').disks.get(name='*').name
TemplateName_Disk1
>>> print api.vms.get(name='VMName').disks.get(name='*').alias
None

So that doesn´t seem to work either?

/Karli




>
> 3) Create a snapshot called "Origin", so if a customer calls in and says 
> they´ve borked it completely, we´ll just revert to it´s "Origin" and they´re 
> up and running again;
> OK, found another OOTB example, thank you.
> 4) Add the customer to VM´s Permissions with an appropriate role; Not OK. I 
> have found no examples on how to do this and just don´t know where to start 
> looking. BTW,
> creating a new VM with Python results in Permissions completely empty, no 
> inheritance either. Don´t know if that is intended...

elena, ilia,

guys, do you have any permission related code to share?

>
> client# rpm -qa | grep ovirt
> ovirt-engine-cli-3.2.0.11-1.fc17.noarch
> ovirt-engine-sdk-3.2.0.10-1.fc17.noarch
>
> engine# rpm -qa | grep ovirt
> ovirt-engine-config-3.1.0-4.fc17.noarch
> ovirt-engine-dbscripts-3.1.0-4.fc17.noarch
> ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
> ovirt-engine-restapi-3.1.0-4.fc17.noarch
> ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
> ovirt-engine-genericapi-3.1.0-4.fc17.noarch
> ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
> ovirt-engine-webadmin-portal-3.1.0-4.fc17.noarch
> ovirt-engine-setup-3.1.0-4.fc17.noarch
> ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
> ovirt-engine-backend-3.1.0-4.fc17.noarch
> ovirt-engine-tools-common-3.1.0-4.fc17.noarch
> ovirt-engine-3.1.0-4.fc17.noarch
> ovirt-engine-userportal-3.1.0-4.fc17.noarch
> ovirt-engine-notification-service-3.1.0-4.fc17.noarch
>
> --
>
> Best Regards
> ---
> Karli Sjöberg
> Swedish University of Agricultural Sciences
> Box 7079 (Visiting Address Kronåsvägen 8)
> S-750 07 Uppsala, Sweden
> Phone:  +46-(0)18-67 15 66
> karli.sjob...@slu.se 
> 
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>




--

Med Vänliga Hälsningar
---
Karli Sjöberg
Swedish University of Agricultural Sciences
Box 7079 (Visiting Address Kronåsvägen 8)
S-750 07 Uppsala, Sweden
Phone:  +46-(0)18-67 15 66
karli.sjob...@slu.se
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Guest Agent

On 05/23/2013 12:17 PM, René Koch (ovido) wrote:

On Tue, 2013-05-21 at 08:28 +0200, Vinzenz Feenstra wrote:

On 05/20/2013 03:12 PM, supo...@logicworks.pt wrote:

Ok, thanks. from where can I start?

On Fedora 17+ you can install the guest agent by 'yum install
ovirt-guest-agent-common'

On other OS you can start by checking out the git repository on the OS
you'd like to build it on.

`git clone http://gerrit.ovirt.org/p/ovirt-guest-agent.git`

On Windows you should follow these instructions:
http://gerrit.ovirt.org/gitweb?p=ovirt-guest-agent.git;a=blob;f=ovirt-guest-agent/README-windows.txt;h=HEAD

On Linux you go into the repository
$ ./autogen.sh
$ ./configure --prefix=/usr --without-sso
And then as root
# make install

However not all files might yet be put into the right places on all
systems, and for Debian/Ubuntu systems we don't have any daemon or
upstart scripts, so far we only support systemd in the repository so
that would have to be done manually.

Are there plans to provide packages for Windows or various Linux
distributions in oVirt repositories as long as they aren't available in
official distro repos?

well, they are supposed to be packaged and be part of the various
distros, but someone needs to try and push them for those distros.
in the meantime, i think for OSs which we can, we should have a built
guest agent.

Another little bit off-topic question: what are the criteria for an
operating system to be listed as an operating system when creating new
servers/desktops? At the moment the same os'es are listed as in RHEV.
In my opinion either all distributions which are fully tested (working
IDE/VirtIO disks, e1000/rtl/VirtIO nics, maybe guest agent available...)
should be listed here - in a similar way as you can find it in
virt-manager...

today there are code deps for various options/configs per OS.
roy golan is working on making these file based configs, which will
allow to add more OSs without code changes.

For me it's clear that I can run e.g. Debian vms on oVirt and I have to
choose Other Linux for debian. But having e.g. Debian, Ubuntu, openSUSE
in the list of operating systems and their icons in user and self
provisioning portal would look much nicer.

agree, unless someone will send comprehensive patches for that, i expect
roy's work to allow easy patches for other OSs.

Last, it would be great to have a matrix of operating systems in oVirt
wiki to provide an overview which operating systems are working and
where you can find guest agent packages - as available for e.g. VMware
and KVM. I think there are a lot of users tried out different operating
systems and are willing to update the support matrix...
I think this would help a lot to find the right settings for operating
systems. e.g. for Fedora 18 I can/should choose VirtIO disks and nics,
but for Solaris 10/11 only IDE disks are working and network isn't
working (none of the 3 types).

What do you think?

feel free to open the wiki and start populating it :)

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

Re: [Users] Migration from Ovirt 3.2 to rhev 3.1

2013-05-23 Thread Omer Frenkel



- Original Message -
> From: "Jakub Bittner" 
> To: users@ovirt.org
> Sent: Thursday, May 23, 2013 12:15:34 PM
> Subject: [Users] Migration from Ovirt 3.2 to rhev 3.1
> 
> Hello,
> 
> I have a question if it is possible to migrate VMs from Ovirt 3.2 to
> RHEV 3.1?

yes, you need to export them, then import.

> 
> Thank you :-)
> ___
> 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: [Users] Problems using the PythonSDK


Hi Karli,

On 05/23/2013 12:35 PM, Karli Sjöberg wrote:
> Hi!
> 
> We´re in the process of building an orderportal where our customers will be 
> able to log in, select a virtual machine template, type in a desired hostname 
> and it will be
> automatically created, and they recieve a mail explaining what they´ve gotten 
> themselves into:). For this I figured the PythonSDK would be the best choice 
> but I´m having
> trouble using it. What we´ve done so far is:
> 
> 1) Create a new VM from a template; OK. I found an example and it worked OOTB
> 2) Rename the new VM´s disk from ${TemplateName}_Disk1 to ${VMName}_Disk1; 
> Not OK. I found an example of how to change the name of a VMNic and that 
> works, but using the
> same method to change VMDisk´s name does not (FYI, the VM only has one VNic 
> and VDisk):
 from ovirtsdk.xml import params
 from ovirtsdk.api import API
 api = API(url='https://${ENGINE}:443/api', 
  ca_file='${CACERT}', 
 username='admin@internal ', password='letmein!')
 vm = api.vms.get(name='VMName')
> 
 vmnic = vm.nics.get(name='*')
 vmnic.name
> 'nic1'
 api.vms.get(name='VMName').nics.get(name='*')
> 'nic1'
 vmnic.name='nic2'
 vmnic.update()
 api.vms.get(name='VMName').nics.get(name='*')
> 'nic2'
 vmnic.name
> 'nic2'
> 
 vmdisk = vm.disks.get(name='*')
 vmdisk.name
> 'TemplateName_Disk1'
 api.vms.get(name='VMName').disks.get(name='*')

this kind of call is not efficient, by fetching the disk
you also fetch the vm,

i'd suggest fetch vm, store it in local variable and then
reuse it for any sub-collection manipulations.


> 'TemplateName_Disk1'
 vmdisk.name='VMName_Disk1'
 vmdisk.update()
 vmdisk.name
> 'VMName_Disk1'
 api.vms.get(name='VMName').disks.get(name='*')
> 'TemplateName_Disk1'
> 
> See? Am I holding it wrong?

disk.name is deprecated, please use 'alias' instead.

> 
> 3) Create a snapshot called "Origin", so if a customer calls in and says 
> they´ve borked it completely, we´ll just revert to it´s "Origin" and they´re 
> up and running again;
> OK, found another OOTB example, thank you.
> 4) Add the customer to VM´s Permissions with an appropriate role; Not OK. I 
> have found no examples on how to do this and just don´t know where to start 
> looking. BTW,
> creating a new VM with Python results in Permissions completely empty, no 
> inheritance either. Don´t know if that is intended...

elena, ilia,

guys, do you have any permission related code to share?

> 
> client# rpm -qa | grep ovirt
> ovirt-engine-cli-3.2.0.11-1.fc17.noarch
> ovirt-engine-sdk-3.2.0.10-1.fc17.noarch
> 
> engine# rpm -qa | grep ovirt
> ovirt-engine-config-3.1.0-4.fc17.noarch
> ovirt-engine-dbscripts-3.1.0-4.fc17.noarch
> ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
> ovirt-engine-restapi-3.1.0-4.fc17.noarch
> ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
> ovirt-engine-genericapi-3.1.0-4.fc17.noarch
> ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
> ovirt-engine-webadmin-portal-3.1.0-4.fc17.noarch
> ovirt-engine-setup-3.1.0-4.fc17.noarch
> ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
> ovirt-engine-backend-3.1.0-4.fc17.noarch
> ovirt-engine-tools-common-3.1.0-4.fc17.noarch
> ovirt-engine-3.1.0-4.fc17.noarch
> ovirt-engine-userportal-3.1.0-4.fc17.noarch
> ovirt-engine-notification-service-3.1.0-4.fc17.noarch
> 
> -- 
> 
> Best Regards
> ---
> Karli Sjöberg
> Swedish University of Agricultural Sciences
> Box 7079 (Visiting Address Kronåsvägen 8)
> S-750 07 Uppsala, Sweden
> Phone:  +46-(0)18-67 15 66
> karli.sjob...@slu.se 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


-- 

Michael Pasternak
RedHat, ENG-Virtualization R&D
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Active Directory Groups

2013-05-23 Thread Thomas Scofield

I tried various search strings,  but I could only find groups if I searched
for the full group name.
On May 23, 2013 3:44 AM, "René Koch (ovido)"  wrote:

> Hi,
>
> I also had a problem with '#' in an customer project with RHEV 3.0, but
> we also had issues with a broken active directory replication. White
> spaces aren't a problem in groups.
>
> I can't tell if groups with '#' are working, as I told them to not use
> special characters in group names and to fix their replication. Now
> everything is working fine, but don't know if they created new groups
> for RHEV or if it was just the replication.
>
>
> Regards,
> René
>
>
>
> On Thu, 2013-05-23 at 00:36 -0400, Yair Zaslavsky wrote:
> > I don't remember encountering such an issue, but probably never
> > checked.
> >
> > a. What is the search string you're passing in order to get the
> > users/groups?
> > b. From quick look at the code - looks like this is at the step
> > of initializing the data that will be queried  - that is, before
> > sending the AD query.
> >
> >
> >
> >
> > Eli - looks like this is from the SeachQuery.InitQueryData - can you
> > elaborate here?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > __
> > From: "Thomas Scofield" 
> > To: "users" 
> > Sent: Thursday, May 23, 2013 4:06:29 AM
> > Subject: [Users] Active Directory Groups
> >
> >
> > I was attempting to assign some permissions to Active
> > Directory groups and ran into an issue where groups with
> > spaces or the # sign in them.  The engine log contained
> > messages like these
> >
> >
> > 2013-05-22 08:39:35,228 WARN
> >  [org.ovirt.engine.core.bll.SearchQuery]
> > (ajp--127.0.0.1-8702-134)
> > ResourceManager::searchBusinessObjects - erroneous search text
> > - ADGROUP: name=#Virtual Engineering
> > 2013-05-22 08:39:35,228 WARN
> >  [org.ovirt.engine.core.bll.SearchQuery]
> > (ajp--127.0.0.1-8702-46)
> > ResourceManager::searchBusinessObjects - erroneous search text
> > - ADUSER: allnames=#Virtual Engineering
> >
> >
> > The group name is valid.  The example above contains both the
> > space and #, but trying groups with just a space and others
> > with just a # also fail.  I was able to successfully add
> > groups that contained characters and -.  Has anyone else had
> > an issue like this?
> >
> >
> >
> > ___
> > 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: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released

On 05/23/2013 01:04 PM, Michael Pasternak wrote:
> On 05/23/2013 12:37 PM, Itamar Heim wrote:
>> On 05/23/2013 12:36 PM, Michael Pasternak wrote:
>>> On 05/23/2013 11:22 AM, Itamar Heim wrote:
 On 05/23/2013 11:21 AM, René Koch (ovido) wrote:
>
> On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:
>> On 05/23/2013 11:07 AM, René Koch (ovido) wrote:
>>> On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:
 On 05/22/2013 05:18 PM, Itamar Heim wrote:
> On 05/22/2013 03:55 PM, René Koch (ovido) wrote:
>>
>> On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:
  Original Message 
 Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
 Date: Thu, 16 May 2013 16:31:24 +0200
 From: René Koch 
 To: users 

 I'm happy to announce version 1.2 of check_rhev3.

 check_rhev3 is a monitoring plugin for Icinga/Nagios and it's 
 forks,
 which is
 used to monitor datacenters, clusters, hosts, vms, vm pools and
 storage
 domains
 of Red Hat Enterprise Virtualization (RHEV) and oVirt 
 virtualization
 environments.

 The download locations are
*
 https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
*
 https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm


*
 https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm



 For further information on how to install this plugin visit:

 https://github.com/ovido/check_rhev3/wiki/Installation-Documentation

 A detailed usage documentation can be found here:
 https://github.com/ovido/check_rhev3/wiki/Usage-Documentation


 Changelog:

 - General:
 -   Moved project to github: https://github.com/ovido/check_rhev3

 - New features:
 -   Verify RHEV-M certificate
 -   Allow authentication sessions for authentication in RHEV >= 3.1
 and
 oVirt >= 3.1
 -   Use option -n  to check a specific nic

 - Bugs fixed:
 -   Performance data issue with check_multi


 If you have any questions or ideas, please drop me an email: 
 r.k...@ovido.at.

 Thank you for using check_rhev3.



>>>
>>> Hi Rene,
>>>
>>> we deployed the plugin and noticed its flooding the event log with
>>> login
>>> events for the user its using via the REST API.
>>> can you please add persistent session to the REST API calls so login
>>> will happen only once and won't flood the log?
>>>
>>> http://www.ovirt.org/Features/RESTSessionManagement
>>
>>
>> It's one of the features in the latest version (1.2):
>>
>>  -o, --cookie
>> Use cookie based authenticated sessions (requires RHEV >= 
>> 3.1)
>>
>>
>> I implemented it in the following way:
>> - Plugin checks if file with session cookie exists (per default
>> in /var/tmp)
>> - If not: login with username and password (that's why you need to
>> specify auth pair or authfile) and fetch JSESSIONID
>> -- Writes ID into session cookie file
>> - If cookie file is found: login using JSESSIONID and ignore username
>> and password. So you can change username/password and login will 
>> still
>> work.
>> - If login using session ID fails and cookie file exists, it will be
>> deleted and a login with username and password is tried the next time
>> the plugin is executed
>>
>> If you start the script with -vvv you can see if login is down with 
>> auth
>> session or with username/password...
>>
>> I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.
>
> well, we are trying it with next version of RHEV actually :)
> sasha - can you please start the script with -vvv to provide the log
> for login behavior?
>
 Here is all (I hope) the relevant data:
 [V] Starting the main script.
 [V] Checking which component to monitor.
 [D] check_host: Called function check_host.
 [V] Host: Checking host .
 [V] Host: No subcheck is specified, checking memory usage.
 [D] check_statistics: Called

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released

On 05/23/2013 12:37 PM, Itamar Heim wrote:
> On 05/23/2013 12:36 PM, Michael Pasternak wrote:
>> On 05/23/2013 11:22 AM, Itamar Heim wrote:
>>> On 05/23/2013 11:21 AM, René Koch (ovido) wrote:

 On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:
> On 05/23/2013 11:07 AM, René Koch (ovido) wrote:
>> On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:
>>> On 05/22/2013 05:18 PM, Itamar Heim wrote:
 On 05/22/2013 03:55 PM, René Koch (ovido) wrote:
>
> On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:
>>>  Original Message 
>>> Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
>>> Date: Thu, 16 May 2013 16:31:24 +0200
>>> From: René Koch 
>>> To: users 
>>>
>>> I'm happy to announce version 1.2 of check_rhev3.
>>>
>>> check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
>>> which is
>>> used to monitor datacenters, clusters, hosts, vms, vm pools and
>>> storage
>>> domains
>>> of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
>>> environments.
>>>
>>> The download locations are
>>>*
>>> https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
>>>*
>>> https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm
>>>
>>>
>>>*
>>> https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm
>>>
>>>
>>>
>>> For further information on how to install this plugin visit:
>>>
>>> https://github.com/ovido/check_rhev3/wiki/Installation-Documentation
>>>
>>> A detailed usage documentation can be found here:
>>> https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
>>>
>>>
>>> Changelog:
>>>
>>> - General:
>>> -   Moved project to github: https://github.com/ovido/check_rhev3
>>>
>>> - New features:
>>> -   Verify RHEV-M certificate
>>> -   Allow authentication sessions for authentication in RHEV >= 3.1
>>> and
>>> oVirt >= 3.1
>>> -   Use option -n  to check a specific nic
>>>
>>> - Bugs fixed:
>>> -   Performance data issue with check_multi
>>>
>>>
>>> If you have any questions or ideas, please drop me an email: 
>>> r.k...@ovido.at.
>>>
>>> Thank you for using check_rhev3.
>>>
>>>
>>>
>>
>> Hi Rene,
>>
>> we deployed the plugin and noticed its flooding the event log with
>> login
>> events for the user its using via the REST API.
>> can you please add persistent session to the REST API calls so login
>> will happen only once and won't flood the log?
>>
>> http://www.ovirt.org/Features/RESTSessionManagement
>
>
> It's one of the features in the latest version (1.2):
>
>  -o, --cookie
> Use cookie based authenticated sessions (requires RHEV >= 3.1)
>
>
> I implemented it in the following way:
> - Plugin checks if file with session cookie exists (per default
> in /var/tmp)
> - If not: login with username and password (that's why you need to
> specify auth pair or authfile) and fetch JSESSIONID
> -- Writes ID into session cookie file
> - If cookie file is found: login using JSESSIONID and ignore username
> and password. So you can change username/password and login will still
> work.
> - If login using session ID fails and cookie file exists, it will be
> deleted and a login with username and password is tried the next time
> the plugin is executed
>
> If you start the script with -vvv you can see if login is down with 
> auth
> session or with username/password...
>
> I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.

 well, we are trying it with next version of RHEV actually :)
 sasha - can you please start the script with -vvv to provide the log
 for login behavior?

>>> Here is all (I hope) the relevant data:
>>> [V] Starting the main script.
>>> [V] Checking which component to monitor.
>>> [D] check_host: Called function check_host.
>>> [V] Host: Checking host .
>>> [V] Host: No subcheck is specified, checking memory usage.
>>> [D] check_statistics: Called function check_statistics.
>>> [V] Statistics: Checking statistics of hosts.
>>> [D] check_statistics: Input parameter $component: hosts
>>> [D] check_statistics: Input parameter $search:
>>> [D] check_st

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released


On 05/23/2013 12:36 PM, Michael Pasternak wrote:

On 05/23/2013 11:22 AM, Itamar Heim wrote:

On 05/23/2013 11:21 AM, René Koch (ovido) wrote:


On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:

On 05/23/2013 11:07 AM, René Koch (ovido) wrote:

On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:

On 05/22/2013 05:18 PM, Itamar Heim wrote:

On 05/22/2013 03:55 PM, René Koch (ovido) wrote:


On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:

 Original Message 
Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
Date: Thu, 16 May 2013 16:31:24 +0200
From: René Koch 
To: users 

I'm happy to announce version 1.2 of check_rhev3.

check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
which is
used to monitor datacenters, clusters, hosts, vms, vm pools and
storage
domains
of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
environments.

The download locations are
   *
https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
   *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm


   *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm



For further information on how to install this plugin visit:

https://github.com/ovido/check_rhev3/wiki/Installation-Documentation

A detailed usage documentation can be found here:
https://github.com/ovido/check_rhev3/wiki/Usage-Documentation


Changelog:

- General:
-   Moved project to github: https://github.com/ovido/check_rhev3

- New features:
-   Verify RHEV-M certificate
-   Allow authentication sessions for authentication in RHEV >= 3.1
and
oVirt >= 3.1
-   Use option -n  to check a specific nic

- Bugs fixed:
-   Performance data issue with check_multi


If you have any questions or ideas, please drop me an email: 
r.k...@ovido.at.

Thank you for using check_rhev3.





Hi Rene,

we deployed the plugin and noticed its flooding the event log with
login
events for the user its using via the REST API.
can you please add persistent session to the REST API calls so login
will happen only once and won't flood the log?

http://www.ovirt.org/Features/RESTSessionManagement



It's one of the features in the latest version (1.2):

 -o, --cookie
Use cookie based authenticated sessions (requires RHEV >= 3.1)


I implemented it in the following way:
- Plugin checks if file with session cookie exists (per default
in /var/tmp)
- If not: login with username and password (that's why you need to
specify auth pair or authfile) and fetch JSESSIONID
-- Writes ID into session cookie file
- If cookie file is found: login using JSESSIONID and ignore username
and password. So you can change username/password and login will still
work.
- If login using session ID fails and cookie file exists, it will be
deleted and a login with username and password is tried the next time
the plugin is executed

If you start the script with -vvv you can see if login is down with auth
session or with username/password...

I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.


well, we are trying it with next version of RHEV actually :)
sasha - can you please start the script with -vvv to provide the log
for login behavior?


Here is all (I hope) the relevant data:
[V] Starting the main script.
[V] Checking which component to monitor.
[D] check_host: Called function check_host.
[V] Host: Checking host .
[V] Host: No subcheck is specified, checking memory usage.
[D] check_statistics: Called function check_statistics.
[V] Statistics: Checking statistics of hosts.
[D] check_statistics: Input parameter $component: hosts
[D] check_statistics: Input parameter $search:
[D] check_statistics: Input parameter $statistics: memory
[D] check_statistics: Converting variables.
[D] check_statistics: Converted variable $url: hosts
[D] get_result: Called function get_result.
[D] get_result: Input parameter $_[0]: /hosts?search=
[D] get_result: Input parameter $xml: hosts
[D] get_result: Input parameter $search: id
[D] rhev_connect: Called function rhev_connect.
[V] REST-API: Connecting to REST-API.
[D] rhev_connect: Input parameter: /hosts?search=.
[V] REST-API: RHEVM-API URL: https://:8443/api/hosts?search=
[V] REST-API: RHEVM-API User: 
[V] REST-API: RHEVM-API Password: 
[V] REST-API: cookie filename:
bm90dDA0LmVuZy5sYWIudGx2LnJlZGhhdC5jb20tdmlld2VyQG5vdHQwNC5lbmcubGFiLnRsdi5y
ZWRoYXQuY29tCg==
[D] rhev_connect: Using username and password authentication.
[V] REST-API: Cache-Control: no-cache
Connection: close
Date: Thu, 23 May 2013 07:50:33 GMT
Pragma: No-cache
Server: Apache-Coyote/1.1
Content-Type: application/xml
Expires: Thu, 01 Jan 1970 02:00:00 IST
Client-Date: Thu, 23 May 2013 07:50:33 GMT
Client-Peer: 10.35.16.97:8443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=Red Hat TLV/CN=CA-.31149
Client-SSL-Cert-Subject: /C=US/O=Red Hat TLV/CN=
Client-SSL-Cipher: DHE-RSA-AES256-SHA
Client-SSL-Warning: Peer certificate not verified
S

[Users] Problems using the PythonSDK

2013-05-23 Thread Karli Sjöberg

Hi!

We´re in the process of building an orderportal where our customers will be 
able to log in, select a virtual machine template, type in a desired hostname 
and it will be automatically created, and they recieve a mail explaining what 
they´ve gotten themselves into:). For this I figured the PythonSDK would be the 
best choice but I´m having trouble using it. What we´ve done so far is:

1) Create a new VM from a template; OK. I found an example and it worked OOTB
2) Rename the new VM´s disk from ${TemplateName}_Disk1 to ${VMName}_Disk1; Not 
OK. I found an example of how to change the name of a VMNic and that works, but 
using the same method to change VMDisk´s name does not (FYI, the VM only has 
one VNic and VDisk):
>>> from ovirtsdk.xml import params
>>> from ovirtsdk.api import API
>>> api = API(url='https://${ENGINE}:443/api', 
>>> ca_file='${CACERT}', username='admin@internal', 
>>> password='letmein!')
>>> vm = api.vms.get(name='VMName')

>>> vmnic = vm.nics.get(name='*')
>>> vmnic.name
'nic1'
>>> api.vms.get(name='VMName').nics.get(name='*')
'nic1'
>>> vmnic.name='nic2'
>>> vmnic.update()
>>> api.vms.get(name='VMName').nics.get(name='*')
'nic2'
>>> vmnic.name
'nic2'

>>> vmdisk = vm.disks.get(name='*')
>>> vmdisk.name
'TemplateName_Disk1'
>>> api.vms.get(name='VMName').disks.get(name='*')
'TemplateName_Disk1'
>>> vmdisk.name='VMName_Disk1'
>>> vmdisk.update()
>>> vmdisk.name
'VMName_Disk1'
>>> api.vms.get(name='VMName').disks.get(name='*')
'TemplateName_Disk1'

See? Am I holding it wrong?

3) Create a snapshot called "Origin", so if a customer calls in and says 
they´ve borked it completely, we´ll just revert to it´s "Origin" and they´re up 
and running again; OK, found another OOTB example, thank you.
4) Add the customer to VM´s Permissions with an appropriate role; Not OK. I 
have found no examples on how to do this and just don´t know where to start 
looking. BTW, creating a new VM with Python results in Permissions completely 
empty, no inheritance either. Don´t know if that is intended...

client# rpm -qa | grep ovirt
ovirt-engine-cli-3.2.0.11-1.fc17.noarch
ovirt-engine-sdk-3.2.0.10-1.fc17.noarch

engine# rpm -qa | grep ovirt
ovirt-engine-config-3.1.0-4.fc17.noarch
ovirt-engine-dbscripts-3.1.0-4.fc17.noarch
ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
ovirt-engine-restapi-3.1.0-4.fc17.noarch
ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
ovirt-engine-genericapi-3.1.0-4.fc17.noarch
ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
ovirt-engine-webadmin-portal-3.1.0-4.fc17.noarch
ovirt-engine-setup-3.1.0-4.fc17.noarch
ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
ovirt-engine-backend-3.1.0-4.fc17.noarch
ovirt-engine-tools-common-3.1.0-4.fc17.noarch
ovirt-engine-3.1.0-4.fc17.noarch
ovirt-engine-userportal-3.1.0-4.fc17.noarch
ovirt-engine-notification-service-3.1.0-4.fc17.noarch

--

Best Regards
---
Karli Sjöberg
Swedish University of Agricultural Sciences
Box 7079 (Visiting Address Kronåsvägen 8)
S-750 07 Uppsala, Sweden
Phone:  +46-(0)18-67 15 66
karli.sjob...@slu.se
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released

On 05/23/2013 11:22 AM, Itamar Heim wrote:
> On 05/23/2013 11:21 AM, René Koch (ovido) wrote:
>>
>> On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:
>>> On 05/23/2013 11:07 AM, René Koch (ovido) wrote:
 On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:
> On 05/22/2013 05:18 PM, Itamar Heim wrote:
>> On 05/22/2013 03:55 PM, René Koch (ovido) wrote:
>>>
>>> On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:
>  Original Message 
> Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
> Date: Thu, 16 May 2013 16:31:24 +0200
> From: René Koch 
> To: users 
>
> I'm happy to announce version 1.2 of check_rhev3.
>
> check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
> which is
> used to monitor datacenters, clusters, hosts, vms, vm pools and
> storage
> domains
> of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
> environments.
>
> The download locations are
>   *
> https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
>   *
> https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm
>
>
>   *
> https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm
>
>
>
> For further information on how to install this plugin visit:
>
> https://github.com/ovido/check_rhev3/wiki/Installation-Documentation
>
> A detailed usage documentation can be found here:
> https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
>
>
> Changelog:
>
> - General:
> -   Moved project to github: https://github.com/ovido/check_rhev3
>
> - New features:
> -   Verify RHEV-M certificate
> -   Allow authentication sessions for authentication in RHEV >= 3.1
> and
> oVirt >= 3.1
> -   Use option -n  to check a specific nic
>
> - Bugs fixed:
> -   Performance data issue with check_multi
>
>
> If you have any questions or ideas, please drop me an email: 
> r.k...@ovido.at.
>
> Thank you for using check_rhev3.
>
>
>

 Hi Rene,

 we deployed the plugin and noticed its flooding the event log with
 login
 events for the user its using via the REST API.
 can you please add persistent session to the REST API calls so login
 will happen only once and won't flood the log?

 http://www.ovirt.org/Features/RESTSessionManagement
>>>
>>>
>>> It's one of the features in the latest version (1.2):
>>>
>>> -o, --cookie
>>>Use cookie based authenticated sessions (requires RHEV >= 3.1)
>>>
>>>
>>> I implemented it in the following way:
>>> - Plugin checks if file with session cookie exists (per default
>>> in /var/tmp)
>>> - If not: login with username and password (that's why you need to
>>> specify auth pair or authfile) and fetch JSESSIONID
>>> -- Writes ID into session cookie file
>>> - If cookie file is found: login using JSESSIONID and ignore username
>>> and password. So you can change username/password and login will still
>>> work.
>>> - If login using session ID fails and cookie file exists, it will be
>>> deleted and a login with username and password is tried the next time
>>> the plugin is executed
>>>
>>> If you start the script with -vvv you can see if login is down with auth
>>> session or with username/password...
>>>
>>> I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.
>>
>> well, we are trying it with next version of RHEV actually :)
>> sasha - can you please start the script with -vvv to provide the log
>> for login behavior?
>>
> Here is all (I hope) the relevant data:
> [V] Starting the main script.
> [V] Checking which component to monitor.
> [D] check_host: Called function check_host.
> [V] Host: Checking host .
> [V] Host: No subcheck is specified, checking memory usage.
> [D] check_statistics: Called function check_statistics.
> [V] Statistics: Checking statistics of hosts.
> [D] check_statistics: Input parameter $component: hosts
> [D] check_statistics: Input parameter $search:
> [D] check_statistics: Input parameter $statistics: memory
> [D] check_statistics: Converting variables.
> [D] check_statistics: Converted variable $url: hosts
> [D] get_result: Called function get_result.
> [D] get_result: Input parameter $_[0]: /hosts?search=
> [D] get_result: Input parameter $xml: hosts
> [D] get_result: Input paramete

Re: [Users] Guest Agent

On Tue, 2013-05-21 at 08:28 +0200, Vinzenz Feenstra wrote:
> On 05/20/2013 03:12 PM, supo...@logicworks.pt wrote:
> 
> > Ok, thanks. from where can I start?
> > 
> > 
> On Fedora 17+ you can install the guest agent by 'yum install
> ovirt-guest-agent-common'
> 
> On other OS you can start by checking out the git repository on the OS
> you'd like to build it on.
> 
> `git clone http://gerrit.ovirt.org/p/ovirt-guest-agent.git`
> 
> On Windows you should follow these instructions:
> http://gerrit.ovirt.org/gitweb?p=ovirt-guest-agent.git;a=blob;f=ovirt-guest-agent/README-windows.txt;h=HEAD
> 
> On Linux you go into the repository
> $ ./autogen.sh
> $ ./configure --prefix=/usr --without-sso
> And then as root
> # make install 
> 
> However not all files might yet be put into the right places on all
> systems, and for Debian/Ubuntu systems we don't have any daemon or
> upstart scripts, so far we only support systemd in the repository so
> that would have to be done manually.

Are there plans to provide packages for Windows or various Linux
distributions in oVirt repositories as long as they aren't available in
official distro repos?

Another little bit off-topic question: what are the criteria for an
operating system to be listed as an operating system when creating new
servers/desktops? At the moment the same os'es are listed as in RHEV.
In my opinion either all distributions which are fully tested (working
IDE/VirtIO disks, e1000/rtl/VirtIO nics, maybe guest agent available...)
should be listed here - in a similar way as you can find it in
virt-manager...

For me it's clear that I can run e.g. Debian vms on oVirt and I have to
choose Other Linux for debian. But having e.g. Debian, Ubuntu, openSUSE
in the list of operating systems and their icons in user and self
provisioning portal would look much nicer.

Last, it would be great to have a matrix of operating systems in oVirt
wiki to provide an overview which operating systems are working and
where you can find guest agent packages - as available for e.g. VMware
and KVM. I think there are a lot of users tried out different operating
systems and are willing to update the support matrix...
I think this would help a lot to find the right settings for operating
systems. e.g. for Fedora 18 I can/should choose VirtIO disks and nics,
but for Solaris 10/11 only IDE disks are working and network isn't
working (none of the 3 types).

What do you think?

> 
> HTH
> > Jose
> > 
> > 
> > 
> > From: "Vinzenz Feenstra" 
> > To: supo...@logicworks.pt
> > Cc: "Itamar Heim" , Users@ovirt.org
> > Sent: Segunda-feira, 20 de Maio de 2013 10:56:21
> > Subject: Re: [Users] Guest Agent
> > 
> > On 05/19/2013 10:14 AM, supo...@logicworks.pt wrote:
> > 
> > For Linux (Ubuntu, Fedora, RH) and Windows (7,8,2008,2012)
> > 
> > 
> > 
> > Thanks
> > 
> > Jose
> > 
> > 
> > 
> > 
> > 
> > De: "Itamar Heim" 
> > Para: supo...@logicworks.pt
> > Cc: Users@ovirt.org, "Vinzenz Feenstra"
> > 
> > Enviadas: Sábado, 18 Maio, 2013 20:50:29
> > Assunto: Re: [Users] Guest Agent
> > 
> > 
> > On 05/18/2013 09:38 PM, supo...@logicworks.pt wrote:
> > > Hi, where can I found guest agent for installation?
> > 
> > 
> > for which OS?
> > Vinzenz - we should have a wiki on this if we don't already
> > have one.
> > 
> > We do have a description in the repository for Fedora and Windows
> > targets, however we don't have yet a description for other Linux
> > distributions than Fedora since we haven't supported it yet.
> > There has been some work done for supporting other distribution
> > targets however without single sign on support.
> > 
> > I will put the wiki pages on my todo list.
> > 
> > 
> > >
> > > Thanks
> > > Jose
> > >
> > > --
> > >
> > 
> > 
> > > Jose Ferradeira
> > > http://www.logicworks.pt
> > >
> > >
> > >
> > > ___
> > > Users mailing list
> > > Users@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > >
> > 
> > 
> > 
> > 
> > 
> > 
> > -- 
> > Regards,
> > 
> > Vinzenz Feenstra | Senior Software Engineer
> > RedHat Engineering Virtualization R & D
> > Phone: +420 532 294 625
> > IRC: vfeenstr or evilissimo
> > 
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
> > 
> > 
> 
> 
> -- 
> Regards,
> 
> Vinzenz Feenstra | Senior Software Engineer
> RedHat Engineering Virtualiza

[Users] Migration from Ovirt 3.2 to rhev 3.1

2013-05-23 Thread Jakub Bittner


Hello,

I have a question if it is possible to migrate VMs from Ovirt 3.2 to 
RHEV 3.1?


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

Re: [Users] vm pools


On Mon, 2013-05-20 at 16:43 -0400, Eli Mesika wrote:
> 
> - Original Message -
> > From: "Ryan Wilkinson" 
> > To: users@ovirt.org
> > Sent: Monday, May 20, 2013 6:05:32 PM
> > Subject: [Users] vm pools
> > 
> > Is there a method with pools to update (install new apps or updates) a
> > "golden image" and have those updates propagate to a pool? Seems currently
> > you have to create a new template from the image and then create a new pool.
> 
> Hi
> Currently you will have to create a new template from the image and build the 
> pool on top of it ...

Hi,

I started writing a Perl (prototype) script a year ago to make the
process of "updating" pool vms a little bit easier. What this script
does (should do) is:
- stop all vms which belong to this pool
- detach vms from pool
- delete vms
- delete pool
- delete template
- create new template from master vm
- create new pool
- add users/groups to pool

All these tasks are possible with the Python/JAVA SDKs and ovirt-shell,
too.
Just make sure no other vms/pools uses this template with thin
provisioned allocation policy. And don't forget error handling...


Regards,
René


> 
> > 
> > ___
> > 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: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released


On Thu, 2013-05-23 at 11:22 +0300, Itamar Heim wrote:
> On 05/23/2013 11:21 AM, René Koch (ovido) wrote:
> >
> > On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:
> >> On 05/23/2013 11:07 AM, René Koch (ovido) wrote:
> >>> On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:
>  On 05/22/2013 05:18 PM, Itamar Heim wrote:
> > On 05/22/2013 03:55 PM, René Koch (ovido) wrote:
> >>
> >> On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:
>   Original Message 
>  Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
>  Date: Thu, 16 May 2013 16:31:24 +0200
>  From: René Koch 
>  To: users 
> 
>  I'm happy to announce version 1.2 of check_rhev3.
> 
>  check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
>  which is
>  used to monitor datacenters, clusters, hosts, vms, vm pools and
>  storage
>  domains
>  of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
>  environments.
> 
>  The download locations are
>    *
>  https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
>    *
>  https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm
> 
> 
>    *
>  https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm
> 
> 
> 
>  For further information on how to install this plugin visit:
> 
>  https://github.com/ovido/check_rhev3/wiki/Installation-Documentation
> 
>  A detailed usage documentation can be found here:
>  https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
> 
> 
>  Changelog:
> 
>  - General:
>  -   Moved project to github: https://github.com/ovido/check_rhev3
> 
>  - New features:
>  -   Verify RHEV-M certificate
>  -   Allow authentication sessions for authentication in RHEV >= 3.1
>  and
>  oVirt >= 3.1
>  -   Use option -n  to check a specific nic
> 
>  - Bugs fixed:
>  -   Performance data issue with check_multi
> 
> 
>  If you have any questions or ideas, please drop me an email: 
>  r.k...@ovido.at.
> 
>  Thank you for using check_rhev3.
> 
> 
> 
> >>>
> >>> Hi Rene,
> >>>
> >>> we deployed the plugin and noticed its flooding the event log with
> >>> login
> >>> events for the user its using via the REST API.
> >>> can you please add persistent session to the REST API calls so login
> >>> will happen only once and won't flood the log?
> >>>
> >>> http://www.ovirt.org/Features/RESTSessionManagement
> >>
> >>
> >> It's one of the features in the latest version (1.2):
> >>
> >> -o, --cookie
> >>Use cookie based authenticated sessions (requires RHEV >= 3.1)
> >>
> >>
> >> I implemented it in the following way:
> >> - Plugin checks if file with session cookie exists (per default
> >> in /var/tmp)
> >> - If not: login with username and password (that's why you need to
> >> specify auth pair or authfile) and fetch JSESSIONID
> >> -- Writes ID into session cookie file
> >> - If cookie file is found: login using JSESSIONID and ignore username
> >> and password. So you can change username/password and login will still
> >> work.
> >> - If login using session ID fails and cookie file exists, it will be
> >> deleted and a login with username and password is tried the next time
> >> the plugin is executed
> >>
> >> If you start the script with -vvv you can see if login is down with 
> >> auth
> >> session or with username/password...
> >>
> >> I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.
> >
> > well, we are trying it with next version of RHEV actually :)
> > sasha - can you please start the script with -vvv to provide the log
> > for login behavior?
> >
>  Here is all (I hope) the relevant data:
>  [V] Starting the main script.
>  [V] Checking which component to monitor.
>  [D] check_host: Called function check_host.
>  [V] Host: Checking host .
>  [V] Host: No subcheck is specified, checking memory usage.
>  [D] check_statistics: Called function check_statistics.
>  [V] Statistics: Checking statistics of hosts.
>  [D] check_statistics: Input parameter $component: hosts
>  [D] check_statistics: Input parameter $search:
>  [D] check_statistics: Input parameter $statistics: memory
>  [D] check_statistics: Converting variables.
>  [D] check_statistics: Converted variable $url: hosts
>  [D] get_result: Called function get_result.
> >

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released


On 05/23/2013 11:21 AM, René Koch (ovido) wrote:


On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:

On 05/23/2013 11:07 AM, René Koch (ovido) wrote:

On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:

On 05/22/2013 05:18 PM, Itamar Heim wrote:

On 05/22/2013 03:55 PM, René Koch (ovido) wrote:


On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:

 Original Message 
Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
Date: Thu, 16 May 2013 16:31:24 +0200
From: René Koch 
To: users 

I'm happy to announce version 1.2 of check_rhev3.

check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
which is
used to monitor datacenters, clusters, hosts, vms, vm pools and
storage
domains
of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
environments.

The download locations are
  *
https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
  *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm


  *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm



For further information on how to install this plugin visit:

https://github.com/ovido/check_rhev3/wiki/Installation-Documentation

A detailed usage documentation can be found here:
https://github.com/ovido/check_rhev3/wiki/Usage-Documentation


Changelog:

- General:
-   Moved project to github: https://github.com/ovido/check_rhev3

- New features:
-   Verify RHEV-M certificate
-   Allow authentication sessions for authentication in RHEV >= 3.1
and
oVirt >= 3.1
-   Use option -n  to check a specific nic

- Bugs fixed:
-   Performance data issue with check_multi


If you have any questions or ideas, please drop me an email: 
r.k...@ovido.at.

Thank you for using check_rhev3.





Hi Rene,

we deployed the plugin and noticed its flooding the event log with
login
events for the user its using via the REST API.
can you please add persistent session to the REST API calls so login
will happen only once and won't flood the log?

http://www.ovirt.org/Features/RESTSessionManagement



It's one of the features in the latest version (1.2):

-o, --cookie
   Use cookie based authenticated sessions (requires RHEV >= 3.1)


I implemented it in the following way:
- Plugin checks if file with session cookie exists (per default
in /var/tmp)
- If not: login with username and password (that's why you need to
specify auth pair or authfile) and fetch JSESSIONID
-- Writes ID into session cookie file
- If cookie file is found: login using JSESSIONID and ignore username
and password. So you can change username/password and login will still
work.
- If login using session ID fails and cookie file exists, it will be
deleted and a login with username and password is tried the next time
the plugin is executed

If you start the script with -vvv you can see if login is down with auth
session or with username/password...

I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.


well, we are trying it with next version of RHEV actually :)
sasha - can you please start the script with -vvv to provide the log
for login behavior?


Here is all (I hope) the relevant data:
[V] Starting the main script.
[V] Checking which component to monitor.
[D] check_host: Called function check_host.
[V] Host: Checking host .
[V] Host: No subcheck is specified, checking memory usage.
[D] check_statistics: Called function check_statistics.
[V] Statistics: Checking statistics of hosts.
[D] check_statistics: Input parameter $component: hosts
[D] check_statistics: Input parameter $search:
[D] check_statistics: Input parameter $statistics: memory
[D] check_statistics: Converting variables.
[D] check_statistics: Converted variable $url: hosts
[D] get_result: Called function get_result.
[D] get_result: Input parameter $_[0]: /hosts?search=
[D] get_result: Input parameter $xml: hosts
[D] get_result: Input parameter $search: id
[D] rhev_connect: Called function rhev_connect.
[V] REST-API: Connecting to REST-API.
[D] rhev_connect: Input parameter: /hosts?search=.
[V] REST-API: RHEVM-API URL: https://:8443/api/hosts?search=
[V] REST-API: RHEVM-API User: 
[V] REST-API: RHEVM-API Password: 
[V] REST-API: cookie filename:
bm90dDA0LmVuZy5sYWIudGx2LnJlZGhhdC5jb20tdmlld2VyQG5vdHQwNC5lbmcubGFiLnRsdi5y
ZWRoYXQuY29tCg==
[D] rhev_connect: Using username and password authentication.
[V] REST-API: Cache-Control: no-cache
Connection: close
Date: Thu, 23 May 2013 07:50:33 GMT
Pragma: No-cache
Server: Apache-Coyote/1.1
Content-Type: application/xml
Expires: Thu, 01 Jan 1970 02:00:00 IST
Client-Date: Thu, 23 May 2013 07:50:33 GMT
Client-Peer: 10.35.16.97:8443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=Red Hat TLV/CN=CA-.31149
Client-SSL-Cert-Subject: /C=US/O=Red Hat TLV/CN=
Client-SSL-Cipher: DHE-RSA-AES256-SHA
Client-SSL-Warning: Peer certificate not verified
Set-Cookie: JSESSIONID=8gUbxG1-uk8HOi2tq4krw7tq; Path=/api; Secure
[D] rhev_connect: 

# The out

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released


On Thu, 2013-05-23 at 11:11 +0300, Itamar Heim wrote:
> On 05/23/2013 11:07 AM, René Koch (ovido) wrote:
> > On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:
> >> On 05/22/2013 05:18 PM, Itamar Heim wrote:
> >>> On 05/22/2013 03:55 PM, René Koch (ovido) wrote:
> 
>  On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:
> >>  Original Message 
> >> Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
> >> Date: Thu, 16 May 2013 16:31:24 +0200
> >> From: René Koch 
> >> To: users 
> >>
> >> I'm happy to announce version 1.2 of check_rhev3.
> >>
> >> check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
> >> which is
> >> used to monitor datacenters, clusters, hosts, vms, vm pools and
> >> storage
> >> domains
> >> of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
> >> environments.
> >>
> >> The download locations are
> >>  *
> >> https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
> >>  *
> >> https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm
> >>
> >>
> >>  *
> >> https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm
> >>
> >>
> >>
> >> For further information on how to install this plugin visit:
> >>
> >> https://github.com/ovido/check_rhev3/wiki/Installation-Documentation
> >>
> >> A detailed usage documentation can be found here:
> >> https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
> >>
> >>
> >> Changelog:
> >>
> >> - General:
> >> -   Moved project to github: https://github.com/ovido/check_rhev3
> >>
> >> - New features:
> >> -   Verify RHEV-M certificate
> >> -   Allow authentication sessions for authentication in RHEV >= 3.1
> >> and
> >> oVirt >= 3.1
> >> -   Use option -n  to check a specific nic
> >>
> >> - Bugs fixed:
> >> -   Performance data issue with check_multi
> >>
> >>
> >> If you have any questions or ideas, please drop me an email: 
> >> r.k...@ovido.at.
> >>
> >> Thank you for using check_rhev3.
> >>
> >>
> >>
> >
> > Hi Rene,
> >
> > we deployed the plugin and noticed its flooding the event log with
> > login
> > events for the user its using via the REST API.
> > can you please add persistent session to the REST API calls so login
> > will happen only once and won't flood the log?
> >
> > http://www.ovirt.org/Features/RESTSessionManagement
> 
> 
>  It's one of the features in the latest version (1.2):
> 
> -o, --cookie
>    Use cookie based authenticated sessions (requires RHEV >= 3.1)
> 
> 
>  I implemented it in the following way:
>  - Plugin checks if file with session cookie exists (per default
>  in /var/tmp)
>  - If not: login with username and password (that's why you need to
>  specify auth pair or authfile) and fetch JSESSIONID
>  -- Writes ID into session cookie file
>  - If cookie file is found: login using JSESSIONID and ignore username
>  and password. So you can change username/password and login will still
>  work.
>  - If login using session ID fails and cookie file exists, it will be
>  deleted and a login with username and password is tried the next time
>  the plugin is executed
> 
>  If you start the script with -vvv you can see if login is down with auth
>  session or with username/password...
> 
>  I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.
> >>>
> >>> well, we are trying it with next version of RHEV actually :)
> >>> sasha - can you please start the script with -vvv to provide the log
> >>> for login behavior?
> >>>
> >> Here is all (I hope) the relevant data:
> >> [V] Starting the main script.
> >> [V] Checking which component to monitor.
> >> [D] check_host: Called function check_host.
> >> [V] Host: Checking host .
> >> [V] Host: No subcheck is specified, checking memory usage.
> >> [D] check_statistics: Called function check_statistics.
> >> [V] Statistics: Checking statistics of hosts.
> >> [D] check_statistics: Input parameter $component: hosts
> >> [D] check_statistics: Input parameter $search:
> >> [D] check_statistics: Input parameter $statistics: memory
> >> [D] check_statistics: Converting variables.
> >> [D] check_statistics: Converted variable $url: hosts
> >> [D] get_result: Called function get_result.
> >> [D] get_result: Input parameter $_[0]: /hosts?search=
> >> [D] get_result: Input parameter $xml: hosts
> >> [D] get_result: Input parameter $search: id
> >> [D] rhev_connect: Called function rhev_connect.
> >> [V] REST-API: Connecting to REST-API.
> >> [D] rhev_connect: Input parameter: /hosts?search=.
> >> [V] REST-API: RHEVM-API URL: https://:8443/api/hosts?sea

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released


On 05/23/2013 11:07 AM, René Koch (ovido) wrote:

On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:

On 05/22/2013 05:18 PM, Itamar Heim wrote:

On 05/22/2013 03:55 PM, René Koch (ovido) wrote:


On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:

 Original Message 
Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
Date: Thu, 16 May 2013 16:31:24 +0200
From: René Koch 
To: users 

I'm happy to announce version 1.2 of check_rhev3.

check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
which is
used to monitor datacenters, clusters, hosts, vms, vm pools and
storage
domains
of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
environments.

The download locations are
 *
https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
 *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm


 *
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm



For further information on how to install this plugin visit:

https://github.com/ovido/check_rhev3/wiki/Installation-Documentation

A detailed usage documentation can be found here:
https://github.com/ovido/check_rhev3/wiki/Usage-Documentation


Changelog:

- General:
-   Moved project to github: https://github.com/ovido/check_rhev3

- New features:
-   Verify RHEV-M certificate
-   Allow authentication sessions for authentication in RHEV >= 3.1
and
oVirt >= 3.1
-   Use option -n  to check a specific nic

- Bugs fixed:
-   Performance data issue with check_multi


If you have any questions or ideas, please drop me an email: 
r.k...@ovido.at.

Thank you for using check_rhev3.





Hi Rene,

we deployed the plugin and noticed its flooding the event log with
login
events for the user its using via the REST API.
can you please add persistent session to the REST API calls so login
will happen only once and won't flood the log?

http://www.ovirt.org/Features/RESTSessionManagement



It's one of the features in the latest version (1.2):

   -o, --cookie
  Use cookie based authenticated sessions (requires RHEV >= 3.1)


I implemented it in the following way:
- Plugin checks if file with session cookie exists (per default
in /var/tmp)
- If not: login with username and password (that's why you need to
specify auth pair or authfile) and fetch JSESSIONID
-- Writes ID into session cookie file
- If cookie file is found: login using JSESSIONID and ignore username
and password. So you can change username/password and login will still
work.
- If login using session ID fails and cookie file exists, it will be
deleted and a login with username and password is tried the next time
the plugin is executed

If you start the script with -vvv you can see if login is down with auth
session or with username/password...

I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.


well, we are trying it with next version of RHEV actually :)
sasha - can you please start the script with -vvv to provide the log
for login behavior?


Here is all (I hope) the relevant data:
[V] Starting the main script.
[V] Checking which component to monitor.
[D] check_host: Called function check_host.
[V] Host: Checking host .
[V] Host: No subcheck is specified, checking memory usage.
[D] check_statistics: Called function check_statistics.
[V] Statistics: Checking statistics of hosts.
[D] check_statistics: Input parameter $component: hosts
[D] check_statistics: Input parameter $search:
[D] check_statistics: Input parameter $statistics: memory
[D] check_statistics: Converting variables.
[D] check_statistics: Converted variable $url: hosts
[D] get_result: Called function get_result.
[D] get_result: Input parameter $_[0]: /hosts?search=
[D] get_result: Input parameter $xml: hosts
[D] get_result: Input parameter $search: id
[D] rhev_connect: Called function rhev_connect.
[V] REST-API: Connecting to REST-API.
[D] rhev_connect: Input parameter: /hosts?search=.
[V] REST-API: RHEVM-API URL: https://:8443/api/hosts?search=
[V] REST-API: RHEVM-API User: 
[V] REST-API: RHEVM-API Password: 
[V] REST-API: cookie filename:
bm90dDA0LmVuZy5sYWIudGx2LnJlZGhhdC5jb20tdmlld2VyQG5vdHQwNC5lbmcubGFiLnRsdi5y
ZWRoYXQuY29tCg==
[D] rhev_connect: Using username and password authentication.
[V] REST-API: Cache-Control: no-cache
Connection: close
Date: Thu, 23 May 2013 07:50:33 GMT
Pragma: No-cache
Server: Apache-Coyote/1.1
Content-Type: application/xml
Expires: Thu, 01 Jan 1970 02:00:00 IST
Client-Date: Thu, 23 May 2013 07:50:33 GMT
Client-Peer: 10.35.16.97:8443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=Red Hat TLV/CN=CA-.31149
Client-SSL-Cert-Subject: /C=US/O=Red Hat TLV/CN=
Client-SSL-Cipher: DHE-RSA-AES256-SHA
Client-SSL-Warning: Peer certificate not verified
Set-Cookie: JSESSIONID=8gUbxG1-uk8HOi2tq4krw7tq; Path=/api; Secure
[D] rhev_connect: 

# The output is truncated 



It seems to me that you did start the plugin without "-o" option...

Without -o pl

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released

2013-05-23 Thread Sasha Chuzhoy


On 05/22/2013 05:18 PM, Itamar Heim wrote:

On 05/22/2013 03:55 PM, René Koch (ovido) wrote:


On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:

 Original Message 
Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
Date: Thu, 16 May 2013 16:31:24 +0200
From: René Koch 
To: users 

I'm happy to announce version 1.2 of check_rhev3.

check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
which is
used to monitor datacenters, clusters, hosts, vms, vm pools and 
storage

domains
of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
environments.

The download locations are
* 
https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz

*
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm 



*
https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm 




For further information on how to install this plugin visit:

https://github.com/ovido/check_rhev3/wiki/Installation-Documentation


A detailed usage documentation can be found here:
https://github.com/ovido/check_rhev3/wiki/Usage-Documentation


Changelog:

- General:
-   Moved project to github: https://github.com/ovido/check_rhev3

- New features:
-   Verify RHEV-M certificate
-   Allow authentication sessions for authentication in RHEV >= 3.1 
and

oVirt >= 3.1
-   Use option -n  to check a specific nic

- Bugs fixed:
-   Performance data issue with check_multi


If you have any questions or ideas, please drop me an email: 
r.k...@ovido.at.

Thank you for using check_rhev3.





Hi Rene,

we deployed the plugin and noticed its flooding the event log with 
login

events for the user its using via the REST API.
can you please add persistent session to the REST API calls so login
will happen only once and won't flood the log?

http://www.ovirt.org/Features/RESTSessionManagement



It's one of the features in the latest version (1.2):

  -o, --cookie
 Use cookie based authenticated sessions (requires RHEV >= 3.1)


I implemented it in the following way:
- Plugin checks if file with session cookie exists (per default
in /var/tmp)
- If not: login with username and password (that's why you need to
specify auth pair or authfile) and fetch JSESSIONID
-- Writes ID into session cookie file
- If cookie file is found: login using JSESSIONID and ignore username
and password. So you can change username/password and login will still
work.
- If login using session ID fails and cookie file exists, it will be
deleted and a login with username and password is tried the next time
the plugin is executed

If you start the script with -vvv you can see if login is down with auth
session or with username/password...

I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.


well, we are trying it with next version of RHEV actually :)
sasha - can you please start the script with -vvv to provide the log 
for login behavior?



Here is all (I hope) the relevant data:
[V] Starting the main script.
[V] Checking which component to monitor.
[D] check_host: Called function check_host.
[V] Host: Checking host .
[V] Host: No subcheck is specified, checking memory usage.
[D] check_statistics: Called function check_statistics.
[V] Statistics: Checking statistics of hosts.
[D] check_statistics: Input parameter $component: hosts
[D] check_statistics: Input parameter $search:
[D] check_statistics: Input parameter $statistics: memory
[D] check_statistics: Converting variables.
[D] check_statistics: Converted variable $url: hosts
[D] get_result: Called function get_result.
[D] get_result: Input parameter $_[0]: /hosts?search=
[D] get_result: Input parameter $xml: hosts
[D] get_result: Input parameter $search: id
[D] rhev_connect: Called function rhev_connect.
[V] REST-API: Connecting to REST-API.
[D] rhev_connect: Input parameter: /hosts?search=.
[V] REST-API: RHEVM-API URL: https://:8443/api/hosts?search=
[V] REST-API: RHEVM-API User: 
[V] REST-API: RHEVM-API Password: 
[V] REST-API: cookie filename: 
bm90dDA0LmVuZy5sYWIudGx2LnJlZGhhdC5jb20tdmlld2VyQG5vdHQwNC5lbmcubGFiLnRsdi5y

ZWRoYXQuY29tCg==
[D] rhev_connect: Using username and password authentication.
[V] REST-API: Cache-Control: no-cache
Connection: close
Date: Thu, 23 May 2013 07:50:33 GMT
Pragma: No-cache
Server: Apache-Coyote/1.1
Content-Type: application/xml
Expires: Thu, 01 Jan 1970 02:00:00 IST
Client-Date: Thu, 23 May 2013 07:50:33 GMT
Client-Peer: 10.35.16.97:8443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=Red Hat TLV/CN=CA-.31149
Client-SSL-Cert-Subject: /C=US/O=Red Hat TLV/CN=
Client-SSL-Cipher: DHE-RSA-AES256-SHA
Client-SSL-Warning: Peer certificate not verified
Set-Cookie: JSESSIONID=8gUbxG1-uk8HOi2tq4krw7tq; Path=/api; Secure
[D] rhev_connect: 

# The output is truncated 

Thanks,
   Itamar




--
Sasha Chuzhoy
Engineering Operations
Red Hat Israel Ltd


___
Users mailing list
Users@ovirt.org
http://li

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released

On Thu, 2013-05-23 at 10:55 +0300, Sasha Chuzhoy wrote:
> On 05/22/2013 05:18 PM, Itamar Heim wrote:
> > On 05/22/2013 03:55 PM, René Koch (ovido) wrote:
> >>
> >> On Wed, 2013-05-22 at 14:59 +0300, Itamar Heim wrote:
>   Original Message 
>  Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released
>  Date: Thu, 16 May 2013 16:31:24 +0200
>  From: René Koch 
>  To: users 
> 
>  I'm happy to announce version 1.2 of check_rhev3.
> 
>  check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks,
>  which is
>  used to monitor datacenters, clusters, hosts, vms, vm pools and 
>  storage
>  domains
>  of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization
>  environments.
> 
>  The download locations are
>  * 
>  https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz
>  *
>  https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i686.rpm
>   
> 
> 
>  *
>  https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x86_64.rpm
>   
> 
> 
> 
>  For further information on how to install this plugin visit:
>  
>  https://github.com/ovido/check_rhev3/wiki/Installation-Documentation
> 
>  A detailed usage documentation can be found here:
>  https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
> 
> 
>  Changelog:
> 
>  - General:
>  -   Moved project to github: https://github.com/ovido/check_rhev3
> 
>  - New features:
>  -   Verify RHEV-M certificate
>  -   Allow authentication sessions for authentication in RHEV >= 3.1 
>  and
>  oVirt >= 3.1
>  -   Use option -n  to check a specific nic
> 
>  - Bugs fixed:
>  -   Performance data issue with check_multi
> 
> 
>  If you have any questions or ideas, please drop me an email: 
>  r.k...@ovido.at.
> 
>  Thank you for using check_rhev3.
> 
> 
> 
> >>>
> >>> Hi Rene,
> >>>
> >>> we deployed the plugin and noticed its flooding the event log with 
> >>> login
> >>> events for the user its using via the REST API.
> >>> can you please add persistent session to the REST API calls so login
> >>> will happen only once and won't flood the log?
> >>>
> >>> http://www.ovirt.org/Features/RESTSessionManagement
> >>
> >>
> >> It's one of the features in the latest version (1.2):
> >>
> >>   -o, --cookie
> >>  Use cookie based authenticated sessions (requires RHEV >= 3.1)
> >>
> >>
> >> I implemented it in the following way:
> >> - Plugin checks if file with session cookie exists (per default
> >> in /var/tmp)
> >> - If not: login with username and password (that's why you need to
> >> specify auth pair or authfile) and fetch JSESSIONID
> >> -- Writes ID into session cookie file
> >> - If cookie file is found: login using JSESSIONID and ignore username
> >> and password. So you can change username/password and login will still
> >> work.
> >> - If login using session ID fails and cookie file exists, it will be
> >> deleted and a login with username and password is tried the next time
> >> the plugin is executed
> >>
> >> If you start the script with -vvv you can see if login is down with auth
> >> session or with username/password...
> >>
> >> I didn't test it with oVirt 3.2 (yet), but works fine in RHEV 3.1.
> >
> > well, we are trying it with next version of RHEV actually :)
> > sasha - can you please start the script with -vvv to provide the log 
> > for login behavior?
> >
> Here is all (I hope) the relevant data:
> [V] Starting the main script.
> [V] Checking which component to monitor.
> [D] check_host: Called function check_host.
> [V] Host: Checking host .
> [V] Host: No subcheck is specified, checking memory usage.
> [D] check_statistics: Called function check_statistics.
> [V] Statistics: Checking statistics of hosts.
> [D] check_statistics: Input parameter $component: hosts
> [D] check_statistics: Input parameter $search:
> [D] check_statistics: Input parameter $statistics: memory
> [D] check_statistics: Converting variables.
> [D] check_statistics: Converted variable $url: hosts
> [D] get_result: Called function get_result.
> [D] get_result: Input parameter $_[0]: /hosts?search=
> [D] get_result: Input parameter $xml: hosts
> [D] get_result: Input parameter $search: id
> [D] rhev_connect: Called function rhev_connect.
> [V] REST-API: Connecting to REST-API.
> [D] rhev_connect: Input parameter: /hosts?search=.
> [V] REST-API: RHEVM-API URL: https://:8443/api/hosts?search=
> [V] REST-API: RHEVM-API User: 
> [V] REST-API: RHEVM-API Password: 
> [V] REST-API: cookie filename: 
> bm90dDA0LmVuZy5sYWIudGx2LnJlZGhhdC5jb20tdmlld2VyQG5vdHQwNC5lbmcubGFiLnRsdi5y
> ZWRoYXQuY29tCg==
> [D] rhev_connect: Using username and password authentication.
> [V] REST-API: Cache-Control: no-cache
> Connection: close
> Date: Thu, 23 May 2013 0

Re: [Users] Active Directory Groups