Bug 1126447
| Summary: | [RFE][nova] Optionally allow nova-scheduler to be deployed as Active/Active or Active/Passive | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Scott Lewis <sclewis> |
| Component: | openstack-foreman-installer | Assignee: | Jason Guiditta <jguiditt> |
| Status: | CLOSED ERRATA | QA Contact: | Asaf Hirshberg <ahirshbe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 (RHEL 7) | CC: | aberezin, ajeain, breeler, dnavale, jguiditt, lnatapov, mburns, morazi, oblaut, rbalakri, rhos-maint, sclewis, sgordon, yeylon |
| Target Milestone: | z1 | Keywords: | FutureFeature |
| Target Release: | Installer | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-foreman-installer-2.0.23-1.el6ost | Doc Type: | Enhancement |
| Doc Text: |
This enhancement adds support to allow nova-scheduler to be deployed as Active/Passive deployments as Active/Active deployments are not desired for all HA scenarios.
To use the Active/Passive deployment, set scheduler_host_subset_size parameter to 1 in the advanced configuration tab.
|
Story Points: | --- |
| Clone Of: | 1104219 | Environment: | |
| Last Closed: | 2014-10-01 13:25:52 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: | 1104219 | ||
| Bug Blocks: | 1083890, 1104884, 1111701 | ||
|
Comment 2
Leonid Natapov
2014-08-19 13:10:48 UTC
default is currently set to 30. [root@macf04da2732fb1 ~]# grep -ir host_subset /etc/nova/nova.conf #scheduler_host_subset_size=1 scheduler_host_subset_size=30 [root@puma42 ~]# rpm -qa |grep rhel rhel-osp-installer-0.3.6-1.el6ost.noarch That is what the default should be. When set this way, scheduler is A/A. When you change it to 1, the schedulers should be A/P 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. http://rhn.redhat.com/errata/RHBA-2014-1350.html |