Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1255408

Summary:	[RFE] New network interface dialog - show a mac from pool by default
Product:	[oVirt] ovirt-engine	Reporter:	Jiri Belka <jbelka>
Component:	Frontend.WebAdmin	Assignee:	Nobody <nobody>
Status:	CLOSED DEFERRED	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs, danken, ecohen, gklein, lsurette, rbalakri, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-07 16:06:58 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:

Description Jiri Belka 2015-08-20 13:46:21 UTC

Description of problem:
We work in an environment where there's often issue with duplicated hwaddr in physical network. This is caused by people having engines with default mac pool ranges.

One cool thing - not fully related to the statement above! - could be to see mac range pool hwaddr in 'New network interface dialog'.

Thus:
- new network interface dialog
- in grey box, there should be written a random hwaddr from current mac pool range written in grey color
- switching custom mac address would cause the random hwaddr from current pool range disappear and the box should be just white for inserting user defined hwaddr

Version-Release number of selected component (if applicable):
3.6.0-9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
why? seeing this hwaddr in grey box could remind our great QE that they are using (same) default mac pool range :)

Comment 1 Dan Kenigsberg 2015-12-07 16:06:58 UTC

Providing a hint on how a vNIC mac address would look like sounds indeed quite handy.

However, implementing this would require the frontend to allocate the sample mac address temporarily, and deallocate it immediately (backend would need to make sure that the frontend did not die in between, or otherwise the address would leak).

This seems a bit to complex for a nice-to-have-feature.