Move from vmrun to REST API

[anfernee]

Fusion has a newly designed REST API. It's a better model than current one which is heavily related to vmrun, in terms of

• REST API is the new standard way to control fusion in future, with official support. While vmrun is gradually going to end of life mode
• It's easier to consume as a client
• Current vmrun approach has a lot of hacks, especially those around IP address parsing. Those are not needed when it's officially supported in REST API.

The only problem now is the REST API is only supported in Fusion. However, it's going to be supported in future version of workstation too, and it's fully compatible.

[frapposelli]

The REST API that shipped in Fusion 10 is coming straight off AppCatalyst, I still have the docker machine driver available for it, you can borrow the driver from there: https://github.com/vmware/docker-machine-driver-vmwareappcatalyst/blob/master/driver.go

We also had a swagger spec for it, not sure if it's still current/maintained.

[StefanScherer]

The problem could be that users run into a problem as they have to activate the REST API first.
But I agree, for a WSL environment it would be much simpler to use the localhost connection from WSL to contact VMware Workstation running outside WSL directly on Windows 10.