Bug 781917

Summary: Beaker should generate kickstarts, rather than relying on Cobbler
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: lab controllerAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.8CC: bpeck, dcallagh, mcsontos, rmancy, stl
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-26 06:40:34 UTC Type: ---
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: 800687    
Bug Blocks: 781918    

Description Dan Callaghan 2012-01-16 05:16:45 UTC
Beaker should be able to generate a complete kickstart for a given system, based on the recipe which is currently running on it.

To achieve feature parity and minimal disruption for users, we could use Cheetah and implement a similar system of "snippets" as Cobbler currently gives us. Or we could switch to a different system of kickstart templating, such as Snake templates.

Comment 1 Bill Peck 2012-01-16 15:04:49 UTC
Could we support different templates easily?  have the default be cheetah and allow users to specify different?

First line of snippet or kickstart would specify what template?

##cheetah
or
##snake
or
##foobar

Comment 4 Dan Callaghan 2012-06-26 06:40:34 UTC
Beaker 0.9.0 has been released.