Fix kubecfg.sh
apiserver listen on 0.0.0.0 in vagrant
Delete should use current node, not prev node index

The index an object was deleted on should be resp.Node.ModifiedIndex
Change CreationTimestamp to a util.Time and set in each storage implementation

Because time.Time doesn't work correctly with our YAML package, it is necessary
to introduce a type, util.Time, which serializes correctly to JSON and YAML.

Eventually we would like timestamping to cut across storage implementations;
for now, we set it in each storage.
Remove unreachable code.
Pass obj with lock by reference.  Methods->funcs.
Fixes "lock passed by value" issues raised by "go vet".
Return not required after panic.
Suggested by "go vet".
Merge pull request #902 from jbeda/e2efix

Fix e2e teardown
Merge pull request #856 from pmorie/workaround-timestamp

Set CreationTimestamp in each storage implementation
Merge pull request #901 from erictune/cleanup3

Remove unreachable code.
Merge pull request #903 from erictune/cleanup4

Pass obj with lock by reference.
Merge pull request #904 from erictune/cleanup5

Return not required after panic.
Merge pull request #886 from brendandburns/shell_sucks

Fix kubecfg.sh
Merge pull request #867 from derekwaynecarr/apiserver_loopback

Vagrant: apiserver doesn't bind to 127.0.0.1, inaccessible through master nginx
Merge pull request #896 from smarterclayton/return_correct_index_for_delete

Delete should use current node, not prev node index
Allow kubecfg to parse other types via initialization map
Merge pull request #888 from csrwng/pluggable_type_parsing

Allow kubecfg to parse other types via register function
Remove a print that is confusing jq in the e2e tests.
Merge pull request #908 from brendandburns/time

Remove a print that is confusing jq in the e2e tests.
Watch should start from next index when getting the initial state

Also, the fake response we return should have an Action that is
appropriate for the operation.