Update to latest bosh-utils for Windows fixes

[Fydon]

Newer versions of bosh-utils have fixes for Windows. To do this is running update-deps all that is required?

If not then in order to use the latest version of bosh-utils it seems that the following dependencies are required:

• doublestar
• fs
• gouuid

Also NewWriterLogger only requires two parameters, so main has to be updated.

[DanielJonesEB]

Had a room full of Windows users trying to use BOSH earlier, and got hit by cloudfoundry/bosh#1821.

The BOSH Lite Vagrant solution is deprecated. The lack of a working bosh create-env is a huge barrier to Windows users being able to learn BOSH, and also Concourse by merit of bosh create-env being one of two documented means to get a local Concourse working.

[Fydon]

The way I see it there are two stages to this:

1. getting it working on Windows
2. evaluating how things currently work in light of improving the cross platform experience.

Unfortunately at the moment the amount of time that I can work on this is very limited. I try to work to get more of BOSH working on Windows when I can. I try to make my efforts in helping with stage 1 public for bosh-cli and bosh-virtualbox-cpi-release. I'm using the following:

• tar that comes with git for Windows
• I think the current branch is using the MinGW bash (also comes with git for Windows), but I've also been trying Windows Subsystems for Linux (I've only tried Ubuntu, but I recommend MinGW as there are complications mentioned here)
• RubyInstaller for Window (I'm using 2.3.3) and the Devkit (I see that from Ruby 2.4 it isn't a separate install)
• VirtualBox

Make sure each of those are on your path, e.g. using Powershell either something like the following for Windows Subsystems for Linux (and change changes) $env:PATH = "C:\Windows\System32;C:\Program Files\Oracle\VirtualBox;C:\Program Files (x86)\Git\usr\bin;RUBY_PATH\bin;RUBY_DEV_PATH\bin;RUBY_DEV_PATH\mingw\bin;" + $env:PATH or the following for MinGW bash env:PATH = "D:\Program Files\Oracle\VirtualBox;C:\Program Files (x86)\Git\usr\bin;RUBY_PATH\bin;RUBY_DEV_PATH\bin;RUBY_DEV_PATH\mingw\bin;" + $env:PATH, where you'd need to add your location for RUBY_PATH and RUBY_DEV_PATH.

As those are my development branches, they aren't ready for general usage but they can fork to work for your computer and then generalised to be ready for a pull request.

Currently create-env reaches the point where the first blobs are deployed to the instance, but they fail to start. I'm thinking of using a proxy to try work out what is not working, as I can't seem to log into the instance, so can't see that state of the blob store. I've prevented the clean up from occurring locally and can't see any obvious issues like line ending issues or the incorrect output of ruby templates.

With regard to stage 2, I've tried to write up all the issues as I see them in bosh-notes.

Any help that you or people that you know could contribute to this effort would be greatly appreciated. I'm generally on the Cloud Foundry Slack, so probably ask questions there and I can try to improve this post so that more people can help with this. I could possibly even add this to bosh-notes, but I didn't as my branch is development work rather than stable.

[bosh-admin-bot]

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

[bgandon]

Removing the Stale label, and possibly #20 is updating the dependencies as required.
Re-testing on Windows would be necessary though.

[bosh-admin-bot]

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

[bosh-admin-bot]

This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.