| Summary: | When creating an "external provider network" in rhevm with vlan tag, the vlan tag disappears from GUI | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | awinter <awinter> | ||||||
| Component: | ovirt-engine-webadmin-portal | Assignee: | Moti Asayag <masayag> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | GenadiC <gcheresh> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.3.0 | CC: | ecohen, iheim, lvernia, masayag, mkolesni, myakove, rbalakri, Rhev-m-bugs, sherold, yeylon | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | ovirt-3.5.0_rc1 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-02-17 17:10:54 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: | |||||||
| Attachments: |
|
||||||||
|
Description
awinter
2013-11-17 13:58:40 UTC
Created attachment 825145 [details]
No vlan tag on net2
Created attachment 825146 [details]
engine.log
(In reply to awinter from comment #0) > Additional info: > When importing a network with vlan tag from a network provider, the vlan IS > visible. I think this behavior should be fixed to "hide" the vlan ID of imported network, since the underlying technology might be gre or vxlan or something else, and basically we don't care what it is when it's managed by oVirt.. So I suggest to change the bug to remove vlan id of imported network. (In reply to Mike Kolesnik from comment #3) > (In reply to awinter from comment #0) > > Additional info: > > When importing a network with vlan tag from a network provider, the vlan IS > > visible. > > I think this behavior should be fixed to "hide" the vlan ID of imported > network, since the underlying technology might be gre or vxlan or something > else, and basically we don't care what it is when it's managed by oVirt.. > > So I suggest to change the bug to remove vlan id of imported network. When creating a network with vlan via rhevm (at the provider), the network in Neutron is created as vlan and not gre/ vxlan (as far as I know). As a rhevm user, I would like to know as much as possible from rhevm (I wouldn't want to look in neutron) so even though the network is external, I think that we should present the vlan ID if there is one. The bug is about creating a new network via rhevm on Neutron, if the user checked vlan ID, I guess he would be happy to see it in the list of networks. Maybe, *when importing*, we can hide the vlan ID but I'm not sure it is the right approach.. Conclusion: * When creating a new network with vlan via *rhevm*, show vlan ID * When *importing a network* show only if the network is vlan (and not gre/vxlan) OR don't show it at all. That is my opinion... (In reply to awinter from comment #4) > When creating a network with vlan via rhevm (at the provider), the network > in Neutron is created as vlan and not gre/ vxlan (as far as I know). > As a rhevm user, I would like to know as much as possible from rhevm (I > wouldn't want to look in neutron) so even though the network is external, I > think that we should present the vlan ID if there is one. Why differentiate between technologies then? > > The bug is about creating a new network via rhevm on Neutron, if the user > checked vlan ID, I guess he would be happy to see it in the list of networks. > > Maybe, *when importing*, we can hide the vlan ID but I'm not sure it is the > right approach.. > > Conclusion: > * When creating a new network with vlan via *rhevm*, show vlan ID > * When *importing a network* show only if the network is vlan (and not > gre/vxlan) OR don't show it at all. > > That is my opinion... I think for sake of a level technology playing field the vlan id should be hid from the webadmin, since it can also be random vlan if you dont specify it (depending on plugin). I think it looks bad as presenting only vlan but not other technology ids... (In reply to Mike Kolesnik from comment #5) > (In reply to awinter from comment #4) > > When creating a network with vlan via rhevm (at the provider), the network > > in Neutron is created as vlan and not gre/ vxlan (as far as I know). > > As a rhevm user, I would like to know as much as possible from rhevm (I > > wouldn't want to look in neutron) so even though the network is external, I > > think that we should present the vlan ID if there is one. > > Why differentiate between technologies then? > > > > > The bug is about creating a new network via rhevm on Neutron, if the user > > checked vlan ID, I guess he would be happy to see it in the list of networks. > > > > Maybe, *when importing*, we can hide the vlan ID but I'm not sure it is the > > right approach.. > > > > Conclusion: > > * When creating a new network with vlan via *rhevm*, show vlan ID > > * When *importing a network* show only if the network is vlan (and not > > gre/vxlan) OR don't show it at all. > > > > That is my opinion... > > I think for sake of a level technology playing field the vlan id should be > hid from the webadmin, since it can also be random vlan if you dont specify > it (depending on plugin). > > I think it looks bad as presenting only vlan but not other technology ids... I agree but just concern that a rhevm admin will *need* this information. We can ask for support of gre and vxlan in rhevm but I don't sure it will be done soon, so, like you said, we should probably hide the vlan id and maybe in the future, we will unhide it. The behavior as far as I'm aware is currently consistent, with VLAN tag never showing for external networks. Should probably be fixed in the future for all "segmentatio" technologies in OpenStack. (In reply to Lior Vernia from comment #9) > The behavior as far as I'm aware is currently consistent, with VLAN tag > never showing for external networks. Should probably be fixed in the future > for all "segmentation" technologies in OpenStack. Indeed, the vlan-tag is not saved for external networks, hence won't appear for external network created from ovirt-engine or imported from neutron. If you create a new network indeed no VLAN is presented. But if you import the network the VLAN field is populated with the value So in order to reproduce the bz just import the network from External provider Verified in 3.5.0-0.0.master.20140804172041.git23b558e.el6 This requires doc_text only if it's not already made clear somewhere else that Neutron network VLAN-tagging isn't exposed in RHEV. rhev 3.5.0 was released. closing. |