5ab9ef11e2
Changing the minval/maxval attribute to the minimum/maxium of every weigher run changes the outcome of future runs. We noticed it in the SoftAffinityWeigher, where a previous run with a host hosting a lot of instances for a server-group would make a later run use that maximum. This resulted in the weight being lower than 1 for a host hosting all instances of another server-group, if the number of instances of that server-group on that host is less than a previous server-group's instances on any host. Previously, there were two places that computed the maxval/minval - once in normalize() and once in weigh_objects() - but only the one in weigh_objects() saved the values to the weigher. The code now uses the maxval/minval as defined by the weigher and keeps the weights inside the maxval-minval range. There's also only one place to compute the minval/maxval now, if the weigher did not set a value: normalize(). Closes-Bug: 1870096 Change-Id: I60a90dabcd21b4e049e218c7c55fa075bb7ff933 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .pre-commit-config.yaml | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| babel.cfg | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| MAINTAINERS | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: