StarlingX

  1. Bug #1837749
  2. Comment #8

Comment 8 for bug 1837749

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/674718
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=e2cc0f53ac7be50fc4dfd1e2baedc3b2b32b1038
Submitter: Zuul
Branch: master

commit e2cc0f53ac7be50fc4dfd1e2baedc3b2b32b1038
Author: Tao Liu <email address hidden>
Date: Thu Aug 1 14:32:57 2019 -0400

    Fix the host unlock rejection caused by memory check

    Historically, the node total memory is calculated based on
    total of allocated hugepages, and usable Linux memory.
    NODE_TOTAL_MiB = HTOT + (AVAIL + PSS)

    This bottom-up calculation introduced variability and complexity.
    In some cases, the previously allocated memory exceeds the current
    total memory when AVAIL and PSS changed.

    This update changes NODE_TOTAL_MiB to MemTotal (the node's total
    usable ram), therefore Possible Huge Pages Memory = MemTotal -
    Platform Reserved.

    This update also adds a constraint, which only allows 90% of the
    Possible Huge Pages Memory to be allocated.

    Closes-Bug: 1837749

    Change-Id: I2fa1d82f70263bb2a1b93df2a405a979b42ed83a
    Signed-off-by: Tao Liu <email address hidden>