Bug 1573209
| Summary: | [BACKPORT-12] Implement CPU weighter filter | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Stephen Finucane <stephenfin> | |
| Component: | openstack-nova | Assignee: | Stephen Finucane <stephenfin> | |
| Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 10.0 (Newton) | CC: | aguetta, berrange, brault, dasmith, dcadzow, dwojewod, egallen, eglynn, jhakimra, kchamart, lyarwood, mbooth, nova-maint, pablo.iranzo, sbauza, sgordon, srevivo, stephenfin, vromanso | |
| Target Milestone: | async | Keywords: | FeatureBackport, TestOnly, Triaged, ZStream | |
| Target Release: | 12.0 (Pike) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | https://blueprints.launchpad.net/nova/+spec/vcpu-weighter | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-16.1.4-2.el7ost | Doc Type: | Enhancement | |
| Doc Text: |
Feature:
Add the CPUWeigher weigher for nova-scheduler.
Reason:
The CPUWeigher allows operators to configure a stacking or spreading policy for vCPUs.
Result:
Operators can enable the CPUWeigher and configure a stacking (use all vCPUs on one node first) or spreading (attempt to use a roughly equal amount of vCPUs from all hosts) policy.
|
Story Points: | --- | |
| Clone Of: | 1571286 | |||
| : | 1573210 1576887 (view as bug list) | Environment: | ||
| Last Closed: | 2018-12-05 18:50:50 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1469073, 1565089, 1571286, 1576882, 1576885, 1576888, 1582406, 1582409, 1582412, 1582413 | |||
| Bug Blocks: | 1476900, 1573210, 1576887 | |||
|
Comment 1
Lon Hohberger
2018-10-03 10:34:53 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3791 |