Enhancing Foreman Community Demos: Suggestions for Improvement

Nofar, let me start by saying this is a great effort.

I volunteer to demo some use cases. Do you already have some topics in mind? Few that comes to my mind:

  • adding hosts to the Foreman inventory (registration and other means, perhaps each can be separate)
  • various kinds of provisioning (baremetal, discovery, bootdisks, compute resources, image based provisioning), customizing provisioning templates through parameters and template editor
  • compliance enforcement through openscap integration
  • running custom script/task on hosts
  • tweaking Foreman behavior through settings
  • configuration of hosts through ansible roles
  • configuration of hosts through puppet modules
  • investigating infrastructure through dashboard capabilities
  • managing Foreman templates in external git repository
  • searching through out the inventory
  • mirroring some repository and maintaining a local copy
  • versioning of the content

It may be good to have some structure, this was just a quick brainstorming.

Also there’s probably many more. I think such recordings will reveal the what is possible to do with Foreman to users but also will help the developers to better understand more use cases from other parts of the ecosystem.

Did you already find some co-host? And if so, would it make sense to have more than one in case one of you is unavailable?

The guidance document is a good list of things to consider and focus on during the demos. Thanks for putting it together. Do you have some thoughts on where to have this information stored so people can link to it and potentially update it in future easily?

2 Likes