So Foreman gives you two use-cases for ansible integration. The first is configuration management like with puppet, the second is arbitrary remote execution. I suppose you’re most interested in the first one.
Of course the main difference between puppet and ansible is, there’s no daemon that would rerun the configuration. There are 2 ways you can get the similar behaviour though in Foreman.
A) You can setup recurring execution of running ansible roles. If you go to the invocation form, you can select the recurring, see attached screenshot.
B) you can setup cron to trigger the same through API
The limitation is that if host is offline, the job will fail and it’s status will turn red. Once it comes back online and ansible run is triggered again, it comes back green. There’s no “ignore the failure I know the host is down” feature atm. You can disable host reporting so you won’t receive configuration report for such host at least. Good thing is, that at least the interval for “host out of sync” can be adjusted via settings, so you can define what is your expected ansible rerun interval.