Bug 888396 - Edit pool - Prestarted VMs - slowdown
Summary: Edit pool - Prestarted VMs - slowdown
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.2.0
Assignee: Arik
QA Contact: Jiri Belka
URL:
Whiteboard: virt
Depends On:
Blocks: 915537
TreeView+ depends on / blocked
 
Reported: 2012-12-18 16:08 UTC by Jiri Belka
Modified: 2013-06-11 08:25 UTC (History)
10 users (show)

Fixed In Version: sf7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 11636 0 None None None Never
oVirt gerrit 11637 0 None None None Never

Description Jiri Belka 2012-12-18 16:08:35 UTC
Description of problem:

When creating new pool, waiting a while so VMs are created, editing pool to define number of prestarted VMs, then it takes some time to make them running. According to tjelink@ it is VmPoolMonitor interval. My (default) VmPoolMonitorIntervalInMinutes is 5 minutes and I have to wait... Make it to trigger the action immediatelly for newly edited pool or let the user know in documentation about this slowdown.

Version-Release number of selected component (if applicable):
25.1

How reproducible:
100%

Steps to Reproduce:
1. new pool
2. edit pool (when previous task is done)
3. wait...
  
Actual results:
Have to wait for next trigger of VmPoolMonitor to start my VMs.

Expected results:
Have my prestarted VMs up ASAP when possible or let me know I have to wait.

Additional info:

2012-Dec-18, 16:54
VM test_pool-3 was restarted on Host dell-r210ii-04

2012-Dec-18, 16:54
VM test_pool-2 was restarted on Host dell-r210ii-04

2012-Dec-18, 16:54
VM test_pool-1 was restarted on Host dell-r210ii-04

2012-Dec-18, 16:53
VM test_pool-3 was restarted on Host <UNKNOWN>

2012-Dec-18, 16:53
VM test_pool-2 was restarted on Host <UNKNOWN>

2012-Dec-18, 16:53
VM test_pool-1 was restarted on Host <UNKNOWN>

2012-Dec-18, 16:51
VM Pool test_pool was updated by admin@internal, 0 VMs were added.

2012-Dec-18, 16:50
VM test_pool-5 creation has been completed.


[root@jb-rh31 ~]# rhevm-config -a | egrep -i "pool.*interval"
VmPoolMonitorIntervalInMinutes: 5 version: general

Comment 1 Simon Grinberg 2012-12-26 12:45:53 UTC
Required behavior: 
The VMs should start immediately when setting the pre-started number

VmPoolMonitor should be the mechanism to grantee that if VMs where consumed, to pre-start other.

Comment 3 Jiri Belka 2013-02-14 14:38:55 UTC
OK, sf7.

2013-Feb-14, 15:30
VM testpool-2 was restarted on Host <UNKNOWN>
	
2013-Feb-14, 15:30
VM testpool-1 was restarted on Host <UNKNOWN>
	
2013-Feb-14, 15:30
VM Pool testpool was updated by admin@internal, 0 VMs were added.

Comment 4 Itamar Heim 2013-06-11 08:23:07 UTC
3.2 has been released

Comment 5 Itamar Heim 2013-06-11 08:25:02 UTC
3.2 has been released


Note You need to log in before you can comment on or make changes to this bug.