ovirt 3.5 Test day 1 - vdsm-tool configure libvirt with python code
Hi all, I was assigned to test [1], which was fixed by [2], which pointed at [3]. Most things worked as expected. Issues I noticed: * the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work. * the vdsm-tool package does not depend on vdsm, but 'vdsm-tool configure --force' fails without it. I didn't open bugs on them because they seem insignificant. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1069636 [2] http://gerrit.ovirt.org/27298 [3] http://www.ovirt.org/Configure_libvirt_testing_matrix -- Didi
On 07/01/2014 05:13 PM, Yedidyah Bar David wrote:
Hi all,
I was assigned to test [1], which was fixed by [2], which pointed at [3].
Most things worked as expected.
Issues I noticed:
* the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work.
"vdsClient -s" means to use secure communication, which will work properly if "ssl=true" is configured in vdsm.conf (btw, if ssl not specified there true is the default). bare in mind, that after changing the conf file you need to restart vdsmd service. when you change vdsm.conf like "ssl=true" to "ssl=false", before running vdsmd again, you need to perform "vdsm-tool configure" to configure all related service to work properly with the new vdsm configuration (in that case, not secured which require libvirtd.conf and qemu.conf update) after vdsm-tool configures libvirtd.conf and qemu.conf accordingly , you can start vdsmd and see that "vdsClient" (without -s) works properly. this works as far as I checked in vdsm 3.5
* the vdsm-tool package does not depend on vdsm, but 'vdsm-tool configure --force' fails without it.
I didn't open bugs on them because they seem insignificant.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1069636 [2] http://gerrit.ovirt.org/27298 [3] http://www.ovirt.org/Configure_libvirt_testing_matrix
-- Yaniv Bronhaim.
----- Original Message -----
From: "ybronhei" <ybronhei@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com>, devel@ovirt.org Sent: Thursday, July 3, 2014 6:05:52 PM Subject: Re: [ovirt-devel] ovirt 3.5 Test day 1 - vdsm-tool configure libvirt with python code
On 07/01/2014 05:13 PM, Yedidyah Bar David wrote:
Hi all,
I was assigned to test [1], which was fixed by [2], which pointed at [3].
Most things worked as expected.
Issues I noticed:
* the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work.
"vdsClient -s" means to use secure communication, which will work properly if "ssl=true" is configured in vdsm.conf (btw, if ssl not specified there true is the default).
bare in mind, that after changing the conf file you need to restart vdsmd service.
when you change vdsm.conf like "ssl=true" to "ssl=false", before running vdsmd again, you need to perform "vdsm-tool configure" to configure all related service to work properly with the new vdsm configuration (in that case, not secured which require libvirtd.conf and qemu.conf update)
after vdsm-tool configures libvirtd.conf and qemu.conf accordingly , you can start vdsmd and see that "vdsClient" (without -s) works properly.
this works as far as I checked in vdsm 3.5
Not sure I got you right - with the above (edit/configure/restart), is it intended that '-s' will work with 'ssl=false'? Because iirc it didn't. I do not think it's important that it works - if a user wants ssl they should obviously do 'ssl=true' and '-s', and if not, 'ssl=false' and no '-s'. The only reason I tested this and point out above is that it is mentioned in the wiki table that it's supposed to work and it didn't for me (again, if I understood everything correctly). -- Didi
On 07/03/2014 06:11 PM, Yedidyah Bar David wrote:
----- Original Message -----
From: "ybronhei" <ybronhei@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com>, devel@ovirt.org Sent: Thursday, July 3, 2014 6:05:52 PM Subject: Re: [ovirt-devel] ovirt 3.5 Test day 1 - vdsm-tool configure libvirt with python code
On 07/01/2014 05:13 PM, Yedidyah Bar David wrote:
Hi all,
I was assigned to test [1], which was fixed by [2], which pointed at [3].
Most things worked as expected.
Issues I noticed:
* the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work.
"vdsClient -s" means to use secure communication, which will work properly if "ssl=true" is configured in vdsm.conf (btw, if ssl not specified there true is the default).
bare in mind, that after changing the conf file you need to restart vdsmd service.
when you change vdsm.conf like "ssl=true" to "ssl=false", before running vdsmd again, you need to perform "vdsm-tool configure" to configure all related service to work properly with the new vdsm configuration (in that case, not secured which require libvirtd.conf and qemu.conf update)
after vdsm-tool configures libvirtd.conf and qemu.conf accordingly , you can start vdsmd and see that "vdsClient" (without -s) works properly.
this works as far as I checked in vdsm 3.5
Not sure I got you right - with the above (edit/configure/restart), is it intended that '-s' will work with 'ssl=false'? Because iirc it didn't. -s means secured, and you set ssl=false. so no, when you set ssl to false, vdsClient with -s should not work.
I do not think it's important that it works - if a user wants ssl they should obviously do 'ssl=true' and '-s', and if not, 'ssl=false' and no '-s'. The only reason I tested this and point out above is that it is mentioned in the wiki table that it's supposed to work and it didn't for me (again, if I understood everything correctly).
mooli, maybe the wiki misleading in that area. consider to update it
-- Yaniv Bronhaim.
----- Original Message -----
From: "ybronhei" <ybronhei@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com>, "Mooli Tayer" <mtayer@redhat.com> Cc: devel@ovirt.org Sent: Thursday, July 3, 2014 6:22:52 PM Subject: Re: [ovirt-devel] ovirt 3.5 Test day 1 - vdsm-tool configure libvirt with python code
On 07/03/2014 06:11 PM, Yedidyah Bar David wrote:
----- Original Message -----
From: "ybronhei" <ybronhei@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com>, devel@ovirt.org Sent: Thursday, July 3, 2014 6:05:52 PM Subject: Re: [ovirt-devel] ovirt 3.5 Test day 1 - vdsm-tool configure libvirt with python code
On 07/01/2014 05:13 PM, Yedidyah Bar David wrote:
Hi all,
I was assigned to test [1], which was fixed by [2], which pointed at [3].
Most things worked as expected.
Issues I noticed:
* the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work.
"vdsClient -s" means to use secure communication, which will work properly if "ssl=true" is configured in vdsm.conf (btw, if ssl not specified there true is the default).
bare in mind, that after changing the conf file you need to restart vdsmd service.
when you change vdsm.conf like "ssl=true" to "ssl=false", before running vdsmd again, you need to perform "vdsm-tool configure" to configure all related service to work properly with the new vdsm configuration (in that case, not secured which require libvirtd.conf and qemu.conf update)
after vdsm-tool configures libvirtd.conf and qemu.conf accordingly , you can start vdsmd and see that "vdsClient" (without -s) works properly.
this works as far as I checked in vdsm 3.5
Not sure I got you right - with the above (edit/configure/restart), is it intended that '-s' will work with 'ssl=false'? Because iirc it didn't. -s means secured, and you set ssl=false. so no, when you set ssl to false, vdsClient with -s should not work.
Very well. Just a note about how it does not work - one case hangs trying to connect to a port indefinitely, the other outputs an error message. Don't remember which is which. As I said, none of them is that important.
I do not think it's important that it works - if a user wants ssl they should obviously do 'ssl=true' and '-s', and if not, 'ssl=false' and no '-s'. The only reason I tested this and point out above is that it is mentioned in the wiki table that it's supposed to work and it didn't for me (again, if I understood everything correctly).
mooli, maybe the wiki misleading in that area. consider to update it
-- Yaniv Bronhaim.
-- Didi
Hi all, I repeated my tests from test day 1 with updated packages and got the same results - all seem ok. -- Didi ----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: devel@ovirt.org Cc: "Mooli Tayer" <mtayer@redhat.com> Sent: Tuesday, July 1, 2014 5:13:25 PM Subject: ovirt 3.5 Test day 1 - vdsm-tool configure libvirt with python code
Hi all,
I was assigned to test [1], which was fixed by [2], which pointed at [3].
Most things worked as expected.
Issues I noticed:
* the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work.
* the vdsm-tool package does not depend on vdsm, but 'vdsm-tool configure --force' fails without it.
I didn't open bugs on them because they seem insignificant.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1069636 [2] http://gerrit.ovirt.org/27298 [3] http://www.ovirt.org/Configure_libvirt_testing_matrix -- Didi
participants (2)
-
ybronhei -
Yedidyah Bar David