Deploy k8s to vSphere

This change adds support for deploying kubernetes to a vSphere instance (either ESXi or vCenter).
Either way is fine with me.  We generally squash before the final commit,
but in the interim, additional commits are fine.

Thanks
--brendan


On Mon, Aug 25, 2014 at 9:57 AM, Joe Beda <notifications@github.com> wrote:

> In cluster/saltbase/salt/static-routes/init.sls:
>
> > +  file.managed:
> > +    - source: salt://static-routes/if-up
> > +    - template: jinja
> > +    - user: root
> > +    - group: root
> > +    - mode: 755
> > +
> > +/etc/network/if-down.d/static-routes:
> > +  file.managed:
> > +    - source: salt://static-routes/if-down
> > +    - template: jinja
> > +    - user: root
> > +    - group: root
> > +    - mode: 755
> > +
> > +refresh routes:
>
> Looks strange to have a space here. YAML is a complex and confusing
> format. I'd name this refresh-routes.sh or something.
>
> In any case, I *think* the name ("refresh routes") is the name used to
> download and stage the script locally. Not sure where salt puts it. When
> doing stuff like this I often look for other examples to copy from on
> github:
> https://github.com/search?utf8=%E2%9C%93&q=cmd.wait_script+extension%3Asls
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1011/files#r16665925>
> .
>