Red Hat Bugzilla – Bug 1257398
Default value of max_resources_per_stack too low
Last modified: 2016-08-19 16:19:53 EDT
Description of problem:
When using RHEL OSP-d to deploy a small cloud (65 bare metal machines), the deployment will run out of resources and fail due to max_resources_per_stack =1000 . Increasing the value allows the deployment to succeed.
Ideally the director should be able to calculate this, if nt, set the value to at least 100000.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to deploy 60+ nodes
Deployment runs out of resources and fails
It should just deploy out of the box.
Is there any additional overhead of allowing a higher count if it is not reached ?
(is some amount of system resources set aside for the given value ?)
*** This bug has been marked as a duplicate of bug 1240587 ***
Need to wait for https://bugzilla.redhat.com/show_bug.cgi?id=1257401 to be fixed before this is able to be fixed.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
The setting appears to be -1 since OSP 8/liberty