Resource pools CPU usage/availability shown as integers not float

[vfebvre]

Following merge of #100 to include HMC Shared Processor Pools in the inventory as Resource Pools :

• CPU Reserve/Share values stored in the resource_pools table are integers and not accurate as actual values from the HMC can include fraction of a CPU (granularity of 0.01).

vmdb_development=# \d+ resource_pools
                                                                  Table "public.resource_pools"
        Column         |            Type             | Collation | Nullable |                  Default                   | Storage  | Stats target | Description
-----------------------+-----------------------------+-----------+----------+--------------------------------------------+----------+--------------+-------------
 id                    | bigint                      |           | not null | nextval('resource_pools_id_seq'::regclass) | plain    |              |
 name                  | character varying           |           |          |                                            | extended |              |
...
 cpu_reserve           | integer                     |           |          |                                            | plain    |              |
 cpu_reserve_expand    | boolean                     |           |          |                                            | plain    |              |
 cpu_limit             | integer                     |           |          |                                            | plain    |              |
 cpu_shares            | integer                     |           |          |                                            | plain    |              |
 cpu_shares_level      | character varying           |           |          |                                            | extended |              |
...

In the example below, CPU Reserve should be 1.3 and Shares 1.7

[Fryguy]

Discussion about whether we should do this over in the schema PR 👉 ManageIQ/manageiq-schema#675 (comment)

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[miq-bot]

This issue has been automatically closed because it has not been updated for at least 3 months.

Feel free to reopen this issue if this issue is still valid.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[jaywcarman]

This issue is still valid... re-opening.

[miq-bot]

This issue has been automatically closed because it has not been updated for at least 3 months.

Feel free to reopen this issue if this issue is still valid.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[jaywcarman]

Fixed by ManageIQ/manageiq-schema#708