Bug 1207681

3. What is the nature and description of the request?  

the interface name that is used by RHEV/Ovirt is causing various problems with other software.
";vdsmdummy;" is not a sensible interface name.
the ; characters has to specially escaped for bash and other tools. 

It would save a lot of hassle and work if ovirt would use sensible names. 
I don't see any reason to use special chars in the interfacename.
The reason was to eliminate possible conflicts. This is not a real issue in my view. http://lists.ovirt.org/pipermail/users/2014-November/029392.html

Examples:

Facter: https://access.redhat.com/solutions/799413
https://tickets.puppetlabs.com/browse/FACT-546

spacewalk: https://bugzilla.redhat.com/show_bug.cgi?id=1011049

rkhunter rootkit hunter tool:

+ for FNAME in '${OPT_VALUE}' + test -z
'/dev/.udev/db/net:;vdsmdummy;' ++ echo
'/dev/.udev/db/net:;vdsmdummy;' ++ egrep '(^[./]*$)|[;&]|/\.\./' +
'[' -n '/dev/.udev/db/net:;vdsmdummy;' ']' + ERRCODE=1 + echo
'Invalid ALLOWDEVFILE configuration option: Invalid pathname: 
/dev/.udev/db/net:;vdsmdummy;'

4. Why does the customer need this? (List the business requirements here)  
Prevention of problems with various tools. 
Creates additional work for debugging and workarounds.
Could possibly have side effects as the ; is a command delimiter in bash.
      
5. How would the customer like to achieve this? (List the functional requirements here)  
interface with sensible name without special chars. so output of ifconfig etc can be parsed without special treatment.
      
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 
Just use a standard name like "vdsmdummy" or "ovirt_vdsmdummy"
      
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
Not to my knowledge. But there are other companies that have had problems and additional work because of this.
      
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
No. It's not an urgent, major issue, but one that can create problems in various unexpected places.
      
9. Is the sales team involved in this request and do they have any additional input?  
no
      
10. List any affected packages or components.  
vdsm
      
11. Would the customer be able to assist in testing this functionality if implemented?  
probably, but should not be necessary.