Bug 1309957
Summary: | [RFE] Support ovs-vsctl auto attach in RHEV | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Bryan Yount <byount> |
Component: | RFEs | Assignee: | Scott Herold <sherold> |
Status: | CLOSED WONTFIX | QA Contact: | Gil Klein <gklein> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | byount, gklein, lsurette, mburman, rbalakri, yeylon, ykaul, ylavi |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-27 11:20:44 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: | |
Embargoed: | |||
Bug Depends On: | 1195208 | ||
Bug Blocks: |
Description
Bryan Yount
2016-02-19 05:42:20 UTC
I'm not sure why the customer need to control OVS functionality directly. Can you describe the use case? We do plan to switch from bridge to openvswitch networking in 4.0 - what exactly is needed in addition? (In reply to Yaniv Kaul from comment #2) > I'm not sure why the customer need to control OVS functionality directly. > Can you describe the use case? We do plan to switch from bridge to > openvswitch networking in 4.0 - what exactly is needed in addition? Primarily this RFE is to enable RHEV-M (via a restAPI call) to perform the auto attach commands that are available via ovs-vsctl: add-aa-mapping BRIDGE I-SID VLAN add Auto Attach mapping to BRIDGE del-aa-mapping BRIDGE I-SID VLAN delete Auto Attach mapping VLAN from BRIDGE get-aa-mapping BRIDGE get Auto Attach mappings from BRIDGE Example flow: 1. On physical fabric switch, someone changes I-SID 20 to I-SID 22. AFO notices this change. 2. AFO goes to RHEV and says “which hypervisors are using I-SID 20?” 3. AFO makes call to RHEV-M to change I-SID 20 to 22 on the above hypervisor(s). 4. In theory, RHEV-M would then make a call to vdsm to perform ovs-vsctl del-aa-mapping BRIDGE 20 <VLAN_ID>, add-aa-mapping BRIDGE 22 <VLAN_ID>. |