Do you want to generate Beaker jobs from simple JSON template? You're on the right place ...

Hello you brave humans who are trying to use this little script written by me.

Let's start with talking about how does it work. It typically does 3 steps:

1. Load JSON template into internal representation
2. Modify/add/delete some parameters in this internal representation by commands specified as parameters for this script
3. Print XML out.

It should be able to do more things in close future, but it does only these things for now.

./bkr_job_gen.py command1 command2 ... commandN

• load 'json-file' Load JSON template
• print Print out the XML
• kickstart 'file-with-kickstart' Attach kickstart file for specified recipe
• recipe 'seq. number of recipe in recipeset' Select recipe from recipeset for next operations, default 0 (first recipe)
• task 'task-name' Select task with specified name in selected recipe for next operations
• param set|delete 'task-param-name' 'param-value if set' Change parameters passed to tasks
• requires host|distro 'req-name' set|delete 'req-value if set' (format of req-value is: "opvalue", so f.e. "=RHEL-6.3" or ">4096") This speaks for itself, but when using "distro", you don't have to write the "distro" or "distro_" prefix. If you set the key_value tags like HVM, MEMORY or so, use $-prefix -> $HVM, $MEMORY ...
• user 'username' Specify Beaker user name
• pass 'password' Specify Beaker password
• summary Prints out simple summary of the entered XML
• submit-watch Submits the XML into Beaker and starts watching te tasks until closure (or Cancelled) reached
• closure 'taskname' Task which when starts, detaches from the submit-watch operation
• whiteboard 'whiteboard-text' Text used for describing the job

./bkr_job_gen.py load job.json task "/CloudForms/Installation/CloudEngine" param set YUM_RELEASEVER 6.2 task "/distribution/reservesys" param set RESERVETIME 2d recipe 0 (<- this command isn't actually needed, as it is 0 by default) kickstart kickstart.txt requires host hostname set "troll.pc.com" print

./bkr_job_gen.py load job.json task "/CloudForms/Installation/CloudEngine" param set YUM_RELEASEVER 6.2 task "/distribution/reservesys" param set RESERVETIME 2d recipe 0 (<- this command isn't actually needed, as it is 0 by default) kickstart kickstart.txt requires host hostname set "troll.pc.com" summary name "username" pass "password" closure "/some/task" submit-watch

Commands task and recipe don't have to be specified every time using them-dependent commands (param, requires, ...), they are simply valid until overrided with next task or recipe command. Imagine them as simple variables you have available. When you issue load command, all changes you made before are lost and you're starting from clean loaded template.

IMPORTANT THING!!! This thing is imperative, so commands are readed and processed sequentially as they are readed from the parameters. so putting submit-watch in the beginning is not a good idea.

ANOTHER IMPORTANT THING!!! This thing works only pre-made JSON templates, it can't generate new XML from nothing. I decided to make it this way because:

1. JSON is much simpler than XML
2. Tasks used inside some testing suite usually have many common parameters, so it's better to have some basic stuff you can modify (inheritance -> good practice )

• requires delete doesn't work yet, working on it