Support NSX Logical Switch created by NSX-T

[jessehu]

This enhancement is for recognizing NSX Logical Switch created by NSX-T.
Otherwise when a NSX Logical Switch is specified as the network name, it won't find it and create a new Logical Switch with the same name. However, VMs connected to this new Logical Switch cannot get DHCP IP.

[ticobotbot]

Can one of the admins verify this patch?

[jjlimepoint]

This one looks good to me!

[jessehu]

@jjlimepoint can this be merged?

[jjlimepoint]

I can't commit myself, and i think this being in chef-boneyard now means no-one can/will? - I'm chasing up to see what to do from here to get it merged somewhere :).

[jessehu]

Thanks @jjlimepoint ;)
BTW, can chef-provisioning-fog (using fog::vsphere) replace chef-provisioning-vsphere?

[jjlimepoint]

chef-provisioning-fog has long been unmaintained, and is believed to not work - I don't use that myself, ymmv!

I maintain a fork of c-p-vsphere at https://github.com/jjlimepoint/chef-provisioning-vsphere (which we use with our customers and integration test daily), and was advised by chef people that this one will never recieve commit again and that we should just run with that fork - if you're cool, i'm going to merge you're two branches into that, as well as any other PR's you might have, and then I'll try and see how we can get a release out from that forked version (I only have maintainer myself on chef-provisioning and chef-provisioning-aws, sadly)

[jessehu]

@jjlimepoint Sounds like a plan! Let's figure out get a release out from that forked version :)

[jessehu]

It's a pitty that chef-provisioning-fog has long been unmaintained. How about the future plan for chef-provisioning?

[jjlimepoint]

For chef provisioning itself, I'm maintaining it for our customers as a part of my job, and I have commit to the official repo, so that's somewhat better

…

On Tue, Mar 19, 2019, 10:56 PM Jesse Hu ***@***.***> wrote: It's a pitty that chef-provisioning-fog has long been unmaintained. How about the future plan for chef-provisioning? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#97 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AO85KX8hqoyhFvTHpOoMWvQfq8pok2grks5vYc16gaJpZM4bESrH> .

-- *This message is intended only for the confidential use of the intended recipient(s). If you have received this communication in error, please notify the sender by reply e-mail, and delete the original message and any attachments. Any unauthorised disclosure, copying, or distribution of this message (including the attachments), or the taking of any action based on it, is strictly prohibited.*

[jessehu]

That's nice!! I really like chef-provisioning. It's so quick to create a deployment service prototype with chef-provisioning.

[jessehu]

Loop in @jjasghar. Please help. We have problem no merging PR:

I can't commit myself, and i think this being in chef-boneyard now means no-one can/will? - I'm chasing up to see what to do from here to get it merged somewhere :).