[openstack-dev] [ironic] [nova] Ironic virt driver resources reporting
vdrok at mirantis.com
Fri Dec 30 16:40:45 UTC 2016
There is a long standing problem of resources reporting in ironic virt
driver. It's described in a couple of bugs I've found - , . Switching
to placement API will make things better, but still there are some problems
there. For example, there are cases when ironic needs to say "this node is
not available", and it reports the vcpus=memory_mb=local_gb as 0 in this
case. Placement API does not allow 0s, so in  it is proposed to remove
inventory records in this case.
But the whole logic here  seems not that obvious to me, so I'd like to
discuss when do we need to report 0s to placement API. I'm thinking about
the following (copy-pasted from my comment on ):
- If there is an instance_uuid on the node, no matter what
provision/power state it's in, consider the resources as used. In case it's
an orphan, an admin will need to take some manual action anyway.
- If there is no instance_uuid and a node is in cleaning/clean wait
after tear down, it is a part of normal node lifecycle, report all
resources as used. This means we need a way to determine if it's a manual
or automated clean.
- If there is no instance_uuid, and a node:
- has a bad power state or
- is in maintenance
- or actually in any other case, consider it unavailable, report
available resources = used resources = 0. Provision state does not matter
in this logic, all cases that we wanted to take into account are
in the first two bullets.
Happy holidays to everyone!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev