Re: [ovirt-users] [Ovirt 4.0] Cluster : Scheduling policy

2017-07-16 Thread Doron Fediuck 
Hi Rohit,
You have 2 ways to handle this case;

1. Use pin to multiple hosts [a]. This will force the VM to run on one of
the hosts you specify (1 or 2).
If the VM is defined as highly available, it'll automatically be restarted
on the other host in case the
current one goes down.

2. Use affinity labels [b]. You would like to set a hard affinity to host
1, and a soft affinity to host 2
to ensure host 1 is chosen if it's up.

HTH,
Doron

[a]
https://www.ovirt.org/develop/release-management/features/sla/vmpinningtomultiplehosts/
[b] https://www.ovirt.org/blog/2016/07/affinity-labels/

On 3 July 2017 at 16:37, TranceWorldLogic . 
wrote:

> I got it.
> It is under configure button at top right corner.
>
> I want to do below stuff please help me how can I make it possible using
> ovirt.
> (let assume 2 host system and 1 vm)
> 1> I want to pin Host for particular VM let say host is host1.
> 2> In some circumstances let say host1 goes down in that case vm migrate
> to host2.
> 3> After sometime host1 comes up.
> 4> I want vm to migrate back to its pin host (i.e host1)
>
> Please help me.
>
> Thanks,
> ~Rohit
>
> On Mon, Jul 3, 2017 at 6:27 PM, TranceWorldLogic . <
> tranceworldlo...@gmail.com> wrote:
>
>> Hi,
>>
>> Can some one help me how to select PinToHost policy in ovirt 4.0 ?
>> I am lost in GUI.
>>
>> http://www.ovirt.org/develop/release-management/features/sla
>> /scheduler-policies/
>>
>> Thanks,
>> ~Rohit
>>
>
>
> ___
> 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 4.1.3 / iSCSI / VM Multiple Disks / Snapshot deletion issue.

2017-07-16 Thread Benny Zlotnik 
[Adding ovirt-users]

On Sun, Jul 16, 2017 at 12:58 PM, Benny Zlotnik  wrote:
> We can see a lot of related errors in the engine log but we are unable
> to correlate to the vdsm log. Do you have more hosts? If yes, please
> attach their logs as well.
> And just to be sure you were attempting to perform cold merge?
>
> On Fri, Jul 14, 2017 at 7:32 PM, Devin Acosta  wrote:
>>
>> You can get my logs from:
>>
>> https://files.linuxstack.cloud/s/NjoyMF11I38rJpH
>>
>> They were a little to big to attach to this e-mail. Would like to know if
>> this is the similar bug that Richard indicated is a possibility.
>>
>> --
>>
>> Devin Acosta
>> Red Hat Certified Architect, LinuxStack
>> 602-354-1220 || de...@linuxguru.co
>>
>> On July 14, 2017 at 9:18:08 AM, Devin Acosta (de...@pabstatencio.com) wrote:
>>
>> I have attached the logs.
>>
>>
>>
>> --
>>
>> Devin Acosta
>> Red Hat Certified Architect, LinuxStack
>> 602-354-1220 || de...@linuxguru.co
>>
>> On July 13, 2017 at 9:22:03 AM, richard anthony falzini
>> (richardfalz...@gmail.com) wrote:
>>
>> Hi,
>> i have the same problem with gluster.
>> this is a bug that i opened
>> https://bugzilla.redhat.com/show_bug.cgi?id=1461029 .
>> In the bug i used single disk vm but i start to notice the problem with
>> multiple disk vm.
>>
>>
>> 2017-07-13 0:07 GMT+02:00 Devin Acosta :
>>>
>>> We are running a fresh install of oVIRT 4.1.3, using ISCSI, the VM in
>>> question has multiple Disks (4 to be exact). It snapshotted OK while on
>>> iSCSI however when I went to delete the single snapshot that existed it went
>>> into Locked state and never came back. The deletion has been going for well
>>> over an hour, and I am not convinced since the snapshot is less than 12
>>> hours old that it’s really doing anything.
>>>
>>> I have seen that doing some Googling indicates there might be some known
>>> issues with iSCSI/Block Storage/Multiple Disk Snapshot issues.
>>>
>>> In the logs on the engine it shows:
>>>
>>> 2017-07-12 21:59:42,473Z INFO
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler2) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>>> type:'PrepareMerge' to complete
>>> 2017-07-12 21:59:52,480Z INFO
>>> [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler2) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'RemoveSnapshot' (id: '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on
>>> child command id: '75c535fd-4558-459a-9992-875c48578a97'
>>> type:'ColdMergeSnapshotSingleDisk' to complete
>>> 2017-07-12 21:59:52,483Z INFO
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler2) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>>> type:'PrepareMerge' to complete
>>> 2017-07-12 22:00:02,490Z INFO
>>> [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler6) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'RemoveSnapshot' (id: '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on
>>> child command id: '75c535fd-4558-459a-9992-875c48578a97'
>>> type:'ColdMergeSnapshotSingleDisk' to complete
>>> 2017-07-12 22:00:02,493Z INFO
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler6) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>>> type:'PrepareMerge' to complete
>>> 2017-07-12 22:00:12,498Z INFO
>>> [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler3) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'RemoveSnapshot' (id: '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on
>>> child command id: '75c535fd-4558-459a-9992-875c48578a97'
>>> type:'ColdMergeSnapshotSingleDisk' to complete
>>> 2017-07-12 22:00:12,501Z INFO
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler3) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>>> type:'PrepareMerge' to complete
>>> 2017-07-12 22:00:22,508Z INFO
>>> [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
>>> (DefaultQuartzScheduler5) [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>>> 'RemoveSnapshot' (id: '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on
>>> child command id: '75c535fd-4558-459a-9992-875c48578a97'
>>> type:'ColdMergeSnapshotSingleDisk' to complete
>>>

Re: [ovirt-users] oVIRT 4.1.3 / iSCSI / VM Multiple Disks / Snapshot deletion issue.

2017-07-16 Thread Ala Hino 
Please note that bug 1461029
 is about live merge
(the VM is up) while, at least according to the logs, the issue described
here is related to cold merge (the VM is down).

On Thu, Jul 13, 2017 at 7:22 PM, richard anthony falzini <
richardfalz...@gmail.com> wrote:

> Hi,
> i have the same problem with gluster.
> this is a bug that i opened  https://bugzilla.redhat.com/
> show_bug.cgi?id=1461029 .
> In the bug i used single disk vm but i start to notice the problem with
> multiple disk vm.
>
>
> 2017-07-13 0:07 GMT+02:00 Devin Acosta :
>
>> We are running a fresh install of oVIRT 4.1.3, using ISCSI, the VM in
>> question has multiple Disks (4 to be exact). It snapshotted OK while on
>> iSCSI however when I went to delete the single snapshot that existed it
>> went into Locked state and never came back. The deletion has been going for
>> well over an hour, and I am not convinced since the snapshot is less than
>> 12 hours old that it’s really doing anything.
>>
>> I have seen that doing some Googling indicates there might be some known
>> issues with iSCSI/Block Storage/Multiple Disk Snapshot issues.
>>
>> In the logs on the engine it shows:
>>
>> 2017-07-12 21:59:42,473Z INFO  [org.ovirt.engine.core.bll.Se
>> rialChildCommandsExecutionCallback] (DefaultQuartzScheduler2)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>> type:'PrepareMerge' to complete
>> 2017-07-12 21:59:52,480Z INFO  [org.ovirt.engine.core.bll.Co
>> ncurrentChildCommandsExecutionCallback] (DefaultQuartzScheduler2)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command 'RemoveSnapshot' (id:
>> '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on child command id:
>> '75c535fd-4558-459a-9992-875c48578a97' type:'ColdMergeSnapshotSingleDisk'
>> to complete
>> 2017-07-12 21:59:52,483Z INFO  [org.ovirt.engine.core.bll.Se
>> rialChildCommandsExecutionCallback] (DefaultQuartzScheduler2)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>> type:'PrepareMerge' to complete
>> 2017-07-12 22:00:02,490Z INFO  [org.ovirt.engine.core.bll.Co
>> ncurrentChildCommandsExecutionCallback] (DefaultQuartzScheduler6)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command 'RemoveSnapshot' (id:
>> '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on child command id:
>> '75c535fd-4558-459a-9992-875c48578a97' type:'ColdMergeSnapshotSingleDisk'
>> to complete
>> 2017-07-12 22:00:02,493Z INFO  [org.ovirt.engine.core.bll.Se
>> rialChildCommandsExecutionCallback] (DefaultQuartzScheduler6)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>> type:'PrepareMerge' to complete
>> 2017-07-12 22:00:12,498Z INFO  [org.ovirt.engine.core.bll.Co
>> ncurrentChildCommandsExecutionCallback] (DefaultQuartzScheduler3)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command 'RemoveSnapshot' (id:
>> '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on child command id:
>> '75c535fd-4558-459a-9992-875c48578a97' type:'ColdMergeSnapshotSingleDisk'
>> to complete
>> 2017-07-12 22:00:12,501Z INFO  [org.ovirt.engine.core.bll.Se
>> rialChildCommandsExecutionCallback] (DefaultQuartzScheduler3)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>> type:'PrepareMerge' to complete
>> 2017-07-12 22:00:22,508Z INFO  [org.ovirt.engine.core.bll.Co
>> ncurrentChildCommandsExecutionCallback] (DefaultQuartzScheduler5)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command 'RemoveSnapshot' (id:
>> '40482d09-8a7c-4dbd-8324-3e789296887a') waiting on child command id:
>> '75c535fd-4558-459a-9992-875c48578a97' type:'ColdMergeSnapshotSingleDisk'
>> to complete
>> 2017-07-12 22:00:22,511Z INFO  [org.ovirt.engine.core.bll.Se
>> rialChildCommandsExecutionCallback] (DefaultQuartzScheduler5)
>> [a5f6eaf2-7996-4d51-ba62-050272d1f097] Command
>> 'ColdMergeSnapshotSingleDisk' (id: '75c535fd-4558-459a-9992-875c48578a97')
>> waiting on child command id: 'd92e9a22-5f0f-4b61-aac6-5601f8ac2cda'
>> type:'PrepareMerge' to complete
>>
>> This is what I seen on the SPM when I grep’d the Snapshot ID.
>>
>> 2017-07-12 14:22:18,773-0700 INFO  (jsonrpc/6) [vdsm.api] START
>> createVolume(sdUUID=u'0c02a758-4295-4199-97de-b041744b3b15',
>> spUUID=u'0001-0001-0001-0001-0311',
>> imgUUID=u'6a887015-67cd-4f7b-b709-eef97142258d', size=u'107374182400',
>> volFormat=4, preallocate=2, diskType=2, 
>> volUUID=u'5921ba71-0f00-46cd-b0be-3c2ac1396845',
>> desc=u'',

Re: [ovirt-users] Installation oVirt node and engine on the same machine

2017-07-16 Thread Yedidyah Bar David 
On Fri, Jul 14, 2017 at 7:40 PM, Vinícius Ferrão  wrote:
> WC, here is one guide. The procedure is what Alexander said: self-hosted
> engine.
>
> http://www.ovirt.org/documentation/self-hosted/Self-Hosted_Engine_Guide/

Indeed.

There is one important difference: hosted-engine requires some shared storage.
In principle you can use shared storage exported from the same machine.
You can do that with NFS or iSCSI. NFS is considered somewhat more risky, but
somewhat easier to setup (at least, if you have no experience with iSCSI).
You can search the list archives with things like 'hosted-engine all-in-one
same machine nfs iscsi'.

Another option, depending on your needs, is lago + ovirt-system-tests.

Best,

>
> V.
>
> Sent from my iPhone
>
> On 14 Jul 2017, at 10:21, wc hung  wrote:
>
> Hi all,
>
> Could we install oVirt node and engine on the same machine? If we can do
> that, is there any guide to show the step?
>
> ___
> 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
>



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