Bug 883120

it is possible to search vms by pool name ("VMS: pool = somePool")
does this answer the requirement? if not, can you please elaborate on what exactly requested?

(In reply to Omer Frenkel from comment #1)
> it is possible to search vms by pool name ("VMS: pool = somePool")
> does this answer the requirement? if not, can you please elaborate on what
> exactly requested?

This is for dwh not in the UI so no.

In the vm pools table we have the following values:
pool id,
pool name,
pool description,
pool type,
parameters,
cluster id,
prestarted vms,
max assigned vms per user

I'm not sure what have these are used and what are not.
I plan to add pool id to vm configuration history. The option is either to add a separate configuration history table and a history version to vm configuration or not.

Simon, what do we want to keep?
Yair, do you know what is used and what is not?

max_assigned_vms_per_user is the maximum number of VMs a user can be associated with from this pool.
name and decription are obvious .
PoolType-  I think only Automatic and Manual are relevant.
Parameters - not relevant if not time lease pool, and as I said, IIRC - this is not relevant any more.

prestarted vms is the number of vms pre started , IIRC.

You also have a relation table - vm_pool_map you did not take into consideration.
Does this provide you more info?

Omer, did i forget something here?

> Omer, did i forget something here?

no

In order to answer the above question (comment #3), we need to understand:

- what are the reports that we would like to enable ?
- what happens on corner cases (VM was removed from pool ...)

Andrew ?

verified on is21:

rhevm-reports-3.3.0-19.el6ev.noarch
jasperreports-server-pro-5.5.0-4.el6ev.noarch
rhevm-dwh-3.3.0-19.el6ev.noarch


psql -U postgres -d ovirt_engine_history -c "select vm_pool_id, vm_pool_name from vm_configuration where vm_pool_id is not null;"
could not change directory to "/root"
              vm_pool_id              | vm_pool_name 
--------------------------------------+--------------
 9d95b43d-fbea-42f7-88ca-c708d0eac3fb | pool1
 9d95b43d-fbea-42f7-88ca-c708d0eac3fb | pool1
 9d95b43d-fbea-42f7-88ca-c708d0eac3fb | pool1
 9d95b43d-fbea-42f7-88ca-c708d0eac3fb | pool1
 9d95b43d-fbea-42f7-88ca-c708d0eac3fb | pool1
 9d95b43d-fbea-42f7-88ca-c708d0eac3fb | pool1
 77f17c61-56c8-4985-b7f4-1cda87f22b1d | pool2
 77f17c61-56c8-4985-b7f4-1cda87f22b1d | pool2
 77f17c61-56c8-4985-b7f4-1cda87f22b1d | pool2

This bug is currently attached to errata RHEA-2013:15116. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0036.html