VPC support on Hyper-V

Bug Reference

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

Branch

4.4, Master

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 Nic" error will be shown
• When a tier/private gateway has to be created, if there is an error while modifying the VPC VR Nic, then the command will be failed and database changes will be roll-backed.
• When a tier/private gateway got created successfully, then the vlan specified by the CS will be assigned on the NIC and internally associated eth device will be configured and will be in "UP" state.
• When a tier/private gateway got removed successfully, then vlan will be removed on the VR NIC and associated eth device will be configured to  "down" state.

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"

Support-ability Characteristics

Logs can be looked up at the following location

• Management server logs for VPC commands will be logged in management-server.log and vmops.log(dev setup). All the requests forwarded to the Hyper-V agent can also be seen here.
• The Hyper-V agent logs can be seen in windows event viewer on the respective hosts. The logs can be filtered by source "CloudStack Hyper-V Agent".
• Hyper-V specific logs can be viewed in the event viewer under "Application and Services Logs" >> Microsoft >> Windows >> "Hyper-V-VMMS".

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.

Web Services APIs

No new web apis were added

UI flow

No change in the UI Flow

IP Clearance

  NA 

Appendix

Appendix A:

Appendix B: