Re: [ovirt-users] for some reason ovirtnode creates unecessary vg and lvs

[martin chamambo]

I created a vg and an lv using targetcli on a centos 7.3 host,managed to
connect my ovirtengine on that Lv When I reboot my engine and nodes,
the storage won't come up and when I check my storage server,the lun will
have been deleted and those lvs and vg will be automatically created.I have
initialized my storage more than 3 times and.the same thing keeps happening

On Apr 6, 2017 8:31 PM, "Liron Aravot"  wrote:

>
>
> On Wed, Apr 5, 2017 at 3:16 PM, Yaniv Kaul  wrote:
>
>>
>>
>> On Sun, Apr 2, 2017 at 9:15 PM, martin chamambo 
>> wrote:
>>
>>> I managed to configure the mail iscsi domain for my ovirt 4.1 engine and
>>> node , it connects to the storage initially and initialises the data center
>>> ,but after rebooting the node and engine , it creates unecessary vg and lvs
>>> like below
>>>
>>> 280246d3-ac7b-44ff-8c03-dc2bcb9edb70 d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a- 128.00m
>>>   2d57ab88-16e4-4007-9047-55fc4a35b534 d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a- 128.00m
>>>   ids  d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a- 128.00m
>>>   inboxd5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a- 128.00m
>>>   leases   d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a-   2.00g
>>>   master   d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a-   1.00g
>>>   metadata d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a- 512.00m
>>>   outbox   d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a- 128.00m
>>>   xleases  d5104206-5863-4f9d-9ea7-2b140c97d65f
>>> -wi-a-   1.00g
>>>
>>> whats the cause of this
>>>
>>
>> I'm not sure what is the problem? These LVs are the metadata LVs for a
>> storage domain.
>> Y.
>>
>>
>
> As Yaniv wrote - those are LVs created by oVirt.
> Is the node  currently in use in oVirt? if so, it should be connected to
> your storage server and have those vg/lvs.
>
>>
>>> NB:mY ISCSI storage is on a centos 7 box
>>>
>>> ___
>>> 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] Upgrading libguestfs to import debian VM

[Tomáš Golembiovský]

Hi,

On Thu, 6 Apr 2017 12:33:36 +0100
Simon Vincent  wrote:

> I find that running oVirt 4.1.1 I can not import any debian based VMs as
> virt-v2v/libguestfs is too old.
> This bug report https://bugzilla.redhat.com/show_bug.cgi?id=1362497
> indicates that newer versions of libguestfs support importing debian and
> Ubuntu VMs.

you did not specify what OS are your hosts so I assume it is
RHEL/CentOS. The newer libguestfs is scheduled to appear in 7.4.

AFAIK it should already be available for Fedora 25/26.


> Are there any plans to include a newer version of libguestfs in oVirt soon?
> If I built a newer version of libguestfs on my ovirt-node would it break
> everything?

That should be OK. If you feel brave enough to do that, sure you can
build your own RPMs. You should not need to update anything else
(libvirt/qemu). 


> 
> Regards
> 
> Simon


-- 
Tomáš Golembiovský 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mount glusterfs from 127.0.0.1

[Jason Brooks]

On Thu, Apr 6, 2017 at 1:33 PM, /dev/null  wrote:
> Jason,
>
> yes - thats how i am doing it. I wonder if its better to access the local 
> bricks
> primarily for both relyability and performance/load.
>
> - if one node fails, it does not mean an impact if we access 127.0.0.1
> - if i write to 127.0.0.1 it might be faster than accessing on network host 
> from all
> hypervisors
> - backup-volfile-servers was set to the other nodes if local gluster fails
>
> My question is, if it´s critical to access all replicas simultanly.

I think that using localhost on each node will lead to split-brain.
With the backup volfile setting taking care of failover, I don't think
mounting at localhost buys you anything, anyway. Gluster already
handles spreading out the load among the hosts on its own, when you're
using the native gluster mounts (vs nfs, where you are accessing
through the specified mount point).
>
> Thanks!
>
> On Thu, 6 Apr 2017 12:30:28 -0700, Jason Brooks wrote
>> On Thu, Apr 6, 2017 at 8:53 AM, /dev/null  wrote:
>> > Hello all together,
>> >
>> > having a three node oVirt cluster for virtualization and gluster, each 
>> > node providing
>> > bricks for a replica 3 volume, I would like to mount the volume from 
>> > 127.0.0.1 to
>> > distribute i/o and to have a better failover situation.
>>
>> The right way to do this is to fill in the mount options with:
>>
>> backup-volfile-servers=:
>>
>
> --
> Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht
> und ist - aktuelle Virenscanner vorausgesetzt - sauber.
> For all your IT requirements visit: http://www.transtec.co.uk
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mount glusterfs from 127.0.0.1

[/dev/null]

Jason,

yes - thats how i am doing it. I wonder if its better to access the local bricks
primarily for both relyability and performance/load. 

- if one node fails, it does not mean an impact if we access 127.0.0.1
- if i write to 127.0.0.1 it might be faster than accessing on network host 
from all
hypervisors
- backup-volfile-servers was set to the other nodes if local gluster fails

My question is, if it´s critical to access all replicas simultanly.

Thanks!

On Thu, 6 Apr 2017 12:30:28 -0700, Jason Brooks wrote
> On Thu, Apr 6, 2017 at 8:53 AM, /dev/null  wrote:
> > Hello all together,
> >
> > having a three node oVirt cluster for virtualization and gluster, each node 
> > providing
> > bricks for a replica 3 volume, I would like to mount the volume from 
> > 127.0.0.1 to
> > distribute i/o and to have a better failover situation.
> 
> The right way to do this is to fill in the mount options with:
> 
> backup-volfile-servers=:
> 

--
Diese Nachricht wurde auf Viren und andere gef�hrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
For all your IT requirements visit: http://www.transtec.co.uk

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

Re: [ovirt-users] mount glusterfs from 127.0.0.1

[Jason Brooks]

On Thu, Apr 6, 2017 at 8:53 AM, /dev/null  wrote:
> Hello all together,
>
> having a three node oVirt cluster for virtualization and gluster, each node 
> providing
> bricks for a replica 3 volume, I would like to mount the volume from 
> 127.0.0.1 to
> distribute i/o and to have a better failover situation.

The right way to do this is to fill in the mount options with:

backup-volfile-servers=:


>
> This leads to a volume having the same address in oVirt althoght it is 
> addressed on
> different hosts.
>
> Is this common, supported, relyable and recommended?
>
> Thanks in advance!
>
> /dev/null
>
> --
> Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht
> und ist - aktuelle Virenscanner vorausgesetzt - sauber.
> For all your IT requirements visit: http://www.transtec.co.uk
>
>
> ___
> 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] New SAN Storage Domain: Cannot deactivate Logical Volume

[Adam Litke]

Actually I was seeing something similar yesterday and I have seen very
sporadic failures in this area in the past.  It seems that in some cases
the VG is not properly set up before we try to use it (perhaps a race with
devicemapper).  I wonder if adding some sleeps in
BlockStorageDomain.create() would mask the issue.  If so, we need to figure
out where the race is happening and might need to add some polling to make
sure the underlying devices are ready.

On Thu, Apr 6, 2017 at 2:35 PM, Liron Aravot  wrote:

> Thanks Alexey,
> Nir/Adam/Raz - any initial thoughts about that? have you encountered that
> issue before?
>
> Regards,
> Liron
>
> On Wed, Apr 5, 2017 at 12:21 PM, Николаев Алексей <
> alexeynikolaev.p...@yandex.ru> wrote:
>
>> Hi Liron,
>>
>> Well, this error appear on freshly installed oVirt hosted engine 4.1.1.6-1
>> with oVirt Node NG 4.1.
>> There is no engine major version upgrade.
>> Node NG was updated from 4.1.0 to 4.1.1 by the ovirt-node-ng-image* pkgs.
>>
>> vdsm version is:
>>
>> Installed Packages
>> Name: vdsm
>> Arch: x86_64
>> Version : 4.19.10
>> Release : 1.el7.centos
>> --
>>
>> I also install oVirt 3.6 hosted engine on another server (CentOS 7.2
>> minimal, not updated to 7.3) and add the some ISCSI target as the data
>> domain. This work OK.
>> After I update engine from 3.6 to 4.1. ISCSI data domain is OK after
>> update. Another ISCSI targets was added as data domain without errors.
>>
>> vdsm version is:
>>
>> Installed Packages
>> Name: vdsm
>> Arch: noarch
>> Version : 4.17.32
>> Release : 0.el7.centos
>>
>> 04.04.2017, 16:48, "Liron Aravot" :
>>
>> Hi Alexey,
>>
>> Looking in your logs - it indeed look weird, the vg is created seconds
>> later we fail to get it when attempting to create the domain.
>>
>> Did you upgrade/downgraded only the engine version or the vdsm version as
>> well?
>>
>> 2017-04-03 11:16:39,595+0300 INFO  (jsonrpc/4) [dispatcher] Run and
>> protect: createVG(vgname=u'3050e121-83b5-474e-943f-6dc52af38a17',
>> devlist=[u'3600140505d11d22e61f46a6ba4a
>> 7bdc7'], force=False, options=None) (logUtils:51)
>>
>>
>> output error', '  /dev/mapper/36001405b7dd7b800e7049ecbf6830637: read
>> failed after 0 of 4096 at 4294967230464: Input/output error', '
>>  /dev/mapper/36001405b7dd7b800e7049ecbf
>> 6830637: read failed after 0 of 4096 at 4294967287808: Input/output
>> error', '  WARNING: Error counts reached a limit of 3. Device /dev/mapper/
>> 36001405b7dd7b800e7049ecbf68306
>> 37 was disabled', '  Failed to find physical volume "/dev/mapper/
>> 3600140505d11d22e61f46a6ba4a7bdc7".'] (lvm:323)
>> 2017-04-03 11:16:38,832+0300 WARN  (jsonrpc/5) [storage.HSM] getPV
>> failed for guid: 3600140505d11d22e61f46a6ba4a7bdc7 (hsm:1973)
>> Traceback (most recent call last):
>>   File "/usr/share/vdsm/storage/hsm.py", line 1970, in _getDeviceList
>> pv = lvm.getPV(guid)
>>   File "/usr/share/vdsm/storage/lvm.py", line 853, in getPV
>> raise se.((pvName,))
>>
>>
>> On Tue, Apr 4, 2017 at 3:33 PM, Николаев Алексей <
>> alexeynikolaev.p...@yandex.ru> wrote:
>>
>> The last I was update oVirt oVirt 3.6.7.5-1 to oVirt 4.1.1.6-1. Main
>> ISCSI datadomain is OK. Another one ISCSI datadomain was added
>> successfully.
>>
>> The problem are only with freshly installed oVirt 4.1.1.6-1.
>>
>> Added logs after update ovirt and add new ISCSI datadomains.
>>
>> 03.04.2017, 17:26, "Николаев Алексей" :
>>
>> Also I test again ISCSI TARGET with oVirt 3.6.7.5-1 and CentOS 7.2.1511
>> host. ISCSI data domain was added succesfully. "the truth is out there".
>> Add logs.
>>
>> 03.04.2017, 11:24, "Николаев Алексей" :
>>
>> Add logs. Thx!
>>
>>
>> 02.04.2017, 16:19, "Liron Aravot" :
>>
>> Hi Alexey,
>> can you please attach the engine/vdsm logs?
>>
>> thanks.
>>
>> On Fri, Mar 31, 2017 at 11:08 AM, Николаев Алексей <
>> alexeynikolaev.p...@yandex.ru> wrote:
>>
>> Hi, community!
>>
>> I'm try using ISCSI DATA DOMAIN with oVirt 4.1.1.6-1 and oVirt Node 4.1.1.
>> But get this error while adding data domain.
>>
>> Error while executing action New SAN Storage Domain: Cannot deactivate
>> Logical Volume
>>
>>
>> 2017-03-31 10:47:45,099+03 ERROR [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.CreateStorageDomainVDSCommand] (default task-41) [717af17f]
>> Command 'CreateStorageDomainVDSCommand(HostName = node169-07.,
>> CreateStorageDomainVDSCommandParameters:{runAsync='true',
>> hostId='ca177a14-56ef-4736-a0a9-ab9dc2a8eb90',
>> storageDomain='StorageDomainStatic:{name='data1', id='56038842-2
>> fbe-4ada-96f1-c4b4e66fd0b7'}', 
>> args='sUG5rL-zqvF-DMox-uMK3-Xl91-ZiYw-k27C3B'})'
>> execution failed: VDSGenericException: VDSErrorException: Failed in
>> vdscommand to CreateStorageDomainVDS, error = Cannot deactivate Logical
>> Volume: ('General Storage Exception: (\'5 [] [\\\'  /dev/mapper/36001405
>> b7dd7b800e7049ecbf6830637: read failed after 0 of 4096 at 0:
>> Input/output error\\\', \\\'  /dev/mappe

Re: [ovirt-users] SKD4

[Yaniv Kaul]

On Thu, Apr 6, 2017 at 9:19 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

>
> Le 6 avr. 2017 à 20:06, Yaniv Kaul  a écrit :
>
>
>
> On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella <
> fabrice.bacche...@orange.fr> wrote:
>
>>
>> > Le 6 avr. 2017 à 16:12, Yaniv Kaul  a écrit :
>>
>> > Seriously though - perhaps you could borrow code from our Ansible
>> module? See[1].
>> >
>>
>> If the code already exists, why it's not already in the sdk instead of
>> having to dig throw external code ?
>
>
> It's a good question, which I've asked as well in the past. The reason is
> that it's above the SDK, not part of the SDK.
> But that doesn't matter - we really ought to have a module/library on top
> of the SDK,  that can be shared.
> For example, between ovirt-system-tests, Ansible, oVirtBackup[1] and
> several others who write on top of our SDK.
> We just never got to generalise it enough and split it. You are welcome to
> begin this work - I believe it has value.
> (It's also a good Google Summer of Code project - I'll see if I can update
> that page on ovirt.org).
>
>
> I have already started it for sdk3, I will need to restart if almost from
> scratch to sdk4: https://github.com/fbacchella/ovirtcmd and need to right
> a lot of very basic code.
>

Well, if you are talking about a CLI, I've started one for SDK4[1]. It
exactly suffers from what I describe above - due to lack of a library on
top of the SDK I'm quite wastefully re-writing what others (for example,
the Ansible module) have probably done already.
But other than that, and the fact I stopped the effort, it's a very cool
CLI, I encourage you to check it out and perhaps pick it and do a better
job than me.

Y.
[1] https://github.com/mykaul/ovirt4cli
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] New SAN Storage Domain: Cannot deactivate Logical Volume

[Liron Aravot]

Thanks Alexey,
Nir/Adam/Raz - any initial thoughts about that? have you encountered that
issue before?

Regards,
Liron

On Wed, Apr 5, 2017 at 12:21 PM, Николаев Алексей <
alexeynikolaev.p...@yandex.ru> wrote:

> Hi Liron,
>
> Well, this error appear on freshly installed oVirt hosted engine 4.1.1.6-1
> with oVirt Node NG 4.1.
> There is no engine major version upgrade.
> Node NG was updated from 4.1.0 to 4.1.1 by the ovirt-node-ng-image* pkgs.
>
> vdsm version is:
>
> Installed Packages
> Name: vdsm
> Arch: x86_64
> Version : 4.19.10
> Release : 1.el7.centos
> --
>
> I also install oVirt 3.6 hosted engine on another server (CentOS 7.2
> minimal, not updated to 7.3) and add the some ISCSI target as the data
> domain. This work OK.
> After I update engine from 3.6 to 4.1. ISCSI data domain is OK after
> update. Another ISCSI targets was added as data domain without errors.
>
> vdsm version is:
>
> Installed Packages
> Name: vdsm
> Arch: noarch
> Version : 4.17.32
> Release : 0.el7.centos
>
> 04.04.2017, 16:48, "Liron Aravot" :
>
> Hi Alexey,
>
> Looking in your logs - it indeed look weird, the vg is created seconds
> later we fail to get it when attempting to create the domain.
>
> Did you upgrade/downgraded only the engine version or the vdsm version as
> well?
>
> 2017-04-03 11:16:39,595+0300 INFO  (jsonrpc/4) [dispatcher] Run and
> protect: createVG(vgname=u'3050e121-83b5-474e-943f-6dc52af38a17',
> devlist=[u'3600140505d11d22e61f46a6ba4a
> 7bdc7'], force=False, options=None) (logUtils:51)
>
>
> output error', '  /dev/mapper/36001405b7dd7b800e7049ecbf6830637: read
> failed after 0 of 4096 at 4294967230464: Input/output error', '
>  /dev/mapper/36001405b7dd7b800e7049ecbf
> 6830637: read failed after 0 of 4096 at 4294967287808: Input/output
> error', '  WARNING: Error counts reached a limit of 3. Device /dev/mapper/
> 36001405b7dd7b800e7049ecbf68306
> 37 was disabled', '  Failed to find physical volume "/dev/mapper/
> 3600140505d11d22e61f46a6ba4a7bdc7".'] (lvm:323)
> 2017-04-03 11:16:38,832+0300 WARN  (jsonrpc/5) [storage.HSM] getPV failed
> for guid: 3600140505d11d22e61f46a6ba4a7bdc7 (hsm:1973)
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/hsm.py", line 1970, in _getDeviceList
> pv = lvm.getPV(guid)
>   File "/usr/share/vdsm/storage/lvm.py", line 853, in getPV
> raise se.((pvName,))
>
>
> On Tue, Apr 4, 2017 at 3:33 PM, Николаев Алексей <
> alexeynikolaev.p...@yandex.ru> wrote:
>
> The last I was update oVirt oVirt 3.6.7.5-1 to oVirt 4.1.1.6-1. Main
> ISCSI datadomain is OK. Another one ISCSI datadomain was added
> successfully.
>
> The problem are only with freshly installed oVirt 4.1.1.6-1.
>
> Added logs after update ovirt and add new ISCSI datadomains.
>
> 03.04.2017, 17:26, "Николаев Алексей" :
>
> Also I test again ISCSI TARGET with oVirt 3.6.7.5-1 and CentOS 7.2.1511
> host. ISCSI data domain was added succesfully. "the truth is out there".
> Add logs.
>
> 03.04.2017, 11:24, "Николаев Алексей" :
>
> Add logs. Thx!
>
>
> 02.04.2017, 16:19, "Liron Aravot" :
>
> Hi Alexey,
> can you please attach the engine/vdsm logs?
>
> thanks.
>
> On Fri, Mar 31, 2017 at 11:08 AM, Николаев Алексей <
> alexeynikolaev.p...@yandex.ru> wrote:
>
> Hi, community!
>
> I'm try using ISCSI DATA DOMAIN with oVirt 4.1.1.6-1 and oVirt Node 4.1.1.
> But get this error while adding data domain.
>
> Error while executing action New SAN Storage Domain: Cannot deactivate
> Logical Volume
>
>
> 2017-03-31 10:47:45,099+03 ERROR [org.ovirt.engine.core.
> vdsbroker.vdsbroker.CreateStorageDomainVDSCommand] (default task-41)
> [717af17f] Command 'CreateStorageDomainVDSCommand(HostName = node169-07.,
> CreateStorageDomainVDSCommandParameters:{runAsync='true',
> hostId='ca177a14-56ef-4736-a0a9-ab9dc2a8eb90', storageDomain='
> StorageDomainStatic:{name='data1', 
> id='56038842-2fbe-4ada-96f1-c4b4e66fd0b7'}',
> args='sUG5rL-zqvF-DMox-uMK3-Xl91-ZiYw-k27C3B'})' execution failed:
> VDSGenericException: VDSErrorException: Failed in vdscommand to
> CreateStorageDomainVDS, error = Cannot deactivate Logical Volume: ('General
> Storage Exception: (\'5 [] [\\\'  /dev/mapper/36001405b7dd7b800e7049ecbf
> 6830637: read failed after 0 of 4096 at 0: Input/output error\\\', \\\'
> /dev/mapper/36001405b7dd7b800e7049ecbf6830637: read failed after 0 of
> 4096 at 4294967230464: Input/output error\\\', \\\'  /dev/mapper/36001405
> b7dd7b800e7049ecbf6830637: read failed after 0 of 4096 at 4294967287808:
> Input/output error\\\', \\\'  WARNING: Error counts reached a limit of 3.
> Device /dev/mapper/36001405b7dd7b800e7049ecbf6830637 was disabled\\\',
> \\\'  WARNING: Error counts reached a limit of 3. Device /dev/mapper/
> 36001405b7dd7b800e7049ecbf6830637 was disabled\\\', \\\'  Volume group "
> 56038842-2fbe-4ada-96f1-c4b4e66fd0b7" not found\\\', \\\'  Cannot process
> volume group 56038842-2fbe-4ada-96f1-c4b4e66fd0b7\\\']\\n5603884

Re: [ovirt-users] for some reason ovirtnode creates unecessary vg and lvs

[Liron Aravot]

On Wed, Apr 5, 2017 at 3:16 PM, Yaniv Kaul  wrote:

>
>
> On Sun, Apr 2, 2017 at 9:15 PM, martin chamambo 
> wrote:
>
>> I managed to configure the mail iscsi domain for my ovirt 4.1 engine and
>> node , it connects to the storage initially and initialises the data center
>> ,but after rebooting the node and engine , it creates unecessary vg and lvs
>> like below
>>
>> 280246d3-ac7b-44ff-8c03-dc2bcb9edb70 d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a- 128.00m
>>   2d57ab88-16e4-4007-9047-55fc4a35b534 d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a- 128.00m
>>   ids  d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a- 128.00m
>>   inboxd5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a- 128.00m
>>   leases   d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a-   2.00g
>>   master   d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a-   1.00g
>>   metadata d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a- 512.00m
>>   outbox   d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a- 128.00m
>>   xleases  d5104206-5863-4f9d-9ea7-2b140c97d65f
>> -wi-a-   1.00g
>>
>> whats the cause of this
>>
>
> I'm not sure what is the problem? These LVs are the metadata LVs for a
> storage domain.
> Y.
>
>

As Yaniv wrote - those are LVs created by oVirt.
Is the node  currently in use in oVirt? if so, it should be connected to
your storage server and have those vg/lvs.

>
>> NB:mY ISCSI storage is on a centos 7 box
>>
>> ___
>> 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] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 20:06, Yaniv Kaul  a écrit :
> 
> 
> 
> On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella 
> mailto:fabrice.bacche...@orange.fr>> wrote:
> 
> > Le 6 avr. 2017 à 16:12, Yaniv Kaul  > > a écrit :
> 
> > Seriously though - perhaps you could borrow code from our Ansible module? 
> > See[1].
> >
> 
> If the code already exists, why it's not already in the sdk instead of having 
> to dig throw external code ?
> 
> It's a good question, which I've asked as well in the past. The reason is 
> that it's above the SDK, not part of the SDK.
> But that doesn't matter - we really ought to have a module/library on top of 
> the SDK,  that can be shared.
> For example, between ovirt-system-tests, Ansible, oVirtBackup[1] and several 
> others who write on top of our SDK.
> We just never got to generalise it enough and split it. You are welcome to 
> begin this work - I believe it has value.
> (It's also a good Google Summer of Code project - I'll see if I can update 
> that page on ovirt.org ).

I have already started it for sdk3, I will need to restart if almost from 
scratch to sdk4: https://github.com/fbacchella/ovirtcmd 
 and need to right a lot of very basic 
code.

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

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 17:21, Ondra Machacek  a écrit :
> 
> 
> 
> On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella 
> mailto:fabrice.bacche...@orange.fr>> wrote:
> Ho my good, in ovirtsdk.services.py , for every 
> service, there is a different method with a different name that return a 
> associated service, so it's not possible to have a generic like:
> 
> def  resolve(service, ...):
>   id = .
>   return service.service(id)
> 
> because the generic call service is used by something that take a path 
> argument. But why not a service_by_id(self, id) ?
> 
> I am not fully sure I understand what you are missing, but feel free to open
> the bug on Python SDK in bugzilla, we will be happy to improve the SDK.
>  

Done, with a first idea for what might be needed:

https://bugzilla.redhat.com/show_bug.cgi?id=1439879 




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

Re: [ovirt-users] SKD4

[Yaniv Kaul]

On Thu, Apr 6, 2017 at 5:30 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

>
> > Le 6 avr. 2017 à 16:12, Yaniv Kaul  a écrit :
>
> > Seriously though - perhaps you could borrow code from our Ansible
> module? See[1].
> >
>
> If the code already exists, why it's not already in the sdk instead of
> having to dig throw external code ?


It's a good question, which I've asked as well in the past. The reason is
that it's above the SDK, not part of the SDK.
But that doesn't matter - we really ought to have a module/library on top
of the SDK,  that can be shared.
For example, between ovirt-system-tests, Ansible, oVirtBackup[1] and
several others who write on top of our SDK.
We just never got to generalise it enough and split it. You are welcome to
begin this work - I believe it has value.
(It's also a good Google Summer of Code project - I'll see if I can update
that page on ovirt.org).

Y.

[1] https://github.com/wefixit-AT/oVirtBackup
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour

[Pavel Gashev]

I’d suggest to update it from http://thepax.gitlab.io/ovirt36/

-Original Message-
From: Chris Adams 
Date: Thursday, 6 April 2017 at 18:47
To: Pavel Gashev 
Cc: "users@ovirt.org" 
Subject: Re: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour

That version of vdsm doesn't seem to be in the ovirt-3.6 repos - where
would I get it?

My plan is to continue upgrading to 4.0 and then 4.1.  Does that version
(or newer) come from 4.0+?  If so, is it safe to upgrade to 4.0 with the
older vdsm, or should I update vdsm first (to eliminate this error)?

Thanks.


Once upon a time, Pavel Gashev  said:
> Chris,
> 
> Make sure you have vdsm >= 4.17.35 installed.
> 
> -Original Message-
> From:  on behalf of Chris Adams 
> Date: Thursday, 6 April 2017 at 16:29
> To: "users@ovirt.org" 
> Subject: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour
> 
> After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the
> following error every hour:
> 
> Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF
> data isn't updated on those OVF stores (Data Center Middle-Earth,
> Storage Domain equallogic).
> 
> Looking in the vdsm log on the SPM node, it looks like the problem is
> that an attempt was made to lvextend an LV to 2m, but the LV is already
> 128m, so the extend failed (not needed).  I've attached the log entries
> for that task.
> 
> Any suggestions, ideas how to fix, etc.?
> 
> -- 
> Chris Adams 
> 
> 

-- 
Chris Adams 


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

[ovirt-users] mount glusterfs from 127.0.0.1

[/dev/null]

Hello all together,

having a three node oVirt cluster for virtualization and gluster, each node 
providing
bricks for a replica 3 volume, I would like to mount the volume from 127.0.0.1 
to
distribute i/o and to have a better failover situation.

This leads to a volume having the same address in oVirt althoght it is 
addressed on
different hosts.

Is this common, supported, relyable and recommended?

Thanks in advance!

/dev/null

--
Diese Nachricht wurde auf Viren und andere gef�hrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
For all your IT requirements visit: http://www.transtec.co.uk

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

Re: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour

[Chris Adams]

That version of vdsm doesn't seem to be in the ovirt-3.6 repos - where
would I get it?

My plan is to continue upgrading to 4.0 and then 4.1.  Does that version
(or newer) come from 4.0+?  If so, is it safe to upgrade to 4.0 with the
older vdsm, or should I update vdsm first (to eliminate this error)?

Thanks.


Once upon a time, Pavel Gashev  said:
> Chris,
> 
> Make sure you have vdsm >= 4.17.35 installed.
> 
> -Original Message-
> From:  on behalf of Chris Adams 
> Date: Thursday, 6 April 2017 at 16:29
> To: "users@ovirt.org" 
> Subject: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour
> 
> After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the
> following error every hour:
> 
> Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF
> data isn't updated on those OVF stores (Data Center Middle-Earth,
> Storage Domain equallogic).
> 
> Looking in the vdsm log on the SPM node, it looks like the problem is
> that an attempt was made to lvextend an LV to 2m, but the LV is already
> 128m, so the extend failed (not needed).  I've attached the log entries
> for that task.
> 
> Any suggestions, ideas how to fix, etc.?
> 
> -- 
> Chris Adams 
> 
> 

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

Re: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour

[Pavel Gashev]

Chris,

Make sure you have vdsm >= 4.17.35 installed.

-Original Message-
From:  on behalf of Chris Adams 
Date: Thursday, 6 April 2017 at 16:29
To: "users@ovirt.org" 
Subject: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour

After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the
following error every hour:

Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF
data isn't updated on those OVF stores (Data Center Middle-Earth,
Storage Domain equallogic).

Looking in the vdsm log on the SPM node, it looks like the problem is
that an attempt was made to lvextend an LV to 2m, but the LV is already
128m, so the extend failed (not needed).  I've attached the log entries
for that task.

Any suggestions, ideas how to fix, etc.?

-- 
Chris Adams 


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

Re: [ovirt-users] SKD4

[Ondra Machacek]

On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

> Ho my good, in ovirtsdk.services.py, for every service, there is a
> different method with a different name that return a associated service, so
> it's not possible to have a generic like:
>
> def  resolve(service, ...):
> id = .
> return service.service(id)
>
> because the generic call service is used by something that take a path
> argument. But why not a service_by_id(self, id) ?
>

I am not fully sure I understand what you are missing, but feel free to open
the bug on Python SDK in bugzilla, we will be happy to improve the SDK.


>
> grep 'def .*_service.self, id.:' site-packages/ovirtsdk4/services.py
> def vm_service(self, id):
> def group_service(self, id):
> def host_service(self, id):
> def vm_service(self, id):
> def label_service(self, id):
> def label_service(self, id):
> def profile_service(self, id):
> def profile_service(self, id):
> def network_service(self, id):
> def permission_service(self, id):
> def role_service(self, id):
> def tag_service(self, id):
> def profile_service(self, id):
> def storage_domain_service(self, id):
> def balance_service(self, id):
> def bookmark_service(self, id):
> def level_service(self, id):
> def cluster_service(self, id):
> def profile_service(self, id):
> def data_center_service(self, id):
> def attachment_service(self, id):
> def disk_profile_service(self, id):
> def snapshot_service(self, id):
> def disk_service(self, id):
> def group_service(self, id):
> def user_service(self, id):
> def domain_service(self, id):
> def event_service(self, id):
> def resource_service(self, id):
> def host_service(self, id):
> def group_service(self, id):
> def provider_service(self, id):
> def host_service(self, id):
> def certificate_service(self, id):
> def agent_service(self, id):
> def file_service(self, id):
> def filter_service(self, id):
> def brick_service(self, id):
> def hook_service(self, id):
> def volume_service(self, id):
> def group_service(self, id):
> def device_service(self, id):
> def hook_service(self, id):
> def nic_service(self, id):
> def node_service(self, id):
> def storage_service(self, id):
> def host_service(self, id):
> def icon_service(self, id):
> def image_transfer_service(self, id):
> def image_service(self, id):
> def console_service(self, id):
> def nic_service(self, id):
> def watchdog_service(self, id):
> def instance_type_service(self, id):
> def iscsi_bond_service(self, id):
> def job_service(self, id):
> def katello_erratum_service(self, id):
> def mac_pool_service(self, id):
> def attachment_service(self, id):
> def network_filter_service(self, id):
> def label_service(self, id):
> def network_service(self, id):
> def provider_service(self, id):
> def image_service(self, id):
> def provider_service(self, id):
> def network_service(self, id):
> def subnet_service(self, id):
> def key_service(self, id):
> def provider_service(self, id):
> def type_service(self, id):
> def operating_system_service(self, id):
> def permit_service(self, id):
> def qos_service(self, id):
> def limit_service(self, id):
> def limit_service(self, id):
> def quota_service(self, id):
> def role_service(self, id):
> def policy_service(self, id):
> def unit_service(self, id):
> def cdrom_service(self, id):
> def disk_service(self, id):
> def nic_service(self, id):
> def snapshot_service(self, id):
> def key_service(self, id):
> def statistic_service(self, id):
> def step_service(self, id):
> def disk_service(self, id):
> def connection_service(self, id):
> def template_service(self, id):
> def attachment_service(self, id):
> def vm_service(self, id):
> def storage_domain_service(self, id):
> def storage_connection_extension_service(self, id):
> def storage_connection_service(self, id):
> def permission_service(self, id):
> def tag_service(self, id):
> def cdrom_service(self, id):
> def attachment_service(self, id):
> def disk_service(self, id):
> def console_service(self, id):
> def nic_service(self, id):
> def watchdog_service(self, id):
> def template_service(self, id):
> def unmanaged_network_service(self, id):
> def user_service(self, id):
> def network_service(self, id):
> def application_service(self, id):
> def cdrom_service(self, id):
> def disk_service(self, id):
> def console_service(self, id):
> def device_service(self, id):
> def nic_service(self, id):
> def node_service(self, id):
> def pool_service(self, id):
> def reported_device_service(self, id):
> def session_service(self, id):
> def watchd

Re: [ovirt-users] SKD4

[Barak Korren]

On 6 April 2017 at 18:00, Fabrice Bacchella  wrote:
> Ho my good, in ovirtsdk.services.py, for every service, there is a different
> method with a different name that return a associated service, so it's not
> possible to have a generic like:
>
> def  resolve(service, ...):
> id = .
> return service.service(id)
>
> because the generic call service is used by something that take a path
> argument. But why not a service_by_id(self, id) ?
>
I think you can use getattr to get a generic call like you want:

With your example code:

def resolve(service, ...):
id = .
return getattr(services, service + '_service')(id)




-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

Ho my good, in ovirtsdk.services.py, for every service, there is a different 
method with a different name that return a associated service, so it's not 
possible to have a generic like:

def  resolve(service, ...):
id = .
return service.service(id)

because the generic call service is used by something that take a path 
argument. But why not a service_by_id(self, id) ?

grep 'def .*_service.self, id.:' site-packages/ovirtsdk4/services.py
def vm_service(self, id):
def group_service(self, id):
def host_service(self, id):
def vm_service(self, id):
def label_service(self, id):
def label_service(self, id):
def profile_service(self, id):
def profile_service(self, id):
def network_service(self, id):
def permission_service(self, id):
def role_service(self, id):
def tag_service(self, id):
def profile_service(self, id):
def storage_domain_service(self, id):
def balance_service(self, id):
def bookmark_service(self, id):
def level_service(self, id):
def cluster_service(self, id):
def profile_service(self, id):
def data_center_service(self, id):
def attachment_service(self, id):
def disk_profile_service(self, id):
def snapshot_service(self, id):
def disk_service(self, id):
def group_service(self, id):
def user_service(self, id):
def domain_service(self, id):
def event_service(self, id):
def resource_service(self, id):
def host_service(self, id):
def group_service(self, id):
def provider_service(self, id):
def host_service(self, id):
def certificate_service(self, id):
def agent_service(self, id):
def file_service(self, id):
def filter_service(self, id):
def brick_service(self, id):
def hook_service(self, id):
def volume_service(self, id):
def group_service(self, id):
def device_service(self, id):
def hook_service(self, id):
def nic_service(self, id):
def node_service(self, id):
def storage_service(self, id):
def host_service(self, id):
def icon_service(self, id):
def image_transfer_service(self, id):
def image_service(self, id):
def console_service(self, id):
def nic_service(self, id):
def watchdog_service(self, id):
def instance_type_service(self, id):
def iscsi_bond_service(self, id):
def job_service(self, id):
def katello_erratum_service(self, id):
def mac_pool_service(self, id):
def attachment_service(self, id):
def network_filter_service(self, id):
def label_service(self, id):
def network_service(self, id):
def provider_service(self, id):
def image_service(self, id):
def provider_service(self, id):
def network_service(self, id):
def subnet_service(self, id):
def key_service(self, id):
def provider_service(self, id):
def type_service(self, id):
def operating_system_service(self, id):
def permit_service(self, id):
def qos_service(self, id):
def limit_service(self, id):
def limit_service(self, id):
def quota_service(self, id):
def role_service(self, id):
def policy_service(self, id):
def unit_service(self, id):
def cdrom_service(self, id):
def disk_service(self, id):
def nic_service(self, id):
def snapshot_service(self, id):
def key_service(self, id):
def statistic_service(self, id):
def step_service(self, id):
def disk_service(self, id):
def connection_service(self, id):
def template_service(self, id):
def attachment_service(self, id):
def vm_service(self, id):
def storage_domain_service(self, id):
def storage_connection_extension_service(self, id):
def storage_connection_service(self, id):
def permission_service(self, id):
def tag_service(self, id):
def cdrom_service(self, id):
def attachment_service(self, id):
def disk_service(self, id):
def console_service(self, id):
def nic_service(self, id):
def watchdog_service(self, id):
def template_service(self, id):
def unmanaged_network_service(self, id):
def user_service(self, id):
def network_service(self, id):
def application_service(self, id):
def cdrom_service(self, id):
def disk_service(self, id):
def console_service(self, id):
def device_service(self, id):
def nic_service(self, id):
def node_service(self, id):
def pool_service(self, id):
def reported_device_service(self, id):
def session_service(self, id):
def watchdog_service(self, id):
def vm_service(self, id):
def profile_service(self, id):
def weight_service(self, id):
def katello_erratum_service(self, id):





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

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 16:12, Yaniv Kaul  a écrit :
> 
> 
> 
> On Thu, Apr 6, 2017 at 4:49 PM, Fabrice Bacchella 
> mailto:fabrice.bacche...@orange.fr>> wrote:
> 
>> Le 6 avr. 2017 à 15:32, Yaniv Kaul > > a écrit :
>> 
>> 
>> 
>> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella 
>> mailto:fabrice.bacche...@orange.fr>> wrote:
>> Yes I'm starting to understand that thinking about migrating code is 
>> pointless.
>> 
>> The old skd3 code is just good to be thrown away. There is no hope thinking 
>> about "migrating code". And as it's just a thin layer around REST calls, 
>> it's up to us to try to make something usable around that. So I expect a lot 
>> of sweat and tears to adapt my existing code.
>> 
>> Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind 
>> the v4 API philosophy, it's quite easy to write to (at least in Python).
> 
> An example of code that I'm unhappy to write and that a good sdk should have 
> provided:
> 
> searchfilter = "%s=%s" % (type, value)
> vm = vms_service.list(search= searchfilter)[0]
> 
> instead of :
> vms_service.list(search= {type: value})[0]
> 
> or even better:
> vms_service.get(**{type: value})
> 
> 
> Yes, I see what you mean. 100% more LoC are currently needed vs. your idea ;-)

It's not about the number of LoC, it's about legibility, having code that says 
what's it's doing and doing what it says.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 16:12, Yaniv Kaul  a écrit :

> Seriously though - perhaps you could borrow code from our Ansible module? 
> See[1].
> 

If the code already exists, why it's not already in the sdk instead of having 
to dig throw external code ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SKD4

[Yaniv Kaul]

On Thu, Apr 6, 2017 at 5:02 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

