Windows documentation and related code changes #754
Conversation
triggers
commented
Oct 19, 2015
triggers
commented
- Reorganized scripts and resources into separate directories
- Added Windows documentation: docs/content/usage/windows-machine-images.md
- (building, installing, configuring, and using Windows images)
- Major refactoring of the Window build scripts
- Flattened build steps into one layer
- Made new distinction between easy-to-automate and manual build steps
- Added manual actions as explicit build steps
- Renamed build steps to less ad-hoc and maybe more-readable
- Replaced supernext.sh with (refactored) auto-windows-image-build.sh
- Added code to help in recording VNC streams for KVM UI automation
- Fixed intermittent but with extra mouse click to raise PowerShell window
- Added code to generate vdc-manage commands for registering a specific Windows image
- Moved *.ps1 files to wakame-init directory
- Fixed unrelated typo :-)
…ot-with-install-iso...
|
The first thing that I see is that the example build log was added to the Usage menu on the left. I think an example log is a great idea but it shouldn't be in that menu. It should be a link in the Windows Machine Images guide. Full disclosure: I write this before having reviewed the actual Windows Machine Images guide itself. |
|
The Usage menu on the left currently has Perhaps it would be a better idea to make a new section called |
| @@ -0,0 +1,383 @@ | |||
| ## Overview | |||
|
|
|||
| Wakame has functionality | |||
There was a problem hiding this comment.
In official documentation like this, we should always refer to Wakame as Wakame-vdc. This of course goes for the rest of the guide too.
Starting a newline after functionality is probably a mistake too although it seems to show up as one paragraph in mkdocs.
|
When using specific terms like instance or seed image, you should make them links to the jargon dictionary. Of course if you use the word instance ten times in a paragraph, you don't need to make ten links. I'll leave the correct amount of links to common sense. :) |
|
|
||
| For creating seed images, certain steps are necessary to make installations of Windows compatible with Wakame-vdc. The main requirement is that virtio drivers must be installed, because Windows instances are always run in KVM virtual machines. To make working with multiple instances possible, a special initialization script must also be installed, so that Wakame-vdc can coordinate with the Windows OS. | ||
|
|
||
| When launching new instances, Microsoft requires that its Windows sysprep utility be used. This requirement affects both seed image creation and how instances are launched and backed up. In addition, there are various configuration options that can be set when starting Windows instances, such as initial passwords, firewall options, product keys, and automatic activation. |
There was a problem hiding this comment.
Maybe a link to sysprep here. https://technet.microsoft.com/en-us/library/cc721940(v=ws.10).aspx
