Hi @UXabre,
If I understand you correctly, it sounds like you’re describing an orchestration tool like Hashicorp’s Terraform, OpenStack’s Heat or AWS’ Cloudformation and to a lesser degree tools like Ansible or Salt. Basically, you want a higher level tool that can describe an application stack and then have it talk to tools like Foreman to have them implement the full application. Is that correct? If so, I think you’ll find that a couple of these tools already have Foreman “providers”. Therefore, the next step in your vision, would be to use one of those tools to create blueprints for common stacks, such as your K8s example.
Now, I’m sorry if I’m hijacking the original intent of your thread, but your comment below really grabbed my attention and since you mentioned it here, it seems fair game to bring this up.
I’m very interested in this comment, because I, and at least a couple of other people, are currently trying to find our way through the installation and configuration of Foreman and Katello. As you say, we’re finding user adoption to be a slow process. As mentioned in another thread, I have been scripting the install, but I’m finding that there is no clearly defined path toward getting a properly functioning Foreman/Katello system up and running. I seem to be repeatedly taking two steps forward and one back. Even the “Success Story” that is buried in the documentation isn’t terribly useful, because there are big holes in it.
I’d really appreciate it if a more seasoned Foreman/Katello user could look over my current install script and help me understand why I’m still not able to successfully provision a new host from Foreman. As you can see from my README, I don’t think I’m being overly ambitious in what I’m trying to accomplish.