>
> > Le 6 avr. 2017 à 15:47, Yaniv Kaul  a écrit :
> >
> >
>
> > Perhaps in your case. Here[1] is an example of the ovirt system tests,
> which were only partially converted (work in progress...) to v4 API.
>
> yes that really related to my use case.
>
> Another problem that I have with lack of documentation, that REST API
> documentation or samples don't provide.
>
> In python, what does vms_service.list(search='name=NotExistingVM') will
> return ? It's not stated in the REST documentation, but it's even worst in
> python.
>

You could file a bug for documentation, or better yet, contribute a patch
to it.
A patch to a basic example for negative cases would be very helpful as well.
An example of a patch[1] for the SDK examples from someone who found it is
lacking.

Let me know if I can help you with contributing the example. Start here[2]
TIA,
Y.

[1] https://gerrit.ovirt.org/#/c/75076/
[2] http://www.ovirt.org/develop/dev-process/working-with-gerrit/


> It could throw an exception, return None, or return an empty list ?
>
> If I'm using a sdk instead of direct HTTP call is not to be bothered my
> xml versus json representation, but instead find an answer to that kind of
> questions easily.
> In the sample I just find:
>
> vm = vms_service.list(search='name=myvm')[0]
>
> Not really helpfull.
>
> Is there any documentation about python exception thrown ? Or must I dig
> throw all the examples ?
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SKD4

[Yaniv Kaul]

On Thu, Apr 6, 2017 at 4:49 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

>
> Le 6 avr. 2017 à 15:32, Yaniv Kaul  a écrit :
>
>
>
> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella <
> fabrice.bacche...@orange.fr> wrote:
>
>> Yes I'm starting to understand that thinking about migrating code is
>> pointless.
>>
>> The old skd3 code is just good to be thrown away. There is no hope
>> thinking about "migrating code". And as it's just a thin layer around REST
>> calls, it's up to us to try to make something usable around that. So I
>> expect a lot of sweat and tears to adapt my existing code.
>>
>
> Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind
> the v4 API philosophy, it's quite easy to write to (at least in Python).
>
>
> An example of code that I'm unhappy to write and that a good sdk should
> have provided:
>
> searchfilter = "%s=%s" % (type, value)
> vm = vms_service.list(search= searchfilter)[0]
>
> instead of :
> vms_service.list(search= {type: value})[0]
>
> or even better:
> vms_service.get(**{type: value})
>


Yes, I see what you mean. 100% more LoC are currently needed vs. your idea
;-)

Seriously though - perhaps you could borrow code from our Ansible module?
See[1].

Y.

[1]
https://github.com/ansible/ansible/blob/699df5824d36dab5cb46b3f7c63e8992bd778b27/lib/ansible/module_utils/ovirt.py#L220
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 15:47, Yaniv Kaul  a écrit :
> 
> 

> Perhaps in your case. Here[1] is an example of the ovirt system tests, which 
> were only partially converted (work in progress...) to v4 API.

yes that really related to my use case.

Another problem that I have with lack of documentation, that REST API 
documentation or samples don't provide.

In python, what does vms_service.list(search='name=NotExistingVM') will return 
? It's not stated in the REST documentation, but it's even worst in python.

It could throw an exception, return None, or return an empty list ?

If I'm using a sdk instead of direct HTTP call is not to be bothered my xml 
versus json representation, but instead find an answer to that kind of 
questions easily.
In the sample I just find:

vm = vms_service.list(search='name=myvm')[0]

Not really helpfull.

Is there any documentation about python exception thrown ? Or must I dig throw 
all the examples ?


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

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 15:32, Yaniv Kaul  a écrit :
> 
> 
> 
> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella 
> mailto:fabrice.bacche...@orange.fr>> wrote:
> Yes I'm starting to understand that thinking about migrating code is 
> pointless.
> 
> The old skd3 code is just good to be thrown away. There is no hope thinking 
> about "migrating code". And as it's just a thin layer around REST calls, it's 
> up to us to try to make something usable around that. So I expect a lot of 
> sweat and tears to adapt my existing code.
> 
> Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind 
> the v4 API philosophy, it's quite easy to write to (at least in Python).

An example of code that I'm unhappy to write and that a good sdk should have 
provided:

searchfilter = "%s=%s" % (type, value)
vm = vms_service.list(search= searchfilter)[0]

instead of :
vms_service.list(search= {type: value})[0]

or even better:
vms_service.get(**{type: value})



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

Re: [ovirt-users] SKD4

[Yaniv Kaul]

On Thu, Apr 6, 2017 at 4:41 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

>
> Le 6 avr. 2017 à 15:32, Yaniv Kaul  a écrit :
>
>
>
> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella <
> fabrice.bacche...@orange.fr> wrote:
>
>> Yes I'm starting to understand that thinking about migrating code is
>> pointless.
>>
>> The old skd3 code is just good to be thrown away. There is no hope
>> thinking about "migrating code". And as it's just a thin layer around REST
>> calls, it's up to us to try to make something usable around that. So I
>> expect a lot of sweat and tears to adapt my existing code.
>>
>
> Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind
> the v4 API philosophy, it's quite easy to write to (at least in Python).
>
>
> Easy to write code that a well though sdk should have provided.
>

I'd like to believe our v4 SDKs are. They fix several inconsistencies we've
had with v3.


>
> Note that right now you can mix between v3 and v4, so you can migrate
> slowly, function by function.
>
>
> That's a possible but almost as complicated as rewrite everything in my
> case.
>

Perhaps in your case. Here[1] is an example of the ovirt system tests,
which were only partially converted (work in progress...) to v4 API.

HTH,
Y.

[1]
https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blob;f=basic-suite-master/test-scenarios/002_bootstrap.py;h=c0e71df23f17335d59d9d37fcd4c833be6372c69;hb=HEAD#l109


>
>
> Another option that you can consider, if you are re-writing, is automation
> via Ansible.
> See https://github.com/ansible/ansible-modules-extras/tree/
> devel/cloud/ovirt
>
>
> A lot of people don't use ansible or use concurrent tools. So no that's
> not an option.
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

> Le 6 avr. 2017 à 15:32, Yaniv Kaul  a écrit :
> 
> 
> 
> On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella 
> mailto:fabrice.bacche...@orange.fr>> wrote:
> Yes I'm starting to understand that thinking about migrating code is 
> pointless.
> 
> The old skd3 code is just good to be thrown away. There is no hope thinking 
> about "migrating code". And as it's just a thin layer around REST calls, it's 
> up to us to try to make something usable around that. So I expect a lot of 
> sweat and tears to adapt my existing code.
> 
> Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind 
> the v4 API philosophy, it's quite easy to write to (at least in Python).

Easy to write code that a well though sdk should have provided.

> Note that right now you can mix between v3 and v4, so you can migrate slowly, 
> function by function.

That's a possible but almost as complicated as rewrite everything in my case.

> 
> 
> Another option that you can consider, if you are re-writing, is automation 
> via Ansible. 
> See https://github.com/ansible/ansible-modules-extras/tree/devel/cloud/ovirt 
>  

A lot of people don't use ansible or use concurrent tools. So no that's not an 
option.

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

Re: [ovirt-users] oVirt Roadmap

[Nathanaël Blanchet]

https://www.mail-archive.com/users@ovirt.org/msg40244.html


Le 06/04/2017 à 15:29, Yaniv Kaul a écrit :

There isn't any yet. We are still trying to figure it out.
I would say that the general theme would be smaller releases in 
shorter cycles, with emphasis on higher overall quality, ease of use 
(UI improvements - look & feel and functionality, continue to improve 
documentation, especially around API, SDKs and examples to them) and 
smoother upgrade experience.


Y.


On Thu, Apr 6, 2017 at 4:04 PM, John Rushe > wrote:


Hi,

Does anyone know if there is a roadmap for oVirt 4.x published
online any where? I can't seem to be able to find one for 4.x only
for the 3.x releases.

Regards

John

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus 

___
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


--
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] SKD4

[Yaniv Kaul]

On Thu, Apr 6, 2017 at 3:58 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

> Yes I'm starting to understand that thinking about migrating code is
> pointless.
>
> The old skd3 code is just good to be thrown away. There is no hope
> thinking about "migrating code". And as it's just a thin layer around REST
> calls, it's up to us to try to make something usable around that. So I
> expect a lot of sweat and tears to adapt my existing code.
>

Well, yes and no. Yes, it's not smooth, but once you 'get' the idea behind
the v4 API philosophy, it's quite easy to write to (at least in Python).
Note that right now you can mix between v3 and v4, so you can migrate
slowly, function by function.

Another option that you can consider, if you are re-writing, is automation
via Ansible.
See https://github.com/ansible/ansible-modules-extras/tree/devel/cloud/ovirt


Y.


>
> Le 6 avr. 2017 à 14:23, Yaniv Kaul  a écrit :
>
> There is documentation online (and within the project).
> See http://ovirt.github.io/ovirt-engine-api-model/master/
>
> There are tens of examples in the RPM (and online).
> See https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples
>
> HTH,
> Y.
>
> On Thu, Apr 6, 2017 at 12:22 PM, Fabrice Bacchella <
> fabrice.bacche...@orange.fr> wrote:
>
>> I trying to migrate my python code from sdk3 to sdk4, is there any
>> migration doc, documentation help about that ? Even google is unable to
>> find anything relevant about that.
>>
>> ___
>> 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] oVirt Roadmap

[Yaniv Kaul]

There isn't any yet. We are still trying to figure it out.
I would say that the general theme would be smaller releases in shorter
cycles, with emphasis on higher overall quality, ease of use (UI
improvements - look & feel and functionality, continue to improve
documentation, especially around API, SDKs and examples to them) and
smoother upgrade experience.

Y.


On Thu, Apr 6, 2017 at 4:04 PM, John Rushe  wrote:

> Hi,
>
> Does anyone know if there is a roadmap for oVirt 4.x published online any
> where? I can't seem to be able to find one for 4.x only for the 3.x
> releases.
>
> Regards
>
> John
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> ___
> 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] After 3.5->3.6 upgrade, OVF update error every hour

[Chris Adams]

After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the
following error every hour:

Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF
data isn't updated on those OVF stores (Data Center Middle-Earth,
Storage Domain equallogic).

Looking in the vdsm log on the SPM node, it looks like the problem is
that an attempt was made to lvextend an LV to 2m, but the LV is already
128m, so the extend failed (not needed).  I've attached the log entries
for that task.

Any suggestions, ideas how to fix, etc.?

-- 
Chris Adams 
Thread-735868::DEBUG::2017-04-06 
08:12:26,651::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::moving from state init -> state 
preparing
Thread-735868::DEBUG::2017-04-06 
08:12:26,673::task::752::Storage.TaskManager.Task::(_save) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::_save: orig 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
 temp 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac.temp
Thread-735868::DEBUG::2017-04-06 
08:12:26,678::taskManager::78::Storage.TaskManager::(scheduleJob) scheduled job 
downloadImageFromStream for task c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac 
Thread-735868::DEBUG::2017-04-06 
08:12:26,678::task::1183::Storage.TaskManager.Task::(prepare) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::Prepare: 1 jobs exist, move to 
acquiring
Thread-735868::DEBUG::2017-04-06 
08:12:26,679::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::moving from state preparing -> 
state acquiring
Thread-735868::DEBUG::2017-04-06 
08:12:26,680::task::752::Storage.TaskManager.Task::(_save) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::_save: orig 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
 temp 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac.temp
Thread-735868::DEBUG::2017-04-06 
08:12:26,686::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::moving from state acquiring -> 
state queued
Thread-735868::DEBUG::2017-04-06 
08:12:26,686::task::752::Storage.TaskManager.Task::(_save) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::_save: orig 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
 temp 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac.temp
Thread-735868::DEBUG::2017-04-06 
08:12:26,693::taskManager::56::Storage.TaskManager::(_queueTask) queuing task: 
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac::DEBUG::2017-04-06 
08:12:26,693::threadPool::194::Storage.ThreadPool.WorkerThread::(_processNextTask)
 Task: c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac running: > with: None
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac::DEBUG::2017-04-06 
08:12:26,693::task::1200::Storage.TaskManager.Task::(commit) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::committing task: 
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac::DEBUG::2017-04-06 
08:12:26,694::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::moving from state queued -> state 
running
Thread-735868::DEBUG::2017-04-06 
08:12:26,694::taskManager::64::Storage.TaskManager::(_queueTask) task queued: 
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
Thread-735868::DEBUG::2017-04-06 
08:12:26,694::task::1188::Storage.TaskManager.Task::(prepare) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::returning
Thread-735868::DEBUG::2017-04-06 
08:12:26,694::task::993::Storage.TaskManager.Task::(_decref) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::ref 1 aborting False
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac::DEBUG::2017-04-06 
08:12:26,695::task::752::Storage.TaskManager.Task::(_save) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::_save: orig 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac
 temp 
/rhev/data-center/0002-0002-0002-0002-0336/mastersd/master/tasks/c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac.temp
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac::DEBUG::2017-04-06 
08:12:26,701::task::905::Storage.TaskManager.Task::(_runJobs) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::Task.run: running job 0: 
downloadImageFromStream: > (args: ({'length': 1136640, 
'fileObj': }, , '2c2e3b6c-7161-45c5-ae80-3639ab565961', 
'ce8647c6-f936-4633-8a7b-e7dcb45d8ebb', '96be6a82-ab6a-4e38-b184-6dc65e57847c') 
kwargs: {})
c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac::DEBUG::2017-04-06 
08:12:26,702::task::329::Storage.TaskManager.Task::(run) 
Task=`c08b90ca-32dd-4c88-9f5c-7b2be5bf66ac`::Job.run: running 
downloadImageFromStream: > (args: ({'length': 1136640, 
'fileObj': }, , '2c2

[ovirt-users] oVirt Roadmap

[John Rushe]

Hi,

Does anyone know if there is a roadmap for oVirt 4.x published online 
any where? I can't seem to be able to find one for 4.x only for the 3.x 
releases.


Regards

John

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

Re: [ovirt-users] SKD4

[Fabrice Bacchella]

Yes I'm starting to understand that thinking about migrating code is pointless.

The old skd3 code is just good to be thrown away. There is no hope thinking 
about "migrating code". And as it's just a thin layer around REST calls, it's 
up to us to try to make something usable around that. So I expect a lot of 
sweat and tears to adapt my existing code.


> Le 6 avr. 2017 à 14:23, Yaniv Kaul  a écrit :
> 
> There is documentation online (and within the project).
> See http://ovirt.github.io/ovirt-engine-api-model/master/ 
> 
> 
> There are tens of examples in the RPM (and online).
> See https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples 
> 
> 
> HTH,
> Y.
> 
> On Thu, Apr 6, 2017 at 12:22 PM, Fabrice Bacchella 
> mailto:fabrice.bacche...@orange.fr>> wrote:
> I trying to migrate my python code from sdk3 to sdk4, is there any migration 
> doc, documentation help about that ? Even google is unable to find anything 
> relevant about that.
> 
> ___
> 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] Problem Ovirt 4.1

[Fred Rolland]

Hi,

What do you mean by it is not possible ? Glance is still supported as an
external provider in 4.1.
Can you explain what you are trying to do ?

Thanks,

Fred

On Wed, Apr 5, 2017 at 9:21 PM, eric stam  wrote:

> On my Ovirt 4.1 environment, is is not possible anymore to import images
> from "external providers". In previous versions, it was possible.
> Is this a bug, or is there something I have to do to get this working
> again.
> I starten with a previous version of Overt 4 and in that version it was
> working fine.
>
> Regards,
> Eric
>
>
> ___
> 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] mapping shell fencing opions with gui ones for ipmilan agent

[Gianluca Cecchi]

On Thu, Apr 6, 2017 at 10:27 AM, Gianluca Cecchi 
wrote:

> Hello,
> executing from host itself the following command it works
>
> [root@ov300 ~]# fence_ipmilan -P -a 10.10.193.103 -l fenceuser -A
> password -L operator -S /usr/local/bin/pwd_ov300.sh -o status
> Status: ON
> [root@ov300 ~]#
>
> But I'm unable to obtain successful test result in web admin fencing agent
> config window
>
> I set ip, user, password and ipmilan as agent, and then tried in options
>
> auth=password,privlvl=operator,lanplus=1
> and also
> auth=password,privlvl=operator,lanplus=on
>
> this the only host in cluster so it is the one used for testing by oVirt.
>
> Tipically on these same server in RHEL 6.x ClusterSuite I use this in
> cluster.conf and it works too:
>
> 
>  delay="20" ipaddr="10.10.193.107" lanplus="1" login="fenceuser"
> name="dracnode01" passwd_script="/usr/local/bin/pwd_dracnode01.sh"
> privlvl="operator"/>
>
> Any hint on correct mapping of parameters for oVirt?
> Thanks,
> Gianluca
>
>
>
>
Possibly the auth method is not to be inserted as option, because it is
implicit... The test succeeds with these parameters:

privlvl=operator,lanplus=on

I will further check the correct functionality.

BTW: in the bottom left of the power mgmt configuration window ther is a
link named "Fencing Options". Currently it sends me (not able to see if it
is a redirect..) to this link that is not related:

https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement

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

Re: [ovirt-users] SKD4

[Yaniv Kaul]

There is documentation online (and within the project).
See http://ovirt.github.io/ovirt-engine-api-model/master/

There are tens of examples in the RPM (and online).
See https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples

HTH,
Y.

On Thu, Apr 6, 2017 at 12:22 PM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:

> I trying to migrate my python code from sdk3 to sdk4, is there any
> migration doc, documentation help about that ? Even google is unable to
> find anything relevant about that.
>
> ___
> 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] Hosts Network Management

[Kai Wagner]

Hi all,

is it possible to set a comment at the beginning of a file for network
files -> something like don't touch this anymore please?

I want to configure my network stuff on the cli and not via the UI
because I failed now a few times.

Thx

Kai


-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 
(AG Nürnberg)




signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Problem Ovirt 4.1

[eric stam]

On my Ovirt 4.1 environment, is is not possible anymore to import images from 
"external providers". In previous versions, it was possible.
Is this a bug, or is there something I have to do to get this working again.
I starten with a previous version of Overt 4 and in that version it was working 
fine.

Regards,
Eric

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

[ovirt-users] Separating NFS network flow

[Alexis HAUSER]

Hi, 

Is there a way to separate the network flow from NFS ? I know it is possible to 
do it with VM, display, ovirtmgmt, iSCSI, but what about NFS ? Does it use 
ovirtmgmt ? 

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

Re: [ovirt-users] MAC Address is already in use; several of times before Nic/MAC is acceppetd

[Martin Mucha]

Hi,

you're the second (if I'm counting correctly) person able to reproduce
this. So far we do not know what is causing this, and all tests we made so
far cannot reproduce this. Previous unlucky user had problem, that he had
less available macs in MAC pool, than actual nics in system. This does not
answer the question how he was able to reach this situation, but he was
able to greatly reduce this issue via making MAC pool bigger.

You said, that you added extra pool. Which pool are you referring to? MAC
pool? VM pool? Please describe your environment and ideally provide us with
logs. How many VMs do you have in each VM pool? How many vm_interfaces do
you have in your system in total? How many MAC pools do you have in your
system and what is its configuration?

thanks,
Martin.

On Wed, Apr 5, 2017 at 10:34 PM, Matt .  wrote:

> Hi Guys,
>
> Since the upgrade to 4.1 I have the issue that every nic I add I get a
> several of times:
>
> MAC Address xx:xx:xx:xx:xx is already in use.
>
> I have added an extra pool and this issue still exists.
>
> Anyone a clue why this happens ?
>
> Thanks,
>
> Matt
> ___
> 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] Upgrading libguestfs to import debian VM

[Simon Vincent]

I find that running oVirt 4.1.1 I can not import any debian based VMs as
virt-v2v/libguestfs is too old.
This bug report https://bugzilla.redhat.com/show_bug.cgi?id=1362497
indicates that newer versions of libguestfs support importing debian and
Ubuntu VMs.

Are there any plans to include a newer version of libguestfs in oVirt soon?
If I built a newer version of libguestfs on my ovirt-node would it break
everything?

Regards

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

[ovirt-users] [ANN] oVirt 4.1.1 Async release

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the oVirt
4.1.1 Async Release, as of April 6th, 2017

Following oVirt 4.1.1 GA the oVirt team identified some bugs worth to be
addressed out of the usual release cycle.
For this reason an async release including these fixes has been prepared
and is now available for:

* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)

See the new section "What's New in 4.1.1 Async release" within oVirt 4.1.1
release notes [3] for a list of new features and bugs fixed.

Notes:
- oVirt Engine Appliance, oVirt node and oVirt Live will be available soon
[4]

Additional Resources:
* Read more about the oVirt 4.1.1 release highlights:
http://www.ovirt.org/release/4.1.1/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.1/
[4] http://resources.ovirt.org/pub/ovirt-4.1/iso/


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

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

Re: [ovirt-users] VM in oVirt 4 sometimes does not have proper CPU guest count

[Christophe TREFOIS]

Hi all,

I still have this issue and would like to know what we can do to debug this or 
figure out why this is happening?

We are now in 4.1.0 on the engine and the host in question, and still face the 
same problem on some Ubuntu VMs.

Thanks a lot for any pointers,

Kind regards,
Christophe

> On 20 Feb 2017, at 18:47, Christophe TREFOIS  
> wrote:
> 
> Dear all,
> 
> We upgraded today engine to 4.0.6 and a host to CentOS 7.3 and all packages 
> updated.
> 
> Most VMs start up with correct number of guest CPUs except 2 or 3 that only 
> spawn with 1 guest CPU count.
> We set for instance a CPU profile of 1:4:1 but only 1 vCPU is available to VM.
> 
> The VM itself is running Trusty, but other Trusty VM seem fine.
> 
> Do you have any idea what could be the issue and how to perhaps fix this?
> 
> Kind regards,
> Christophe
> -- 
> 
> Dr Christophe Trefois, Dipl.-Ing.  
> Technical Specialist / Post-Doc
> 
> UNIVERSITÉ DU LUXEMBOURG
> 
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine  
> 6, avenue du Swing 
> L-4367 Belvaux  
> T: +352 46 66 44 6124 
> F: +352 46 66 44 6949  
> http://www.uni.lu/lcsb 
>        
>    
>    
> 
> 
> This message is confidential and may contain privileged information. 
> It is intended for the named recipient only. 
> If you receive it in error please notify me and permanently delete the 
> original message and any copies. 
> 
>   
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] SKD4

[Fabrice Bacchella]

I trying to migrate my python code from sdk3 to sdk4, is there any migration 
doc, documentation help about that ? Even google is unable to find anything 
relevant about that.

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

[ovirt-users] mapping shell fencing opions with gui ones for ipmilan agent

[Gianluca Cecchi]

Hello,
executing from host itself the following command it works

[root@ov300 ~]# fence_ipmilan -P -a 10.10.193.103 -l fenceuser -A password
-L operator -S /usr/local/bin/pwd_ov300.sh -o status
Status: ON
[root@ov300 ~]#

But I'm unable to obtain successful test result in web admin fencing agent
config window

I set ip, user, password and ipmilan as agent, and then tried in options

auth=password,privlvl=operator,lanplus=1
and also
auth=password,privlvl=operator,lanplus=on

this the only host in cluster so it is the one used for testing by oVirt.

Tipically on these same server in RHEL 6.x ClusterSuite I use this in
cluster.conf and it works too:




Any hint on correct mapping of parameters for oVirt?
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users