pivotal-cf / docs-pcf-windows

VMware Tanzu Application Service for VMs [Windows]

This repository contains content for VMware Tanzu Application Service for VMs [Windows]. This content is published as part of the following documentation set: [TAS for VMs documentation](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/<% vars.current_major_version %>/tas-for-vms/concepts-overview.html).

The book repository that contains publishing metadata for this content is https://github.com/pivotal-cf/docs-book-application-service.

This book is now published using DocWorks and DocsDash.

Branch map

Branch	TAS version	Doc Link
master	TAS 7.0	TAS v7.0 staging
6.0	TAS 6.0	TAS v6.0
5.0	TAS 5.0	TAS v5.0
4.0	TAS v4.0	TAS v4.0
3.0	TAS v3.0 (EOGS)	TAS v3.0
2.13	TAS v2.13	TAS v2.13
2.12	TAS v2.12 (EOGS)	TAS v2.12
2.11	TAS v2.11	TAS v2.11

docs-pcf-windows's Issues

Stemcell virtual machine recommendations don't match VM Types

docs-pcf-windows/docs-content/index.html.md.erb

Line 24 in b6c8174

The recommended resource requirements for each Windows cell deployed by PCF Runtime for Windows are as follows:

The default recommendations for the Windows Stemcell does not match the available vm types in OpsMan (resource config). The doc lists 4/16/64, but the p-windows-runtime can't match it.

For what it's worth, I'd like to see better consistency within the vm types, but that's a whole 'nutha ball of wax.

Link to docs.pivotal.io for "building a vsphere stemcell"

The link in step 10. for building the vSphere Windows stemcell goes off to github. It should go to https://docs.pivotal.io/pivotalcf/1-11/windows/vsphere-stemcell-build.html instead.

Please configure GITBOT

Pivotal uses GITBOT to synchronize Github issues and pull requests with Pivotal Tracker.
Please add your new repo to the GITBOT config-production.yml in the Gitbot configuration repo.
If you don't have access you can send an ask ticket to the CF admins. We prefer teams to submit their changes via a pull request.

Steps:

• Fork this repo: cfgitbot-config
• Add your project to config-production.yml file
• Submit a PR

If there are any questions, please reach out to [email protected].

Page about Azure should specify HWC Buildpack errand VM size

On this page: https://docs.pivotal.io/pivotalcf/1-11/windows/azure-light-stemcell.html

Under "Requirements," Step 4 should read:

"Ensure that the Install HWC Buildpack Errand also has a VM disk size of 128GB or more."

Test

Trying to deploy PCF with Windows on AWS - is vsphere required?

According to this: https://docs.pivotal.io/pivotalcf/1-8/windows/build-stemcell.html
It seems that I need a vSphere install in order to build the windows stemcell required to deploy pcf with Windows on AWS. This strikes me as very backward. We use aws to avoid having to run vsphere locally. Do I have to spin up vsphere just to generate the image? Why not use aws snapshots, virtualbox or any other method? #stuck.

Page "Azure Light Stemcell Activation" should read "Deploying on Azure"

This is really a general doc page about deploying on Azure. Also, the light stemcell isn't "activated;" I don't think that term has meaning in this context.

Additional instructions for escaped passwords on Windows

Instructions exist for Linux, not Windows. Creating this issue so I have an issue number. I shall send a PR soon.

Stembuild port not specified as a requirement

On https://github.com/pivotal-cf/docs-pcf-windows/blob/2.7/docs-content/create-vsphere-stemcell-automatically.html.md.erb we never indicate which ports needs to be accessible for the stembuild construct process to work. We’ll need access from the jumpbox to the cloned instance on port 5985 per this repo. I wasn’t sure where to put it in a PR, so thought I would let you professional documentarians decide.