Foreman provisioning strategy

Meaning foreman_tasks or something else?

A few questions for the 1. option:

  • Rollback—What if one of the many actors fails? Does each actor know how to roll back itself and the whole process?
  • If multiple actors are waiting for multiple conditions (aka finished actors), you will need a monitoring controller to decide which actor will run and order the execution.
  • As the actor dependency grows, it could get messy quickly. A graph tool visualizing the relationships between the actors might help.
  • Extension - how can the list of actors (and their deps) be extended from the plugin?

Option no. 2 - images
I posted my summarization in the RFC: Support provisioning with bootable images.

We could use an image builder to generate the images. Sadly, one big downside is that it’s host OS-dependent. For example, you can’t create CentOS images on RHEL.