Bug 731475

Summary:	RFE: Kickstart -> TDL
Product:	[Retired] CloudForms Cloud Engine	Reporter:	William Henry <whenry>
Component:	imagefactory	Assignee:	Ian McLeod <imcleod>
Status:	CLOSED EOL	QA Contact:	Rehana <aeolus-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.0.0	CC:	akarol, clalance, cpelland, dajohnso, deltacloud-maint, imcleod, kcleveng, morazi, spurrier, ssachdev
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	kcleveng: needinfo? (imcleod)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-02 19:34:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description William Henry 2011-08-17 18:30:59 UTC

Description of problem:

Many of our customers have lots of Kickstart based assets and would like to be able to take advantage of those assets in CloudForms.  It is desirable to have a way of taking information from Kickstart files and generating a TDL xml file.  

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 jrd 2011-08-17 18:51:27 UTC

This is quite a bit more difficult than turning a template into a kickstart.  Mostly because kickstarts have all kinds of things they can do which were intentionally not included in template semantics.

It would help if there were specific use cases and examples cited.  We aspire to make the easy cases easy, but it's not always obvious what that means.

Comment 2 Chris Lalancette 2011-08-17 20:25:07 UTC

Well, there is already some plumbing for this.  In particular, Oz can (optionally) be overridden to use a user-specified kickstart instead of a pre-canned one.  That functionality is not exposed in imagefactory at the moment, though we could add an optional attribute to the QMF build object to allow the user to specify this.

Of course, that does not help in the "snapshot" case, where you are starting from an already existing image.  There, you would have to resort to parsing the kickstart/autounattend/siffile/etc, and executing parts of it that you could.  We certainly could consider doing this, though it is something of a dicey situation; there are certain things we can't change at all (partition tables come to mind), and certain things that we can (%packages, %post, etc), so the user might get a surprise at the end.  It would take more thought to see how useful that would be.

Comment 3 jrd 2011-09-22 19:24:57 UTC

https://www.aeolusproject.org/redmine/issues/2388

We won't be able to deal with this until post 1.0.

Comment 4 wes hayutin 2011-09-22 19:45:57 UTC

moving version to post 1.0

Comment 5 wes hayutin 2011-09-28 16:37:14 UTC

making sure all the bugs are at the right version for future queries

Comment 7 wes hayutin 2012-02-22 23:45:49 UTC

moving version to 1.0.0 .  version = found in version