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

Compare with Current View Page History

« Previous Version 10 Next »

Bug Reference

https://issues.apache.org/browse/CLOUDSTACK-6493

Branch

Master, 4.4

Introduction


Purpose

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

References

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 it 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 because Hyper-V can support max of 8 virtual network adapters for the VM.
  • 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
    • 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".

Supported Hypervisor

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

Use cases

User can add VM to networks he had created.

Admin can add the VM to multiple networks

Architecture and Design description

When user/admin wants to his VM to present on multiple networks, AddVMToNetwork feature will allow him to add multiple networks to the VM.

This feature is currently supported on xenserver,kvm,vmware and this FS will add support for Hyper-V 

When user/admin tries to add VM to accessible Networks, then a Nic will be plugged to the VM and nic will be configured. The guest vm will get dhcp ip from the associated VR.

for this feature to work, hypervisor should support hot-nic plug functionality for the vm running on the host.

Hyper-v have the limitation that it cannot support hot-nic plug functionality for the VM in running state.

In Hyper-V a new virtual network adapter can be added to VM only when it is stopped state. 

Hyper-V supports maximum of 8 virtual network adapters (http://technet.microsoft.com/en-us/library/jj680093.aspx).

This feature multiple ips for a vm can be supported only for a VM 

  • During Vm Deployment
  • when VM is in stopped state.

And VM can have maximum of 8 networks due to Hyper-v constraint.

Web Services APIs

No new web services were added.

UI flow

NO change in the UI flow

Appendix

Appendix A:

Appendix B: 

  • No labels