VPC support on Hyper-V

Bug Reference

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

Branch

Master, 4.4

Introduction

Purpose

This is functional specification for Implementing Support of VPC on Hyper-V

References

• Inter-VLAN Routing 

Document History

Glossary

Feature Specifications

• Currently VPC support is already available for Xen, VMware, KVM. In 4.3 Hyper-V Hypervisor support is added to cloudstack. This feature is to support VPC on Hyper-V hypervisor.
  In the current implementation of VPC the following features are supported.
  • Management of Tiers/networks
  • New Public IP ranges (tagged/untagged)
  • Private Gateway.
  All the above functionality will be supported for VPC VR running on Hyper-V.
  quality risks (test guidelines)

Functional:

• All existing functionality test cases for VPC should pass
  
• only max of 8 vpc services (tiers, private gateway, different public vlan) are suported
• VPC VR will be created with 8 nics up front.
• when new service is created and fails to configure the virtual nic, then "Fail to hot plug" error will be shown

Corner cases and boundary conditions : existing  test cases should pass.

Negative usage scenarios:

• Existing Negative test cases should pass.
• when services limit reaches 8 and user tries to create any service it will show exception message "Max limit is reached"

Use cases

use cases listed in Inter-VLAN Routing 

Architecture and Design description

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, VPC VR will be deployed with extra nics.

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 by default with 8 Nics.

first nic will be configure with control IP

Second Nic will be configured with public ip

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.

These extra nics will be used to 

it will be  we can create some nics to the VPC during the deployment. We can use the extra nics created to support new VPC elements.

Web Services APIs

NA

UI flow

• NA 

IP Clearance

  NA 

Appendix

Appendix A:

Appendix B: