Bug 1075511

The PRD bug relevant to this issue is here:

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

See also this bug, which does not require documentation but does provide more information about why a predictable vNIC order is desirable:

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

(Spoiler: the old way, RHEV often tried to boot from the wrong NIC, and it had to timeout before booting commenced from the correct NIC.)

Fixed in 8942.

Documentation Link
------------------------------
http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Technical_Guide/index.html#Virtual_Network_Interface_Controller_VNIC

What Changed
------------------------------
The following topic was revised to re-write the first three paragraphs to include a description of how network interface card order is regulated in a Red Hat Enterprise Virtualization environment.

Virtual Network Interface Cards [8942-628365]

Updated revision history: [30107-628366]

NVR
------------------------------
Red_Hat_Enterprise_Virtualization-Technical_Guide-3.4-en-US-3.4-7

Moving to ON_QA.

Andrew I think "ifconfig" command is actually deprecated in favor of "ip" command. This at least is valid for RHEL 7 where ip command is default way of getting NIC configuration. Don't we want to mention this in: 

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Technical_Guide/index.html#Virtual_Network_Interface_Controller_VNIC

Given the fact we're supposed to support RHEL 7 in 3.4 we should make sure we use the preferred commands for given OS family, aren't we?

Hi Tomas,

Thank you for your input.

You raise a very good point - I will update the command to use the 'ip' command and will look through the other guides to see if there are any other instances.
I will also investigate other RHEL7-based changes that might be required.

In regards to what we should replace 'ifconfig' with, do you think the standard 'ip addr show' command will do, or is there another, preferred command that I can use?

Kind regards,

Andrew

changing state to assigned as comment 6 suggests docs is not ready for QA

Revised in 8942.

Documentation Link
------------------------------
https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5-Beta/html-single/Technical_Guide/index.html#Virtual_Network_Interface_Controller_VNIC

What Changed
------------------------------
The following topic was revised in accordance with the advice in comment #5.
This involved editing the mention of the 'ifconfig' command and updating the STDOUT to reflect that when running 'ip addr show'.

Virtual Network Interface Cards [8942-668837]

Updated revision history: [34616-651639]

NVR
------------------------------
Red_Hat_Enterprise_Virtualization-Technical_Guide-3.5-Beta-en-US-3.5-3

Moving to ON_QA.

There should be link or reference to Sealing linux vm- http://www.ovirt.org/Sealing_Linux_VM
on the-http://www.ovirt.org/Feature/Predictable_vNIC_Order
For creating vm from template.

Hi Michael,

Thank you for your comment.

What kind of content are you seeking? The above topic is a conceptual overview of how predictable vNIC order operates, and also touches upon the interaction with templates.

Is there a need to include a link to the sealing procedure? I am just unsure as to how the two would come together.

Kind regards,

Andrew

Hi andrew, 

Because i was testing this feature, i can tell that it's an important information, when you want to import vm from template. 
If you make a vm template without the sealing procedure, you will lose the predictable vNIC order, and it's why i think, that in some way it's a part of the Predictable vNIC order feature. 

If the above topic also touches upon the interaction with templates, so information(link or reference) about sealing procedure should be included.
This is my opinion.

Kind regards,

Michael

this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Cancelling needinfo request.

The content for this bug is now included in the Red Hat Enterprise Virtualization 3.5 documentation on the Customer Portal.

Separate bugs shall be raised to address any further requests with regards to this topic.

Closing.