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):
Steps to Reproduce:
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.
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.
We won't be able to deal with this until post 1.0.
moving version to post 1.0
making sure all the bugs are at the right version for future queries
moving version to 1.0.0 . version = found in version