Bug 1061193
| Summary: | Network label name should not be used when associated with the Neutron | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | GenadiC <gcheresh> |
| Component: | ovirt-engine-webadmin | Assignee: | Lior Vernia <lvernia> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | GenadiC <gcheresh> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4 | CC: | bazulay, ecohen, gklein, iheim, masayag, mgoldboi, mpavlik, nyechiel, oblaut, rbalakri, yeylon |
| Target Milestone: | --- | Keywords: | EasyFix, Triaged |
| Target Release: | 3.5.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | network | ||
| Fixed In Version: | ovirt-3.5.0-alpha1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-17 12:44:19 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: | |||
| Bug Blocks: | 1063716 | ||
|
Description
GenadiC
2014-02-04 14:29:39 UTC
Network label in the Ovirt/RHEVM context is a way to update labeled interfaces on the Host with the labeled network instead of using setupNetwork. On the other hand Network label in Neutron context could be a way of labeling specific range of VLANs, so you can have several labels for several VLAN ranges and it has nothing to do with mapping network to Host interfaces an with Ovirt case Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. Nir, do you think its is the same or different? In my view label in Neutron is the same as in oVirt, telling you which network device to use for the VLAN VM networks. The only difference is that neutron label is restricting the VLAN range, while oVirt label currently has no such restriction, but I don't think it merits a different definition. In this specific case, where the network is created on an external provider and the tenant_network_type is vlan, we are using the "label" to create the mapping to the physical network. So I agree with Mike that the concept is generally similar to oVirt Network Labels feature. That said, the "label" itself in this case is not controlled/configured by oVirt, but from Neutron (plugin.ini). My advice is to add a tool-tip to describe the use of Network Label specifically where the logical network is created on external provider, i.e., when "Create on external provider" is checked. This should provide a clearer UX for now, at least until we will conclude our full deployment and configuration solution for Neutron. This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1. This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed. Verified in 3.5.0-0.0.master.20140605145557.git3ddd2de.el6 oVirt 3.5 has been released and should include the fix for this issue. |