Comments on: Optimize-VMwarePKS

By: LucD

LucD — Mon, 10 Jun 2019 12:37:34 +0000

Hi Paul,
Thanks for the feedback. On your questions

1. The script will work against all VMs under the PKSCluster you specified. These are not necessarily all PKS VMs if you have multiple PKS clusters.

2. Not exactly sure what you mean with SDDC here, but you limit the scope of the script with the afformentioned PKSServer parameter.

By: Paul Dillon

Paul Dillon — Mon, 10 Jun 2019 12:17:10 +0000

I read that the script will work against every PKS created vm existing in VMWare.
1. Can you confirm my understanding of the scope of impact for this script?
2. For instance, is there a way to limit the scope to a single SDDC in VMWare?

By: Chip Zoller

Chip Zoller — Wed, 03 Apr 2019 20:26:08 +0000

Thanks for bringing up that idea. A couple reasons, mainly, but there are others depending on how customers like to consume things.

1.) This script, because idempotent and if run on a schedule, will ensure ready state is maintained in case a user removes a tag or changes folders inadvertently. It’ll also allow scaling out of masters to update the DRS rule.

2.) Easier visibility since VM extensions have to be created against the API directly.

3.) Quickly modified and extended if other functionality is later desired.

By: AdaptiveThinking

AdaptiveThinking — Wed, 03 Apr 2019 19:56:50 +0000

I’m not sure why you would use Powershell outside of PKS (Opsman) for that.

It would be a lot better to just use the BOSH VM Extensions for DRS, Folders and Tags.
If you do that, BOSH (=PKS) would automatically create all that for new VMs and delete it if it deletes a VM.