https://issues.apache.org/jira/browse/CLOUDSTACK-6106
Master
This is functional specification for Implementing Support of VPC on Hyper-V
use cases listed in Inter-VLAN Routing
When new Tier/new public vlan range/new Private gateway is added to VPC, a new nic will be Hot-Plugged to the VPC VR and it will be configured accordingly.
w.r.t Hyper-V, it cannot support Hot-Nic plug to the VPC VR.Hyper-V can support Max of (8) Virtual Network Adapters.
So to overcome this limitation imposed by Hyper-V. we can create some nics to the VPC during the deployment. We can use the extra nics created to support new VPC elements.
This is how the deployment for VPC will work when running in Hyper-V.
when the VPC is created, VPC VR will be created on Hyper-V with 8 Nics ( 1 public + 1 private + 1 private gateway and 5 extra nics)
When a new tier/new publicvlan/new private gateway is created on VPC, we will find the free extra nic created and use this nic to configure the associated configuration.
When any tier/public vlan range(last ip)/private gateway is deleted in VPC, then the nic configurations will be removed inside the VR and on the VM level.
when all the extra nics are configured and user attempts to create a new tier etc then exception/error message will be thrown/shown to the user and config will be roll backed.
Web Services APIs
NA
NA
Appendix A:
Appendix B: