Comment 10 for bug 1928949

Reviewed: https://review.opendev.org/c/starlingx/config/+/792565
Committed: https://opendev.org/starlingx/config/commit/8423e70fd04f07bbf6a22eb83d45c719663b0c51
Submitter: "Zuul (22348)"
Branch: master

commit 8423e70fd04f07bbf6a22eb83d45c719663b0c51
Author: Dan Voiculeasa <email address hidden>
Date: Fri May 21 12:56:47 2021 +0300

    Fix pod max pids service parameter default value

    Openstack installation fails for rabbit-mq pods.

    Change the approach of how the default value is selected.
    Document recommended minimum values for apps instead of using them.
    Select the default value as high as possible, protecting against a
    rogue pod, protecting against platform slowdowns created by high number
    of processes in the system, but low enough such that platform is still
    responsive even on older hardware.
    User is free to decrease the limit to increase the degree of protection
    against slowdowns.

    Initially it was observed that openstack pods reach ~450 processes
    in steady state.
    New tests show even with the 2/3 extra room, 750 pid limit is not
    sufficient when deploying rabbit-mq pods. But 2000 is.
    Recommended minimum value for openstack pods pid limit becomes 2000.

    Partial-Bug: 1928949
    Related-Bug: 1928353
    Signed-off-by: Dan Voiculeasa <email address hidden>
    Change-Id: I0d66173e2247fae15eda1ad0e83c7bcf858f0369