Hide Forgot
Description of problem: For OpenShift Online, we're going to need to set the following in /etc/origin/master/scheduler.json: { "kind": "Policy", "apiVersion": "v1", "predicates": [ {"name": "MatchNodeSelector"}, {"name": "PodFitsResources"}, {"name": "PodFitsPorts"}, {"name": "NoDiskConflict"}, {"name" : "MaxEBSVolumeCount"} ],"priorities": [ {"name": "LeastRequestedPriority", "weight": 1}, {"name": "ServiceSpreadingPriority", "weight": 1} ] } It would be ideal to have some installer options to set these variables. Related github issue is here https://github.com/openshift/online/issues/77 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
openshift-ansible PR: https://github.com/openshift/openshift-ansible/pull/1680 To override the scheduler as needed, the following variables can be set in the inventory: openshift_master_scheduler_predicates=[{"name": "MatchNodeSelector"}, {"name": "PodFitsResources"}, {"name": "PodFitsPorts"}, {"name": "NoDiskConflict"}, {"name" : "MaxEBSVolumeCount"}] openshift_master_scheduler_priorities=[{"name": "LeastRequestedPriority", "weight": 1}, {"name": "ServiceSpreadingPriority", "weight": 1}] if defining in yaml format, it can be done in the following (much more readable way): openshift_master_scheduler_predicates: - name: MatchNodeSelector - name: PodFitsResources - name: PodFitsPorts - name: NoDiskConflict - name: MaxEBSVolumeCount openshift_master_scheduler_priorities: - name: LeastRequestedPriority weight: 1 - name: ServiceSpreadingPriority weight: 1
This is in openshift-ansible-3.0.70-1.git.0.3f80411.el7 which is built and available in the latest puddles.
check on openshift-ansible-3.0.71-1.git.0.63af28f.el7.noarch scenarios 1: Install env without 'openshift_master_scheduler_predicates' and 'openshift_master_scheduler_priorities' check the configuration file, compare with the configuration from template, the "ServiceSpreadingPriority" is changed to 'SelectorSpreadPriority', is it by design? scenarios 2: Install ha-master env with 'openshift_master_scheduler_predicates' and 'openshift_master_scheduler_priorities' <--snip--> openshift_master_scheduler_predicates=[{"name": "MatchNodeSelector"}, {"name": "PodFitsResources"}, {"name": "PodFitsPorts"}, {"name": "NoDiskConflict"}, {"name" : "MaxEBSVolumeCount"}] openshift_master_scheduler_priorities=[{"name": "LeastRequestedPriority", "weight": 1}, {"name": "ServiceSpreadingPriority", "weight": 1}] <--snip--> check the configuration file after installation, the specified value take effect. Move this issue to VERIFIED.
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-2016:1065