You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Bug Reference

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

Branch

Master

Introduction

Purpose

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

References

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: existing functionality test cases should pass.
    • corner cases and boundary conditions : existing  test cases should pass.
    • negative usage scenarios: existing functionality test cases should pass. 

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 to add 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.


Web Services APIs

NA

UI flow

  • NA 

IP Clearance

  NA 

Appendix

Appendix A:

Appendix B:

  • No labels