Project

General

Profile

Feature #8130

Add support of async puppet / chef report processing

Added by Romain Vrignaud almost 6 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hello,
When using foreman_chef with a few nodes, we really need to process reports and facts asynchronously.
Facts processing is currently implemented in foreman-task but reports are still done in foreman-background.
Would that be possible to implement report processing in foreman-task in order to avoid a deployment with both plugin ?

Thoughts ?


Related issues

Related to Foreman - Feature #18618: Use Dynflow as an ActiveJob backendClosed2017-02-22

History

#1 Updated by Ivan Necas almost 6 years ago

Yes, it does not make sense to support two ways of running async tasks. Should not be hard to do (it would be very similar to how the facts import works),
there was just bigger need for the facts import being async in chef world.

Btw. do you use both puppet and chef in your infra: there are different requirements for the facts imports (puppet expects the sync one, while
in chef, it's vice versa.

#2 Updated by Romain Vrignaud over 5 years ago

Ivan Necas wrote:

Btw. do you use both puppet and chef in your infra: there are different requirements for the facts imports (puppet expects the sync one, while
in chef, it's vice versa.

Sorry I didn't see the question. I'm currently only using Chef in my infrastructure.

#3 Updated by Anonymous over 3 years ago

  • Related to Feature #18618: Use Dynflow as an ActiveJob backend added

Also available in: Atom PDF