Implementing VPC on Hyper-V Hypervisor

JIRA id: https://issues.apache.org/jira/browse/CLOUDSTACK-6106 

Supporting VPC on Hyper-V requires Supporting VPC VR on Hyper-V.

VPC feature is already supported in other cloudstack supported hypervisors. 

There is a limitation in Hyper-V that it cannot support Hot-Nic plug support for linux guests.

This is required for VPC, because whenever a new tier is added we plug a new nic to the VPC VR and configure the new NIC attached to the VR.

As HOT-NIC plug is not supported for the VR on Hyper-V, we will upfront create dummy number of nics.

The number can be configurable from global config (hyperv.vpc.maxtier) and default value will be 3 and max value will be 5. So we can support max of 5 tiers for a VPC.

When a new tier is added, we will find an empty nic and then configure the nic externally and internally.

when a tier is removed, then the nic for the tier will be configured

Regarding public ip support in VPC VR,

by default one nic will be plugged for the public nic acquired while deploying the vpc vr.

for supporting the multiple tagged public vlan, it requires hot nic plug support  so same above approach is followed.

The number can be configurable from global config (router.extra.public.nics) and default value will be 2 and max value will be 5.

Unit Tests:

Existing unit tests will be able to test the feature.

Support of iSCSI as Primary Datastore in Hyper-V

Network throttling for the VMs

JIRA ID: https://issues.apache.org/jira/browse/CLOUDSTACK-6108 

Hyperv  supports specifying the Bandwidth management on the NIC cards attached to the VMs

Currently when VM's are deployed on the Hyper-V, network rate specified by cloudstack is not getting applied.

This feature will take the network rate limit from the cloudstack command, and it will apply the rate limit on the NIC card attached to the VM's

Vm can be guest vm or the systemvm.

Unit Tests:

Existing unit tests will be able to test the feature.