Bug 1571286
| Summary: | [BACKPORT-13] Implement CPU weighter filter | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Erwan Gallen <egallen> | |
| 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, joflynn, jschluet, kchamart, lmarsh, lyarwood, mbooth, nova-maint, pablo.iranzo, sbauza, sgordon, srevivo, stephenfin, vromanso | |
| Target Milestone: | z3 | Keywords: | FeatureBackport, TestOnly, Triaged, ZStream | |
| Target Release: | 13.0 (Queens) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | https://blueprints.launchpad.net/nova/+spec/vcpu-weighter | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-17.0.5-2.d7864fbgit.el7ost | Doc Type: | Enhancement | |
| Doc Text: |
You can use the weigher `CPUWeigher` to spread (default) or pack workloads on hosts based on their vCPU usage. You can set the nova.conf `[filter_scheduler] cpu_weight_multiplier` configuration option to -1.0 or 1.0. If you set this option to 1.0, instances are spread across hosts. If you set this option to -1.0, instances are packed on a host. If you set the value to 0, the weigher is disabled.
|
Story Points: | --- | |
| Clone Of: | 1565089 | |||
| : | 1573209 1576885 (view as bug list) | Environment: | ||
| Last Closed: | 2018-11-13 22:13:45 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, 1576882, 1576888, 1582406, 1582409, 1582412, 1582413 | |||
| Bug Blocks: | 1476900, 1573209, 1573210, 1576885, 1576887, 1732909 | |||
|
Comment 8
Joanne O'Flynn
2018-08-13 10:09:19 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:3602 |