unreserved_ram and memory_provisionable_bytes are not same

[chayeon]

Hi,

Even if the "provisionable" value of a node displayed in the operations portal(adminui) is "0", instances can be scheduled and deployed on that node.

So, I read the regarding source code portion of sdc-cnapi, I found followings: (let's say the overprovision_ratios_ram = 1)

• To describe free memory on each node, "unreserved_ram" and "memory_provisionable_bytes" variables are used
• unreserved_ram = total memory size - reserved memory size - total vm memory size ( in "running" and "stopped" state not "failed" state)
• memory_provisionable_bytes = unreserved_ram - total failed vm memory size
• "unreserved_ram" is used to filter out the min_ram hosts by the scheduler.
• "memory_provisionable_bytes" are used to display the free memory size on the portal.

Here's my question.

• What is the purpose of "memory_provisionable_bytes"?
• How about removing the failed vms in calculation of memory_provisionable_bytes to make the two variables' values same?

Thanks.