From 4c988c1f32940be525f120e65014d00b08378134 Mon Sep 17 00:00:00 2001 From: "Gareth J. Greenaway" Date: Mon, 21 Dec 2020 09:59:03 -0800 Subject: [PATCH 1/3] Adding a SEP for change proposed changes to state system, adding the ability to add states automatically from the state system. --- add_beacons_from_states.md | 41 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 add_beacons_from_states.md diff --git a/add_beacons_from_states.md b/add_beacons_from_states.md new file mode 100644 index 0000000..9110b53 --- /dev/null +++ b/add_beacons_from_states.md @@ -0,0 +1,41 @@ +- Feature Name: Add Beacons from Salt States +- Start Date: 2020-12-21 +- SEP Status: Draft +- SEP PR: (leave this empty) +- Salt Issue: (leave this empty) + +# Summary +[summary]: #summary + +Adding a new global option to Salt state system that would audomatically add a beacon on the targeted minion for specific functions in specific state modules. + +# Motivation +[motivation]: #motivation + +Adding this new option would allow beacons easier and associating them with Salt managed resources. + +# Design +[design]: #detailed-design + +The design and implementation of this new option would done in a similar way to the mod_watch system. During a state run +the various individual states will be scanned and those that include the beacon option will be run through a function that +calls a "mod_beacon" function in the desired state module. This "mod_beacon" function would create the beacon using the +configured resources associated with the state in question, eg. the PKGs, files, or services. + +## Alternatives +[alternatives]: #alternatives + +N/A + +## Unresolved questions +[unresolved]: #unresolved-questions + +- If we want to allow the configured beacon to be configurable or only have specific states use specific beacons. +- Allow the beacons for specific use cases to be combined, eg. a common beacon which monitors PKGs. + +# Drawbacks +[drawbacks]: #drawbacks + +Why should we *not* do this? Please consider: + +- This addition would add another level of complexity to the state system. From 89cfec6b3b3d218c19715e29e944fc8affb03985 Mon Sep 17 00:00:00 2001 From: "Gareth J. Greenaway" Date: Mon, 25 Jan 2021 14:23:08 -0800 Subject: [PATCH 2/3] rename with SEP number. --- add_beacons_from_states.md | 41 -------------------------------------- 1 file changed, 41 deletions(-) delete mode 100644 add_beacons_from_states.md diff --git a/add_beacons_from_states.md b/add_beacons_from_states.md deleted file mode 100644 index 9110b53..0000000 --- a/add_beacons_from_states.md +++ /dev/null @@ -1,41 +0,0 @@ -- Feature Name: Add Beacons from Salt States -- Start Date: 2020-12-21 -- SEP Status: Draft -- SEP PR: (leave this empty) -- Salt Issue: (leave this empty) - -# Summary -[summary]: #summary - -Adding a new global option to Salt state system that would audomatically add a beacon on the targeted minion for specific functions in specific state modules. - -# Motivation -[motivation]: #motivation - -Adding this new option would allow beacons easier and associating them with Salt managed resources. - -# Design -[design]: #detailed-design - -The design and implementation of this new option would done in a similar way to the mod_watch system. During a state run -the various individual states will be scanned and those that include the beacon option will be run through a function that -calls a "mod_beacon" function in the desired state module. This "mod_beacon" function would create the beacon using the -configured resources associated with the state in question, eg. the PKGs, files, or services. - -## Alternatives -[alternatives]: #alternatives - -N/A - -## Unresolved questions -[unresolved]: #unresolved-questions - -- If we want to allow the configured beacon to be configurable or only have specific states use specific beacons. -- Allow the beacons for specific use cases to be combined, eg. a common beacon which monitors PKGs. - -# Drawbacks -[drawbacks]: #drawbacks - -Why should we *not* do this? Please consider: - -- This addition would add another level of complexity to the state system. From ce877780f13bf4a19a05c85e5005b099ec4ab60e Mon Sep 17 00:00:00 2001 From: "Gareth J. Greenaway" Date: Mon, 25 Jan 2021 14:23:33 -0800 Subject: [PATCH 3/3] rename with SEP number. --- 0030-add_beacons_from_states.md | 41 +++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 0030-add_beacons_from_states.md diff --git a/0030-add_beacons_from_states.md b/0030-add_beacons_from_states.md new file mode 100644 index 0000000..9110b53 --- /dev/null +++ b/0030-add_beacons_from_states.md @@ -0,0 +1,41 @@ +- Feature Name: Add Beacons from Salt States +- Start Date: 2020-12-21 +- SEP Status: Draft +- SEP PR: (leave this empty) +- Salt Issue: (leave this empty) + +# Summary +[summary]: #summary + +Adding a new global option to Salt state system that would audomatically add a beacon on the targeted minion for specific functions in specific state modules. + +# Motivation +[motivation]: #motivation + +Adding this new option would allow beacons easier and associating them with Salt managed resources. + +# Design +[design]: #detailed-design + +The design and implementation of this new option would done in a similar way to the mod_watch system. During a state run +the various individual states will be scanned and those that include the beacon option will be run through a function that +calls a "mod_beacon" function in the desired state module. This "mod_beacon" function would create the beacon using the +configured resources associated with the state in question, eg. the PKGs, files, or services. + +## Alternatives +[alternatives]: #alternatives + +N/A + +## Unresolved questions +[unresolved]: #unresolved-questions + +- If we want to allow the configured beacon to be configurable or only have specific states use specific beacons. +- Allow the beacons for specific use cases to be combined, eg. a common beacon which monitors PKGs. + +# Drawbacks +[drawbacks]: #drawbacks + +Why should we *not* do this? Please consider: + +- This addition would add another level of complexity to the state system.