Managing compose from multiple parts¶
There may be cases where it makes sense to split a big compose into separate parts, but create a compose output that links all output into one familiar structure.
The pungi-orchestrate tools allows that.
It works with an INI-style configuration file. The
contains information about identity of the main compose. Other sections define
The parts are scheduled to run in parallel, with the minimal amount of serialization. The final compose directory will contain hard-links to the files.
Path to directory where the final compose should be created.
Type of compose to make.
Name of the product for the final compose.
Short name of the product for the final compose.
Version of the product for the final compose.
Type of the product for the final compose.
Additional arguments that will be passed to the child Pungi processes.
If specified, a current event will be retrieved from the Koji instance and used for all parts.
If set to yes, a kerberos ticket will be automatically created at the start. Set keytab and principal as well.
Path to keytab file used to create the kerberos ticket.
Kerberos principal for the ticket
Commands to execute before first part is started. Can contain multiple commands on separate lines.
Commands to execute after the last part finishes and final status is updated. Can contain multiple commands on separate lines.
post_compose_script = compose-latest-symlink $COMPOSE_PATH custom-post-compose-script.sh
Multiple environment variables are defined for the scripts:
YESfor layered products, empty otherwise
BASE_PRODUCT_NAME– only set for layered products
BASE_PRODUCT_SHORT– only set for layered products
BASE_PRODUCT_VERSION– only set for layered products
BASE_PRODUCT_TYPE– only set for layered products
Executable name (or path to a script) that will be used to send a message once the compose is finished. In order for a valid URL to be included in the message, at least one part must configure path translation that would apply to location of main compose.
Only two messages will be sent, one for start and one for finish (either successful or not).
Partial compose settings¶
Each part should have a separate section in the config file.
It can specify these options:
Path to configuration file that describes this part. If relative, it is resolved relative to the file with parts configuration.
- just_phase, skip_phase
Customize which phases should run for this part.
A comma separated list of other parts that must be finished before this part starts.
A boolean toggle to mark a part as failable. A failure in such part will mark the final compose as incomplete, but still successful.