Bug 1548804 - [Docs][RFE][Admin]Document ability to select vNIC profiles for templates when registering them from storage domain
Summary: [Docs][RFE][Admin]Document ability to select vNIC profiles for templates when...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Emma Heftman
QA Contact: Avital Pinnick
URL:
Whiteboard: docs-accepted
Depends On: 1507277
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-25 08:52 UTC by Avital Pinnick
Modified: 2019-05-07 12:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-11 15:37:49 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Avital Pinnick 2018-02-25 08:52:51 UTC

Comment 1 Lucy Bopf 2018-03-01 07:19:01 UTC
You can now select vNIC profiles for templates when registering them from a storage domain.

Comment 2 Lucy Bopf 2018-03-01 10:53:00 UTC
Accepting into Beta 3 program and assigning to Emma for review.

Comment 3 Emma Heftman 2018-03-01 12:02:48 UTC
Hi Maor
1. Can you please explain what was the problem that this RFE resolved?

Is it that if you created a template based on a VM that was mapped to a vNIC, this configuration was deleted and therefore the user needed to reassign the vNIC per VM that was subsequently created based on this template?

2. Is there a feature page?

3. What is the significance of the registering them from the storage domain? as opposed to registering them from where?

Thanks!
Emma

Comment 4 Maor 2018-03-01 13:37:27 UTC
Hi Emma, you can take a look in BZ1277675 for refrerence

(In reply to Emma Heftman from comment #3)
> Hi Maor
> 1. Can you please explain what was the problem that this RFE resolved?
> 
> Is it that if you created a template based on a VM that was mapped to a
> vNIC, this configuration was deleted and therefore the user needed to
> reassign the vNIC per VM that was subsequently created based on this
> template?
> 
> 2. Is there a feature page?

Not that I'm aware of

> 
> 3. What is the significance of the registering them from the storage domain?
> as opposed to registering them from where?

(Same for question 1)
This feature allows you to map external VNIC profiles that are defined on an imported Template to the ones that are present in the cluster the Template is going to be imported to.
The previous solution exchanged all external VNIC profiles that were not present in the target cluster with an empty profile, which removed the imported Tempalte's network functionality. Now, after importing a Template from a data domain, the Tempalte is configured properly according to the VNIC profiles that are defined in the target cluster.

> 
> Thanks!
> Emma

Comment 7 eraviv 2018-03-06 11:33:04 UTC
Hi Emma,
In reply to comment 6:

1. IMO step 6 should read:
"For each template in the Import Templates(s) window, ensure the correct target cluster is selected in the Cluster list."

- same as step 6 of "http://file.tlv.redhat.com/~eheftman/bz1548804/html-single/#Importing_Virtual_Machines_from_an_Imported_Data_Storage_Domain"


2. step 7c should read:
"If multiple target clusters are selected in the Import Template(s) window..." 

HTH
Eitan

Comment 9 Emma Heftman 2018-03-06 13:59:15 UTC
Hey Avital

Please review this MR: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/merge_requests/885

Thanks!
Emma


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