search

chef-boneyard / chef-provisioning-vsphere

DEPRECATED: A chef-provisioning provisioner for VMware vSphere
MIT License
17 stars 15 forks source link

Decouple chef-provisioning-vsphere and kitchen-vsphere #5

Open jjasghar opened 7 years ago

jjasghar commented 7 years ago

This is to track the progress on figuring out how to do this.

If you are interested, please don't hesitate to comment or post any findings to we can get this done!

image

gaelcolas commented 7 years ago

I'm def. interested and should be able to test kitchen-vsphere driver soon (I'd be using it mainly with kitchen-dsc for Windows machines).

michaeltlombardi commented 7 years ago

@gaelcolas: I've been using the project pretty much exclusively for the kitchen-vsphere driver up to this point. Glad to help out if you have any questions or brick walls.

BenMitchell1979 commented 6 years ago

" Windows provisioned servers need to point to a chef server for the cookbooks since winrm does not support port forwarding and there fore cannot reach back on the chef-zero port to get the local cookbooks."

Can someone help me understand why this is an issue? If I'm provisioning a linked-clone or full-clone in my vSphere environment - why does it require "port forwarding" @ WinRM? The instance will have an IP (via DHCP) just like any other VM I manage over WinRM. It should be just be a matter of providing the required credentials for HTTP WinRM or preconfigure for HTTPS..

Like the above posters - I'm only interested in the kitchen-vsphere piece of this code - so more than willing to help anyway I can.

qubitrenegade commented 6 years ago

Any further movement on this? We are definitely interested in seeing this change!

Thanks!