Bug 1212911

Summary:	[RFE] [instack-undercloud] [CLI] Separate image building process into 2 parts
Product:	[Community] RDO	Reporter:	Jaromir Coufal <jcoufal>
Component:	rdo-manager-cli	Assignee:	Ana Krivokapic <akrivoka>
Status:	CLOSED WONTFIX	QA Contact:	yeylon <yeylon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	trunk	CC:	jslagle, mburns, srevivo
Target Milestone:	---	Keywords:	RFE, Triaged
Target Release:	Kilo
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-18 11:07:12 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:

Description Jaromir Coufal 2015-04-17 16:11:35 UTC

At the moment we are building discovery, deploy and overcloud images all at once. Then we face user to deal with uploading all images at one step.

User should not be exposed to discovery/deploy images. This should happen automatically for the user during undercloud installation as post-config step, so that undercloud is usable for him.

Once user installs undercloud (and have discovery & deploy images at their place) he should be able to build / download / create overcloud images (by overcloud images I mean overcloud-full.*). This is what user should deal with.

For this we will need to separate building process for discovery+deploy and for overcloud images. Furthermore we need to move the discovery+deploy part into instack-install-undercloud.

This affects both instack-undercloud as well as unified CLI.

Comment 1 James Slagle 2015-05-12 21:31:15 UTC

you can already build images separately via instack-build-images:

instack-build-images overcloud-full
instack-build-image discovery-ramdisk
instack-build-images deploy-ramdisk

we don't want to add image building as part of undercloud installation. they're logically separate tasks. for someone who wants to do it all in one step, it's 3 lines of automation (and they'd probably do a lot more as well). But I don't think we need the tight coupling in our tooling, we already easily enable this if it's desired.

Comment 2 Ana Krivokapic 2015-06-18 11:07:12 UTC

Agree with Slagle here. We support building images individually or in bulk, that should suffice.

Comment 3 Mike Burns 2015-06-18 11:09:34 UTC

I know it's closed, but there has been talk of providing pre-built images so people don't have to build them making the image build step optional.  I'd definitely vote for keeping them separate.

Comment 4 Ana Krivokapic 2015-06-18 11:34:00 UTC

We already have separate commands for building and uploading images: "openstack overcloud image build" and "openstack overcloud image upload". So if you have pre-built images, you would simply skip "openstack overcloud image build" and only run "openstack overcloud image upload".

This bug was about separating the building process for discovery+deploy and for overcloud images and moving building of discovery+deploy to undercloud installation. I think Slagle explained pretty well why this is not a good idea.