Bug 1040977

Summary: [RFE] Ability to specify VLAN ID at the time of adding NIC to the VM
Product: Red Hat Enterprise Virtualization Manager Reporter: Dharmit Shah <dshah>
Component: ovirt-engine-webadmin-portalAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: acathrow, ecohen, iheim, lpeer, nyechiel, pbandark, Rhev-m-bugs, sankarshan, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: nyechiel: Triaged+
Hardware: All   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-18 10:02:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dharmit Shah 2013-12-12 12:58:58 UTC
1. Proposed title of this feature request  
Ability to specify VLAN ID at the time of adding NIC to the VM

     
2. What is the nature and description of the request?  
Multiple NICs are to be attached to the VM. RHEVM should provide functionality to provide VLAN ID when a new NIC is being added to the VM.

      
3. Why does the customer need this? (List the business requirements here)  

      
4. How would the customer like to achieve this? (List the functional requirements here)
Same as #2
      
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

      
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
None that I am aware of.
      
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
      
8. Is the sales team involved in this request and do they have any additional input?  
      
9. List any affected packages or components.  
   
10. Would the customer be able to assist in testing this functionality if implemented?  
Yes