anchor.diff:  The config files are fully specifying with no defaulting.  This means that any empty value means that you want to start up with an empty value for that parameter.  It makes it easy to reason about exactly what your configuration is, but it also means that it can be difficult to remember all of the options to specify.  To make this easier, the config files can be created with the `--write-config` flag and can be used via the `--config` flag.
   
   == Create the starting config files
  -The `openshift start` command accepts flags that indicate that it should simply write the config file that it would have used and terminate.  This is useful for getting a starting point for the config.  You can do this by running `openshift start --writeconfig --master-config=master.yaml --node-config=node.yaml` or `openshift start master --write-config --config=master.yaml` or `openshift start node --write-config config=node.yaml`.
  +The `openshift start` command accepts flags that indicate that it should simply write the config file that it would have used and terminate.  This is useful for getting a starting point for the config.  You can do this by running 
  +*`openshift start --writeconfig --master-config=master.yaml --node-config=node.yaml`
  +* `openshift start master --write-config --config=master.yaml`
  +* `openshift start node --write-config config=node.yaml`
   
   == Use the config files
  -Once you have modified the config file to your liking, you can make use of them by specifying them as an argument.  Keep in mind that if you specify a config file, *none of the other flags you pass in will be respected*.  You can run them like: `openshift start --master-config=master.yaml --node-config=node.yaml` or `openshift start master --config=master.yaml` or `openshift start node config=node.yaml`.
  +Once you have modified the config files to your liking, you can make use of them by specifying them as an argument.  Keep in mind that if you specify a config file, *none of the other flags you pass in will be respected*.  You can run them like: 
  +* `openshift start --master-config=master.yaml --node-config=node.yaml`
  +* `openshift start master --config=master.yaml`
  +* `openshift start node config=node.yaml`
   
   == Stub for discussion of generating the config for a new node
   
  
positive.code:   masterIP: 10.13.137.161
    servicesSubnet: 172.30.17.0/24
    staticNodeNames:
    - deads-dev-01
  masterClients:
    deployerKubeConfig: openshift.local.certificates/openshift-deployer/.kubeconfig
    kubernetesKubeConfig: openshift.local.certificates/kube-client/.kubeconfig
  
negative.code: dnsDomain: local
  dnsIP: 10.13.137.161
  kind: NodeConfig
  masterKubeConfig: openshift.local.certificates/node-hostname.example.org/.kubeconfig
  networkContainerImage: openshift/origin-pod:v0.4.1
  nodeName: hostname.example.org
  recordEvents: false
  servingInfo:
    bindAddress: 0.0.0.0:10250
    certFile: openshift.local.certificates/node-hostname.example.org/server.crt
    clientCA: ""
    keyFile: openshift.local.certificates/node-hostname.example.org/server.key
  volumeDirectory: openshift.local.volumes
  ---
  
  