1. Proposed title of this feature request

[RFE] Create a tunable dynflow that allows for custom prioritization of tasks

3. What is the nature and description of the request?

Occasionally on large satellites, certain actions in the environment may cause an influx of tasks that can starve out other more timely tasks, or tasks that have a higher business importance.

For example, a change to repos across the environment may cause a high number of tasks to regenerate errata applicability, which may interfere with something more user-driven like a Host Creation task from provisioning, or a one-time task like a host registration.

Customer would like a way to prioritize certain tasks so that they can jump ahead of a potential wave of other less important tasks.

4. Why does the customer need this? (List the business requirements here)

Certain actions in the environment like building a new host or registering it, or promoting new content have a higher expectation of availability, while others like package profile uploads can be done whenever. Allowing for customer customization could help solve business priorities first.

5. How would the customer like to achieve this? (List the functional requirements here)

The implementation is fairly open for discussion, but it is envisioned as a giving priority to certain task types over others. (a "nice" system for foreman tasks may be a good analogy)

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Customer would prioritize certain task types, and then when an overwhelming number of tasks of a lower priority were encountered, the high-priority business task would succeed without having to wait for the numerous less important tasks.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

No. There are BZs for improving the queue (BZ#1609371), but this RFE is asking for more of a user control over customization of priority.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No

9. Is the sales team involved in this request and do they have any additional input?

No

10. List any affected packages or components.

11. Would the customer be able to assist in testing this functionality if implemented?