Bug Reference

Branch

Master, 4.4

Introduction

Purpose

This is to support multiple nic's for the guest Vm's running on Hyper-V

References

• Add Remove Networks to VMs

Document History

Glossary

Feature Specifications

This feature is to support multiple network interfaces to guest vm's by following operations

• • Deploy VM with multiple networks
  • Add Network to VM 

Hyper-V have a limitation of dynamically adding NIC to a VM which is in running state. To add a new NIC to a VM on hyper-v it should be in stopped state.

Multiple nic for the VM will be supported only when VM is in stopped state or during VM Deployment.

• list what is deliberately not supported or what the feature will not offer - to clear any prospective ambiguities
  • This feature is supported only when the VM is in stopped state.
  • VM can be added to Max 8 Networks.
• quality risks (test guidelines)
  • functional
    • While deploying the VM,select multiple networks. VM will be created with multiple nics and will have configured guest Vlan's on the nic.
    • When Add network to VM, if the VM is in stopped state it should be successfull
    • When Add network to VM, if the VM is in Running state, Error Message "Vm in Running state cannot be addeded to new network" will be shown 
    • for a VM it can be Max on 8 networks. This is because of the Number of Nic's limitation imposed by Hyper-V
  • corner cases and boundary conditions
  • negative usage scenarios
    • When user tries to Add Network to VM when VM is in running state. Error Message "Vm in Running state cannot be addeded to new network" will be shown.
    • When user tries to Add Network to VM when VM is in stopped state and the number of networks is more than 8, then Error Message "Maximum 8 networks will be supported"  will be shown.

Support-ability Characteristics

Logs can be looked up at the following location

• • 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".

• 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)

Supported Hypervisor

This feature is implemented for Windows Server 2012 R2 and Hyper-V 2012 R2 (Core).

Use cases

listed in Add Remove Networks to VMs feature

Architecture and Design description

• discussion of alternatives amongst design ideas, their resources/time tradeoffs and limitations. Explain why a certain design idea is chosen over others
• highlight architectural patterns being used (queues, async/sync, state machines, etc)
• talk about main algorithms used
• explain what components are being changed and what the dependent components are
• regarding database: talk about tables being added/modified
• performance implications: what are the improvements or risks introduced to capacity, response time, resources usage and other relevant KPIs
• preferably show class diagrams, sequence diagrams and state diagrams
• if possible, publish signatures of all methods classes and interfaces implement, and the explain the object information of different classes

Web Services APIs

list changes to existing web services APIs and new APIs introduced with signatures and throughout documentation

UI flow

• either demonstrate it visually here or link to relevant mockups

IP Clearance

• what dependencies will you be adding to the project?
• are you expecting to include any code developed outside the Apache CloudStack project?

Appendix

Appendix A:

Appendix B: