Bug 1104219
Summary: | [RFE][nova] Optionally allow nova-scheduler to be deployed as Active/Active or Active/Passive | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Russell Bryant <rbryant> | |
Component: | openstack-foreman-installer | Assignee: | Jason Guiditta <jguiditt> | |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | high | |||
Version: | 5.0 (RHEL 7) | CC: | aberezin, acathrow, ajeain, breeler, ddomingo, mburns, morazi, rhos-maint, sclewis, sgordon, vpopovic, yeylon | |
Target Milestone: | ga | Keywords: | FutureFeature | |
Target Release: | 5.0 (RHEL 7) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-foreman-installer-2.0.7-1.el6ost | Doc Type: | Enhancement | |
Doc Text: |
With this release, the Compute scheduler runs in Active/Active mode for high availability (HA) by default.
This is required because Active/Active mode in HA for the Compute scheduler allows better scaling than the Active/Passive mode.
If you wish to run the Compute scheduler in Active/Passive mode, simply set scheduler_host_subset_size=1.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1104884 1111701 1126447 (view as bug list) | Environment: | ||
Last Closed: | 2014-08-04 18:32:48 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: | ||||
Bug Blocks: | 1083890, 1104884, 1111701, 1126447 |
Description
Russell Bryant
2014-06-03 14:28:48 UTC
(In reply to Russell Bryant from comment #0) > The nova-scheduler service requires special consideration when deploying it > for HA. > > The default should be an Active/Passive setup using Pacemaker. > > For larger deployments, we should also provide the option of deploying > nova-scheduler in an Active/Active mode. Some notes about deploying it > Active/Active: > > * In this mode, the number of nova-scheduler instances should be > configurable. it should default to 2. It could be up to the number of > controller nodes. > > * When using Active/Active, the following configuration option needs to be > set in nova.conf: scheduler_host_subset_size. This option defaults to 1. I > would recommend setting it to a default of "10" when using Active/Active. > However, it's something that should be allowed to be tweaked if needed. After further discussion, consider the following changes to this: 1) Make the default A/A instead of A/P. 2) In the A/A configuration, use a default value of 30 instead of 10 as described before. 3) To keep things simple, just run nova-scheduler on every controller node in the A/A case. 4) Still work toward having A/P as an optional deployment choice. I am currently implementing this in quickstack (openstack-foreman-installer component), and I just want to verify that the only configuration difference between A/A and A/P is really just: 1. A/A has scheduler running on all nodes instead of 1 2. A/A has scheduler_host_subset_size=30 (default, can be overridden). (In reply to Jason Guiditta from comment #4) > I am currently implementing this in quickstack (openstack-foreman-installer > component), and I just want to verify that the only configuration difference > between A/A and A/P is really just: > 1. A/A has scheduler running on all nodes instead of 1 > 2. A/A has scheduler_host_subset_size=30 (default, can be overridden). Yes, that's right. If you're also implementing A/P, then you need pacemaker config for that, but I think that's it. Patch merged: https://github.com/redhat-openstack/astapor/pull/271 Russel, can you look at my doc text and correct if you think the description is incorrect? Thanks (In reply to Jason Guiditta from comment #10) > Russel, can you look at my doc text and correct if you think the description > is incorrect? Thanks Updated. Let me know if you'd like to discuss further. 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/RHEA-2014-1003.html |