Auto commit by PR queue bot

Configure lower NFS grace period.

Deleting unused test code

Changed JobSucceded to JobComplete

Update development godep instructions

Add link to create a question tagged Kubernetes on Stack Overflow to the

Clean-up CoreOS documentation.

Reword introduction and requirements for build/README.md

Amend an ordered list markdown error in scratch.md

Updates fedora ansible guide

Change "chmod +X" to "chmod +x" in prereqs.md

Move E2E PD Test out of flaky

Clarify boundaries of Kubernetes.

troubleshooting doc, along with a couple other small improvements.

Fix E2E Test "Pod Disks should schedule a pod w/ a RW PD, remove it, then schedule it on another host" out of flaky

Kubelet: do not remove pod directory if any container is still running

If there are any running container in the pod, we cannot remove the volume.
Therefore, we should not attempt to remove the pod directory.

When calling kubectl.sh, allow error due to API server bouncing

Don't run flaky e2e tests in parallel test runs.

Transfer maintainer responsibilities for fluentd configs/images.

e2e: skip restart count test

https://github.com/kubernetes/contrib.git .

add a fuzz function for expapi.APIVersion

From RFC 3530:
  During the grace period, the server must reject READ and WRITE operations
  and non-reclaim locking requests (i.e., other LOCK and OPEN operations)
  with an error of NFS4ERR_GRACE.

That basically means that all open() calls from clients are blocked until the
grace period is over (90 seconds by default).

We want the grace period as low as possible to speed up the tests. '10'
seconds were tested on Fedora 21 and Ubuntu 15.04 as the hosts.

The test image is rebased to Fedora in order to get 'rpc.nfsd -G <n>' option,
Ubuntu does not support it.

Add patch notes to versioning doc

Moved failing tests to the flaky suite on Jenkins

Change `chmod +X` to `chmod +x`, since `+X` does not take affect when there is no  execute permission bit already set (either user, group or other).

```console
# ls -l /usr/bin/kubectl
-rw-r--r-- 1 root root 14190181 Aug 10 16:16 /usr/bin/kubectl
# chmod +X /usr/bin/kubectl
# ls -l /usr/bin/kubectl
-rw-r--r-- 1 root root 14190181 Aug 10 16:16 /usr/bin/kubectl
```

Please refer to [chmod](https://en.wikipedia.org/wiki/Chmod "chmod") for more details.
>which is not a permission in itself but rather can be used instead of x. It applies execute permissions to directories regardless of their current permissions and **applies execute permissions to a file which already has at least one execute permission bit already set (either user, group or other)**. It is only really useful when used with '+' and usually in combination with the -R option for giving group or other access to a big directory tree without setting execute permission on normal files (such as text files), which would normally happen if you just used "chmod -R a+rx .", whereas with 'X' you can do "chmod -R a+rX ." instead

Amend an ordered list markdown error in scratch.md in section **etcd** by enter a newline after the first sentence

Revert "LimitRange updates for Resource Requirements Requests"

Revert "Bump cadvisor godep"

Revert "Make MASTER_IP_RANGE master-only"