edits

Author: mburke5678

modules/nodes-scheduler-default-creating.adoc

@@ -10,6 +10,22 @@
 You can control change the default scheduling behavior using a ConfigMap in the `openshift-config` project.
 Add and remove predicates and priorities to the ConfigMap to create a _scheduler policy_.
 
+.Sample scheduler configuration map
+[source,yaml]
+----
+kind: ConfigMap
+apiVersion: v1
+metadata:
+  name: scheduler-policy
+  namespace: openshift-config
+  selfLink: /api/v1/namespaces/openshift-config/configmaps/mypolicy
+  uid: 83917dfb-4422-11e9-b2c9-0a5e37b2b12e
+  resourceVersion: '1049773'
+  creationTimestamp: '2019-03-11T17:24:23Z'
+data:
+  policy.cfg: "{\n\"kind\" : \"Policy\",\n\"apiVersion\" : \"v1\",\n\"predicates\" : [\n\t{\"name\" : \"PodFitsHostPorts\"},\n\t{\"name\" : \"PodFitsResources\"},\n\t{\"name\" : \"NoDiskConflict\"},\n\t{\"name\" : \"NoVolumeZoneConflict\"},\n\t{\"name\" : \"MatchNodeSelector\"},\n\t{\"name\" : \"HostName\"}\n\t],\n\"priorities\" : [\n\t{\"name\" : \"LeastRequestedPriority\", \"weight\" : 10},\n\t{\"name\" : \"BalancedResourceAllocation\", \"weight\" : 1},\n\t{\"name\" : \"ServiceSpreadingPriority\", \"weight\" : 1},\n\t{\"name\" : \"EqualPriority\", \"weight\" : 1}\n\t]\n}\n"
+----
+
 .Procedure
 
 To create the scheduler policy:
@@ -44,6 +60,12 @@ To create the scheduler policy:
 . Create a ConfigMap based on the JSON file:
 +
 ----
+$ oc create configmap -n openshift-config --from-file=policy.cfg <configmap-name>
+----
++
+For example:
++
+----
 $ oc create configmap -n openshift-config --from-file=policy.cfg scheduler-policy
 
 configmap/scheduler-policy created

modules/nodes-scheduler-default-modifying.adoc

@@ -33,14 +33,14 @@ To modify the scheduler policy:
 
 Edit the scheduler configuration file to configure the desired
 predicates and priorities. 
-+
+
 .Sample modified scheduler configuration map
 [source,yaml]
 ----
 kind: ConfigMap
 apiVersion: v1
 metadata:
-  name: mypolicy
+  name: scheduler-policy
   namespace: openshift-config
   selfLink: /api/v1/namespaces/openshift-config/configmaps/mypolicy
   uid: 83917dfb-4422-11e9-b2c9-0a5e37b2b12e
@@ -49,19 +49,18 @@ metadata:
 data:
   policy.cfg: "{\n\"kind\" : \"Policy\",\n\"apiVersion\" : \"v1\",\n\"predicates\" : [\n\t{\"name\" : \"PodFitsHostPorts\"},\n\t{\"name\" : \"PodFitsResources\"},\n\t{\"name\" : \"NoDiskConflict\"},\n\t{\"name\" : \"NoVolumeZoneConflict\"},\n\t{\"name\" : \"MatchNodeSelector\"},\n\t{\"name\" : \"HostName\"}\n\t],\n\"priorities\" : [\n\t{\"name\" : \"LeastRequestedPriority\", \"weight\" : 10},\n\t{\"name\" : \"BalancedResourceAllocation\", \"weight\" : 1},\n\t{\"name\" : \"ServiceSpreadingPriority\", \"weight\" : 1},\n\t{\"name\" : \"EqualPriority\", \"weight\" : 1}\n\t]\n}\n"
 ----
-+
+
 For example, the following strings add the `labelpresence` predicate requiring the `rack` label on the nodes and the `labelPreference` priority giving a weight of 2 to the `rack` label:
-+
+
 [source,yaml]
 ----
 \n\t{\"name\" : \"labelPresence\", \"label\" : \"rack\",  \"presence\" : \"true\"},
 \n\t{\"name\" : \"labelPreference\", \"label\" : \"rack\", \"presence\" : \"true\", \"weight\" : 2},\n\t
------
+----
 
 The ConfigMap appears as following with the new priority:
-+
+
 [source,yaml]
 ----
 policy.cfg: "{\n\"kind\" : \"Policy\",\n\"apiVersion\" : \"v1\",\n\"predicates\" : [\n\t{\"name\" : \"PodFitsHostPorts\"},\n\t{\"name\" : \"PodFitsResources\"},\n\t{\"name\" : \"NoDiskConflict\"},\n\t{\"name\" : \"NoVolumeZoneConflict\"},\n\t{\"name\" : \"MatchNodeSelector\"},\n\t{\"name\" : \"HostName\"},\n\t{\"name\" : \"labelPresence\", \"label\" : \"rack\",  \"presence\" : \"true\"}\n\t],\n\"priorities\" : [\n\t{\"name\" : \"LeastRequestedPriority\", \"weight\" : 10},\n\t{\"name\" : \"BalancedResourceAllocation\", \"weight\" : 1},\n\t{\"name\" : \"ServiceSpreadingPriority\", \"weight\" : 1},\n\t{\"name\" : \"EqualPriority\", \"weight\" : 1},\n\t{\"name\" : \"labelPreference\", \"label\" : \"rack\", \"presence\" : \"true\", \"weight\" : 2},\n\t]\n}\n "
 ----
-