Bug 1012881 - [RFE] Allow filling also network prefix to 'netmask' fields of static IP configuration
Summary: [RFE] Allow filling also network prefix to 'netmask' fields of static IP conf...
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Dan Kenigsberg
QA Contact: Meni Yakove
Depends On:
TreeView+ depends on / blocked
Reported: 2013-09-27 10:17 UTC by David Jaša
Modified: 2016-03-09 20:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
This release adds prefix format support. Both netmask and prefix format are now supported in the netmask field of static IP configuration.
Clone Of:
Last Closed: 2016-03-09 20:33:11 UTC
oVirt Team: Network
Target Upstream Version:
nyechiel: Triaged+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0376 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.6.0 2016-03-10 01:20:52 UTC
oVirt gerrit 35144 0 master MERGED common: adding maskValidator util Never
oVirt gerrit 35145 0 master MERGED webadmin: allowing prefix as mask staticIP conf Never
oVirt gerrit 35155 0 master MERGED backend: adding @Mask annotation Never
oVirt gerrit 35410 0 master MERGED backend: integrate @mask to VdsNetworkInterface Never
oVirt gerrit 36529 0 master MERGED backend: allowing mask as prefix Never

Description David Jaša 2013-09-27 10:17:10 UTC
Description of problem:
Using netmasks is cumbersome: they're much longer and harder to remember as opposed to corresponding network prefix. The correct prefix can not be interchanged with correct netmask, conversion is quite straightforward and newer low-level tools work with prefixes natively.
Therefore I propose the "Netmask" fields (and appropriate places in API) to have their heading changed to "Netmask/Prefix" and have them accept integers in 0-32 range as correct prefix values.

This is IMO quite a small change nice leap forward in convenience in environments with statically assigned IP configuration.

Version-Release number of selected component (if applicable):
RHEV 3.3.

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 3 Nir Yechiel 2014-11-13 18:14:18 UTC
Hi Eliraz,

I have a question with regards to the implementation of this; currently there is a netmask field in which the user should enter the subnet mask in dot-decimal notation (x.x.x.x). With this change, are we going to change that and only accept CIDR notation (/xx)? Or the user can fill the info in either way (dot-decimal or CIDR)?


Comment 4 Lior Vernia 2014-11-16 09:22:01 UTC
The current design is to accept either, but always report in dot-decimal format.

Comment 5 Michael Burman 2015-04-28 08:49:59 UTC
Verified on - 3.6.0-0.0.master.20150412172306.git55ba764.el6
with vdsm-4.17.0-632.git19a83a2.el7.x86_64

Comment 8 errata-xmlrpc 2016-03-09 20:33:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.