* Using Fedora 21 as the base box
* Discover the active network interfaces in the box to avoid hardcoding
them in configuration.
* Use the master IP for the certificate.
Amend two markdown errors in authentication.md.
1, amend order list display error by enter a newline after the first sentence
2, add two backticks to make ``"@`date +%s`"`` display correctly
gunk when installing the google-fluentd agent.
Also let it log things by not redirecting to a file within the container
and only using -q (warning logs only) rather than -qq (error logs only).
A small bug from #11941: When we push to GCS, we were pushing bucket
names that matched the old pattern `git describe`, e.g.:
gs://kubernetes-release/ci/v1.1.0-alpha.0-2413-g986d37d/
But after #11941, the binaries inside these actually have versions that look like:
v1.1.0-alpha.0.2413+g986d37d
to more closely match up with semver.
This pull makes the GCS directory match the binaries it's already serving.
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.
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
Allow the user to specify the resolver configuration file that is used
to determine the default DNS parameters. This defaults to the system's
/etc/resolv.conf.
