Page History

...

Glossary

Feature Specifications

• put a summary or a brief description of the feature in question 
• 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. Currently VPC support is already available for Xen, VMware, KVM.
• list what is deliberately not supported or what the feature will not offer - to clear any prospective ambiguities
• 
  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.list all open items or unresolved issues the developer is unable to decide about without further discussion
  quality risks (test guidelines)functional
  
  • non functional: performance, scalability, stability, overload scenarios, etcfunctional: existing functionality test cases should pass.
  • corner cases and boundary conditions : existing  test cases should pass.
  • negative usage scenarios
• specify supportability characteristics:
  • what new logging (or at least the important one) is introduced
  • how to debug and troubleshoot
  • what are the audit events 
  • list JMX interfaces
  • graceful failure and recovery scenarios
  • possible fallback or work around route if feature does not work as expected, if those workarounds do exist ofcourse.
  • if feature depends other run-time environment related requirements, provide sanity check list for support people to run
• explain configuration characteristics:
  • configuration parameters or files introduced/changed
  • branding parameters or files introduced/changed
  • highlight parameters for performance tweaking
  • highlight how installation/upgrade scenarios change
• deployment requirements (fresh install vs. upgrade) if any
• system requirements: memory, CPU, desk space, etc
• interoperability and compatibility requirements:
  • OS
  • xenserver, hypervisors
  • storage, networks, other
• list localization and internationalization specifications 
• explain the impact and possible upgrade/migration solution introduced by the feature 
• explain performance & scalability implications when feature is used from small scale to large scale
• explain security specifications
  • list your evaluation of possible security attacks against the feature and the answers in your design* *
• explain marketing specifications
• explain levels or types of users communities of this feature (e.g. admin, user, etc)
  • : 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 

...