Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

SEP 17 - Job acknowledgement events #23

Merged
merged 1 commit into from
Jan 6, 2020

Conversation

lukasraska
Copy link
Contributor

Rendered markdown: https://github.com/lukasraska/salt-enhancement-proposals/blob/job-ack-event/job-ack-event.md

Basic idea is to be able to determine whether minion received job event, or not (due to various reasons). Particularly usable in integrated systems to determine if retrying is an option.

@lukasraska lukasraska requested a review from a team as a code owner October 24, 2019 12:45
@ghost ghost requested review from dwoz and removed request for a team October 24, 2019 12:45
@thatch45
Copy link
Contributor

I LOVE this SEP, I made the saltutil.running system before beacons and the event bus was in full swing! I would also consider leveraging a beacon that also just fired what jobs are running on a regular cadence which would be much smoother than how we track running jobs now

@lukasraska
Copy link
Contributor Author

Beacon could be an option here, to periodically send all running jobs. That will however not help 100% here. It will almost certainly miss short-running jobs (but then you will receive return event from the job, so not that big of an issue), but it won't be "realtime" and will always fire.

If the beacon is set up for every minute and the job lasts 30 minutes, you get 30 events instead of single ack. But as temporary solution it's usable. I was also looking into how engines are working on minion, but it seems it can only listen for fired events from minion, not the opposite way (so essentially it works as on master, you can catch what minion sends, not what master sends).

@waynew
Copy link
Contributor

waynew commented Oct 29, 2019

Yeah, I don't have much to add other than this is a fantastic idea :)

@waynew waynew changed the title Job acknowledgement events SEP 17: Job acknowledgement events Nov 14, 2019
@waynew waynew changed the title SEP 17: Job acknowledgement events SEP 17 - Job acknowledgement events Nov 14, 2019
@lukasraska
Copy link
Contributor Author

@waynew Could we get this moved to "Final Comment Period"? :)

@waynew waynew added the Final Comment Period Speak now or forever hold your peace. label Dec 5, 2019
@waynew
Copy link
Contributor

waynew commented Dec 5, 2019

@lukasraska yeah, sorry for the delay - there has been much travel and holiday time. I'll bring it up in our core meeting tomorrow.

@waynew
Copy link
Contributor

waynew commented Dec 6, 2019

@lukasraska I brought it up in our meeting, and the consensus is 👍

There should be some official votes coming in soon and we can get this approved/merged. In our discussion it came up that this is an awesome idea, but it's potentially a large undertaking. @thatch45 has a bunch of information that he plans to share, but this week is super busy for him. You should be able to expect a response from him next Friday.

Let us know if you have any other questions!

@lukasraska
Copy link
Contributor Author

Great, I have PR for this ready (with tests, more or less), so I will just wait for follow-up

@lukasraska
Copy link
Contributor Author

Any comment to this SEP, @thatch45 ?
If not, I will prepare the implementation and it can be incrementally enhanced as the details arise. Thanks

waynew added a commit that referenced this pull request Jan 6, 2020
@waynew waynew merged commit 01da6bc into saltstack:master Jan 6, 2020
@waynew waynew added Accepted and removed Final Comment Period Speak now or forever hold your peace. labels Jan 6, 2020
@waynew
Copy link
Contributor

waynew commented Jan 6, 2020

@lukasraska This SEP has been accepted 👍

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants