bugfix/vyata-dhcp-ip-allocation-issues

[myminseok]

this is the same PR with previous PR that has discarded due to "sign off rule on commit", sorry @carlosonunez-vmw

Hi, @carlosonunez-vmw
this PR address the issues on assigning IP to TKG VMs using the vyos DHCP server.
expected to get IP for each port group from the expected dhcp network on vyos vm. but assigned all IPs from single dhcp-server network. solution is adding vlan on portgroup.

expected:

1) Test VM with portgroup: "tkg_mgmt_pg-192.168.40.1"          should get 192.168.40.200 from vyos DHCP pool "tkg-mgmt-network"
2) Test VM with portgroup: "tkg_workload_pg-192.168.60.1"      should get 192.168.60.200 from vyos DHCP pool tkg-workload-network

actual result

1) Test VM with portgroup: "tkg_mgmt_pg-192.168.40.1"          got 192.168.40.200 from vyos DHCP pool "tkg-mgmt-network"
2) Test VM with portgroup: "tkg_workload_pg-192.168.60.1"      got 192.168.40.201 from vyos DHCP pool tkg-mgmt-network

solution

adding vlan on portgroup

govc host.portgroup.add -vswitch vSwitch0 -vlan=10 "nsx_alb_management_pg-172.16.10.1"
govc host.portgroup.add -vswitch vSwitch0 -vlan=40 "tkg_mgmt_pg-172.16.40.1"
govc host.portgroup.add -vswitch vSwitch0 -vlan=50 "tkg_mgmt_vip_pg-172.16.50.1"
govc host.portgroup.add -vswitch vSwitch0 -vlan=80 "tkg_cluster_vip_pg-172.16.80.1"
govc host.portgroup.add -vswitch vSwitch0 -vlan=70 "tkg_workload_vip_pg-172.16.70.1"
govc host.portgroup.add -vswitch vSwitch0 -vlan=60 "tkg_workload_pg-172.16.60.1"

thank you.