chef/kitchen-vcenter

Attach multiple networks to a VM

cattywampus opened this issue · 3 comments

Describe the Enhancement

When creating a VM using the vCenter driver for Kitchen I want to be able to set more than one network

Describe the Need

This is a requirement for how we build and test cookbooks for one of my customers. Many of our servers that we build and configure with Chef are attached to multiple networks and it's important that we're able to test our cookbooks setup managed services on specific network interfaces, which we can test for with InSpec.

In YAML, I would expect users to be able to provide the network names they want to attach to their VM using an array, like this:

network_name:
  - Network_1
  - Network_2

Since this is already in use that change would break compatibility with a lot of users so it should be smart enough to support the array notation for multiple networks as above in addition to specifying a single network as before:

network_name: "Network_1"

Current Alternative

The only alternative option we have to accomplish this is to use the unsupported chef-provisioner-vsphere driver.

In addition to it not being supported, it's also not compatible with the new version of Test Kitchen, which makes it impossible for my team up upgrade to Chef Workstation. As a result we are locked into using ChefDK for the foreseeable future until this is supported.

Can We Help You Implement This?

Absolutely! I have aspirations of working on this and want to contribute to this, but if Chef or someone else beats me to it I would be just as happy to have it finished. Would also be willing to collaborate with anyone too, which would probably motivate me to dedicate time to give it attention.

Hello. The customer is asking for a status on this. Can you let us know where we are with this, please?

Thanks,
Alan

JKD9 commented

Hello - talked to the customer today - any updates about this that I can share?

@cattywampus @JKD9 this is addressed via #172