Cumulative CPU time not implemented
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-powervm |
Fix Released
|
Low
|
Matthew Edmonds |
Bug Description
The nova-powervm driver claims 'complete' for:
[operation.
title=Guest instance status
status=mandatory
notes=Provides a quick report on information about the guest instance,
including the power state, memory allocation, CPU allocation, number
of vCPUs and cummulative CPU execution time. As well as being
informational, the power state is used by the compute manager for
tracking changes in guests. Therefore this operation is considered
mandatory to support.
However, "cumulative CPU execution time" would be reported via InstanceInfo.
There's a couple of questions here:
- Is this attribute mandatory to claim 'complete' for the operation?
- To what level is it even possible for us to calculate this?
- Does PCM report a total-since-birth for an LPAR?
- Does that total get reset at events like LPAR reboot? Live migration? REST server restart?
Need to look at how the other drivers handle this and make some attempt at parity.
Changed in nova-powervm: | |
assignee: | nobody → Eric Berglund (esberglu) |
https:/ /github. com/openstack/ nova/commit/ 5db9389c01b0cb6 eeacf57c2255087 6ffcd1a87c removes cpu_time_ns from nova, so we should just need to cleanup nova-powervm to no longer set that at all (or the other things that nova commit removed).