Bug 1788904

Summary: [QE][DOC] Build a custom GPU guest image procedure uses virt-customize instead of using OpenStack's snapshot capabilities.
Product: Red Hat OpenStack Reporter: Rafal Szmigiel <rszmigie>
Component: documentationAssignee: Irina <igallagh>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: low Docs Contact:
Priority: low    
Version: 16.0 (Train)CC: igallagh, jparker, mburns, pkopec
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-08 10:45:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1832341, 1855223, 1855247    

Description Rafal Szmigiel 2020-01-08 10:54:09 UTC
Description of problem:

Our official docs available here https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html/instances_and_images_guide/ch-virtual-gpu#nvidia-build-guest-image engages utils like genisoimage and virt-customize to achieve something what OpenStack has been made for. 

Instead of customising qcow2 image file in-place on Director I think it would be better to re-write the procedure to use OpenStack's capabilities to do it. This would be easier approach and will work better for cases where Director's node is virtualised (avoid nested virtualisation). 

The procedure would be something like the following:
1) Upload stock RHEL image to glance
2) Spin-up an instance from it
3) Register it with RHN
4) Update system and install extra packages
4) Upload NVIDIA drivers there, unarchive and install
5) Prepare gridd.conf file
6) Shutdown the instance
7) Create image from the instance

IMHO this is less hacky approach comparing to preparation of ISO file and shell script to modify qcow2 image. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Sylvain Bauza 2020-01-22 09:12:54 UTC
Given it's just another way to create an image (while there are many other ways to do this as well), do we have a customer asking for it ? 
To make it clear, we wouldn't remove the current way, just adding an alternative.